Security posture
Zelluvo is designed for business ecommerce workflows where store access, supplier credentials, marketplace tokens, customer orders, and operational labels need careful handling.
Zelluvo
Security
How Zelluvo approaches protection of ecommerce operations data.
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 should be stored through secured app flows and never placed in public pages, support messages, exports, screenshots, or unsafe logs.
Transport security
Hosted Zelluvo should run behind HTTPS so browser sessions, form submissions, API calls, and connected workflows are encrypted in transit.
Auditability
Sensitive workflows should maintain logs for connection changes, stock updates, order actions, label workflows, admin access, and support-sensitive activity.
Operational safeguards
High-impact actions such as marketplace stock pushes, shipping labels, and automation rules should use previews, confirmations, limits, and duplicate protection.
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.