1. What Zdravo stores
Zdravo stores information needed to provide the service, including account information, saved memories and other content you choose to submit, organization and agent configuration, API credentials in their protected form, and service activity needed for security, billing, and operation.
2. How we use it
We use this information to authenticate users, store and retrieve context, enforce organization and agent policies, operate the API and integrations, maintain security and audit records, provide support, and process subscriptions where applicable.
3. AI processing
Some Zdravo features require content to be processed to provide retrieval, summarization, embedding, or other requested functionality. Zdravo does not represent customer memory as training data for its own models. Customers should review the configuration and applicable terms of any external model provider they choose to connect.
4. Service providers
Zdravo uses infrastructure providers including Vercel and Supabase and may use other providers for payments, email, monitoring, or AI functionality depending on the feature and configuration. We do not publish an outdated fixed provider list here because the active service architecture can change.
5. Security
Production controls include authentication, row-level security, organization-scoped authorization, governed agent identity, policy enforcement, and audit/provenance records. Hosted Zdravo is not presented as end-to-end or zero-knowledge encryption.
6. Your choices
Depending on the feature and account configuration, you can export, update, or delete information stored in Zdravo. For a privacy request or data-processing discussion, contact shqiprim@zdravo.ai.
7. Changes
We may update this policy as the service changes. The date at the top of this page identifies the current version.