How we use
Google data.

Effective date: July 23, 2026. Presentation updated September 7, 2026.

Google Calendar — sensitive scope

When a user enables Calendar, Lazyest Work requests https://www.googleapis.com/auth/calendar.events.readonly. The app reads events from the user's primary Google Calendar in a rolling seven-day window.

It uses event title, start and end time, description, location, meeting link, status/type, organizer, and attendee response information only to show upcoming meetings in the menu bar, provide local meeting reminders, and provide meeting-assistance controls on that Mac.

Lazyest Work never creates, modifies, deletes, or shares calendar events. It does not use Calendar data for advertising, sale, profiling, or transfer to third parties.

Gmail Inbox unread badge

When a user enables the Gmail unread badge, Lazyest Work requests https://www.googleapis.com/auth/gmail.labels and reads only messagesUnread from the Inbox label. The app uses that number only to display the unread badge in the macOS menu bar.

It does not request or read email senders, subjects, bodies, attachments, or message IDs. Although the scope also permits label changes, Lazyest Work only uses it to read the unread count.

Account identification

The openid, email, and profile scopes identify the Google account a user connects and display its connection status.

Storage and control

Google access tokens are stored in macOS Keychain. The app processes the described data locally on the user's Mac. A user can turn off the relevant feature, disconnect in the app, or revoke access in Google Account security settings at any time.

Questions or requests about Google user data: [email protected].