Privacy & how your sheet is read

Your links live in your own spreadsheet — URLflows for Teams just reads it, read-only, with no account and no server in the middle.

Read-only access — your sheet stays as private as you set it

Your sheet does not need to be public. The bar reads it through your browser's existing Google session, so Google's own permissions are respected: a sheet shared only with your team loads for the people you've granted access and no one else. "Anyone with the link" and published CSVs work too, if you'd rather not require a sign-in. Either way, access is strictly read-only — the bar can display your links, but it can never edit your spreadsheet.

No URLflows account, no server in the middle

You never create a URLflows account or sign into URLflows, and neither do your teammates — there's no backend. For a sheet you've restricted to your team, the bar simply relies on the Google session your browser is already using, the same one that lets you open the sheet in a tab. Nothing is routed through a URLflows server.

Your data stays in your spreadsheet

The data lives in your spreadsheet, which you control. Nothing is sold, and nothing is synced to a URLflows server. To change what the team sees, you change the sheet — that's the whole system.

Settings are stored locally

Your bar configuration — which sheets you've connected, your theme, toolbar layout, and per-site overrides — is stored locally on your device. You can save a copy any time; see Back up & restore your settings.

Questions about privacy?

If anything here is unclear or you have a privacy question, let us know and we'll be glad to help.