Security posture
Zelluvo is designed for business ecommerce workflows where store access, supplier credentials, marketplace tokens, customer orders, and operational labels need careful handling.
Legal
Security
The safeguards Zelluvo uses to protect accounts, integrations, and ecommerce operations data.
Last updated 4 July 2026
Access control
Accounts, platform admin tools, store permissions, and operational actions are separated so users should only access the stores and workflows assigned to them.
Credential handling
OAuth tokens, supplier passwords, API keys, and production credentials are handled through secured app flows. Zelluvo does not intentionally place them in public pages, routine exports, screenshots, or unsafe logs.
Transport security
The hosted Zelluvo service uses HTTPS to encrypt browser sessions, form submissions, API calls, and connected workflows in transit.
Auditability
Sensitive workflows maintain audit records for actions such as connection changes, stock updates, order operations, admin access, and support-sensitive activity.
Operational safeguards
High-impact actions use safeguards such as previews, explicit approval, confirmations, limits, and duplicate protection where appropriate.
Backups and recovery
Zelluvo may use backups and operational recovery processes to protect availability and support incident recovery.
Incident response
If Zelluvo becomes aware of a security incident affecting customer data, we will investigate, contain, remediate, and notify affected customers where legally required.
Customer responsibilities
Customers should use strong passwords, limit admin access, remove departed users, keep supplier credentials current, review automation settings, and report suspicious activity quickly.
Reporting
Report security concerns through the contact page without including secrets, buyer exports, or live credentials in the initial message.