contents
01
what we collect — and what we don't.
what we store
- Your username (chosen by you)
- Your invite code and invite tree
- Your trusted circle connections
- Device fingerprint (for login only)
- Subscription status (if applicable)
- Abuse reports (if filed)
- App settings and preferences
- Anonymous crash logs (Crashlytics)
- Aggregate analytics events (PostHog)
what we never store
- Messages or conversation content
- Media or files shared in sessions
- Voice or video call recordings
- Call logs or session transcripts
- Your real name
- Your phone number or email
- Your location
- Screenshots or recordings
- AI translation content
02
how conversations work.
When two people enter a Silen session, the conversation exists only in the memory of their devices for the duration of that session. No message is transmitted to our servers. No content is stored anywhere outside your device during or after a session.
When either person leaves — the session ends, local memory is cleared, the channel is destroyed, and the session object is deleted. There is no archive, no backup, no "deleted messages" folder. It is gone.
03
third-party services we use.
Silen uses the following services to operate. Each has its own privacy policy governing how they handle data.
- Supabase stores user accounts, circles, invite trees. No messages stored. Hosted in EU/US regions.
- Ably handles real-time WebSocket signaling for session coordination. No message content is persisted by Ably on our behalf.
- Agora provides voice and video infrastructure. Sessions are not recorded or stored by us. Agora's own data practices apply.
- Firebase (Google) — crash reporting via Crashlytics and push notifications via FCM. No personally identifiable data is sent in crash reports.
- PostHog — product analytics. Tracks aggregate events only. No message content, no user identification.
04
analytics and tracking.
We use Firebase Analytics and PostHog to understand how the product is used at an aggregate level. The events we track are strictly limited to:
- invite accepted % how often invites result in account creation
- session started % how often connections lead to live sessions
- avg session length how long sessions last on average
- day 7 + day 30 retention whether people return after their first session
No event contains message content, user identity, or any personally identifiable information.
05
device fingerprinting.
Silen uses a device fingerprint to allow you to log back into your account without a password. This fingerprint is a hash derived from device characteristics. It is not linked to your hardware identity, not transmitted to advertising networks, and stored solely in Supabase for authentication purposes only.
06
screenshot detection.
When a screenshot or screen recording is detected during an active session, the other participant is notified immediately. We do not store, log, or transmit the screenshot itself. The notification is a live in-session signal only — it is not saved anywhere once the session ends.
07
data sharing and selling.
We do not sell your data. We do not share your personal data with advertisers, data brokers, or any third party for commercial purposes.
We may disclose data if required by valid legal process — but given the nature of what we store, there is very little to disclose. We cannot hand over what does not exist.
08
account deletion.
You can delete your account at any time from within the app:
You can also submit a manual deletion request at silenapp.in/delete-account
On deletion, we remove your account, username, invite tree, circles, device fingerprint, and subscription data within 7 days. Because conversations were never stored, there is nothing conversation-related to delete.
09
children's privacy.
Silen is not intended for anyone under 18. We do not knowingly collect data from minors. If you believe a minor has created an account, contact us and we will remove it immediately.
10
changes to this policy.
If we make material changes to this policy, we will notify users through the app. The effective date at the top of this page will always reflect the latest version.
11
contact.
Privacy questions, concerns, or data requests: