SILNT
Privacy

Your messages are end-to-end encrypted. Only the people in the conversation can read them. Our delivery service cannot read your messages, photos, voice notes or payment details shared in a chat. SILNT's first-party messaging code does not use advertising identifiers or embed advertising or analytics SDKs.

No personal details to sign up

SILNT creates your identity on your device. You do not give us your name, phone number or email address to get started. The delivery service still stores identifiers and public identity keys, which identify an app identity without requiring a real name.

What our server stores

• Encrypted messages waiting for delivery. These are deleted on delivery or expire after 30 days.
• Encrypted photos, voice notes and other media, which expire after 90 days.
• Identifiers needed to deliver messages, along with public identity keys. These can be linked even if you do not claim an @handle.

The server also holds notification tokens linked to delivery identifiers, file upload records and group invitation records. It sees delivery timing and uses temporary IP counters to limit abuse. Anyone who knows a delivery identifier can look up its public identity key.

If you choose an @handle, it is public. The server keeps the handle, its linked public identity key and delivery identifier until the handle is released, and keeps a public history of changes to those links permanently. Choosing a handle is optional. Some public identity information remains accessible without one.

Edits, deletes for everyone and view-once opens travel as encrypted messages like any other. Our server sees only an encrypted envelope and sends no notification for them. They work through the other person's app, so a modified or out-of-date app can ignore them and keep the original.

These records do not reveal message contents, but may allow connections between people to be inferred. The data privacy guide explains what each service can see.

Payments

You control your wallet keys. SILNT does not hold your funds. Bitcoin payments use Spark and Lightning, and USDt uses the Liquid network. Breez, Spark operators and other payment services process wallet identifiers, payment destinations, amounts, timing and settlement records. Their access to payment records is separate from the encrypted contents of your chats. If you claim an @handle, the app also registers it with Breez as your Lightning address, such as name@silnt.net, so Breez can link your handle to the wallet that receives your Bitcoin payments. Registering the address and paying it both go through silnt.net, which passes each request, with the IP address it came from, to Breez's hosted Lightning address service. Our messaging server cannot read payment details in your chats.

Each payment network charges its own fees. USDt is issued by Tether, so holding it is a claim on Tether. Currency estimates use a public price feed; conversions happen on your device. See the data privacy guide for payment providers, including optional purchases through MoonPay.

If you choose Buy, MoonPay opens a checkout inside the app. MoonPay may require contact details, payment information, identity documents and a selfie to process and verify your purchase. SILNT cannot read the fields you enter in that checkout. MoonPay and its verification and payment providers process them under MoonPay's privacy policy.

Wallet services synchronize encrypted wallet records through Breez. The synchronization service can see record identifiers, revisions and request timing, but the record contents are encrypted on your device. Payment operators separately receive the information needed to process payments. Their retention and other uses are governed by their own policies, including the Spark privacy notice. Deleting SILNT does not delete payment-provider records or public blockchain history.

SILNT Pro

For App Store purchases, Apple processes the auto-renewing subscription. Your device checks your subscription, and our delivery server receives neither your receipt nor your subscription status. Pro adds the optional features described in the app and the Pro guide. Free and Pro use the same message encryption.

On Android, Google processes Pro purchases through Google Play. The app checks the purchase on your device. Our delivery server receives no purchase token, order ID or Google account details.

What stays on your device

Your message history, contacts and wallet data are encrypted on your phone and protected by your device security. On iPhone, this app data is excluded from standard iPhone and iCloud device backups.

SILNT's own encrypted iCloud backups are on by default and can be turned off. They are encrypted before leaving the app and require your recovery phrase to open. Deleting the app does not remove an existing iCloud backup.

On iPhone, Lock when backgrounded requires authentication when you return to SILNT, even if the phone is unlocked. Lockdown requires enrolled biometrics instead of accepting the device passcode and turns previews off. Erase this device removes local keys and app data. It does not remove copies held by other people. Notification previews are prepared on your device; the push notification contains no message text or sender name. With previews on, a notification shows who a message is from, never the message text, and messages can be read for notifications without unlocking SILNT. Leave previews off for stronger protection. These controls do not guarantee safety on a compromised operating system or while SILNT is already open. Some wallet records rely on device security. See the device privacy guide.

On iPhone, a message you copy stays on that phone, never on your other devices, and is cleared after 60 seconds. A view-once photo or video is kept encrypted on the phone until it is opened, outside device backups and never in a SILNT backup; it is decrypted in memory only when opened and shown only after its key has been erased, and an unopened one is erased after 14 days.

On iPhone you can also share text, links, photos, videos and files into SILNT from other apps. The share extension saves them as files on your phone, under iOS file protection and outside device backups, for you to send from SILNT. It does not open your chats or keys and makes no network connection. Items are deleted once sent or discarded; anything older than 24 hours is deleted the next time SILNT or the share extension runs, and Erase this device deletes them too.

On Android

Messages and contacts are stored encrypted. Your recovery phrase always requires your biometrics or device PIN. Your messages and contacts require them too, and locking the app closes access until you authenticate again. The one exception is the optional sender-name notifications described below. Lockdown requires strong biometrics and turns sender names off. These controls cannot guarantee safety if the operating system is compromised or SILNT is already open.

