Privacy Policy
Version 0.1 (draft)
This policy explains how AI Optimization Platform (“we”) processes personal data (a) about visitors and customers of our website and dashboard, and (b) on behalf of our customers, about the end users of the apps and games they connect to the platform.
1. Roles
For website visitors and account holders we act as controller. For end-user data sent through our SDKs and APIs we act as processor on behalf of our customer, who is the controller and is responsible for providing notices and obtaining consent from their users.
2. Data we process
- Account data: name, work email, organization name, hashed password (Argon2id), role and audit logs of actions in the dashboard.
- Contact and demo requests: the details you submit in our forms.
- Free audit uploads: files you upload are parsed in memory; we store the resulting report and a summary of the input (row counts, detected format), plus any contact details you choose to provide. Raw uploaded files are not stored.
- End-user event data (processor): a pseudonymous user ID chosen by our customer, session IDs, event names, timestamps, platform, app version, consent flags and event properties.
3. Data minimization by design
- The SDKs are designed for pseudonymous identifiers only; the web SDK rejects identifiers that look like email addresses.
- Event property keys that resemble personal data (email, phone, card, address, names, date of birth, government identifiers) are stripped on ingest.
- We never accept or store payment card data.
- Events without analytics consent are discarded; personalization and marketing features only apply to users who granted those consents.
4. AI processing
Analytics, statistics and financial metrics are computed deterministically. Language models are used only to write explanations and generate template-bound content. By default we use locally hosted models. Cloud AI providers are disabled unless enabled by the platform operator and opted into by the customer organization; even then, prompts contain aggregated metrics, not raw events or user identifiers.
5. Purposes and legal bases
Providing the service (contract), securing it and preventing abuse (legitimate interests), responding to requests (legitimate interests / pre-contractual steps), and complying with law. For processor data, purposes are defined by our customer’s instructions.
6. Retention and deletion
Customers configure a retention period per project (default 395 days) and can purge expired events. Customers can erase all data for a specific end user. Account data is kept while the account is active and deleted or anonymized afterwards, except where law requires retention.
7. Security
Tenant isolation, role-based access control, hashed API keys, encrypted secrets, TLS in transit and audit logging. See our security overview.
8. International transfers and sub-processors
[To be completed: hosting region, sub-processor list and transfer mechanisms such as Standard Contractual Clauses.]
9. Your rights
Depending on your jurisdiction (including the GDPR), you may have rights to access, rectify, erase, restrict or object to processing and to data portability. End users of our customers’ products should contact that customer first; we will assist them. Contact us via the contact form or support@example.com.
10. Children
Our website is not directed to children. Customers whose products are directed to children must mark their projects accordingly, which disables personalized offers and enforces stricter content rules; customers remain responsible for complying with laws such as COPPA and GDPR-K.
11. Changes
We will post updates here and notify account holders of material changes.