Noumento
How it’s used Privacy Security Docs Sign in
Request access

Privacy policy

Last updated: 14 October 2026

The short version

  • Noumento is for businesses. When a company uses Noumento, it decides what happens to the content of the tools it connects, and we process that content on its behalf.
  • We read only the tools each person connects and, where a tool offers a choice, only what they choose within it. Our connectors only read: they never post, send, edit or delete anything in those tools. If your company adds Noumento to its Slack workspace, we can also send you your weekly review as a Slack direct message, once you turn that on (section 3.8). Our security page lists the tools, exactly what we read from each, and what we send.
  • What Noumento learns from a person’s sources stays private to them until they choose to share it with their team.
  • We do not sell personal data, and we do not train AI models on it. Google, which runs the AI models we use, does not use it to train its models either.
  • Our servers are in Ireland. Some of our providers work outside the UK and EU, and we name them below.
  • Our website sets no cookies and runs no analytics or advertising trackers.

1. Who we are

Noumento is provided by Noumento Ltd, a company registered in England and Wales under number 17487720, with its registered office at 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ (“Noumento”, “we”, “us”).

For anything about this policy or your data, email privacy@noumento.com. We have not appointed a data protection officer.

2. Whose data this covers, and our role

Whose dataWhat it includesOur role
People who visit noumento.comNothing is collected (section 3.1)Not applicable
People who request accessThe request form’s detailsController
People who use Noumento: members and adminsEmail address, team, role, and a Slack user identifier if you connect SlackController
Content from the tools a customer connectsThe content of those tools, and what Noumento extracts from it, including about people who never use NoumentoProcessor, for the customer

Where we are a processor, the customer is the controller. That is usually your employer, and it decides how its content is used. Our data processing terms with the customer govern what we may do with it.

Your data may have reached Noumento through a customer’s tools, for example because you wrote to someone at a company that uses Noumento. If so, contact that company first, and we will help it respond. This policy still explains what happens to that data.

3. What we collect and why

3.1 Visiting our website. The site sets no cookies and runs no analytics or advertising trackers, and our web server keeps no log of visits.

3.2 Requesting access. The form asks for:

  • your name and work email address
  • your company and team size
  • the tools you would like to connect
  • the AI assistant you use
  • any note you add

We also keep a scrambled (hashed) form of your network address to limit spam. We use this to review your request and to reply. Someone at Noumento reads every request. Legal basis: our legitimate interest in responding to businesses that ask to use Noumento.

3.3 Using Noumento. Once your team is approved, or an admin invites you, we hold:

  • your email address
  • the team you belong to, and your role
  • if you connect Slack, your Slack user identifier; and if you use the weekly review in Slack, your choice (section 3.8)

We do not store your name with your account, though an access request keeps the name given on it. WorkOS handles sign-in for us: with Google, or with an email address and password, and it may hold your name. WorkOS also sends our invitation emails. The app uses two cookies, both needed for it to work, and page scripts cannot read either: one keeps you signed in, for up to 30 days, and one lasts 10 minutes to protect the sign-in step. The sign-in page is run by WorkOS and may set its own cookies needed for signing in. Legal basis: our legitimate interest in providing, securely, the service your organisation signed up for.

3.4 Connecting your tools. Each person chooses which tools to connect, and nothing is connected for them. When you connect one, we keep the access credential it issues in AWS Secrets Manager. We read every tool the same way:

  • We connect with your own access, so we see only what you can already see.
  • Where a tool lets you choose what we read, such as Slack and Teams channels, mail folders, Notion pages or Granola folders, we read only what you choose. From Granola we keep meeting transcripts, not Granola’s AI summaries or private notes.
  • Our connectors only read: they never post, send, edit or delete anything in your tools.
  • We do not download attachments or files. A message’s own record of an attachment, such as its name, is kept with the message.

Our security page lists the tools Noumento connects to, and exactly what it reads from each. Disconnecting a tool stops us reading it and deletes the credential, unless another of your connections still uses it.

This content contains personal data about you and others: colleagues, and people outside your company, such as people who write to you. We process it for the customer, under our data processing terms, to build the record described next.

3.5 What Noumento does with that content.

  • It extracts decisions, owners, open questions, commitments and other facts, and indexes them so your AI assistant can find them.
  • Everything it learns starts in your private record. Only you, and the assistants you connect, can reach it in Noumento. If you turn on the weekly review in Slack, we also send you the wording of what is waiting, in Slack (section 3.8).
  • It reaches your team’s shared record only when you approve it, or when you have chosen to share automatically from the channel, folder or Notion area it came from. You can take back something you shared; your team then stops seeing it, unless a teammate shared it too.
  • It checks content for five kinds of sensitive matter: judgements about named people, pay, the company’s own deals and fundraising, legal matters about a person, and personal lives. Flagged content is never shared with the team. When the check is unsure, the content is treated as sensitive. When the check cannot run, the content is held back, unprocessed and unshared, and checked again later; if it still cannot be checked after about three days, it is set aside and never processed.
  • When your assistant asks a question, Noumento answers from your private record and your team’s shared record, and nothing else. The answer goes to the assistant you connected, such as Claude or ChatGPT, under that assistant provider’s own terms.

3.6 Running and protecting the service. We record operational data, such as errors and timings, in Pydantic Logfire in the EU, with identifiers disguised. We keep a record of important actions, such as sharing decisions and changes to connections, so we can keep the service secure and show what happened. Where you edited a fact before sharing it, that record keeps your edited text. Our servers keep technical logs to fix faults and keep the service secure. They hold identifiers, not the content of your tools, and most are deleted each time we update the service. Legal basis: our legitimate interest in running a secure, reliable service.

