All resources
HelpENMay 30, 2026

Notra Security, Privacy, and AI Data Principles

A practical explanation of how Notra approaches workspace privacy, admin access, public content, and responsible AI context handling.

#security#privacy#ai-data#trust

Security starts with product boundaries

Notra is designed around authenticated workspaces, admin-only operational areas, and clear separation between private app surfaces and public pages.

That means public marketing and resource pages can be indexed, while app, admin, billing, review, and private workspace routes should stay protected or noindexed.

AI should use context carefully

AI features are most useful when they understand the user's current work. They are also most responsible when context is limited to what is needed for the request.

In practice, this means AI workflows should:

  • Use the active workspace context intentionally
  • Avoid sending unnecessary data
  • Keep file sizes and prompt payloads bounded
  • Handle errors without exposing sensitive details
  • Respect user access rules before reading workspace material

Admin areas need stronger gates

Operational tools can affect users, billing, support, content, and moderation. For that reason, admin surfaces should require authenticated admin access and a second verification step before sensitive work continues.

Public content should be safe by default

Blog and help pages are public. They should never include private customer data, internal secrets, access tokens, or screenshots that reveal sensitive workspace information.

Before publishing a resource article, check:

  • Does it contain private data?
  • Does it reveal internal credentials or keys?
  • Does it make claims the product cannot support yet?
  • Does it explain user data handling clearly?

Account and data rights matter

Users should be able to understand how support, privacy, terms, AI data processing, permissions, and account deletion work. Those pages are part of trust, not legal decoration.

The publishing mindset

Every public resource should be useful, accurate, and careful. Good content helps users move faster. Careful content helps them trust the product while they do it.

Recommended next reads

Try it in Notra

Before publishing or sharing a workspace artifact, review the context you included, remove anything unnecessary, and keep the final output useful without exposing private information.