Privacy Policy
Last updated: August 31, 2026
1. Scope and who is responsible
This policy explains how MindReminder handles personal information in its web app, installable PWA, and Expo-based mobile app. It is an operational description, not a certification or guarantee that every legal requirement is met in every circumstance.
MindReminder is the service operator for the data described here. For privacy questions, rights requests, or a complaint, contact privacy@mindreminder.com. You can also use our contact page.
2. Information we handle
- Account and profile: email address, authentication identifiers, name or profile details you provide, settings, timezone, and notification choices.
- Content: reminders, descriptions, Lofty Questions, Micro Habits, saved or generated quotes, affirmations, check-ins, completion history, and messages used when sharing with friends.
- Friend and sharing data: friend requests, accepted relationships, shared reminders, read status, and the names needed to display those relationships. Do not put health information or other sensitive personal information in shared content.
- Device and delivery data: browser push subscriptions, Expo push tokens, platform, notification permission and delivery status. Raw push-token values are not included in a user data export.
- Support data: name, email, category, subject and message sent through the contact form. The form is rate-limited using the sender email and timestamp.
- Technical and usage data: request and security logs, error/performance information, page paths, session identifiers, and controlled product events. Analytics is described separately below.
Please keep sensitive information out
MindReminder is not a healthcare service. Avoid entering diagnoses, medication details, crisis information, biometric data, or other health, financial, identity, or similarly sensitive information in reminders, reflections, sharing messages, contact messages, or AI-refinement text. Content you submit may be stored by us or sent to a service provider described below.
3. Why we process information
Depending on the feature, our basis is performance of the service you request, steps needed before providing it, our legitimate interests in security and support, legal obligations, or your consent for optional analytics. We do not use acceptance of the Terms as a substitute for consent where consent is required.
- Provide the service: create accounts, save and sync content, display Journey history, manage friends and sharing, and send requested reminders.
- AI features: refine a Lofty Question and, when configured, generate an inspirational quote. The submitted text and category are sent to the configured AI provider only to produce the requested result. Do not submit sensitive information.
- Notifications: request permission, register a delivery token, and submit reminder content to the selected push provider. Push can be disabled in device or app settings.
- Support and safety: answer messages, prevent abuse, rate-limit contact submissions, investigate faults, and protect accounts and infrastructure.
- Optional measurement: understand feature use and conversion on the web, improve the product, and provide the private Journey analytics view. MindReminder-controlled GA4, internal product events, and project-event calls are enabled only after the user selects “Accept all”; Replit may separately collect platform traffic metrics as part of hosting under its own terms.
4. Providers and recipients
We do not sell personal information. We use processors and infrastructure providers to run the service. The data they receive depends on the feature you use:
| Provider/category | What it receives and why | Location/transfer note |
|---|---|---|
| Supabase | Database records, authentication, and push-token records needed for accounts, sync, sharing, exports, and deletion. | The project database is hosted in Stockholm, Sweden/EU. This does not mean all processing in the service occurs in the EU. |
| Replit hosting | Application requests, runtime data, and technical logs needed to serve the web app and APIs. | Replit infrastructure is primarily on Google Cloud in the United States. Replit workspace geography and product terms may affect applicable location. |
| Replit Analytics | Published-app traffic information, including network/browser-based visitor metrics, and the controlled project events sent by this app after analytics consent. | The consent gate controls MindReminder’s project-event calls, not platform traffic measurement that Replit may perform as part of hosting. We do not describe Replit Analytics as anonymous, cookieless, EU-hosted, or consent-free. Location and retention follow Replit’s current product and privacy documentation. |
| Google Analytics 4 | Consent-gated page views and controlled events such as feature use, sign-up, and CTA interaction. We intentionally avoid sending reminder text, reflections, or free-form content as event dimensions. | Google may process data outside the EEA under its current transfer safeguards. Retention is controlled by the GA4 property settings. |
| Resend | Contact-form name, email, subject, category, and message so support can reply. | Resend may process data outside the EEA under its current terms and safeguards. Provider retention is not fixed by this app. |
| Anthropic and OpenAI | AI input and output needed for configured AI features. The current server routes use Anthropic when its key is configured; an OpenAI-backed quote utility is also present and may receive quote input if enabled. Do not send sensitive content. | These providers may process data outside the EEA under their current API terms and safeguards. Provider retention depends on the account, endpoint, and settings in use. |
| Expo | Expo push token, platform, notification title/body, and delivery identifiers for mobile notifications. | Expo’s push service may route through infrastructure outside the EEA. Expo forwards notifications to Apple or Google as applicable. |
| Apple and Google push services | The device token and notification payload needed to deliver notifications on iOS or Android. Web push uses the browser’s push service and our Web Push/VAPID endpoint. | Apple Push Notification service, Firebase/Google push infrastructure, and browser push services may process data outside the EEA under their own terms. |
We may also disclose information when required by law, to protect users or the service, or as part of a business transfer. A friend receives only the content you choose to share and the relationship information needed to display it.
5. Analytics, cookies and local storage
Essential Supabase session cookies and local settings are used to keep authentication and preferences working. Optional analytics is off until an explicit “Accept all” choice is stored locally. The choice is kept in browser localStorage under mindremindr_cookie_consent; it is not itself a server account record.
After consent, the web app can send controlled events to GA4, Replit Analytics, and the app’s own Supabase user_events table. Internal product analytics is separate from GA4 and Replit Analytics and is visible to the signed-in user in Journey/analytics. See the Cookie Policy for the technology list and preference instructions.
6. Security and incidents
We use access controls, authenticated API requests, row-level database policies where applicable, encryption provided by our infrastructure, and scoped service credentials. No online service can promise absolute security.
If we become aware of a personal-data incident, we will assess it and make any notification required by applicable law. We may contact affected users through the account or support details available to us.
7. Retention and deletion
We keep information only for the period or purpose described below. The retention matrix in our internal record is maintained alongside provider checks.
| Data | Period/criterion | Deletion route |
|---|---|---|
| Account and content | While the account is active, then removal is requested; legal holds can take precedence. | Settings account deletion invokes transactional deletion of application rows and closes the Supabase Auth user. |
| Internal analytics | Only after analytics consent; retained with the account unless deleted earlier by an operational process. Daily summaries follow the source account data. | Account deletion removes event and summary rows. Withdraw consent stops future collection but does not automatically erase prior events. |
| GA4/Replit analytics | According to the configured property and provider retention settings; exact periods are not controlled by this page. | Use the cookie preference for future collection and contact us for an access/deletion request; provider-specific deletion may be required. |
| Logs and security records | As needed for security, debugging and legal obligations; platform retention periods can change. | Operational deletion follows the hosting/logging configuration. |
| Contact email/message | The email/timestamp is used for a one-hour rate-limit window. The configured retention period for rate-limit rows is 24 hours; when a valid contact-form request is processed, up to 100 older rows are removed. Since cleanup is request-triggered, rows can remain until a subsequent request. Resend/support mailbox retention follows their controls and terms. | Request deletion from privacy/support; a message already delivered to a mailbox or provider may require separate deletion. |
| Push tokens | Until you unregister, disable notifications, the token expires, or the account is deleted. | Disable/unregister in the app or device; account deletion removes stored token rows and stale provider tokens are cleaned when detected. |
| Backups | Provider backup cycles and disaster-recovery policies apply. We do not promise a fixed erasure interval for copies that are not immediately restorable. | Deleted data is removed from active systems; backup copies age out under the provider’s current policy. |
Account deletion is available in Settings → Account and is intended to remove application data in one transaction. The export endpoint lets an authenticated user download their account and content data as JSON. If a deletion or export appears incomplete, contact us promptly.
8. Your rights and choices
Subject to applicable law, you may ask for access, a copy/export, correction, deletion, restriction, objection, and withdrawal of consent. You can export data from the account feature, correct profile/content in the app, delete the account from Settings, and change analytics choice through the cookie control. Withdrawal affects future optional analytics; it does not make earlier lawful processing unlawful automatically.
We may need to verify your request and may retain a minimal record of the request. We aim to respond within the period required by law. You may complain to the data protection authority where you live, work, or believe an infringement occurred. In Norway, complaints may be submitted to Datatilsynet.
9. International transfers
Supabase database storage in Stockholm, Sweden/EU is described separately above. Hosting, analytics, AI, email, and push providers can process information outside the EEA. Depending on the provider and circumstances, transfers may rely on an adequacy decision, standard contractual clauses, or another lawful safeguard. We do not claim that all processing occurs in the EU.
Provider terms and transfer mechanisms can change. Ask us for current information about a particular processing activity when exercising your rights.
10. Age rule
MindReminder is intended for people aged 16 or older. We do not knowingly invite children under 16 to create accounts, and we do not operate a technical age-verification or parental-consent flow. If you believe a person under 16 has provided information, contact us so we can review and remove it where appropriate.
11. Changes and contact
We may update this policy when the service, providers, or legal requirements change. We will post the new version and update the date; material changes may also be communicated in the app or by email where appropriate.
For general support, use hello@mindreminder.com or the contact page.