Eventy Privacy Policy
Effective date: 2026-01-26
Eventy processes webpage content or selected text only when you use
the "Scan" action. The selected text or page text is sent to our
Cloudflare Worker proxy and to OpenRouter to extract event details.
Depending on your Settings, Eventy then either opens a prefilled
Google Calendar page or creates events via the Google Calendar API
after you authorize with Google.
What data we handle
- No third‑party trackers are embedded.
-
We do not sell or share your personal information. We do not
maintain server‑side user profiles.
-
Text and images you choose to scan are sent to our Cloudflare Worker and to
OpenRouter solely to extract event fields (title, date/time,
location, description, optional recurrence).
-
Bring Your Own Key (BYOK): If you provide your own OpenRouter API key, it is transmitted
securely via our proxy to authenticate your requests. We do not store your API key on our servers.
-
When you enable "Use Google Calendar API (OAuth)", Eventy uses
the minimal scope
https://www.googleapis.com/auth/calendar.events
to create calendar events you select. Eventy does not request
broader calendar scopes.
OAuth and tokens
-
Authentication uses Chrome Identity. Access tokens are obtained
from Google and cached by Chrome; Eventy does not store tokens on
our servers.
-
Tokens are used only to call Google Calendar’s REST API from the
extension. They are not sent to our Cloudflare proxy.
-
You can revoke access at any time via Settings → Disconnect, or
in your Google Account at
Google Account → Security → Third‑party access.
Storage and retention
-
Basic preferences (e.g., theme, whether API mode is enabled) are
stored in your browser’s
chrome.storage. Event
extraction results may be cached locally to improve UX. We do
not store your data on our servers.
- All network traffic is transmitted over HTTPS.
Contact
If you have questions about this policy, contact us at the email
above.