Even

Privacy policy

How Even accesses, uses, stores, and shares information. Last updated November 6, 2026.

Who operates Even

Even is a private household application operated by its owner. Access is limited to approved accounts. Contact the operator at friendtechventures@gmail.com with privacy questions or data requests.

Information you provide

Even stores household records you add, including names, dates, notes, links, document references, tasks, assignments, labels, comments, and agent proposals. Household members can access shared household information. Only add information you are authorized to share with the household and any agents you permit to access it.

Google account access

Google sign-in provides account identity information, such as your email address and profile information, to authenticate you and check whether your account is approved. Even also requests read-only Calendar and Drive permissions. Those Google permissions can authorize access across your account; selecting a source in Even determines which calendars or folders the application displays and indexes.

Even reads calendar lists and events to display selected calendars and associated dates. It reads Drive folder and file metadata, including file identifiers, names, file types, links, parent folders, and modification times, to browse selected folders and index chosen files. Indexed document metadata and any notes or links you add are stored in the household database. Calendar responses and folder listings may be cached temporarily in server memory. Opening or previewing an original file uses Google’s services and access controls.

The requested Drive permission also permits reading and downloading file contents, although the current Even integration uses metadata and Google-hosted previews. The integration does not edit or delete Google files or calendar events.

Storage and service providers

Even runs on Vercel and uses Supabase for authentication and the household database. Google provides sign-in and the connected Calendar and Drive services. These providers process information needed to operate those features under their own policies.

Google access and refresh tokens are encrypted before storage in the application database and are used by the server for authorized Google requests. Authentication cookies keep you signed in; browser storage remembers appearance preferences. Operational records may include request information, identifiers, timestamps, action outcomes, and fixed error codes. Agent audit history records who acted and what operation was attempted.

Connected agents and sharing

When you authorize an agent connection, that agent can read or change only the information permitted by its current Even grant. Allowed record types and permissions can include indexed document metadata and other household records. Calendar reads and raw Google credentials are not exposed through the current agent connector. Grant permissions do not give an agent the household user’s identity.

Data you authorize a connected agent to receive is also processed by that agent’s provider under its own terms and privacy settings. The household operator and other authorized household members can see shared records, comments, proposals, and permitted activity history. Infrastructure administrators may access data for specific support you authorize, security investigations, or legal obligations.

Even does not sell Google user data, use it for advertising, or use it to train generalized AI models. Even’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Your controls, retention, and deletion

You can revoke an agent connection in Settings and remove Even’s Google authorization in your Google Account’s third-party connections. Revocation stops the corresponding authorized access; it does not automatically delete household records or information an agent provider already received.

Household information is retained while needed for the application’s features and history, unless removed through an available app control or a deletion request. Archived tasks, comments, proposals, and audit records may remain as household history. Operational logs and backups may retain copies for their applicable retention periods. Contact the operator to request removal of stored household information or Google connection credentials. Removing an indexed record from Even does not delete the original Google file or event.

Updates

This policy will be updated when data practices change. New Google access or agent permissions require the corresponding authorization. The operator will provide notice and obtain consent when required for changes to how Google data is used.