Your data. Your orbit.

This privacy policy explains how Neptune at neptune.org handles information when you sign in and use its family office workspace.

Effective and last updated: October 9, 2026.

Information we collect

Neptune processes your account identity, email address and display name, workspace membership, role and entity permissions. When you create or import office records, we store the information you choose to provide: entities and ownership, investments, balances, obligations, beneficiary details, tasks, goals, approvals, accounting records, source documents and related audit events. Office setup also stores your preferences, objectives and selected source systems.

Our hosting and authentication providers process connection and request information to deliver and secure the service. Browser cookies maintain your authenticated session. Temporary tab storage carries your sign-in destination and invitation context; it is checked for expiry after 15 minutes. Google sign-in credentials are never placed in that invitation context.

Google sign-in data

If you choose Google, Neptune requests only the openid, email and profile permissions. Google supplies an account identifier, email address, verification status and basic profile information such as your name and profile picture. Managed Neon Auth processes this identity information and the OAuth credentials needed for sign-in. Neptune uses it to authenticate you, identify your account and check access to your workspace and invitations. We do not receive your Google password.

Signing in with Google does not grant Neptune access to Gmail, Google Drive, Calendar, contacts or other Google Workspace content. An existing email account is connected to Google only through an explicit account-linking confirmation. Email sign-in works separately. We do not sell Google sign-in data, use it for advertising or credit decisions, or use it to train general-purpose AI or machine-learning models.

How we use your information

We use account information to provide authentication, recovery and access control. We use the records your office supplies to display its permitted information, support imports and exports, coordinate responsibilities, preserve evidence and approvals, and record the office’s accounting and audit history. We use request information to diagnose failures, enforce limits and protect the service. Your permission to access a source system must be established separately; a Neptune agent token does not create access to another vendor.

Who processes or receives data

Vercel hosts Neptune and processes application requests. Neon provides managed authentication and the Postgres database that stores accounts and office data. Google processes the sign-in flow when you choose Google. Members of your office can see information permitted by their current roles and entity scope. Owners control invitations and scoped agent access. Exporting a file or giving an agent access shares the selected information with the recipient you choose.

OpenRouter and the model provider selected for a request process the context you explicitly authorize for AI analysis or document extraction. These providers operate outside Neptune. Their own privacy policies and processing terms also apply. Neptune does not sell account or office data or share it for targeted advertising.

Your choice about AI processing

Each office analysis request requires confirmation before Neptune sends permitted record context to OpenRouter. General analysis excludes bank beneficiary details and original file bytes. Document extraction requires separate consent to process the selected document’s content. Google OAuth credentials are not included in AI requests. Neptune requests provider routes that disallow prompt collection for training; this routing setting is not a guarantee of every external provider’s retention practices. Review the selected provider before sharing sensitive records.

Storage and protection

Neptune uses HTTPS and server-side membership and entity checks. Original evidence files are encrypted with AES-256-GCM before storage in Postgres, with the encryption key held in server-side runtime configuration. This document encryption does not mean that every account or structured office field is encrypted with that same key. Agent import tokens are scoped, expire after seven days and can be revoked. No system can promise absolute security. Further technical controls and current limitations are described in our trust and security guide.

Retention and deletion

Account identity is retained to support your account and access history. Workspace records do not have an automatic expiry in this release. Authorized users can remove draft records; related audit events remain. Original evidence and posted financial history are retained for office continuity and cannot be deleted through ordinary record controls. Removing a member or revoking an agent stops future access but does not erase records already supplied to the office or exported to another recipient.

To request account or data deletion, contact us using the address below. Requests require identity and authority checks, especially for records shared with an office. We will explain which data can be removed and any retention needed for the shared office’s records or applicable obligations. Account deletion is handled by request; Neptune does not currently offer an automatic account-deletion button. Copies in provider backups and exports may follow separate retention processes.

Your controls and contact

Office owners can manage members and revoke agent tokens in Team & access, export permitted workspace data and retrieve original documents. You can decline AI processing and use the record workflows without sending that context to a model. You can also revoke Google authorization in your Google Account’s third-party connections; revoking Google access does not by itself delete your Neptune account or shared office records.

For privacy questions, corrections, access or deletion requests, contact Neptune at jacksonjezio@gmail.com. Please describe the request without sending passwords, access tokens or sensitive office files by email.

Changes to this policy

We will update this page and its date when Neptune’s handling of data changes. Material changes to Google data access or AI processing will be reflected in the relevant in-product notices and permissions before that new processing begins.