SigApp — Privacy Policy
Effective date: May 27, 2026
SigApp ("we", "us", "the app") helps users understand their communication patterns through AI-powered conversation analysis and coaching with Dr. Sigi. Your privacy matters to us. This policy explains what data we collect, how we use it, and your rights.
1. What Data We Collect
- Conversation text: When you run an analysis, the conversation text you provide is sent to our servers for AI processing. On Android this can include SMS content you have selected. On iOS and the web, this is conversation text you have shared into the app — most commonly a WhatsApp chat exported via WhatsApp's "Export Chat" feature (see Section 2 for details). The conversation text is stored in your Firestore account so Dr. Sigi can reference past conversations during coaching. It is retained until you delete your account.
- Analysis results: The AI-generated analysis of each conversation is stored in Firestore tied to your account. This includes the structured analysis output, summaries, and insights Dr. Sigi uses for coaching.
- Coaching state: If you use Dr. Sigi, your coaching progress, goals, session notes, memory entries, and a synced summary of your communication themes are stored in Firestore so Sigi can remember context across sessions and devices.
- Chat messages: Messages exchanged with Dr. Sigi during coaching are stored in Firestore tied to your account.
- Firebase Authentication: We create a Firebase Auth account for you. If you sign in with Google, we receive your name, email, and profile photo from Google. If you use the app without signing in (Android and iOS), we assign an anonymous identifier that you can later upgrade by signing in.
- Subscription state: If you upgrade to a paid plan, your subscription record is stored in Firestore (no payment-card data is stored by us — payment is handled by the App Store, Google Play, or our web payment processor).
- Crash reports: We use Firebase Crashlytics (Android and iOS) to collect anonymous crash reports, including device model, OS version, and stack traces. Your Firebase user ID is attached to crash reports so we can investigate issues you report.
- Analytics events: We use Firebase Analytics to collect anonymous usage events (e.g., "analysis started", "chat message sent"). These help us understand which features are used and improve the app. No conversation content is included in analytics.
2. WhatsApp Conversation Imports
On iOS and Android, you can import a WhatsApp conversation for analysis by using WhatsApp's "Export Chat" feature and sharing the resulting file into SigApp via the operating system share sheet. The file is either a plain-text _chat.txt or a .zip archive containing a _chat.txt.
- When you share a chat to SigApp, the file is uploaded over HTTPS to our backend, which extracts the text content (and, for ZIPs, unpacks the
_chat.txt on the server).
- We do not download or process any media files included in the export. We recommend using WhatsApp's "Without Media" export option.
- The extracted conversation text is treated the same as any other conversation text described in Section 1: sent to an AI provider for analysis, and stored in your Firestore account until you delete it.
- If you choose not to import a conversation, no conversation data leaves your device.
3. How We Use Your Data
- To provide AI-powered conversation analysis and coaching.
- To maintain your coaching progress, memory, and personalized insights across sessions and devices.
- To diagnose and fix crashes and technical issues.
- To understand app usage patterns and improve features.
We do not use your data for advertising. We do not sell your data to third parties.
4. Third-Party Processors
- Firebase / Google Cloud: Authentication, cloud storage (Firestore), crash reporting (Crashlytics), analytics, and serverless functions. Firebase Privacy.
- Third-party AI providers: Analysis and coaching responses are generated by third-party AI providers, which may include Anthropic, OpenAI, or Google. Conversation text and chat messages are sent to one of these providers (selected by our backend routing layer) for processing. The specific provider used for a given request may change over time as we tune for quality and reliability. Each provider's data usage policies apply: Anthropic Privacy · OpenAI API Data Usage · Google AI Terms.
- Apple / Google payment processors: If you purchase a subscription through the iOS or Android app, payment is handled by Apple's StoreKit or Google Play Billing. We do not receive your payment-card data — only a verification token confirming the purchase.
5. Data Storage & Security
- In transit: All communication between the app and our servers uses HTTPS/TLS.
- Server-side: Conversation text, analysis results, coaching state, and chat history are stored in Google Cloud Firestore. Firestore data is protected by security rules that ensure users can only read their own data. All server-side writes use the Firebase Admin SDK.
- Server region: Our Firestore database and Cloud Functions are hosted in Google Cloud's us-central1 region (Iowa, United States). Your data is stored and processed in the United States. If you access SigApp from outside the US, your data is transferred to the US for processing.
- API keys: AI provider API keys are stored in Google Secret Manager and are never present in the app code.
5.1 Local Storage — Platform-Specific
- Android: Analysis results, chat history, saved conversations, and pending analysis jobs are mirrored locally in a SQLCipher-encrypted Room database for fast offline access. The database is stored in the app's private sandbox and encrypted at rest.
- iOS: Analysis results, chat history, and saved conversations are mirrored locally using Apple's SwiftData, stored in the app's private sandbox. iOS additionally protects app sandbox data at rest using the device's hardware-backed Data Protection encryption.
- Web: The web app does not store conversation data locally — it reads directly from Firestore. A small amount of session metadata (e.g., signed-in state) may be cached by your browser.
6. Data Retention
- Conversation text, analysis results, coaching state, and chat history: Retained in Firestore until you delete your account or delete the data through in-app controls. We do not auto-expire this data because Dr. Sigi uses it to provide continuity across coaching sessions.
- Crash reports & analytics: Retained per Google/Firebase default retention periods (typically 90 days for crash data, 14 months for analytics).
- Local data: Retained on your device until you delete it through in-app controls, sign out, or uninstall the app.
7. Your Rights — Deletion
You can delete all your data at any time:
- In-app account deletion: Go to Settings > Account > Delete Account. This deletes your Firebase Auth account, all Firestore documents associated with your user ID (conversation text, analysis results, coaching state, memory, subscription record, chat history), and instructs the app to clear its local database.
- Web request: Visit our deletion request page to request account deletion by email if you no longer have access to the app.
Upon deletion, we remove all of the above from our active systems. Crash reports and aggregated analytics data may persist in anonymized form per Firebase's default retention windows.
8. Children's Privacy
SigApp is not intended for users under the age of 16. We do not knowingly collect data from children. If you believe a child has used the app, please contact us and we will delete their data.
9. Not a Medical or Therapeutic Service
SigApp is not therapy, diagnosis, or mental health treatment. AI-generated insights are for educational and self-reflection purposes only. They may be inaccurate and should not replace professional advice from a licensed therapist, psychologist, or counselor.
10. Platform-Specific Notes
- Android: If you grant SMS read permission, SigApp can read SMS messages from your device for analysis. SMS content is treated the same as any other conversation text (Section 1). SMS access is optional — you can use the app without granting it.
- iOS: SigApp cannot read SMS messages on iOS due to platform restrictions. Conversation imports are limited to text you share via the iOS share sheet (most commonly WhatsApp exports). Sign in with Apple is planned for a future release; in the current version, sign-in options on iOS are limited to anonymous use and Google Sign-In.
- Web: The web app requires Google Sign-In (no anonymous mode). Conversations are imported by pasting text directly. The web app does not store data locally beyond your sign-in session.
11. Changes to This Policy
We may update this policy from time to time. Material changes will be reflected in an updated effective date at the top of this page and summarized in the changelog below. Continued use of the app after changes constitutes acceptance.
Changelog
- May 27, 2026: Added WhatsApp Export share-sheet flow (Section 2). Made retention language honest — conversation text and analysis results persist in Firestore until account deletion (was previously misstated as "not stored after processing"). Replaced specific OpenAI naming with generic third-party AI provider language reflecting our multi-provider routing layer (Anthropic, OpenAI, Google). Disclosed us-central1 server region. Split local-storage description into per-platform sections (Android SQLCipher / iOS SwiftData / Web Firestore-only).
- March 16, 2026: Initial policy.