Symbiose
What we process
Symbiose processes account and authentication details, language preferences, invitations, conversation messages, delivery information, subscription entitlements, and limited operational telemetry needed to keep the service reliable.
We do not upload or retain your full address book. Contact discovery is a separate opt-in: an account appears in matches only after its owner enables discoverability, and a lookup runs only after you request it and grant contact permission. Your device normalizes phone and email identifiers and sends only a limited set of hashed identifiers; contact names and raw values stay on the device. A matched account must also have opted in. When you send an invitation, the selected contact detail is handled by your device's sharing or messaging tools.
Hashed contact identifiers reduce exposure in transit and at rest, but they are not the same as irreversible anonymization: someone with database access could enumerate a small phone-number or email address space.
Learning help and Pawly
Sentence and word translation for the eight supported languages runs on the device in native iOS and Android builds after the required ML Kit models are downloaded. The source and result for that feature stay on the device; the browser has no production translator. When you request remote help, or enable automatic post-send correction and analysis, only the content needed for that request is processed by Symbiose and its configured language- processing provider.
Pawly is a separate, explicitly labeled AI conversation. Its conversation sends your Pawly turn and a short window of Pawly context to the configured provider; your human chat is not included unless you put it into Pawly yourself. Learning requests are not used to train Symbiose models. Provider retention and security controls apply to remote processing.
To recover a remote learning answer if its connection drops, Symbiose temporarily stores that answer encrypted on the server. Only the same account and request can recover it, for up to 15 minutes. Clearing that conversation or deleting the account removes access immediately. Expired encrypted answers are removed during subsequent request processing or maintenance.
You can keep using human messaging when learning assistance is unavailable or when you choose not to request it.
Security and encryption
Connections use TLS. Access to application data is protected by authentication, row-level access controls, and server-side authorization checks. Local message storage on supported native builds uses SQLCipher.
Symbiose is not currently end-to-end encrypted. Authorized Symbiose services can read message content when they need to deliver messages or provide a learning feature you ask for.
Retention and requests
The server message store is a short-retention delivery buffer, designed to expire within 30 days; it is not a cloud backup or a complete history restore. Your local history and saved learning data remain on the device under the app's local-data policy. Messages older than 365 days may be removed when there are at least 500 newer messages in that conversation. Pending sends are preserved. Reinstalling, clearing app data, signing out under the current policy, or replacing a device can remove local history. Analytics and crash reporting are designed to exclude message, draft, translation, contact, and provider-response content.
For privacy questions or an account access or deletion request, email contact@symbiose.chat from the address associated with your account.
Changes
We may update this notice as Symbiose changes. The date above identifies the current version.