Privacy Policy

This policy covers the SuperPassword app (bundle com.superpassword.app) for iOS and Android, including its autofill extension, published by SUPERSOSED LLC. It covers the app only: there is no web account area and no server side.

SUPERSOSED LLC, 21 Anadyrsky proezd, unit V/8/136, Moscow 129327, Russia. Questions about this policy go to support@supersosed.ru or the @SuperSosedBot Telegram bot; we respond within 30 days.

Everything you enter — passwords, card numbers, documents, attachments and notes — is stored encrypted in the app’s private directory on your device. The developer has no access to it: the vault opens only with your master password, and no copy of that password exists anywhere.

The master password itself is never stored: it derives a key and is then gone from both the database and the settings. Card titles and logins are indexed for search in memory only, and only after you unlock the vault; passwords, PINs, CVVs, TOTP secrets, seed phrases and private keys never enter that index at all.

Interface preferences (theme, language, auto-lock interval) are stored in the same place and contain nothing but those preferences.

• it does not send your data to any server — ours or anyone else’s;
• it creates no accounts and never asks for an email address;
• it shows no ads and contains no advertising SDKs;
• it embeds no analytics, no counters and no crash-tracking services;
• it does not read contacts, location, calendar or browsing history;
• it does not track you across other companies’ apps and websites;
• it shares no data with third parties and sells none — there is nothing to share.

This is verifiable, not just stated: the Android build carries no internet permission — the permission list is shown on the app’s Google Play page — so the app technically has no network access. On the App Store its App Privacy section reads “Data Not Collected”, and the privacy manifest declares no tracking and an empty list of collected data types.

Permissions are requested at the moment you use the feature that needs them, and the app works without them — just without that feature. Any of them can be revoked in your device settings.

Microphone, location, contacts and calendar are never requested — those permissions are stripped from the build.

Face ID and Touch ID are handled by the operating system. The app receives a yes-or-no answer and never sees biometric data. The key that biometrics unlocks lives in the Keychain (iOS) or the Android Keystore marked “this device only”, so it never travels to iCloud or another phone.

None of these mechanisms replaces the security of the device itself. On a jailbroken or rooted phone, or one infected with malware, the operating system’s guarantees no longer hold — and in the end the vault is only as strong as your master password is long and unique.

Text recognition on photos of bank cards, passports, driving licences and insurance policies is performed by the operating system on the device itself: Apple Vision on iOS, ML Kit on Android. Neither the images nor the recognised text are sent anywhere, Apple and Google servers included. The result is only offered as a suggestion for the card fields; anything you typed by hand is never overwritten.

If you enable SuperPassword as a system autofill provider, the operating system calls the app when a login or password field appears in a website or another app. The data stays on the device throughout, and access is guarded by biometrics.

• On iOS the autofill extension has no access to the vault: the app writes a separate encrypted projection into the shared container — logins, passwords and site addresses only. The projection key is generated on the device and never leaves it, and documents, bank cards and attachments are beyond the extension’s reach.
• On Android the autofill service is part of the same app and uses the same vault; the key is guarded by the Android Keystore. Saving a password from the browser happens only when you confirm it.
• The app keeps no log of where or when autofill was used.

Autofill can be switched off in the app settings and in your device settings.

A backup is an encrypted archive that opens with the same master password. Where you send it — email, files, your computer — is your choice, and from that moment the file is governed by that service’s privacy policy, not this one.

There is also a spreadsheet export. It is not encrypted, it is created only after you confirm in the app, and it stays on the device until you send it somewhere yourself.

Saving an attachment to the phone is the one operation where a decrypted file briefly touches the disk: the share sheet accepts a file, not bytes. The copy is deleted as soon as the sheet closes, and the app warns beforehand that the saved copy is no longer protected. An mSecure transfer runs entirely on the device: the file is parsed and decrypted locally, and the mSecure password is never stored.

If iCloud or Google backup is enabled on the device, the operating system may include the app’s files in that backup. The data goes there in the same encrypted form in which it sits on the device — without your master password it is useless. Keys in the Keychain and the Android Keystore are marked “this device only” and are not included. Such backups are managed by Apple and Google under their own policies; you can disable or delete them in your device settings.

The only situation in which we receive your data is when you write to us. We then see your email address or Telegram account name and whatever you wrote.

• Purpose: answering your message and resolving the problem you describe.
• Legal basis: performance of the user agreement and our legitimate interest in supporting users; under Russian Federal Law No. 152-FZ, the consent you give by writing to us.
• Retention: up to 12 months after the request is closed, after which the correspondence is deleted.
• Sharing: the correspondence is held by our email provider and by Telegram; we pass it to no one else except where the law expressly requires it.

The app bundles no advertising networks, no analytics, no crash-reporting services and no other SDK that sends data anywhere. We do not sell, rent or share user data — we simply do not have any.

The app is distributed through the App Store and Google Play. Apple and Google collect their own data about downloads and store usage under their own privacy policies; we have no influence over that, and it gives no access to the contents of your vault.

The app is rated 4+: it carries no advertising, no purchases and no user-generated content that could turn out to be age-inappropriate. It collects no data about anyone, so it collects none about children either, and everything in the vault is entered by whoever uses the device and kept on that same device. No separate parental consent is required for that.

Deleting the app deletes the vault, the attachments and the keys with it. There is no deletion request to send: the developer holds no data of yours to delete. Backups you saved outside the app are yours to delete — the app knows nothing about them.

• A single card or attachment can be deleted in the app at any time.
• There is no account to delete: the app creates none.
• Support correspondence is deleted once its retention period ends, or on your request.

For the data inside the app you exercise the rights of access, rectification, erasure and portability yourself and in full: the data is on your device, it is edited in the app, exported to an archive or a spreadsheet, and deleted along with the app. There is no need — and no way — to ask us for this: we hold neither a copy nor access.

The only personal data we process is support correspondence. In respect of it you may request access, correction or deletion, withdraw your consent and lodge a complaint with a supervisory authority; where the GDPR or California law (CCPA/CPRA) applies, those rights apply to the extent they provide, including the right not to have personal information sold — we sell none. Send requests to support@supersosed.ru.

If you have a question about how storage works, or you believe something behaves differently from what is described here, write and we will look into it.

A new version is published at this same address with a new effective date. Material changes — for instance the app starting to collect anything — will be called out in the store release notes and in the app itself.

SUPERSOSED LLC · 21 Anadyrsky proezd, unit V/8/136, Moscow 129327, Russia · support@supersosed.ru · @SuperSosedBot

Revision of 23 August 2026. This policy applies to every version of the app until a new revision appears at this address.