For the Enterprise edition, your organization (the tenant) is the data controller; CuraIQ is the tool it runs. For the Families edition, the parent/guardian is in control of their household's setup.
Account and event metadata is stored on the CuraIQ server, isolated per tenant — one tenant can never read another's. Secrets (SSO client secrets, your bring-your-own vision key) are encrypted at rest (AES-256-GCM) and are never sent back to any device. Sessions are signed; the admin console is restricted to the administrator (password or your SSO).
CuraIQ for Families is designed for data minimization. The on-device review means a child's conversations are not uploaded. Parents receive a signal that something needs attention — not their child's transcripts. Where signs of self-harm appear, the app surfaces help resources locally.
If you're a parent enrolling a minor's device, you are providing consent for that household setup. We collect the minimum needed to run the controls and never sell or share children's data. (COPPA / GDPR-K: confirm your specific obligations — see "Legal review" below.)
You can request access to, correction of, or deletion of your account data. Because CuraIQ holds only redacted metadata, there is no conversation content to export or erase. Direct requests to the contact below; enterprise tenants should route requests through their administrator.
Event metadata is retained for operational reporting and removed when an account is closed. Installation tokens can be revoked at any time from the console.
Questions or requests: the administrator of your tenant, or the operator of this CuraIQ instance.
Legal review: this page describes CuraIQ's actual data handling in plain language and is a starting point — it is not legal advice. Have it reviewed by counsel for your jurisdiction before publishing, especially the children's-data section.