How 1stSeen uses Google data

1stSeen's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

1stSeen asks for one permission:

• https://www.googleapis.com/auth/calendar.events. Google describes it as letting an app view and edit events on all your calendars.

That is broader than what 1stSeen does with it. With it, 1stSeen does exactly this, and only when you ask:

• For each date you tick in the calendar's sync panel, it adds an all-day event to your primary calendar. The event's ID is one 1stSeen makes, starting with "1stseen".
• If you sync a date again after it has changed, it updates that same event instead of adding another.
• When you disconnect and choose to remove synced events, it deletes the events it added. Otherwise they stay.

It never lists, reads, or changes any other event, and never touches another calendar. When you connect, it also asks Google for your primary calendar's name, to show which account is connected. This permission does not include that, so Google refuses it and no name is stored.

Each event says what it is. A forecast event says it is a 1stSeen statistical forecast and not a confirmed company date, with its confidence score where there is one, and every event links back to the role's page on 1stSeen.

1stSeen asks for three permissions, together:

• openid and email, to learn your Google account's email address, once, when you connect. That address is the only one a digest is ever sent to.
• https://www.googleapis.com/auth/gmail.send, to send the digest you previewed, from your account to that same address, each time you tick the confirmation and press Send, where sending is turned on for this site. It can send mail only. It cannot read, search, or delete your mail.

Connecting sends nothing, and nothing is sent on a schedule.

• It uses Google data only to add your chosen dates and to send the digests you ask for.
• It does not sell it, use it for advertising, or use it to train any AI model.
• It transfers it to no one, except that its hosting providers store it for 1stSeen: the access tokens are stored encrypted, and each is bound to your account and to the service it belongs to.
• No person reads it, unless you ask for help and agree to it, to investigate abuse or a security problem, or where the law requires.

What is stored, and for how long, is in the privacy policy.

• Disconnect Google Calendar from the calendar page, or Gmail from the digest page. 1stSeen asks Google to revoke its access and deletes the stored tokens.
• You can also remove 1stSeen's access yourself at any time, from your Google Account's list of third-party connections at myaccount.google.com/connections.
• Deleting your 1stSeen account deletes both stored tokens and asks Google to revoke both. The deletion never waits on Google: if Google does not confirm the revocation, your account is still deleted and you are told to remove the access yourself at the address above.

Questions about Google data go to hello@1stseen.win.