Nuramem
Product Surfaces Projects FAQ Pricing Connect Log in

Legal

Nuramem Sub-processors


Effective date: September 1, 2026

Last updated: September 9, 2026

The service providers Nuramem uses to run the product, and what each one touches. This is the authoritative, versioned list referenced by Section 6 of our Privacy Policy.


The list

ProviderWhat it does for NuramemWhat reaches it
Google CloudHosting, databases, the short-lived cache of your self-model, encrypted backups, and our logs.Everything we hold: your memory records and copies derived from them, your account details, and our usage and security logs.
AnthropicRuns the models that turn what you capture into records, compress your records into your self-model, and write Nura's replies.The text you capture, the records being synthesized, what you type to Nura, and the parts of your memory relevant to a question Nura is answering. Identifiers are removed from captured mail before it reaches the models. Processed under Anthropic's commercial API terms: no training on your content, confidentiality and security obligations, held only briefly for the request and abuse-and-safety checks.
Google (Gemini API)Builds the search index behind semantic search.The text of records being indexed. Processed under Google's Gemini API commercial terms: no training on your content, confidentiality and security obligations, held only briefly for the request and abuse-and-safety checks.
Auth0 (Okta)Sign-in and identity.Your email address, your name if you give one, and your sign-in activity. No memory content.
GitHubSign-in, if you choose GitHub.Your GitHub account identifier and the profile data you allow. No memory content.
MicrosoftSign-in, if you choose Microsoft; and, if you connect Microsoft Teams, the service that carries those messages.Identity data for sign-in; for Teams, what you exchange with Nura there and what you capture from it.
ResendSends our outbound mail — project invitations, save receipts, and Nura's email replies — and receives the mail sent to your capture address.Your email address; receipts, which can quote your subject line and what was saved; and every message captured to your address as it arrived — attachments and addresses included — before the removal we do on the way into your memory. Resend keeps its own copy and offers no way to delete it. See how email capture works.
Amazon SESResend's inbound mail exchanger — it accepts mail addressed to your capture address and is the source of the spam and virus verdicts we act on.Every message sent to your capture address, before any of our checks run.
StripePayments, if you buy a paid plan.Your email address and an account identifier. Card details go straight to Stripe; we never see them. No memory content.
Expo, with Apple and GoogleDelivers mobile push notifications, if you turn them on.Your device's notification token and the notification text, which can include a due plan's title.
SlackIf you connect your Slack workspace, carries what you exchange with Nura there and what you capture. Separately, feedback you send us from any surface goes to our own Slack workspace.Your Slack messages to Nura and what you capture there; and the text of any feedback you send, with the account identifier it came from.

Model providers and training

We do not train AI models on your memory. Content we send them travels through their commercial APIs, and their own terms govern their side.


Where they process it

Every provider named here is a United States company, and the systems we run ourselves run in the United States — see Section 4 of the Privacy Policy. Our identity tenant sits in Auth0's US region.

If you're outside the United States, using Nuramem means your information is transferred here. Section 7 of the Privacy Policy describes the safeguards we rely on when personal data moves out of the EEA, UK, or Switzerland, and how to ask which apply to a particular provider.


How you learn about changes

This page is versioned: every change is recorded in the change log below, with its date, and we update this page before a new provider touches your data. When a change is material we also move the Privacy Policy's "Last updated" date and notify you by email or in the product.

We don't offer a right to block an individual provider — the ones listed here are how the Service runs. If you object to one, email privacy@nuramem.ai. You can also download your memory and delete your account at any time (Privacy Policy, Section 9).


Change log

  • 2026-09-09 — No provider added or removed. The Anthropic and Google rows now state the terms your content is processed under and what reaches them when Nura answers a question; the mobile app asks for your permission in-app before anything is sent (Privacy Policy 5.1).
  • 2026-09-01 — No provider added or removed. Recorded that identifiers are removed from captured mail before it reaches the model providers, and that our mail provider's copy is not covered.
  • 2026-08-31 — First standalone version of this page, superseding the inline list in Privacy Policy Section 6. Added Stripe, Expo with Apple and Google, Slack, and Amazon SES (Resend's inbound mail exchanger, present since email capture launched). Corrected Resend's scope to cover outbound mail as well as inbound, and Microsoft's to cover the Teams service as well as sign-in. Clarified Anthropic's scope: extraction and Nura's replies, not only synthesis. Removed the statement that Anthropic and Google are barred from training on your content — no executed term supports it. What we can say is above: we don't train models on your memory, and each provider's own API terms govern its side.

Questions: privacy@nuramem.ai

This page describes how Nuramem actually handles your information. It is not legal advice.

Nuramem · cross-model memory

Home Pricing Connect Privacy Terms Log in

© 2026 LeadHash LLC · Nuramem™