Repute legal / Security

Security and Retention

How Repute approaches access control, private document storage, retention, and customer safeguards.

Back to homepageLast updated: June 2026

Product-level notice

Plain language for building teams.

Need help with a customer-specific position?

hello@repute.ae
This page is product-level information for Repute. It is not legal advice and should be reviewed by qualified counsel before it is relied on for a customer-specific compliance position.

01

Role-based access

Repute uses role and building-scoped access. Repute admins create customer organizations, customer managers manage their organization, and staff accounts are limited to the guard workflow and assigned buildings.

02

Private documents

Where document images are captured, they are stored privately and accessed through secure routes or temporary signed URLs. Identity images are not sent to an LLM.

03

Retention posture

Visitor log retention is designed to follow configured production policy and customer arrangements. Staff-facing mobile views are intentionally limited to recent records.

04

Customer safeguards

Customers should restrict admin access, remove departed users promptly, train guards and managers, avoid shared credentials, secure shared lobby tablets, and report suspected unauthorized access quickly.

05

Limits

No system can remove all security risk. Repute depends on correct customer configuration, secure devices, network availability, cloud providers, authentication providers, and user review of captured records.

Repute is owned and operated as a sub-product of AISH CAPITALS FZCO. For legal or privacy questions, contact hello@repute.ae.