1. Data we collect

• Account and role data: profile details, role, site/building/unit assignments, and onboarding status needed to run access control workflows.
• Access and operations data: invite and visit verification data, incident details, and audit records generated as you use the app.
• Camera data for QR scanning: camera access is used by security personnel to scan visitor QR codes. In this flow, camera frames are used for live scan processing and are not used as a photo/video gallery feature.
• Location data for SOS: if you trigger SOS and grant location permission, the app may attach your current GPS latitude/longitude, accuracy, and capture timestamp to the SOS alert.
• Push notification data: device push token and platform metadata so we can deliver operational alerts (for example, SOS updates).
• Local app storage: secure authentication tokens and limited local settings (for example, selected assignment filters) stored on your device.
• Marketing website analytics: page usage data may be collected via privacy-focused analytics to understand website performance.

2. How we use data

• Operate visitor verification, incident response, and audit logging.
• Enable SOS workflows, including optional location attachment at trigger time.
• Authenticate users, secure sessions, and prevent unauthorized access.
• Send operational push notifications relevant to your role.
• Monitor service quality, troubleshoot issues, and improve reliability.

3. Data controller and sharing

For most deployments, the estate, property manager, or organization operating the site is the Data Controller because it determines why and how personal data is used for access control and security operations. EntryGuard generally acts as a Data Processor on that organization's documented instructions.

We share data with your organization's authorized operators (such as estate admins and security personnel) to provide the service. We may also share data with service providers that support hosting, notifications, analytics, and infrastructure security. We may disclose data where required by law or to protect safety and legal rights.

4. Data retention

We retain personal data for as long as needed to provide the service, maintain security and audit trails, meet contractual obligations, and comply with applicable law. Retention periods can vary by deployment and customer requirements.

5. Your choices

• You can deny camera permission, but QR scanning features will not work.
• You can deny location permission, but SOS alerts may be sent without live GPS coordinates.
• You can disable push notifications in device settings.
• You can request account-data updates or deletion through your administrator or by using our account deletion request page.

6. Security

We use technical and organizational controls designed to protect personal data. However, no system is completely secure, and you should also protect your device and account credentials.

7. Children's privacy

EntryGuard is intended for operational use by authorized users and is not directed to children.

8. Policy updates

We may update this policy from time to time. Material changes will be reflected on this page with an updated effective date.

9. Contact

For privacy questions or requests, contact support@entryguard.app, use our contact form, or book a call.