Zealer Dashboard — Privacy Policy

Effective Date: November 4, 2026

1. What Data We Access

Zealer Dashboard accesses:

• Jira credentials (base URL, email, API token)
• Sentry credentials (base URL, organization, project, auth token)
• Sprint data, stories, subtasks, worklogs from your Jira instance
• Error issues and events from your Sentry instance
• If you connect Google Calendar: your own calendar events, and when your teammates are busy (see section 5)
• Locally-stored notes (1:1 logs, people log, growth plans, promotion cycle)

2. Where It's Stored

Settings, credentials, notes and cached data are stored in chrome.storage.local on your device. The Google access token is kept in browser memory only. Nothing is synced to the cloud, and none of it is stored on Zeal servers.

3. How It's Used

Credentials are used only to make read-only API calls directly from your browser to your Jira and Sentry instances and, if you connect it, to Google Calendar. Your tickets, worklogs, Sentry issues and calendar data go from those services straight to your browser and are not sent to Zeal or anyone else.

Zealer Dashboard also checks GitHub for new releases of the extension. That request carries no personal data.

4. Usage Reporting

To see who uses Zealer Dashboard and which parts help, the extension sends usage events to Zeal's own Sentry project. Each event carries your Jira email address, display name and account ID, the extension version, your role (engineering manager or engineer) and your squad key. The events are:

• App opened, once per browser session, with a small tally kept on your device: the first and latest day you used it, how many days and how many times you have opened it, and which versions
• Which sections you view (for example the Gantt or Insights), once per section per session
• A few actions: generating the sprint report, switching between Me and Squad, and opening a ticket in Jira
• Timings: how long each Jira refresh took, and roughly how long the panel stayed open
• When a Jira refresh fails, the error message

Usage events never include ticket content, anything you type, notes, your Jira, Sentry or Google tokens, or any Google Calendar data. They are separate from the Sentry views you set up: those read your own Sentry organization with your own token. Nothing is reported in Demo mode. Usage data is not sold, not used for advertising, and not shared outside Zeal.

5. Google Calendar (optional)

Connecting Google Calendar is optional. When you connect it, Zealer Dashboard asks Google for read-only access:

• calendar.events.readonly: your own events (titles, times, all-day and out-of-office entries), to show today’s meetings, your meeting hours and your days off.
• calendar.freebusy: when the teammates you list in Settings are busy, to show the team’s meeting hours. Zealer never sees the titles or details of their meetings.

Zealer reads this data from Google directly into your browser. The access token is kept in browser memory only and is cleared when the browser closes. Zealer stores your Google email address and the computed meeting-hour totals in chrome.storage.local on your device. Google Calendar data is never sent to Zeal or to anyone else, never included in usage reporting, never sold, never used for advertising, and never used to train AI models.

Zealer Dashboard’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

To disconnect, click Disconnect in Settings → Meetings and time, which revokes Zealer’s access, or remove Zealer at myaccount.google.com/permissions.

6. How to Delete Your Data

Uninstall the extension. All data in chrome.storage.local is deleted automatically when the extension is removed. To have your usage events deleted from Zeal's Sentry project, contact us.

7. Contact

For questions: https://www.getzeal.io/