NEPTUNE SIGNET / TRUST & PRIVACY

Intelligence with
clear boundaries.

An agent is useful only when its authority is clear. These are the controls implemented in this release, and the limits that remain.

Read the Neptune privacy policy for account and Google sign-in data, service providers, retention and your data choices.

Private by workspace

Managed Neon Auth establishes identity. Every data-bearing request checks current workspace membership on the server. Owners can give approvers, operators, advisors and auditors access to selected entities. Advisors and auditors have read-only access. Invitations expire after seven days and require a matching verified email.

Evidence protection

Original documents are encrypted with AES-256-GCM before they are saved in Postgres. The encryption key is held in server-side runtime configuration. Downloads require current membership and entity permissions. A SHA-256 fingerprint supports duplicate detection and original-file integrity. Documents and posted journals are immutable in the product.

AI context and provider privacy

Neptune uses OpenRouter. A user explicitly confirms each analysis request before permitted record context is sent. Bank beneficiary details and original file bytes are excluded from general office analysis. Document extraction requires separate consent. Neptune requests providers that do not collect prompts for training. Provider processing still occurs outside Neptune; review your organization’s requirements before sharing sensitive information.

Human financial authority

Agents cannot approve payments or record settlement. A human owner or approver must approve a proposal with source evidence, a verified beneficiary and an entity-specific funding account. Editing the proposal invalidates its approvals. Neptune prepares an exportable packet. Your bank executes the transfer. Human-reported submission and evidence-backed settlement are different states.

Temporary agent access

Owners can issue scoped import tokens that expire after seven days and revoke them immediately. Every request also checks the token issuer’s current membership. A token never grants permission inside another vendor’s system, and cannot bypass human approval.

Audit and portability

Workspace events form a hash-linked audit chain. This makes accidental or application-level history changes detectable; it is not an independently notarized or externally immutable log. Owners can export their permitted workspace data and retrieve original documents. Concurrent updates are rejected rather than silently overwriting another person’s work.

Deployment and readiness limits

This release uses Vercel, Neon and OpenRouter. Neptune has not completed an independent security audit or claimed SOC 2 certification. Enterprise SSO, independent audit anchoring, institution-specific bank integrations and jurisdiction-specific compliance controls require further implementation and review before they can be represented as available.

Data control

Your office controls what it imports, who receives access and which context is sent for AI analysis. Remove draft records through the workspace; revoke access through Team & access. Original evidence and posted financial history are retained for continuity and cannot be removed through ordinary record deletion. Do not upload records unless you have permission to use and process them.