Skip to content
DocsGet Noema

Trust

Trust and security

How the Noema app and Noema Teams handle data, where the keys live, the security practices we follow, and how to report a vulnerability.

Architecture

Where data goes.

The personal app runs on your device and needs no Noema account. Noema Teams adds a company connector you run and a Noema service that never holds your keys.

The Noema app

Local models, documents, indexes and conversations can stay on your device. Each optional feature contacts only its own destination.

Noema app data paths by feature
FeatureDestinationWhat may be sent
Local models and RAGYour deviceNothing leaves for generation or local retrieval.
Local Python, Memory, Calculator, Converter, ChartsYour deviceTool inputs and results remain local; Python has no network access.
DownloadsSelected model, dataset, or voice sourceAsset identifier and normal connection metadata.
Web Search / Deep ResearchSelected search service and source readerQueries, locale, controls, candidate URLs or snippets, source references, and open/find parameters; a remote report-writing model also receives the relevant findings.
MCP connectorsServer you configureApproved tool-call arguments and returned results. Remote connectors use the network even with a local chat model.
Remote ControlThe Mac that owns the coding chatMessages, activity, eligible approval choices, and replies over end-to-end encrypted Constellation connections. Folder paths and filesystem grants stay on the owner Mac.
Local APIYour Noema host and configured clientsAuthenticated model requests and replies. The displayed listener can use HTTP on a trusted local network; do not assume Constellation encryption applies to this separate API.
Remote endpointConfigured providerPrompt, relevant chat and system context, supported attachments, tools and results, and retrieved excerpts.
Autopilot remote routerConfigured routerEach evaluated message, limited routing context, and capability information.
Autopilot escalationConfigured stronger modelPrompt and context needed for the answer; knowledge excerpts only when explicitly allowed.
Constellation chat syncPrivate iCloud databaseChat and project payloads; models, datasets, and source files remain device-local.
Constellation Local NetworkYour Mac on the local networkAuthenticated request, supported attachments, tool exchanges, and streamed response.
Constellation Private LinkYour configured private meshRequest, supported attachments, tool exchanges, and streamed response.
Constellation DirectThe other personal deviceEnd-to-end encrypted device-to-device request after CloudKit introduction.
Noema BridgeNoema-operated bridgeEnd-to-end encrypted traffic relayed as ciphertext; the Bridge does not run the model.
Constellation Cloud RelayPrivate iCloud database and your MacRequest, optional bounded image assets, tool exchanges, and reply.
Apple SpeechApple speech-recognition systemAudio may be processed by Apple when on-device recognition is unavailable or not required.
Local WhisperYour deviceAudio and transcripts remain local after download.
Remote audio modelConfigured providerMedia required for transcription.
CalendarDevice Calendar storeReads and confirmed writes use OS calendar permissions.
Enterprise enrollmentOrganization serviceEnrollment credentials, policy state, catalogs, and managed dataset requests.

From Privacy & Network Activity, reviewed October 17, 2026. Off-grid Mode blocks external HTTP and HTTPS traffic initiated through Noema's network stack.

Noema Teams

Devices decrypt and infer locally. Your company connector holds sources, keys and policy signing. The Noema service handles accounts, audit records and encrypted delivery, and holds no keys.

Plaintext content and keys stay on this side

Zone 1

Your devices

Employee iPhone, iPad or Mac running Noema 4.2 or later

  • Verifies the customer-signed device policy
  • Decrypts approved datasets locally
  • Retrieves and generates on the device
  • Enforces approved datasets, tools, models, endpoints and the offline lease

Uses independently approved device keys

Zone 2

Your company connector

Runs in your environment, under your control

  • Keeps original documents and private indexes
  • Signs device policy and approves or revokes content-access devices
  • Answers direct retrieval from approved devices
  • Integrates configured OIDC and SCIM

Holds your signing and decryption keys

Ciphertext only

Zone 3

Noema service

Operated by NoemaAI

  • Workspace accounts, billing and console roles
  • Device-delivery registrations and audit records
  • Stores and delivers customer-encrypted artifacts

