This Privacy Policy explains how Zropi collects, uses, shares, and protects information when you use our web app and our mobile app.
1) Who we are / contact
If you have questions or requests about privacy, contact: [email protected].
2) What Zropi is (high-level)
Zropi is an AI companion application. Your companion uses your messages, context, and optional uploads to respond, remember details you choose to share, and (if enabled) send notifications.
3) Data we collect
We collect data you provide, data generated by the app, and limited technical data needed to operate the service.
- Chat content: the messages you send and the AI responses, timestamps, and message metadata.
- Uploads you choose to send: images and documents (for example PDFs, text files, and docs). We store file URLs and file metadata (name/type/size) and may store additional processing metadata.
- Persona / transcript uploads (optional): if you upload a chat transcript to build a persona, we store the uploaded file reference and may store a short text preview and validation status.
- Companion and customization data: selected companion traits, tone, and related configuration you create.
- Memory and personalization data (optional): if you use memory features, we may store items derived from your chats such as interests, routines, goals, life events, relationship context, and summaries to improve continuity.
- Notification data (optional): if you enable notifications, we store push notification tokens/subscriptions and notification scheduling context (for example the reminder time and a short description of what the reminder is for).
- Email / task features (optional): if you use features that send deliverables via email, we may store the recipient email address you provide and task artifacts you choose to generate or upload.
- Technical and security data: IP address may be recorded in connection with certain uploads/requests; server logs may include timestamps and error details.
- Local device storage: the app may cache chat data and session information locally on your device (web: localStorage/sessionStorage; mobile: Capacitor Preferences) to speed up loading.
4) How we use data
- Provide core functionality: chat, companion responses, and conversation continuity.
- Process uploads you submit so the AI can respond to them.
- Generate and maintain memory summaries and personalization (if enabled/used).
- Send notifications you request or enable (for example reminders and proactive messages).
- Maintain service reliability, prevent abuse, debug issues, and improve performance.
5) Sharing and third parties
We do not sell personal or sensitive user data. We may share data with service providers strictly to operate Zropi, such as:
- AI processing: Our model APIs (text, image generation, and text-to-speech where enabled) to generate responses and media.
- Push notifications: Firebase Cloud Messaging (FCM) for mobile notifications and Web Push infrastructure for web notifications.
- Infrastructure providers: hosting, database, storage, and CDN providers used to run the service and serve uploaded files.
We may also disclose information if required by law, to enforce our terms, or to protect the rights and safety of users and our service.
6) OAuth connections (optional)
If you connect third-party apps (for example email, calendar, tasks, storage, or social platforms), we use OAuth to get permission to access those accounts on your behalf. The goal is to let you ask Zropi to read or write data in those apps only when you request it (for example, “summarize my inbox,” “create a calendar event,” or “save a file”).
- What we receive: access tokens and refresh tokens, along with the app’s authorized scopes.
- How we store it: tokens are stored encrypted and are used only to perform the actions you request.
- How to revoke: you can disconnect an integration in the app (where available) or revoke access from the third-party provider’s security settings.
- Scope minimization: we request only the scopes needed for the feature you enable.
7) Data retention
- Chats and memory: retained until you delete them or request deletion (see below), unless we must retain limited data for security, fraud prevention, or legal compliance.
- Task secrets: sensitive task inputs are stored encrypted and are configured to expire automatically after a limited time.
- Push tokens/subscriptions: retained while active so notifications work; removed/disabled when you unsubscribe or stop using the device.
- Persona uploads: retained to support the companion/persona you created and for debugging validation issues; you can request deletion.
- OAuth tokens: retained while the integration is connected; removed when you disconnect or revoke access.
8) Deletion and your choices
- Local app data: you can clear local cached data by clearing the app’s storage (or uninstalling on mobile / clearing site data on web).
- Server-side deletion: you can request deletion of chat history and associated memory by emailing [email protected]. For us to locate your data in a no-login system, we may ask for your companion access code.
- Notifications: you can disable notifications in your device settings and/or inside the app where available.
9) Security
- We transmit data using modern cryptography in transit (for example HTTPS/TLS).
- Certain secrets (such as task secrets and mailbox credentials) are stored encrypted.
- No system is 100% secure; you should avoid sharing highly sensitive information in chat.
10) International data transfers
Depending on where you live and where our providers operate, your information may be processed in countries other than your own. We take reasonable steps to protect data during such transfers.
11) Children
Zropi is not intended for children under 13. If you believe a child has provided personal information, contact us and we will take reasonable steps to delete it.
12) Changes
We may update this Privacy Policy from time to time. We will update the “Last updated” date above when changes are made.
13) Data Safety (Google Play)
Google Play requires a Data Safety form in addition to a Privacy Policy. The Data Safety disclosure in Play Console should match this policy.