Your data on PostYourGame.

Information we use

Public game posts. Listings may include a creator’s public name or handle, profile link, source post, images or video, and game links. We find imported posts through public platforms, search and data services, or submissions, and link their original source. Posts written here contain the author’s own text, public name, optional contact and game links, and uploaded media. Declared contact links do not verify an author’s identity.

Submissions and reports. We store the link and details you send so we can review them. If you choose email updates, we also store your address until you unsubscribe or it is removed under our retention rules. Your private receipt gives access to your request status, so keep its link to yourself. A submission may become a public listing; your email address and private report details are not published.

Posts you write here. We store drafts, proposed and published versions, review decisions and upload records. An anonymous private receipt gives its holder access to manage that post. You may link a community account for longer-term access to your own posts; importing someone’s source post does not grant ownership of it. Your first native post is reviewed before publication.

Optional submission sign-in. If you submit while signed in, we privately link the request to your community account. We record source-check results and, when the operator grants or revokes submission recognition after review, the decision and its reason. Recognition is private and does not verify creator ownership. It may allow supported posts that pass automatic checks to publish without waiting for human review; uncertain or unavailable sources still need review. Email-code sign-in alone does not grant recognition.

Community conversations. Your pseudonym and comments or replies are public. Your sign-in email is used privately by Supabase Auth to send and verify access codes; we do not publish it or automatically use it as your pseudonym. Comment reports and moderation reasons stay private. Optional reply notifications are off by default and appear in your community profile on this site.

Optional public profiles. Your public profile is off by default. If you enable it, visitors can see your chosen pseudonym, avatar, biography and selected eligible game affiliations. An enabled profile is searchable on this site. A public biography or selected public game affiliation also allows its page to appear in search engines; a pseudonym-only profile is kept out of our sitemap and marked not to be indexed. Opting out removes that profile and its creator introductions from public and Following views. Search engines and other caches may take time to reflect removal. A public profile, email-code sign-in and a game relationship are separate choices.

Games, teams and authority requests. Private game drafts, team invitations and explanations help you prepare and manage a space. The operator reviews authority claims, recovery requests and disputes. Known team members can receive an in-app case notice; their own view does not disclose the requester’s private evidence. No automatic email is sent for these notices. Membership and publication trust are separate; neither lets a game manager moderate other people’s criticism.

Private Following. Game and creator follows, dates, activity read markers and command receipts are private. Following a creator does not follow their games automatically. Creator introductions are explicit announcements. Only an authorized creator’s private introduction preview shows aggregate reach; follower identities and individual read activity are not published. Following does not send email or change your separate reply notifications.

Community sessions and drafts. Signing in sets separate functional, HttpOnly community authentication cookies, with browser lifetimes of one hour for the access cookie and 60 days for the refresh cookie. They are separate from operator access and do not grant moderation rights. Cookie expiry does not itself delete your account. Comment drafts can be saved privately on the server and are also kept temporarily in this tab’s session storage so they survive sign-in, errors and reloads. Authentication tokens are not saved with drafts.

Native drafts and uploads in your browser. This tab temporarily stores your native draft and its private receipt capability so you can recover after a reload. Upload resume records may also remain in browser storage. These records contain scoped upload references, not your account authentication tokens or selected file bytes. You may need to select an unfinished file again. Keep private receipt links to yourself and clear browser storage on a shared device.

Votes and basic preferences. When you vote, a functional browser cookie identifies your votes for up to 180 days. Our database stores a keyed hash of that identifier. Your light or dark theme choice is saved in your browser until you clear it. We do not add advertising trackers or third-party audience analytics.

Security. Network information is used to limit abuse. Application rate limits use keyed hashes of IP addresses. Hosting, database and email providers may also retain technical logs. Operator accounts use separate authentication cookies; visitors do not need an operator account.

Why we use it

We use public source information to help people discover games and credit their creators, and private request details to review submissions and corrections. Community profile and session information lets you participate under a pseudonym, manage your comments and receive the in-app reply notifications you choose. Private comment reports support moderation. We propose legitimate interests for catalogue discovery, requested community features, vote integrity and abuse prevention, while the assessment remains incomplete. You can object to processing involving your personal information.

