Responsible Party and Operator
For tenant operations, the security company, estate, HOA, or business using Pin My Guard is normally the Responsible Party because it decides why and how guard, resident, client, site, shift, incident, and panic data is processed. Pin My Guard acts as an Operator for that tenant data under contract.
Pin My Guard is the Responsible Party for its own website enquiries, marketing, platform administration, tenant administration, account administration, manual EFT billing administration, product analytics, support, and security logs.
Accounts and access
Names, email addresses, phone numbers, roles, company and role assignments, sign-in logs, device tokens, support access logs, and audit logs.
Security operations
Guards, sites, clients, residents, shifts, assignments, check-ins, check-outs, QR checkpoint scans, patrol routes, handover notes, and attendance data.
Location and panic data
Guard GPS pings during active shifts, patrol traces, panic/SOS GPS fixes, escalation records, missed-checkpoint warnings, and control-room responses.
Workforce and payroll
When a tenant uses the workforce tools: guard pay rates, including overtime and night, weekend and public-holiday premiums; attendance sign-offs with payable and overtime minutes, and payroll exports with gross amounts; employment details such as employee number, employment type, start date, supervisor, emergency contact and next of kin; time off and its reason; HR documents and offboarding records, such as the reason, effective date and whether equipment was returned; and PSiRA details exactly as the tenant enters them, such as registration number, grade, certificate expiry date, site qualifications and training records. Pin My Guard does not check these details with PSiRA.
Visitors
When a guard records a visitor at a site, or asks a resident to approve one: the visitor's name, phone number and vehicle registration if given, the purpose of the visit, who they are visiting, sign-in and sign-out times, whether entry was approved or refused, and when the visitor accepted the POPIA visitor notice. When a resident pre-authorises a visitor: the visitor's name, vehicle registration if given, the expected visit window and an access code or QR pass.
Incidents and evidence
Incident text, photos, videos, voice notes, AI voice-to-text transcripts, categorisation, priority suggestions, published reports, and client summaries.
Tenant administration, account records, and manual EFT billing
Tenant subscription state, package and add-on usage, administrative notes, invoice status, billing notes, manual EFT invoice records, payment allocation records, service records, and account support details needed to sustain the customer relationship. Pin My Guard does not collect card numbers or CVVs.
Analytics and AI
Usage analytics, platform health signals, risk forecasts, scheduling suggestions, GPS anomaly warnings, and AI-generated summaries when the tenant has switched those features on.
Website enquiries
When you send an enquiry or demo request from our website: company or estate name, contact name, work email, phone number if given, preferred contact method, province and city or area, approximate guard, site and resident numbers, rollout timeline, the package, add-ons and services you select, any notes you add, and when you agreed to this notice. Each enquiry is saved with a reference number so our team can reply. To limit repeated or automated submissions, we also keep one-way coded (hashed) versions of your email address and network (IP) address with a count of recent enquiries.
Bot protection
Our website and web portals use Google reCAPTCHA Enterprise, through Firebase App Check, to check that requests come from a genuine browser rather than an automated bot. To do this, Google processes technical information about your browser, device and connection, such as IP address and browser details. Google's Privacy Policy and Terms of Service apply to that check. The Guard and Resident phone apps use Firebase App Check with Google Play Integrity on Android phones, and Apple App Attest or DeviceCheck on iPhones, to check that requests come from a genuine copy of the app on a genuine device. To do this, Google or Apple processes information about the app and your device.
Purposes and lawful processing
- To provide guard management, live control-room operations, patrol proof, panic response, incident management, reporting, and client portal services.
- To help tenants manage visitor access at their sites and keep workforce, time-off, payroll-export and HR records when they use those tools.
- To perform tenant contracts, manage account records and manual EFT billing, support users, secure the platform, prevent misuse, and maintain reliable service delivery.
- To reply to website enquiries and demo requests, and to protect the website, enquiry form and web portals from automated abuse.
- To comply with legal, accounting, safety, labour, records, dispute, insurance, and security obligations that may apply to tenants or Pin My Guard.
- To send operational alerts, security notices, and product communications where allowed by law and user preferences.
- To provide AI-assisted categorisation, transcription, forecasting, scheduling, anomaly detection, and summaries only when enabled and subject to human review.
Who may receive information
- Authorised tenant administrators, control-room operators, managers, guards, residents, and clients according to role-based access controls.
- Emergency responders, armed response providers, medical responders, law enforcement, insurers, or regulators where required for safety, legal claims, or lawful requests.
- Approved service providers and Operators, including Firebase/Google Cloud, hosting, storage, messaging, analytics, monitoring, bot protection (Google reCAPTCHA Enterprise), maps, support, and approved AI providers.
- Clients through the client portal only when tenants approve published reports, summaries, patrol proof, or attendance summaries. Raw resident GPS and device tokens are not included in client reports.
Pin My Guard does not sell personal information.
Security and data minimisation
- Each tenant's data is kept separate, and access depends on each person's role and assigned sites.
- Guard GPS is collected only during active shifts. Resident panic GPS is collected only when panic/SOS is activated or as otherwise disclosed by the tenant app configuration.
- Incident evidence, voice notes, and patrol records are stored privately by default. Client publication requires an approved summary or report workflow.
- Access controls, least-privilege roles, audit logs, support access logs and private storage rules protect platform data. Automated bot checks help protect the website and web portals.
- External AI processing is disabled unless a tenant enables it after vendor, operator agreement, retention, and data residency review.
How long information is kept
Retention depends on tenant contracts, legal duties, safety investigations, accounting rules, labour requirements, disputes, and product configuration. Default periods are:
- Guard GPS pings: 90 days.
- Panic/SOS GPS and escalation logs: 24 months, with legal hold where needed.
- Incident reports and evidence: 36 months by default, with legal hold support.
- Published client reports: tenant contract period plus 12 months.
- Audit logs, support access logs, account records, and manual EFT invoices: 5 years or the legally required accounting period.
- AI transient processing payloads: no provider retention unless approved in writing.
Records are not yet deleted automatically, so some records may be kept for longer than these periods.
Data subject rights
POPIA gives data subjects rights to ask for access, correction, deletion or de-identification where lawful, objection to processing, withdrawal of consent where processing relies on consent, and complaint escalation. Requests about tenant operational data should usually be routed to the relevant tenant. Pin My Guard will help tenants respond where the data is stored in the platform.
Guard and Resident users can start a verified account and associated-data deletion request through the public Account & Data Deletion page. The page explains tenant-managed account boundaries, verification, lawful retention exceptions, and the human-reviewed support process.
You may also complain to the Information Regulator South Africa if you believe your personal information has been processed unlawfully.
Information Regulator (South Africa)
- Address: Woodmead North Office Park, 54 Maxwell Drive, Woodmead, Johannesburg, 2191
- Phone: 010 023 5200, or toll-free 0800 017 160
- General enquiries: enquiries@inforegulator.org.za
- POPIA complaints: POPIAComplaints@inforegulator.org.za
- PAIA complaints: PAIAComplaints@inforegulator.org.za
- Website: inforegulator.org.za
These details were taken from the Information Regulator's website on 1 October 2026. Check its website for any changes.
Access to information requests
Requests under the Promotion of Access to Information Act (PAIA) should be directed to the relevant Responsible Party's Information Officer. Pin My Guard will provide platform records to authorised tenant administrators or lawful request handlers when the request is valid, scoped, logged, and approved.
Customers, prospective customers and other requesters can send PAIA requests about records held by Pin My Guard to compliance@pinmyguard.com.
Cross-border and cloud processing
Pin My Guard runs on Firebase and Google Cloud and uses the South African africa-south1 region where the relevant product supports it. Some services, such as bot protection, sign-in and analytics, may process information outside South Africa. If a required service processes information outside South Africa, Pin My Guard and the tenant must use appropriate contractual, security, and transfer safeguards.
- Scheduled background jobs run outside South Africa, in Google Cloud's europe-west1 region in Belgium. They read and update the records they need there, such as shifts, patrols, SOS alerts, invoices and retention reviews, and send SOS alert notifications from there.
- Emails from Pin My Guard, such as account invitations and replies to enquiries, are sent through Google Workspace (Gmail), which may process them outside South Africa.
- Push notifications to Android phones are sent through Firebase Cloud Messaging (FCM). Notifications to iPhones are sent through Expo's push service and Apple's push notification service. These services may process notifications outside South Africa.
- Pin My Guard is operated from the United States. Its administrators manage the platform from there, so information they view or manage, such as company account, invoice and website enquiry records, is accessed from outside South Africa.
- Maps in the Company and Control Room web portals load map images from OpenStreetMap's public tile servers (tile.openstreetmap.org). Your browser sends these servers your IP address, browser details and the area of the map being shown, and they may process this outside South Africa.
Cookies and browser storage
Our websites keep a small amount of information in your browser. The web portals keep you signed in on that browser and remember choices you save, such as your Company start page and whether the Control Room SOS alarm sound is on. The enquiry form keeps an unsent enquiry in that browser tab for up to ten minutes while the page reloads to check your browser, and Company billing keeps the details of a proof-of-payment upload until it is recorded. Firebase App Check and Google reCAPTCHA Enterprise keep a short-lived verification token, and Google may set its own cookies for the bot check described above. The web portals use Firebase Performance Monitoring, which keeps an identifier for that browser to measure page speed. You can clear this information in your browser settings; you will then need to sign in again.
Incident notification
If Pin My Guard becomes aware of a security compromise affecting tenant data, it will notify the affected tenant as soon as reasonably possible and support the tenant's POPIA notification duties. Where Pin My Guard is the Responsible Party, it will notify the Information Regulator and affected data subjects as required.
Privacy contacts
Email privacy@pinmyguard.com for our registered name and address.