Privacy Policy: Next Up by URLflows
Last updated: 15 November 2026
Next Up by URLflows is a Chrome extension that counts down to your next meeting from your own Google Calendar, and shows you the rest of your day. This policy says exactly what it does with data. The short version: your calendar goes from a script in your own Google account straight to your browser, never through us, and your settings stay on your device. Nobody, including us, can see your calendars, events or meeting links. The only thing sent to us is which features get used, such as "the side panel was opened", anonymously, so we know what to improve. You can switch that off; see exactly what's sent. If you turn on the weather, the place you choose is sent to Open-Meteo, a free weather service, for its forecast.
Next Up is also available as web pages you download and open from your own computer. The downloaded Next Up pages send no usage events, and nothing else, to us or to Google Analytics; only the Chrome extension described here does.
What it works with, on your device
Next Up reads your calendar through a Google Apps Script (the "bridge") that you add to your own Google account and deploy yourself. You give the extension that script's Web app address and your personal key. None of this is sent to us or to Google Analytics.
- Your calendar list and upcoming events: the extension asks your script for your calendars and for your events from 12 hours ago to as far ahead as you choose, and two weeks ahead while you use the All day view, with their titles, times, meeting links, locations, calendar colors and your response. Each request goes from your browser straight to Google (
script.google.com, which answers fromscript.googleusercontent.com), with your Google sign-in, so the script can check it's you. There is no server of ours in between. - The weather, only if you turn it on: Settings › What's shown › Daylight and weather shows sunrise, sunset and each hour's weather on the timelines. It's off unless you turn it on and choose a town or city. To find the place, what you type in its search is sent to Open-Meteo's place search (
geocoding-api.open-meteo.com); after that, only the place's position, rounded to about a kilometer, is sent to its forecast (api.open-meteo.com), about once an hour while a timeline shows it. Open-Meteo is a free weather service with no account or key; it never receives your calendar or anything about you beyond what any web request carries, such as your IP address, under its own terms. - What you choose and type: which calendars to show, alerts, views, the hours that count as free, your list of things to do, what you place in free time, which meetings you skip or pin, themes and your settings.
Your script keeps its last answer for about four minutes, in your own Google account, so asking again soon after doesn't read your calendar again. Google sees these requests, as it does any request to your own script, and Google's privacy policy applies to your Google account and Apps Script. The extension has no access to the pages you visit.
Where it is kept
Everything stays on your device, in Chrome's own extension storage (chrome.storage.local):
- Your connection and settings: your script's Web app address, its ID (so Settings can link to it) and your key, the calendars you picked, alerts, views, availability, what the toolbar icon opens, where its window was last placed, themes and any themes you have customized, and the town or city you chose for the weather.
- The last weather forecast, if you turned the weather on, so the timelines can show it between refreshes. Forgetting the place in Settings deletes it.
- Your calendar's last answer, so the panel, the toolbar badge and alerts can work between refreshes.
- What you've marked: meetings you skipped (forgotten a day after they end), meetings you pinned as critical (a copy of each is kept until you unpin it, even after the meeting ends), your list of things to do, and activities you placed in free time (forgotten a day after they end). Placed activities are never added to your Google Calendar.
- The usage-data switch and its random install ID (below).
- Performance history: for the Performance card on Settings › About, 30 days of the extension's own numbers on this computer (how fast its pages open, their memory, its background start-ups and the storage it uses). It holds nothing about your calendar and is never sent.
The Original Next Up, the full page inside the extension, keeps its own settings in its own page storage (localStorage) on your device.
None of it is synced between devices or sent to the developer (the usage events below hold none of it). Settings › Backup & Restore writes your settings to a JSON file on your computer, and imports it again, only when you ask; your script's address and key go in that file only if you tick the box to include them. Settings › Resets clears settings at any time, and uninstalling the extension deletes all of it. Keep your Web app address and key to yourself: together they work like a password for your calendar feed.
Links it opens
Join, Open map, Open link, the Google Calendar button and the links on Settings open in a new tab only when you click them, like any link. Open map and Get directions send that meeting's location to the map you chose in Settings: Google Maps unless you pick Apple Maps or Waze (from version 1.10.0; earlier versions always use Google Maps). Open link goes to the web address in its location. From version 1.10.0, a Zoom or Teams meeting also has Open in the app, which hands that meeting's number and passcode (Zoom) or its join link (Teams) to the app on your computer instead of opening a tab. Nothing is sent or handed to any of them until you click. The extension's fonts, icons and sounds are part of the extension and are not fetched from anywhere.
What it sends: which features get used
To see which parts of the extension get used and what to improve, it sends anonymous usage events to Google Analytics 4. Each event is a single request from the extension's own code to https://www.google-analytics.com/mp/collect; no Google script is loaded. The address also carries our Analytics property ID and key, which identify us, not you. Only the Chrome extension sends these; the downloaded Next Up pages send nothing.
The events, in full:
extension_installedandextension_updated: when the extension is installed or updated, with the Chrome version, the operating system (for examplewinormac), the browser language and, for an update, the version it updated from.panel_opened: Next Up was opened, and where (panelunder the toolbar icon,sidepanel, orpopoutfor its own window).page_viewed: a Settings section was opened, by its fixed name (for examplealerts,availabilityorabout).setting_changed: a setting was changed, by its fixed name. For on/off switches and fixed choices it also sends the new value (for exampleviewandagenda, orshowAvailabilityandtrue); for anything else, such as times, colors, lengths or anything you type, only the name, never the value.
Every event also carries the extension's name and version, a random install ID made when you install it and kept only in its storage (so a week of use counts as one user, not hundreds; it isn't tied to you or your Google account, Reset all replaces it with a new one, and uninstalling deletes it), and a session number and fixed timing value Google Analytics needs to group events into a visit. Here is a whole event as sent:
{
"client_id": "6f1c2e9a-4b7d-4e21-9a3c-0d5b8e7f1a24",
"events": [{
"name": "setting_changed",
"params": {
"extension": "next-up",
"version": "1.2.0",
"setting": "view",
"value": "agenda",
"session_id": "1761834012",
"engagement_time_msec": 100
}
}]
}
Never sent: your calendars or their names; your events, their titles, times, locations or meeting links; what you pin or place in free time; the place you chose for the weather; your list of things to do; your script's address or key; anything you type; the pages you visit; your name, email or Google account; advertising identifiers.
Google receives your IP address with each request, as with any request your browser makes; Google Analytics 4 doesn't log or store IP addresses. Google signals and ads personalization are off, the property isn't linked to any advertising product, and event data is kept for 2 months. Google processes it under Google's privacy policy.
To switch it off, turn off Share anonymous usage data on Settings › About. It's on unless you switch it off, and only that switch changes it. Nothing more is sent, not even an "opted out" event, and resetting or restoring a backup keeps your choice.
Uninstall feedback form
When you remove the Next Up extension from Chrome, Chrome opens a short feedback form in a new tab. Answering is optional, and you can just close the tab. The extension sends nothing to the form: the form's link only says which extension you removed. The form is hosted by Airtable, so anything you type there goes to Airtable and to the developer, under Airtable's privacy policy.
What it does not do
- No other network requests than the calendar requests to your own script, the weather requests to Open-Meteo when you've turned the weather on, and the usage events above. There is no backend.
- No access to web pages: its only host access is to Google's Apps Script addresses, to reach your own script, and it runs no scripts on websites.
- No tracking: no crash reporting, advertising identifiers or third-party code, and no usage events beyond the four kinds listed above.
- No account to sign up for.
- No sale or sharing of data: the usage events are used only to improve the extension and are shared with no one but Google as our analytics provider, following the Chrome Web Store's Limited Use requirements.
Permissions it asks for, and why
| Permission | Why it is needed |
|---|---|
storage | To keep everything described above on your device. |
alarms | To keep the toolbar badge current, send alerts that come due and refresh your calendar, once a minute. |
sidePanel | To open Next Up in Chrome's side panel. |
notifications | To send the system notifications you turn on, with a Join button. |
Host access to script.google.com and script.googleusercontent.com | To reach the Apps Script you deployed in your own Google account and read your calendars and events from it. Chrome may describe this as reading and changing your data on those sites; the extension only asks your own script for your events. |
It asks for no access to the pages you visit. Sending the usage events needs no permission.
Changes to this policy
If a future version changes what data the extension handles, this policy will be updated, and the store listing will say so, before that version ships.
Contact
Questions about this policy or the extension: hello@urlflows.app, or via urlflows.app.
This policy covers the Next Up by URLflows Chrome extension only. For the urlflows.app website, see the site privacy policy.