ReviewLoop is a published application on the Amazon Selling Partner Appstore. You approve it from inside Amazon's own authorisation screen, and Amazon passes the access back to us directly — there is no Client ID, Client Secret or token for you to find, copy or paste anywhere, and nothing sensitive ever passes through your hands or your email.
What Amazon returns is a refresh token, and it's encrypted with AES-256 (via the Fernet scheme) before it ever touches 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, what's 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.
The Amazon connection screen shows a connection status and nothing else — no token, no identifier, not even a masked one. There's nothing to leak over your shoulder, and nothing for you to keep track of.
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 reconnect, 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.