Privacy Policy
Last updated: September 20, 2026
Qiz Origin is operated by Xianming Dou, an individual merchant. This notice covers our website, accounts, AI Agent services, LLM API, Seat services and support. Privacy contact: [email protected].
1. Information we collect
Do not submit identity documents, payment credentials or other sensitive information unnecessary for the task. Make sure you are authorized before submitting another person’s information.
- Accounts: email, profile, preferences, password hashes where applicable, authentication and session records. Optional Google or GitHub sign-in supplies the authorized account identifier, email and basic profile, not your provider password.
- Content: prompts, responses, conversations, Agent configuration and memory, files, tool inputs/results and workspace data. Agent conversations and memory are stored for continued use. Seat execution can automatically save workspace snapshots, final responses and provider-context events for continuity and recovery, without a separate save action.
- Connected credentials: when you configure your own model key (BYOK), we receive and store that credential to run the selected service. In direct BYOK execution through E2B, the supplied key is passed into the sandbox so it can authenticate requests to the configured model endpoint.
- Usage and technical records: timestamps, model/route, token and runtime usage, status, request identifiers, IP, browser/client information, access and security logs, billing and entitlements.
- Payment and support: order/customer identifiers, product, amount, currency, payment/refund/dispute status, emails and attachments. Hosted checkout providers collect payment credentials directly; Qiz Origin does not receive or store full card numbers or card security codes.
2. Purposes and legal grounds
- Contract: information necessary to create and authenticate accounts, perform tasks, deliver purchased access, meter usage and provide support.
- Legal obligations: applicable accounting, tax and consumer-protection requirements. We also process information where necessary and lawful to handle disputes and establish or defend legal claims.
- Security, abuse prevention, fault diagnosis and improvement rely on a ground permitted by the law applying to the activity. Where legitimate interests are permitted, we assess necessity and the impact on your rights before relying on that ground.
- Consent or separate consent is obtained before processing where legally required. You may withdraw consent without affecting earlier lawful processing. De-identified data is still personal data if it can be linked to you.
3. Providers and other recipients
We do not sell or rent personal information. Information is shared as needed for the function used, not with every recipient below. Recipients may be our processors or independent controllers for activities they determine themselves. Their policies do not remove our responsibility for our own disclosures, instructions to processors or assistance with your rights.
We may provide the minimum necessary information to advisers or competent authorities when legally required or necessary for legal claims. A change of operator is subject to the notices and safeguards required by law.
| Recipient / service | Purpose and information | Location / scope |
|---|---|---|
| Creem (Armitage Labs OÜ) | Current hosted checkout / Merchant of Record: purchases, customer/payment details, tax, invoices, refunds, disputes and fraud prevention. We receive fulfillment records. | Estonia-based provider; international processing is described in its privacy notice, not restricted to Estonia. |
| Alibaba Cloud | Production hosting, databases, object storage and backups: account, content, usage and technical records. | Main production infrastructure: Jakarta, Indonesia; other recipients are not necessarily in Jakarta. |
| Cloudflare | Domain, network security and delivery services, and support-email routing: network/request metadata and routed messages. | Global network; location depends on service and traffic path. |
| Google (Gmail; optional Google sign-in) | Support emails and attachments; optional authentication and authorized profile information. | International processing under Google’s policy. |
| GitHub (optional sign-in) | Optional authentication and authorized profile/email information. | International processing under GitHub’s policy. |
| Resend | Service notifications where enabled: recipient and message content. Account authentication email has a separately configured SMTP route; contact support for its recipient details. | Resend’s policy applies to its processing; SMTP location depends on its actual provider. |
| E2B (when used for Agent execution) | Isolated execution: task inputs, temporary files, tool results and runtime metadata. Direct BYOK execution also passes the supplied model key into the sandbox for requests to the configured model endpoint. | Default E2B execution configuration: United States. Other runtimes depend on the infrastructure used. |
| AI recipients for the configured route | Inference sends prompts, context, file excerpts and request metadata to the recipient serving that route. Depending on configuration this can involve OpenAI, Anthropic or another service, including an intermediary. A compatible protocol name alone does not identify the actual recipient. Ask support for route-specific recipients and retention before submitting sensitive data. | Depends on the route and intermediaries; no universal region or zero-retention guarantee. |
4. Storage, transfers and security
Main production hosting is in Jakarta, Indonesia. Processing by the recipients above can occur outside your country. Any legally required transfer mechanism, contractual protection, notice or consent must be in place before the relevant transfer. This notice does not certify that a specific standard contractual clause or certification has already been obtained.
Measures include HTTPS/TLS for public connections, password hashing, encrypted storage for supported secrets, service authentication and restricted administrative access. Runtime isolation, log filtering and encrypted backups are used where supported by the relevant component. Encryption is not deletion: backup ciphertext may remain recoverable while its decryption key exists.
No system is completely secure. We investigate incidents, take remedial action and make legally required notifications. Where GDPR applies, a notifiable breach is reported to the authority without undue delay and, where feasible, within 72 hours of awareness; high-risk affected individuals are notified without undue delay. Other laws may impose different conditions and deadlines.
5. Retention and deletion
Retention depends on the purpose of the record, account state, outstanding work, disputes and legal obligations. Different types of data have different deletion processes; closing an account does not erase every record or copy at the same time.
| Information | Retention and deletion |
|---|---|
| Account and Agent content | Kept while needed for the account and saved history. Closure revokes access and drains work before deletion. The ordinary content-deletion waiting period is 30 days after the closure retention period begins, not necessarily after the initial request. Unsettled usage, refunds, disputes or legal holds can delay this stage; only relevant necessary records should remain. |
| Account exit export | Downloadable for up to 30 days from creation. After expiry, download is refused and the cleanup process clears the content, retaining a non-content status record for deletion retries and accountability. Export expiry does not itself complete account closure. |
| Credentials and runtime files | Live BYOK secrets are removed during closing; cancelling closure does not restore old keys. Temporary runtimes are requested to terminate after work ends; failed cleanup is retried and escalated, not guaranteed to complete at every provider within a fixed number of minutes. |
| Seat workspace and execution artifacts | Automatically saved snapshots, responses and context can persist beyond a request or entitlement end for continuity and recovery. Entitlement expiry does not itself delete all saved content. Contact support to request deletion, subject to applicable dispute or legal holds. |
| Usage, security and support records | Retained for the service, reconciliation, support or investigation for which needed and any applicable legal preservation period. The retention period depends on the record and purpose; these records do not all expire automatically on a common schedule. You can request deletion or information about the criteria applying to your records. |
| Transaction, tax and dispute evidence | Records relating to products sold through Creem are retained for at least seven calendar years under its merchant terms, longer where law or an active legal hold requires. This does not justify keeping unrelated conversation content. The relevant record and legal obligation determine the start date. |
| Backups and third-party copies | Live deletion does not instantly remove every backup or independent recipient’s copy. Backup expiry depends on the storage system; an account or export deletion period does not automatically apply to every backup. Restored data must be checked against deletion requests before returning to service. Independent recipients retain records under their applicable obligations; we assist within our responsibility. |
6. Browser storage and communications
Browser storage holds authentication/session information and preferences such as language. Clearing it may sign you out or reset preferences. This version does not load third-party analytics scripts or Google-hosted fonts. Before introducing optional analytics or marketing, we will disclose the provider and implement choices or consent where required.
Necessary account, security, billing and service notices are separate from marketing. Contact support to stop optional marketing; any legally required consent must be obtained before sending it.
7. Your rights
Subject to applicable law, request access, correction, copies or portability, deletion, restriction, objection or consent withdrawal at [email protected]. Verification is proportionate to account ownership and does not require unnecessary identity documents.
Requests are normally free. We respond within the applicable deadline; where GDPR applies, ordinarily within one month of receipt. We explain any lawful extension or limitation. A manifestly unfounded or excessive request may be refused or charged a reasonable administrative fee only where legally permitted; repetition alone does not automatically justify refusal.
Deletion can be limited for legally required records or a specific legal claim. We explain the reason and do not extend the exception to unrelated content. You may complain to the competent data-protection authority, including in your place of residence where applicable.
8. Children
The service is not directed to children under 13. A higher local age or valid parental authorization applies where required. If a child supplied data without necessary authorization, contact us for investigation and appropriate deletion or other protective action.
9. Changes and contact
The date above changes with the policy. Material changes receive additional notice through the service, website or email before taking effect where required; urgent legal or security changes may require a different schedule. Fresh consent is obtained when legally necessary rather than inferred from continued use for every new purpose.
Operator: Xianming Dou · Privacy and support: [email protected]