What we hold,
and what we do not.
Easybie collects what it needs to be a social platform and stops there. There is no advertising business here, so there is no reason to build a profile of you, and nothing in the product is trying to.
This page is meant to be read, not agreed to. It describes the software as it is today, including the parts that are unfinished — where something is missing it says so rather than leaving you to assume otherwise.
In force since 7 September 2026.
The short version
- Nothing is sold, and nothing is shared for advertising. There is no advertising.
- There are no third-party trackers, no analytics service and no error-reporting service. The page you are reading loads nothing from anybody else.
- If you switch on notifications for a device, a push service — Google's, Mozilla's or Apple's, depending on your browser — is involved, and only then. What we send it is an empty knock: no name, no words, nothing about what happened. Your browser then asks us what it was about, over your own session. They learn that something is waiting for one anonymous endpoint. Most sites send the notification's text through that service encrypted; encryption hides the words but not that somebody messaged you at 2am, and we would rather they did not know that either.
- Uploaded photographs are re-encoded, which removes the GPS coordinates a phone puts in them.
- You can download everything at once, and delete the account yourself without asking anyone.
- Deletion is immediate and cannot be undone.
Easybie was rebuilt, and this notice was written again from scratch rather than edited — from an audit of what the software actually stores, shares and deletes, checked against the list the GDPR's Article 13 asks for.
- Nothing new is collected, shared or sold as a result of the rewrite. What changed is that it is now written down, line by line, including the things that are not kept.
- The lawful basis for each thing, where it goes, and how long it is kept are named rather than summarised.
- Leaving is unchanged and still complete: you can export everything and delete the account yourself, without asking anybody.
- Since then: your About tab, the town in your profile header, the list of posts you are tagged in and the list of people who reacted to a post now need a reader to have an account, alongside the follower lists that already did. Nothing was deleted and nothing new is stored — what somebody without an account can see sets out exactly what moved, and which of it this really protects.
If you would rather not be here under it, that is a fair answer. Export your account and close it — your writing comes with you, and what is deleted is gone.
Who is responsible Copy a link to this section
Easybie is run by Arifur Rahman, who is the data controller for everything described here. He operates it as a sole trader (enkeltpersonforetak) registered in Norway under the name ARIFUR RAHMAN, organisation number 918 509 755; a sole trader and the person are one and the same party in law. The service and its database are hosted in the European Union.
Anything about your own data goes through the request form, which needs no account, or by email to info@easybie.com. Ordinary questions go through the help desk inside the product.
What we collect Copy a link to this section
To make an account
A username, a display name, an email address and a password. The password is hashed and is never stored or recoverable in a form anybody can read — including us. Everything else on a profile is optional: a bio, a location you type yourself, a website, a birthday, links, work and achievements. None of it is asked for at sign-up and all of it is public if you fill it in.
What you post
Posts, replies, articles, photographs, polls, events, groups, reactions, follows and messages. This is the product: it is stored because it has to be for anybody to read it.
Messages
Direct messages are private between the people in the conversation and are not read, scanned or used for anything. Their text is encrypted where it is stored, so the database on its own — a stolen backup, a stray dump — does not give anybody your words. They are NOT end-to-end encrypted: the key sits on the same server, so somebody who takes the whole machine takes the key with it, and a moderator can still be shown a single message you report. Say nothing here you would not put in an email.
A record of signing in
Each signed-in device leaves a session row holding the IP address it connected from and the browser it reported. Settings → Where you are signed in lists them and ends any one you do not recognise, and you are told when a device signs in for the first time. Sessions expire after thirty days and expired ones are deleted every hour.
A single "last seen" timestamp
Updated at most once every two minutes, and only on ordinary page loads. It exists so that an email is not sent to somebody who is already looking at the page. There is no history behind it — no record of which pages you opened or when.
Reading, counted without knowing who
An article counts a reader as a one-way hash of the address, the browser and the day, salted with a key we hold. The address itself is never stored, the salt changes at midnight so yesterday's hashes cannot be recomputed, and the rows are deleted after sixty days. It can tell that an article was read twice; it cannot tell that it was you.
Why we are allowed to Copy a link to this section
Data protection law asks for more than a list of what is held: it asks what entitles us to hold each thing. There are four answers on Easybie and none of them is consent to advertising, because there is no advertising to consent to.
| What | On what basis |
|---|---|
| Your account, your posts, your messages | Performing the agreement you made when you signed up. Without this there is no service to provide — you cannot have a profile without us storing a profile. |
| Sign-in sessions, rate limits, abuse controls | Our legitimate interest in keeping the service secure and usable for everybody. We think this is uncontroversial: nobody has an interest in a platform that spammers can flood. |
| Anonymous reading counts | Legitimate interest in knowing whether anybody read an article. Built as a rotating one-way hash precisely so this basis is proportionate — the least it can be and still answer the question. |
| Moderation records, and reports about you | Legal obligation, and our legitimate interest in enforcing our own rules. The Digital Services Act requires a notice-and-action mechanism, and a mechanism with no record is not one. |
| Anything optional on your profile | Your choice. Nothing asks for a bio, a birthday or a location, and removing them removes them. |
What decides things automatically, and what does not Copy a link to this section
No account is ever suspended, restricted or removed by software. Every one of those is a person reading a case and writing down why, and that has not changed. Nor does anything here predict what you will do, or build a picture of you from what you read.
Two things do act on their own, and this page used to say that nothing did. That was true when it was written and stopped being true when the platform started dealing with bulk advertising, so here is what they are.
A post can stop being amplified. A nightly rule looks at recent posts and asks three questions about them — is this picture posted by other accounts, are these words, does this link go to a site we have refused. A post it decides against stays up, stays on your profile and stays visible to anyone who follows you; it leaves the public feed, Explore, search and the sitemap. You are told, you are told plainly that a rule and not a person decided it, and you can ask a person to look — a person then reads it and answers you either way. Separately, and for the first day only, a brand-new account with no followers keeps its posts with links off those same listings.
A post can be hidden while a person checks it. The same rules score every new post, and a very small number of them score far above the level at which reach is taken away — several signals at once, not one bad-looking link. Those are hidden from everyone except you, straight away, and put in a queue for a moderator. You are told the moment it happens, you are told a rule and not a person did it, you can still see the post yourself, and you can ask for it to be looked at. A person then decides: shown again, or removed with a reason you can appeal. Nothing stays hidden because a rule said so — it stays hidden until somebody reads it.
Your account carries a number. It counts three things and nothing else: whether a person granted you a badge, whether you are a moderator, and how many people follow you. It exists so that the rules written for accounts that signed up yesterday do not get applied to people who have been here for years. It is not a prediction and it is not a judgement about you — a moderator can see it on your account page, and so can you, by asking for your data.
Rate limits also act on their own — they count how fast an account is doing something and ask it to wait. Those decide nothing about you and leave no mark. Nothing in any of this has a legal effect on you or anything close to it. The furthest any of it reaches is one post: how widely it is shown, or whether it waits out of sight until a person has read it. No software here deletes anything and none of it touches your account, and a person will look at any of it if you ask.
What we do not collect Copy a link to this section
Anything about where a photograph was taken Copy a link to this section
Every uploaded image is decoded and written out again as a new file. Nothing from the original survives that, including the EXIF block — which is where a phone writes the exact coordinates the picture was taken at, by default, without saying so. It matters most on a profile picture, which is very often taken at home. The original filename goes the same way.
Anything biometric Copy a link to this section
You can name the people in a photograph. What is stored is the rectangle somebody drew and the person they chose — four numbers and a name. Nothing reads the picture. There is no face template, no descriptor and no automatic detection of any kind, so nothing here can recognise the same face in another photograph, on Easybie or anywhere else. There is no facial-recognition code in this product and there never has been.
A birthday anybody can see Copy a link to this section
The birthday on a profile is a day and a month, with no year — it is optional, it is social, and it exists so people can say happy birthday. The year lives somewhere else entirely: a date of birth asked once at sign-up, used only for the age limit, shown to nobody. Two fields rather than one, so clearing the birthday you share never touches the record, and the record is never on display.
Any of the usual tracking Copy a link to this section
No analytics service, no advertising pixel, no error-reporting service, no fingerprinting, no cross-site anything. The browser is also told explicitly not to put you in an interest cohort. There is no advertising on Easybie, which is why none of this exists rather than why it is switched off.
Cookies, and the small things stored in your browser Copy a link to this section
There is no cookie banner because there is nothing to consent to. Every one of these is needed for the thing you asked for, and none of them is used to follow you anywhere:
| What | Why |
|---|---|
| A session cookie | Keeps you signed in. It holds an identifier and nothing else — the session itself lives on the server. |
| A "remember me" cookie | So signing in lasts beyond closing the browser. |
| A CSRF token | Stops another site submitting a form as you. Standard, and required. |
| locale | The language you picked, for a year. |
| watch_theatre | Whether Watch uses the wide layout, for a year. |
| theme and scheme | Light or dark, and the colour set — kept in the browser as well as on the account so the page does not flash the wrong colour before it loads. |
What somebody without an account can see Copy a link to this section
Reading Easybie needs no account, and that is deliberate: your posts, your articles, your pictures, your replies and your profile are readable by anyone, which is what makes them worth writing. Five things are not, and they are not because each one is a way to learn something about you that you did not set out to publish.
- Who follows you, and who you follow. Every name on those lists belongs to somebody who chose to follow — not to be catalogued for strangers.
- Who reacted to a post. The count stays public, because it is part of the post. The names do not: reacting is an opinion about one piece of writing, and nobody leaving one asked to be gathered into a list under it.
- Your About tab. It is the only place on Easybie that holds where you live, where you work, your job titles and their dates. Name, face, town and employer on one screen is how a stranger finds a person in the real world.
- The town in your profile header. It went with the About tab, because a locked tab over a fact printed four lines above it protects nothing.
- The list of posts you are tagged in. Those were written by other people about you, and you did not ask for them to be gathered into one place under your name.
Two of those are worth being precise about. Your About details genuinely exist nowhere else, so a sign-in really does withhold them. A post that tags you, on the other hand, stays public on its own page — what needs an account is the collected list of them. The difference is real, and we would rather write it down than let the lock imply more than it does.
None of this is a judgement about who is asking. It is that "everything about this person, free, in one request, with no idea who wanted it" is the shape of the problem, and an account is the smallest thing that changes it. Your replies stay open to everybody: each one is already readable on the post it answers, so hiding the tab would cost you readers and protect nothing. If you want the stricter version, Settings → Privacy can make the whole account private.
Who else sees any of it Copy a link to this section
Nobody buys it, and nobody is given it for advertising. Data leaves the server in seven places, all of them because the product asked it to:
A video you share
When somebody shares a YouTube, Vimeo, Spotify, SoundCloud, TikTok, Bandcamp or Dailymotion link, our server — not your browser — asks that site for the title and thumbnail once, and then keeps its own copy of the thumbnail. Reading the post contacts nobody. The player only loads if you press play, and then it is you visiting them, at which point their privacy policy applies rather than ours. Autoplay is off by default and stays off by default, for exactly this reason.
A link somebody pastes
To draw a preview card, the server fetches the page in a background job. It sends no cookies, no referrer and nothing about you — the site sees a request from Easybie, some time after the post was written, and cannot tell who wrote it or who read it.
GIF search
If the GIF picker is switched on, what you type in it goes to the GIF provider to get results back. Nothing else does. The GIFs themselves are fetched by our server and served from our domain, so browsing them does not put you in front of theirs.
Notification and account email is handed to whichever mail server the operator has configured, which necessarily sees the address it is delivering to.
Proving you are a person
The sign-up form, the password-reset form and the request form on this page carry a Cloudflare Turnstile challenge, and only those three. Your browser loads a small script from Cloudflare and answers a question it sets; the answer and your address are sent to Cloudflare so it can tell us whether to believe it. No cookie is set for it, nothing about it is kept here, and no other page on Easybie contacts them at all. It was chosen over the alternatives because the usual ways of telling a person from a script — device fingerprinting, a bought reputation feed, a phone number — all work by building a record of you.
Signing in with Google
Only if you press that button. Google then knows you signed in to Easybie at that moment, and tells us your Google account id, your email address, whether Google has verified that address, and the name on the account. Nothing else, and nothing about what you do here afterwards. The button itself contacts nobody until you press it — the logo on it is drawn by us, not fetched from them — so a visitor who never uses it is never reported to Google at all. If you disconnect it in Settings, the link is deleted here; what Google keeps is theirs and is covered by their policy.
Backups, kept somewhere other than this server
Everything here lives on one server, so a copy of the database and of uploaded pictures is sent to storage at Backblaze — otherwise losing that one machine would lose the platform and every backup of it in the same second. The copies are encrypted on this server first, with a key that is not sent with them and that Backblaze does not have, so what they hold cannot be read by them or by anybody who obtains it from them. Nothing is ever read back from those copies in the ordinary running of the site; they exist only to rebuild it. Private messages are separately encrypted before they are even written here, so they are unreadable in a backup twice over.
Uploaded files are stored on our own server, and served from it — no content-delivery network holds your pictures. Encrypted backup copies are kept off this machine, as described above; nothing is read from them in the ordinary running of the site. We will also hand over data where the law actually requires it, which means a valid order rather than somebody asking.
What a moderator can see, and what that leaves behind Copy a link to this section
A moderator can open the report queue, anybody's account page, and a private message that somebody reported — that message and nothing else from the conversation. That is the whole list. There is no screen anywhere that shows a moderator your inbox.
Every one of those is written down: which moderator, what they opened, and when. Not only the decisions they make — the looking itself. Most misuse of a moderation tool is reading rather than acting, and reading is the part that used to leave nothing behind. The record keeps no copy of what was read, because a log that quoted your message would be a second copy of it somewhere with weaker rules than the first.
That record is read, which is the half most platforms skip. Every moderator can see what every moderator opened, including their own looks — and once a week a summary is emailed to whoever runs the site, singling out any account that was opened when there was no report about that person or about anything they posted. That is a question rather than an accusation, and there are ordinary answers to it, but somebody has to be in a position to ask. The summary is sent whether or not there is anything in it, because a report that only arrives when something is wrong is indistinguishable from one that stopped working.
Access records are kept for six months and then deleted. Moderation decisions are a different record and are kept — the two live in the same place and expire on different clocks, on purpose. Six months is long enough to answer somebody who suspects weeks later that they were looked at, and short enough that this does not become a permanent file on which moderator was where on which evening.
Moderator accounts are also required to sign in with two factors. That is optional for everybody else and not optional for them, and the reason is the difference between protecting your own things and holding somebody else's.
Data leaving Europe Copy a link to this section
Easybie itself is hosted in the EU and your data stays there. The exception is pressing play on a shared video, or searching the GIF picker: those companies are mostly American, and at that moment your browser is talking to them directly under their own terms rather than ours. That is the reason the video loads nothing until you press it, and the reason autoplay is off by default — so the choice to make that request is always yours, and always deliberate.
The encrypted backup copies described above are held in the European Union as well. They are encrypted before they leave this server, so they would be unreadable wherever they sat — but a backup is still your data, and where it rests is still a promise rather than a detail.
Children Copy a link to this section
Easybie is not for children under 13. A date of birth is asked for once, when the account is made, and it is used for one thing: working out whether somebody is old enough. It is never shown to anybody, never appears on a profile, and cannot be changed from any settings screen — the birthday your friends can see is a different, optional field that carries no year at all.
Being straight about the limits of that: it records what somebody stated, and it does not verify it. Nothing short of an identity document could, and demanding one to read a feed would be a far worse trade than the problem it solves. Accounts made before this was asked have no date on file and are not pretended otherwise. If you believe an account belongs to a child, tell us and it is closed.
How long it is kept Copy a link to this section
Until you delete it Copy a link to this section
Posts, messages and everything else on a profile stay until you remove them or close the account. There is no automatic expiry, because a platform that quietly deleted your writing after a year would be a worse one.
On a timer Copy a link to this section
A Today post is deleted for good after twenty-four hours, along with its pictures — unless it has been reported and the report is still open, in which case it is hidden from everybody and kept until that is decided. Sign-in sessions last thirty days. The anonymous reading rows last sixty. Failed background jobs are cleared after a week.
After a suspension Copy a link to this section
When an account is suspended, a moderator may also stop that inbox opening a new one. What is stored is a one-way hash of the mailbox and the reason — never the address itself, so the list cannot be read back into the names of the people it covers. It answers one question, “is this the same inbox”, and nothing else. Lifting the suspension removes it, and a block can be given an expiry date when it is made.
Kept on purpose Copy a link to this section
Every username an account has ever used is kept permanently, released by nobody, so that an old link still leads to the right person and a handle somebody abandoned cannot be picked up to impersonate them. Moderation decisions are kept as a record — including the decision to leave something up, because a log that only records removals cannot be reviewed.
Deleted immediately Copy a link to this section
Closing the account. It is a real deletion, not a hidden row: the account, its posts, articles, follows, blocks, mutes and reactions go, and the uploaded files are removed from disk. There is no grace period and no undo — an account that is "deleted" but quietly recoverable is exactly what the right to erasure exists to prevent, so we would rather be blunt about it before you press the button than keep a copy in case you change your mind.
What you can do Copy a link to this section
Under the GDPR you have rights over your own data. Two of them are buttons in Settings rather than a request somebody has to grant:
Take it with you Copy a link to this section
Settings → Account → Download my data gives you a JSON file straight away: the account, every setting, every post including ones you deleted, every article including the drafts and the private ones, the metadata of everything you uploaded, who you follow, who follows you, who you blocked and your muted words. Also your own messages, the rooms and events you are in, tags other people put on you, and a link to every picture you uploaded. Not emailed, not queued, not "within thirty days" — downloaded.
One thing is deliberately absent, and it is worth saying why: a conversation has two people in it, and the other person's messages are their data rather than yours. So you get your own words in full and, of theirs, only that the conversation happened and who it was with. The same reasoning keeps names off your notifications — what arrived and when is yours; who caused it is a record of somebody else.
Leave Copy a link to this section
Settings → Account → Delete account. Your password and your username, typed once each, and it is done. Nobody has to approve it and nobody will email you to ask why.
Correct it, or narrow who sees it Copy a link to this section
Everything on a profile is editable by you, including the username. Settings → Privacy decides who may message you, reply to you, mention you, tag you, and whether your account is private or listed for search engines at all. Tags of you wait for your approval before anybody sees them.
You have four more rights that are not buttons, because they need a person to read what you are asking:
- Access. A copy of what we hold, including anything the export leaves out.
- Correction. Anything wrong that you cannot edit yourself.
- Restriction. Tell us to hold something still — not delete it — while a disagreement about it is settled.
- Objection. Object to anything we do on the basis of our own legitimate interest, and we stop unless we can show a reason that outweighs yours.
All four go through the request form, or to info@easybie.com. You do not have to be signed in and you do not have to have an account at all — if you appear in somebody else's photograph, the data is about you and the rights are yours. We answer within a month. Before handing over or deleting anything we will check the account is yours, which is not obstruction: without that check, anybody could ask for your data by typing your name into a form.
If we get it wrong, complain to your national data protection authority — in Norway, Datatilsynet. You do not have to come to us first.
Being straight about what is missing Copy a link to this section
Easybie is in beta and this section will get shorter. Today:
- Messages are encrypted where they are stored, but not end-to-end — the key is on the same server. That protects the database on its own, not somebody who takes the whole machine.
If something on this page is not true of the product, that is a bug and worth saying so. See also the terms, the community standards and what Easybie is.
Check it yourself.
The export button and the delete button are both two clicks from here.