Navi privacy policy · After Bedtime Labs

This policy covers Navi Gmail Monitor, a locally operated application developed by Isaac at After Bedtime Labs, including its financial-email dashboard and optional Discord features. It explains what happens when an account owner authorizes Gmail access. Learn about Navi Gmail Monitor.

Gmail permission and information accessed

Navi requests exactly one Gmail API scope: https://www.googleapis.com/auth/gmail.readonly. Google describes this as read-only access to Gmail. The permission covers the mailbox, even though Navi searches for financial terms and configured vendors and filters candidates before fetching message content. It is not limited by Google to financial email.

Navi uses this access to recognize bills, statements, payment notices, subscriptions, renewals, cancellations, and related account notices. It can read message identifiers, timestamps, labels, message headers (including sender and subject), and the text or HTML message payload needed for analysis. HTML is converted to inert text. The monitor does not use a separate snippet field, download attachments, fetch remote images, or open message links.

Navi uses read requests only. It cannot send, edit, delete, archive, label, or mark messages as read. It does not request Gmail write permissions or your Google password. Authorization is through Google OAuth, which provides access and refresh tokens for the permission you grant.

Local processing and storage

Gmail retrieval and message analysis run on the operator’s computer. Raw message content is processed temporarily in memory. Optional analysis passes bounded message text and subject information to a locally running model through Ollama; optional vendor naming passes a domain hint. The Gmail integration rejects remote/cloud models and has no cloud model fallback. The operator must use a trusted local model service with cloud features and request logging disabled.

Navi does not intentionally persist raw subjects, full sender addresses, snippets, message bodies, HTML, attachments, or model prompts and responses. They do not enter Navi’s general conversation history. Memory, operating-system swap, crash dumps, and model-server internals are not securely erased by Navi.

A local SQLite database stores structured observations such as category, amount and currency, explicit dates, payment/autopay status, confidence, source timestamps, vendor labels, and amount comparisons. It also stores hashed message/sender identifiers, scan progress, deduplication and notice records. Vendor discovery retains bounded vendor names, sender domains, counters, timestamps, and the owner’s approval or ignore decisions. Hashing reduces direct identifiers; it does not make these records anonymous.

The authenticated local dashboard displays financial observations and vendor information to the operator. Email can be incomplete or misleading; these observations are not authoritative account or payment status.

OAuth and data protection

Gmail and Google OAuth requests use HTTPS. OAuth credentials are stored in a private local directory and are not published by this website. On Windows, saved OAuth tokens use Windows Data Protection API protection tied to the current user. On other supported systems, plaintext token storage requires explicit operator opt-in and restrictive file permissions; Navi does not include a cross-platform credential keyring.

The financial database is not encrypted by the application. Operators are responsible for private file permissions, disk and backup protection, and restricting access to their computer and local dashboard. Navi’s logs use bounded diagnostic codes rather than raw mail or OAuth token contents. These controls are not a guarantee against access by a compromised computer or local administrator.

Google provides the Gmail API and OAuth service, and processes requests under its own policies. The monitor does not send raw mail or vendor-discovery content to third-party or cloud AI services. After Bedtime Labs does not receive mailbox contents through this static website.

Optional Discord alerts: when configured, a private alert destination receives fixed generic warnings/recoveries and opaque identifiers. These alerts omit sender addresses, subjects, bodies, vendor names, financial amounts, and dates.
Optional owner-requested financial responses: private Discord commands or restricted owner-and-bot voice features can transmit formatted observations containing vendor names, message categories, amounts/currencies, due dates, payment/autopay states, amount changes, and apparent cadence or typical-amount ranges. Discord processes the request and text/audio response. Raw email, sender-domain discovery evidence, account numbers, and OAuth credentials are excluded. A local model may route the owner’s question; financial query results are formatted without sending those results back to the model.

Enable and use these optional features only if you want that information processed by Discord. Private or ephemeral delivery does not prevent Discord from processing it, and already delivered text or audio cannot be recalled by revoking Gmail access. Discord’s retention and privacy practices apply to data sent there; see Discord’s privacy policy.

Retention, deletion, and revocation

Structured financial history defaults to 730 days, configurable from 90 to 1,825 days, with row limits. Pruning runs after successful polls, so stopping the monitor or persistent polling failures can delay deletion. Vendor discovery entries and owner approval/ignore decisions do not expire with history pruning; they persist until the local data is removed. OAuth credentials and scan state also remain locally until removed.

You can stop future access through Google Account → Third-party connections: select the connection used for Navi and remove its access. Revoking permission prevents further authorized Gmail access but does not delete information already stored locally or delivered to Discord.

To remove Navi’s local Gmail data:

Stop the application hosting the monitor and disable the Gmail monitor in its local configuration.
Revoke the OAuth grant in your Google Account.
Verify the configured private Gmail data directory, then remove its credentials, tokens, vendor configuration, financial database, scan state, and related database journal files.
Remove corresponding backups, snapshots, or synced copies separately. Restart the host application to clear its in-memory Gmail events and cached financial state.

Database pruning is logical deletion, not secure erasure. Database free pages, journals, backups, swap, and crash dumps can retain information. Handle data already sent to Discord using Discord’s controls and retention policies. Removing local Navi data does not delete messages from Gmail.

Google API Services and Limited Use

Navi Gmail Monitor’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Google user data, including derived financial observations, is used only to provide the financial-email features described here. It is not sold, used for advertising, creditworthiness or lending decisions, or used to train general-purpose AI models. Optional local model inference does not train a model on your mail.

Transfers are limited to the disclosed, user-enabled features and the narrow exceptions allowed by Google’s policy, such as security or legal requirements. After Bedtime Labs does not routinely read your Gmail data. Any human access beyond the account owner’s own use must be limited to Google’s permitted cases, such as your affirmative agreement to review specific data, necessary security investigation, or legal obligations. This policy is not a claim of Google verification or a security certification.

Contact and policy updates

For confidential privacy or data-related inquiries, email privacy@afterbedtimelabs.dev. Include only the details needed to explain your question; never send passwords, OAuth tokens, or credentials. Messages to this address are routed through Cloudflare Email Routing to a dedicated studio Gmail inbox and processed to receive and respond to your inquiry. This is separate from Navi’s local Gmail monitoring; contacting us does not grant the monitor access to your account.

For general support and feedback, open an issue on the After Bedtime Labs website repository. GitHub issues are public: do not post personal information, email contents, financial information, account identifiers, tokens, or credentials. Send confidential privacy and data inquiries to the email address above instead.

This website hosts project information and this policy; it does not offer Gmail sign-in, receive Gmail tokens, or store your financial database. It has no account system or analytics. The theme preference is saved in your browser. GitHub Pages hosts the site and may process routine web-request information under GitHub’s privacy statement.

Updates will appear here with a revised date. If Gmail data use changes, the policy and relevant in-app disclosures must be updated and any required user consent obtained before that new use begins.