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.

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, password hash, and login sessions 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. Transactional emails go through the configured delivery service; in internal tests Mailpit captures them instead of delivering them externally. 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.