Plainphone

Privacy policy

Last updated 17 November 2026

Plainphone keeps as little as it can, for as short a time as it can. This page says what that means in practice. It is written to be read, not to hide things.

Plainphone is early. The parent app and the server exist, but the Plainphone app on the phone does not connect to them yet, so today it sends nothing to the server. Where something only starts once phones are connected, this page says so. A phone can already be set up to use the web filter, which is covered below.

The short version

Who is responsible

Plainphone is an open-source project maintained by Mahoje in Denmark. We are responsible for the data in the hosted service: the parent app at app.plainphone.org and the web filter at dns.plainphone.org.

For anything about your data, such as a copy of it or deleting it, write to privacy@plainphone.org. For questions that are not personal, you can also open an issue at github.com/plainphone/plainphone/issues, but issues are public, so keep personal details such as your email address out of them. Security problems go through the private report form described in SECURITY.md.

Why we use your data

We use it to run Plainphone for you: to sign you in, to apply the rules you set to the phones you manage, and to keep the service working and safe. The legal basis is the agreement between you and the service (GDPR article 6(1)(b)) and our legitimate interest in security and stopping abuse (article 6(1)(f)). For someone who is invited by another person, it is that person’s request together with our interest in delivering it (article 6(1)(f)). We use the data for nothing else.

Your account

You sign in with your email address and a link we send you. There is no password. We store:

Everyone in a household can see each other’s email addresses and manage all of its phones. Sign-in links, sessions and the keys that phones use are stored as hashes.

Phones and rules

A parent, or an adult for their own phone, adds a phone by entering the code it shows. Children get no account and are never asked for an email address. For each phone we store what the adult sets up:

A trusted person you name gets an email. Once signed in, they can see the phone’s name, what is being asked for, and your email address.

Children

Children do not make accounts. A parent does, and the parent decides what is stored about the child’s phone. We do not knowingly collect data directly from a child, we show no ads, and we do not build profiles of children. The most sensitive data about a child’s phone is its last known position and its list of approved contacts. We suggest telling your child what the phone shares, and why.

Location

Location is a setting for each phone. It starts on for a child’s phone and off for an adult’s own phone, and a parent can change it at any time. When it is on, the phone reports its position every few minutes (five by default), and a parent can ask for a fresh one.

The server keeps only the latest position: coordinates, accuracy and time. Each new position replaces the old one, and no history is kept. Switching location off, or removing the phone, deletes the stored position.

If a parent chooses “Open in OpenStreetMap”, the coordinates are in the link that opens, and OpenStreetMap’s own policy applies from there.

The web filter

Each phone gets its own address on our filtering DNS service (dns.plainphone.org). This is how the web filter works in every app. The address contains a random ClientID, not your name, number or device id. To answer, the filter sees which domains the phone asks for. It does not save them:

Allowed lookups are passed on over encrypted connections to Quad9 (Switzerland) and Mullvad, with Cloudflare as a fallback. They see the domain and our server’s address, never the phone’s, and no part of the phone’s IP address is passed on. The technical details are in docs/privacy.md.

Email

We send email only to run the service: sign-in links, invitations and the messages a trusted person gets. No newsletters and no ads. The mail is sent from our own mail server in the EU. The logo in our emails is loaded from plainphone.org, which Cloudflare hosts, so if your mail program shows images, Cloudflare sees your IP address when it fetches the logo. The logo’s address has no identifier and is the same for everyone, so it does not tell us who opened a mail.

This website, cookies and browser storage

plainphone.org sets no cookies, runs no analytics and loads no scripts, fonts or images from other sites. It is hosted on Cloudflare Pages, so Cloudflare, like any web host, handles your IP address and the address you ask for when it delivers a page. Links to other sites, such as GitHub, are ordinary links. Once you follow one, that site’s policy applies.

The parent app at app.plainphone.org sets one cookie, pp_session. It keeps you signed in, is only sent to our own server, cannot be read by scripts on the page (HttpOnly), is only sent on same-site requests (SameSite=Strict) and lasts 60 days at most. You need it to sign in, so there is no cookie banner.

The app also remembers, in your browser, your language choice (local storage) and, only while you sign in, where to go afterwards and an invitation or pairing code (session storage, cleared when the tab closes). A service worker keeps a copy of the app’s own files so it opens without a network. It never stores your data.

Who else is involved

We do not sell data, share it for advertising or use it to profile anyone. These help us run the service:

Account and phone data is kept on servers in the EU.

How long we keep things

How long each kind of data is kept
WhatHow long
Sign-in linksAbout a day after they expire (they expire after 15 minutes)
SessionsUntil they expire (60 days) or you log out
Pairing codesDeleted within a day. This includes the key a phone collects once. Until then it is stored in readable form
Your account (email address, language)Until the account is deleted. There is no delete button yet, so ask us (see Your rights)
Household, phones, apps, contacts, school time, filter settingsUntil the phone or the household is removed. There is no button for either in the app yet, so ask us. A removed contact or schedule is deleted when the removal takes effect
Latest positionOnly the latest one. Deleted when you switch location off or remove the phone
Changes that waited for the key on an adult’s own phoneUntil the phone is removed
InvitationsThey stop working after 7 days. The record is not deleted automatically yet. You can withdraw an open invitation, and we can remove the rest when you ask
Web filter counters24 hours
Backups of the databaseTaken every night and kept for up to 30 days. Deleted data can stay in a backup until it rotates out
Backups of the web filter settingsThe last 14 daily copies

Like any web service, the web server in front of the app writes ordinary technical logs (IP address, time, the address asked for). We use them only to keep the service running and to stop abuse. The app itself holds IP addresses only in memory, for rate limits, and never writes them to its database.

Your rights

You can ask us, free of charge, for a copy of the data we hold about you, to correct it, to delete it, to limit how we use it, to hand it over in a common format, or to stop a use you object to. You can also complain to Datatilsynet, the Danish Data Protection Agency, or to the authority in your own country.

In the parent app you can already do some of this yourself:

There is no button yet to rename or remove a phone, delete your account, download your data or remove an expired invitation. Ask us for these (see Who is responsible). Removing a phone deletes everything stored about it and asks the web filter to forget its ClientID. We check that you control the email address before we change or delete anything, and we aim to answer within a month.

Running your own server

Plainphone can run on your own server. If you do that, you are responsible for that server and its data, and this policy does not cover it. The software stores what this page describes, but you choose where it runs, how long backups are kept (the sample setup keeps 14 daily and 8 weekly copies) and which mail and DNS services it uses. The guides are self-hosting.md and self-hosting-dns.md.

Changes to this policy

If what we do changes, we change this page and the date at the top before the change takes effect. The page is part of the public project, so every change can be seen in its history on GitHub.