Holds no customer signing or decryption keys

  1. Company connector → DevicesCustomer-signed policy, device approval and direct retrieval of authorized passages.
  2. Your publisher → Noema serviceDatasets encrypted before upload. Noema stores ciphertext without decryption keys.
  3. Noema service → DevicesCiphertext delivered to approved devices, which decrypt and run inference locally.
  4. Devices → Approved endpointRemote inference only to an endpoint your company approves. Off-grid policy blocks it.
The Noema Teams boundary. Employee workflows require Noema 4.2 or later on iPhone, iPad or Mac.

Data handling

By product.

  • Noema app

    Personal use
    Where content is processed
    On your device by default. Optional features send data only to the destination you choose.
    Account
    None for ordinary personal local use.
    What NoemaAI receives
    Nothing for local generation or local retrieval. Built-in Noema Search receives search queries, and Noema’s source reader the sources it opens. Noema Bridge relays end-to-end encrypted traffic as ciphertext. Support requests you choose to send.
    Analytics
    No analytics or advertising trackers in the app or on this website.
    Privacy Policy

  • Noema Teams

    Available
    Where content is processed
    Approved devices decrypt and infer locally. Direct retrieval goes to your company connector; remote inference only to an endpoint your company approves.
    What NoemaAI holds
    Workspace accounts, billing, console roles, device-delivery registrations, audit records and encrypted artifacts.
    Keys
    Noema does not hold the customer signing or decryption keys.
    Console records
    Administrative actions such as invites, role changes and device registrations. Employees’ local prompts and answers are not sent to the console.
    Noema Teams

  • Custom model pilots

    Pilot
    What is processed
    Only data you explicitly approve, in the training environment agreed for the engagement.
    Retention
    Access, retention and deletion of files, checkpoints and logs are set in advance.
    Other use
    Client data is not used for unrelated models or other customers without explicit permission.
    Before training
    Access to an adapted model is defined first, because a model can retain what it was trained on.
    Custom model pilots

Security practices

What we do today.

We list only practices that are in place today and described in our product documentation.

  • A named security lead

    Armin Stamate, Founder & CEO, leads security as a one-person function within Engineering and is accountable for security decisions, product security review, access to development systems and coordinating responses to reported issues.

  • Keys stay with the customer

    In Noema Teams, datasets are encrypted before upload and only approved recipient devices can decrypt them. Noema stores ciphertext and does not hold customer signing or decryption keys.

  • Policy enforced on the device

    The app verifies the customer signature on each device policy and checks it where tools and inference run. An expired lease or a device reboot locks protected access until a fresh policy is obtained.

  • Verified enrollment and revocation

    Workspace enrollment uses verified email and DNS domain ownership. Customer administrators approve and revoke content-access devices separately from console roles.

  • Off-grid Mode

    The app can block external HTTP and HTTPS traffic initiated through its network stack, while local generation, retrieval and tools keep working.

  • Careful diagnostics

    Diagnostic exports are designed to exclude chat transcripts and document contents and to redact common secrets. We still ask you to review every export before sending it.

  • Encrypted device-to-device paths

    Constellation can use end-to-end encrypted Direct or Noema Bridge transport between your own devices. Noema Bridge forwards ciphertext and does not run the model.

  • Public source for review

    A community source edition of the Noema Apple client is public on GitHub for learning, experimentation and security review.

Vulnerability disclosure

Report a vulnerability.

Email our security lead at armin@noemaai.com. Please do not open a public issue or post details publicly for a suspected vulnerability or exposed credential.

Armin Stamate coordinates the response to each report. Please avoid accessing other people's data or disrupting services while you investigate, and give us a chance to fix the issue before you publish details.

Email a reportSecurity contact

For the community source edition on GitHub, you can also use GitHub private vulnerability reporting. Machine-readable contact details are at /.well-known/security.txt.

Include in your report

  • The affected product or service, and its version or build
  • What an attacker could do (the impact)
  • Steps to reproduce the issue
  • Any mitigation you would suggest
  • No passwords, private keys or personal data

Documents

Related policies.

Privacy requests and legal questions go to clientcare@noemaai.com.