tideco

tide for Chrome privacy policy

Effective 1 November 2026.

tide for Chrome tiles and arranges your Chrome and web app windows on chromeOS. This policy says what it reads, what it keeps, and where that goes.

In short: tide for Chrome has no server, no analytics and no ads. It sends nothing to its developer or to anyone else. What it keeps stays in Chrome’s own extension storage, on your Chromebook. The one exception is your settings, which Chrome Sync copies to your Google account if you have Sync turned on.

What tide for Chrome reads

What tide for Chrome keeps, and where

What tide for Chrome sends

Nothing over the network. tide for Chrome makes no network requests of its own. On Linux, with tide for Linux’s tab list allowed, the tabs go to tide for Linux’s helper on the same computer, through Chrome’s native messaging, and no further. Showing a tab’s site icon in the launcher loads that icon the way Chrome’s own tab strip does.

Permissions

tide for Chrome asks for the first three when you install it. Chrome shows no warning for them. It asks for the rest only when you click Allow in its settings, and you can turn each off there again.

Permission Why
system.display Each display’s size, to lay out windows
storage Keeping the state and settings above
scripting The unread-count script on sites you allow, and the shade over inactive windows
tabs (optional) Tab titles and addresses, for tab search, restarts and Secure Shell’s windows
Each site in your unread counts list (optional) Its unread count, from the page title
All sites (optional) Only for dimming inactive windows
nativeMessaging (optional, Linux only) Handing your tabs to tide for Linux’s switcher, on the same computer

Changes and contact

Changes to this policy are made in this file, and its history is public in tideco’s repository. Questions go to tideco’s issues.