Privacy policy

Account and Google sign-in

When you create an account, we use your email address and account identifier to sign you in, manage access and associate your settings, API keys, usage and billing with you. Authentication is handled by Amazon Cognito.

If you choose Google sign-in, Google supplies basic identity information, including your name, email address, email verification status and Google account identifier. Cognito stores the mapped profile information; deep.navy uses it to authenticate you and maintain your account. The sign-in permissions we request are limited to basic profile, email and OpenID identity. They do not grant access to your Gmail messages, Drive files or contacts.

Tool requests and stored content

We process the queries, URLs, filters and other arguments you or your connected client send to our tools so we can return results. Web fetches can store retrieved pages and their versions for caching, history and comparison. Search queries and indexed text may be processed through Amazon Bedrock to generate embeddings used for search.

Monitors store their queries, settings, webhook destinations and run history. Results and delivery metadata are sent to the webhook destination you configure. Your MCP client receives the tool results you request and handles them under its own policies. Avoid sending secrets or private material in queries, URLs or webhook destinations.

We also index public sources, including news, public filings and public profile pages. Public profile results may contain names, roles, organizations and source links. See our people search documentation for source and removal information.

Usage, billing and service operation

We record account and tool usage, request timing, errors and technical logs to operate the service, troubleshoot problems, protect access and calculate billing. Usage records associate calls and monitor deliveries with your customer account. Our hosting and network providers also process connection information when serving requests.

Billing uses Lago and Stripe. We process customer identifiers, email, plans, usage, invoices and payment-method references. When you add a card, Stripe collects the card details through its payment interface; deep.navy displays limited payment-method details such as card brand, last four digits and expiry.

Our website uses browser storage and cookies for sign-in sessions and interface preferences. Clearing that storage can sign you out or reset those preferences.

Where information is processed

We use Amazon Web Services for authentication, application hosting, storage, search and related processing, and GitHub Pages to serve the website. Google participates when you select Google sign-in; Stripe processes payments, and our Lago billing system tracks usage and invoices. These services process the information needed for their roles. Requests to source websites and webhook receivers disclose the request information needed to fetch content or deliver results.

Authorized operators can access account, billing and operational information to administer the service and respond to support requests. Information may also be disclosed where required by applicable law or to address abuse or security incidents.

Your choices and privacy requests

You can revoke API keys and pause or delete monitors in the dashboard. You can also remove deep.navy access in your Google Account settings. Revoking Google access does not itself delete your deep.navy account or existing records.

For account access, correction or deletion requests, or requests about an indexed public profile, contact privacy@deep.navy. Include enough information to identify the account or source page; do not send passwords or API keys. We may need to verify your request. Account, content, operational and billing records have different storage needs; deletion requests can be subject to records needed for security, billing or legal obligations.

See our data retention statement for the configured periods, records without automatic expiry and backup limitations.

We will update this page when our handling changes and revise the date above.