Privacy notice

Data controller

The data controller is Hammerank’s non-professional publisher. They can be contacted through the public “Contact / report” form.

OpenAI processes hosted data to provide Sites under the ChatGPT Sites Data Processing Addendum. Supabase provides authentication and processes the data needed to create accounts, sign users in and manage sessions. Google acts as the identity provider only when a user chooses Google sign-in.

Data we collect

• Account and identity: email address, Supabase technical identifier, sign-in method, mandatory Hammerank username, earned badges and selected public badge. Administrators may add an optional Twitch or YouTube link for a “Creator” badge. For Google sign-in, Google may provide Supabase with the identity data required for authentication, including an email address and profile information.
• Password: it is submitted to and managed by Supabase. Hammerank does not access the plain-text password or store it in its own database.
• Run: public player name, faction, lord, victory type, turn count, game version, required settings and submission status.
• Evidence and validation: the .save file is received and processed transiently, then its binary content is discarded as soon as the check finishes, whether the submission is accepted or rejected. For an accepted run, only the result and its technical metadata may be recorded: SHA-256 fingerprint, size, validator version and extracted facts (campaign identity, victory, turn, game version and settings).
• Communications: private administration notes, report subject and details, and any optional contact submitted with a report.
• Preferences, session and technical data: language, recently viewed lords, session tokens kept in the browser, security logs and data needed to operate Supabase and Sites.

Purposes and legal bases

• Creating and securing an account: email-and-password or Google authentication, email confirmation, session maintenance and password recovery, for performance of the requested service.
• Assigning a unique public username: creating the Hammerank profile and linking runs to the account, for performance of the requested service.
• Providing a profile, receiving a run, awarding badges and displaying rankings: performance of the terms and steps requested by the user.
• Transiently analysing the save and publishing the player name and result: performance of the requested service. The file is used only for the automated check and is not retained afterwards.
• Handling reports, preventing abuse and securing the service: legitimate interests in Hammerank’s integrity, security and operation.
• Meeting an obligation or responding to an authority: applicable legal obligation.

Recipients and public visibility

The public can see the player name, result, ranking and selected badge. When a “Creator” badge is selected, its Twitch or YouTube link is also public. The save itself is never published or downloadable. Email addresses, private notes, the save fingerprint, detailed validation evidence and report contact details are not displayed publicly.

Data may be accessed by the publisher and service administrators, by OpenAI for hosting, by Supabase for authentication and, only when that method is selected, by Google for sign-in. Each receives only the data needed for its role. The Sites addendum describes safeguards used when certain transfers outside the European Economic Area are required.

Retention periods

• Hammerank account, username, badges and optional creator link: while the account is used, then until technical deletion or for the time needed to process an account-deletion request. After deletion, an awarded Pioneer number may remain reserved in anonymised form so that it is not reassigned.
• Authentication and session data: according to the retention settings applied by Supabase. The local session persists in the browser until sign-out, expiry or clearing of browser storage.
• Binary save content: no retention after analysis. The file is discarded as soon as the check finishes, including when the submission is rejected.
• Published run, player name, result and validation metadata: while the leaderboard is operated, until the player requests removal, or until the service closes.
• Administration notes: only as long as needed, and no longer than 12 months after closure when a record is necessary.
• Report and optional contact: while it is handled, and no longer than 12 months after closure unless required for a dispute or legal duty.
• Local preferences: until cleared in the browser. Technical logs follow the retention periods applied by Sites.
• Save folder: if you choose one, a reference may be remembered in this browser to find your files when you click “Find a Hammerank campaign”. It stays on your device and can be removed with “Forget folder”. You can also revoke access in your browser settings. Searching does not upload your files to the site.

Your rights

Depending on your circumstances and applicable law, you may request access, correction, deletion, restriction or portability, or object to certain processing.

The “Export my data” feature in the profile downloads the Hammerank data linked to the account. A published run and its metadata can be withdrawn from the profile. “Delete my account” removes the profile, runs and their metadata after an explicit confirmation. For another data-rights request, or when deletion or withdrawal cannot be completed from the profile, use the public “Contact / report” form and identify the account or run concerned. Limited proof of identity may be requested where there is reasonable doubt.

You may also complain to the CNIL or the data protection authority in your country.

Local storage, cookies and security

Browser storage remembers your language, recently viewed lords and sign-in session. An internal counter measures visits and page views without recording IP addresses, email addresses or full URLs. Each tab uses a random visit identifier, renewed after 30 minutes without a new page view or at midnight. Deduplication records older than 48 hours and daily totals older than 90 days are deleted the next time statistics are collected or viewed. Visits from signed-in owner or administrator accounts are excluded. No advertising is displayed.

Closed-season standings are archived. When an account is deleted, its username and badge are anonymised; historical points and ranks are retained.

Reasonable measures are used to limit unauthorised access. No online service can guarantee absolute security; avoid including unnecessary personal data in a save or its filename, notes or reports, even though the save is processed only transiently.

Account confirmation and recovery use Supabase authentication services.