Role-based permissions
Permissions are attached to roles and scoped by site, zone and function.
Security
Security is a property of the platform.
Permissions, verification and audit trails are part of how Zipr works day to day — not a hardening exercise applied before go-live.
- Access
- Role-based and scoped
- Identity
- Configurable verification
- Infrastructure
- WAF and edge integration points
- Evidence
- Operational audit trails
Posture
What we design against.
Destination platforms carry an unusual combination: public-facing sales surfaces, physical access decisions, cash handling and a large, changing workforce. Each of those is a different kind of exposure.
Our controls are organised around that reality — who may act, on what, from where, and what record that action leaves.
Least privilege by default
Rights are granted to a role, a scope and a period.
Identity before access
Verification workflows precede deployment and entry.
Everything leaves a trail
Operational events are logged with actor and device.
Identity & access
Who may do what, and until when.
Time-bound access
Access rights can be bound to a shift or booking window so they lapse automatically.
Identity verification
Verification workflows for guests, staff and contractors, including Satyapan-style checks where a deployment enables them.
Approval chains
Sensitive actions can require a second approver, configured per operation.
Infrastructure
Protection at the edges.
Public surfaces, administrative surfaces and device endpoints each have a different threat profile and a different control set.
Filter at the edge
Web application firewall
Integration points for WAF and edge filtering in front of public surfaces.
Transport security
Encrypted transport between surfaces, services and devices.
Device trust
Gate and POS devices are registered and attributable.
Monitoring
Operational and security-relevant events are collected for review.
Specific providers, hosting regions and configurations are agreed per deployment. This page describes platform capabilities and integration points; it is not a certification statement.
Operations
How a control stays true.
- 1
Configure
Roles, scopes and verification requirements agreed at onboarding.
- 2
Operate
Rights granted and withdrawn as shifts and bookings change.
- 3
Review
Access reviews run against the live permission model.
- 4
Respond
Incidents follow the escalation matrix agreed with your team.
We do not publish certification claims on this website. Where a procurement process requires evidence of our security posture, we share current documentation directly with your team under a confidentiality agreement.
What we can provide during procurement
- A description of the deployment architecture proposed for your environment.
- The data categories processed by each module in scope.
- Retention, access and deletion arrangements for that data.
- The incident response and escalation process that would apply.
- Current third-party attestations held at the time of the engagement, where applicable.
Reporting a vulnerability
If you believe you have found a security issue in a Zipr deployment, contact us at security@zipr.in with enough detail to reproduce it. We will acknowledge receipt and keep you informed while we investigate.
Bring your security questionnaire.
We would rather answer it properly than publish a badge.