Privacy

Privacy Policy

Status: Legal review required Version: 1.4-commercial-rc Effective: After owner approval before public launch

This is a pre-release document. Final legal approval and law freshness review are required before public launch.

Revision date: 2026-06-28. Complete the real operator full name, tax identifier and self-employed tax region before publication.

1. Controller

Personal data controller: [self-employed project owner full name], self-employed taxpayer, tax identifier [tax identifier], self-employed tax region [region]. Domain: futuretechcorp.org. Privacy contacts: ft.futuretechcorp@gmail.com, fta4dmin2@yandex.ru.

2. Data categories

The service may process account data, optional email/date of birth/display name, technical data such as IP address, user-agent, HWID/device id, session id, token hash, client type and logs, game profile data, support and moderation records, content artifact metadata and minimal payment/receipt data.

3. Purposes

Data is processed for registration, authentication, account security, MFA, recovery, launcher and server access, Drasl/OIDC integration, support, moderation, content scanning, paid services, receipts, anti-fraud, incident investigation, backup, audit, legal compliance and information security.

4. Legal basis and consent records

Processing is based on terms acceptance, user consent, contract performance, operator obligations, legitimate protection of the service and users, payment accounting and Russian legal requirements. The service records accepted document code, version, language, content hash, accepted_at, source and hashed IP/user-agent where available.

5. Storage and transfers

Primary storage and processing are planned on servers located in the Russian Federation. Cross-border transfer is not the default model and is allowed only where required by Russian law, chosen integration, payment scenario or separately reviewed legal basis.

6. Retention

Data is retained only as long as necessary for processing purposes, security, support, payment accounting, legal compliance and dispute resolution. Production retention should be implemented by configured retention jobs.

7. User rights

The user may request information, correction, blocking, deletion, withdrawal of consent or termination of processing where permitted by law. Requests are sent to ft.futuretechcorp@gmail.com, fta4dmin2@yandex.ru. The operator may request evidence that the request belongs to the account.

8. Security

The service should use TLS, password and token hashing, admin MFA, RBAC, per-resource authorization, audit logs, rate limiting, secret control, backups, artifact scanning and restricted production access.