SafeID is built around one rule: your information never leaves your iPhone. There are no accounts, no servers, and nothing to sync. This policy explains exactly what that means in practice, what little data the app touches, and how it's handled.
SafeID lets you create up to three kinds of cards, entirely optional and entirely typed in by you. Nothing is pre-filled with real information, and nothing is collected automatically — the app has no way to read your contacts, photos, location, or health data unless you manually type something into a card.
You decide what to put in each field, and you can leave any of them blank. SafeID does not validate, analyze, or draw conclusions from what you enter — it simply stores it and displays it back to you.
Everything you enter is saved locally on your iPhone, inside a storage container shared only between the SafeID app and its own Lock Screen widget extension — both written by us, both running only on your device. No SafeID server exists to send this data to, because SafeID has no backend at all.
In practice: if you were to inspect your network traffic while using SafeID, you would find no outbound requests carrying your card data — because there is nowhere for that request to go.
If you delete the app, this data is deleted along with it, the same as any other app's local storage on iOS.
This is the one privacy trade-off that's core to how SafeID works, and it's worth stating plainly rather than burying in legal language:
Anything you choose to display on a Lock Screen widget can be seen by anyone holding your iPhone, without unlocking it. That's intentional — it's what makes the widget useful to a stranger returning your phone or a paramedic treating you — but it also means you should only put information on an active widget that you're comfortable with a stranger seeing.
Cards you create but don't set as your active Lock Screen widget are not shown anywhere outside the app itself.
SafeID's Lock Screen widgets are a separate process from the main app, as required by iOS. To let the widget show your current card without you having the app open, SafeID uses an App Group — Apple's mechanism for two pieces of the same app to share a private, on-device storage container. This is not a network connection or a cloud sync; it's a local handoff that never leaves your phone.
The widget only updates when you make a change inside the app — editing a card, or switching which card is active. It does not poll, phone home, or refresh on a schedule.
SafeID uses Apple's TipKit framework to show a short first-time walkthrough (e.g. suggesting you edit a card, then activate it, then add the widget). TipKit's tracking of which tips you've seen is stored locally by iOS on your device only, the same way your card data is — it is not connected to any account or transmitted anywhere.
Because everything lives on your device, you're already in full control of it:
There is no "export my data" or "delete my account" request to make, because there is no account and no copy of your data anywhere but your device.
SafeID does not knowingly collect any information from anyone, including children under 13, because it does not collect information from anyone at all — everything typed into the app stays on the device it was typed on. SafeID is not directed at children and contains no social, chat, or data-sharing features of any kind.
Your card data benefits from the same on-device protections iOS applies to any app's local storage — including the passcode/biometric lock on your device itself. Because SafeID has no server and no network transmission of your card contents, there is no server-side breach surface for that data to be exposed through.
If this policy changes — for example, if a future version of SafeID adds an optional feature that does involve a network request — we'll update the "Last updated" date at the top of this page and describe the change here in plain language before it ships in an update.
Questions about this policy or how SafeID handles information can be sent directly to the developer.