In short: Zaprite P2P is built so your contacts, message content, and spending keys stay under your control. We use your phone number for one-time codes, and your account keeps it only as a one-way keyed hash. We match contacts by hash and never see your address book. Your profile, messages, and payment history live on your device. When you send or request money, our payment services hold limited order details briefly so the payment can complete, then delete them.
1. Who we are and what this covers
In short: This policy covers the Zaprite P2P app and the services that run it.
This Privacy Policy explains how Zaprite Inc. (“Zaprite,” “we,” “us”) collects, uses, and shares information when you use the Zaprite P2P mobile application and related backend services (together, “P2P”).
It does not cover third-party wallets, exchanges, websites, or apps you connect, such as Strike, Alby, or other Lightning and on-chain providers. Those have their own policies. Our website and merchant products may have separate notices. For P2P use, this policy controls if they conflict.
Contact
Zaprite Inc.601 Congress Ave #230, Austin, TX 78701, United States
Privacy, deletion and rights requests: privacy@zaprite.com
2. What we never receive
In short: Some sensitive information stays on your phone and never reaches us.
P2P is designed so that we do not receive:
- Your address book: names, photos, or raw phone numbers from your contacts
- Your spending credentials, such as NWC connection secrets or provider spending tokens, which stay in secure storage on your device
- The content of peer messages, which is end-to-end encrypted so we can't read it
- Your seed phrases for third-party wallets. We are non-custodial, so those stay with you and your wallet apps.
3. What we process briefly or only as a hash
In short: Some data we need only for a moment, and some we keep only as a one-way hash.
| Data | What happens |
|---|---|
| Phone number | You enter your number so we can send a one-time code for signup, recovery, and deletion requests and to limit spam. Our servers and our SMS provider (Twilio Verify) see the number in readable form only while the code is being sent; we do not store it in readable form. Your account record keeps your phone number, and your username if you set one, only as one-way keyed hashes. Short-lived verification, recovery, and deletion-request records refer to the number by a one-way hash. |
| Contact matching (optional) | If you opt in, your phone turns your contacts' numbers into irreversible hashes and sends only those hashes. We tell you which of them use P2P. This doesn't give us contact names, photos, or raw numbers. |
| Anonymized payment statistics | Before our payment service deletes a completed order, it keeps an anonymized record of the payment: amount, currency, payment method and wallet type, and the month each account was created. The record contains no account or transaction identifiers. We keep it for internal reporting. |
4. Information we collect or process
In short: Your profile, contacts, messages and payment history live on your phone. Our servers keep the minimum needed to run your account, mostly public keys, hashed lookup values and encrypted data we can't read. Our payment service holds order details only briefly so a payment can complete.
Kept on your device, not on our servers in readable form: your username, display name and profile photo; your contacts and nicknames; the content of your messages; your payment history and notes; your recovery phrase, private keys and wallet spending credentials. A bug report you choose to send can include some of this (see Diagnostics below).
| What our servers hold | Form | How long |
|---|---|---|
| Account record: an internal account ID and your public keys | Readable (these are public by design) | Until you delete your account |
| Phone number and username: for sign-in, recovery and optional discovery | One-way keyed hashes, not plain text | The phone number hash is removed when you delete your account. A username you give up by deleting your account stays reserved, as a hash, so no one else can take it |
| Profile (display name, username, photo) | Encrypted on your device; only people you share your profile key with can read it, not Zaprite | Until you delete your account |
| Messages in transit | Content is end-to-end encrypted. We can see delivery details: sender and recipient account IDs, message type, and timestamps | Deleted once your devices receive it, and never kept longer than 30 days (7 days for invite links) |
| Encrypted backups (optional): a copy of your on-device database and, if you use a passkey, your encrypted account recovery key | Encrypted on your device with keys we don’t have | Your latest two database backups; deleted with your account |
| Passkeys: credential IDs and public keys | Readable (public values) | Until you remove them or delete your account |
| Devices and notifications: push tokens, device and installation IDs, platform, OS version, app version, app-integrity check results | Readable | Push tokens are removed after 30 days of inactivity; integrity sessions expire within minutes |
| Blocks: which accounts you block | Readable | Until you or the blocked account is deleted |
| Security and abuse prevention: short-lived verification and session records, rate-limit counters (which can include your IP address), app version and last-seen time | Hashed or readable | Most expire within minutes; app version and last-seen time stay with your account |
| Bug reports you choose to send: a screenshot, recent app logs with sensitive values removed, and an app summary that includes your account ID, wallet types, and recent order details and amounts | Readable by Zaprite and our bug-reporting provider (Shake) | 1 Year |
| Crash and performance data: app start-up timings, device model and OS, app version, a random install ID, your IP address, and crash and error details | Readable by Zaprite and Expo. Not linked to your account | 60 days |
| Usage counts: one record for each contact request you send and each invite of yours that is accepted, holding your account ID and the date | Readable | Kept after you delete your account. The ID then points to no account |
Payments. When you send or request money, the amount, currency, note, and the accounts paying and receiving go to Zaprite's payment service so it can create the order and complete the payment. These order records are held only briefly to complete the payment, then deleted. Orders are deleted about six hours after they're paid or expire. An order with an unconfirmed on-chain payment is kept until it confirms, for up to 30 days. Before deleting a completed order, we keep an anonymized record of it (amount, currency, payment method and wallet type, and the month each account was created), with no account or transaction identifiers, for internal reporting. The payment service also keeps your account ID, public keys, currency settings and the receiving wallet setup you configure, until you delete your account.
Processed but not stored: your phone number in readable form while we send you a one-time code through our SMS provider (Twilio Verify); the hashed phone numbers your device sends for optional contact matching.
Blockchain and Lightning: Payments on public networks can be visible on those networks. That comes from how the networks work, not from Zaprite storing your payment history.
We do not sell your personal information. We do not use your P2P data to train third-party AI models or to target ads for other companies.
5. How we use information
We use information to:
- Create, verify, and secure accounts
- Send one-time codes and reduce spam, fraud, and abuse
- Run optional contact matching
- Deliver encrypted messages and push notifications
- Process payments you start and keep the receiving setup you configure
- Support the recovery and backup options you choose
- Handle account deletion and privacy requests
- Operate, secure, debug, and improve P2P
- Comply with the law and enforce our terms
- Contact you about the service
7. Retention and deletion
In short: We keep less on our servers than a typical payments app, and we delete most of it within weeks.
- Messages on our servers: each encrypted message is deleted once your devices receive it, and is never kept longer than 30 days (7 days for invite links). Automated cleanup removes expired messages.
- Payment orders on Zaprite payment services: held only briefly to complete the payment, then deleted, about 6 hours after the order is paid or expires. An order with an unconfirmed on-chain payment is kept until it confirms, for up to 30 days.
- Anonymized payment statistics: kept for internal reporting. They contain no account or transaction identifiers.
- Verification codes and device checks: expire and are removed automatically within minutes.
- Devices and backups: push tokens and device registrations not seen for 30 days are removed. We keep your latest encrypted database backup and the one before it, and delete older ones. Account records, encrypted profile, passkey records, and blocks are kept until you delete your account.
- Vendor and infrastructure logs: kept according to our providers' and our own operational policies.
Your controls
- Delete your account in the app: go to Settings > Danger Zone > Delete account and confirm. Deletion is immediate and can't be undone. The app then erases its data from your device.
- Request deletion without the app: if you no longer have the app or can't open it, email support@zaprite.com. We reply with a link to our account deletion page. The link is valid for 7 days. You don't need to reinstall the app. We don't store your phone number in readable form, so we verify the request with a one-time code sent by SMS to the number on the account. Once it's verified, deletion is scheduled for 7 days later. Any device still signed in to the account shows the request and can cancel it during that time. After 7 days we delete the account. We complete requests within one month.
- Remove from this device (Settings > Danger Zone): erases your keys and data on that phone only. It does not delete your account, and you can sign in again on another device with your usual recovery method.
What deletion removes: your account (user record and the hashed phone identifier); your profile, name and photo; your encrypted backups of account keys and app data; your passkey and device registrations, push tokens, and app attestation records; blocks you placed and blocks others placed on you; messages and payment requests waiting on our servers, and messages you sent that are still stored there; phone recovery requests and their codes; and your Zaprite organization, including the wallets you connected through the app and any linked Zaprite Pay browser sessions. Your phone number becomes available for a new account right away. Your username is retired for good.
What deletion does not remove:
- Copies on other people's devices: messages, payment requests, and profile details already delivered to your contacts stay on their devices. We can't reach them.
- Payment orders: these follow the schedule above, about 6 hours after the order is paid or expires, or up to 30 days while an on-chain payment is unconfirmed.
- Anonymized payment statistics: these contain no account or transaction identifiers, so they can't be linked back to your account.
- Records kept by merchants: merchants you paid keep their own records of those payments.
- Public networks and third parties: records on public Bitcoin or Lightning networks, and information held by wallets or providers you connected.
- Things you control: your passkey stays in your password manager (for example iCloud Keychain or Google Password Manager), and your recovery phrase stays wherever you saved it. You can delete them yourself.
- Usage counts: one record for each contact request you sent and each invite of yours that was accepted. Each holds only your old account ID and a date. The ID no longer points to an account.
- Your retired username: kept as a one-way hash so no one else can take it.
- Submitted bug reports: diagnostics you choose to submit remain with our bug-tracking service for a maximum of 1 year.
8. Security
We protect data in transit with encryption. Message content is end-to-end encrypted, profile content is encrypted before we store it, the app's local database is encrypted (SQLCipher), and spending credentials stay in secure storage on your device. Not everything we hold is end-to-end encrypted. Some operational data, such as push notification tokens and IP-based rate-limit records, is stored in a form our systems can read so the service can run. No system is perfectly secure. You are responsible for your device, your recovery methods, and your third-party wallets.
9. Age requirement
You must be at least 18 and have reached the age of majority where you live to use Zaprite P2P. We do not knowingly allow anyone underage to use it. If we learn that someone under 18 has an account, we delete it and the personal data we control that's linked to it, subject to the law.
10. Your choices and privacy rights
Choices: your device permissions (contacts, camera, notifications); whether to use contact matching; your profile details; recovery and backup features; connecting or disconnecting wallets; and deleting your account.
US state rights (including California): Depending on where you live, you may have the right to access, correct, delete, and get a copy of your personal information, and to opt out of its “sale” or “sharing” for cross-context behavioral advertising. We do not sell personal information or share it for that kind of advertising. We do not discriminate against you for exercising your rights. To exercise them, contact support@zaprite.com. We may need to verify your request. If we deny a request, you can appeal by replying to our decision email.
We do not respond to browser Do Not Track signals. The mobile app does not use third-party ad trackers or advertising identifiers. It sends crash and performance data to Expo.
11. Legal requests, business transfers, and breaches
- Legal requests: We may disclose information to courts, regulators, or law enforcement when we believe in good faith that we're required to, or to protect rights, safety, and security.
- Business transfers: If Zaprite is part of a merger, acquisition, financing, or sale of assets, information may be transferred as part of that deal under appropriate confidentiality. This policy, or a successor notice, continues to apply unless we tell you otherwise.
- Breaches: If a breach of personal information affects you, we notify you and regulators as the law requires.
12. Changes to this policy
We may update this policy. When we do, we post the new version with a new “Last updated” date. For material changes, we give reasonable notice in the app or by email, at least 30 days before they take effect where practicable, unless the law requires a shorter period or we need to address an urgent security issue. If you keep using P2P after the effective date, you accept the updated policy, except where the law requires your express consent.