Privacy
DRAFT — REQUIRES LEGAL APPROVAL
Data used
Accounts store a display name, an email when supplied, a password verification hash, language and a verified Telegram connection. Security uses session records, a short browser description, activity timestamps and a protected network-address fingerprint. Devices have a server-issued identifier and name, without a hardware fingerprint.
Purchases, support and reviews
Records include orders, amount and currency, verified payment events, issued licenses and action history. Ticket text is available to the user and authorized support staff. Reviews require separate publication consent and moderation; consent can be withdrawn in the account, removing the text from public display.
Cloud AI and recipients
When cloud AI is enabled, messages are sent to the selected provider for a response. The platform records token usage and cost without storing prompt text in AI usage logs. Before enabling it, disclose the provider, purpose, legal basis, processing region, transfer and retention rules, commercial terms and opt-out options. The operator must also list email, hosting and payment providers.
Retention and rights
Users can change their name and language, end sessions, unlink devices, withdraw review publication and request deletion. Requests are recorded for the operator; they do not promise immediate destruction of legally required financial and audit records. Specific retention periods, exception grounds, response procedures, privacy contact and supervisory authority rights must be completed for the chosen jurisdiction.
Cookies and protection
The website uses an essential sign-in cookie, a short-lived Telegram verification cookie and a language preference. Advertising analytics is not connected. Production requires HTTPS. The final policy must define operator responsibilities, incident notification and applicable consent requirements.