POLICY STRUCTURE · NOT FINAL TERMS
Privacy Policy
How account, creative and connection information will be handled.
2 min read
This is a proposed structure, not final terms. It has not been through legal review and is not yet enforceable. Nothing here creates an agreement.
1. Who we are and what this policy covers
This working draft covers the proposed Adogenic website, shared studio, creative workflows and assistant connections. It is not a statement that those services are live.
Before publication, identify the operating legal entity, address, privacy contact and relevant controller/processor roles. Effective date: to be finalized.
2. Information categories
| Category | Proposed purpose |
|---|---|
| Account and studio membership | Sign-in, account administration and project permissions. |
| Briefs, scripts, assets and outputs | The creative tasks the user chooses to perform. |
| Billing references and entitlement records | Subscriptions, invoices and credit accounting; actual payment handling must be documented. |
| Connection grants and activity | Scoped assistant access, authorized actions and revocation. |
| Technical/support records | Reliability, security and support; actual collection must be inventoried. |
3. Purposes and applicable processing grounds
The final notice must connect each actual data category to its purpose and applicable processing ground. Optional analytics or marketing use must be distinguished from providing the service.
Do not publish blanket claims that all processing relies on consent, or that no data is collected, without checking the implemented service and applicable requirements.
4. AI providers and other recipients
Creative work may require sending selected inputs to an external provider. The finalized notice must identify actual recipients or recipient categories, their purpose and applicable processing terms.
Model-training use, provider retention, payment processing and support tooling remain unconfirmed. This draft does not promise that providers never retain data or use it for training.
5. Assistant and business connections
A connection should use the user-authorized scope and relevant project context. Authorization, tool discovery and a readiness read do not authorize a paid generation job.
The notice must explain actual connection data, token handling, revocation and any operation that may already be in progress. No business or ads-library integration is represented as live here.
6. Retention and deletion
Define separate retention rules for accounts, drafts/media, audit logs, billing records and backups. Actual periods and exceptions must be approved before launch.
Account deletion, subscription cancellation and connector revocation are different actions. The final notice must explain what is deleted, retained or de-identified and when.
7. Security and international processing
Document the actual hosting and provider locations, safeguards and applicable transfer arrangements. Do not claim a certification, encryption guarantee or data-residency option that has not been verified.
No system can be described as risk-free. Security language must accurately reflect the implemented controls.
8. Your choices and requests
The finalized policy must explain applicable access, correction, deletion and other rights, identity verification and the actual request channel. Jurisdiction-specific rights and response periods require confirmation.
9. Policy updates and contact
Publish the effective/revised date and explain how material changes are communicated. Verified business/privacy contact details remain to be supplied before launch.