Privacy Policy. What Satin keeps about you, why, and how to have it deleted.

Satin is operated by Pranav Goswami, in Ahmedabad, Gujarat, India. We’re setting up an Indian private limited company to run Satin; once it’s registered, this policy will name it. In this policy, “Satin”, “we” and “us” mean the operator.

For anything about your data, including requests and complaints, email [email protected]. Our grievance officer is Pranav Goswami, at the same address. For help with the product, email [email protected].

It covers three things Satin runs, each described separately below:

• the website, usesatin.com, including the beta waitlist and the private-beta login,
• the Satin Chrome extension, Satin for People,
• the developer portal, for teams bringing OwnUX to their product, in private beta.

The OwnUX SDK runs inside other companies’ products. There, that company decides what happens to its users’ data, and its own privacy policy applies. The SDK keeps your settings in your browser and sends nothing to Satin unless you choose to share your preferences with that product through DNA Share.

The beta waitlist

When you join the waitlist, we store your name and email address, whether you’re a person or a product team, which app you use most (if you tell us), which page you joined from, and when. If you join again with the same email, we update your entry rather than add a second one.

To stop abuse, we count how often the form is used from each network address. We store only a keyed, one-way scramble of the address (a hash), never the address itself.

Analytics

We use Vercel Web Analytics to count page visits. It doesn’t use cookies. Vercel processes each visit, including your IP address, to produce counts, and we see only totals. We use no other analytics, advertising or tracking tools.

Photos and fonts

Some example portraits on the website load from Unsplash, which receives your IP address when your browser fetches them. Fonts are served from usesatin.com itself.

Hosting logs

Vercel, which hosts the website, keeps request logs that include IP addresses and the pages requested, for the time its plan sets.

Only people we’ve invited can log in, and only with Google. Our website handles the login itself. When you log in, Google shares your name, email address and profile picture, and confirms the address is yours. If the address isn’t on our invitation list, we turn the login down and keep nothing about it. If it is, we keep:

• your name, email address and the link to your Google account, but not your profile picture or the sign-in tokens Google issues,
• your login sessions, without your IP address or browser details.

We never see your Google password. We also keep:

• the list of email addresses that may use the beta, and whether each may use Satin for People, Satin for Products or both,
• a short record of each login (which account and session, and when it ends), so a session only counts if it came through our own login page,
• a log of every change an admin makes to someone’s access: who, what and when.

Logging in sets cookies that keep you logged in (see Cookies). When you open the developer portal from the website, our server signs a short-lived note saying who you are, and your browser passes it to the portal in a form, never in a web address.

What stays on your computer

Your settings stay in your browser: the sites you turned Satin on for, your Interface DNA (your display and working preferences, such as spacing, layout, words, text size, contrast and motion), the last 20 changes to them, extension settings, and a log of the last 500 changes Satin made in your work apps (what kind of change, the outcome, the time and the task’s ID, never its title or description). Your long-lived work-app sign-in is kept encrypted, with a key that can’t be copied out of the browser, and the short-lived one only in memory.

What it reads, and why

Satin runs only on sites you turn it on for, and the only sites it can ask for are Jira Cloud and Linear, their APIs and Satin’s own account service. On those sites it reads the page’s address, the position and size of the app’s own notices (never their text), one OwnUX setting the page may publish, and your browser’s display settings, so it can draw its panel in the right place and style. Your tasks come from the app’s official API, using your own sign-in, and go straight to your screen. They never reach Satin’s servers.

What leaves your computer

• To Jira or Linear: requests for your tasks and the changes you confirm, plus a small “am I still connected?” check at most every 15 minutes for sites you used in the last week.
• Through Satin’s sign-in relay (Jira only): when you connect Jira, the relay passes Atlassian’s sign-in codes and tokens through, adding Satin’s app secret. It stores none of them and keeps no request logs.
• To Satin, only if you choose: your Interface DNA, if you turn on sync; your sharing choices, if you open sharing controls; and the address of the current site, if you ask Satin to check whether that product supports OwnUX.

Nothing else is sent: no analytics, crash reports, advertising or remote code. “Delete everything” in the extension removes everything it stored and gives back its site permissions; uninstalling removes it too. The full list of permissions is on Extension permissions.

The portal is for product teams in the private beta. You reach it from the website’s login. It keeps:

