Security you can evaluate — not just take on faith.
This page describes how Imaginne handles identity, credentials, execution and data. It exists so your security team can start an assessment without needing a sales meeting first.
Identity and sessions
OIDC with PKCE
Each organization authenticates with its own identity (single sign-on). Web and desktop use the authorization flow with PKCE; terminal clients use the device-code flow (RFC 8628). Imaginne stores no password of its own.
Per-device sessions
Sessions are issued per client instance, with opaque tokens. Revoking one device doesn't kill the others.
Roles and profiles
What each person can use — integrations, skills, agents, models — comes from roles and profiles administered by the organization.
Credentials and secrets
Per-organization vault
Integration secrets (API keys, database passwords, SSH keys) live in an organization-scoped vault, encrypted at rest.
Injection at execution only
Credentials are resolved by the platform at execution time, scoped per step — they never pass through the conversation and are never available to the model beyond what the step requires.
Referential integrity
A secret referenced by a skill or agent cannot be deleted; publishing fails if a secret declaration is unbound.
Protected memory
Automatic memory goes through filters that keep secrets and credentials from being persisted.
Isolated execution
Kernel-isolated sandbox
Code and analysis run in environments with gVisor (an application kernel), read-only root filesystem and an ephemeral workspace per run.
Controlled egress
Network egress from execution environments is policy-restricted; what the task doesn't need to reach, it can't reach.
Disposable by default
When the run ends, the environment ends. Nothing persists in the execution environment between tasks.
Data and access
Delegated identity
Corporate data queries run with the user's own identity, via OIDC token exchange. The access control that applies is your database's — Imaginne is not a superuser.
Fail-closed gating
Integrations and capabilities only load when active for the organization, the user and the surface. Without explicit permission, the tool doesn't exist for the model.
Content boundaries
Sensitive identifiers are handled at content boundaries with source-scoped redaction rules.
Durable artifacts
Files delivered in conversations go to the organization's durable storage — not to ephemeral container paths.
Models
Single gateway
All model access goes through a platform gateway that abstracts the provider and applies the organization's rules.
BYOK
Organizations can use their own model keys, organization-scoped, assigned per user or profile.
Distribution and updates
Signed releases
The client update manifest is signed (Ed25519) and publishes version, size and SHA-256 — the same source the downloads page displays.
Native builds
The macOS app is signed and notarized by Apple; Windows ships as an MSI.
Audit and observability
Policy decisions recorded
Access decisions and execution events are recorded for the organization's audit.
Execution history
Runs, artifacts and usage remain traceable per organization.
This page describes the product as it is today, operated as a managed service by NNumbers. It is updated together with the product — the changelog tracks the evolution. Changelog
Vulnerability reports
Found something? Contact NNumbers through the official channels and we will prioritize it. We ask for responsible disclosure.