Last updated: August 2026
Laze is a scheduling tool that maps your calendar. It is built so that your data stays with you.
With your permission, Laze reads your Google Calendar using Google's read-only scope
(calendar.readonly). Laze cannot create, edit, or delete calendar events. When Laze helps
you create an event, it opens Google Calendar's own interface prefilled — the saving happens in
Google's product, under your account.
Laze has no database. Your calendar events, home/office addresses, and favorite spots are stored only in your own browser (localStorage) on your own device. When you sign in, your Google sign-in credential (a refresh token) and your basic profile (name and email) are encrypted and stored in a secure cookie on your device; our server uses it transiently to obtain short-lived access tokens from Google and never stores it, your calendar data, or anything else about you. Clearing your browser data and cookies removes everything, and you can revoke access at any time (see below).
Your browser talks directly to: Google (Calendar API, and optionally the Places and Routes APIs for nearby spots and live travel times), OpenStreetMap services (map tiles via CARTO, geocoding via Nominatim, places via Overpass). Each receives only what is necessary to answer the request (for example, map coordinates), governed by their own privacy policies. If you paste a public scheduling link (for example, Calendly) into the Suggest feature, our server fetches that page's public availability on your behalf and returns it to your browser; nothing from that request is stored.
To understand how Laze is used and improve it, we collect usage analytics (via Vercel Web Analytics and PostHog): page views and product actions such as "calendar synced" or "suggestion copied", with counts only. When you sign in with Google, we associate your usage with your name and email address (from your basic Google profile) so we know who is using Laze. Analytics never include your calendar content — no event titles, attendees, locations, or messages — and we do not use session recording or advertising trackers.
Laze's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
You can revoke Laze's access to your Google account at any time at myaccount.google.com/permissions.
Questions: jacobadennis@gmail.com