Privacy Policy
Version v2026-09 · Effective 2026-11-11
This Privacy Policy explains what personal data avidol collects, why, for how long and who processes it. The controller is Avidol.ai.
1. What we collect
Account: the email address you sign in with; if you sign in with Google, also the name Google provides. Your display name (taken from the part of your email before the @ if you do not provide one), language, the region you declare yourself, the version of the Terms you accepted, and the time of any age declaration.
Telegram: if you link the partner bot, also your Telegram user ID and chat ID.
API keys: only a hash and a few leading and trailing characters, never the key itself.
Content: the files you upload (video, photos), your prompts, generation parameters and deliverables; your private characters' settings; the shot sketches, scenes, and series and episode drafts you choose to save to your account; the callback URL you set for a multi-segment job; and, in source-review requests, the production source, source record URL and rights basis you enter.
Transactions: top-up orders (amount, payment method, payment currency and amount, exchange-rate snapshot, the provider's order reference), records of credit holds, charges, refunds and grants, and receipts. We do not receive card numbers or other payment details.
Support: the cases and messages you open on the Workspace support page.
Location and network: the country/region code Cloudflare attaches to your connection. When you accept the Terms or complete the 18+ declaration, we keep the code at that moment with that record for reference; we currently do not use it to decide or restrict whether you can use the Service. Where applicable law requires it, it may in future be used for regional age or compliance checks. The IP address of signed-out requests is used for rate limiting and the counter is removed after about 2 minutes; server logs (Cloudflare Workers Logs) are kept for about 3 days.
Viewer accounts: if you sign in on the viewer site, also your email address, language, last sign-in time, the method and time of your age declaration, the series, characters or creators you follow, and your notification preferences; when you use viewing, unlock, subscription or tip features, also your valid-view records and those transaction records.
Terms acceptance and activity time: when you accept the Terms or update your region, we record the version accepted, the region declared, the time, and the country or region code of your connection at that moment (we do not store the IP address itself for this), to evidence the contract, prevent fraud and handle disputes; we also record the time of your account's most recent activity (updated at most once an hour) to decide how long your asset library is kept.
2. Why we use it
To provide generation, charge and refund credits, prevent abuse, meet legal duties on age and content, and send sign-in links and service notices (by email, or through Telegram if you linked it). We do not run advertising and have no advertising trackers; the website and the Workspace use Cloudflare Web Analytics, which sets no cookies, and we use it only to understand overall page views and loading speed.
Required data: an email address (or Google account) for sign-in is required to use the Service, and without it no account can be created; payment details for top-ups are entered on the payment provider's page, and without a top-up paid features cannot be used; acceptance of the Terms is required to create an account, and a region declaration is optional. Telegram linking, callback URLs, private characters and source-review requests are optional features; not providing them only means you cannot use that feature.
3. How long we keep it
Uploads: 30 days (your library: kept while the account is active and used within the last 360 days). Regular deliverables: until the later of 30 days after the job's creation and 90 days after your most recent credited top-up (the extension counts toward your storage quota). Intermediate generation candidates: 7 days. Text-model call outputs: 30 days. Sign-in sessions: 30 days. Sign-in links: valid for 15 minutes; after a link expires, its sending record (email address, link hash and time of use) remains in the sign-in records and currently has no automatic deletion period. Rate-limit counters: about 2 minutes. Server logs: about 3 days.
Transaction, terms-acceptance and audit records are kept long-term for accurate accounting, evidence of the contract and dispute handling, and the database blocks changing or deleting them; job prompts and quote details also cannot currently be deleted or changed individually, because they lock the quote and support reconciliation. These records currently have no automatic deletion period; if you ask us to delete data, we will delete what can be deleted and tell you what cannot be deleted and why. Account data currently has no automatic deletion period and is kept until you ask us to delete it.
4. Who processes it
Cloudflare — hosting for the website, API, database, file storage and server logs.
Resend — sign-in and notification emails.
Google — to verify your Google account when you choose to sign in with Google.
Telegram — if you link the partner bot.
sidediff — checkout and collection for top-ups. We send the top-up amount and currency, the top-up order number, the payment product code, the address to return to after payment and (for card payments) a product name; you enter payment details directly on sidediff's page.
ReachAPI and BytePlus ModelArk — when you choose "Standard Cloud", your prompt and the reference images of the chosen character look are sent to these upstream providers; when you use the approved text-model call interface, the input you send is sent to ReachAPI for processing. Once sent, upstream providers keep and use the data under their own privacy policies (for example, ReachAPI's public privacy policy says it keeps API request logs and uses them for operations, troubleshooting, security monitoring and product improvement); the expiry of a signed link only stops later downloads and does not mean the provider has deleted what it already obtained, and we cannot delete data held by upstream providers on your behalf; if you ask for deletion, we will pass the request on to the relevant upstream providers and tell you the result and any limits. Once the content licence ends, we stop any new processing and transfer.
Vast.ai — the Director Engine runs on GPU machines rented here; your prompt and reference files are processed on those machines during generation.
Sentry — server error reports. Error reports follow data minimisation: designated sensitive fields (for example prompts, cookies and API keys) are masked and query strings are removed from URLs; we cannot guarantee that sensitive data in arbitrary text will always be detected automatically.
We may disclose data to the extent necessary when the law, a court or an authority lawfully requires it. If the Service is transferred through a merger, acquisition or asset transfer, your data moves with it and remains subject to this Policy.
We do not sell your personal data.
5. Cookies and browser storage
We use only cookies the Service needs to work, and your browser remembers your language and temporarily keeps drafts you have not submitted. See the Cookie Policy.
6. Your rights
You may ask to access, correct or delete your personal data, or ask us to stop processing it. There is currently no self-service account deletion or data export; please write to support@avidol.ai. We will handle your request without undue delay; where the GDPR applies, we will in principle tell you the outcome within one month of receiving it, and if the law requires an extension we will explain why within that period; where the law sets a shorter deadline, that deadline applies. Records that cannot be deleted are described in section 3, and we will explain why. You may also withdraw a consent you gave (without affecting processing before the withdrawal), object to particular processing, or, where applicable law gives you the right, ask for the data you provided in a portable format; you also have the right to complain to the data protection authority where you are. To confirm a request comes from you, we may ask you to reply from the email address registered to the account; a request made by an agent must include proof of authority. We do not charge for handling these requests.
You can delete uploads that no job is using, and revoke API keys, yourself in the Workspace at any time.
7. Minors
The Service is for adults only. We do not knowingly collect data from minors; when we find it, we stop any non-essential processing, restrict access, and delete or de-identify it as far as feasible (job prompts cannot currently be deleted individually; see section 3). Suspected child sexual exploitation content is first restricted, and necessary evidence is preserved and reported as applicable law requires; preservation is limited to what is necessary in scope and time.
8. International transfers
The providers above may process data outside your country, so your data may be processed abroad. This section only informs you that your data may be processed abroad; it does not replace any consent or other lawful transfer basis that the law separately requires.
9. Security
Data is encrypted in transit over HTTPS. API keys are stored only as a hash plus their first and last few characters. The operations back office requires authentication and access control (including Cloudflare Access and an allowlist of back-office accounts), and only authorised operators can enter it. Error reports follow data minimisation and mask designated sensitive fields (for example prompts, cookies and API keys); we cannot guarantee that sensitive data in arbitrary text will always be detected automatically.
No system can guarantee absolute security. If a security incident affects your personal data, we will notify you as required by applicable law.
10. Changes and contact
Updates are published on this page with a new version and effective date; this version takes effect on 11 November 2026. Questions: support@avidol.ai.
Changelog
- v2026-09 · 2026-11-11 · initial