MeetStreak
Last updated: July 3, 2026
MeetStreak turns your Google Calendar into a GitHub-style contributions heatmap. This page explains what data it accesses and what happens to it.
When you connect your calendar, MeetStreak requests Google's calendar.events.owned.readonly scope, limited to calendars you own. That scope technically grants access to full event details — titles, descriptions, locations, attendee identities. MeetStreak only reads four things per event: its date, whether it's an all-day event, whether you declined it, and whether you were the only attendee. We never read, store, or transmit event titles, descriptions, locations, or who else was invited.
Entirely in your browser. MeetStreak has no server that handles calendar data — your browser fetches events directly from Google's API and computes the grid and stats locally. Nothing is ever sent to a MeetStreak server, because there isn't one in this data path.
Nothing. No database, no cookies, no browser storage holds your calendar data. The access token Google issues lives in memory for your current browser session only and is discarded the moment you reload or close the page.
The "Share image" feature draws your heatmap to an image entirely in your browser. Nothing is uploaded anywhere unless you explicitly choose to download or share that image yourself.
We do not sell, rent, or share your calendar data with anyone, under any circumstances.
We do not currently use analytics or tracking of any kind. If that changes, this page will be updated to reflect it.
Because MeetStreak stores nothing, revoking its access to your Google Calendar is the complete way to disconnect entirely. Do that anytime at myaccount.google.com/permissions.
If our data practices change, we'll update this page and its "Last updated" date.
Questions about this policy or your data: [email protected]