What we do — and don't do — with your data.
This isn't a legal document. It's a plain-language explanation of how Momor handles your information across Momor Search and enterprise deployments. The legal version is in our Privacy Policy .
The basics.
Search history is under your control.
When you are signed in, conversation threads are saved to your account by default so you can revisit them later. If you want a search not to be saved, use incognito mode. Either way, we do not turn what you search into advertising or behavioral profiles, and we do not track you across sites.
We never train on your data.
Your queries, your documents, and any saved threads are never used to train, fine-tune, or improve any AI model. Not ours, not our providers'. This is enforced at the API level with every provider in our system. It's not a setting. It's how the system was built.
We don't sell your data.
Your curiosity isn't our product — it's the reason you came here, and we'd like you to be able to exercise it without wondering what it's going to cost you later. We don't sell data to advertisers, data brokers, or anyone else. We make money from subscriptions and enterprise licenses. That's it.
We don't profile you.
We don't build behavioral profiles. We don't track what you click after you leave momor.ai. We don't use cookies for advertising. We don't share data with third-party analytics. The data we need to run the service — account email, subscription status — is the minimum to operate. Authentication is not surveillance. Knowing you exist is not the same as tracking everything you do.
Additional guarantees.
Tenant isolation.
Enterprise deployments are fully isolated. Your documents, queries, and results never cross tenant boundaries. Isolation is enforced at the data layer, not the application layer — which means it doesn't depend on the AI model behaving correctly. The data is separated before the model ever sees it.
Your logs, your infrastructure.
If your compliance requirements need audit trails, logging can be enabled at the tenant level — owned and controlled by you, stored in your infrastructure, not ours. We don't keep logs of your queries unless you explicitly configure us to send them to your systems.
Provider constraints.
If your compliance requirements prohibit sending data to specific AI providers or jurisdictions, the routing system respects those constraints. You control which providers your data touches.
No training. Ever.
We enforce zero-data-retention agreements with every AI provider in our system. Your queries are processed and discarded — no provider stores, trains on, or retains your data. This isn't a setting we toggle on per customer. It's how every API call is configured, every time, for every deployment.
Questions?
If you ever see a gap between what we say here and what we do, email privacy@momor.ai. We want to know. The full legal version — with retention schedules, cookie policies, and technical specifics — is in the Privacy Policy.
Read the Privacy Policy →