• your account: your email address and a display name taken from it,
• your teams, who belongs to each and their roles, and invitations to join a team (kept for 7 days),
• your team’s applications, their settings and keys. Keys are shown only by their last four characters,
• proof that your team controls a website, if you add one,
• a log of who changed what in the portal, and when, never a secret value (kept for a year),
• a scrambled record of each login handed over from the website, so each works once, kept until it expires.

Sign-in tokens, codes and links are stored only as one-way hashes, and the portal’s own logs carry no email addresses, tokens or settings. If you use sync or DNA Share, the account service also keeps your Interface DNA and the sharing choices you make.

Some preferences, such as larger text, higher contrast or reduced motion, could hint at a disability. They stay on your computer unless you turn on sync or choose to share them with a product, one part at a time. We never use them for anything except showing your apps the way you asked.

• To run the waitlist and invite people to the beta, because you asked to join.
• To let invited people log in, and to decide on our servers what each person may open.
• To provide what you turn on: the extension’s features, sync, sharing and the portal.
• To keep the service secure and stop abuse, for example with rate limits and the admin change log.

We don’t sell your data, use it for advertising, or build profiles of you.

Only the services that run Satin for us, each for its own job:

• Vercel hosts the website and its analytics, and will host the account service and portal.
• Neon stores our databases, including the login records.
• Google handles “Continue with Google”.
• Unsplash serves some example photos on the website.
• Resend will send the account service’s emails, such as team invitations, when those are switched on. During the private beta it sends none.

Atlassian (Jira) and Linear receive your requests when you use the extension, because that’s where your work lives; their own privacy policies apply. We share data with authorities only when the law requires it.

The website’s database, which holds the waitlist, the beta access list and the login records, is on Neon, on Amazon Web Services in the United States (US East, North Virginia). The website runs in Vercel’s data centres. The account service and portal are planned for Vercel and Neon in Mumbai, India. The extension’s data stays on your computer unless you turn on sync or sharing.

This means some data is processed outside India. We choose providers that protect it with encryption in transit and access controls.

• Waitlist entries: until you ask us to delete yours, or we no longer need the waitlist.
• Beta access: until it’s removed, or you ask us to delete it.
• Your login account: until you ask us to delete it, or your invitation ends. Login sessions and our login records expire after at most seven days, and are cleared out after that.
• The admin change log: kept as the record of who changed access. Ask us, and we’ll remove your email address from it.
• Rate-limit counters: a few days.
• The extension: on your computer until you delete it, or uninstall Satin.
• Portal accounts: until you delete yours, which erases it at once. Invitations 7 days; the portal’s change log one year.

• Everything travels over encrypted connections (HTTPS).
• Access is checked on our servers on every request, and anyone not on the access list is refused by default.
• We never handle passwords for the website: you log in with Google.
• Login cookies are signed, so a copy of our database alone can’t be used to log in. The portal stores its tokens and codes as one-way hashes, and the extension encrypts your work-app sign-in.
• Our own logs leave out personal data, and admin access is limited to named people.

The website sets cookies only when you log in, and only the ones the login needs:

• the session cookie that keeps you logged in, for up to seven days,
• two one-time cookies during “Continue with Google” (up to ten minutes): one so the login can only finish in the browser that started it, and one that remembers whether you chose Satin for People or Satin for Products.

They’re sent only over secure connections, scripts on the page can’t read them, and they aren’t used for tracking or advertising. Analytics uses no cookies. The extension keeps its data in the browser’s extension storage, not in cookies.

You can ask us to:

• tell you what we hold about you, and give you a copy,
• correct it,
• delete it,
• stop using it where you gave consent, for example by leaving the waitlist. Withdrawing consent is as easy as giving it.

Email [email protected] from the address you used. We’ll confirm it’s you, act on your request, and tell you when it’s done. If you’re not happy with our answer, write to our grievance officer at the same address. You can also complain to the Data Protection Board of India.

In the extension you can delete everything yourself, at any time, from its settings. In the portal you can delete your account yourself.

Satin isn’t for anyone under 18, and we don’t knowingly collect their data. If you think a child has given us data, email [email protected] and we’ll delete it.

When we change this policy, we’ll update the date at the top. If a change matters, we’ll tell people on the waitlist and in the beta by email before it takes effect.

Satin, operated by Pranav Goswami, Ahmedabad, Gujarat, India. Privacy requests and complaints: [email protected] (grievance officer: Pranav Goswami). Help: [email protected]. Please read our Terms of Service too.