Privacy Policy

Monte helps people create a derived persona that can personalize AI tools. To do that, a user may upload files, exports, notes, or other source material. Monte processes that material to extract behavioral signals and create a persona artifact.

The source material is not the product. The persona is the product. Our privacy model is built around that distinction.

Monte does not keep raw uploaded user data as a stored product record. Uploaded source material is used as a temporary processing input while Monte creates or updates the persona.

After the persona creation or update process completes, Monte deletes the raw uploaded material and temporary processing traces from our active systems. The remaining stored record is the derived persona and related account/control-plane records needed to operate the service.

This is a core product commitment: users should not have to trust Monte as a permanent vault for their private exports. Monte is designed to transform temporary inputs into a portable persona, then remove the raw inputs.

Account information: when you create an account or sign in, we may receive your name, email address, profile image, authentication identifiers, and session metadata from the authentication provider.

Temporary source material: if you upload files or connect a source for persona creation, we process the content only to create or update your persona. This material is temporary and is deleted after processing as described above.

Derived persona information: Monte stores the persona artifact created from your inputs, including preference signals, dimensions, self-model summaries, active epochs, open questions, staleness warnings, version metadata, and related configuration.

API and usage information: when you use the dashboard, CLI, API, or future MCP surfaces, we collect operational records such as API key metadata, request timestamps, endpoint names, status codes, usage counts, and billing or credit records.

Support and communications: if you contact us, join the waitlist, or request support, we collect the information you provide and the metadata needed to respond.

We use account information to authenticate users, secure accounts, manage sessions, and communicate important service information.

We use temporary source material only to create, update, validate, or debug the user-requested persona workflow. We do not sell raw uploaded data, use it for advertising, or retain it as a long-term training corpus.

We use derived persona information to provide Monte personalization outputs through the dashboard, CLI, API, and future MCP integrations.

We use API and usage information to operate the service, prevent abuse, monitor reliability, calculate usage or billing, and improve performance.

If you sign in with Google, Monte uses Google OAuth through Supabase Auth. We request only the account information needed to authenticate you, such as your email address, basic profile information, and authentication identifiers.

Monte uses Google sign-in data only for login, account creation, account security, session management, and user support. We do not sell Google user data, use it for ads, or use it to train general-purpose AI models.

Monte’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Monte uses service providers to run the product, including hosting, authentication, databases, email delivery, observability, and payment or billing infrastructure. These providers process information only as needed to provide their services to Monte.

Current categories include cloud hosting, Supabase authentication and database services, email delivery, analytics/observability, and infrastructure providers for queues, object storage, or graph data.

Monte may send task-specific processing requests to model providers when needed to generate persona outputs or supporting analysis. We minimize what is sent for the requested operation.

Monte does not use raw uploaded user data to train a Monte-owned general-purpose model. We also do not sell user data to model providers.

Raw uploaded source material is temporary and deleted after persona creation or update completes.

Derived persona records, account records, API key metadata, billing or credit records, and usage logs are retained while your account is active or as needed to provide the service, comply with law, resolve disputes, prevent abuse, and enforce agreements.

Backups and logs may persist for a limited period according to normal security and disaster-recovery practices, but Monte’s active product systems are designed around deletion of raw uploaded source material after processing.

We use technical and organizational safeguards intended to protect user information, including access controls, authentication controls, secret management, transport encryption, and operational monitoring.

No internet service can guarantee perfect security. If we learn of a security incident that affects your information, we will take appropriate steps consistent with applicable law.

You may request access, correction, export, or deletion of your account or persona information by contacting us.

If you ask us to delete your account, we will delete or de-identify account and persona records unless retention is required for legal, security, billing, or abuse-prevention reasons.

You can revoke Google account access through your Google Account permissions page, and you can revoke Monte API keys from the dashboard where supported.

Monte is not intended for children under 13, and we do not knowingly collect personal information from children under 13.

We may update this Privacy Policy as the product changes. If changes are material, we will take reasonable steps to notify users, such as updating the effective date or providing in-product notice.

For privacy questions or requests, contact help@monteengine.com.