When safety features need it
The supplied brief describes live location for SOS and overdue-arrival alerts. Background access, precision and retention need confirmation from the app team.
SAFETY SHOULD COME WITH CLARITY.
Data Safety
A plain-language overview of data used by the described features, with the details that still need confirmation.
Emergency recording
SOS is described as recording and uploading emergency audio. The exact trigger, consent, storage, access and deletion controls must be documented.
Information that can help
The QR profile may expose selected emergency information to a bystander. The final policy must identify precisely which fields are visible and to whom.
Your request, by email
Submitted form fields go to contact@pukaaralert.com. The forms do not ask for passwords, OTPs, payment information or identity documents.
Protection used by these website forms
The implementation validates requests on the server, uses a request-verification token, applies submission limits and prevents visitors from choosing the email recipient. Use HTTPS when deploying. The form handler does not create a database of message content; copies may remain in the receiving mailbox and hosting or email systems.
What still needs verification
- The full list of app data types, SDKs and service providers.
- Encryption, storage locations, access controls and retention schedules.
- Any analytics, advertising, data sale or other sharing practices.
- Age requirements and parent or guardian consent.
- The scope and timing of account and data deletion.
This page is not a completed Google Play Data safety declaration or Apple App Privacy disclosure. Those submissions must match the app implementation.