Important Safety Notice
MeetSafe is not an emergency service. MeetSafe does not contact police, ambulance, fire, emergency numbers, or emergency services for you.
Alerts, reminders, notifications, SMS messages, location services, device permissions, networks, and responder availability can fail or be delayed. If you are in immediate danger or need urgent medical help, call your local emergency services now.
Data We Collect
We collect information needed to run MeetSafe and provide safety check-in features.
- Account email address and authentication identifier.
- Name or display name if you provide it.
- Safety contacts entered by you, such as contact name, phone number, email address, invite status, and app relationship status.
- Safety session or rendezvous details, such as title, date and time, duration, selected contacts, address or location details, meeting details, notes, mode, and settings.
- Check-in, check-out, missed check, Not OK, request-help, responder-opened, responder-resolved, and other safety event status.
- Device notification tokens and push notification data, including Firebase Cloud Messaging or Apple Push Notification service delivery metadata.
- Location or address information if you enter it or enable a feature that captures it. MeetSafe does not use location to continuously track you in the current submitted build.
- Basic technical logs needed to operate, debug, protect, and secure the service.
How We Use Data
- Provide safety check-ins, reminders, check-in and check-out state, and assistance workflows.
- Notify your selected safety contacts when a safety workflow is triggered.
- Support account, session, device, and trusted-contact functionality.
- Show authorized responders limited session context when needed for an assistance event.
- Improve reliability, security, abuse prevention, and support.
Safety Contacts And Sharing
You choose the safety contacts used for a session. When a safety workflow is triggered, MeetSafe may share relevant information with those selected contacts so they can understand and respond to the alert.
Depending on the session and app state, a selected contact may see details such as your name, session title, relevant times, address or location details you entered or enabled, notes, assistance status, and your phone number if you saved it and chose to share it with responders.
Public alert surfaces, such as push notifications and SMS messages, are designed to stay generic where possible and avoid sensitive session details.
Service Providers
We use service providers to operate MeetSafe. They process information for us so the app and website can work.
- Firebase and Google services for authentication, database, cloud functions, messaging, logs, and hosting-related infrastructure.
- Apple and Google platform services for app delivery, app review, mobile operating-system features, notifications, and account platform services.
- Twilio or a similar SMS provider if SMS fallback or SMS testing is active for eligible or feature-gated flows.
Ads And Payments
MeetSafe does not currently show ads and does not sell personal information.
The current submitted build is free/testing and does not currently unlock a paid subscription inside the app. If paid subscriptions or payment features are added later, payment processing may be handled by Apple, Google, Stripe, or another payment provider, and this policy will be updated as needed.
Location And Address Data
If you enter an address, venue, meeting location, notes, or similar session context, MeetSafe may store and use that information for the safety session and for notifications to selected contacts when a safety workflow is triggered.
If you enable a location-related feature, MeetSafe may use that location information for the related safety workflow. Location availability depends on device permissions, device state, network conditions, and operating-system behavior.
Security
We use reasonable technical and organizational safeguards to protect MeetSafe data. Data is encrypted in transit where supported by the relevant app, browser, platform, and service provider.
No online service can guarantee complete security. Notifications, SMS, providers, devices, networks, permissions, and responder behavior can fail or be delayed.
Data Retention
We retain information while your account or app use continues and as needed to provide MeetSafe, support safety history, troubleshoot issues, maintain security, prevent abuse, comply with legal obligations, resolve disputes, and protect users and the service.
Responder access to private assistance details may be limited in the app even where backend records are retained for safety, audit, legal, or operational reasons.
Account Deletion And Data Deletion
You can request account deletion or personal-data deletion by emailing developer@meetsafe.io. Include the email address associated with your MeetSafe account so we can locate it.
If your installed version includes in-app account deletion, you may also be able to start deletion from Profile or account settings inside the app.
Some information may be retained where required or reasonably needed for legal, safety, security, fraud-prevention, dispute, tax, compliance, backup, or audit reasons.
A public deletion request page is also available at meetsafe.io/account-deletion.
Children
MeetSafe is not intended for children. Do not use MeetSafe if you are not old enough to use it under the laws that apply to you or without any required parent or guardian consent.
Changes
We may update this Privacy Policy as MeetSafe changes. If we make material changes, we will update the date above and provide notice where required.
Contact
For privacy, account deletion, or data deletion requests, email developer@meetsafe.io.
Postal address:
MeetSafe
PO Box 5032
Victoria Point QLD 4165
Australia