Member isolation
Every draft, uploaded file, listing profile, consent record and shop connection is associated with one application member.
ACCOUNT / OAUTH / DATA
The application separates member data, keeps credentials on the server and gives the seller direct controls for shop disconnection and account deletion.
Every draft, uploaded file, listing profile, consent record and shop connection is associated with one application member.
Passwords are processed with PBKDF2-SHA256 using a unique random salt and are never stored as readable text.
Member sessions use random tokens, one-way token hashes and HttpOnly, Secure, SameSite=Lax cookies with a seven-day maximum lifetime.
Shop authorization takes place on Etsy. AutoMenax does not ask for, receive or store the seller's Etsy password.
OAuth access and refresh tokens remain server-side and are encrypted at rest using AES-GCM.
Account and workspace write routes check request origin. Repeated failed sign-in attempts are temporarily limited.
The V1 connection requests only listings_r, listings_w and shops_r. It does not request listing deletion or shop-setting write permissions.
| Control | Implementation | Seller action |
|---|---|---|
| Shop connection | OAuth with PKCE, single-use state and an exact HTTPS callback | The seller reviews permissions on Etsy |
| Listing writes | Defined task and destination are shown before related requests begin | The seller explicitly confirms the task |
| Disconnect | Stored connection tokens are removed and future application access stops | The seller disconnects in AutoMenax or revokes access on Etsy |
| Account deletion | Member account and associated application workspace records are deleted | The seller uses the account deletion control |
The detailed data categories, retention periods and member controls are published on the legal and connection pages.