Optional status emails depend on your choice to receive them and confirmation of your address. They concern your request, not a newsletter or marketing list. You can withdraw that choice without affecting the review of your request.

Service providers and media

Vercel hosts the site, Supabase stores application data and uploaded media and manages operator and community sign-in, Resend sends access codes and requested service emails, and Zoho handles messages sent to our contact address. Native uploads first go to private storage for validation and preparation; approved posts use public media copies. Treg and its upstream search and data providers help us discover public game posts from social platforms and project sites. We do not send private submission emails, community sign-in codes or report text to game-discovery providers.

OpenAI’s Codex assists the operator’s supervised review of public game posts and may assist with requests sent to our contact address. Information provided in those sessions is processed by OpenAI. Read OpenAI’s privacy information.

Images and video posters may load from their original hosts when you browse. Those hosts receive the network information needed to serve the media. YouTube players connect to YouTube only when you choose Load video. The privacy-enhanced player can still use browser storage for technical functions, such as caching player icons and checking local database support. Read Google’s privacy information. Loading or playing other videos can also connect to their original hosts. Visiting a source, game or download link takes you to another service with its own privacy practices.

Share does not load social widgets, connect an account or post automatically. Opening a network composer sends the public draft text and listing link you choose to that network; copied text stays in your clipboard. Device sharing uses your system’s share sheet. We do not call social posting APIs or count shares. Private receipts, sign-in details and report text are excluded from generated sharing drafts.

Our application database is hosted in France, and our contact mailbox uses Zoho’s EU service. Provider processing can also take place outside the European Economic Area: Resend stores messages and delivery data in the United States, Vercel provides international hosting services, and Zoho describes limited support access from India. Treg also describes processing in the United States.

Provider contracts publish safeguards for relevant transfers, including Standard Contractual Clauses. The account-specific contracts and transfer safeguards are still being verified. Contact hello@postyourgame.com for information about the safeguards relevant to your data. Their policies describe their handling of data: Vercel, Supabase, Resend, Zoho and Treg.

How long we keep it

Email confirmation links expire after 24 hours and private receipt links after 180 days. Unsubscribing removes the address from that request immediately. Addresses associated with delivery failures or spam complaints are suppressed to prevent further mail; a keyed hash may be kept for that purpose.

An anonymous native receipt also lasts 180 days from reservation. A linked account can retain management access after that receipt expires. Native cleanup rules make never-published private content eligible for expiry after 180 days of inactivity, or earlier when an unlinked receipt expires. An active linked draft can survive its receipt’s expiry. Expiry removes private text, revision copies and receipt access, then queues associated media for removal with at least a 7-day delay. Upload permissions expire after two hours, but an existing resumable session can remain writable longer. Private originals also wait at least 48 hours after their recorded writing window ends so an old session cannot restore a removed file. These rules describe cleanup eligibility, with retries and storage removal handled separately.

Our implemented maintenance rules make unverified contact addresses eligible for removal after 7 days and contact details and free-text request details 180 days after a case is completed. Message-delivery references become eligible after 30 days and inactive submission rate-limit records after 24 hours. Automatic cleanup is disabled and unscheduled, so these are eligibility thresholds, not a promise of deletion on those dates.

We have adopted a retention policy of 12 months after the last relevant action for remaining closed support and report records, 180 days after review closure for rejected private discovery material, and a rolling 90-day rotation for our private recovery copies. The shorter contact and free-text eligibility rules above still apply. Records outside the bounded cleanup tools and recovery-copy rotation require a separate manual review by the operator, with Codex assistance. These policies do not mean that provider backups or correspondence have already been purged.

Community cleanup defaults make hourly abuse-limit records eligible 24 hours after their window ends. Optional reply notifications become eligible 30 days after being marked read, or 90 days after creation if still unread. Cleanup is bounded to 500 records per category per run, with one combined notification limit; a backlog can delay removal. These rules are implemented but automatic cleanup remains disabled.

Private game-space and saved feedback drafts expire after 180 days without a saved edit. Expired account text becomes unavailable; a separate manual cleanup path removes it in bounded batches and has no automatic schedule. Bodyless draft versions and minimal request fingerprints prevent an old tab from silently restoring expired text. Text still held in your own tab can be copied into a deliberately created new draft. Native post drafts keep their separate rules above. These are not guarantees of immediate physical removal on an expiry date.

