Purpose limitation
One permission for one clear purpose.
Clarity does not bundle cloud AI, family, school, health, location and Support into one blanket consent.
Clarity and privacy
Your data is not a business model.
Clarity uses data to provide the features you request — not for advertising profiles or data trading. In the current iOS build, Ariadne automatically adds broad core Clarity context when a message is sent to the cloud chat. This page states that data route explicitly.
Privacy is architecture
Control begins before data moves.
Clarity controls permissions where data originates — for example in Health, Memory or a connection. That is not the same as choosing sources in chat: Ariadne currently rebuilds the available core context automatically for every message. An AI action shows its scope; a support case does not silently use earlier conversations.
Three product principles
Private, without small print in the interface.
Separate permissions
You open only what you need.
Family, school, health, location, Support and cloud AI are not bundled into one consent. Every permission remains tied to its purpose.
View account permissions
Current Ariadne data route
Core context is attached automatically.
When you send a message, the current iOS chat builds live context from the data available in Clarity. This can include planning, school, reminders, grade summaries, projects, lists, statistics, family and — according to their source permission — Health data. Chat focus ranks relevance; it does not limit this core context. Smart Notes are attached only after selection, and medical document content only after individual approval. A complete source list and per-message selection remain a product gap.
View AI transparencyTransparency in numbers and boundaries
What Clarity does not hide in the background.
These statements describe product boundaries, not invented reach or infrastructure metrics.
advertising profiles
Clarity does not build advertising audience profiles from your content.
separate permission areas
Family, school, health, location, Support and cloud AI are named individually.
clear action boundaries
Reading, suggesting, confirming, bounded execution and human-only decisions remain separate.
only after execution
A sent request is not a completed deletion. The website does not show an outcome the system has not confirmed.
Privacy in the product
Four routes you can verify for yourself.
01
Permissions
Every sensitive data route is assigned to a specific purpose. Available settings are shown in your Clarity Account; the website does not invent toggle states the server does not know.
02
Support
The current case remains the current case. Earlier support cases are not currently used automatically as AI context, and you can request Support without AI.
03
Export and correction
The account shows the documented request route. While new web support cases remain closed, it opens the published support email; the website does not claim a case status.
04
Deletion
A deletion request and its technical execution are two different states. Sending the email confirms only the request, not the deletion.
Legal detail, without hiding it in marketing.
The Legal Centre separates privacy, providers, AI, children, health, Support and Voice Notes into their own versioned documents.