Skip to content

Trust

Privacy Policy

Nauro is local-first. The local store and retrieval path run on your machine and make zero external network calls. Your source code never leaves it. Only the project context you explicitly choose to sync is ever stored by us.

Last updated: 18 July 2026. This policy covers the Nauro command-line tool and core (the open-source software you install), the hosted sync service, and this website.

The short version

  • Run locally and nothing leaves your machine. The local store is plain Markdown on your own disk.
  • We never store your source code. Hosted sync carries decisions, project state, and open questions only.
  • Nauro sends no product analytics. Neither the command-line tool nor the hosted service emits product-usage events.
  • This website sets no third-party tracking cookies.

What stays on your machine

Your project context lives as plain UTF-8 files under your home directory (by default ~/.nauro/): Markdown decision files, current state, and open questions. You can read, edit, diff, version-control, and delete those files directly. The local credentials file is written with owner-only permissions. The core retrieval loop (lexical BM25, and the optional local embedding model) runs entirely on your machine with no external service and no API key.

What we collect

Product analytics. Nauro sends no product analytics. The 1.x nauro telemetry status, enable, disable, and reset commands are deprecated no-network, no-mutation compatibility shims. They report that product telemetry has retired and will be removed in 2.0. Legacy telemetry config is ignored and left untouched.

Hosted sync (only when you enable it). When you enable cloud sync, the hosted service stores the following, all in AWS in the United States (region us-east-1): your verified account email (from Auth0, used as your account identity), an opaque internal account identifier, your synced project context (decisions, project state, open questions, and the snapshots captured when you write, never your source code), project metadata and the membership record linking your account to its hosted project, and usage and rate-limit counters. A hosted project currently has one owner. Project context is configured to be encrypted at rest in AWS S3 using S3 server-side encryption, and access to each project is isolated by a fail-closed membership check: a request can read or write a project only if your account is recorded as a member of it. Sign-in is handled by Auth0.

This website. The marketing site sets no third-party tracking or advertising cookies. Your light or dark theme preference is stored locally in your browser and never sent to us.

What we never collect

Nauro does not send product-usage events, so decision titles, rationale, content, file paths, repository or project names, MCP tool arguments or return values, and source code are not collected as analytics. Project context leaves your machine only when you choose to sync it, and source code is never included.

Subprocessors

A small set of third parties process hosted data on our behalf. There is no payment processor in this list, and we do not collect payment-card data.

  • Amazon Web Services (United States, us-east-1). Storage and compute: S3 (encrypted project context), DynamoDB (account email, identifiers, project metadata, membership, and usage counters), Lambda (request processing), API Gateway (ingress and TLS), CloudWatch (operational logs), and Systems Manager Parameter Store (operator configuration).
  • Auth0, an Okta company (US tenant). Authentication and identity: runs your sign-in, issues your access token, and is the system of record for your login and verified email.

We do not sell or share your personal information, and we do not use your project context to train models. If we add or change a subprocessor that can access hosted customer data, we will update this list.

Where your data is stored

All hosted personal data and all synced project context is stored and processed in the United States, in AWS region us-east-1, and our authentication service uses a US tenant. There is no EU or UK data-residency option today. If you are in the EU, the UK, or another region with data-export rules, using the hosted service means your personal data is transferred to and stored in the United States. Contact us at [email protected] with questions about this transfer.

When you connect an AI tool (remote MCP)

The hosted service can act as a remote MCP server. When you connect it to an AI tool you choose, such as Claude AI, Perplexity, or another MCP client, your project context is read from our storage and delivered to that tool so it can answer with your decisions in view. Once your context reaches that tool, the tool's own data-handling policies govern what happens to it. We do not control or monitor what the AI tool does with your context after it is delivered, so please review the privacy policy of any AI tool before you connect it. Your source code is never read, stored, or delivered by this path.

Product analytics

The hosted service sends no product analytics. Usage and rate-limit counters, authorization checks, and AWS CloudWatch operational logs remain part of operating the service; they are not product-analytics events.

IP addresses and operational logs

Our application code does not read, log, or store your IP address. Your IP is seen transiently at the network edge by our hosting layer (AWS API Gateway and Lambda) to route your request and protect against abuse, in the ordinary way any internet service receives a connecting address. Our backend writes operational logs to AWS CloudWatch; these logs do not contain your project content, but they can contain your account identifiers and, on certain error paths, your email. These logs are not currently set to expire automatically.

Access, export, and deletion

Local data is yours outright: it is just files you can copy or remove. For data held by hosted sync, the format is the same plain Markdown, so export is straightforward, though there is no self-service export command today and we provide an archive on request. There is also no self-service deletion command in the hosted service at this time. To request access to, export of, or deletion of your hosted data, email [email protected] and we carry it out manually on request. Deleting your hosted data removes your synced project context (including its snapshot history) and your account and identity records; operational logs that may contain your identifiers are handled separately and may persist until their retention period elapses.

Changes and contact

We will update this policy as the hosted product changes. Questions or requests: [email protected]. See also our security practices.