Your LWA Client ID, Client Secret, and refresh token are encrypted with AES-256 (via the Fernet scheme) before they ever touch our database. The encryption key is generated once and stored only as a server configuration value — never in the database itself, and never alongside the data it protects. If our database were ever exposed, the credentials inside it would be unreadable without that separate key.
Amazon's system actually involves two credentials, and it's worth knowing the difference:
This means the credential that's actually persisted is only ever used to mint a temporary one — never used directly against Amazon's order or solicitation endpoints.
Once saved, the Amazon connection screen shows only a masked version of your Client ID (enough to recognise it's the right one) and a connection status. The Client Secret and refresh token fields are always blank — leaving them blank when you save just means "keep the current value," so you never need to re-enter something you've already stored.
If you revoke ReviewLoop's access in Seller Central, the very next daily run will detect it immediately (Amazon returns an explicit error for a revoked or invalid token). We pause your billing automatically, stop attempting further runs, and email you — you're never charged while disconnected, and the moment you re-enter valid credentials, the next scheduled run picks up normally.
Your ReviewLoop account password is hashed with bcrypt before storage — a one-way transformation designed specifically so that even we can't recover your original password from what's stored. Signing in checks your password against that hash; it's never stored, logged, or emailed in plain text.
Have a question this page doesn't answer? See our Privacy Policy or get in touch.