Privacy Policy

The personal-data operator is Individual Entrepreneur Anatoly Georgievich Zaydelov, OGRNIP 323784700118697, Tax ID 781129420099, registered at 17/1-225 Podvoyskogo St., Saint Petersburg, 192168, Russia.

GorgeousGPT acts as operator for account, payment, and service data used for registration, authentication, accounting, support, and security. Formal data-subject requests must be sent in writing to the registered address.

Account and service data may include:

• Sign-in email, OTP records, session information, CSRF tokens, and essential cookies.
• API-token records, model selection, token and pricing data, charges, and aggregate API usage.
• Metering-only tool records, such as tool category, call identifier, quantity, and token counters. Queries, URLs, tool arguments, and generated text are excluded.
• IP address, user agent, request date and time, and security or error metadata.
• A voluntary B2B enquiry: Telegram username, page URL, referrer, UTM parameters, IP address, and user agent.
• The consent record: date, time, IP address, user agent, source, and document version.

The initial rollout does not use Telegram authentication, a customer-facing Telegram bot, checkout, or a payment provider. Telegram is used only as the Operator's internal delivery channel for B2B enquiries that a visitor chooses to submit.

Prompts, messages, attached text, tool inputs, model parameters, and model responses are user content. GorgeousGPT processes that content in transit to route the request, obtain the response, calculate usage, prevent abuse, and return errors.

For the eight GPT routes advertised on the GorgeousGPT landing page, application request logs exclude request and response bodies, including prompts and messages. Retained technical and billing metadata can include request and account identifiers, IP address, model, token counts, timestamp, status, error code, and charge. Metering records exclude search queries, URLs, tool arguments, and generated text. GorgeousGPT does not offer conversation history.

The initial rollout does not expose compatibility routes that write job input or session transcripts to persistent account workspaces. Terminal diagnostics retain event types and counters, not raw model events or free-form upstream error text.

Do not include personal, biometric, payment, minor-related, special-category, trade-secret, or unauthorised third-party data in an AI request. You are responsible for having a lawful basis for content you submit.

• Registering, authenticating, and maintaining an account session.
• Issuing an API token and calculating usage and charges.
• Providing support, preventing abuse, and protecting the service.
• Sending essential account and security notices.
• Executing AI requests, adapting compatible request formats, and calculating provider-side token usage.

• No payment provider is active during the initial rollout. If checkout is enabled later, the selected provider will receive only the payment data required for that transaction.
• An SMTP provider receives the email address and message required to deliver OTP and service notices.
• A submitted B2B enquiry and its submission metadata are delivered through a dedicated Telegram bot to the Operator's private chat. Telegram processes that delivery under its own terms.
• Hosting, monitoring, and infrastructure providers process technical and diagnostic data required to run the service.
• AI-model and metering providers receive user content, technical context, tools, and model parameters required to generate and meter a response.

B2B enquiry fields are separate from API request bodies. Prompt or response content is not sent to Telegram or a payment provider. AI and infrastructure recipients operate under their own privacy and retention terms.

The application databases for this deployment are hosted on Hostinger infrastructure in the European Union. AI execution, email delivery, monitoring, support, and any future payment processing can involve providers in other countries as described in this policy and their own terms.

GorgeousGPT may use third-party AI-model and token-counting providers to execute and meter requests. Upstream payloads can contain user content, technical context, tools, selected model parameters, and compatibility instructions.

The service is designed not to place a GorgeousGPT sign-in email, Telegram ID, internal user ID, end-user IP address, billing ID, or payment details into that payload. Gateways can add synthetic request, job, session, or thread identifiers for compatibility and correlation. These technical identifiers must not be treated as proof that an upstream request is anonymous.

Processing is performed to enter into and perform the service contract, comply with law, secure the service, process payments, and—where required—on the basis of consent.

Account, consent, metering, and service records are kept while the account is active and afterwards for periods required to perform the contract, comply with law, resolve disputes, and protect the service.

Operational logs are configured for a seven-day retention window, followed by a deletion delay. Aggregate monitoring series are configured for ninety days. Billing and metering rows do not currently have an automatic time-to-live, but contain technical usage facts rather than request or response bodies.

The B2B form backend does not write enquiry fields to its application logs or database; it validates and delivers them directly to the private operator chat. Telegram retention is governed by the Operator's chat controls and Telegram's terms. If delivery is not configured, the backend rejects the request before reading its body.

The advertised GPT routes do not retain prompt bodies, response bodies, search queries, URLs, tool arguments, generated text, raw model events, job inputs, or session transcripts in application logs or billing rows.

GorgeousGPT does not offer conversation history and does not use these records as a dataset for training models or marketing profiles.

You may request information about processing, correction, restriction, or deletion of data; withdraw consent; and stop marketing communications where they have been enabled. A request may require an email, Telegram ID, or another identifier sufficient to locate the relevant records.

This policy may be updated when the service, data categories, infrastructure, or legal requirements change. A new edition applies from the publication date unless it states otherwise.