Kosego

Privacy Policy

Last updated: October 18, 2026

This policy explains how Kosego handles information when you use this personal dashboard at kosego.casa. The service combines Bittensor network-data dashboards with a private Subscription Inbox for one Gmail mailbox authorized by its owner.

Information processed

The dashboard login processes the access password you submit to authenticate you. The site maintains an HTTP-only session cookie after successful login. The password is checked on the server and is not intentionally stored as a user profile.

If the mailbox owner configures the separate Gmail sync worker, it uses OAuth credentials and a refresh token to access that mailbox with Gmail's read-only permission. The worker may store the following message data in the configured PostgreSQL database:

  • Message identifiers and thread identifiers.
  • Sender names and email addresses, subject lines, dates, snippets, and read status.
  • Extracted plain-text message bodies for search and local job-match estimates, and sanitized HTML bodies for formatted display.
  • Whether a message is marked as Spam, plus sync cursors and error status needed to continue syncing.

The worker is configured separately from the website and fetches no more than 20 full messages per hour. It includes Spam and excludes Trash. The web dashboard reads the cached data from PostgreSQL; opening, searching, or filtering the inbox does not itself fetch messages from Gmail. HTML email is sanitized and displayed in an isolated frame. Remote images are blocked by default and load only if you explicitly choose to enable them for a message; doing so can notify the image host that the image was requested.

How information is used

Information is used to authenticate access, operate the dashboard, synchronize the authorized mailbox, display and search cached email, calculate heuristic job-match estimates, and maintain sync status. Gmail content is not used for advertising, sold, or used to train machine-learning models by this application. Match estimates are computed by the application from cached message text.

Storage, retention, and deletion

Cached message content remains in PostgreSQL until it is deleted by the database operator. The dashboard does not currently provide an in-app control to delete individual cached messages or the full cache. The mailbox owner can stop the sync worker and have the database operator remove the cached messages and sync state. Database backups may retain copies according to the database provider's backup lifecycle.

OAuth refresh tokens and client credentials are configuration secrets for the worker and must be kept outside browser code and source control. Access tokens are obtained as needed by the OAuth client library. Do not place Gmail secrets in public or NEXT_PUBLIC environment variables.

Service providers and sharing

The website is hosted on Vercel. The database is hosted by the PostgreSQL provider configured by the operator, and the Gmail sync worker runs on infrastructure selected by the mailbox owner. These providers may process information as needed to provide hosting, database, or computing services. The application does not intentionally disclose Gmail content to other parties except as necessary to provide the service or comply with law.

Gmail data is accessed through the Gmail API. Use of Google user data is limited to providing the inbox features described in this policy and is subject to the Google API Services User Data Policy, including its Limited Use requirements.

Security and your choices

Access to the dashboard is protected by a password and a secure, HTTP-only session cookie in production. The worker credentials and database connection string are server-side secrets. No internet service can guarantee absolute security, so protect the password, VPS, database, environment files, and backups. You may revoke the worker's Gmail access from your Google Account's third-party access settings; revocation stops future Gmail access but does not automatically delete data already cached in PostgreSQL.

Changes

This policy may be updated when the service or its data practices change. The date at the top indicates the latest revision. Continued use after an update means the revised policy applies to subsequent use of the service.