Trust and transparency
How ZonRaseed protects seller data
A description grounded in controls present in the current codebase, with production evidence gaps kept explicit.
Last updated: August 23, 2026
Amazon data we read and why
We read orders, settlements, fees, inventory and listing reports—and Ads data when connected—to calculate profit, monitor stock and produce alerts. We do not ask for your Seller Central password; connections use official OAuth.
What we do not do with your data
We do not sell personal or Amazon data, build advertising profiles from it, or put full financial details or tokens in push payloads. We do not claim certifications, penetration tests, or SLAs that do not exist.
Encryption and tenant isolation
Production web traffic uses HTTPS. Sensitive OAuth and push tokens are application-encrypted in authenticated envelopes bound to the tenant/device. Data access uses RLS and a server-derived workspace scope. General at-rest encryption and backups depend on the database provider configuration and are not presented as an independent guarantee without production evidence.
Retention, deletion and disconnection
A verified workflow exists for account/workspace deletion, and disconnecting Amazon stops new access. Sensitive requests are reviewed and audited. Final backup-cycle and legal-retention periods require operational and legal approval before public launch.
Open production requirements
- Document backup/restore configuration and complete a restore exercise.
- Human legal review of policies and retention periods.
- Independent penetration test if it will be marketed; none is claimed today.
- Live verification of email, push, and monitoring providers with production credentials.