Privacy policy
Overview and effective date
Effective date: October 10, 2026.
This policy explains how Pwdx handles your information. It covers the Pwdx apps for iOS and macOS, the AutoFill extension, the Pwdx keyboard extension, and the pwdx.0os.io website.
Pwdx is a one-time purchase. There are no in-app purchases and no subscriptions. Using Pwdx does not require a Pwdx account, and we never ask for your name, email address or phone number, nor do you sign in to any service of ours. Your vault relies on your own iCloud account, which Apple provides. Apple handles the purchase; we never see your payment details.
Pwdx involves four separate kinds of data, and this policy covers each one:
- Your vault: stored in your private iCloud database, with the sensitive fields encrypted on your device before upload.
- Local features: unlocking, password filling, passkey signing, Quick Fill and the keyboard run on your device; the AutoFill extension connects to your private iCloud database only to save newly created passkeys, as explained below.
- Anonymous device statistics: before you turn on support, the app reports model and version information — without any device name — to the support service operated by 0os.
- Support conversations: created only after you explicitly agree in the app; only then do we see what you write to support.
What we do not do
- We do not receive the contents of your vault. Passwords, titles, websites, notes, server details and bank card details are encrypted on your device before upload, and our server does not hold — and cannot obtain — the keys needed to decrypt them. For login entries, the AutoFill credential identity store holds only website domains, account names and random entry identifiers; the system keeps it on the device, and it never reaches our servers.
- The app and its extensions contain no third-party analytics, crash-reporting or advertising SDKs; the project has no third-party dependencies at all.
- We do not track you across apps or websites, and we do not use advertising identifiers.
- We do not sell or trade your personal information, and we do not use it for advertising or profiling.
- The keyboard does not use the network. The AutoFill extension uploads only a newly created, already-encrypted passkey to your private iCloud database after you save it, and never contacts Pwdx servers; password filling, text insertion and passkey signing do not use the network.
- We never receive passkey private keys. Mac Quick Fill does not log keystrokes or read screen contents or other apps’ content.
- The app uses Face ID / Touch ID for local authentication and requests notifications only after you turn on support. Mac Quick Fill’s “Type automatically” is optional: Accessibility permission is used only to type the value you just picked into the frontmost app, and you can revoke it anytime in System Settings → Privacy & Security → Accessibility. The camera is used only while you scan a two-factor QR code (iPhone, iPad); frames are recognized on the device and never saved or uploaded. Picking a screenshot that contains a QR code uses the system photo picker and needs no photo library permission. It does not ask for contacts, location or microphone.
- We never need your passwords, private keys or recovery code, and we will never ask for them. Please do not send them through a support conversation or the support form.
Your vault (private iCloud database)
Your vault is stored in your own Apple iCloud private database — a dedicated zone named PwdxVault in your private CloudKit database — not on our servers. We neither host it nor can read it.
How it is encrypted: every sensitive field of every entry is encrypted with a one-time AES-256-GCM key, and that key is wrapped with your RSA-3072 public key (RSA-OAEP-SHA256). The matching RSA private key is stored only in encrypted form; the wrapping key that opens it lives in your keychain and syncs between your devices through iCloud Keychain. It is never sent to our servers.
The vault now also supports SSH server and bank card entries. SSH server information includes the host/IP address, port, username, password, private key and its passphrase, purchase website and expiry date; bank card information includes the card number, cardholder name, expiry, security code, PIN, issuing bank and online-banking website. All these fields are stored inside each entry's encrypted details/password fields and are encrypted on your device before upload, exactly like existing passwords and notes; the SSH username is also stored in the plaintext "account" field described below.
What is uploaded to iCloud falls into two groups:
- Encrypted: password, title, website, notes, server details, bank card details and two-factor code settings.
- Plaintext: the account name, the entry identifier, the modification time, the revision and the deletion marker. For login and server entries, the "account" field holds the username (including an SSH username), without app-layer encryption as before, so lists can be shown and sorted without decrypting anything; the uploaded plaintext is kept in your private iCloud database and never reaches our servers. For bank card entries, the "account" field is left empty, so no card data is stored in plaintext.
Two-factor (TOTP) settings — the secret, issuer, account label, algorithm, digits and period — are a separately encrypted field of their login item and are encrypted on the device with the same scheme before upload; whether an item has a code is visible from the presence of that encrypted field, but not its contents. Codes are computed on the device from the current time. When you import from another authenticator, QR codes, screenshots, backup files and pasted links are read only on the device, and Pwdx keeps no copy of the original image or file.
Passkeys are stored separately as Passkey records in your private iCloud database. The private key and the website / relying party ID, user name, display name, user handle, credential ID and creation time are encrypted on your device using the same scheme as other items: AES-256-GCM, with the encryption key wrapped by the vault’s RSA-3072 public key. Apart from the encrypted payload, the record has only the vault ID in plaintext; unlike login entries, passkey user names are not stored in plaintext. Pwdx sends the site only what WebAuthn requires: the public key at creation (attestation “none”, with no device attestation), and a signature at sign-in. All users share one fixed authenticator ID (AAGUID), which does not identify a user or device.
Your recovery code is 256 random bits shown to you as hexadecimal; HKDF-SHA256 derives a second key from it that can also open your private key. The recovery code itself is never uploaded to our servers and is never written to iCloud. Only a copy of the private key encrypted with the key derived from it is stored with the key record in your private iCloud database. A newly generated recovery code is kept temporarily in this device's keychain (not synced through iCloud) until you confirm that you have saved it.
Your device also keeps a snapshot of the vault in the App Group container so that AutoFill and the keyboard can work without a network connection. The snapshot matches the cloud copy: only the fields listed above are in the clear, and everything else stays encrypted. The snapshot file uses complete file protection and is excluded from device backups. A private key restored from a recovery code, a new recovery code you have not yet confirmed, and keyboard sessions are all stored in this-device-only keychain items and never sync to your other devices.
Local authentication, AutoFill and the keyboard
- Unlocking: Face ID, Touch ID or your device passcode is verified by the system. Pwdx only receives a pass or fail result and never receives biometric data.
- AutoFill: bank cards are never offered to system password AutoFill. After you pass verification, the AutoFill extension decrypts entry details on your device to show the list, decrypts a password only for the entry you pick, and the system fills in its account and password in the target app or web page. Password filling, text insertion and passkey signing do not use the network. The extension connects to Apple CloudKit only immediately after a newly created passkey is saved, to upload the already-encrypted passkey to your private iCloud database so it is not lost. If the upload fails or the device is offline, the encrypted passkey waits in the App Group container and the app uploads it on its next sync. The extension never contacts Pwdx servers.
- QuickType suggestions: when the Pwdx AutoFill extension is enabled, the app registers the website domain, account name and random entry identifier for each login entry that has both an account and a website in Apple’s on-device AutoFill credential identity store (ASCredentialIdentityStore). It contains no passwords, titles, notes, server data or card data. The system uses it to show suggestions above the keyboard or in the password field; the system keeps this information on the device, and it is not sent to us. It is refreshed when the vault changes and cleared when the vault is deleted or the iCloud account changes. Choosing a suggestion still requires Face ID / Touch ID / device passcode before Pwdx decrypts that one entry.
- Passkey creation and sign-in: when a website or app creates a passkey, choose Pwdx in the system sheet, verify with Face ID / Touch ID / device passcode on the confirmation screen and tap Save. Pwdx then creates an ES256 (P-256) key pair on your device. To sign in, select the passkey in the system sheet or a QuickType suggestion and verify in the same way; Pwdx decrypts only that one private key on the device to sign the site’s challenge. The private key is never shown, copied or exported, and is never sent to us.
- Passkey QuickType suggestions: when the Pwdx AutoFill extension is enabled, the app registers each passkey’s site (relying party ID), user name, credential ID, user handle and random item ID in Apple’s on-device credential identity store so the system can suggest it. This information stays on the device and is never sent to us; it is refreshed when the vault changes and cleared when the vault is deleted or the iCloud account changes.
- Mac Quick Fill: off by default; nothing happens and no shortcut exists until you turn it on in Settings → Quick Fill and record a shortcut containing ⌘, ⌥ or ⌃. Pwdx never opens the panel by itself. Pressing the shortcut opens a small panel over the current app; verify with Touch ID or your Mac password, then pick an item and field (or “account ⇥ password” for logins). By default, the chosen value is copied to the clipboard, marked concealed / transient, and cleared after 45 seconds if unchanged. The shortcut uses the standard system hot-key API: Pwdx receives only its own shortcut, not other keystrokes.
- Quick Fill’s “Type automatically” is a separate optional toggle: after you turn it on, Pwdx explains the permission, then macOS asks for Accessibility permission. It is used only to type the value you just picked into the frontmost app as keystrokes. Pwdx does not read screen contents, other apps’ content or your keystrokes, never types without you picking an item, and never sends typed values anywhere. You can revoke permission anytime in System Settings → Privacy & Security → Accessibility; without it, Pwdx falls back to copying.
- Quick Fill offers an optional menu bar icon (shown only while Quick Fill is on) and optional “Open at login” (off by default, enabled by you). You can turn off Open at login in Pwdx Settings or System Settings → General → Login Items.
- Two-factor codes: viewing or copying a code requires an unlocked vault. On iOS / iPadOS 18 and macOS 15 or later, for each login with a code and a website the app registers the website domain, a display label (the account name, or the item title when there is no account) and the random item ID in Apple’s on-device credential identity store, so the system can suggest it above one-time-code fields. The secret is not included; this stays on the device and is never sent to us. With “Copy 2FA Code After Filling Password” on, filling a password copies the current code to this device’s clipboard (excluded from Universal Clipboard) and clears it after 45 seconds.
- Single-field AutoFill: on iOS / iPadOS 18 and later, choose “AutoFill → Pwdx” in any text field’s menu to insert a single chosen field, such as a card number, expiry, security code, server host or SSH command, username or password. This happens on the device after authentication; only the chosen text is given to the system to insert. Bank cards are still never offered for password AutoFill.
- The keyboard: the Pwdx keyboard needs Full Access, which you grant in system settings, before it can read the vault snapshot in the App Group; without Full Access it can only type as an ordinary keyboard. After you unlock the keyboard once, either in the keyboard with device authentication or in the app, it stays unlocked for a period you choose (1 minute to 1 hour), until that period ends or the vault is locked. The session is recorded in a this-device-only keychain item and becomes invalid as soon as you lock, switch vaults, or the time runs out.
- While locked, the keyboard shows only an unlock prompt. After unlocking through device authentication in the keyboard or from the app, it decrypts each entry’s name and type on the device to label its list. Buttons depend on the entry type: logins offer account, password and notes; SSH servers offer host, username and password (the password button is omitted when no password is stored, which is determined without decryption); bank cards offer card number, expiry and security code, never the card’s PIN. Secret values are decrypted only for the button tapped and inserted into the current text field. Recently used entry identifiers (at most 12) remain in local App Group preferences to order those entries first and never leave the device. Labels are discarded when the keyboard locks or disappears. No networking is involved.
- The keyboard does not record keystrokes, does not read the surrounding text in the input field, and uploads nothing.
Anonymous device statistics (before you turn on support)
Even before you turn on support, Pwdx periodically sends an anonymous device record to the support service operated by 0os. It tells us how many installations there are, which models and system versions they cluster on, and how many are still on older versions, so we can decide which devices and versions to keep supporting.
The report contains only:
- The platform (iOS or macOS) and the push environment.
- The device model name and model identifier (for example iPhone 17 Pro).
- The system version, the app version and the build number.
- The notification permission state (not determined, authorized, denied and so on) and whether notifications are currently usable.
How the installation is identified: the first time it reports, the app generates a random installation secret and stores it in this device's keychain (it does not sync through iCloud). The server stores only the SHA-256 hash of that secret, assigns the installation a random identifier, and records when it was created and when it last reported. That identifier is not linked to your Apple account, name or email address, and we cannot work backwards from it to a person.
The report does not contain a device name, your name or email address, an advertising identifier, your location, or any vault data. Identical content is reported at most once per hour; it is updated when the model, system or version changes.
Until you agree to turn on support, this record has no push capability at all: the server holds no push token and cannot send a notification to the device.
Contacting support (after you turn it on)
Only after you open Settings → Contact support in the app, read the disclosure and tap "Agree & enable Feedback" does this device become a support identity, and only then do we receive what you write.
Once it is on, the server stores:
- All of the anonymous fields listed above, plus the time you agreed.
- Once you allow notifications, the APNs push token issued by Apple.
- The display name of this device (see below).
- The text of the messages you send (up to 4,000 characters each) and when you sent them, along with our replies (title and body), when we replied, message status and whether a message has been read.
The device name defaults to the model plus a short random identifier (for example "iPhone 17 Pro 1a2b"). You can set your own in Settings → Contact support → Feedback settings → This device's name. On macOS, if you have not set one, the app reports your computer's name; on iOS the system only returns a generic name such as "iPhone", and such names are discarded in favour of the default. The device name is used only so we can tell your devices apart across conversations.
Support conversations are not end-to-end encrypted: we, as the operator, can read what you send. We use it only to answer your questions, investigate the problems you report, and run the service. Please do not send passwords, private keys or your recovery code in a conversation.
Push notifications: if you allow notifications, we hand the title of a reply (up to 120 characters) and its body (up to 500 characters) to Apple Push Notification service for delivery to your device. System notification previews may show that text on your Lock Screen; you can turn previews or notifications off in system settings. Turning notifications off does not delete conversations already on the server.
Website support form
The form at pwdx.0os.io/support stores the message you write (up to 4,000 characters), the optional email address you provide (up to 254 characters) and the time of submission, so we can reply to and act on your request. You may submit without an email address, but then we have no way to reply.
To prevent abuse, submissions are rate-limited by a hash of the source IP address. Form submissions are not deleted automatically; if you want yours deleted, say so in the form.
Service providers and sharing
We hand the necessary information to the service providers below so we can deliver the features you choose to use. Beyond that we do not share your information with third parties, except where the law requires it or where it is necessary to protect the service and its users. We require our service providers to protect this information consistently with this policy and to process it only on our instructions.
- Apple: provides iCloud / CloudKit (storing and syncing your vault), iCloud Keychain (syncing the wrapping key that unlocks your vault), local authentication (Face ID / Touch ID, with biometric data always remaining on the device), Apple Push Notification service (delivering support replies), and App Store and TestFlight distribution and purchase handling.
- 0os: operates the Pwdx support service and the pwdx.0os.io website, including the servers, database and operational logs that hold anonymous device records, support conversations, replies and push identifiers. To prevent abuse, rate limiting stores only a hash of the IP address and clears it within minutes; we never write your IP address into a device record or a conversation.
Cross-border processing: these providers may process and store your information outside the country or region where you live.
Retention
| Data category | Retention |
|---|---|
| Vault entries and key record (your private iCloud database) | Controlled by you: deleting an entry writes a deletion marker that syncs between devices; deleting the vault removes the entire PwdxVault zone |
| On-device vault snapshot, keychain keys and keyboard session | Kept until you delete the vault, switch iCloud account or remove the app; a keyboard session lasts at most 1 hour and ends when it expires or you lock |
| Anonymous device record (support not yet enabled) | Deleted by a scheduled cleanup job once the installation has not reported for 90 days and has no support messages or notification records |
| Support conversations, replies and push identifiers (support enabled) | No automatic expiry: kept until you delete them in the app, ask us to delete them, or we shut the service down |
| Website support form submissions and optional email address | No automatic deletion: deleted by us once your request is handled, or on your request |
| Service call diagnostics | 30 days |
| Rate-limit counters | Counted per minute and cleared after about two minutes |
| Website access logs | No access logs are kept |
Your choices and deletion
Withdraw support consent and delete the server-side data: Settings → Contact support → Feedback settings → Disconnect and delete notification data. This deletes this device's entire conversation, our replies, its notification records, its push identifiers and its device record on the server, and stops notifications immediately. Your vault is unaffected. Afterwards the app starts reporting anonymously again under a new random installation identifier. Merely turning notifications off in system settings deletes nothing.
Delete the Pwdx vault: Settings → Delete Pwdx vault. This takes two verification steps: first Face ID, Touch ID or your device passcode, then the original recovery code for this vault (repeated wrong entries lock the step temporarily). Once confirmed, the app deletes the PwdxVault zone in iCloud (credentials and key record) along with the keys and local snapshot on this device, and asks the server to delete this device's support conversation, replies and push identifiers. The server keeps one anonymous device record (model, system and app version, last-seen time) with the device name, push identifiers and consent state cleared, until this installation reports again or the 90-day cleanup rule in the table above removes it. The deletion cannot be undone, and it does not affect other iCloud data such as your photos or notes.
Delete passkeys: delete them individually under the Passkeys filter; deletion syncs to other devices.
Turn off Mac Quick Fill: turn off Quick Fill, “Type automatically” and “Open at login” in Pwdx Settings. Accessibility permission is only for optional “Type automatically” and can be revoked anytime in System Settings → Privacy & Security → Accessibility; without it, Pwdx falls back to copying. Open at login can also be turned off in System Settings → General → Login Items.
Generate a new recovery code: Settings → Generate a new recovery code. This also requires Face ID, Touch ID or your device passcode plus the original recovery code. The old code stops working as soon as the new one is issued, so save the new code offline right away.
If you lost your recovery code: neither deleting the vault nor regenerating the code is possible in the app without it. You can delete Pwdx's iCloud data outside the app, on iPhone under Settings → Apple Account → iCloud → Manage Storage → Pwdx. Devices that are already unlocked can keep using the existing vault.
Deleting the app deletes nothing automatically: your vault in iCloud, the wrapping key in iCloud Keychain and any support records already on the server all remain. Use the steps above in the app first, then uninstall.
Other requests: for access, correction, deletion or any other privacy request, use the form on our support page at https://pwdx.0os.io/support (leave an email address so we can reply). To confirm that you control the installation in question we may ask for limited verifying information; we will never ask for your passwords, private keys or recovery code, and we have no ability to read your vault in the first place.
Children
Pwdx is not directed to children under 13, and we do not knowingly collect their personal information. If we discover that we have received such information, we delete it.
Security, changes to this policy, and contact
Traffic between the app and our servers uses HTTPS/TLS. The installation secret stays in your device's keychain and the server stores only its SHA-256 hash. We keep no key on the server that can decrypt your vault, so even a breach of the server would not expose your passwords. Biometric data is always held by the system and never reaches Pwdx. No system is perfectly secure, so please protect your device passcode, your iCloud account and your recovery code.
Changes to this policy: we publish updated versions at https://pwdx.0os.io/privacy and update the effective date at the top of this page at the same time.
Contact: use the form on our support page at https://pwdx.0os.io/support. Once support is enabled, you can also talk to us directly in the app under Settings → Contact support.