What we store, what apps can see, and how to change or delete any of it. For the formal notice, read our privacy policy.
The essentials
Onairos turns information from accounts you choose to connect into a personal profile that can help apps understand you. Connecting a source, sharing with an app, and publishing a public profile are different decisions.
Review the receiving app and the requested information before continuing. You can disconnect sources, withdraw consent, export your information, or request account deletion. Derived traits and summaries are still personal information, even when they do not contain your original conversations.
Your PIN (also called a secret code) protects access to your encrypted model. Where you keep it changes how recovery works. The choices available are shown during setup.
Save with Onairos: Onairos stores an encrypted, recoverable copy. This makes future authorized access more convenient, but it means trusting Onairos to hold recovery material. It is not the same as keeping the only copy yourself.
Remember it yourself: Onairos does not retain a recoverable copy. You supply the code when it is needed. If you forget it and have no other backup, Onairos cannot recover the encrypted model protected by that code. Resetting access does not decrypt the old model.
Keep it on your device: the code is kept locally where supported. Losing the device or clearing its storage can remove that copy. Keep your own secure backup if you need to recover access.
If you choose to remember your PIN yourself, losing the PIN can mean permanently losing access to the encrypted model.
Sharing & visibility
When you create a public Onairos profile, its public-facing identity includes your handle, display name, and profile photo when provided. These help people recognize you and find the right profile, much like the familiar name-and-photo identity used in sign-in products.
A public profile can also show your summary, connected-platform labels, interests, and follower counts. Profile readiness and viewer access determine whether people see a limited preview or fuller profile content. A limited preview is still public; it is not a private account.
Public profile responses are filtered before they are returned. Private account fields, source credentials, and your PIN are not part of the public profile. Creating a profile does not publish your original chat transcripts.
Treat your public name, handle, photo, and visible profile content as information that other people can view and share.
An authorized connection needs an account identifier so the receiving app can associate a response with the right person. The consent flow also records the receiving app and the information you approved. These are the foundations of an app connection.
The exact profile fields depend on the flow and approved scope. A public profile displays a name and photo when available, but these are not an always-shared bundle across every developer API. For example, the traits response uses a user identifier and omits username and email.
Personality, preferences, facts, and memories are separate kinds of information. Review the consent screen to see what the app is requesting. Basic identity does not by itself authorize access to all of your connected data.
Passwords, provider access tokens, private keys, and the stored PIN are not ordinary profile-sharing fields. They should never be something a receiving app asks you to copy out of Onairos.
In supported conversation imports, the smart filter groups conversation titles into topics so you can review what to include. Topics identified as sensitive start switched off in the consent interface. The import uses your approved selection.
Sensitive topics can include health and mental health, personal finances, relationships, sexual content, legal matters, religion, and politics. When the model-based classifier is unavailable, a simpler title-based filter is used; its coverage is narrower.
Separate content checks also remove flagged sensitive records from supported profile-processing and public-profile outputs. Import selection and public-profile filtering work at different stages.
Automatic filtering is not perfect. A harmless-looking title may contain private details, and a useful conversation may be flagged. Review the selected topics and exclude anything you do not want imported. Availability and controls vary by connector.
Sensitive topics start excluded where smart filtering is offered. Review your selection before approving an import.
Onairos binds authorized sharing to the receiving application and the information approved in the consent flow. Consent records and time-limited authorization help the backend check subsequent requests.
Sharing a derived profile is different from sharing raw memories. Raw-memory access has additional application eligibility and consent requirements; it is not included automatically with ordinary personality or preference sharing.
Before approving, check the app name and requested categories. If the request is broader than you want, do not continue with that connection.
Protection & ownership
Onairos uses encrypted model storage and encryption for supported stored credentials and conversation evidence. Access checks and scoped responses limit what connected apps receive.
Encryption at rest protects stored information. Authorized server-side processing can still need access to readable data or a decrypted model. Saving recovery material with Onairos changes who can recover it.
We do not describe every current flow as on-device, end-to-end encrypted, or inaccessible to operators. Confidential enclaves, verifiable private computation, and other planned protections should not be confused with guarantees of today’s service.
You choose which supported accounts to connect. The available information depends on the connector and the permissions you approve. A conversation import and a social-account connection can collect different kinds of information.
Hosted conversation imports use an isolated browser session for the import. Session cookies and passwords are not intended to be retained after that session ends. Approved imported content may be stored or processed according to the selected flow; ending a browser session does not itself delete imported content.
Disconnecting a source stops that connection. It is a separate action from withdrawing app consent or deleting information already imported.
Onairos supports authenticated export of account and personality-profile information. Exports exclude reusable secrets such as tokens, passwords, and encryption material.
Available export formats depend on the product and data type. An account export is not necessarily a downloadable model file. Keep any exported personal information somewhere you trust.
You can withdraw consent for future processing and sharing. The backend records a processing restriction until you explicitly consent again. Disconnect individual sources when you no longer want to use those connections.
Authenticated account deletion removes account-linked data through the deletion flow, including associated public profiles. Export what you need before requesting deletion.
Revoking access cannot pull back copies an app or another person has already received. Check the receiving app’s privacy policy for how it handles previously shared information and deletion requests.
This page covers how the product works. Retention periods, legal bases and your rights are set out in the privacy policy.