Keyring's Chrome Web Store Permissions and Privacy

Your Privacy is Important to us.

At Keyring, we care about privacy. It is at the core of our decision-making process and how we deliver the Keyring experience to you. We want to put our policy in simple terms to make it clear and understandable for everyone who uses Keyring.

Here's what you need to know:

  • We do not sell your personal information financial data, demographic data, or personally identifiable information (PII)
  • We do not link any of your browsing behavior to your personally identifiable information.
  • We do not collect your passwords
  • We do not collect your password personal browsing history
  • We do not store you contacts

What we do collect:

  • We track what shows and movies you watch so that we can recommend similar content on services you already have access to, and services that have content that you don't have access to yet.
  • We track what services you have access to so that we can surface the best content on those services for you.

That’s is all, in simple terms. Though, if you want the legal-speak version, it's available to you here. We're happy to answer any quesitons that you may have at

What our Chrome Extension permissions mean

Keyring will ask you for permissions, which we also have to get approval from the wonderful Chrome Web Store Review team to use. Here's we ask for, and what it means.

Read your browsing history — We only look at the history of streaming services, unfortunately, Google Chrome's system permission limitations don't allow us to define each service, we only read browser URLs of streaming services.

activeTab —  This permission allows Keyring to go through the active tab domain (e.g if you're on Netflix, the activeTab domain is, if the user is currently on any of the Keyring's supported services' websites. The purpose of this permission is to enable us to notify the user if Keyring can let them access to subscription services and for the user to view trailers that navigate to the respective service's content, in-browser. How cool is that!

How it works: We scan the text of the user's sites, if we find a word match, we show the user if they can access that content. Before we show them if they can access the content, we show them a preview of the content to pique their interest.

tabs — This permission enables us to track if logs out of shared services no longer in-use. This permission also helps enable login for supported subscription services: we open the tab of the respective service, securely and privately log users in, if they are invited by another user to share said service.

It also lets us open/close tabs during our onboarding experience for a smooth flow, and the user after see a content preview, that we provide in-browser, it lets us open a tab to lead the user to the content, on the service the content is located on.

storage — We use storage to store authorized user authentication data on a user's local machine, to enable them access to the respective service. We also store data from the last service a user visited to enable them to "Resume" consuming the last content they were watching/reading.

cookies — Cookies are used to keep users logged in, and to enable private and secure access to shared accounts without revealing passwords.

webNavigation — This enables credential sharing through the sites that user visits (by reading the email/password fields on the page DOM) that login info shared in Keyring is able to give them access to. This is similar to popular password managers like Dashlane, 1Password, LastPass, and other password managers.

More from Keyring