Sidekick Browser Extension Privacy Policy

1. What this policy covers

This policy covers the Sidekick browser extension for Chrome, Brave and Edge. Our main privacy policy covers the 1p.dev website, accounts and hosted instances, and still applies to those. Where the two meet, this one describes the extension and the main one describes the instance.

The extension is operated by Player One.

2. The extension sends nothing to us

The extension talks to one place: the Player One instance you sign in to. It sends nothing to Player One, and we operate no server that it reports to. It contains no analytics, no advertising, no trackers and no third-party scripts of any kind.

If the instance you sign in to is one we host for you, then what reaches it is covered by our main privacy policy, where you are the controller of that data and we act as your processor. If you host your own instance, the data never reaches us at all.

3. What the extension keeps on your device

All of it stays in your browser's extension storage, on your computer:

• The address and display name of each Player One instance you have connected.
• A cryptographic key and the tokens that identify this browser to that instance, so you need not sign in repeatedly. The key never leaves your device.
• What you have allowed each connection to do, and whether you have paused everything.
• The list of sites you have told Player One never to look at.

Signing out of a connection removes its tokens from your browser and asks the instance to forget this browser. Removing the extension removes all of it.

4. What leaves your browser, and only when you allow it

Nothing is read from a page until an agent asks and you allow it. When you do, what leaves your browser goes to your Player One instance and nowhere else. Depending on what the agent is doing, that can include:

• The address, title and content of the page you allowed it to work in, including text and form labels.
• A picture of that page.
• What the agent typed or clicked, and what the page did in response.

Your instance then sends what the agent needs to whichever language model provider that instance is configured to use. You choose that provider. Content shared with an agent is kept in your instance's chat history in the ordinary way.

The extension never reads pages you have not allowed it to, never reads tabs it is not attached to, and never collects your browsing history.

5. What is masked, and what is not

We want you to be able to rely on this distinction, so we state it plainly.

When an agent reads a page as an outline, the values of password fields and of fields a site marks as one-time codes or payment card details are replaced before the outline leaves your browser. That is a reduction and not a guarantee: a picture of a page shows whatever the page shows, and a site that does not mark a field as sensitive cannot be recognised as such.

When you tick Act on the page, an agent works in the page the way your browser's own developer tools do, and nothing is masked. It can read the page as it stands, including whatever is typed or filled into it. The extension tells you this under that setting, before you turn it on.

6. What you control

• Access. Each connection is Off, Observe only, or Change things, and you choose. A new connection starts at Observe only, and nothing changes it but you.
• Consent. Player One asks before it works in a page, naming the page. You can deny, allow once, or allow without asking, and you can withdraw the last of those at any time.
• Visibility. Your browser shows its own banner for as long as Player One is attached to a tab, and the panel shows it too.
• Stop. One button in the panel, and your browser's own Cancel on that banner, both end it at once.
• Sites Player One never sees. Any site you list is refused before anything attaches, so the banner never appears on it.
• Pause. One switch stops everything without changing what you have allowed.
• Revocation. Your instance's Devices page removes this browser's access, immediately and from its end.

7. Why the extension asks for the permissions it does

• Debugger. This is how the extension reads and acts on a page, using the same interface your browser's own developer tools use. Your browser shows a banner for as long as it is in use, and the extension attaches only to a tab you have allowed, one at a time.
• Access to your Player One instance's site. Asked for when you sign in, for the one address you typed, so the extension can reach that instance's login and show its panel. Nothing is granted for a site you have not named.
• Storage. The items in section 3.
• Side panel. To show your Player One chats beside the page.
• Alarms. To restore the connection to your instance after your browser has put the extension to sleep.

The extension does not sell or transfer your data to third parties, does not use it for advertising or for any purpose unrelated to its single purpose above, and does not use it to determine creditworthiness or for lending.

8. Children

The extension is not directed at children under 16, and we do not knowingly collect their data.

9. Changes

We will update this page when the extension changes what it stores, sends or asks for, and the date at the top will say when. Material changes are announced in the extension's listing.

10. Contact

Write to hello@1p.dev. Your rights over data held in a hosted instance, and how to exercise them, are in our main privacy policy.