Security
How we protect your shop and data
These controls are in place in the current release.
| HTTPS only | The site is served only over HTTPS with HSTS. Plain HTTP is redirected. |
|---|---|
| OAuth 2.0 with PKCE | Shops connect through Etsy's authorisation code flow with PKCE (S256). Your Etsy password is entered only on Etsy. |
| State validation | Each connection attempt uses a high-entropy, single-use state value that is tied to your account, expires after 10 minutes and cannot be replayed. |
| Encrypted tokens | Etsy access and refresh tokens are encrypted at rest with AES-256-GCM, bound to your account and shop, and refreshed only on our server. |
| Secrets stay on the server | API credentials, tokens and encryption keys are never placed in web pages, scripts, URLs or browser storage. |
| Least privilege | Only three Etsy permissions are requested: listings_r, listings_w, shops_r. See Etsy connection. |
| Account isolation | Every request is checked against the signed-in account and its one connected shop. A shop can be connected to only one account, and listings outside your shop are refused. |
| Passwords | Stored only as salted PBKDF2-SHA256 hashes. Sign-in, sign-up and reset attempts are rate limited. |
| Sessions and forms | HttpOnly, Secure, SameSite cookies; every form that changes data carries a per-session protection value and is checked for its origin. |
| Write safety | Each change needs an explicit confirmation on a review screen and can be sent only once. |
| Restricted logs | Logs never contain passwords, tokens, authorisation codes or form contents. |
Reporting a problem
If you think you found a security issue, email support@alpomera.com with the subject "Security". Please do not test against other users' accounts or shops.