Legal
Privacy Policy
What personal data we process, why, where it is stored, how long we keep it and how to exercise your rights.
This policy explains how personal data is processed when you use the Humanity Ledger websites and Ledger Chat. The controller of that data is Stefan Antonio Cirisanu, who provides the service as a private individual under the name Humanity Ledger. You can reach the controller at [email protected]. Full details are in the legal notice.
The short version
We cannot read direct messages delivered through XMTP, and we never receive the keys of your wallet or of your private payments wallet. We can read some other things, listed below, and we say exactly which. We do not sell data, we do not show advertising, and we do not use analytics or advertising trackers.
1. Data we process
| Data | Why | Kept for |
|---|---|---|
| Wallet address | It is your account identifier. | Until you ask us to delete your account. |
| Email address, if you sign in with email | To send you sign in codes and, if you ask, messages about your account. | Until you ask us to delete your account. |
| Sign in codes | To check the code you type. Stored only as a hash. | Until used or expired, within minutes. |
| Session data | To keep you signed in. Held in cookies described in the Cookie Policy. | Seven days, or thirty days for the email refresh token. |
| Display name and profile picture, if you set them | So that people you talk to can recognise you. | Until you change or remove them. |
| Contacts and contact requests | So that your contacts follow you to new devices. | Until you remove them or delete your account. |
| Community memberships, roles, posts and channel messages | To run communities. | Until deleted by you or a moderator, or until the community is deleted. |
| Messages sent through the fallback path | To deliver a message when XMTP delivery fails. These are readable by us and labelled in the chat. | Up to seven days in our cache, and in our database until deleted. |
| Attachments | So the recipient can download them. Not yet encrypted. | Until deleted. |
| Hash of your PIN | To check the PIN you enter. | Until you remove the PIN or delete your account. |
| Online status | So that contacts can see when you are available. | A few minutes after you go offline. |
| Device linking codes | To link a second device by QR code. | Four minutes, in server memory. |
| IP address and request details | To keep the service secure and to limit abuse, for example by rate limiting. | Rate limit counters expire within minutes. Our hosting provider keeps request logs for a limited period. |
What we do not receive. The content of direct messages delivered through XMTP, which is encrypted on your device. Your wallet's private key or recovery phrase. The keys of your private payments wallet, which are created in your browser. Your Aztec address, your private balances, your transactions and the content of your private notes: the private wallet runs in your browser and talks to the Aztec test network directly, without our server. If you send a private payment from a conversation, the chat message that announces it is handled like any other message.
2. Legal bases
- Contract (article 6.1.b GDPR). Most processing is needed to provide the service you asked for.
- Legitimate interests (article 6.1.f). Security, abuse prevention and keeping the service working. You can object at any time.
- Consent (article 6.1.a). Optional features such as push notifications. You can withdraw consent in your settings at any time.
- Legal obligation (article 6.1.c). Where a law requires us to keep or disclose data.
We do not make decisions about you based solely on automated processing that have legal or similarly significant effects, and we do not build advertising profiles.
3. Service providers
We use a small number of providers to run the service. They process data only on our instructions or, for open networks, as part of the network's normal operation.
| Provider | Purpose |
|---|---|
| Hosting, database and cache providers | Running our servers, our PostgreSQL database and our Redis cache. |
| XMTP network | Delivering encrypted direct messages. |
| Resend | Sending sign in codes by email. |
| Cloudflare | Bot protection on email sign in, and storage of attachments. |
| Reown | Connecting wallets through WalletConnect. |
| PeerJS, Google and OpenRelay | Setting up and relaying voice and video calls. Call content is encrypted between browsers. |
| Blockchain RPC providers | Reading balances and broadcasting the transactions you approve. |
| Aztec test network nodes | Receiving the private payment transactions your browser has already proven. They see that a transaction exists, not its amount or its parties. |
Some providers are outside the European Economic Area. Where that is the case, transfers rely on an adequacy decision of the European Commission or on its standard contractual clauses.
4. Public blockchains
Payments you send on Ethereum and similar networks are public and permanent. Neither we nor anyone else can delete them. Moving funds into or out of a private Aztec balance is also public. Think carefully before linking a wallet address to your real name.
5. Requests from authorities
We disclose personal data to public authorities only when Spanish or European law requires it, in response to a request that is valid in form and scope. We can only hand over what we hold, as listed in section 1. We cannot hand over the content of direct messages delivered through XMTP or private payment details, because we do not have them.
6. Security
Connections are encrypted with TLS. Sessions are held in cookies that scripts cannot read, PINs are stored as Argon2id hashes, and access to production systems is limited to the provider. The measures in place, and the weaknesses we know about, are described openly in the security model and on the audits page. If a breach puts your rights at risk, we will tell the supervisory authority and, where required, you.
7. Your rights
Under the GDPR and Spanish Organic Law 3/2018 you can ask for access to your data, to correct it, to delete it, to receive it in a portable format, to restrict its processing and to object to processing based on legitimate interests. Write to [email protected] from the email address linked to your account, or include a message signed with the wallet linked to your account, so that we can confirm the request is yours. We answer within one month.
You also have the right to complain to a data protection authority. In Spain this is the Agencia Española de Protección de Datos.
8. Deleting your account
When you ask us to delete your account, we delete your profile, contacts, PIN hash and the fallback messages we hold for you. Posts you made in communities are deleted or anonymised. We cannot delete what lives outside our systems: messages on the XMTP network, history stored on your own devices, and transactions on public blockchains.
9. Children
The service is not intended for anyone under 16. If you believe a child has given us personal data, contact us and we will delete it.
10. Changes
When this policy changes, we update the date on this page. If the change is significant, we also tell you in the app before it takes effect.