Privacy and your calendar data

Your events never pass through us

Next Up reads your calendar through the script you add to your own Google account. Your browser asks that script for your events, and the script answers directly. URLflows never receives, stores or sees your events.

Read-only, and locked to you

The script can only read your calendars — it can't create, change or delete anything. It only answers requests that carry your personal key, and it refuses anyone signed in to Google as someone else. You can read every line of it before you paste it into Apps Script.

Where your settings live

Your Web app URL, key, calendar choices, alerts, layout and theme are saved in your browser's local storage, separately for each Next Up window and tied to where the file is saved. They aren't sent anywhere, and the file itself stays on your computer.

Keep your Web app URL and key to yourself — together they work like a password for your calendar feed. If you think your key has been shared, open your Web app URL and click Make a new key.

No accounts, no tracking

There's nothing to sign up for, and the Next Up file doesn't include analytics. It loads its fonts and icons from public font and icon services, the same way most websites do.

Stop using Next Up

In Apps Script, go to Deploy → Manage deployments → Archive, then remove the script's access at your Google account's third-party connections.

Related guides

See how the connection is set up in Set up Next Up with a personal Google account, and fix connection problems in Troubleshoot common issues.