Notifications are neutral by default: they say only that a new message arrived, with no sender name or message text. You can turn on sender names in Settings, under Notifications, which asks you to authenticate. A notification then shows the contact's or group's name and never the message text. Android can keep what a notification showed in its own notification history, outside the app, which is why SILNT never puts message text in a notification. Leave sender names off for stronger protection.

To show that name while SILNT is locked, the app creates a separate preview key in the Android Keystore. It lets the app open its encrypted store without unlocking SILNT, but only while the phone itself is unlocked. The preview key cannot open your recovery phrase. Turning sender names off or turning on Lockdown deletes the preview key.

The app excludes its data and settings from Android cloud backups and device-to-device transfers. There is no automatic cloud backup on Android. You can export an encrypted backup file of your message history from Settings. Only your recovery phrase can open it. SILNT does not upload the file; you choose where it goes through the Android share menu, and wherever you send it keeps a copy.

SILNT blocks screenshots and hides its screens in the recent-apps view. Erase this device removes local data, keys, wallet files, the preview key and app settings. It does not remove backup files you exported or copies held by other people.

When SILNT is in the background or closed on Android, it is woken through Firebase Cloud Messaging (FCM). Our server holds an FCM token next to your delivery identifier, as it holds an Apple push token for an iPhone. When a message arrives, the server sends a wake to that token, and the wake goes through Google's servers. Google receives the token and a constant wake with no message content, sender or identifiers, and can see when wakes are sent. If SILNT is unlocked, the app then fetches and decrypts new messages on your device. If it is locked, the notification follows your notification setting described above.

Deleting your account

Erase this device on your main phone also removes your account from our server, while your keys are still on the phone. On iPhone and Android it releases the @handle claimed on that phone and deletes the server mailbox and notification registration of the identity you are using. What else it removes differs between iPhone and Android; how to delete your account lists it for each, and explains what to do if you lost your phone. If you set up the phone by restoring your recovery phrase, claim your @handle again first, or Erase cannot release it and the server keeps the mailbox.

After deletion, the server keeps some records for a limited time:

• the public history of your @handle, permanently, so anyone can check that a handle was never moved to someone else's key
• the deleted mailbox's identifier and public authentication key, for 180 days, so no one else can take over the address
• invitations you created, each with the identifier of the mailbox that created it to enforce the invitation limit per mailbox, until they expire within 30 days
• encrypted messages you sent that are still waiting for delivery, until they are collected or for up to 30 days, and encrypted group messages for up to 30 days
• encrypted media you sent, and the upload records that keep your mailbox identifier to enforce the storage limit per mailbox, for up to 90 days

These periods describe the live delivery database. Server backups retain the newest 14 backup files. A deleted record may remain in an older backup until that file is replaced; this is not a fixed 14-day deletion deadline. Public @handle history, your own exported or iCloud backups, and payment-provider records have the separate retention rules described here.

When the server deletes an unused mailbox on its own is explained under if you lost your phone. A mailbox usually stays until you erase it or ask us to delete it.

Analytics and third parties

We do not include advertising frameworks or analytics and crash-reporting SDKs in the iPhone and Android apps. The apps connect to the delivery service and payment services. Wallet and checkout providers process information under their own policies, including service analytics and legal compliance. Optional backups, notifications and purchases involve the providers described in the data privacy guide.

Your choice of delivery service

You can run your own delivery service and select it in Settings, under Server. That operator handles delivery records instead of us. Payment, notification and backup providers may still be involved.

Legal requests

We can only provide records we hold. These include encrypted messages, delivery identifiers, notification tokens, public identity keys, file upload and invitation records, and public @handle history. We cannot decrypt message contents or recover data that has expired and been deleted. The data privacy guide explains the links these records can reveal.

Newsletter

You do not need an email address to create a SILNT identity or use its chats. Optional checkout and support services may ask for one. The newsletter is separate from the app, and joining it is optional. Fantom Tech Labs runs it. If you join through the form on silnt.net, we keep your email address and the time you joined, plus a note of which version of the form's wording you saw. We use the address to send you beta invitations and occasional SILNT news.

We rely on your consent, given when you submit the form, and you can withdraw it at any time. The list is kept in its own database on SILNT's own server, apart from the delivery service, and the form does not record your IP address or browser. We do not sell the list or share it with advertisers or analytics services. When we email you, the message goes through our email provider, which handles your address only to deliver it.

We keep your address until you ask to be removed or we close the list. To be removed, reply to any of our emails or write to privacy@fantomlabs.io. You can also ask us for a copy of your entry, or to correct or delete it, by writing to the same address. If you are unhappy with how we handle it, you can complain to your local data protection authority.

Changes and contact

Effective 6 October 2026. This revision clarifies wallet synchronization, payment and checkout providers, and server backup rotation. The 2 October version described edits, deletes for everyone and view-once messages, copying a message, and sharing into SILNT from other apps on iPhone, and said that iPhone notifications show at most who a message is from. The 28 September 2026 version described optional sender-name notifications and encrypted backup export on Android, said that the app registers your @handle with Breez as a Lightning address through silnt.net, and described what Erase this device removes from our server and what the server keeps after you delete your account. The 27 September 2026 version added the newsletter, who runs it, and your rights over your entry.

On 17 September 2026 the app and this policy were renamed from SIGNET to SILNT; the practices described are unchanged.

Material changes to this policy will be published at this URL with a new effective date. Questions: privacy@fantomlabs.io.