nemonist is operated by nTwins, Inc. ("nTwins", "we", "us"). It gives coding agents a memory that learns. This policy covers nemonist.com, the dashboard and the API: what we collect, why, who we share it with, how long we keep it, and the choices you have. Our Terms of Service also apply.
1. What we collect
Account details. Your email address and password (the password is handled by Amazon Cognito; nemonist never sees or stores it), and your name and profile photo if you sign in with GitHub or Google. If you upload a profile photo, we store it and show it to the members of your organizations in place of your sign-in picture; it is deleted when you remove it or delete your account. From GitHub or Google we receive only your basic profile and verified email (the openid, email and profile scopes), never your password for those services.
Organizations. If you create or join one: its name, handle and logo, its members' email addresses, roles and profile photos, pending invitations, and an audit log of administrative actions that names the member who took each one.
Requests you send through nemonist. The prompts, code, files and tool results your agent sends, and the model's replies. We process them to add your memory and pass them to the model provider that serves the request. For a workspace nemonist recognizes, we also keep each request exactly as your agent sent it, so your agent can search its own earlier conversations in that workspace (the recall_history tool). We keep them for one year, and delete them sooner when you delete that memory or your account. We keep the model's reply to each request beside it, for the same year, so we can find and fix problems such as refusals, cut-off replies and wrong answers. Other requests (for example an app's side calls, or requests from a project nemonist doesn't recognize) are kept with their replies for 30 days, for the same reason. If your account turns on zero data retention in Settings > Privacy, we keep no replies and none of these other requests. We don't write prompts or replies to our logs.
Memory. Notes your agent writes for each workspace from your conversations, such as decisions, conventions, preferences and unfinished work, with their edit history and a record of the agent's reads and edits. To name each workspace on your Memory page, we also keep the last part of its folder path as your coding app reports it (for example code/my-app, never the full path) and the app that last used it; you can rename a workspace, or turn folder names off in Settings > Privacy.
Usage records. For each request: the time, model, provider, token counts, cost, latency, the API key that made it, and the calling app as it names itself (its title, referring site or user agent).
Billing. Credit purchases, automatic top-ups, promo codes and credit transfers. Stripe holds your card; we keep only its brand, last four digits and the Stripe reference used to charge it.
Organization administration. If your organization connects an identity provider: a SCIM token (stored only as a one-way hash) and, for members it deactivates, their email and the time, so the provider can read them back; workload identity trust policies (issuer, audience and subject pattern) and an audit record of each exchange.
Support tickets. If you open a ticket on the Support page: your email, the account you had selected, its subject, category and priority, what you and our support staff write in it, and the files you attach, which we keep privately and share only through short-lived download links.
Forms. If you ask to be notified about a plan, your email; if you contact sales, the name, company, work email, expected spend and needs you enter, which go to our support inbox.
Keys. nemonist API keys are stored only as a one-way hash. If you connect your own Router key, it is stored encrypted.
Technical data. The IP address of each request, used to enforce IP allowlists you set and to protect the service; and operational logs (request ids, status codes, timings and error types), which don't contain your prompts or replies.
Session recording. On nemonist.com we record what you see and do on the site (pages, clicks, what you type, network requests and their content, console messages and errors) with OpenReplay, which we host ourselves in AWS us-east-1, to find and fix problems. Passwords, one-time codes, card numbers, API keys and tokens are never recorded: they are hidden or removed in your browser before anything is sent. A recording is linked to your account and email. Our support team can view a live session to help you; a call or screen control asks you first. Your browser's Do Not Track setting turns recording off.