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. When you send an invitation, the selected contact detail is handled by your device's sharing or messaging tools.
Learning help and Pawly
When you request translation, writing help, an explanation, or a conversation with Pawly, the content needed for that request is processed by Symbiose and its configured language-processing provider. Learning requests are not used to train Symbiose models. Provider retention and security controls apply to that remote processing.
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
Delivery buffers and operational records are retained only for the period needed to deliver messages, prevent abuse, support accounts, and operate the service. 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.