Ringly — Privacy Policy
Last updated: August 26, 2026
Ringly is a browser extension that provides a fast tab switcher overlay,
triggered by holding a key (default Alt) or a two-finger swipe. This
policy explains what data Ringly accesses, how it is used, and — just as
importantly — what Ringly does not do with it.
Summary
All data Ringly touches stays on your device. Ringly does not have a
server, does not send any data over the network to us or to anyone
else, and does not sell or share data with third parties.
What data Ringly accesses
Open tab information.
Titles, URLs, favicons, and
window/tab positions of your currently open tabs, so the switcher can
display them.
Web history (recent navigation, per tab).
Ringly keeps
a short rolling history (up to the last 20 pages) of the pages each
open tab has navigated to, along with the page title and time of
visit. This powers the "lineage" view in the switcher, so you can see
and jump back to where a tab has recently been. This history is
limited to open tabs — closed tabs' history is discarded — and is not
the same as your browser's full history.
User activity within Ringly's own overlay.
While the
switcher overlay is open, Ringly listens for mouse movement, clicks,
and keyboard input in order to run its own interface — for example,
detecting your hold-key, letting you drag nodes in the tab graph, and
navigating with arrow keys. This is limited to interaction with
Ringly's own UI and is not used to monitor your activity on the
websites you visit.
Where this data is stored
All of the above is stored locally in your browser using Chrome's
built-in
storage.session
and
storage.local
APIs:
Recent tab history and tab ordering are kept in
chrome.storage.session
, which is automatically cleared
when you close your browser.
Your customized trigger-key preference is kept in
chrome.storage.local
so it persists across browser
restarts, until you change it or uninstall the extension.
None of this data is transmitted to any external server, including any
server operated by us.
Third parties
Ringly does not sell, rent, or share any user data with third parties.
The only outbound network requests Ringly makes are to
Google's public favicon service
(
google.com/s2/favicons
), used purely to display a small
site icon next to each tab in the switcher — this is a standard image
request and does not transmit your browsing history or any other data
about you.
Permissions Ringly requests, and why
tabs
— to read tab titles/URLs and switch between tabs.
storage
— to save your trigger-key preference and a short-lived tab history cache, both locally.
scripting
— to load the switcher overlay into tabs that were already open before install/update.
webNavigation
— to detect page navigations so the per-tab history/lineage view stays accurate.
alarms
— to keep the extension responsive by periodically preventing it from going idle; performs no other action.
host permission (all sites)
— so the switcher overlay is available on any page you're browsing.
Data retention and deletion
Recent tab history clears automatically when you close your browser.
Uninstalling Ringly removes all locally stored data, including your
trigger-key preference.
Changes to this policy
If this policy changes, the "Last updated" date at the top of this page
will be revised accordingly.
Contact
Questions about this policy can be sent to:
mohitreal.nz@gmail.com