Privacy Policy
DRAFT. Embrilo is in public beta, and this page is a draft under legal review. It may change before the beta ends. Questions go to contact@digitalden.so.
Last updated: 15 November 2026
Embrilo is a messenger and voice app for groups of friends who play games together. It is run by Digital Den LLC ("we"). You can reach us about privacy at contact@digitalden.so.
The short version
- Your messages, group names, files, calls, availability and what you are playing are end-to-end encrypted. They are locked on your PC and unlocked only on the PCs of the people you are talking to. Our server passes them on and cannot read them.
- You do not give us a phone number, an email address or your real name. You choose a handle.
- Our server does see who talks to whom and when (which accounts share a group, who is friends with whom, who is in a call), because it has to deliver messages. We keep as little of that as we can, for as short a time as we can, and list it all below.
- The one time anything said in Embrilo reaches us readable is a report: someone who reports another person picks messages from their conversation and sees exactly what will be sent first. That can include messages you sent them.
- No advertising, no trackers, no analytics SDKs, no selling data, no training AI models on what you write.
What never reaches us readable
The server never sees, and could not hand to anyone:
- the text of your messages, and their times and IDs as your app records them;
- the names of your groups;
- your files, their names and their types;
- what is said in calls (voice goes through our relay encrypted with keys only the people in the call have; we never record calls);
- whether you are available, until when, and your availability label;
- the game you are playing, if you turn Now playing on (only its name is shared, encrypted, with the friends you share availability with; nothing else about the programs on your PC leaves it);
- which friends and groups you want alerts for, and your quiet hours;
- your recovery key, and every private key.
The exception is a report, which someone chooses to send after seeing all of it: see "Reports" below.
What the server keeps, and why
To deliver messages between devices, the server has to know some things. Each is listed in full in data-boundaries.md; in short:
| What | Why | How long |
|---|---|---|
| Your handle, a random account ID and your account's public key | So friends can find you and check it is really you | Until you delete your account. Your handle then stays reserved, so nobody else can take it and pose as you |
| Your devices' public keys, and when each was linked or signed out | So your friends' apps know which devices are yours | Until you delete your account |
| Who you are friends with, and friend requests | So strangers cannot message you | Until either of you unfriends, or 30 days for an unanswered request |
| Which devices share each group or call, the roles in a group, and the order members joined | To deliver messages and enforce who may add or remove people | While you are in it |
| Encrypted messages waiting for a device | To deliver them | Until that device fetches them, at most 30 days |
| Encrypted files | To deliver them | 30 days, or 1 or 7 days where the conversation keeps messages that long |
| When each device signs in, fetches messages and uploads files; padded sizes | It cannot deliver without seeing this | Not kept as a record; it shows in the rows above while they last |
| Who blocked whom | To keep a blocked person from contacting you | Until you unblock, or either account is deleted |
| A public log of account keys (account ID, a hash of the handle, the public key) | So apps can detect a server that lies about someone's key | Permanently: it only grows. It holds no messages and no private data |
| Your encrypted backup, if you turn Backup on | So you can restore your history on a new PC | Until you delete it, or 90 days after a device of yours last refreshed it |
| Reports you send | So we can act on abuse | 90 days |
| Crash reports you choose to send | To fix bugs | 30 days |
IP addresses
- The service uses your IP address only to limit how fast requests can come (for example, ten sign-ups an hour from one address). It keeps a hashed form in memory, for at most 24 hours, and never writes it to a log or the database.
- The web server in front of it keeps no access log, and its logs keep no addresses. The server's system log keeps one day.
- During a call, our voice relay sees the IP address and port of each device in the call while it is connected, and how much each sends. It does not keep them after the call. Calls always go through the relay, so the people in a call never see each other's addresses.
- If you turn on link previews (off by default), your PC fetches the linked page itself, so that website sees your IP address.
Reports
Reporting works within the encryption (more on the reporting page):
- You choose the messages to include, one by one, from a conversation on your PC. Nothing else is read, and nothing is scanned, on your PC or on the server.
- You see the exact text we would receive before anything is sent.
- What we receive: who you are reporting, why, your own words, and the messages you picked as your PC shows them, with their senders' handles and times, and the names of any files (not the files). Not the conversation's name, its other members or other messages.
- We keep a report for 90 days, even if either account is deleted (if you delete yours, your account ID is removed from your reports). The person you report is not told.
Backups we make of the server
We copy the server's database once a day, and once more before each upgrade, so we can recover from a failure. The copies are kept on the server itself and nowhere else. They hold what the database holds (the table above), never your messages' content, which the service never has. They are not encrypted to a key kept off the server: we can read them as the server's administrator, and so can our hosting provider, which can read the server's whole disk. A daily copy is deleted after 14 days and an upgrade's copy within 4, so something deleted from the service is gone from every copy within 15 days. The one exception: if we ever have to roll back or restore the database, the database it replaced is kept on the server too, also unencrypted, until we delete it by hand once the service works again.
Deleting your account
In the app, Settings lets you delete your account. It is signed by your account's key, so nobody who steals a session can do it.
- At once: your devices are signed out, your friendships end, you leave every conversation, and your requests, invites, backup and blocks are deleted.
- Within a day: files you sent that your PC knows of, and the database's leftover pages.
- Within 15 days: the server's own backups, except in the one case described above.
- What stays: your handle remains reserved and the key log keeps its entries (they hold no private data); reports about you, and reports you sent (without your account ID), until their 90 days are up; and anything your friends already received, which is theirs.
Exporting your data
The app can save your conversations and files to a folder on your PC (Settings). This happens entirely on your PC; the server has almost nothing of yours it could read.
Who else is involved
| Who | What for | What they can see |
|---|---|---|
| DigitalOcean, in San Francisco, USA | Runs our server | What any host sees (which addresses connect, when, how much), and the server's disk: the database described above, never your messages' content |
| Vercel | Hosts this website and the download | Your IP address and browser details when you visit, under their own retention |
sslip.io, a free public DNS service (we have no domain of our own yet: the service is reached at 137-184-7-224.sslip.io) | Answers lookups of the service's name | Lookups, usually from your internet provider's resolver rather than your PC |
| Let's Encrypt | Issues the server's HTTPS certificate | Nothing about you |
We do not use any other service that receives information about you.
Children
You must be at least 13 to use Embrilo, or older where the law where you live says so (for example, 16 in some countries). The app asks you to confirm this before it makes an account. Your answer is not sent to us or kept anywhere: the app simply will not make an account until the box is ticked. If you believe a child under that age is using Embrilo, tell us at contact@digitalden.so and we will delete the account.
Your rights
You can export your history and delete your account in the app (Settings), at any time. You can also ask us for a copy of what we hold about you, or ask us to correct or delete it, at contact@digitalden.so. If you are unhappy with how we handle your data, you can complain to your local data-protection authority. Which data-protection laws apply to Embrilo, and the legal basis for each kind of processing, will be added here after legal review, during the beta. Because we hold so little readable data, most requests are answered by the app itself: deleting your account, exporting your history, and the list above of everything the server keeps.
Requests from authorities
We can only hand over what we have: the records in the table above. We cannot provide the content of messages, files or calls, because we never have the keys. Requests go to contact@digitalden.so, and we check each one before anything is disclosed. We do not publish a transparency report yet.
Changes
If we change this policy, we will say so on this page and in the app's release notes before the change takes effect, and at least 30 days before for a material change.
Contact
Digital Den LLC, contact@digitalden.so.