Security

What is in place, and what is not yet

This is our own trust page, not something Etsy asked us to publish. It lists the controls that are actually implemented and marks the ones that are still planned, because a list that only shows the good parts is not worth reading.

HTTPS only

in place

The website and the OAuth callback are served over HTTPS.

Secrets stay on the server

in place

The API keystring, shared secret, access token and refresh token never leave the server. They are not placed in HTML, JavaScript, URLs or browser storage.

Authorization Code flow with PKCE S256

in place

The Etsy connection uses the authorization-code flow with a PKCE code challenge, as Etsy Open API v3 requires.

Single-use state value

in place

A high-entropy state value is generated for each attempt, bound to the account that started it and validated when Etsy returns.

Per-account and per-shop isolation

in place

Every record is scoped to the account and the shop it belongs to; one account cannot read another account's shops.

Least-privilege scopes

in place

Only the scopes listed on the Etsy connection page are requested.

Confirmation before a write

in place

The destination shop, the listing and the operation are shown before a write request, and the result Etsy returns is displayed as it is.

Update verification

in place

After an update, what Etsy returns is compared with what was sent. A field Etsy did not apply is reported as a failure instead of being shown as a success.

Rate-limit handling

in place

Rate-limit responses are honoured with bounded backoff, and the rolling daily quota is respected.

Two-factor sign-in

in place

Available on application accounts.

Encrypted tokens at rest

planned

Tokens are held in a database file restricted at the operating-system level on a single-tenant server. Field-level authenticated encryption is planned before public sign-up opens.

Self-service account deletion

planned

Disconnecting a shop already deletes its tokens and its cached Etsy data. Deleting a whole account is handled on request by email today; a self-service control is planned.

Reporting a problem

If you find a security problem, write to support@fablenco.com with enough detail to reproduce it, and please give us a chance to fix it before you publish it. We will confirm that we received it and tell you when it is fixed.

We do not publish keys, secrets, tokens, server paths or other details that would only help someone attack the service, and we never put a credential in a page, in JavaScript, in a URL or in browser storage.

The term 'Etsy' is a trademark of Etsy, Inc. This Application uses Etsy's API, but is not endorsed or certified by Etsy.