OAuth 2.0 + PKCE (S256) Security Architecture
LoomSync Studio implements Etsy Open API v3 authentication strictly using OAuth 2.0 Authorization Code Flow with PKCE (code_challenge_method=S256) and cryptographic CSRF state verification. Every token exchange and storage operation executes exclusively on hardened backend servers.
PKCE code_verifier & state CSRF Generation
Before redirecting a Seller, the backend generates a cryptographically random 64-byte code_verifier, computes its SHA-256 code_challenge (code_challenge_method=S256), and binds a single-use CSRF state nonce to an HttpOnly, Secure session cookie.
Official Etsy OAuth 2.0 Consent Redirect
The Seller is redirected to https://www.etsy.com/oauth/connect requesting only declared scopes (shops_r, listings_r, listings_w, transactions_r, transactions_w). LoomSync Studio never handles or views the Seller's Etsy password.
Constant-Time State Check & Server-Side Token Exchange
Upon callback, LoomSync verifies the state parameter in constant time, rejects replayed callbacks, and exchanges the authorization code plus raw code_verifier directly server-to-server over TLS 1.3 against https://api.etsy.com/v3/public/oauth/token.
PostgreSQL AES-256-GCM Envelope Encryption
The received access_token and refresh_token are wrapped immediately using AES-256-GCM authenticated encryption with per-record IVs and KMS-managed envelope key rotation, then persisted strictly inside an isolated VPC PostgreSQL cluster.
Zero-Exposure Browser Session Cookie
The Seller's browser receives only an opaque, signed HttpOnly; Secure; SameSite=Lax session identifier. Etsy OAuth tokens never enter browser memory, JavaScript state, localStorage, sessionStorage, or third-party telemetry.
Encryption & Zero-Exposure Infrastructure Controls
Every OAuth access_token and refresh_token is encrypted using per-record Data Encryption Keys rotated via KMS.
All Seller traffic, Etsy Open API v3 requests, and database channels enforce TLS 1.3 with perfect forward secrecy.
Tokens never touch browser localStorage, client API responses, or analytics scripts; sessions use HttpOnly cookies.
Strict compliance with Etsy API Terms TTL limits; automated cache invalidation on webhook/manual sync or disconnect.
How to Disconnect Your Etsy Shop & Revoke OAuth Tokens
Sellers retain full, frictionless control over Etsy API authorization at all times. You may disconnect your Etsy shop and revoke all OAuth 2.0 tokens using either method below:
Method A: Inside LoomSync Studio
In-App Control- 1Sign in to your LoomSync Studio workspace.
- 2Open Integrations from the top navigation or workspace sidebar.
- 3Locate your Connected Etsy Shop card (displaying your Shop Name and Shop ID).
- 4Click "Disconnect Shop & Revoke Token".
- 5Confirm immediate data purge in the modal to invalidate OAuth tokens and queue full API cache & Buyer PII deletion within 24 hours.
Method B: Inside Etsy Shop Manager
Etsy Native Control- 1Sign in to your Etsy account at etsy.com.
- 2Open Shop Manager from the top navigation bar.
- 3Navigate to Settings -> Apps in the left Shop Manager menu.
- 4Select the Connected Apps tab to view authorized third-party applications.
- 5Locate "LoomSync Studio" in the list of connected apps.
- 6Click "Disconnect" to revoke all Etsy Open API v3 OAuth grants immediately.
Right to Erasure (GDPR Art. 17 / CCPA) & Purge SLAs
Automated deletion of all cached listings, receipts, and Buyer PII within 24 hours of OAuth disconnect or revocation.
Rolling Buyer PII anonymization/purging after order fulfillment (mandatory statutory tax invoices masked of non-essential PII).
Written GDPR Art. 17 / CCPA erasure confirmation delivered via compliance@loomsyncstudio.site.
Under GDPR Article 17 (Right to Erasure) and the California Consumer Privacy Act (CCPA/CPRA), Sellers and authorized representatives may trigger immediate shop disconnection and permanent Buyer PII deletion using the self-service workflow below or by emailing compliance@loomsyncstudio.site.