3.7 Contacting us. If you email us, or send us a message from the Help page in the app, we keep your message and our reply so we can deal with your question. A message from the app reaches us by email, with the topic you chose, your email address (if your account has one), your team’s name, your role, the app page you came from (if any) and the identifiers we use to find your account. We keep it as we keep any other email. Our email is hosted by Google.

3.8 The weekly review in Slack. An admin can add Noumento to your company’s Slack workspace. Adding it gives Noumento permission to send messages there; Noumento uses it only for direct messages. It gives no permission to read messages. If you have connected Slack, you can then choose to get your weekly review in Slack. When you do, we send you your weekly review by direct message, at most once a week, listing what is waiting for your decision. We also send you a message to confirm when you turn it on, and reply in Slack when you press one of its buttons. The review includes the wording of things that are still private to you. Slack then holds that message under your company’s own agreement with Slack. To send it we keep the workspace’s access credential in AWS Secrets Manager, the workspace’s name and identifier, your Slack user identifier, and whether you have the review on. You can turn it off at any time. When an admin removes Noumento from Slack we delete the credential, and we keep your choice in case it is added again. We do not answer questions in Slack.

4. How we use AI

  • Google’s Gemini models process the text Noumento reads, through Google’s Gemini API, to extract, check and index it. They also process the questions your assistant asks and the notes it saves to Noumento. Google does not use any of it to train its models. Google keeps it for up to 55 days, only to detect and prevent misuse of its service.
  • We do not train AI models on your data.
  • The sensitivity check is automated. It decides what may be shared with a team, and nothing about you that has a legal or similarly significant effect.
  • AI can be wrong. Noumento’s record may miss things or get them wrong, which is why every answer shows its sources.

5. Who we share data with

We do not sell personal data. These providers process it for us:

ProviderWhat it does for usWhere
Amazon Web ServicesHosting: servers, database, file storage, credential storageIreland (EU)
GoogleGemini AI models; our emailAny country where Google has facilities, including outside the UK and EU
WorkOSSign-in and invitation emailsUnited States
Pydantic (Logfire)Operational monitoring, with identifiers disguisedEU (Netherlands)

We may also share data:

  • with the AI assistant you choose to connect, which receives the answers to your questions
  • with Slack, when you choose to get your weekly review there: the review is sent to you in your company’s Slack workspace
  • where the law requires it, or to protect our rights or someone’s safety
  • with a buyer or successor if Noumento is sold or merged; this policy would continue to apply to your data

6. Transfers outside the UK and EU

Our servers are in Ireland. Where a provider processes data outside the UK and EU, we rely on these safeguards: for Google, its participation in the EU-US Data Privacy Framework and its UK Extension; for WorkOS and Pydantic, the UK International Data Transfer Addendum to the EU Standard Contractual Clauses, in their data processing agreements. Email us for a copy of the safeguards.

7. How long we keep data

DataHow long we keep it
An access requestUntil it is decided. If rejected, deleted within 12 months. If approved, kept while your organisation’s account is open, then deleted with everything else.
Account detailsWhile your organisation’s account is open, then deleted within 30 days of it ending
Content from connected tools, and the record built from itWhile your organisation’s account is open. Deleted within 30 days of your organisation asking, or of its account ending
A connection credentialUntil you disconnect the source, unless another of your connections still uses it
The Slack workspace credentialUntil Noumento is removed from the Slack workspace
Your Slack user identifierUntil you disconnect Slack
Your choice to get the weekly review in SlackWhile your organisation’s account is open
BackupsMade daily; each one kept for 14 days
Operational monitoring30 days
The record of important actionsWhile your organisation’s account is open. Deleted with everything else, within 30 days of your organisation asking, or of its account ending

An organisation’s account ends when its subscription ends, or 30 days after a trial ends without a move to a paid plan. After a trial ends, nothing new is collected from connected tools, and the team can still ask about what is already there until the account ends.

If a member leaves, what they shared stays in the team’s record, and their private record stays until the customer asks us to delete it.

8. How we protect data

Our security page sets out the detail, including:

  • encryption of stored data and of data in transit
  • connection credentials kept in AWS Secrets Manager
  • access to production systems limited to Noumento’s founder, with two-factor sign-in
  • private records by default
  • a permission check on every answer

9. Your rights

Under UK data protection law you can ask us to:

  • give you a copy of your data
  • correct it
  • delete it
  • restrict or object to how we use it
  • send it to you, or to someone else, in a portable form

Email privacy@noumento.com and we will reply within one month. If your data reached us through a customer’s tools, we will pass your request to that customer and help it respond. Inside Noumento, members can see what their record holds and take back what they shared.

You can also complain to the Information Commissioner’s Office (ico.org.uk). We would like the chance to help first.

10. Children

Noumento is for work, for people aged 18 and over. We do not knowingly collect children’s data.

11. Changes to this policy

We post changes here with a new date. If a change is significant, we will email customers’ admins at least 30 days before it takes effect.

12. Contact

privacy@noumento.com, or by post to Noumento Ltd, 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ.

Noumento Security and privacy Privacy policy Terms Docs FAQ Support
  • Noumento Ltd, registered in England and Wales
  • Company number 17487720
  • Registered office: 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ
  • Contact: hello@noumento.com