Account access
The public service uses HTTPS. Passwords and recovery keys are stored as hashes rather than readable account credentials. Production sign-in cookies are HTTP-only and Secure, and sessions have an expiry. You can view sessions and revoke other sessions from your account.
Optional passkeys use a public key stored by FeedGuard; the private key and device biometrics are not sent to the application. Keep your recovery key private and use a unique password. Account recovery replaces the recovery key and invalidates existing sessions and passkeys.
Data & store actions
Saved catalogs and reports are scoped to your signed-in account. The application checks access on the server; operational administrators may access underlying systems when needed to maintain the service or handle incidents.
Supported store changes require product-edit permission, an exact preview and your separate confirmation. A scheduled check is a read operation and does not authorize product edits. Store integrations may be unavailable; the connection screen shows the current capability.
The standalone CSV comparison processes its files locally in the browser. The saved account workspace sends data to the server. These have different storage behavior, explained in Privacy.
Service limits
These controls do not eliminate all risks or guarantee uninterrupted access. Keep your original files and needed downloads. The service is not intended for regulated or highly sensitive data. We do not offer a certification, data-residency guarantee or guaranteed recovery time through the current free service.
Removing active account data does not immediately remove provider logs and backups. A hash of the email used for the free allowance can remain after closure. See storage and removal for details.
Report a concern
Use the public contact page to report a security concern without signing in. Send a concise description and safe reproduction steps. Do not include passwords, tokens, recovery keys or other people’s data.