Data Protection
Export, deletion, and account data controls.
Monrac is built for personal finance, so data protection is part of the product surface. This page explains the controls and practices planned for account data.
Last updated: May 7, 2026
1. Purpose of This Page
This Data Protection and Deletion page explains how Monrac approaches data isolation, export, deletion, retention, and privacy requests across the Monrac mobile app and web app.
This page is meant to make user data controls clear. It works together with the Monrac Privacy Policy and Terms and Conditions.
2. Data Isolation
Monrac is designed around account-level isolation. Financial records, portfolio records, documents, commands, and context summaries are intended to be scoped to the authenticated user's account.
The product architecture is designed so database access is tied to user identity, reducing the risk that one account can access another account's information.
3. Data Export
Monrac is intended to support export of your account data, including finance records, portfolio records, command history, settings, and related user-scoped information where technically available.
Exports may be provided in common machine-readable formats such as JSON or CSV. Certain operational logs, security records, derived analytics, and provider-side records may not be included if they are not part of your user-controlled dataset.
4. Data Deletion
You may request deletion of your Monrac account and user-scoped data. Deletion is intended to remove personal financial records, portfolio records, documents, settings, command history, and related user-controlled information from active systems.
Some limited information may be retained where required for legal, billing, fraud prevention, dispute resolution, security, backup, audit, or compliance purposes.
Deleted data may remain in encrypted backups or logs for a limited period until those systems rotate or expire, unless faster deletion is technically feasible.
5. Retention
Monrac keeps user data while your account is active or as needed to provide the service. If your account is deleted, we aim to remove active user-scoped records within a reasonable period.
Security logs, billing records, support records, and legal records may be retained for longer periods if needed to comply with obligations or protect the service.
6. AI and Derived Data
Monrac may create derived data such as categories, summaries, insights, context summaries, and command classifications to make the service useful.
When you delete your account, Monrac aims to delete derived records that are scoped to your account. Aggregated or de-identified analytics that no longer identify you may be retained.
7. How to Make a Request
You can request access, export, correction, or deletion by using in-app controls where available or by contacting hello@monrac.io from the email address associated with your account.
We may need to verify your identity before completing a request. If we cannot verify that you control the account, we may be unable to disclose, export, modify, or delete account data.
8. Mobile App and Web App Scope
The same data protection approach applies whether you use Monrac through the mobile app or web app. Local mobile data used for offline-capable features may sync when connectivity returns.
If you delete the mobile app from your device, that may remove local app data from the device, but it does not necessarily delete your cloud account. Use account deletion controls or contact us to delete cloud data.