Privacy Policy
This policy describes the current privately operated Harness OS application and its public information site, hvos.dev. Harness OS is maintained by Vitaliy Goncharov. Contact: 1990vitaliy1990@gmail.com.
Google access and its purpose
Google access is granted through OAuth in your browser. Harness OS does not ask for your Google password. It uses access and refresh tokens to access the account you authorize, including refreshing access without repeating sign-in while the authorization remains valid.
The Gmail integration uses gmail.readonly to read inbox messages and gmail.compose, when granted, to create drafts you approve. Although Google's compose permission also permits sending, the current Harness OS integration implements no email-send operation. It does not delete Gmail messages or change their read status.
The application fetches the connected account's email address, message and thread identifiers, sender, subject, received time, snippet, message text, Message-ID header and attachment filenames. Attachment contents are not downloaded by the integration. The default manual sync covers the last 24 hours and up to 20 inbox messages per run; these limits are configurable.
Separately granted Calendar permissions allow reading the primary calendar and creating approved events. Calendar context may include event titles, dates and times. The integration creates events without attendees and does not send invitations.
AI analysis and data transfers
When analysis is requested, Harness OS sends the sender, subject, attachment filenames and a limited portion of message text to Anthropic through Claude Code using the operator's subscription. The default message-text limit is 6,000 characters. Relevant stored memory and upcoming calendar event titles and times may also be included. This processing produces summaries, classifications and proposed replies, tasks or events.
The AI receives no Google OAuth tokens and has no tools in this analysis flow. Claude Code is invoked with session persistence disabled. This disables local CLI session persistence; it is not a promise of zero retention by Anthropic. Anthropic's processing and retention depend on its applicable terms and account privacy settings. Harness OS itself has no model-training feature and does not use Google data to train general-purpose models. Before processing Google data, the operator must ensure that the AI account settings and terms exclude such training.
Google receives requests needed for the authorized Gmail and Calendar features. The application's persistent database is hosted on Supabase (PostgreSQL), so the stored records described below leave the local device. The backup workflow can place encrypted database backups in the operator's Google Drive and credential backups in the operator's Bitwarden vault. These transfers serve application operation and recovery.
What is stored
The database stores the connected account address, label, granted permissions, connection status and synchronization times. Mail records contain message and thread identifiers, sender, subject, received time, a snippet of up to 500 characters and a content hash. It also stores AI summaries and classifications, proposed reply text, task or event details, approval records and execution results. These derived records can contain information from your emails.
The mail pipeline does not store the full fetched message body as a database field. It reads the body again when analysis needs it. This does not mean that no email content is retained: snippets, summaries, draft proposals and other derived records are retained. Operational mail journal entries contain identifiers, status codes, counts and model usage metadata rather than message bodies.
OAuth tokens are stored per account outside the application repository and database. On Windows, the token files are protected by Windows DPAPI, tied to the Windows user. On other operating systems, the implemented fallback is JSON files with owner-only permissions, not application-level encryption. The local OAuth client configuration is kept outside version control. The credential backup workflow uses Bitwarden.
Database backups may contain the same personal information as the database. The offsite backup workflow encrypts backups locally with GPG before copying them to Google Drive. Local database dumps are not necessarily encrypted. Backup retention is managed separately from live records.
Retention, revocation and deletion
The current application has no automatic expiry for mail history or derived records. They remain until the operator deletes them. Disconnecting an account deletes its local runtime tokens and attempts to revoke Google authorization; it retains the account record, mail history and proposals. Disconnecting does not erase previously created Gmail drafts, calendar events, tasks or backup copies.
You can revoke access in Google Account connections. For deletion of stored application data, contact 1990vitaliy1990@gmail.com. Deletion currently requires operator handling, including associated proposals, approvals, tasks and applicable backups or vault copies; there is no one-click complete-erasure feature. Data retained by Google or Anthropic is governed by their own controls and terms.
Use restrictions and access
Google user data is used for the described personal productivity features and recovery. Harness OS does not sell it, use it for advertising, or make mailboxes public. The operator administers the private application and its database; this is not an end-to-end encrypted service in which the operator cannot access stored records.
Use and transfer of information received from Google APIs must adhere to the Google API Services User Data Policy, including its Limited Use requirements, and the Google Workspace user data policy. This includes limiting AI processing to the disclosed user-facing features and excluding general-purpose model training.
This public website
hvos.dev is a static information site hosted on Cloudflare Pages. It has no Google sign-in, mailbox API, contact form, advertising or application analytics scripts. Cloudflare processes ordinary web-request information, such as IP addresses and request metadata, to deliver and protect the site under its Privacy Policy. Contacting the support email uses your email service and shares your message with the maintainer.
Changes and questions
This policy will be updated when the application's data practices change. The effective date appears above. For questions, access or deletion requests, email 1990vitaliy1990@gmail.com.