Closed game-authority cases and comment reports become eligible for private-text cleanup after 180 days and removal of account/reviewer references after 12 months. Open cases and cases keeping management paused remain available for review. Minimal decision and report identifiers can remain to prevent old requests from recreating erased details. Private identity-change notices become eligible after 180 days; closed authority notices use the same period from closure. Technical correction history, aliases and publication-event identities remain so corrections can be understood and safely reversed.

Team invitations expire after seven days; invitation records become eligible for removal 180 days after expiry. Private follows and their read markers remain while you keep that follow, and are removed on unfollow or account deletion. Cleanup does not make old activity unread again. Abandoned avatar and cover uploads become eligible after an hour, with their recorded writing window and a five-minute safety margin respected. A failed storage deletion stays queued for retry; removing visibility and removing stored bytes are separate steps.

Deleting your own comment removes its public text; a placeholder may remain to keep replies understandable. To delete your community account, email hello@postyourgame.com. Once we verify your request, we remove your sign-in account, public pseudonym and comment text, including hidden comments. Your old sessions can no longer access community features. Other people’s replies stay in place; a deleted-comment placeholder is shown only where needed to preserve those replies.

We keep minimal comment and deletion identifiers and request fingerprints to prevent erased text or accounts from being restored by a repeated request. Private moderation reports, audit records and security information are reviewed separately when handling your request; they are not all automatically erased. There is no automatic age-based deletion of community accounts. Independently imported game listings remain separate from community accounts: use our correction and removal form to ask about one.

Deleting a linked account also removes its optional public profile, avatar, private follows, activity markers and drafts, and ends its game-team access. Its personal native posts are withdrawn and their text, revisions and media are removed through the deletion process; private receipt capabilities are revoked. Posts explicitly created under the collective game contract can remain after publication with a nonidentifying “Former team member” signature. Unpublished collective drafts and the erased member’s unapproved uploads are removed; another living member’s pending revision is preserved without the erased author’s signature. Existing personal posts are never converted to collective posts by joining or leaving a team. Other people’s comments and independently imported posts are preserved. Media removal can take time while storage cleanup retries, and browser or delivery caches can retain copies temporarily.

The last responsible member can also request account deletion. Useful game history can remain without representation, while an empty space is withdrawn. Further management requires an evidence-reviewed recovery. Invitations, authority evidence and actor references are removed or detached; minimal tombstones, publication event identities and deletion receipts remain to prevent replay from restoring erased data. Private report text and separate security records are reviewed separately.

Published posts remain in the catalogue as they age. We retain source attribution, review history and records needed to avoid reimporting removed sources. Open requests remain available while they are being handled. Provider logs, backups and correspondence sent directly to our mailbox have separate retention; contact us about removal from those systems.

Your choices and rights

Use the unsubscribe link in a status email to stop updates for that request. You can browse and submit without giving an email address. Clearing browser storage removes your local theme preference, voting cookie, stored comment and native drafts, and upload resume records. Save a private receipt elsewhere first if you still need it. Sign out from your community profile to end that browser’s community session.

Manage a post you wrote here through its private receipt or linked account: propose edits, withdraw it or add a substantive update. Withdrawal removes public access and starts media cleanup; temporary cached copies may remain.

In Settings, you can change your pseudonym, choose whether to publish a profile and turn in-app reply notifications on or off. Manage private follows in Your space. Use Delete beneath your own comment to remove it, or Report beneath a comment to request moderation. Save the private report receipt to read its state and decision; contact us with the case reference to appeal. A report does not automatically hide content. These notifications are separate from submission status emails.

To request access, correction, deletion, restriction or, where applicable, a portable copy of your personal information, or to object to its use, email hello@postyourgame.com. We may need enough information to confirm that a request concerns you. The usual response deadline is one month; we will explain any permitted extension or limits. Deletion from the live service may not immediately erase separate backups; we will explain how retained copies are handled.

You can also contact your local data protection authority or the Belgian Data Protection Authority. For a wrong credit or a source you want reviewed, our correction and removal form is another way to reach us.