Who we are
Fortress is published by StellarTimeLock. The Android package is
com.stellartimelock.stellarvault. Contact
support@stellartimelock.com. This policy
covers the Fortress Android app and this website.
Data that stays on your device
Passwords, usernames, notes, recovery codes, authenticator secrets, addresses, card
numbers, and passkeys are stored only on your phone, in an encrypted save file
(stellar-vault.svault) in a folder you pick. The key comes from your seed or
recovery phrase. StellarTimeLock cannot open that file. We do not have an account system,
and we do not receive a copy of the vault.
Fingerprint or face unlock is a shortcut on that phone. It does not encrypt the save file. If you add a fingerprint, reinstall, or change phones, Fortress asks for the seed again. A backup still opens with the seed alone.
What can leave the device
Nothing leaves the phone unless you do one of these:
- Export or backup. You pick the folder or the share sheet. We are not the destination.
- Send to PC. You confirm first. One login is handed to the Stellar Send app on the same phone, which copies it to your paired computer.
-
Breach check. If you tap Check breached passwords, Fortress sends the
first five characters of the SHA-1 hash of a password to Have I Been Pwned
(
api.pwnedpasswords.com) over HTTPS. The password and the rest of the hash stay on the phone. The request is not tied to your name or email. We do not receive the prefix.
Autofill and the passkey provider fill other apps on the same phone. That data is not uploaded by Fortress.
What we do not do
No ads. No analytics. No crash-reporting account. No sale of data. No advertising ID. The camera is used to scan an authenticator QR code and the picture is not saved. This website does not set tracking cookies and does not ask you to sign in.
Children
Fortress is for adults 18 and older. It is not directed at children.
Deletion
There is no server account to delete. See Delete your data.
Changes
If this policy changes, the new date will be on this page. The app will keep treating the vault as local-only unless a future version says otherwise before you update.