Published information
Use the smallest safe channel.
This English page is operational information, not legal advice. Do not send secrets or unnecessary personal data by email. We will ask for proportionate verification when a request could expose account or payment information.
1. Contact routes
| Need | Contact | Include |
|---|---|---|
| Account, API, security, or service support | [email protected] | Account email, request identifier, date, and a short description |
| Payment, refund, or chargeback | [email protected] | Account email, order identifier, amount, and requested outcome |
| Privacy rights, deletion, or data concern | [email protected] | Request type, account email, and the data scope you are asking about |
2. Service support
Support can help with account verification, API-key revocation or replacement, model availability, request failures, usage records, policy versions, and access restrictions. Support cannot reveal an API key after it is shown once, bypass a security control, or open a closed launch gate.
For an account closure request, use DELETE /v1/account when authenticated or contact [email protected] if you cannot authenticate. See Account Closure and Data Deletion.
3. Billing, refunds, and disputes
Billing can investigate an exact server quote, a duplicate or failed payment, a refund request, chargeback freeze, or uncertain provider outcome. Never send full payment-card data. The Checkout information, Payment confirmation information, and Refund and Cancellation Policy explain the EUR total, 6% fee, tax, all-in charge, withdrawal, immediate performance, and refund states.
4. Privacy requests
You may request access, correction, erasure, restriction, portability, or objection where applicable. Tell us which right you are exercising, the account or data involved, and any relevant date or order identifier. A privacy request does not require account closure.
See the Privacy Notice for the processing map, recipients, transfers, retention, and complaint route.
5. Identity verification
We use proportionate verification before disclosing account data, changing access, or completing a deletion request. Verification may use the verified account email, authenticated account action, or another reasonable signal. We do not ask you to send a password, API key, private key, payment-card number, or provider credential.
6. Response timing and case evidence
We acknowledge and track requests with a case identifier. Privacy-rights requests are normally answered within one month; where law permits an extension for a complex request, we explain the reason and revised timing. Support and billing timing depends on severity, payment reconciliation, and information needed to verify the case.
Case records contain only the information needed to investigate, respond, meet legal duties, and establish or defend claims. They are deleted or anonymised when no longer needed unless a lawful retention exception applies.
7. Safe messages
- Use a subject such as “Account support”, “Refund request”, or “Privacy request”.
- Include identifiers, not secrets. A request ID or order ID is safer than prompt content.
- Do not attach prompt or output content unless support asks for the minimum necessary excerpt.
- If you suspect key compromise, revoke the key first when possible and describe the incident without sending the key.
8. Complaints and supervisory contact
If you have a privacy complaint, you may contact the Commission for Personal Data Protection. Consumer rights and any mandatory dispute route remain available.