Version 1.5.1 · effective 2026-10-19 · for the gateway operated by [operator not configured — see docs/legal/operator.md]
playnet is federated: anyone can run a gateway, and the software's authors run none of them. The controller of your personal data is the operator of the gateway you use — here, [operator not configured]. The authors of the software are not a controller and hold none of your data.
Contact for anything in this notice, including any request under §5: [operator contact not configured]. Postal address, where the operator has one: [not configured]. Representative or data-protection officer, where one is designated: [not configured].
| Data | Where it comes from | Notes |
|---|---|---|
| Your AID and its key event log — creation, key rotations, signatures, registration time | Created in your browser when you sign up | Published — see §4.1. Contains no name or contact detail. |
| Display name and email | Only if you enter them in settings — both are optional and blank by default | Name aids discovery; email enables notifications. Neither is used for account recovery. |
| The index from your AID to your name | Derived, so the gateway can look you up | This is the single record that turns a pseudonym back into a person. Its removal is the core of any erasure request (§5). |
| Notification bindings — email address, Telegram chat id, Matrix room, Reticulum/LXMF address, browser push subscription | Only channels you connect | Keyed by your AID, which joins them all together. |
| Presence — your display name against a live session, and the meeting room you are in | While you are signed in | Broadcast to other connected members. |
| Position and home — where you say you are or live (§2.4) | Only if you share it, from your device's location or from a place you pick | Held as a named place or a coarse grid cell, not as a track of where you have been. |
| Profile attributes — conditions, diet, abilities and other tags you choose to state | Only what you enter | May be health data; see §3.2. Used by the planner to match needs. |
| Messages — chat posts, and the needs, offers and proposals you write | What you post | Visible to the members the space it is posted in lets read it, and to other gateways it is federated to. |
| Content sent to AI features — audio, pictures, text | Only when you use such a feature, and only once you have agreed to it — a tick of its own when your identity is made, a switch under settings › the AI after; without it nothing is sent (§4.3) | Processed to give you an answer. Speech is recognised on your device first, by a model this gateway serves (about 80 MB, fetched once and kept in your browser), and the audio goes to the gateway only if that returns nothing. |
| Payout records — your claim, payout requests, the Monero address you give, amounts, status | Only where payouts are enabled and you use them | Financial data. A transfer on the blockchain is permanent (§5.2). |
| Network data — your IP address and the time of a request | Every connection | Visible to this gateway and to the operator's hosting and content-delivery providers. It is not visible to them when you reach the gateway through its onion address. |
| Server logs | Operation of the service | Rotated hourly and compressed by the operating system, on storage that holds nothing once the machine is powered off. Identifying fields in the gateway's logs are redacted to a short, non-identifying tag before they are written; the web server's log records the time, status, duration and size of a request and no address, path, referrer or browser. |
Most of what the system knows about you is held as signed credentials, stored by the hash of their contents and anchored in the issuing scope's key event log:
You choose what is shared. The location panel offers live location, "here, now" and "not shared". Choose not shared to stop. A shared fix is filed at the nearest known place within a short distance of you, or else as your own place on a grid of about one kilometre, named for the nearest place we know. One place is kept for you and replaced as you move, so the service keeps where you are and no trail. Your home, if you set it, is kept the same way. Your device may ask your permission before it gives the browser its location; refusing is always possible, and the service works with a place you pick by hand. Who sees your position depends on the scope you share it into, and it reaches other gateways only as far as the federation shares that scope.
How you vote is recorded against your identity, in signed form. Under Article 9 GDPR that is special-category data and needs a specific condition to process at all. The condition relied on is Article 9(2)(d): processing by a not-for-profit body with a political or philosophical aim, in the course of its legitimate activities, concerning its own members, with no disclosure outside the body without your consent. Where the operator is not a body of that kind, the condition is instead your explicit consent — Article 9(2)(a) — asked once, separately from the terms, either when you create your identity or the first time you cast a vote.
What that means in practice, and its limits:
You can withdraw that consent at any time — settings, "your data and the notices," the toggle for it — as easily as you gave it, per Article 7(3). Withdrawing does not erase a vote already recorded (§5.2 says what cannot be erased); it means you will be asked again before the next one. If you do not want a political opinion recorded against your identity at all, do not vote. Abstaining is the only complete protection we can honestly offer.
You may state conditions, allergies, diet or abilities in your profile so the planner can meet needs that depend on them. That is health data, and it is optional. The condition relied on is your explicit consent, Article 9(2)(a), given when you enter it, and you may withdraw it by removing the tag. Other things you enter — a diet, a belief, who you trust, where you are — can reveal sensitive characteristics too, such as religion, health or sexual life. The planner reads profile tags to match needs, and other members of your commune may see them as the space allows. Enter only what you accept being seen by those people, and by anyone a member shares it with. The service is a planning aid and not a medical device; the notices beside these fields in the app, and §5.6 of the terms, say what it cannot do for your health.
Every key event is broadcast to witnesses — independent machines run by other people, in jurisdictions we do not choose or know — which keep copies so that no single party, including us, can rewrite your key history. Your key event log is also served at this gateway's discovery endpoints, without authentication: anyone who knows your AID can fetch it. It contains your public keys, rotation history and timestamps; it does not contain your name or email.
Credentials are shared with federated gateways so that work, skills and personhood recognised in one commune are recognised in another. Those gateways are run by other people under their own notices and their own law.
| Service | What reaches it | When |
|---|---|---|
| Hosting and content-delivery providers | Network data and encrypted traffic to this gateway | Whenever you reach the gateway over the open internet |
| AI model providers the operator selects | The words, audio or pictures you submit, and the instructions the app adds to them | Only when you use an AI feature (transcription of speech the device could not recognise, drafting, reading a photo) and have agreed to it: the AI consent is asked for by itself, separately from these terms, and switched off under settings › the AI at any time. The gateway sends only to models that run inside a hardware enclave and verifies the enclave's attestation on every request. Ask us which provider, and in which country, the operator uses and what its terms say about keeping and training on content. |
| Web-push providers (Google, Mozilla, depending on your browser) | Your push subscription endpoint and notification content | Only if you enable browser notifications |
| Telegram | Your chat id and notification content | Only if you connect Telegram |
| Matrix homeserver | Your room id and notification content | Only if you connect Matrix |
| Email delivery | Your address and notification content | Only if you give an email address |
| Reticulum / LXMF mesh | An opaque cryptographic address | Only if you use the mesh. Preferred: it carries no identifying address. |
| The Monero network, and the node the operator uses to reach it | The transaction: destination address and an encrypted amount | Only if you request a payout. Monero hides sender, receiver and amount from the public by design, and a transaction on it is permanent. |
| Map tiles | Nothing leaves this gateway: the map's tiles are OpenStreetMap data held on the gateway itself | Whenever you open a map. No tile provider is contacted, by the gateway or by you. |
We do not sell your data, do not share it for cross-context advertising, do not use it for advertising, and run no analytics or advertising trackers.
Meetings held through the service connect participants' browsers to one another, so the people in a meeting can see and hear what you send, and can learn the network address your connection comes from. The gateway carries the roster of who is in a room. No third-party server is contacted to set a call up: the gateway names no STUN or TURN server unless the operator runs one, so a call connects where a direct path between the two browsers exists. Anyone can record a meeting with their own tools.
We disclose data where a valid legal order compels it, and we will tell you unless we are prohibited from doing so. We ask that an order be specific and lawful, and push back where we reasonably can. We hold no passcode and no private key, so we cannot produce them, and we cannot recover what is held only as a hash.
You have the rights of access, rectification, erasure, restriction, portability and objection, and the right to withdraw consent. Exercise any of them by writing to [operator contact not configured]. We answer within one month; where a request is complex or numerous we may extend that by two further months and tell you why. We do not charge for requests unless they are manifestly unfounded or excessive.
Stated so you can judge the gap rather than take a promise on trust:
If you are in the EU or EEA you may complain to your national data protection authority (directory); the authority for this operator is [not configured]. Elsewhere, to your equivalent regulator. Please raise it with us first if you are willing.
We check that a request comes from you in a way that asks for no more identifying information than we already hold — for example, a signature made with your key, or a reply over a channel you have connected. We do not ask for identity documents unless nothing else can protect you from someone impersonating you. A request about data tied only to a pseudonym can be met only for the pseudonym you can prove you control.
The rights above come from the GDPR. The operator applies them to every member, wherever they live. Where the law of your country gives you more, you have it:
| Data | Purpose | Legal basis |
|---|---|---|
| AID, key event log, authentication | Providing the service at all | Contract — Art 6(1)(b) |
| Display name, notification bindings | Discovery and notifying you | Consent — Art 6(1)(a); both are optional and withdrawable |
| Position and home | Showing you what is near you and letting members who share a place find one another | Consent — Art 6(1)(a), which you give by choosing to share and withdraw by choosing not shared |
| Profile attributes, where they are health data | Matching needs that depend on them | Explicit consent — Art 6(1)(a) with Art 9(2)(a) |
| Work, claim and skill credentials | Computing the plan; recording contribution and entitlement within the commune | Contract — Art 6(1)(b), and the legitimate interest of the association in an auditable record — Art 6(1)(f) |
| Personhood and relationship credentials | Keeping out spam and vote-stuffing; resolving delegation | Legitimate interest — Art 6(1)(f) |
| Stances and ballot snapshots | Counting votes and resolving delegated voice | Art 6(1)(a) together with Art 9(2)(d) or 9(2)(a) — see §3.1 |
| Messages, presence and meetings | Letting members communicate through the feature you use | Contract — Art 6(1)(b) |
| Content sent to AI features | Giving you the answer you asked for | Consent — Art 6(1)(a), given by using the feature |
| Payout records | Making a payout you request, and keeping the records the law requires of whoever makes one | Contract — Art 6(1)(b), and legal obligation — Art 6(1)(c) |
| Network data, server logs, your recorded consent | Security, debugging and showing that you accepted these documents | Legitimate interest — Art 6(1)(f) |
Where we rely on consent you may withdraw it at any time, and where we rely on legitimate interest you may object; in both cases write to the contact in §1. Withdrawing consent does not make earlier processing unlawful. We assess our legitimate interests against yours and will show you the assessment on request. Giving us the data in the first group is necessary to have an identity; the rest is optional.
What this gateway keeps of a visitor beyond your own record has a limit, and the limits are applied hourly. A message left for you in an offline mailbox that you have not fetched goes after 30 days; a delivery left for a mesh address, after 30 days; a message a witness of this gateway keeps for an identifier it witnesses (a credential offered to a holder who reads its mail at its witnesses, where this gateway keeps such a mailbox), after 7 days, held in plain text, and carried by the encrypted backups for their own period below; mail written to a spool directory (a development transport — a deployed gateway relays mail and keeps none), after 30 days; anonymous feedback, after 180 days from when it arrived; a report, after 180 days from the operator's decision on it (a report still waiting for a decision is kept however old, since it has not been answered). Server logs are rotated hourly with their identifying fields already redacted (§9), and encrypted backups age out after 30 days.
What has no age limit, and why. Your member record, the files kept for you (contacts, log, pins, taxonomy, credential backup, recovery pieces), your devices and your key log stay until you forget yourself (§5.1): they are yours, a recovery file kept for a day you need it, or a log other signatures depend on, and a cut-off by age would delete someone's backup for being quiet. Credential validity windows — a personhood credential's expiry, a skill's valid-until — govern whether a credential still counts, not whether it is still stored; a lapsed credential remains readable on disk, and a sweep of credential bodies waits on encrypting them per person, which is not yet built. Records the law requires us to keep, such as those of a payout, are kept for as long as it requires. Key events and credential anchors are kept for good, for the reasons in §4.1.
The planner computes allocations automatically — by convex optimization over recorded needs, capacities, limits and contributed labour — and those allocations affect what you can claim from the commons. We consider this not to be a decision "based solely on automated processing" within Article 22 GDPR, because the output is a proposal that the federation adopts, amends or rejects through its governance, in which you have a voice and a vote. Either way, you can ask a person to look at any allocation that affects you, express your point of view and contest it — through the governance process, or by writing to the contact in §1. AI features draft or read for you and decide nothing about you.
No system is perfectly secure. If a breach is likely to put your rights at risk we will notify the supervisory authority within 72 hours of becoming aware of it, and, where the risk is high, you without undue delay.
Witnesses and federated gateways are run by independent people in places we do not choose, and mesh transport routes wherever the mesh routes. Publishing to them is inherent to how the system resists tampering. No adequacy decision, standard contractual clauses or other safeguard covers these flows, and the law of those places may give you less protection than yours does. When you create an identity you ask us, knowing that, to publish your key events to witnesses and to share your credentials with federated gateways, and that is the explicit consent on which we rely for these transfers (Article 49(1)(a) GDPR); it is a derogation for a reason, so we limit what is sent to what the protocol needs. If that is unacceptable to you, this system is not suitable for you — we would rather say so than bury it.
Where the operator uses a provider outside your country or the EEA for hosting, AI, notifications or maps, it relies on an adequacy decision, standard contractual clauses or comparable safeguards where they are available, and otherwise on your consent as above. Ask us for the details.
This service is not intended for children below the age given in §8 of the terms, and the operator does not knowingly collect personal information from a child below that age. Signing up asks for a month and year of birth and the country you live in, which your device turns into an age bracket; only the bracket reaches the gateway, which holds it in memory for an hour while your seat is taken and writes it nowhere, and neither a birth date nor a country is kept by us. Your device keeps the month and year and the country in your profile, in the browser's own storage (§12), and works your age out from them each time it is needed, so it moves on with your birthday and a second commune does not ask again; you can change the birth month in your profile. Once you state anything in your profile, the age worked out — not the month — is told to the commons with the rest of your profile tags, as §3.2 describes. A person whose answer puts them below the lowest age is not asked again for a day: the device keeps the time of that refusal and nothing of the answer. If you believe a child has created an identity here, or that a child is at risk or has been sent harmful material, write to [operator contact not configured] with the word "child" in the subject and we will act on it first: we remove the member record or the material — subject to the limits in §5.2 — and report it to the competent authorities where the law requires us to.
No advertising, analytics or third-party tracking cookies are used, and the service does not track you across other sites, so it treats a "Do Not Track" or Global Privacy Control signal as honoured. The page keeps data in your browser's own storage — your sign-in hint, your profile (with the month and year you were born and your country), your keys, your interface preferences, a cache of the app so it works offline, and any map regions you choose to keep — all of which stays on your device. This is what the service you asked for needs, which is why it does not ask for a cookie consent. You can clear it in your browser's settings.
Material changes are published here with a new version number and effective date, and you will be asked to acknowledge them the next time you sign in. We will not use data collected under an older version for a new purpose without telling you first and, where the law requires, asking for your consent.