ABYSS GAMING HUB← Return to site
Legal & privacy

Privacy Policy

This policy describes the current data practices of Abyss Gaming Hub, an independent personal/portfolio gaming project.

Last updated: October 10, 2026 · Policy version 2026-10-10

Scope and important note

This page is a good-faith description of the current implementation. It is not a promise that laws cannot change or that using this policy makes the site immune from legal claims. If Abyss becomes a commercial service, adds advertising/analytics, materially expands public registration, or begins targeting children, the operator should have the policies reviewed by qualified counsel.

Information Abyss processes

Why the information is used

Abyss does not currently use your account data for targeted advertising and does not include a third-party advertising or behavioral-analytics SDK in the core Hub.

Cookies, local storage and sessions

The authenticated Hub uses a first-party HttpOnly session cookie with a SameSite setting; HTTPS deployments mark the session appropriately for secure transport. The Hub also uses browser local/session storage for functional features. See Cookies & Storage for the current inventory.

Third-party services

Cloudflare Turnstile

When public bot protection is enabled, the login/register page can load Cloudflare Turnstile. Turnstile may process technical/device information necessary to determine whether a request is likely automated. Cloudflare's own privacy terms govern its processing. Cloudflare Privacy Policy.

External links and data sources

The Hub may link to or use public game-information/artwork sources for collection maintenance. Those third-party sites have their own practices. Abyss does not send them your plaintext password.

Retention and deletion

Account, collection and save information may remain in the site's SQLite data store while an account remains active and while needed for security, backup and operational purposes. The current project does not provide a public self-service account-deletion workflow. A user may ask the site operator directly to review, export, correct or delete account information; the operator should verify the requester before acting.

Security

The current implementation includes salted PBKDF2 password hashing, HttpOnly sessions, CSRF protection, rate limiting, optional MFA, audit logging, HTTPS/public-edge controls and optional Turnstile bot protection. No internet service can guarantee absolute security.

Children

Abyss Gaming Hub is a general-audience personal project and is not intended for children under 13. New registration requires confirmation that the registrant is at least 13. If the operator learns that an account belongs to a child under 13, the account and associated personal information should be reviewed promptly and removed unless lawful parental-consent requirements have been satisfied.

Your choices

You can clear local browser storage through your browser, sign out to end the active authenticated browser session, choose whether to enable optional MFA, and avoid uploading a custom profile image. Clearing local/offline storage may remove locally saved preferences or offline state.

Privacy requests are handled by the site operator. This personal deployment does not currently publish a dedicated privacy-request email address; one should be added before broad public commercialization or account growth.