Security & privacy
The rules hold,even under pressure.
The app is the interface. Gateora's server decides who may approve, who may enter and who may access sensitive data—then records every action.
Security guarantees
Protection at every layer.
Isolation, approval, privacy and accountability are enforced together—not added as optional controls after the fact.
Tenant isolation
Each organisation's data is separated and every request is authorised on the server. Cross-community access attempts are refused and logged.
Approval you can trust
Approval and entry are separate, atomic steps. A visitor can be checked in only once, and only while the approval is valid.
Privacy by default
We collect the minimum visitor data, mask phone numbers in lists, never put photos in notifications, and delete data on a retention schedule.
Complete audit trail
Approvals, entries, exits, overrides and administrative changes are recorded in append-only logs.
Signed offline passes
Offline passes are cryptographically signed, bound to one device and usable once. Anything suspicious is flagged for review.
No billing lock-out at the gate
If a payment fails, gates keep working and your data stays safe. Only adding new communities, flats or staff is paused.
Operational controls
How protection works in practice.
Concrete safeguards across access, storage, emergencies, retention and support.
- Access control
- Deny-by-default authorisation on every request. Roles are scoped to an organisation, community, gate or flat, and the server re-checks the selected role each time. Suspended or ended memberships lose access immediately.
- Data in transit and at rest
- All traffic uses HTTPS with HSTS. Sessions on mobile are kept in the device's secure keystore. Invitation tokens and guest codes are stored only as hashes.
- Visitor photos
- Uploaded to private storage, checked to be real images, and served only through signed links that expire in five minutes after a permission check. Every view is logged.
- Emergency overrides
- Restricted to roles each community chooses, require a reason and incident reference, notify management immediately and enter a mandatory review queue.
- Retention
- Visitor photos are deleted after the community's retention window (30 days by default). Expired notification tokens and old operational data are cleaned up automatically.
- Support access
- Our team cannot browse your data. Time-limited support access must be approved by your organisation's owner, exposes only operational counts and is fully audited.
Authorisation
Protection
Private media
Controlled exception
Lifecycle
Accountable support
Indian privacy law
Privacy under the DPDP Act, 2023.
Your organisation decides why and how resident and visitor data is used, making it the data fiduciary. Gateora processes that data only to run the service as your data processor.
Read our privacy policy or contact our grievance officer.
- Purpose-limited collectionOnly the visitor information needed to operate the service.
- Controlled retentionConfigurable schedules for visitor data and private photos.
- Access and erasureProduct workflows that support privacy requests and controlled exports.
Responsible disclosure
Report a vulnerability
Send steps to reproduce without accessing other people's data or disrupting the service. Our team will review your report.
Make every entry an approved entry.
See Gateora with your own towers, gates and shifts. We will set up a pilot for your community.