How SafeSociety approaches personal data.
This page explains, at a high level, what kinds of information may be processed to support visitor management, resident approvals, society operations, and related platform communication.
Information we may process
Depending on the workflow, SafeSociety may process resident account details, society and flat mapping data, visitor names and phone numbers, visitor photos when captured for gate operations, staff assignment information, device identifiers used for push notifications, and operational logs required to support entry events.
Why the information is used
- To authenticate users and protect account access.
- To let guards create and manage visitor or staff entry records.
- To let residents review relevant activity connected to their flat.
- To send operational notifications related to visitor approvals, staff entries, or society activity.
- To maintain service reliability, fraud prevention, auditability, and support workflows.
Access and sharing
Data access should remain limited to the product operators, society stakeholders, and service providers needed to run the workflow. SafeSociety is designed around flat-level relevance and role-based access so operational information is not broadly exposed across unrelated users.
Retention and security
Operational records may be retained for as long as needed to support society management, dispute resolution, auditability, compliance, or platform support. Appropriate technical and organizational safeguards should be maintained to protect stored data and limit unauthorized access.
Launch note
Before public release, this policy should be reviewed and finalized with your actual operating entity details, support contact, retention rules, jurisdiction-specific disclosures, and any third-party subprocessors used in production.