Privacy Policy

1. Who is responsible

Navigator is operated by Brian Lambert, who is the controller of the personal data described here. Contact:brian@digitalcommand.co.

Where your organization provides the service to you, that organization is the controller of the content in its workspace and we act as its processor. Its own privacy notice governs how it decides to use that content.

2. What we collect

Account data. Your email address, an account identifier issued by Google Identity Platform, authentication timestamps, and the tenant and profile you belong to. We do not receive or store your password; authentication is handled by Google Identity Platform.

Content you submit. Chat messages, uploaded documents (PDF, TXT, MD, DOCX, HTML, CSV, JSON), audio you send for transcription, files pulled from sources you connect such as Google Drive, and material derived from these: extracted text, transcripts, chunk metadata, and vector embeddings used for retrieval.

Usage and technical data. Request logs including timestamp, route, response status, correlation identifier, and coarse error detail; the IP address your request arrives from; and browser-reported information such as user agent.

Local browser storage. Your session token, theme preference, and — during a magic-link sign-in — the email address you entered. These are held in your browser, not on our servers.

We do not deliberately collect special-category data. Please do not put it into prompts or uploads unless your organization has established a lawful basis for doing so.

3. Why we use it, and on what basis

• To provide the service — authenticate you, run conversations, index and retrieve your documents, and keep your history. Basis: performance of a contract.
• To keep it secure and working — logging, debugging, abuse prevention, and capacity management. Basis: legitimate interests in a secure, reliable service.
• To communicate with you — service notices, security alerts, and replies to your requests. Basis: legitimate interests, or contract.
• To meet legal obligations — responding to lawful requests and keeping required records. Basis: legal obligation.

We do not use your content to train foundation models, we do not sell personal data, and we do not share it for cross-context behavioural advertising.

4. Who processes it for us

We use a small set of subprocessors, each under contract and each limited to the purpose below:

• Google Cloud Platform — application hosting, Cloud SQL (PostgreSQL) for accounts, chats, and document metadata, and Cloud Storage for uploaded files.
• Google Vertex AI — model inference, embeddings, and audio transcription. Prompts and relevant document excerpts are sent for processing.
• Google Identity Platform — authentication, password handling, magic links, and password resets.
• Google Drive API — only where you connect a Drive source, to read the files you select.
• Firecrawl — where public-web retrieval is enabled, to fetch pages relevant to your query. Your search terms are sent; your documents are not.

We will also disclose data where we are legally required to, or to establish or defend legal claims.

5. Where data is held

Data is processed in Google Cloud regions in the United States. If you are in the United Kingdom, the European Economic Area, or Switzerland, transfers out of your region rely on the European Commission’s Standard Contractual Clauses together with the additional safeguards our providers commit to.

6. How long we keep it

• Account data — for as long as the account is open, then deleted within 30 days of closure.
• Chats, documents, and embeddings — until you or your administrator delete them, or the workspace is closed, then removed from backups on the normal backup cycle.
• Request logs — retained for a limited operational period and then rotated out.

Deleted items may persist briefly in encrypted backups before those backups expire.

7. Security

Traffic is encrypted in transit with TLS, and data at rest is encrypted by our cloud provider. Access is gated by authenticated sessions and scoped to your tenant. Internal access is limited to what is needed to run and support the service. No system is perfectly secure; if a breach affects your data we will notify you and any regulator as the law requires.

8. Your rights

Depending on where you live, you may have the right to access your data, correct it, delete it, receive a portable copy, restrict or object to certain processing, and withdraw consent where we rely on it. UK and EEA residents may complain to their supervisory authority. California residents may exercise rights under the CCPA/CPRA, including the right to know, delete, correct, and not be discriminated against for exercising them.

Write to brian@digitalcommand.coand we will respond within the period the applicable law allows. If your workspace is administered by your organization we may need to route your request through them.

9. Cookies and similar technologies

We do not use advertising or analytics cookies. We use browser storage strictly to keep you signed in and to remember your theme preference, which is why no consent banner is shown.

10. Children

The service is for professional use and is not directed at anyone under 18. We do not knowingly collect data from children; if you believe we have, contact us and we will delete it.

11. Automated processing

The service generates responses using a language model. It does not make automated decisions producing legal or similarly significant effects about you. Model output is informational and should be checked before you act on it, as set out in ourTerms of Service.

12. Changes

We may update this policy. Material changes will be notified by email or in the service before they take effect, and the date at the top of this page will change.