Privacy policy

What we collect

• Your account. You sign in with Google. We receive and store your name, email address and profile photo. We keep Google’s sign-in tokens, encrypted, so you stay signed in. We never see a password. We use this Google account data to sign you in, show your profile and, when you start checkout or open billing, create your Stripe customer record. We don’t use it for advertising, we don’t sell it, and we don’t use it to train AI models.
• Sessions. A session record with your IP address and browser type, so we can keep you signed in and spot misuse. A session expires 30 days after your last visit. Expired session records currently stay in our database until your account is deleted.
• Abuse protection. When anyone, signed in or not, uses sign-in and some other endpoints, we store their IP address with a request counter so we can apply rate limits. These records are not yet deleted on a schedule.
• What you create. Dashboards, with the notes and custom widgets on them, and the pages you save to your menu.
• Notifications. The notifications in your inbox, including notes from assistants you connect, and which notifications you turned off.
• Billing. Payments run on Stripe’s own checkout and billing pages. When you start checkout we send Stripe your name and email address. We store your Stripe customer ID, email, subscription status, plan and billing period, and the billing events Stripe sends us, which can include your name, email address and billing address. Card details go to Stripe only; we never see or store them.
• API keys and connected assistants. API keys are stored as a one-way hash. To tell keys apart we keep a short key ID, the last four characters, the name you give the key and when it was last used; revoked keys stay listed with an audit trail. When you connect an assistant, we store the connection and its access tokens. We count requests per key and per connection, by day and by month, to apply limits.
• The in-App assistant. We store your chats so they follow you to other devices: your questions, the answers, the data the assistant’s tools returned for them, the chat title, whether you pinned it and any thumbs up or down you gave an answer. Deleting a chat erases its messages and title. Separately, for each turn we keep an audit record: status, provider and model, prompt version, the tools used, token counts, any error, the page you asked from, a conversation ID and a hash of the input, not the text itself; it stays when you delete the chat. When the assistant proposes a change for you to confirm, we store the proposal and its reasoning. What reaches the model provider is described below.
• Access checks. When you use a feature with plan limits, we record your account ID, the feature, your plan, whether access was allowed, a request ID and the time.
• Error logs. Server errors are logged. Our logger filters email addresses and secret-looking values from what it records.

The in-App assistant and connected assistants

When you ask the in-App assistant something, we send the model provider that handles the turn your conversation so far, what’s on the page you’re viewing and the results of the tools the assistant uses to answer. When a question needs them, those tools read your own dashboards and notifications, and the results go to the provider too.

Turns run first on Claude Haiku, a model we reach directly at Anthropic. When it can’t answer, they run on openly published models (from Z.ai, DeepSeek and Xiaomi) reached through OpenRouter, a service that routes each request to a company hosting the model. For those we allow only hosts based in the United States — GMI Cloud, Novita AI, Baseten, Parasail, DeepInfra and CoreWeave — never the companies that made the models. An image you attach goes with the rest of the turn to the same models. We ask OpenRouter to use only hosts that don’t store inputs long-term or train on them.

When you connect your own assistant (such as Claude, ChatGPT or Cursor) over MCP or the API, the data it asks for, including your dashboards and notifications if you granted that access, goes to that assistant. How its provider handles it is governed by your terms with that provider, not by this policy. We keep the request counts described above and, when your assistant proposes a dashboard change, the proposal (its contents, the assistant’s reasoning, which connection sent it, its status and times) until you delete your account.

Cookies and browser storage

We set only what the service needs. None of it is used for advertising or to track you across sites.

Google sign-in and Stripe checkout run on Google’s and Stripe’s own sites, which set their own cookies there under their own policies. We don’t track you across sites, so Do Not Track and Global Privacy Control signals change nothing here, and no third party collects your activity across sites through Nomior.

Why we use it

You need to give us your Google account details to have an account; without them we can’t provide one. Nothing else is required by law or by contract. We don’t make decisions about you that have legal or similarly significant effects by automated means alone.

Who receives it and where

Stripe also processes payment data for its own purposes, such as fraud prevention and legal compliance, as an independent controller under the Stripe privacy policy. That data is processed outside your country.

Our team works from the United States and reaches the data hosted in Germany from there. We share personal data with no one else, except as listed on this page, as you direct (for example with an assistant you connect), or when the law requires it.

How long we keep it

• Account data and what you create: while your account exists. Deleting your account deletes your dashboards, saved pages, sessions, API keys, assistant chats and their audit records, and assistant connections with it.
• Sessions and rate-limit records: see What we collect.
• Database backups on our server roll off automatically, most within days. Deleted data disappears from them when they roll off.
• The billing events Stripe sent us, which can include your name, email address and billing address, are kept after an account is deleted, for tax and accounting. Your Stripe customer ID, subscription, plan and billing period are deleted with the account. Stripe keeps its own records.

Your rights

You can ask us to:

• show you the personal data we hold about you (access);
• correct it (rectification);
• delete it (erasure);
• limit how we use it while a question is sorted out (restriction);
• give it to you, or to another service, in a machine-readable format (portability);
• stop using it where we rely on legitimate interest (objection).

Email support@nomior.com from the address on your account. If you can’t, we’ll verify who you are another reasonable way. We’ll act within 30 days. You can disconnect any assistant and revoke API keys yourself from the App.

You can also complain to a data protection authority: in the UK, the Information Commissioner’s Office (ico.org.uk); in the EU, the authority in the country where you live or work.

Children

Nomior Memory is for adults. We don’t knowingly collect data from anyone under 18. If we learn that someone under 18 has an account, we delete it. Tell us at support@nomior.com.

Changes

When this policy changes in a way that matters, we update the date at the top and, for significant changes, tell signed-in users in the App.