OpenAI and your Programs
Mentum uses OpenAI, a third-party AI service, through its API to interpret requests and create or edit Programs: the rules, feeds, trackers, charts and other supported behaviors you ask Mentum to make. OpenAI processes the request on its servers and returns proposed behavior, clarification questions or generated text. You do not need a ChatGPT account to use this integration.
Some activated Programs also use OpenAI to match messages by meaning or generate automatic replies. A Program that counts words, checks a sender or filters by attachment type can run without sending each matching message to an AI model. Using OpenAI to draft a Program and using it while that Program runs are separate activities.
Data sent to OpenAI
For Program creation and editing, we send the instructions you type to Mentum, your clarification answers, and relevant parts of that authoring conversation, including earlier proposals and validation feedback. Context can include your display name; internal account, chat and participant identifiers; chat titles, roles and time zones; participant display names and usernames from chats you can access; and the existing Program definition when you request an edit. This helps the agent resolve people, scope and requested behavior. Names and identifiers can be personal information, even when an internal identifier is used instead of an email address.
For meaning-based matching, relevant message text and reference phrases describing the rule are sent to OpenAI to produce embeddings, which are numerical representations used for similarity comparisons. For automatic AI replies, the Program’s instructions and selected, bounded message context are sent to OpenAI to generate a response. This can include another participant’s message and personal information contained in it. Processing follows the Program’s room or personal-account scope; a personal notification policy may evaluate eligible messages across the owner’s accessible chats. Embeddings, matching results and Program state can be cached in Convex.
The current Program AI paths send text and structured context, not raw photo, audio, video or file contents. Attachment metadata can describe a message as containing a photo without uploading that photo to OpenAI. We do not automatically upload an entire chat transcript or unrelated private chats. Text you paste or quote in an agent request or an eligible message can nevertheless contain personal or sensitive information; do not include information you are not entitled to share.
Passwords, sign-in tokens, payment-card details, your device address book and precise device coordinates are not supplied as Program AI context. A country label or other personal detail you include in a request or permitted Program context may be processed with that text. OpenAI also receives the technical request metadata needed to operate and secure its API. We use the responses to provide the requested feature, not to sell your conversations or target advertising.
AI choices and separate permission
Personal information must not be sent to a third-party AI service without the required prior permission. That permission must identify OpenAI, the information being shared and its purpose. Reading this Privacy Policy or accepting the Terms of Service is not, by itself, permission for AI sharing.
Program drafting uses OpenAI before the later activation review. Before your first AI request, the app presents a separate disclosure naming OpenAI, the information sent, its purpose, and background processing. Signing up and ordinary chatting do not require AI sharing. Choose Allow sharing with OpenAI to opt in or Don't allow to leave it off. Both choices are saved for your account. Permission is not inferred from signing in, opening a policy, navigating away or approving a Program’s automatic actions. A materially revised disclosure requires a new affirmative choice. Older clients without this permission flow cannot start new AI requests; update the app to review the choice.
Review AI sharing remains available on the Mentum agent screen after either choice. The full disclosure and your current choice are also available in Settings → Privacy sharing → AI sharing. Opening or rereading the disclosure does not change your choice or send an AI request. If the app cannot verify a saved choice, it cannot grant new permission; you can skip AI setup and keep using ordinary chat.
You can withdraw permission in Settings → Privacy sharing → AI sharing. Turning it off stops new authoring requests and new background AI processing of your messages. Ordinary chats and Programs that do not need external AI continue to work. Meaning-based matching and automatic AI replies require the relevant author’s permission, not just the Program owner’s approval. Programs that remember earlier message context may need an edited, reapproved revision to rebuild that context after a contributor’s permission changes. This does not delete already-created Programs, messages or cached records; use the separate pause, delete and account-deletion controls for those purposes.
Contact araujota97@gmail.com to withdraw an AI-processing permission or request deletion of associated information if an in-app control is unavailable. We may verify account ownership. Withdrawal stops the applicable future processing; it cannot recall a completed API request or erase copies another participant retains. The retention and deletion limits below still apply.
OpenAI retention and protection
OpenAI states that API inputs and outputs are not used to train or improve its models by default unless the API customer explicitly opts in. This is an API integration, not a consumer ChatGPT conversation. Mentum’s text-generation requests disable optional response storage with store=false; that is not a promise of zero retention.
OpenAI may retain API content in abuse-monitoring logs for up to 30 days by default, and longer when required by law or reasonably necessary to protect its services or others from harm. Other technical retention, such as model-dependent prompt caching, can apply. Mentum does not promise Zero Data Retention or immediate deletion from every provider record. See OpenAI API data controls for the applicable details.
OpenAI’s processing on our behalf is governed by the OpenAI Services Agreement and OpenAI Data Processing Addendum. These address instructed processing, confidentiality, security, subprocessors and assistance with personal-data requests. We remain responsible for our use of the provider and for the safeguards described in this policy; linking to another policy does not replace our obligations to you.
Information you provide
Account information includes your authentication identifier, username, display name, profile photo if you add one, and email address or other sign-in details if you supply them. Clerk handles authentication credentials and sessions; Mentum does not store your password in its application database.
We store the messages, replies, reactions, files and images you share, chat memberships, historical access records, and account settings needed to provide the service. We also store your requests to the Mentum agent, clarifications, Program definitions and revisions, feeds, trackers, notification policies, and their execution state.
Where membership billing is used, we receive subscription and entitlement information such as the selected plan, billing period, status, trial or cancellation dates, and provider account or transaction references. Payment providers handle payment credentials; Mentum’s application database does not store full payment-card or bank-account details.
If you contact support or report content, we receive the information you choose to include and relevant account, content and diagnostic references. Do not send passwords, authentication codes, or unnecessary private conversation content to support.
Device and usage information
Mentum uses account and device identifiers, app and operating-system versions, session and event timestamps, delivery/read state, push-notification tokens, and security or error metadata. Local app storage can hold cached messages, pending actions and settings. On native mobile clients, authentication token caching uses the operating system’s protected storage. Clerk manages browser authentication using browser cookies, session tokens and its session-security mechanisms.
The browser client uses local storage, including IndexedDB, for recent messages, drafts, unsent files, queued actions, profile pictures and Program results. These records use browser isolation and Mentum’s account/session access checks, not separate app-level encryption. Account → Browser storage lets you clear saved profile pictures and Program results without clearing drafts, unsent files or queued actions. Clearing site data in your browser can remove unsent work; it does not delete your server account or copies you downloaded or shared. Sign out when you finish using a shared device.
Our hosting and service providers process network information such as IP addresses and request metadata to deliver, secure and troubleshoot the service. The public information pages use no advertising or analytics scripts and do not add tracking cookies. The browser client uses authentication and security technologies and sends bounded, redacted reliability diagnostics; it does not use advertising trackers.
Country badge and device permissions
Sharing a country badge is optional. You may select a country manually or explicitly ask the device to suggest one. Continuing to the system location request is not permission itself: the operating system lets you allow or decline access. You can decline, continue using Mentum and choose a country manually. For a suggestion, the operating system obtains a foreground location and reverse-geocodes it. Mentum’s country feature does not send precise coordinates to its application backend or keep a location history; the operating system’s location/geocoding services may process them.
The saved information is the country code and your sharing preference. A shared badge can appear with your profile and messages to permitted viewers and can be used by Programs or notification rules. It is a user-selected label, not proof of citizenship or verified residence. You may change or stop sharing it in Privacy settings.
The current app can inspect contacts-permission status, but does not upload your address book. Recent people are derived from chat activity, not a bulk contact import.
Photo, file, camera, location and notification features depend on the relevant device permissions or system pickers. You can manage permissions in device settings; denying a permission may prevent the related feature from working.
Why we use information
We use information to authenticate users; deliver and synchronize chats; provide discovery, profiles and shared rooms; create and run requested Programs, feeds and notification rules; handle account access; prevent abuse; respond to support and deletion requests; and diagnose reliability problems.
Messages and other shared content are visible to authorized chat participants. Exact-username lookup can expose a limited profile to help another user find you. Room authority, privacy settings and Program scope determine additional access; a Program is not permission to read unrelated private chats.
Mentum is not an end-to-end encrypted messenger. Server-side storage and processing are necessary for its synchronization and programmable features. Do not use it to send information that requires end-to-end encryption or regulated handling.
Service providers and other disclosures
Our providers include Clerk for authentication and configured account/billing services; Convex for application data, file storage, backend execution and searchable application diagnostics; OpenAI for the Program authoring, embedding and reply-generation processing described above; Expo, Apple/Google and browser push services for notifications and app distribution; Vercel for this website and the browser client; and Langfuse for agent-workflow diagnostics.
We require service providers processing personal information on our behalf to provide the same or an equivalent level of protection as described in this policy and required by applicable law and platform rules. This includes purpose-limited processing, confidentiality, appropriate security, restricted access, and support for retention, deletion and rights requests. We do not authorize providers to sell private chat content or use it for targeted advertising. We remain accountable for selecting and configuring these providers; their separate operational or legal retention is disclosed here, not represented as identical to Mentum’s own retention.
Diagnostic collection is designed to redact message bodies, prompts, credentials and direct contact details. It can still contain error categories, app versions, timing, model/token usage and hashed or pseudonymous identifiers. These records are not necessarily anonymous. Notifications may contain a preview or a redacted alert according to your settings, and pass through the relevant push provider.
We use encrypted HTTPS/TLS connections for app-to-backend and backend-to-provider transmission, with authenticated, permission-checked access to application records. Encryption in transit is not end-to-end encryption: authorized servers and the disclosed providers can process the information needed for their functions. No system can guarantee absolute security.
We may disclose relevant information to protect people or the service, investigate abuse, comply with a lawful request, enforce our terms, or support a change in ownership subject to appropriate notice and safeguards. We do not sell private chat content or use it for targeted advertising. Other participants can copy or share content they receive; Mentum cannot control their independent actions.
Service providers may process information outside your country, including in the United States. Where applicable law requires it, transfers must use the safeguards required by that law.
Retention and account deletion
Account and chat data are kept while needed to operate your account, maintain shared conversations and Programs, or meet security, support and legal needs. Different records have different lifetimes; we do not represent all data as being automatically erased after a single universal period. Generated account-export downloads expire after seven days.
You can request export or deletion from Account → Data & support in the app. Deletion is a multi-step process, not merely sign-out or uninstall. It revokes account/device access and removes or de-identifies account-associated records. A room you own may need to be transferred or archived before deletion can finish.
Shared conversation history may remain for other participants, with the deleted author shown as “Deleted member.” Removing the account link does not erase identifying information someone wrote inside a message, a recipient’s copy, or screenshots. Contact us about a specific content-removal request.
Limited safety, integrity, diagnostic and deletion-evidence records may be retained for abuse prevention, troubleshooting, disputes and legal compliance. Provider backups and operational records follow their applicable retention processes and are not instantly erased from every copy. We do not promise deletion of information another participant independently retains.
Your choices and rights
You can edit your profile, withdraw the country badge, change notification preferences, manage supported Programs, block/report users, and request export or deletion. Device permissions are controlled through your operating system. See Account deletion for the in-app and external request paths.
Depending on your location and applicable law, you may have rights to access, correct, delete or receive a copy of personal information, object to or restrict processing, withdraw consent, or complain to your data-protection authority. Contact araujota97@gmail.com; we may need to verify ownership before acting. Some information or requests may be subject to lawful exceptions.
Where data-protection law requires a legal basis, we process information as necessary to provide the service you request, for legitimate interests in securing and improving it, to comply with legal obligations, or with consent where required. Withdrawing consent does not undo processing that was lawful before withdrawal.
Children, updates and contact
Mentum is intended for users aged 13 or older, subject to any higher minimum age or parental-consent requirement where they live. It is not directed to children below that age. If you believe a child has provided information contrary to these rules, contact us.
We may update this policy as the service or our practices change. The effective date identifies the current version; material changes will be communicated as required by applicable law.
For privacy questions or requests, contact araujota97@gmail.com. The operator is Tyler Araujo, based in Illinois, United States.