Privacy Notice \u2014 GDPR & Data Rights

Draft updated 14 October 2026 · Version 0.2 · Review before launch

This notice describes the personal data processed by the current development build. It must be revised after a live infrastructure, email vendor, backups, third-party integrations and any new features are configured. The individual operator identified below is the intended data controller.

Data we collect and purposes

• Account email, scrypt password hash, country code, adult verification timestamp and Terms acceptance timestamp: account creation, lawful access and eligibility.
• Temporary date of birth: used at registration to check age 18+; the full birth date is not persisted in the account database.
• Essential login cookie and hashed session token in PostgreSQL: secure authenticated access; nominal expiry after seven days.
• Bot, application identifiers, encrypted GameVox bot credentials, workflow graphs, and execution results: provide requested bot-building functionality.
• Pseudonymous HMAC rate-limit keys, short-lived reset token hashes and operational error events: prevent abuse, recover access and diagnose failures.

Legal bases

Account creation and bot services normally rely on contractual necessity under GDPR Article 6(1)(b); security, abuse prevention and basic technical operations may rely on legitimate interests under Article 6(1)(f), subject to balancing; legal retention may rely on Article 6(1)(c). Terms acceptance is not a blanket consent for optional analytics or unrelated processing. No tracking consent is collected because this build does not deploy non-essential trackers.

Third parties, transfers and processors

Hosting providers and the configured outbound email provider (if password reset is enabled) may process limited account or connection metadata as service providers. GameVox receives requests and bot operations associated with connected applications. Users may separately visit GameVox documentation links, which are external sites. No Google Analytics, Google Fonts requests, session replay, advertising SDK, keystroke recording, or embedded third-party content is included in this build. Hosting, operating-system, anti-abuse, network providers and device browsers may process connection metadata; verify contracts and international transfer safeguards before launch.

Retention and deletion

Accounts and their bots are kept while active. Session records expire after seven days and password reset tokens after ten minutes; expired records must also be pruned by the scheduled cleanup job. Execution history is configured for deletion after 90 days when cleanup is enabled. Rate limit records expire when their windows close and are pruned by cleanup. Account deletion cascades account projects, runs and associated login/reset records from the active database. Database snapshots, email delivery records and system/security logs are subject to separate documented retention schedules and cannot be truthfully promised to disappear instantly.

Rights and requests

Where applicable, you may request access, correction, deletion, restriction, portability, object to certain processing and complain to your local supervisory authority. Use Account & Privacy to export current account data or delete your account, or contact the operator for identity-verified requests. California and other regional rights may also apply depending on legal applicability and statutory thresholds; the Service does not sell user data or use it for cross-context behavioral advertising in this build.

Security and incidents

Controls include secure server-side sessions, encrypted stored bot credentials, origin protection, database parameterized queries, access ownership checks and request limits. No system is immune from compromise. Suspected breaches will be investigated and reported to affected users and authorities where required. Do not send secrets or sensitive personal information through general support email.

Minors

The Service is intended only for adults 18+. If we identify an account belonging to a minor, we will take steps to restrict access and assess deletion of improperly collected data. No parental consent or age-verification identity documents are collected in this build.

Individual operator and contact

Website operator: NOT CONFIGURED — operator legal identity required before launch
Contact email: NOT CONFIGURED — contact email required before launch
Public contact address: NOT CONFIGURED — public contact address required before launch

These documents are draft templates, not a legal-compliance certification. Complete the operator details, assess actual hosting and processors, obtain jurisdiction-specific legal advice, and confirm all statements match the deployed service before publication.