POLICIES / PREVIEW

Privacy Policy

1. Information processed

Account features use an email address, an authentication identifier, and account approval status. The community stores profile names, bios, visibility preferences, badge assignments, avatars/banners, and image positioning. Reporting and moderation features store report details, statuses, staff notes, and action records. Site preferences can be stored in your browser.

2. Public and private information

Only profiles you mark public are listed in the member directory. Public profiles display the information and images you submit. Email addresses, private reports, and internal moderation notes are not displayed in public search. Uploaded images use publicly accessible Storage URLs, which are not made secret by switching a profile to private.

3. What the information is used for

Information is processed to provide sign-in, determine account access, customize profiles, show community search, receive reports, prevent abuse, troubleshoot service problems, and operate relay tools where enabled.

4. Providers and technical data

Supabase is used for authentication, profile data, and image storage. Cloudflare serves website traffic. Render or other infrastructure providers may handle relay requests when those features are used. Providers may process necessary connection information, such as IP addresses and technical logs, under their own policies. Websites visited through relay tools may also have separate privacy practices.

5. Cookies and local storage

The site uses browser storage to maintain account sessions and remember local preferences. Authentication uses Supabase's session system. Some settings, notes, or saved shortcuts may be stored locally in your browser.

Appeals and administrative email

If you appeal a suspension, we store your appeal message, account ID, ticket status, and any private staff review notes. When email notifications are configured, the appeal text and account email may be sent to the site's authorized administrator through an email delivery provider for ticket review. Only include details necessary for your appeal.

6. Retention and deletion

Account, profile, and moderation records may remain while needed to operate the service, review abuse, or comply with applicable requirements. The operator has not yet confirmed exact deletion schedules or a contact for account and data-deletion requests; both must be finalized before production. Removing an avatar or banner from a profile does not necessarily delete its file, publicly shared URL, or provider backups. Users should avoid uploading private or sensitive images.

7. Security and requests

Access to staff moderation data is restricted by database permissions. No system can guarantee absolute security. Before production release, the owner must specify how users can request access, correction, or deletion of personal information and how to contact the service administrator.

8. Age requirement and younger users

Zeyad's Stuff is intended for users aged 13 and older. Registration includes a declaration that the user is at least 13; this is self-reported and is not a verified age check. We do not intentionally offer accounts to children under 13. If we learn that an account belongs to someone under 13, we may restrict it while reviewing deletion of associated personal information as applicable. We should not ask users to submit an ID or full birth date just to use the preview.

Users aged 13–17 may have additional rights or protections under applicable laws. Before production, the operator must review regional age, consent, advertising, and privacy requirements and clearly document how users or guardians can contact the service about a younger user's data.