a6a1. Scope and contact
This policy covers a6a create. The name a6a identifies the service; privacy requests go to tom@a6a.app. Ordinary registration does not require an identity document. The service is intended for people aged 18 and over.
2. Information we process
Account data includes your email, account identifier and registration date. Authentication data includes a one-time-code hash, attempts, expiry, session hashes and security records. The code is sent by email; its plain text is not stored in our database and we do not ask for an account password.
Creation data includes your description, settings, reference images, task identifier and status, completed images or videos and collection records. Purchase data includes the order, amount, currency, credits, status and provider identifiers. Support purchases may include the details you choose for the card and advertising arrangements. We keep the messages you send us to handle your request.
3. Why we use it
We use this information to verify access, fulfil and deliver your creation request, manage credits and purchases, answer questions and prevent fraud or abuse. Security verification may process your IP address; local rate-limit counters use identifiers derived through hashing.
Service and purchase processing require data needed to perform your request; security and legal obligations may require other permitted processing. Publishing your materials as advertising requires separate permission. We do not sell your personal information or publish your uploads, results or supporter name without that permission.
4. Providers and transfers
AutoDL receives the prompt, settings and, when supplied for video, necessary reference images. The image channel 可乐 AI (Kele AI) receives the image prompt and settings. They generate the results; we do not send them an account password or payment-card data.
Cloudflare Turnstile processes browser and network signals for access verification. The SMTP service receives your email address and verification message. Waffo receives necessary purchase data and what you enter directly in its checkout; we receive payment results and identifiers. The hosting service runs the application, database and files.
Files currently use private storage on the a6a server. The server and providers may be outside your country. Each provider’s processing and retention also depend on its own terms. We do not represent that every upstream provider excludes training use. Avoid submitting sensitive information or third-party data you are not entitled to provide.
6. Retention and deletion
Completed creation files are normally cleaned after 30 days. Unused temporary reference uploads are cleaned after one day; they may remain while a task is active or under review. Cleanup is periodic, rather than immediate. Removing a creation from your collection hides it and does not guarantee immediate deletion of all related records.
Codes expire after 10 minutes and sessions after 30 days. Expired authentication and security records are cleaned periodically. Account details, prompts, task records and orders may remain while needed for the service, support or legal obligations. Accounting records may be retained after closure where required by law. Account deletion is handled on email request, rather than automatically.
7. Your requests
Write to tom@a6a.app to request access, correction, a copy or deletion of your information, account closure or withdrawal of publicity permission. We check account ownership and explain information we need to retain. Applicable legal rights and response deadlines apply, including the right to contact a competent authority. Withdrawing permission does not invalidate earlier authorized processing.
8. Security and changes
We limit file access using expiring signed links, protect sessions, verify operations on the server and keep provider credentials out of the browser. No system removes every risk. Do not put passwords, card data or sensitive documents in a prompt. Report concerns to tom@a6a.app. Policy revisions will show their version and date; we will request additional consent when required.