Yazan dev collects only the information needed for accounts, game discovery, publishing, and moderation. The operator must configure Firebase Authentication and deploy the separate publishing API before these services are active.
Firebase Authentication, Google, Groq, GitHub, Render, and the hosting provider process data under their own terms. The operator controls configuration and retention. No automated submission-retention or account-deletion job is included.
Private submissions and administrator actions are protected by server-side verification of Firebase ID tokens and the administrator custom claim. Never include API keys, authentication tokens, or private personal data in game uploads.
You can choose not to create an account or submit a game. Publicly served game files may be copied and cannot be made private simply by removing a listing. For questions or removal requests, contact the maintainer through the official GitHub profile.
This template is not legal advice. The operator must add the operating entity, jurisdiction, contact details, retention periods, and applicable integrations before launch.