Privacy policy

Who this policy covers

This policy applies to the SwiftGuard mobile apps (iOS and Android) and the website at https://swiftguard.app. SwiftGuard is a personal safety service. There is one kind of account: you can send SOS and you can help someone else.

SwiftGuard does not replace police, ambulance, or fire services. If you can, contact local emergency services as well.

Information we collect

Account. Phone number, phone country, email, and a password we store as a hash. We also keep last login time and whether the account is active.

Profile you choose to add. First name, last name, display name, photo, date of birth, gender, blood group, address, city, district, country, and emergency notes. These fields are optional except where the app requires a name or email to finish setup.

SOS alerts. Emergency type, whether the alert is private (My protectors) or public (nearby), title, message, photos you attach, location and accuracy when you send it, status (open, responding, resolved, cancelled, expired), and timestamps.

Live location. When you send SOS, keep an alert open, offer help, or use Nearby, we may collect latitude, longitude, accuracy, speed, heading, and battery level so people can find you or see what is near them.

My protectors. Who you connect with, how you connected (phone or QR), and the status of that connection. QR codes are stored as a hash and expire after a short time.

Help and notices. When someone responds to an SOS, we store that they accepted and, if they share it, their location. We also store in-app notifications (for example SOS, replies, connection requests, and public announcements).

Your device. A push token, device id, platform (iOS or Android), and app version so we can send alerts to this phone. Notification sound and similar preferences stay on the device.

Safety tools. If you report or block someone, we store that report or block so we can review it and keep you from seeing that person.

Technical logs. Our servers may record IP address, time, and request path when the app talks to the API. We use this to run and secure the service, not to build a marketing profile.

How we use it

We use this information to:

• Create and sign in to your account
• Send SOS to My protectors or nearby SwiftGuard users, depending on the visibility you pick
• Show live location and a road route while an alert is open
• Show who was notified and who is coming
• Deliver push and in-app notifications
• Show nearby public alerts and official safety notices
• Let you connect, remove, report, or block people
• Keep the service working, fix problems, and prevent abuse

We do not sell your personal information. We do not use SOS or location data for advertising.

Who can see an SOS

Private (My protectors). You, people you are connected with, and anyone who is actively helping. They can see the alert, your display name and photo, the message and photos you added, and your location while the alert is open.

Public (Nearby public). Nearby SwiftGuard users can see that an emergency is happening, the type, message, photos, and map location. A public SOS does not show your phone number, email, home address, blood group, date of birth, or emergency notes.

Helpers who offer to help may share their own name, photo, and location with the person who sent the alert.

Location

SwiftGuard asks for location so SOS can include where you are, so helpers can get directions, and so Nearby can show public alerts and notices around you.

We do not continuously track you when you are not using those features. While an alert is open, the app may update your location so people can still find you if you move. When the alert is resolved, cancelled, or expired, those live updates stop. A last known location may stay on that alert for people who already had access.

You can turn off location in your phone settings. Without it, you cannot send an accurate SOS or see nearby alerts.

Services we use to run SwiftGuard

We share only what is needed with companies that help us operate the app:

• Google Maps, Directions, and Places — to show maps, reverse-geocode a place name, and draw a driving route from a helper to an SOS.
• Firebase Cloud Messaging and Apple Push Notification service — to deliver alerts to your device. They receive a device token, not your SOS message history.
• Object storage — to store profile photos and SOS photos you upload.
• Hosting and database — to keep accounts, alerts, and connections available.

Those providers process data on our instructions. We may also disclose information if the law requires it, or to protect someone’s safety in an emergency.

How long we keep it

We keep your account and profile while the account is active. You can edit your profile at any time. Deleting your account marks it deleted, signs you out, and removes it from normal use in the app. Your phone number is replaced so it cannot be used to sign in again.

SOS alerts, photos, location points, and notifications that other people already received may remain as part of that emergency record. Device push tokens are removed or stop being used when you sign out or delete the account. QR connect codes expire on their own. Server logs are kept only as long as needed to operate and secure the service.

Your choices

• Edit or clear profile fields in the app
• Choose private or public visibility each time you send SOS
• Remove a protector, leave an alert, or mark I’m safe
• Control notification sound and alerts on the device
• Allow or deny location, camera, and photos in your phone settings
• Delete your account from Profile in the app, or email support@swiftguard.app

If you want a copy of the data we hold about you, or you want us to correct it, write to support@swiftguard.app from the email or phone on the account.

Security

The app and API use HTTPS. Passwords are stored hashed, not in plain text. QR connect codes expire. The server checks who may view an SOS; we do not rely on the device alone. No method of transmission or storage is completely secure, but we work to protect emergency data in transit and at rest.

Children

SwiftGuard is not directed at children under 13. We do not knowingly collect personal information from them. If you believe a child has created an account, contact support@swiftguard.app and we will delete it.

Where data is processed

SwiftGuard is used in more than one country. Your information may be processed on servers outside the country where you live, including where our hosting, maps, and push providers operate. By using the app you understand that this is necessary to deliver SOS and notifications.

Changes

If we change this policy, we will update this page and the date below. For a material change, we may also notify you in the app.

Contact

SwiftGuard
https://swiftguard.app
support@swiftguard.app