ShiftMate — Privacy Policy
ShiftMate is a browser extension that helps users of the Keka HR platform clock in and out, take timed breaks, and view their attendance from the browser toolbar. This page explains exactly what data the extension touches and where that data lives.
Short version: ShiftMate has no servers. Everything runs locally in your browser, and the only network destination is Keka itself. Your data is not collected, sold, shared, or transmitted to the extension's author.
1. Data the extension handles
To do its job, ShiftMate handles the following pieces of data, all of which originate from your interaction with Keka:
- OIDC tokens (access token, refresh token, expiry, OIDC client_id) — issued by Keka's identity server to authenticate your API calls.
-
Email and password — only when you choose to sign
in through the extension's built-in login form. They are sent
directly to Keka's login endpoint (
app.keka.com) and are never retained by the extension after the request completes. - Captcha response and one-time code (OTP) — submitted to Keka when it asks for them during sign-in. Not retained.
- Device location (latitude and longitude) — read from Chrome only at the moment you punch in or out, and only when your company's Keka attendance policy requires a location for web clock-in. It is sent to Keka with that punch, exactly as Keka's own web app does, and is never stored or sent anywhere else. If location is unavailable, the punch is sent without one.
- Attendance data (today's punches, recent workdays, totals) — fetched from Keka on demand to render the popup; not stored beyond what the popup needs to display.
- Work-calendar and team data (your shift, holidays, weekly offs, leave balances, pending-approval and notification counts, colleagues' names and birthdays, who is on leave today) — fetched from your Keka dashboard to show in the popup, skip auto clock-in on days off and send reminders. Cached briefly in memory for the browser session; never sent anywhere except back to Keka.
- Your settings (auto clock-in/out times, break preferences, reminder toggles, birthday-wish template).
- Active break state (start time, return time, duration) — stored locally so the countdown survives the popup closing.
-
Keka tenant subdomain — read from the
Subdomaincookie Keka itself sets on.keka.com, so the extension calls the correct API host.
2. Where this data is stored
Sign-in tokens, the active break and other device-specific state are
kept in chrome.storage.local on this computer only.
Your settings and Keka subdomain are kept in
chrome.storage.sync so they follow your Chrome profile.
Short-lived API caches live in chrome.storage.session and
are cleared when the browser closes. Nothing is written to any
external database, file, or remote server operated by the extension
author.
3. Where this data is sent
The extension contacts the following hosts, all owned by Keka:
https://app.keka.com— OIDC authentication endpoints (/connect/authorize,/connect/token,/Account/Login,/captcha).https://<your-subdomain>.keka.com— attendance APIs (clock in/out, daily and historical punch data, user profile, deploy config).
No other host is contacted. No data is sent to the author, to analytics services, to advertising networks, or to any third party.
4. What the extension does not do
- It does not run any analytics, telemetry, crash reporting, or remote logging.
- It does not load or execute remote code. All extension code is bundled in the package.
- It does not read tabs, cookies, or storage from non-Keka domains.
- It does not sell, share, or transfer your data to anyone.
- It does not display advertising and is not monetized.
5. Permissions, briefly explained
storage— keep tokens, settings and break state across popup opens.alarms— run scheduled auto clock-in/out and breaks, and refresh the toolbar badge once a minute.notifications— tell you about automatic punches, birthdays and requests awaiting your approval.scripting— read the sign-in session from an open Keka tab so you can sign in without copying tokens by hand.geolocation+offscreen— attach your real location to a punch when your company's Keka policy requires it (the offscreen page lets the background read it for automatic punches).cookies— read the Keka-setSubdomaincookie to find your tenant.- Host permissions on
*.keka.com— required to call Keka's own APIs.
6. Your control
You can clear every piece of data ShiftMate has stored at any time
via the popup's Settings → Reset Everything button,
or by removing the extension from
chrome://extensions/.
7. Children
ShiftMate is designed for adult employees of organisations that use Keka. It is not intended for use by children under 13.
8. Changes to this policy
If the extension's data handling ever changes, this page will be updated and the "Last updated" date at the top will change with it.
9. Contact
Questions or concerns: open an issue on GitHub.