Esment

Privacy Policy

Last updated: October 21, 2026

This policy explains how NotasAI Inc. (“we”), the company behind Esment, handles personal data. It covers your rights under the GDPR, the UK GDPR, the CCPA/CPRA, and similar laws.

Esment is local-first: in the macOS app, your memories, notes, and knowledge graph are stored on your own device and never reach our servers. Cloud memory is optional — a cloud account, the web dashboard, the hosted MCP endpoint, or sync from the app — and when you use it, we store your memories on our servers. Memories are the most sensitive data we handle, so section 3 explains exactly what happens to them.

1. Who we are

  • Company: NotasAI Inc., Delaware, USA
  • Address: 131 Continental Dr, Suite 305, Newark, DE 19713, USA
  • Contact: privacy@notas.ai

2. What we collect

  • Account — email and a hashed password.
  • Cloud memory — only if you use it: what you and your assistants save to your workspaces. See section 3.
  • Workspace members — the email and role of each person in a workspace, and which of them wrote each memory.
  • Billing — handled by Stripe. We see your plan and billing status, never full card numbers.
  • Sales — name, email, company, and notes, if you contact sales.
  • License & activation — a device fingerprint, app version, and heartbeats, to enforce activation limits and stop abuse.
  • Trial signups — email, IP, and device fingerprint, to stop repeat free trials.
  • Usage telemetry — off by default. If you turn it on, we receive counts only (memories, workspaces, LLM tokens) — never memory content.
  • Website analytics — PostHog: with cookies only if you consent, cookieless and anonymous otherwise. When you create an account we record the page and site your visit started from, and your country (never your IP). See our Cookie Policy.

What we don’t collect: the content of your memories in the macOS app, unless you turn on sync. That stays on your device; its search models run locally.

3. Your memories in the cloud

What we store

To provide cloud memory, we store what you or your connected assistants save to your workspace: the text of each memory with its tags and dates, Memory Blocks and pages, voice notes, the people, projects, and other things Esment finds in your memories and the links between them, and a history of every change (what changed, and when) so you can audit and undo it. We also store embeddings — numeric representations of the text used for search.

Who processes it

Your memories are stored, searched, and organised on our servers. Finding people, projects, and links in them happens there too, without any AI service. Two steps of search use a provider:

  • OpenAI receives the text of each memory, and of each search, to compute its embedding.
  • Voyage AI receives the text of a search and of its candidate memories, to rank them by relevance.

Both process the text only to return that result, under our agreements with them. Neither receives your account details, and we don’t allow either to use your content to train their models; each may keep it for a limited time to detect abuse, as its terms allow. No other AI service sees your cloud memory unless you choose one: an assistant you connect (section 7), the dashboard assistant with your own key (section 4), or an integration you set up with your own key (below).

What we never do

  • We never sell your memories or use them for advertising.
  • We never use your memories to train AI models — ours or anyone else’s.
  • Our staff don’t read your memories, except when you ask us to (for example, for support), when it’s needed to investigate abuse or keep the service secure, or when the law requires it. Access is limited to the few people who operate the service.
  • We work from counts, never content. We count the memories in each workspace to apply your plan’s limit and to email you before you reach it. To run and improve the service, our team sees usage only as totals across all workspaces — how many memories, which tools and assistants are used, how fast — with small groups folded together, so no person or workspace can be singled out.
  • If a public authority asks for your memories, we require valid legal process, and we tell you first unless the law forbids it.

Cloud memory is not end-to-end encrypted: our servers have to read the text in order to search it. For memories nobody else can read, keep them in the macOS app with sync off.

Workspaces and teams

A workspace is shared by design. Every member — Admin, Member, or Viewer — can read every memory in it, including memories captured by integrations, and Esment records which member wrote each one. Before you save something to a shared workspace, assume all its members will see it. The workspace’s owner decides who’s in it; when someone leaves, the memories they wrote stay in the workspace. If you join a workspace hosted on a teammate’s Mac, your memories sync with that Mac, not with us.

When a workspace is used for an organisation, the organisation decides what goes in it and who can see it, and we process its content on the organisation’s behalf, under our Data Processing Addendum.

Information about other people

Memories often mention other people — colleagues, clients, family — and Esment adds them to your knowledge graph so it can answer questions like “who knows about X”. You decide what’s saved, so only save information about others that you’re entitled to keep. If someone asks us about information about them in your memory, we’ll refer them to you, or to the workspace’s owner.

Sensitive information

Memories can hold sensitive information — about health, finances, beliefs, or relationships. Esment doesn’t need it to work, and we treat everything in your memory as confidential, whatever it contains. Esment isn’t designed for records governed by sector-specific rules, such as health records under HIPAA or payment card data; don’t store those in cloud memory unless we’ve signed an agreement that covers them.

Voice notes

A voice note recorded in the web dashboard is transcribed in your browser — the audio isn’t sent to any AI service. The recording is uploaded directly to our storage at Cloudflare, and the transcript is stored with your memories. You can delete the audio and keep the text, or delete the whole note; memories your assistant created from it stay until you delete them. We never use recordings to identify you by your voice.

Sync, integrations, and webhooks

  • Sync — off by default in the macOS app. When you turn it on, new memories on your Mac are sent to your cloud workspace and, if you also allow it, memories saved in the cloud are brought back to your Mac. Search data is recomputed on each side.
  • Integrations (Slack, Notion) — when you connect one, we keep its access token encrypted and read only the channels or databases you choose, from the day you choose them. Facts are extracted with your own OpenAI key, so that text is processed by OpenAI under your account; by default we keep the extracted facts, not the original messages. Disconnecting deletes the token; memories already captured stay until you delete them.
  • Webhooks — if you add one, we send the memory events you select to the address you give us.
  • Web access tunnel — if you turn it on in the macOS app, web assistants reach your Mac through Cloudflare’s network. That traffic doesn’t pass through our servers.

