Privacy policy | DeadlockHacks

Scope and operator

This notice describes the functionality implemented by Deadlock Hacks. The operator’s legal identity and contact details must be supplied before a public launch. Until then, the project is a local preview. It is not affiliated with Valve, Google or Discord.

Account information

If account sign-in is enabled, the authentication provider supplies information such as your name, email address and profile picture. Discord may also supply your username. The site stores provider account identifiers, protected session records and the information needed to manage access. Provider credentials are handled by the provider; they are not requested in an article or contact message.

Readership analytics

First-party analytics count page views and group them by article, topic, day, referring hostname and broad browser family. A random first-party visitor identifier is transformed with a server-side secret before it is stored with an event. Analytics do not store a raw IP address as the reader identifier. Repeated views of the same page within a 30-minute period are deduplicated. Automated clients are filtered where identifiable.

Cookies

Authentication uses session cookies to keep you signed in. A first-party readership cookie may last up to 30 days. You can remove cookies through your browser. Reading public articles does not require an account. Removing cookies may sign you out and will reset readership deduplication.

Storage and retention

Editorial content, accounts, audit events and analytics are stored in PostgreSQL. Uploaded images are stored on the operator’s configured storage. OAuth and session records may include technical security information needed for authentication. The operator must set and publish retention periods before public launch; no unverified retention promise is made here.

External services and links

Google or Discord sign-in sends you to the selected provider and is subject to its privacy terms. External article links take you to other websites. Optional third-party analytics are disabled unless separately configured; any public deployment must update this notice and obtain consent where required before enabling them.

Your requests

Use the contact details on the contact page to request access, correction or deletion of account information. Operator contact details are pending for this local preview. Do not include a password, session token or other secret in a request.

Editorial policy · Corrections · Contact