EVA Pilot Privacy Policy
Last updated: 27 September 2026
EVA Pilot is operated by Mykyta Krushelnytskyi. For privacy questions or requests, contact mykyta@krudamedia.ch.
Information EVA processes
EVA processes your signed-in account identity, preferences, text, recordings, transcripts, documents and images that you provide. It stores the resulting summaries, extracted records, Contexts, Projects, People, identity corrections and feedback to provide your personal assistant workspace.
Connecting Google Calendar is optional. EVA requests your Google account identity and email, permission to read your calendar list, and permission to read and write calendar events. It reads events from calendars you select. Stored event information can include titles, descriptions, locations, dates, times, timezones, cancellation status and identifiers needed for synchronization. The active calendar mirror normally covers one calendar month into the past and six months into the future. EVA does not request access to your Gmail mailbox through this connection.
EVA uses Calendar information to show your schedule alongside EVA Events and support your daily Brief. When you explicitly choose to publish an EVA Event, EVA can create an event in a selected writable Google calendar.
If you choose to turn on publication for newly approved EVA Events, EVA attempts to create a copy in your selected primary Google Calendar after you approve an Event. It sends the approved Event title, date, time and location. EVA stores the publication choice and delivery state securely, and uses the Google Calendar permission you granted to create or confirm that copy. Older approved Events are not sent automatically. Turning this option off stops copies that have not been sent; a copy already created in Google remains there until you manage it in Google Calendar. EVA does not update or delete existing Google events through this option.
AI processing and service providers
EVA uses OpenAI for transcription, understanding supplied material, generating daily Briefs and reviewing responsibility on existing records. Material relevant to those operations is sent to OpenAI. Daily Brief inputs can include the current day's selected Google Calendar event titles, locations, dates, times and status, alongside relevant EVA records. Google access and refresh tokens are not sent as AI input.
EVA is hosted through OpenAI's Sites platform, using Cloudflare infrastructure for application execution, database storage and uploaded files. Sign-in uses ChatGPT. Google provides the optional Calendar connection. The public information pages on krudamedia.ch are hosted by Squarespace, separately from the EVA workspace. These providers process information needed to deliver their services under their applicable terms and privacy policies. Their processing may occur outside your country; this notice does not promise Swiss-only or EU-only storage.
EVA does not sell Google user data or use it for advertising. EVA'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 Workspace API data is not used to develop, improve or train non-personalized AI or machine-learning models. Provider processing to deliver your requested features is distinct from training a general-purpose model.
Storage and protection
EVA uses application-level encryption for semantic content, uploaded originals and Calendar credentials. The application server can decrypt information to deliver features, so this is not end-to-end or zero-knowledge encryption. Some operational metadata, including identifiers, timestamps, status and Calendar timing information, is not covered by this content encryption. No service can guarantee absolute security or uninterrupted availability.
EVA records operational diagnostics such as processing stages, errors, duration, file size, model usage and estimated cost to troubleshoot reliability. These diagnostic records are designed not to contain source bodies or transcripts. Feedback you explicitly submit is separate content.
Retention, export and deletion
EVA currently retains your supplied material and derived records for ongoing use unless removed through supported deletion operations. Original audio is not automatically deleted after processing. Avoid using EVA as your only copy of important information.
You can export a bounded copy of supported EVA data in Settings, optionally including original files. The export has size and record limits and excludes some information, including the Google Calendar mirror and unapproved items. It is not a complete account backup or a guaranteed restore point.
Deleting a Context removes its associated EVA records and schedules deletion of associated uploaded files. File cleanup may remain pending if storage deletion fails. Minimal deletion and operational records may remain; feedback can remain with its association to the deleted record removed. The current pilot does not provide individual Source deletion or a self-service account-deletion control. Contact the operator to request access, correction or deletion assistance; your identity and the scope of the request may need to be verified. Do not send passwords, API keys or Google tokens in a request. Provider retention and backup deletion timelines are separate and are not guaranteed by EVA.
Disconnecting Google Calendar removes EVA's local Calendar connection, credentials and mirror, and attempts to revoke Google's authorization. You can also revoke EVA directly in your Google Account's third-party connections settings. Disconnecting does not delete your EVA account or events previously created in Google Calendar.
Changes and contact
This notice will be updated when EVA's data practices materially change. Contact mykyta@krudamedia.ch with questions or privacy requests.