Keeping, exporting, and deleting

  • We keep your cloud memory for as long as your account exists. Cancelling a paid plan doesn’t delete it; your workspaces move to the free plan’s limits.
  • Export it anytime from Memories → Export pack, as a file the macOS app can import.
  • Deleting a memory removes it from search, and from everything assistants see, at once. Its text stays in the workspace’s change history — which is what lets you audit and undo changes — until the workspace is erased.
  • Deleting a workspace ends everyone’s access to it at once, and its memories, history, and voice notes are erased 30 days later.
  • To erase everything — memories, history, voice notes, and integration data — delete your account in Account → Privacy, or email privacy@notas.ai from your account’s address. We erase the workspaces you own within 30 days. Backups of the cloud database roll over every few days, so erased data leaves them within a further 7 days.
  • Memories you wrote in a workspace someone else owns belong to that workspace — ask its owner to delete them.

4. Third-party AI (your own keys)

Optional features like the dashboard assistant use your own API key for OpenAI, Anthropic, or OpenRouter. To answer, the assistant sends your message and the memories relevant to it to that provider, and it can save, edit, or delete memories when you ask it to; voice input is transcribed by OpenAI with your key. We relay the request but never store your key, prompts, or the AI’s response. Your data is then subject to that provider’s own policy.

5. Why we use it

  • Run the service and your account — contract.
  • Store, search, and sync your cloud memory, and run the integrations you connect — contract.
  • Take payment via Stripe — contract.
  • Prevent abuse and secure the service — legitimate interest.
  • Measure how the service is used, in aggregate — legitimate interest.
  • Improve the product and site — your consent.
  • Send you emails (sign-in, receipts, support, plan-limit notices) — contract.
  • Send product news and changelogs, each with a one-click unsubscribe — legitimate interest.
  • Meet legal and tax obligations — legal obligation.

6. Who we share it with

We never sell your data. We use these processors:

  • Render — hosting of the cloud memory service and of our account servers.
  • Vercel — hosting of this website and the web dashboard; dashboard requests pass through it on their way to the cloud memory service.
  • Cloudflare — encrypted backups of the cloud database, and voice note recordings.
  • OpenAI — embeddings for cloud memory search.
  • Voyage AI — relevance ranking for cloud memory search.
  • Stripe — payments.
  • Resend — transactional email.
  • PostHog — product analytics; cookies and session replay only with consent.
  • GitHub — app downloads.

We may also disclose data when the law requires it (see section 3), and to a successor if NotasAI is merged or acquired, which would remain bound by this policy.

7. Plugins and assistant integrations

Esment offers an official plugin and MCP connector that let compatible assistants (Claude Code, Claude Cowork, Claude Desktop, ChatGPT, and other MCP clients) retrieve context from and save memories to your Esment store on your behalf. When you use the plugin or connector, your assistant sends your queries to Esment and Esment returns the relevant memory content to that assistant.

  • What leaves your Esment store is decided by what your assistant requests — you control it by installing or disabling the plugin, and by what you ask the assistant.
  • The plugin connects to your local Esment store by default — memory content never touches our servers. If you use the cloud flavor, it connects to your own workspace, processed as described in section 3.
  • The assistant provider (for example, Anthropic for Claude, or OpenAI for ChatGPT) independently processes the retrieved content under its own privacy policy. We don’t control that processing — review your assistant’s policy before connecting it to your memory.

To stop sharing memory with an assistant, disable or remove the Esment plugin in that assistant’s settings.

8. International transfers

We’re based in the US, and cloud memory is hosted in the US. Where we transfer data out of the EEA, UK, or Switzerland, we rely on Standard Contractual Clauses or an equivalent safeguard.

9. How long we keep it

  • Account data — while your account is active, plus a short legal retention period.
  • Cloud memory — while your account exists, until you delete it; see section 3.
  • Billing records — as required by tax law.
  • Trial anti-abuse data — only as long as needed to prevent repeat abuse.
  • Unsubscribe list — if you opt out of our emails, we keep your address on it, even after you delete your account, so we never email you again.

Deleting your account deletes or anonymises your data, including your cloud memory as described in section 3, except where the law requires us to keep records.

10. Your rights

Export or delete your account data anytime from Account → Privacy, and export your memories from Memories → Export pack. You also have the right to access, correct, restrict, object to, or port your data, and to withdraw consent at any time. For a workspace run by an organisation, send requests about its content to the organisation; we’ll help it answer them.

California residents

We don’t sell or share your data for cross-context advertising. You have the right to know, access, delete, and correct your data without discrimination for exercising these rights.

To exercise any right, email privacy@notas.ai.

11. Cookies

We use necessary cookies to run the site, and analytics cookies only with your consent. See our Cookie Policy.

12. Security

  • Data is encrypted in transit to and from our servers, and at rest by our hosting and storage providers.
  • Integration tokens and AI keys you give us are encrypted again by us, with a key kept outside the database.
  • API keys are stored only as hashes and expire. Assistants sign in with OAuth 2.1, and every request is limited to one workspace and to its member’s role.
  • Passwords are hashed, and staff access follows least privilege.

No system is perfectly secure, but we take reasonable measures to protect your data. If a breach affects your personal data, we’ll tell you without undue delay, and notify the authorities where the law requires.

13. Children

Esment isn’t directed at children. We don’t knowingly collect data from anyone under 16.

14. Changes

We’ll update the date above when this policy changes, and notify you of material changes.

15. Contact

Questions? Email privacy@notas.ai.

EEA/UK residents can also lodge a complaint with their local data protection authority.