Drafted, pending solicitor sign-off. This page reflects how FeeBee actually collects and handles data today, but hasn't yet had a final legal review — don't treat it as finished legal copy until it has.
Privacy Policy
This policy explains what FeeBee collects, why, who it's shared with, and the rights you have over it, under UK GDPR and the Data Protection Act 2018. For a quicker, friendlier overview, see the Privacy Center.
What we collect, and why
When you create an account: your email, username, name, and date of birth (used to work out whether your account can post tasks, complete tasks, or both — see Trust and Safety for the age bands). When you post or apply for a task: the task details, and a location — only the town/area is ever stored as public; your exact address is kept separately and only shared with whoever you're matched with for that specific task. When you pay or get paid: your payment details, handled entirely by Stripe (see below) — we never see or store your card or bank details ourselves. When you chat, review, report, or block someone: that content, tied to your account.
We collect this on the basis that it's necessary to provide the service you' ve signed up for (contract), that age-gating is a legal safeguarding necessity given some accounts belong to 15-17 year-olds (legal obligation and legitimate interest), and that trust & safety features (reports, blocks, reviews) are a legitimate interest in keeping the platform safe.
Who we share it with
We use three companies to run FeeBee, each acting as a data processor on our behalf:
- Google Firebase — hosts our sign-in, database, and file storage. Nearly all account and task data passes through it.
- Stripe — processes payments and payouts. We pass it what's needed to charge a card or pay out a connected account; Stripe holds the card/bank details themselves, not us.
- OpenStreetMap (Nominatim) — turns an address you type into a place on the map while you're posting a task. What you type is sent to it as you type (after a short pause, and only once you've typed at least 3 characters, to limit this).
Google and Stripe may process data outside the UK; both provide standard contractual safeguards (UK International Data Transfer Agreements / EU Standard Contractual Clauses) covering this. We don't sell your data, and we don't use it for advertising — see our Cookie Policy for the full, short list of what's actually set in your browser.
Who can see what
Task listings and public profiles (username, rating, reviews) are visible to anyone browsing FeeBee, signed in or not. Chat messages are only visible to the two people in that conversation. Your exact address is only shared with the other party in a task once you've accepted or been accepted for it. Reports you submit are only visible to you and to FeeBee when reviewing them.
Under-18 accounts
FeeBee is used by 15-17 year-olds as Task Doers. UK GDPR sets the age at which someone can consent to their own data processing at 13, so no parental consent step is required — but we still try to minimise what a younger account needs to share: only a coarse town/area is ever public, never an exact address, and age-derived permissions are enforced by the platform itself, not just shown in the app.
How long we keep things
We keep account and task data for as long as your account is active. Payment records are kept for as long as UK tax/accounting law requires after a transaction. If you delete your account, see "Your rights" below for exactly what is and isn't removed, and why.
Your rights
- Access & portability. Download a copy of your profile, tasks, applications, messages, reviews, and notifications at any time from Account settings → Privacy settings.
- Rectification. Edit your name, username, bio, and photo directly from Account settings.
- Erasure. Deleting your account (also in Account settings) removes your login, profile, and any of your own open tasks or applications that nobody has been accepted for. It deliberately does not remove tasks or applications with an accepted counterparty, chat messages, or reviews — UK GDPR (Article 17(3)(e)) permits keeping data the other person involved has a legitimate ongoing interest in, such as a completed job, payment history, or evidence for a trust & safety dispute. If you want something removed beyond this, get in touch and we'll assess it individually.
- Objection & restriction. You can turn off individual notification types from Account settings → Notifications, or block another user from your profile or a task chat at any time.
- Complaints. If you're unhappy with how we've handled your data, you can complain to us via Help, or directly to the UK Information Commissioner's Office (ico.org.uk).
Security
Access to your data is enforced at the database level, not just in the app itself — so a request that doesn't genuinely belong to you is rejected before it can reach your data, regardless of how it's made. Payment actions require you to be signed in and independently verified as the account taking that action.
Changes to this policy
If how we handle your data changes meaningfully, we'll update this page and, for significant changes, let you know directly.
See also our Cookie Policy and Terms & Conditions.
