LEGAL
Klos Privacy Policy
Version: 2026-09-29
Effective date: September 29, 2026
Last updated: September 29, 2026
1. Who we are
Klos LLC, a Florida limited liability company (entity number L26000244944), runs Klos: the iOS app, the web pages at view.getklos.com and join.getklos.com where people open your links and invitations, and the servers behind them. Klos LLC is responsible for your information. Our mailing address is available on request.
Contact: privacy@getklos.com
We don’t sell your information, show ads, or use third-party analytics.
2. What Klos encrypts
Klos encrypts these on your phone before they’re uploaded. We store them only in encrypted form.
- Your document files.
- Document names and notes.
- Pouch names and descriptions.
- The names, email addresses, phone numbers, and relationship labels of people you add.
- The name and phone number on your profile, if you add them.
3. What we can see
- Account: your email address, and when you accepted our terms and this policy. Your password is sent to Supabase Auth to sign you in. We never receive the key derived from it or your content key in usable form.
- Documents: the type of each document (for example, a passport rather than an insurance policy); its issue and expiry dates and statement dates; its freshness status and whether you pin it; whether it’s in My Vault or a Shared Vault; when it was created and updated; its page count, file size, format, and storage path; and which people and Pouches it’s linked to.
- Checksums: each file has a checksum that helps detect corruption. For some files, such as a replaced file or a copy received in Klos, the checksum is computed from the unencrypted file. It could be used to test whether your account contains a file whose contents are already known.
- People: that each person record exists, its ID, any linked Klos account, and when it was created and updated.
- Sharing: the email address of each person you send a link, an invitation, or a document in Klos to; each link’s permission and expiry date; when a link is opened and when you stop sharing it; and Shared Vault membership.
- Keys: your public keys, and copies of your other keys that are encrypted so we can’t use them.
- Notifications: a token that lets us send push notifications to your phone.
- Usage events: our own log of a few things that happen in Klos: account created, document added, link sent, Shared Vault invite sent or accepted, app opened, and errors. We use them to run Klos and keep it working. Each event has your account ID, the event type, the time, a session ID, the app version, build and platform, and sometimes a few details: a page count or file size range, where a document came from (camera, photos or files) and which vault it went to, how many people something was sent to, whether an email went with it, the kind of share, whether the person you invited already uses Klos, and which release of Klos you’re using. We strip names, email addresses, phone numbers, and document and contact IDs from events. A few events, such as opening Klos, are also recorded when no one is signed in, without an account ID.
- Help improve Klos: if you turn this on in Settings, we also record how you use Klos’s other features, such as when you open a document, without saying which one. It’s off unless you turn it on.
- Crash reports: device model, OS and app version, where in the code the error happened, and a hashed account ID. Error messages are redacted and email addresses are removed.
In plain terms: we can see that you hold a passport expiring in March. We can’t see the passport, what you called it, or what you wrote about it.
We don’t store IP addresses in our database. The companies that host Klos log requests, including IP addresses, to run their services. The pages that open your links use a hashed IP address to limit repeated requests, and may send that hashed IP address to Upstash (see section 7).
4. Links and emails
A link you share holds the key that opens it, in the part after the # sign. Browsers don’t send that part to our servers. The file opens in the recipient’s browser.
If Klos emails the link for you, the whole link, key included, passes through our servers and our email service, Resend. Resend keeps a copy of the email. We don’t store the link. The same is true of the invitation when you send a document in Klos to someone who isn’t on Klos yet.
Invitations to a Shared Vault, and invitations to get a document in Klos, show your account email address. Link emails show the part of your email address before the @.
5. Keys, Shared Vault, and recovery
Your keys. Klos encrypts your documents with AES-256-GCM under your content key. That key is itself wrapped by a key derived from your password with Argon2id, and we store only the wrapped result. Klos also keeps keys in your phone’s Keychain so it can open without your password each time. They don’t sync through iCloud Keychain.
Shared Vault. Documents in a Shared Vault use separate keys, wrapped to each member’s registered public key. Klos trusts its own record of which public key belongs to which account. We don’t independently verify the person outside Klos. A malicious or compromised server could substitute a public key for a future Shared Vault document or a future send in Klos. When someone leaves or is removed, the server revokes their Shared Vault keys. Copies they already saved stay with them.
Our stored data alone can’t decrypt the documents in My Vault.
Recovery.
Your password unlocks your vault on another device. If you created a Recovery Kit, its code provides another recovery route. Resetting your account password alone does not recover your documents.
Cached keys support access while Klos remains set up on your device. Do not rely on reinstalling the app, restoring a backup, or transferring phones to preserve recovery access.
If you forget your password and have neither usable device-held keys nor a valid Recovery Kit code, your documents cannot be recovered by you or by us.
6. How we use information
To run Klos: store your files, sign you in, send what you share, and enforce your link settings. To send expiry reminders, notifications, and account emails. To keep Klos working and stop abuse. To fix bugs and decide what to build next. Never for advertising.
7. Who we share it with
We never sell, rent, or trade your information. We share it only:
- With the companies below, which process it for us to run Klos.
- With people you share with, on your terms. View-only links have no download button, but no app can stop a screenshot. Stopping a link blocks new opens. It doesn’t pull back what someone already opened or saved. When you send a document in Klos, once they have their copy, it’s theirs.
- When the law requires it, such as a valid subpoena or court order. Where the law allows, we’ll tell you first so you can object, and we’ll challenge demands that look overbroad. We can’t hand over what we can’t decrypt.
- To stop fraud, abuse, or imminent harm, narrowly and only when needed.
- In a merger or acquisition, under this policy. We’ll tell you before any transfer.
| Company | What we use it for | What it receives |
|---|---|---|
| Supabase | Database, file storage, and sign-in. Supabase handles authentication and initiates account emails. Region: United States. | Your encrypted files and fields, the information in section 3, and your password when you sign in |
| Vercel | Hosting for our website and the pages that open links and invitations | Page requests, including IP addresses |
| Resend | Emails for share notifications, Shared Vault invitations, sending in Klos, and codes to verify someone opening a link | Recipient email address, email subject and body, and the link or access code |
| Upstash | Limiting abuse of shared links, only when rate limiting is turned on | Hashed IP addresses |
| Sentry | Crash reports | The crash data in section 3 |
| Expo and Apple | Push notifications | Your push token and a generic message: “You have something new in Klos.” Never document names or content |
8. Keeping and deleting data
- We keep your information until you delete it or your account.
- To delete your account, open the Klos menu and go to Account. This deletes your account, encrypted files, documents, Pouches, links, people and contacts, and usage events. It can’t be undone, so export any documents you want to keep first. The app exports one document or one Pouch at a time.
- If you set up a Shared Vault, you’ll end it before deleting your account, and choose whether its documents move to My Vault or are deleted. If you’re the Trusted Person, deleting your account removes you from the Shared Vault, and its documents stay in it.
- Documents you sent in Klos, and files people saved from your links, stay with them.
- We keep a record of each deleted account (its ID, email address, and deletion date) to prevent fraud and abuse.
- Shared Vault activity records stay after you delete your account. Your account identifiers in them are replaced with hashes.
- Our logs of emails Klos sends, including the recipient’s address, are scheduled for daily deletion after their retention period, which is at most 45 days.
- Deleted data may remain in our database backups for a limited time.
- Sentry and Resend keep their copies for a limited time under their own retention settings.
- We’ll tell you before any inactive-account deletion policy starts.
9. Your rights
Wherever you live, you can ask to access, correct, delete, or get a copy of your information, or to restrict how we use it. Encrypted information comes back encrypted, and your keys open it. Information we can read, such as account details, document types and dates, record IDs, and usage events, comes back as it is. Email privacy@getklos.com from the address on your Klos account. We reply within 30 days (45 for complex requests, with notice), and we won’t treat you differently for asking.
- California: we don’t sell personal information or share it for advertising. You may use an authorized agent.
- EU and UK: our legal bases are contract (providing Klos), legitimate interest (keeping Klos working and preventing fraud), and consent (optional features such as push notifications). You may complain to your data protection authority.
10. Where data is stored
Our servers are in the United States. If you use Klos from elsewhere, your information is transferred there. For EU and UK data, we rely on Standard Contractual Clauses with the companies that need them.
11. Security
Connections use HTTPS. The file links behind the pages that open your links are signed and expire within an hour. No system is immune to attack. If a breach affects your information, we’ll tell you as the law requires.
12. Children
Klos is for adults 18 and over. We don’t knowingly collect information from children under 13, and we delete it if we find we have. Parents can contact privacy@getklos.com.
13. Changes
If a change affects your rights or how we handle your information, we’ll tell you in the app and by email at least 30 days before it takes effect. For wording fixes, we update the date at the top.
Questions: privacy@getklos.com