Privacy Policy

Version 0.3.0 · Last updated 27 October 2026

The short version

1. Who is responsible

Budgie (called Nook until October 2026) is made and run by Teofil Ionescu-Mihai, who is the “controller” of your personal data under the EU and UK General Data Protection Regulation (GDPR). Contact us through github.com/teofilcelzmecher.

2. What we keep

WhatWho can see itWhy
Your username, profile picture (icon or photo), colour, shape and bio, and when you joinedEveryone on BudgieSo people know who wrote what
Your password and recovery code, only as one-way scrambled hashes that can’t be turned back into themNobodyTo let you sign in and recover your account
Your posts, comments, images, polls and the nests you createEveryone on BudgieThat’s what Budgie is for
Your votes, Sparks and poll answersOnly totals are shown, never who votedTo count them, and so you can change your vote
Nests you joinedOnly the member count is shownFor your home feed
Your friends and friend requestsYou and the other personSo friends can message each other
Your private messages, and when each one was readYou and the person you’re writing to (see section 4). Once you open a chat, your friend sees “Seen” under what they sentTo deliver them and show they arrived
Your notificationsYouTo tell you about replies and requests
Your settings, saved posts, collections, drafts, streak and badgesYouSo they follow you to every device
Reports you make, and moderation decisions about youModerators, and youTo keep Budgie safe and handle appeals
Which version of these terms you agreed to, and which invite code you used, if you joined with oneModeratorsAs a record of your agreement and to stop codes being reused
Your sign-ins: a scrambled form of each sign-in key, when it was made and last usedNobodyTo keep you signed in

We don’t store your IP address. To slow down people guessing passwords, the server briefly counts attempts per address in its memory. That count is never saved and disappears within the hour.

Images are shown through long, random links. Anyone who has an image’s exact link can open it, so don’t upload anything you wouldn’t want shared.

3. Why we’re allowed to (legal bases)

4. Where it’s kept, and who else is involved

Budgie’s server is a single computer looked after by Budgie’s developer. The database on it is protected by the computer’s security, and nightly backups are kept on the same computer, with occasional copies on a storage drive in the developer’s care. As the person who runs the server, the developer can technically open the database, private messages included. We only do so to fix problems, handle reports about a specific message, or when the law requires it.

All three may process data outside the EU, under their own safeguards for international transfers. Budgie’s own fonts, icons and colour library come from the same site; the only thing loaded from another company is Google’s ads.

5. How long we keep it

6. In your browser

Budgie itself doesn’t use cookies. It keeps one thing in your browser’s storage: your sign-in key, so you stay signed in. That’s strictly necessary for the service you asked for, so under EU rules (the ePrivacy Directive) it doesn’t need consent. Signing out removes it.

The ads are different: Google may keep cookies or similar data in your browser for them. In the EU, the UK and Switzerland, Google’s consent message asks you first. If you say no, you get limited ads that don’t use that data for advertising. You can change your answer any time in Settings → Privacy and legal → Ad cookie choices. Wherever you are, you can also manage Google’s ads in My Ad Center and block cookies in your browser’s settings.

7. Your rights

Under the GDPR you have the right to access, correct, delete, restrict and move your personal data, and to object to how it’s used. You can do most of this yourself:

For anything else, contact us (section 1). We’ll answer within a month. You also have the right to complain to a data protection authority, for example in the country where you live.

If you’re in the United States: we don’t sell your personal information, and because we ask Google for non-personalised ads, we don’t use it for targeted advertising. That’s true under the California Consumer Privacy Act and other state privacy laws.

8. Automatic decisions

Budgie’s moderation rules decide automatically whether some text can be posted (see the Terms of Use, section 7). They run on your device and again on the server, only look at the text being posted, and don’t make decisions with legal or similarly significant effects on you. Reports are reviewed by a person. If you think a rule or a decision got it wrong, contact us and a person will look at it.

9. Security

Connections to Budgie are encrypted (HTTPS). Passwords are stored with scrypt, a slow one-way hash, and sign-in keys and recovery codes only as hashes. The server only answers Budgie’s own website and only listens behind its encrypted tunnel. If something ever goes wrong with your data, we’ll tell you and, where the law requires it, the authorities.

10. People named in the credits

Budgie’s credits name the people who made and tested it, with their agreement. If you’re named and want your name changed or removed, contact us and we’ll do it.

11. Children

Budgie isn’t meant for children under 13, and we don’t knowingly let them sign up. Between 13 and your country’s age of digital consent (up to 16 in the EU), you need a parent’s or guardian’s permission to use Budgie. Ads on Budgie aren’t personalised for anyone, whatever their age. If you believe a child under 13 has an account, contact us and we’ll delete it.

12. Changes

If we change this policy in a way that matters, we’ll tell you in the app before it applies. The date at the top always shows the latest version.