Data safety
Know where your data goes.
A plain-language summary of the data ForgeMind needs, how it is protected, and how you can remove it.
Effective September 3, 2026
Data ForgeMind may collect
- Account identifiers and authentication details.
- Conversations, voice transcripts, reflections, memories, mood check-ins, progress, and reset activity.
- Profile preferences, safety records, diagnostic events, and feature usage.
- Device installation, notification preference, and push-token information.
- Store-provided subscription status—not full payment-card information.
Why it is collected
These data support sign-in, AI and voice conversations, personalization, memory retrieval, progress, safety responses, notifications, subscription access, fraud prevention, diagnostics, and service reliability.
Processing by other services
ForgeMind can send only the information needed for a feature to service providers such as OpenAI or configured speech providers, Google or Apple authentication, Firebase notifications, email delivery, Sentry error monitoring, and PostHog product analytics. Provider use depends on the feature and production configuration. We do not sell personal data or conversation content.
Security practices
- Network traffic uses encrypted HTTPS or secure WebSocket transport.
- Production credentials are kept outside application source code and are limited by workload.
- Logs and operational findings are designed to redact conversation and credential material.
No system can guarantee absolute security. Contact us if you believe your account or data is at risk.
Your controls
ForgeMind supports data export, memory controls, notification controls, stored-data deletion, and full account deletion. Full account deletion starts with a seven-day restoration period. Public deletion uses an expiring email verification code and does not reveal whether an address is registered.
Important scope
This page is a readable product summary. The Privacy Policy provides the fuller policy. App-store data-safety disclosures must be kept consistent with the production configuration and should be reviewed whenever a provider or data flow changes.