Security & Data
For partners, insurers and procurement teams · Last updated: 26 October 2026
ScamGuard SOS is designed to collect as little as possible. There are no accounts and no passwords, and contacts never leave the phone. Besides a live location while the user is sharing it, our server keeps a small anonymous install record (random ID, dates, first country) used to check for a live-tracking pass, and anonymous daily usage totals. Payments for a pass are handled by Stripe; card details never reach our server.
Logical architecture
How data moves between the user's phone, our server and other services.
Contacts, messages, policy numbers and medical details never reach our server. Besides the live location during an SOS, which is deleted automatically, it keeps only an anonymous install record and daily usage totals.
1. What data goes where
| Data | Stored | Kept for |
|---|---|---|
| Emergency contacts, user's name, note, policy number, blood type, allergies, chosen insurer, settings | On the user's phone only (browser storage) | Until the user clears it or uninstalls |
| Live location, accuracy, battery level and display name (during an SOS) | ScamGuard server, Singapore | Link works until "I'm safe" or "Stop sharing" (30 days at most; with a pass, until its days run out), then the record is deleted within 7 days |
| Approximate coordinates (country lookup) | Sent to BigDataCloud; not stored by ScamGuard | Not stored by us |
| SOS text and WhatsApp messages | Sent from the user's own SMS or WhatsApp app | Never seen or stored by ScamGuard |
| Text pasted into the scam checker | Analysed on the phone | Never uploaded |
| App install record: a random ID and a random secret key, both in a secure HttpOnly cookie (the server stores the ID and only a hash of the key); date first recorded and last-opened date; country detected on the first opening (saved once) and on the latest opening; link opened from; app type; group label (A or B, worked out from the random ID, from past price tests); share code and the code of the link you joined from, if any. For friends who join through a share link: their install ID and a keyed one-way hash of their network address, kept 60 days. No IP address, name, email address or phone number. Used to check for a live-tracking pass. ScamGuard is free and every SOS includes the GPS location; live tracking needs the yearly plan, bought on the website (not offered in the Play Store app). Free on a partner's link. | ScamGuard server, Singapore | Deleted after 13 months unused, or immediately via "Clear all data" |
| Yearly plan (only if the user subscribes): Stripe customer and subscription IDs, plan status, end of the paid year and a random restore code that moves the plan to a new phone. No card details. Renews yearly until cancelled through Stripe's customer page. Live-map days from earlier passes, partner gifts or referrals: unused days and their expiry (12 months). | ScamGuard server, Singapore; payment details at Stripe | Deleted with the install record (13 months after it was last used; never while unused days are still valid), or via "Clear all data". |
| Usage counts per partner link and country (opens, installs, SOS sent, partner chats, scam checks) | ScamGuard server, Singapore, as daily totals only | Kept for reporting; contain no personal data |
| Usage analytics | Umami (cookieless, recordings with personal fields masked) and Hotjar (personal fields masked) | Per each provider's retention settings |
2. Insurer assistance channel
- For medical, accident, evacuation and claims situations, the app connects the user to their insurer's assistance team: by WhatsApp (with a pre-filled message) and/or by a one-tap call to the 24-hour assistance line.
- The insurer comes from the partner's own link, or from the travel insurer the user chooses in the app. That choice is saved only on the user's phone.
- For WhatsApp, the user sees the full message (name, policy number, country, location and live-map link) and presses Send themselves. ScamGuard does not see or keep it. Calls go straight from the user's phone.
- The policy number is only included in messages to the insurer. It is never sent to personal SOS contacts or to ScamGuard's server.
- Each partner gets its own link (e.g. scamguardsos.com/partner). The partner's name, WhatsApp number and assistance line are managed on the server, so changes take effect without an app update. The public version, without a partner link, shows no insurer options.
- Partners receive anonymous usage totals for their link (opens, installs, SOS sent, chats opened), never individual users' data.
3. How the live map is protected
- Each link uses a random, unguessable ID (16 random bytes).
- Only the sender's phone holds the 24-byte key that can post locations. The server stores only a SHA-256 hash of that key.
- Links stop working as soon as the user taps "I'm safe" or "Stop sharing", when the pass's days run out, and in any case after 30 days.
- Location is only read while the app is open. There is no background tracking.
- Link creation is rate-limited per network address to prevent abuse. Map and API pages are excluded from search engines.
4. Security measures
- HTTPS/TLS for all traffic, including the Android app.
- Security headers: location access restricted to the app's own origin, MIME-sniffing blocked, and no referrer leaked to other sites.
- No accounts or stored credentials, so there are none to steal.
- No ads, no ad SDKs and no sale or rental of data.
- Session recordings mask every personal field (names, phone numbers, messages, location and scam-checker text).
- The Android app is a Trusted Web Activity, cryptographically linked to this domain through Digital Asset Links. It is signed by Google Play App Signing.
- Source code is version-controlled on GitHub, and every change is traceable.
5. Hosting, uptime and continuity
- Hosted on Railway in the Singapore region (asia-southeast1), with a managed PostgreSQL database in the same region.
- Every release is health-checked before it receives traffic. If a new version fails, the previous version keeps running.
- Core features keep working even if the server is unreachable: SOS SMS, emergency numbers and the scam checker run on the phone, and the app works offline once installed. Only the live map needs the server.
- If the service stops: very little user data sits on the server, and live-map data expires on its own within days. For licensed partners, source-code escrow or a handover to partner-controlled hosting can be agreed in the contract.
6. PDPA (Singapore) alignment
- Consent: location is only used after the user grants permission and starts an SOS, and every message is reviewed before sending.
- Purpose limitation: data is used only to deliver alerts, show the live map, pick the correct country's emergency numbers and manage optional live-tracking passes.
- Retention limitation: live-location data is deleted automatically (see section 1). Install records unused for 13 months are deleted automatically.
- Access and deletion: requests are handled within 30 days through Delete your data.
- Transparency: see the public Privacy Policy.
- Partner arrangements: a Data Processing Agreement can be signed with each licensed partner.
7. Certifications and testing
ScamGuard SOS does not currently hold SOC 2 or ISO 27001 certification, and it has not yet had an independent penetration test. On request, we can commission an independent security test and complete a partner's vendor security questionnaire as part of onboarding.
Contact
For security questions, due-diligence requests or to report a vulnerability, email scamguardsos@gmail.com or WhatsApp +65 8887 7041.