DASS Services

Pepper privacy notice

Last updated September 29, 2026

This notice covers Pepper, and data from a connected Google account. It is section 13 of the DASS Services Privacy Policy, which covers everything else about how DASS Services handles personal information.

Pepper is the internal operating system DASS Services runs on, at pepper.dass-services.com. It is invite-only: only people DASS Services adds as members can sign in. This section covers what Pepper does when a member connects a Google account.

What Pepper accesses. With the member’s permission, given on Google’s consent screen:

Why. Only to provide those features to the member: a working calendar, meeting scheduling, and an up-to-date list of the people the member corresponds with, with suggested follow-ups.

AI processing. To suggest who a correspondent is and whether to follow up, Pepper may send that person’s name and email address, the subject lines of up to ten recent messages and the previews of up to six to Anthropic’s Claude API, which returns a one-sentence summary. Anthropic processes this on our behalf and, under its commercial terms, does not use it to train its models.

Where it is stored. Access tokens are kept encrypted in Supabase Vault. Calendar events and the contact records Pepper builds are stored in Pepper’s Supabase database, hosted in the United States (Amazon Web Services, Oregon). Pepper runs on Vercel.

Who sees it. The member, and other DASS Services members who use Pepper. We do not sell Google user data, use it for advertising, or share it with anyone other than the service providers named in this section (Supabase, Vercel and Anthropic), as needed to run these features, or where the law requires it.

Limited Use. Pepper’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data to develop, improve or train generalized AI or machine learning models. No one reads a member’s Google data other than the member and the people they work with in Pepper, except with the member’s permission, for security reasons, or to comply with the law.

Keeping and deleting it. Disconnecting a Google account in Pepper (Settings, Integrations) deletes Pepper’s access tokens at once and stops calendar notifications from Google. Calendar entries and contact records already in Pepper stay until they are deleted; to have them removed, email hello(a)dass-services.com and we will do it within 30 days. You can also remove Pepper’s access at any time at myaccount.google.com/permissions.