The short version
- ADP Shifts runs entirely in your browser. There is no ADP Shifts server, account, or database.
- It reads your own schedule from ADP Workforce Now and writes it to one Google calendar that it creates.
- It never sees your ADP password and never reads, copies, or stores your ADP cookies.
- It reads your calendar list to find ADP Shifts, but cannot read or change events in your other Google calendars.
- No analytics, no advertising, no selling or sharing of data. The developer never receives your data.
1. Who we are
ADP Shifts is an independent, open-source project published under the MIT License at github.com/thedavidweng/adp-calendar. In this policy, "we" means the project's maintainer. ADP Shifts is not affiliated with, endorsed by, or sponsored by ADP, Inc. or Google LLC.
2. What the extension does
ADP Shifts has a single purpose: to copy the signed-in employee's work schedule from ADP Workforce Now into a dedicated Google
Calendar named "ADP Shifts", and to keep that calendar up to date. Everything described below exists only to provide that feature.
When you press Export .ics, the extension also builds the same schedule into an .ics file in your browser and
downloads it to your device. The file is not uploaded anywhere, and exporting does not use Google.
3. Information the extension handles
| Information | Where it comes from | Why | Where it is kept |
|---|---|---|---|
| Your schedule: shift dates and times, shift name, department, job, location, pay code, shift status, and employer holidays | ADP Workforce Now, using the session already in your browser | To create matching events in your ADP Shifts calendar, or to build an .ics file when you press Export .ics |
Processed in memory, then written to your own Google account or saved as a file on your device. Not stored by the extension. |
| Your ADP Position identifier | ADP Calendar’s Position lookup response, or the legacy schedule view address | To request your schedule, and only yours | Local extension storage on your device |
| Your connected Google account email address | Google, after you approve email access | To show which account is connected and keep token renewal on that account | Local extension storage on your device. Cleared when you sign out or disconnect. |
| A Google OAuth access token and its expiry time | Google, after you approve the consent screen | To manage the ADP Shifts calendar | Local extension storage on your device. Tokens expire after about an hour. No refresh token is requested or stored. |
| Settings and status: the ID of the ADP Shifts calendar, time zone override, time and counts of the last successful Sync, retry counters, whether a sign-in reminder was shown, setup progress | The extension itself | To find its own calendar again, schedule Syncs, show status, and avoid repeat notifications | Local extension storage on your device |
ADP's schedule response also contains your name, employee ID, and login ID. The extension ignores those fields. It does not store, display, or send them anywhere.
Your ADP session cookies are attached to requests to workforcenow.adp.com by the browser itself, exactly as they are when
you use the site. The extension never reads, copies, exports, or stores them, and it never asks for or handles your ADP password or
multi-factor codes.
4. Google user data
The extension requests the Google Calendar permission: https://www.googleapis.com/auth/calendar.app.created. This scope lets an app
create secondary calendars and manage only the calendars and events it created.
It also requests https://www.googleapis.com/auth/calendar.calendarlist.readonly to read calendar-list metadata
and recover its existing ADP Shifts calendar after reconnecting or reinstalling. This does not grant access to other calendars' events.
It also requests https://www.googleapis.com/auth/userinfo.email to show the connected account's email address and
keep authorization on that account. It does not request access to Gmail messages, contacts, or other profile information.
With the Calendar permission the extension:
- creates one calendar named "ADP Shifts";
- lists, creates, updates, and deletes events in that calendar so it matches your ADP schedule from today onward;
- never changes events dated before today.
ADP Shifts' use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:
- Google user data is used only to provide and improve the calendar sync feature that is visible in the extension.
- Google user data is not transferred to anyone, except to Google itself as part of the Calendar API requests that perform the sync.
- Google user data is never used for advertising, including personalized, retargeted, or interest-based advertising.
- Google user data is never sold, and is never used to determine credit-worthiness or for lending purposes.
- No human, including the developer, reads your Google user data. The data never leaves your browser except to go to Google.
- Google user data is not used to train artificial intelligence or machine learning models.
5. Where data goes
The extension makes network requests only to these services, and only to perform the sync you asked for:
workforcenow.adp.com(ADP) to read your schedule;accounts.google.comandoauth2.googleapis.com(Google) to sign in and to revoke access when you disconnect;www.googleapis.com(Google Calendar API) to manage the ADP Shifts calendar.
It contacts no other servers. It contains no analytics, crash reporting, advertising, or tracking code, and it does not load or run code from the internet. Your use of ADP and Google is governed by their own privacy policies.
6. What we never do
- Collect, receive, or store your data on any server we control. We do not operate one.
- Sell, rent, or share your data with third parties, data brokers, or advertisers.
- Use your data for any purpose unrelated to syncing your schedule.
- Look up the schedule of any employee other than the one signed in.
7. Keeping and deleting your data
- Sign out of Google. Revokes Google access and clears the connected email, token, calendar ID and Sync history. Your ADP Position and time-zone settings are kept. The existing Google calendar is not deleted.
- Disconnect and clear data. In the extension's Settings, this button revokes the Google token with Google and erases everything the extension stored locally.
- Uninstall. Removing the extension deletes all of its local storage.
- The ADP Shifts calendar lives in your Google account, so it stays there until you delete it in Google Calendar. You can also revoke the extension's access at any time at myaccount.google.com/permissions.
8. Security
Data stays on your device and in your own Google account. Requests use HTTPS. The extension ships with no client secret, requests no long-lived refresh token, and keeps only a short-lived access token in Chrome's extension storage, which other websites cannot read. The full source code is public so anyone can verify these claims.
9. The ADP Schedule Export userscript
The optional userscript adds an Export .ics button to Workforce Now and does not connect to Google. When you press it, the
userscript reads your schedule from ADP using your existing session, builds an .ics file in your browser, and downloads it
to your device. It contacts only workforcenow.adp.com. It stores only your Position identifier and time zone preference
in your userscript manager's storage.
10. This website
This website is a static site hosted by GitHub Pages. It sets no cookies, runs no analytics, and loads no third-party fonts or scripts. GitHub may log technical information such as IP addresses to operate and secure its service, as described in the GitHub General Privacy Statement.
11. Children
ADP Shifts is intended for employees using their employer's ADP account. It is not directed to children under 13.
12. Changes to this policy
If this policy changes, the new version will be published on this page with a new effective date. The full history is available in the project's public repository. If a change would expand how data is used, it will be announced in the extension's release notes before it takes effect.
13. Contact
Questions or requests about privacy can be sent by opening an issue on GitHub. Please do not include personal schedule details in public issues.