PRIVACY NOTICE / V1

Measure the catalog without turning visitors into profiles.

MakeGameWithAI uses PostHog Web Analytics to understand which pages, production stages, and tools are useful. Analytics is used to improve editorial priorities and site navigation.

01

What analytics collects

Events can include visited URLs, referring pages, UTM campaign parameters, browser and device information, anonymous device and session identifiers, and interactions such as opening a tool, choosing a production category, or using a directory filter. Events also include a yes/no flag for signed-in internal or test accounts so their traffic can be excluded. The server checks that status without sending account IDs, names, or email addresses to PostHog.

02

Browser storage

PostHog uses a first-party cookie and local storage to keep anonymous device and session identifiers. This allows us to distinguish a return visit and understand navigation across sessions. We do not call PostHog identify or attach names and email addresses to analytics profiles.

03

What is excluded

Session replay and PostHog surveys are disabled. The submission preview is excluded from autocapture, and PostHog does not collect the text entered into its fields. External tool websites have their own privacy practices.

04

Provider and purpose

Analytics events are processed in the MakeGameWithAI project on PostHog US Cloud. We use aggregated traffic, source, page, and interaction patterns to choose what to research and improve; we do not sell analytics data.

05

Your choices

You can block or clear cookies and site data through your browser or use content-blocking tools. The directory remains available when analytics is blocked, although a return visit may no longer be recognized as the same anonymous browser.

06

Site and community accounts

Accounts store your email, display name, email verification status, login sessions, and a password hash if you set a password, in a separate PostgreSQL database hosted on Railway. Passwords are not stored as plaintext. Verification and reset links are time-limited; pending email links are encrypted and removed after SMTP acceptance or expiry. Account pages do not load visitor analytics. Session cookies are necessary for sign-in; security records may include IP address and user agent.

07

Community identity and email

After you sign in and enter the community, Discourse receives your stable site user ID, verified email, display name, and initial username. It maintains its own session and community profile, posts, and activity. The site and forum do not share passwords. Production verification, password-reset and forum notification emails are delivered through Resend. Site logout and password reset do not end existing forum sessions. Contact [email protected] for account or privacy requests; account deletion is handled manually during private beta.

08

Optional Google sign-in

When Google sign-in is enabled and you choose it, your browser visits Google to authenticate. We request only OpenID, email and basic profile scopes, not Gmail or Drive access. We retain your Google account identifier, verified email and display name to recognize your site account. A matching, already-verified site email links to the same site account and forum identity. Google tokens are used during sign-in but not retained in account credentials; we do not store your Google password or profile picture. Temporary state and essential cookies protect the sign-in redirect. If your Google account's email is not hosted by Gmail or Google Workspace, use email sign-in instead.

09

Tool submissions, claims and maintenance

When the tool workspace is enabled, we retain account links, submission and claim evidence, revisions, review records, images and permission statements to verify ownership and maintain reviewed information. Claim evidence, original submissions and drafts are limited to their applicants, authorized maintainers and site reviewers. Reviewed and published product facts and selected images are public. Images are stored in a private object store; only approved images referenced by the current public revision are served publicly through this site. Workspace pages do not load analytics or advertising. Inputs may be saved in the current browser tab to restore after sign-in. Temporary uploads with no revision references become eligible for cleanup after 24 hours. Referenced or reviewed evidence is retained for maintenance and audit with no automated deletion deadline yet. Contact [email protected] for privacy or deletion requests; the site manually reviews the affected content and backups.

10

DNS claim verification

If you choose DNS verification, you publish a random verification code in the official domain’s public TXT records. Our server queries Google Public DNS and Cloudflare 1.1.1.1 using the record name, without sending your account ID, email or private claim materials. We retain the verified domain, time and result as an access-control record. DNS verification codes are publicly visible while published; you may remove this one-time record after a successful claim. We do not request your domain account password or DNS management keys.