What the Satin extension can access. Every permission, and what it’s for, from the extension’s own manifest.
Satin for People is in development and not yet in the Chrome Web Store. Checked against its code on 25 October 2026; we update this page whenever that changes.
At install, nothing. Satin asks for no website access when you add it. Nothing runs until you switch it on, one site at a time.
One site at a time. You turn Satin on for one Jira Cloud or Linear site with a click. Chrome asks you to allow it.
Only two apps, ever. The only sites it can ask for are Jira Cloud and Linear, their APIs and Satin’s own account service. Not banking, payment or any other sites.
Tasks from the API, not the page. Your tasks come from the app’s official API. Satin doesn’t read them from the page.
No remote code. All of its code ships inside the extension. Its own pages run only their own scripts, with no eval.
No outside messages. No other extension or website can send it messages.
Delete everything. One button clears what it stored, forgets each sign-in and gives the site permissions back. Uninstalling removes what it stored too.
The five permissions it asks for. Requested when you add Satin. Website access is separate, below, and asked for only when you choose.
| Permission | What Satin uses it for |
|---|---|
storage | Keeps your preferences, the sites you turned on and your connection state on your own computer. |
scripting | Adds Satin’s panel only to the Jira or Linear sites you turn on, one site at a time, and removes it when you turn a site off. |
activeTab | When you click Satin’s toolbar button or use its shortcut, reads the current tab’s address to know whether it’s a supported site. |
identity | Signs you in to Jira (through Atlassian) or Linear, and, if you choose, to a Satin account, in Chrome’s own sign-in window. |
alarms | Checks that your connection still works, at most every 15 minutes and only for sites you used in the last 7 days. |
It also adds a keyboard shortcut, Alt+Shift+O, to switch between Satin and the app’s own view, and needs Chrome 140 or later.
Site access, only when you ask. Optional: Chrome asks you each time, from a click. These are the only sites the extension can ever ask for.
| Site | What for | When it’s asked for |
|---|---|---|
Your Jira Cloud site, such as your-team.atlassian.net | Shows Satin’s panel on that site. | When you turn Satin on there. Only the exact site you choose, never every Atlassian site. |
linear.app | Shows Satin’s panel in Linear. | When you turn Satin on there. |
api.atlassian.com | Reads your Jira tasks and makes the changes you confirm. | When you connect Jira. |
api.linear.app | Reads your Linear tasks and makes the changes you confirm. | When you connect Linear. |
| Satin’s account service | Syncs your preferences and lets you manage sharing. | Only if you turn on sync or open sharing controls. The account service isn’t hosted yet. |
What it reads on a site you turned on. Only these, and only there.
- The page’s address.
- The position, size and visibility of the app’s own notice elements, never their text.
- One page element, if present: the attributes of <meta name="ownux-enabled">.
- Your browser’s display settings: colour scheme, contrast, motion and language.
Tasks are not read from the page. An automated test checks this list against the code.
What it keeps on your computer. Not on Satin’s servers.
- The sites you turned on, as addresses only.
- Each connection: the site or workspace, its name, what it’s allowed to do and when you connected.
- Sign-in tokens: the long-lived one encrypted with a key that can’t be exported, the short-lived one in memory only.
- Your preferences (your Interface DNA), and the last 20 changes to them.
- A log of the changes Satin made for you: what, when, the task’s ID and the result. Never titles, descriptions or account IDs.
- Extension settings and connection health.
What leaves your computer, and to whom. Your task titles, descriptions and comments never reach Satin.
| Where | What is sent | When |
|---|---|---|
| The work app’s API (Atlassian or Linear) | Requests for your tasks, and the changes you confirm, with your own sign-in. | When you use Satin’s panel, plus one small “is this connection still working?” check at most every 15 minutes, for sites used in the last 7 days. |
| Atlassian’s or Linear’s sign-in | The standard sign-in, in Chrome’s sign-in window. | When you connect an app. |
| Satin’s sign-in relay (Jira only) | Atlassian sign-in codes and tokens, to which it adds Satin’s app secret. It stores nothing and keeps no request logs. | When you connect Jira, and when the sign-in is renewed. |
| Satin’s account service | Your preferences (with sync on), your sharing choices (when you open sharing controls), or the address of the current site with no sign-in (only when you check a share offer). | Only when you turn those on. Not hosted yet. |
AvailableNothing else is sent: no analytics, telemetry, crash reports, advertising or remote code.
Is the extension’s code public? Not yet.
Until it is, this page lists exactly what the extension can do, taken from its manifest and our internal data inventory. The security page explains how your work and sign-ins are protected, and what we can’t promise. Questions: [email protected].