Vektr

PRIVACY

Privacy Policy

Effective August 22, 2026

Vektr is a private personal intelligence operating system. This policy explains how Vektr handles Google account information used to authenticate its administrator and, only through separately authorized integrations, access Calendar and Gmail.

Information Vektr receives

When you choose Sign in with Google, Vektr receives the basic identity information that Google provides through the OpenID Connect openid, email, andprofile scopes. This can include your Google account identifier, email address, display name, and profile image.

The sign-in flow does not request Gmail, Calendar, Drive, contacts, or other Google content. Calendar and Gmail use separate optional OAuth grants and can be revoked independently.

The Calendar integration reads selected calendar data and may create or update only the private events permitted by Vektr policy. The Gmail integration requests only the gmail.readonly scope to read approved mailbox content. It cannot send, delete, archive, label, move, star, or change message read state.

How the information is used

Vektr uses Google identity information only to verify who is signing in, restrict access to the approved administrator, display basic account information inside the application, protect the service, and investigate authentication or security problems.

Separately authorized Calendar data is used to provide schedule features. Separately authorized Gmail data is used to detect mailbox changes and normalize approved messages for the user's private Vektr workflows. Google user data is not used for advertising.

Storage and retention

Vektr stores authenticated session information in a protected, HTTP-only application cookie. The current session lifetime is no longer than eight hours. Operational logs may retain limited request and security metadata as needed to operate, protect, and troubleshoot the service. Google passwords and multi-factor authentication credentials are handled by Google and are not received or stored by Vektr.

OAuth refresh tokens are encrypted with a server-held application key. For Gmail, Vektr retains normalized plain-text message bodies for up to 30 days, retains bounded metadata for provenance, and does not retain HTML, raw MIME payloads, remote images, or attachment bytes. Backup copies follow the configured backup lifecycle.

Sharing and sale

Vektr does not sell Google user data, use it for advertising, or share it with data brokers. Information may be processed by infrastructure providers only as necessary to operate and secure Vektr, or disclosed when required by law.

Your choices

You can end the current application session by signing out. Calendar and Gmail can be disconnected independently in Vektr Settings or revoked from Google Account permissions. To request information about or deletion of Vektr-held account information, contact the address below.

Changes to this policy

This page will be updated before Vektr materially changes how it accesses, uses, stores, or shares Google user data. The effective date above identifies the current version.

Contact

Questions or privacy requests can be sent to jb@jbandthemoonshineband.com.