Eyra (“we”, “the app”) is an AI assistant that helps you work with your calendar, tasks, Jira, and uploaded documents. This policy explains what data we process and why.
When you sign in (email/password, Google, or Apple), we store your account identifiers (such as email and Firebase Auth UID) so we can provide the service and secure your data.
If you connect Google, Jira, or Microsoft, we store OAuth tokens and use them only to fulfill your requests in the app (for example: listing today’s events, creating a task you approved, or summarizing a sprint). You can disconnect integrations at any time in Tools & Integrations.
When you connect Google, Eyra requests these scopes and nothing else:
auth/calendar.events) — to read your schedule for the daily
brief and to create or change events after you approve the change.
auth/calendar.calendarlist.readonly) — read-only, so that a
brief covers every calendar you follow rather than only the default one.
It does not allow us to create, delete or share a calendar.
auth/tasks) — to read your task list and to add or complete
tasks after you approve the change.
auth/userinfo.email) — to show which account is connected.
Eyra does not request access to Gmail or to your files in Google Drive.
Eyra’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In particular:
Nothing is written to your calendar or tasks without a confirmation step: Eyra prepares the change, shows you what it will do, and acts only when you approve it.
Messages you send to Eyra, optional memory items, daily briefings, and documents you upload to Cloud Vault are stored in your account so Eyra can continue the conversation and answer questions. Private Vault content stays on your device when that mode is used.
While Eyra is in private testing, the operator can open a conversation in an internal, read-only console — to see what Eyra actually replied when something goes wrong, and to fix it. Only the operator's own sign-in can open it, every access is recorded, and nothing can be written, sent, or changed from it. If a conversation contains Google user data, this is the “specific permission” the section above refers to: by taking part in the test you agree to it, and you can ask for your account to be excluded at any time.
If you turn on the job search and CV tool, Eyra can read a CV you have uploaded to Cloud Vault and store what it finds — your name and contact details, employers, roles and dates, the achievements your CV lists, skills, education, and languages — as a candidate profile in your account. It is extracted only from documents you uploaded yourself, it is used to compare vacancies against your experience and to draft CV content for you, and nothing is added to it that your own document does not say.
The profile is kept as a single record: reading a newer CV replaces it rather than adding a second one. It is stored until you delete your account, and it is never used for advertising or shared with employers — Eyra prepares documents for you to send, and does not send them anywhere itself. The tool is off until you switch it on, and no CV is read until you ask.
To generate answers we send relevant prompts and short context excerpts to AI providers (Google Gemini and Anthropic Claude). We send the least context a request needs rather than your whole history, and we use these providers under terms that do not permit training their models on what we send. We do not sell your personal data.
If you enable notifications, we store a device push token to deliver daily briefings and meeting reminders. You can disable notifications in system settings or in the app.
We collect device model, OS version, interface language, and anonymous crash and usage diagnostics, to keep the app stable. Eyra is in open beta: some features may be unstable or change, and we may collect additional crash diagnostics while that is the case.
By uploading documents that contain other people’s personal data or confidential information — employment contracts, NDA material, client records — you confirm you have a lawful basis to have them processed. Do not upload documents your own contractual or professional obligations forbid you to share.
We encrypt data in transit (TLS) and at rest, keep OAuth tokens encrypted, and limit access to production systems. No system guarantees absolute security, but we work to reduce the risk.
You have the right to:
To exercise any of these, write to eyra.copilot@gmail.com.
Eyra is not intended for anyone under 16, and we do not knowingly collect their data.
We may update this policy. We will announce material changes in the app or by email. Continuing to use Eyra after a change means accepting the updated policy.
Eyra is developed by Erika Oleksandrivna Dyendyeshy, Ukraine. Questions about privacy, or any of the rights above: eyra.copilot@gmail.com.