Privacy Policy
Last updated: 5 November 2026 · Effective from: 5 November 2026
What changed on 5 November 2026: section 3.13 is new. It says that a shop can let a member of the Sellexa team into its seller account to set up its listings and shop page, what that person can see and change, that every change they make is recorded with their name, who sees that record and how long we keep it. Sections 2, 4 and 8 now point to it. Nothing about buyers changes, and nothing is open to a helper until the shop adds them or says yes, so this applies from the day it was published. Later on 5 November 2026, section 3.13 now says that a helper can see the shop's collection phone number, but not change it, on the screens for the shop's pickup times and shop page as well as on the listing form, and that we delete the record of a helper's changes, and a helper's access once it has ended, 2 years later instead of keeping them while the shop's account exists. Sections 2 and 8 say the same. We now keep less, and the helper is Sellexa staff, so this applies from the day it was published. Also on 5 November 2026, section 3.2 now says that for a shop with premises buyers can walk into, buyers see the name of the street the shop is on beside its listings, never the number, once the shop has agreed to version 2026-11-05 of the Sellexa delivery terms, which say so. A seller who sells from home has no street shown. Sections 4 and 7 say the same. Nothing about buyers changes, and the street is shown only for a shop that agreed to it, so this applies from the day it was published. What changed on 31 October 2026: section 3.12 is new. It says how we learn what brings people to Sellexa: from records of your first order that we already hold, from your answer if you choose to answer one optional question after your first order, and from a yes or no mark our founder may add if he already knew you. Sections 2, 4 and 8 now point to it. Nothing is stored in your browser, nothing is shared outside Sellexa, and nothing about your orders changes, so this applies from the day it was published. What changed on 27 October 2026: sections 3.8 and 12 now say that at a shop Sellexa packs for, the rider sees the lines of your order (each item, its size, how many, its shelf price and its photo) while the order is still at the shop, because the rider packs it from the shelves, and that those lines leave the rider's screen when the shop releases the order; at a shop that packs its own orders nothing changes. The rider was already the person carrying your order and works under Sellexa's written instructions, no outside company receives anything new, and the lines are used only to pack your order, so this applies from the day it was published. Earlier, on 12 October 2026: section 3.9 now says that a rider gives their identity and bank details in a secure Stripe form inside their rider account and is paid through Stripe straight to their bank account; Stripe still holds those details and we still never see them, so nothing new is collected or shared and this applies from the day it was published. Also, section 3.8 now says that when nobody answers and you typed no safe place, the rider leaves your order at your front door or, if they cannot get into your building, at its entrance door, that we record when your safe place could not be used and the order was left at your door instead, and that we no longer record missed visits, because no order is taken back; the photo and the record are the ones we already kept. Sections 3.8 and 6 also now call it your delivery PIN and say where you find it: on your order page and in the email that tells you your order is on its way. Nothing new is collected or shared, so this applies from the day it was published. What changed on 11 October 2026: sections 3.10 and 3.11 are new. Section 3.10: where a shop offers Collect and you choose it at checkout, you can tick a box asking us to message you on WhatsApp when your order is ready to collect; the section says what we store if you do, what the message contains, and that it is a message about your order and never marketing. Nothing is stored or sent unless you tick the box, and the box tells you this at the moment you tick it, so this change applies from the day it was published rather than after the 14 days in section 14. Section 3.11: a shop you message can now key the order you asked for into Sellexa and send you a link to pay; the section says what the shop types and we hold, who can see it, that paying through the link creates a Sellexa account on the email you type, why the WhatsApp box on that page is ticked for you and how to untick it, and when an order that is never paid is deleted. Nothing is keyed unless you asked the shop for something, nothing happens on Sellexa unless you open the link and pay, and the page tells you what it does at each step, so this change too applies from the day it was published. Section 3.8 also now says that the shop records the collection of a Sellexa delivery order, after entering a collection code the rider shows it, instead of the rider typing a code at the shop, and sections 5 and 6 that the rider sees that code and the order number printed on the bag label, no longer the order code; nobody new receives your data, so this applies from the day it was published too. Section 3.8 also now says that when nobody answers and you typed no safe place, the rider leaves your order at your front door and photographs it there, and that we record that it was left there; it is the same photo and the same record we already kept, so this too applies from the day it was published. Section 3.8 also now says that the photo is taken only when the order is left without you, in your safe place or at your front door; when you take it in person, the PIN check is the record and no photo is taken. Section 8 now says that the first name of whoever took the order is deleted after the same period as the photos. We now keep less, so this too applies from the day it was published. The 10 October 2026 change stands: riders now have their own rider account on Sellexa's systems, which is how they apply, upload their insurance document and set up their Stripe account, and section 3.9 is new: it says what we hold about riders themselves and for how long. From the day Sellexa delivery runs open to riders, a rider who holds a run sees the delivery details for each stop on that account, only while they hold the run, instead of being handed them by the Sellexa team; sections 3.8, 5 and 6 now describe that view, and are written to be true both before and after that day. Section 3.8 also now says that a rider who finds nobody in calls your delivery number from their own phone, and that we record the attempt, not the call. Nobody new receives your data and the set of details a rider sees is unchanged, so these changes apply from the day they were published rather than after the 14 days in section 14. The 8 October 2026 change stands: no courier carries Sellexa delivery orders, and Stuart Delivery Ltd receives nothing from us.
1. Overview
This policy explains how Sellexa Limited (company number NI735255, registered office West Circular Close, 187 West Circular Road, Belfast, Northern Ireland, BT13 3QF) handles your personal data when you use sellexa.app. We comply with the UK GDPR and the Data Protection Act 2018.
2. Snapshot (UK GDPR Art. 13 transparency table)
| Controller | Sellexa Limited (NI735255) |
| Contact | support@sellexa.app · post above |
| Lawful bases | Performance of contract (Art. 6(1)(b)); legal obligation (Art. 6(1)(c)); legitimate interests (Art. 6(1)(f)); consent (Art. 6(1)(a)) for analytics and marketing cookies and for marketing emails |
| Categories of data | Account, KYC, payment metadata, order, delivery records (including, on orders Sellexa delivers itself, a photo where an order was left without you), message, device/log, marketing-preference, shared cart links, orders a shop keyed for you and sent you a link to pay (section 3.11), how you found Sellexa if you told us (section 3.12); for a shop that lets a Sellexa helper in, a record of the helper's changes (section 3.13); for riders, application, insurance, agreement and pay records (section 3.9) |
| Recipients | Stripe, Supabase, Resend, Netlify, Meta (WhatsApp order notifications to sellers, and the ready-to-collect message to a buyer who asked for it on a Collect order; Meta Pixel only with marketing consent), Google (analytics and advert measurement: IP address, page URL and device data), Plausible (cookieless analytics: IP address, page URL and device data), Parcel2Go and the chosen courier (delivery details for parcels Sellexa books), Sellexa's own riders (delivery details for orders Sellexa delivers itself, on Sellexa's instructions), postcodes.io (the delivery postcode only, to work out a delivery fee); sellers (delivery info only); HMRC (DAC7); law enforcement (where compelled) |
| Retention | Account: until deletion or 24 months inactive · Orders + ledger entries: 7 years (HMRC + Companies Act) · Messages: 24 months · Notifications outbox: 12 months · Logs: 12 months · Browsing and click records: 12 months · Search terms: 90 days · Request counts for abuse prevention: 1 day · Shared cart links: stop working after 30 days, deleted 7 days later · Orders a shop keyed for you: the pay link works for a day, and an order never paid is deleted 7 days after the link ran out · How you found Sellexa: while your account exists · Record of a Sellexa helper's changes, and helper access that has ended: 2 years |
| International transfers | Some processors (Stripe, Resend, Netlify, Meta, Google) may process data in the US, under the UK Addendum to EU SCCs or a UK adequacy decision; Plausible processes data in Estonia (EU), covered by UK adequacy for the EEA |
| Your rights | Access, rectification, erasure, restriction, portability, objection, withdraw consent, complain to ICO |
3. What we collect
3.1 Account data (all users)
- Name, email, password hash, optional profile picture and bio.
- Buyer delivery addresses you save.
- Delivery phone number. Required at checkout, so your parcel can be delivered and the seller can reach you about that delivery. See section 5.
3.2 Seller-only data
- Business trading name, registered address, VAT/UTR (where applicable).
- KYC: identity verification handled by Stripe Connect; we receive only the verification status and a high-level summary.
- Bank-account details: held by Stripe; we never see the account number.
- Your shop's street. If your shop has premises buyers can walk into and you have agreed to version 2026-11-05 or a later version of the Sellexa delivery terms, buyers see the name of the street your shop is on on your product pages, never the house or unit number. We use the street from the collection address you gave us, so buyers know which shop the item comes from. If you sell from home, no street is shown. Lawful basis: our legitimate interest in showing buyers which shop an item comes from, on a street your shop already trades on (Art. 6(1)(f)). You can object: email support@sellexa.app and we will stop showing it.
- WhatsApp number. Required at onboarding, because a WhatsApp message is how we tell you a new order has come in. UK mobile numbers only. We never show it to buyers and never display it on your storefront. See section 3.6.
3.3 Order and transaction data
- Items ordered, prices, quantities, taxes, shipping cost, delivery address, and on a Collect order where you asked for it, the number we may message on WhatsApp (section 3.10).
- Stripe payment-intent IDs, charge IDs, refund IDs (no card numbers).
- Shipping tracking. For Simple orders, where Sellexa books the label through Parcel2Go, tracking is created automatically and we receive tracking updates from the Parcel2Go tracking API so you can follow your parcel. For Sellexa delivery orders, where a Sellexa rider carries the order, our own system records the collection and the delivery so you can follow it on your order page; see section 3.8. For seller-managed Custom orders, the seller types in a tracking number when they dispatch your parcel.
- Ledger entries (commission, payout, refund), retained 7 years per HMRC and Companies Act 2006.
3.4 Messaging data
- Order-scoped messages between buyer and seller. The original message body is retained for moderation audit (admin-visible only) even where our contact-info filter strips parts before delivery.
- Notifications outbox: email and WhatsApp sends and their delivery status callbacks (12-month retention for delivery diagnostics). For WhatsApp we keep a record that a message was sent and which order it related to; we do not keep a copy of the message body.
3.5 Device and log data
- IP address, browser, OS, approximate location (city level, derived from IP).
- Pages viewed, click-through, error logs, and the words you type into search (never anything shaped like an email address or phone number).
- A random browser code (the
sx_vid cookie) attached to your product views, clicks and searches, so suggestions can reflect what this browser has looked at. It holds a random code, not your name. See the Cookie Policy.
3.6 WhatsApp order notifications (sellers)
If you sell on Sellexa, we send you a WhatsApp message when one of your orders is paid, so you can pack and dispatch it. These are service messages about an order that has already been placed. We do not send marketing, offers, or promotions over WhatsApp. The one WhatsApp message we send a buyer is the ready-to-collect message on a Collect order, and only where the buyer asked for it; see section 3.10.
- Where the number comes from: the WhatsApp number you gave at onboarding. Lawful basis: performance of contract (Art. 6(1)(b)), because dispatching on time is your obligation under the Seller Agreement.
- What is in the message: your business name, the order reference, the order total, and the number of items. We never put the buyer's name, address, phone number, or any payment detail in a WhatsApp message.
- Who else sees it: to deliver the message, your WhatsApp number and the message content pass to Meta, which runs the WhatsApp Business Cloud API for us as our processor. See section 6.
- Buyers never receive your WhatsApp number. Messages are sent from Sellexa's own business number, and your number is never shown to buyers or on your storefront.
- Turning it off: email support@sellexa.app and we will stop sending WhatsApp messages to your account. You keep getting order alerts by email and in the seller dashboard, so you will not miss an order.
3.7 Shared carts ("Share cart")
On your cart page you can press "Share cart" to make a link to the items in it, and send that link to anyone you like. The page the link opens is called a shared list. Nothing is shared unless you make a link. We make and keep the link because you asked us to (lawful basis: performance of contract, Art. 6(1)(b)).
- What we store for each link: the products, the portion of each (the size or option you picked) and the quantity. That is all we keep from your cart.
- Your account: if you are signed in when you make the link, we store your account id with it, so you can turn the link off and so it is deleted with your account. If you are signed out, we store nothing about you with the link.
- Your first name, only if you choose: the share sheet has a "Show my first name" switch. It is off by default, and only a signed-in sender has it. We store whether the switch is on, never the name. Each time the link is opened while the switch is on, we read the first word of the name on your profile at that moment and show it ("Ada sent you a list"). Never your surname, your picture or anything else. Switch it off and the name stops showing.
- A fingerprint of the link, not the link: our database keeps only a fingerprint of each link (a "hash": a one-way scrambled form). We can check a link that someone opens against it, but nobody, including us, can turn the fingerprint back into a working link. It also means we cannot show you a list of links you made earlier.
- What never travels with a link: your address, your discount codes, your payment details, your delivery choices, your totals, your order history, and prices. Prices are not stored at all: the shared list shows each store's price on the day it is opened.
- What we never do: we never send the link for you, we never ask for or collect the contact details of the person you send it to, and we never tell you who opened a link or whether anyone did. We keep no record against a link of who opened it.
Turning a link off. If you were signed in when you made a link, you can turn it off with "Turn off this link" while the share sheet that made it is still open, and you can turn off every link you have made while signed in, at any time, with "Turn off all my shared links" in the share sheet on your cart page. Because we keep only fingerprints, we cannot pick out one earlier link for you, which is why that control turns them all off together. A link made while you were signed out belongs to no account, so it cannot be turned off early. It stops working by itself after 30 days. Sign in before you share if you want to be able to turn a link off sooner. How long we keep links is in section 8.
Analytics and a shared list's address. The address of a shared list works like a key: anyone who has it can open the list. So we keep it away from analytics and advertising companies. Google's and Meta's scripts are not loaded at all in a browser tab that opened on a shared list, and our own code sends them nothing from a shared list page. Plausible, our cookieless page counter, is sent nothing from a shared list page unless you have allowed analytics cookies, and even then the address reaches it only as "/list/_", with the key taken out.
Limits on making links. To stop misuse we limit how many links can be made in an hour. That uses the short-lived request counts described in section 8 and stores nothing new about you.
3.8 Delivery records on orders Sellexa delivers itself
Where a shop offers Sellexa delivery and you choose it at checkout, a rider working for Sellexa collects the order from the shop and brings it to you. No outside delivery company is involved, so we keep the record of that delivery ourselves, on Sellexa's own systems. From the day Sellexa delivery runs open to riders, the shop records the collection, after scanning or typing the code the rider who holds the run shows it, and that rider records the handover on their own rider account; until that day a member of the Sellexa team records both, and the team can still record either at any time. The lawful basis is performance of your contract (Art. 6(1)(b)), and for the photo, our legitimate interest in being able to show an order arrived if that is ever disputed (Art. 6(1)(f)).
- Safe place. If you type a safe-place instruction at checkout (for example a neighbour or a porch), we store it with the order and the rider making the delivery sees it for your stop (until runs open to riders, the Sellexa team passes it to them). If you do not type one, or the rider cannot use it, and nobody answers, the rider leaves the order at your front door, or at your building's entrance door if they cannot get in, as the checkout tells you before you pay.
- Who took it and when. We record when the order was collected, when it was delivered, whether it was handed to a person, left in your safe place or left at your door (and if your safe place could not be used, that it could not), and for a handover the first name of the person who took it (deleted after the period in section 8). When nobody answers the door, the rider calls your delivery phone number from their own phone before leaving the order; we keep the time the order was left, not the call, and your number may stay in the call history on the rider's phone, which the Rider Agreement binds them to use for that delivery only. An in-person handover is confirmed with your delivery PIN, which is on your order page and in the email that tells you your order is on its way: whoever takes the order reads it out, the rider types it, and our system checks that it matches. That check is our record of an in-person handover, and no photo is taken. The rider is never shown the PIN.
- A photo when it is left without you. When the order is left in your safe place, at your front door or at your building's entrance door, the rider takes one photo of it there, as our record that it arrived and where it was left. When you take it in person, no photo is taken. The photo is stored against the order when the delivery is recorded (from the rider's own account once runs open to riders; by the Sellexa team until then). It is kept in private storage that only Sellexa staff can open, is never shown to the seller, and is not used for anything other than checking a delivery if you or the seller question it. It is deleted automatically after the period in section 8; the rest of the delivery record stays with the order. A photo taken on the rider's own phone may also stay on that phone.
3.9 If you ride for Sellexa: what we hold about riders
Riders are self-employed people who deliver Sellexa delivery orders under the Rider Agreement. If you apply to ride, you get a rider account on Sellexa's systems, and this section is for you. Everything else in this policy, including your rights in section 10, applies to you as well.
- What we hold. The name you gave us; your mobile number, which we use to message you on WhatsApp when a run is ready (you can switch those messages off on your rider account); your vehicle type and, for a motor vehicle, its registration plate; the insurance document you upload and the expiry date you typed; the date, version and fingerprint of the Rider Agreement you agreed to; when you applied, when and by whom you were approved, and, if your account is paused, when and the reason you were given; whether your Stripe account is set up and whether payouts to it are enabled; the runs you claim, the record of each collection, delivery and attempt, and the photos you take at the door (section 3.8); and your pay for each delivery and attempt, and whether it has been paid.
- Why. To run your rider account, show you runs and pay you, under our agreement with you (Art. 6(1)(b)); to keep the records of what we paid you that tax and company law require, and to report to HMRC if the law on digital platforms applies to rider pay (Art. 6(1)(c)); and to check that you are insured for the work and to settle any question about a delivery you made (Art. 6(1)(f)).
- Your insurance document. It is kept in private storage that nobody can browse. A member of the Sellexa team opens it, to check your cover against what you typed, through a link that stops working after 60 seconds. It is not shown to shops or buyers, and you do not read it back from us.
- Stripe does the identity checks. You give your identity and bank details in a secure Stripe form inside your rider account. Stripe Payments UK Ltd checks your identity and holds your bank details, as it does for sellers; we never see them. We hold only whether your details are set up and whether payouts can be made, and your pay is sent through Stripe to your bank account.
- Who sees your name. The Sellexa team sees it on the run sheet and in the record of who carried an order. We do not show it to buyers or shops today; if that changes, this policy will say so first.
- How long. Your rider record stays with your account and is deleted when your account is deleted. The record of what we paid you is kept for 7 years, as all our order and ledger records are, and keeps your name and a reference to your Stripe account as they were when you were paid, so it stays complete after your rider record is gone. We delete the insurance document when your rider account is closed, and sooner if you ask under section 10; today that deletion is a step a member of the Sellexa team takes by hand, not an automatic one. See section 8.
3.10 WhatsApp messages about a Collect order (buyers)
Where a shop offers Collect and you choose it at checkout, you pick your order up from the shop, and we tell you by email when it is ready (Returns & Refunds Policy, section 8). You can also ask us to tell you on WhatsApp. Beside the delivery phone number you typed at checkout there is a box, unticked, that asks whether we may message you on WhatsApp at that number when the order is ready to collect. Tick it and we store, with that order only, the number you asked us to use. Leave it unticked and nothing is stored and nothing is sent: the email is the message.
- What we send: one message when the shop confirms your order is packed, saying it is ready, with the shop's name and the day and time it must be collected by, and telling you that your collection code is in your email and on your order page. It never carries the code itself, on any order: on an order a shop keyed for you, the WhatsApp number is one the shop typed (section 3.11), so we keep the code to your email and your order page. Never a price, your address, or anything to buy.
- Why, and what the tick is: telling you the order is ready is part of the Collect service you chose, so the lawful basis is performance of your contract (Art. 6(1)(b)). The tick chooses the channel; it is not a marketing consent, and we never send marketing to a number given this way. It is a message about an order you placed, not marketing.
- Who else sees it: to deliver the message, the number and the message content pass to Meta, which runs the WhatsApp Business Cloud API for us as our processor, as for the seller notifications in section 3.6. The message comes from Sellexa's own business number, not the shop's. The shop sees your delivery phone number as it does on any order (section 5) and nothing more.
- Only for that order: we use the number for messages about that order and nothing else. Today that is the one message above. If we add another message about the same order, it goes to that number, for that order only, and this policy will say so first.
- How long: the number stays with the order record, for the period in section 8, as the delivery phone number does. It is not copied to your account or used on any later order: each Collect order has its own box.
3.11 Orders a shop keys for you and sends you a link to pay (pay links)
Some shops take orders in their own WhatsApp conversation with you. Where a shop offers this, it can key the order you asked for into Sellexa, typing your name, your mobile number and either your delivery address or Collect, and send you a link to pay. The link opens a page on Sellexa that shows the order, and you pay there as you would on any order. Nothing is keyed unless you asked the shop for something. We hold the keyed order because you asked the shop for it and the shop asked us to take your payment: the lawful basis is the steps you asked for before a contract is made, and then the contract itself (Art. 6(1)(b)). The shop types the details from its own conversation with you, which it handles as an independent business (section 5); Sellexa is not in that conversation and keeps no record of it.
- What the shop types and we store: your name and your mobile number as the shop typed them; the items (which listing, which portion and how many, never a price: the page shows what the shop charges today); whether it is Collect or delivery; for delivery, the address the shop typed; and a short note from the shop to you, if it wrote one. Not your email: the shop does not type one and we do not ask it to.
- How the link reaches you: the shop sends it to you itself, from its own WhatsApp or however else it chooses. Sellexa does not send the link, and the only message we ever send to the number the shop typed is the ready-to-collect message on a Collect order where you left the WhatsApp box ticked (below). Our database keeps only a fingerprint of the link (a "hash", as for shared cart links in section 3.7), so nobody, including us, can turn our records back into a working link or list the links a shop has sent.
- Who can open it: anyone holding the link sees the shop's name, the items and the shop's prices on the day they open it, your name as the shop typed it, the last three digits of your mobile number, whether it is Collect or delivery, and for delivery your town and postcode. The full number and the rest of the address are shown only after you sign in. Whoever you forward the link to sees the same, so keep it as you would any message from the shop. Until you sign in, nothing else can be done with the link.
- What the shop sees: what it typed, whether the link has been opened and the time it was first opened, and whether the order has been paid. Sellexa sees the keyed order, as it sees any order placed through it. Nobody else sees it until you pay. When you pay, the order reaches the shop like any other order, with your name, your delivery address and your delivery phone number as section 5 describes; the number the shop keyed is the delivery phone number on that order.
- Paying creates an account: to pay, you type the email the receipt should go to and we email you a six-digit code. Entering the code signs you in on that device. If there is no Sellexa account on that email, one is created at that moment, with the name the shop typed as its display name, which you can change in your profile. If there is already an account on that email, it is signed in and the order goes onto it. An order can never be put onto an account whose holder did not enter the code. We never set a password for you; you can choose one later with "Forgot password". Your email goes onto your account, not onto the shop's keyed record, and the shop never sees it. If you ask for a code and never pay, the account stays empty, and you can ask us to delete it under section 10.
- The WhatsApp box on a Collect order: the pay page for a Collect order has the box described in section 3.10, and on this page it is ticked for you, because the number beside it is the one you messaged the shop from: it is a WhatsApp number, and you chose that channel when you messaged the shop. One tap unticks it. The ready email goes either way and is the only message that carries your collection code. Everything in section 3.10 applies: the number is stored with that order only, used for the one ready message, and never for marketing. A delivery order has no box.
- Analytics on the pay page: the link's address works like a key, so it gets the same treatment as a shared list (section 3.7). Google's and Meta's scripts are not loaded in a browser tab that opened on a pay link, our own code sends them nothing from that page, and Plausible is sent nothing from it unless you have allowed analytics cookies, and even then sees the address only as "/pay/_", with the key taken out.
- How long: a link works for a day after the shop sends it. The shop can send a fresh one, which makes a new link, and the old one stops working. If you pay, the keyed order stays with the order record, for the period in section 8. If you never pay, or the shop cancels it, a scheduled job in our database deletes the keyed order, with your name, number and address on it, 7 days after the link ran out or was cancelled; the job runs once a day, so it can take up to a day longer. The keyed order is the shop's record of a sale it tried to make, so deleting your account does not delete it early: it goes on that schedule, and any order you paid for is handled as every order is.
3.12 How you found Sellexa
We want to know what brings people to Sellexa, so we spend our time and money on what works. We find this out in three ways, and none of them stores anything in your browser.
- From your order. If your first order came through a link a shop sent you to pay (section 3.11), or used a shop's first-order code, our record of that order already shows it. We count these. We collect nothing new to do it.
- If you tell us. After your first order, the page that confirms it may ask how you found Sellexa, with a short list of answers to tap (for example a sign in a shop, a flyer, a friend or an advert). Answering is up to you. If you do not answer, nothing is stored and nothing changes. If you do, we store your answer with your account and that order. There is no box to type in.
- Whether our founder already knew you. Our founder may mark in our records that he knew you before your first order. It is a simple yes or no. It does not record how he knows you. We use it only to count how many of our buyers are new to us, and it never changes what you pay or how your orders are handled.
- Who sees it. Only the Sellexa team, on our own admin pages. Your answer is only ever shown as part of a total, for example how many first orders came from flyers and what they added up to. We never use any of this to send you marketing, never share it with shops or anyone outside Sellexa, and never use it to make a decision about you.
- Why. Our legitimate interest in knowing which ways of reaching people work (Art. 6(1)(f)). You can object at any time: email support@sellexa.app and we will delete your answer and any mark.
- How long. While your account exists. Your answer and any mark are deleted when your account is deleted. See section 8.
3.13 Sellexa helpers on a shop's account (sellers)
A shop can let a member of the Sellexa team (a helper) into its seller account to set up its listings and shop page, instead of giving them its password. Nothing is open to a helper until the shop adds them in its Settings or says yes when a helper asks. The shop can remove a helper at any time. See the Seller Agreement, section 3.1.
- What a helper sees and changes. The shop's listings (with their photos, prices, portions and stock), its spreadsheet imports and the photos they bring in, its shop page (name, description, city, announcement, logo and banner), the times a rider can collect from it, and the shop's collection phone number, which a helper can see but not change. Helping does not open anything else of the shop's to them: not its money, payouts, bank or Stripe details, orders, buyers' details, terms or other settings.
- What we record. Every change a helper makes, and every change to who may help, with the date and the helper's name as it was then. For prices, names, stock, status and shop page details we keep the old and the new value. The shop sees the record in its Settings and on each listing, and the Sellexa team sees it on our admin pages.
- Why. To give the shop the help it asked for (Art. 6(1)(b)), and because the shop and Sellexa both need a true record of who changed what (our legitimate interest, Art. 6(1)(f)). Helpers are Sellexa staff working on our instructions, so Sellexa stays the controller and no one outside Sellexa takes part.
- How long. We delete each change in the record 2 years after it was made, and a helper's access 2 years after it ended (because the shop removed them or said no, the helper left, or the time ran out). A scheduled job in our database does this once a day, so it can take a day or two longer. Access that is still open, or still waiting for the shop's answer, is never deleted. If the shop's account is deleted first, the record is deleted with it. If a helper's own account is deleted, we remove the link to that account from the record, but their name stays on the changes they made, so the shop can still see who made them. See section 8.
4. Why we use it (lawful bases)
- Performance of contract (Art. 6(1)(b)), running your account, processing orders, sharing buyer name + delivery address + delivery phone number with the seller for fulfilment and with the courier that carries a posted parcel or the Sellexa rider who delivers a Sellexa delivery order, notifying sellers of new orders (including by WhatsApp), telling you a Collect order is ready (by WhatsApp only where you asked for it), holding an order a shop keyed for you at your request until you pay for it or the link runs out (section 3.11), processing refunds, providing payouts, and, if you ride for Sellexa, running your rider account, showing you runs and paying you for the deliveries you make, and, if your shop lets a Sellexa helper in, the help your shop asked for (section 3.13).
- Legal obligation (Art. 6(1)(c)), HMRC DAC7 reporting, Companies Act record retention, responding to lawful enforcement requests, Modern Slavery Act due diligence.
- Legitimate interests (Art. 6(1)(f)), fraud prevention, abuse and contact-info filtering in messages, security logging, debugging, basic site analytics, personalising the products we show you (using the
sx_vid browser code described in section 3.5), learning which ways of reaching people bring buyers to Sellexa (section 3.12), showing the street of a shop with premises (section 3.2), keeping a record of the changes a Sellexa helper makes on a shop and who made them (section 3.13), defending claims. We balance these against your privacy and you can object at any time by emailing support@sellexa.app; to stop the personalisation on this browser you can also simply clear the sx_vid cookie. - Consent (Art. 6(1)(a)): analytics and marketing cookies, and marketing emails, which we send only if you ticked the box at sign-up. Withdraw at any time: for cookies, use "Cookie settings" in the footer; for emails, use the unsubscribe link in any marketing email or email support@sellexa.app.
5. The buyer → seller → carrier data flow
When you place an order, the lawful basis is "performance of contract" (UK GDPR Art. 6(1)(b)). Who your delivery details reach depends on how the listing is shipped:
- Your name and delivery address are shared with the seller so they can fulfil your order. Simple orders: Sellexa books the shipping label, so we also send your name, delivery address and delivery phone number to Parcel2Go, which produces the label and passes those details on to the courier that carries your parcel. Sellexa delivery orders: a rider working for Sellexa collects the order from the seller and brings it to you. The rider making the delivery is shown your name, delivery address, delivery phone number and any safe-place note, and nothing else. From the day Sellexa delivery runs open to riders, they see it on their own rider account on Sellexa's systems, only while they hold the run that carries your order and not once it is delivered or, if nobody could be reached, back at the shop; until that day a member of the Sellexa team gives the rider those details and records the collection and the delivery. Nothing is sent to an outside delivery company. Seller-managed Custom orders: the seller arranges the label themselves and Sellexa does not transmit your data to any carrier.
- Your email address is never shared with the seller. It is passed to Parcel2Go on Simple orders, because Parcel2Go holds a contact email against the shipment and uses it to send you delivery notifications about that order. On Sellexa delivery orders your email stays with Sellexa: the rider does not see it, and our own emails tell you about the delivery. Your delivery phone number is shared with the seller (shown on their order page), on Simple orders with Parcel2Go and the courier, and on Sellexa delivery orders with the Sellexa rider making the delivery, because whoever delivers needs a contact number for the delivery. A Sellexa rider may call or message you on it to complete the drop-off. All of them may only use it in connection with delivering that order. A seller using it for anything else breaches the Seller Agreement and the Off-Platform Transactions Policy. All other buyer↔seller communication runs through in-app messaging on the order page.
- Some information about what is in the parcel travels with it. On every parcel Sellexa books, the titles of the items you ordered are sent to Parcel2Go as the contents description, because a carrier needs to know roughly what it is carrying, together with the declared value of the goods and the parcel's weight and dimensions. On a Sellexa delivery order from a shop that packs its own orders, the rider is not given a list of what you ordered: they see the order number, the code they show at the shop for everything they collect there, and whether there is a cold bag and a dry bag to carry, and they collect the packed order from the shop. At a shop Sellexa packs for, the rider packs your order from the shop's shelves, so while it is still at the shop they see the lines of your order (each item, its size, how many, its shelf price and its photo) to pick and bag them; those lines leave their screen the moment the shop releases the order to them. We never pass your payment details, your card, or your Sellexa account history to any of them.
- Sellexa retains the order record (including the address used at the time of purchase) for 7 years for tax and accounting purposes.
Once the seller receives the address for fulfilment, the seller becomes an independent controller of that data and must comply with their own UK GDPR obligations under the Seller Agreement §12. Parcel2Go and the courier that carries the parcel likewise act as separate controllers for the carriage of the order, deciding for themselves how they run their delivery and record-keeping. A Sellexa rider is different: riders act only on Sellexa's instructions, so Sellexa stays the controller of your data throughout a Sellexa delivery. See section 6.
6. Who processes your data on our behalf
- Stripe Payments UK Ltd / Stripe Inc., payment processing, KYC, payouts. UK Addendum to EU SCCs in place for transfers to the US.
- Supabase Inc., database, authentication, file storage, realtime. EU region (eu-west-2). UK adequacy + SCCs where applicable.
- Resend Inc. (US), transactional and newsletter email delivery. UK Addendum to EU SCCs.
- Netlify Inc. (US), application hosting and CDN. UK Addendum to EU SCCs.
- Meta Platforms Ireland Limited (WhatsApp Business Cloud API), delivery of seller order-notification messages. Message content is processed on Meta-hosted infrastructure and may be processed outside the UK. UK Addendum to EU SCCs.
- Google Ireland Limited (Google Analytics, Google Tag Manager and Google Ads measurement), site usage statistics and advert measurement. Receives your IP address, the page URL and device data. Data may be processed in the US under the UK Addendum to EU SCCs or a UK adequacy decision. Before you have made a cookie choice, and if you refuse analytics or marketing cookies, Google's tag still sends short cookieless pings (no cookie is read or set and no identifier is stored); with consent it sets the cookies listed in the Cookie Policy.
- Plausible Insights OU (Estonia), cookieless page-view analytics. Receives your IP address, the page URL and device data, and keeps no identifier that follows you between days. Processed in the EU, covered by the UK's adequacy regulations for the EEA.
Each processor is bound by a written data-processing agreement requiring confidentiality, appropriate security measures, and onward-transfer controls.
Parcel2Go.com Limited (company number 02591405, a courier-aggregation company registered in England) sits slightly differently. On Simple orders, and on Custom orders where the seller buys the label through us, Sellexa sends the buyer's name, delivery address, delivery phone number and email address to Parcel2Go so it can produce the shipping label, notify the buyer and provide tracking, together with the seller's collection address and business contact details, the titles of the items as the parcel's contents description, and its declared value, weight and dimensions. Parcel2Go passes what it needs to the courier that carries the parcel. Parcel2Go and the courier decide for themselves how they run delivery and keep records, so for the carriage of the parcel they act as separate controllers in their own right, not as processors acting only on Sellexa's instruction. Parcel2Go is UK-based, so this is a domestic transfer with no international-transfer mechanism needed. A written agreement covering data protection governs this sharing.
Sellexa's own riders carry Sellexa delivery orders. They are self-employed people Sellexa engages directly under a written agreement (the Rider Agreement), and they work on Sellexa's instructions, so for data protection they are part of Sellexa rather than a separate company: Sellexa stays the controller and no outside delivery company receives your details. A rider has their own rider account on Sellexa's systems; what we hold about riders is in section 3.9. From the day Sellexa delivery runs open to riders, a rider claims a run on that account and sees, for each stop on it, what the delivery needs and no more: your name, delivery address, delivery phone number and any safe-place note, the shop's name, phone number and collection address, the order number and the collection code they show at the shop, and whether there is a cold bag and a dry bag to carry. At a shop Sellexa packs for, the rider also sees the lines of your order while it is still at the shop (each item, its size, how many, its shelf price and its photo), because the rider packs it from the shelves; a member of the shop's staff then releases the packed order to the rider, and the lines leave the rider's screen. They see it only while they hold that run, and not once the order is delivered or, if nobody could be reached, back at the shop. Until that day, a member of the Sellexa team records the collection and the handover and hands the rider those same details and no more. Either way the rider is given nothing else: not your email address, your payment details, your card, or your Sellexa account history. Your delivery PIN is never shown to the rider; they type the PIN that is read out to them and our system checks it. Riders are bound in writing to use those details only to make that delivery.
One step happens before you order. To work out the delivery fee, which depends on how far your address is from the shop, we need the position of your postcode and the shop's. The shop's business postcode is looked up when the shop saves its address, so that delivery can be priced by distance if the shop offers Sellexa delivery; nothing about you is sent in that lookup. Your postcode is looked up only when we price Sellexa delivery for you, at a quote and again when you pay, and only for a shop that offers it. In each case we send the postcode only, with nothing else about you, to postcodes.io, a free UK postcode lookup service, and keep the position it returns against the postcode so we do not have to ask twice. No name, address line, phone number or email is sent, and nothing about you can be worked out from a postcode on its own.
7. Other sharing
- Other users: public profile fields (display name, profile picture, shop content, and for a shop with premises, the street it is on (section 3.2)) are visible on the platform.
- Anyone you give a shared cart link to: whoever holds the link, signed in or not, sees the items on it, the stores they come from and those stores' prices on the day they open it. They see your first name only if you switched that on, and nothing else about you. Whoever you send a link to can pass it on, so share it as you would anything else you forward. See section 3.7.
- Anyone holding a pay link a shop sent you: they see the order the shop keyed, your name as the shop typed it, the last three digits of your mobile number, and for delivery your town and postcode, until the link runs out; the full number and the rest of the address appear only after you sign in with the code. The shop sends the link to you itself; whoever you forward it to sees the same. See section 3.11.
- HMRC: seller information is reported annually under DAC7.
- Law enforcement and regulators: only where we are legally required (court order, properly served notice).
- Corporate transactions: in the event of a merger or sale, data may transfer to the acquirer subject to this policy.
We do not sell, rent, or trade your personal data for marketing.
8. How long we keep it
- Active accounts: until you ask us to delete or until 24 months of inactivity.
- Order records and ledger entries: 7 years from the order date (HMRC + Companies Act 2006).
- Messages (including original body for moderation): 24 months.
- Notifications outbox: 12 months for delivery diagnostics.
- KYC records: 5 years after account closure (anti-money-laundering retention norm).
- Server logs: 12 months.
- Browsing and click records: 12 months, then deleted. A scheduled job in our database removes them automatically. Google Analytics keeps the event data it collects for the period set in our Google Analytics account; we do not extend that beyond 14 months.
- Search terms: 90 days, then deleted. A scheduled job in our database removes them automatically.
- Request counts for abuse prevention: 1 day, then deleted by a scheduled job in our database. To stop automated misuse we count how often parts of the site are called, relying on our legitimate interests in keeping the site secure: for visitors the count is kept against a one-way scrambled form of the IP address, never the address itself, and is not linked to an account; for a few signed-in actions, such as trying a discount code or making a shared cart link, it is kept against the account.
- Shared cart links: a link stops working 30 days after it is made, or as soon as you turn it off. 7 days after that, a scheduled job in our database deletes our record of the link and the items on it. The job runs once a day, so it can take up to a day longer. We keep the record for those 7 days only so that the link can say it has expired instead of looking broken. If you delete your account, every link you made while signed in is deleted with it. See section 3.7.
- Delivery proof photos, and the first name of whoever took the order (orders Sellexa delivers itself, section 3.8): 120 days after delivery, which covers the time in which a card payment can be disputed, then deleted automatically by a scheduled job. The rest of the delivery record stays with the order for the 7 years above.
- Rider records (section 3.9): while your account exists, deleted with it. Rider pay records: 7 years from the payment, with your name and a reference to your Stripe account as they were when you were paid. Rider insurance documents: deleted by hand when your rider account is closed, or sooner when you ask.
- WhatsApp number for a Collect order (section 3.10): with the order record, for the 7 years above, and used only for messages about that order.
- Orders a shop keyed for you (section 3.11): the pay link works for a day after the shop sends it. A keyed order that is never paid, or that the shop cancels, is deleted by a scheduled job in our database 7 days after the link ran out or was cancelled; the job runs once a day, so it can take up to a day longer. A keyed order you paid for stays with the order record, for the 7 years above.
- How you found Sellexa, and whether our founder already knew you (section 3.12): while your account exists, then deleted with it, or sooner if you object.
- Record of a Sellexa helper's changes, and helper access that has ended (section 3.13): 2 years after the change was made or the access ended, then deleted by a scheduled job in our database; the job runs once a day, so it can take a day or two longer. Access that is still open or waiting for the shop's answer is kept. If the shop's account is deleted first, the record is deleted with it. If a helper's account is deleted first, the link to it is removed and their name stays on the record.
- Marketing preferences and any consent we have collected: until you withdraw consent.
9. Security
We use TLS encryption in transit, encryption at rest for our database, role-based access control (Supabase RLS), least-privilege service accounts, and audit logging. We test for common web vulnerabilities. No system is completely secure, please use a strong unique password and report any suspicious activity to support@sellexa.app.
We will notify the ICO of any qualifying personal-data breach within 72 hours and will notify affected users where the breach is likely to result in a high risk to their rights and freedoms.
10. Your rights
Under the UK GDPR you can:
- Access a copy of the personal data we hold about you.
- Rectify inaccurate or incomplete data.
- Erase personal data where the lawful basis no longer applies (subject to legal retention obligations).
- Restrict our processing while a query is resolved.
- Port data you provided in a structured, machine-readable format.
- Object to processing based on legitimate interests, including any direct marketing.
- Withdraw consent for any consent-based processing at any time. For analytics and marketing cookies, choose "Cookie settings" in the footer of any page; it takes effect straight away.
- Not be subject to a decision based solely on automated processing that significantly affects you (we do not currently make such decisions).
Email support@sellexa.app to exercise any right. We respond within one calendar month and may ask for ID verification.
11. Complaining to the ICO
If you are unhappy with how we handle your personal data, please raise it with us first via the Complaints Policy. You also have the right to complain to the Information Commissioner's Office (the UK supervisory authority):
Information Commissioner's Office
Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF
Helpline: 0303 123 1113
Website: ico.org.uk/make-a-complaint
12. Cookies
We set essential cookies to sign you in and take payment, one functional cookie (sx_vid) that remembers this browser for product suggestions, and analytics and marketing cookies only with your consent (including, if you allowed analytics, a small Sellexa cookie called sellexa_signup_tracked that stops one sign-up being counted twice). Change your choice at any time with "Cookie settings" in the footer. Full detail, cookie by cookie, in the Cookie Policy.
13. Children
Sellexa is for adults. You must be at least 18 to use the platform, whether you are buying or selling. The service is not aimed at anyone under 18, and we do not knowingly collect personal data from anyone under that age. If you believe someone under 18 has registered, contact us and we will close the account and delete the data.
14. Changes to this policy
We will update this policy when our processing changes. Material changes will be notified in-app and by email at least 14 days before they take effect.
Sellexa Limited
Company No. NI735255 (Northern Ireland)
West Circular Close, 187 West Circular Road, Belfast, Northern Ireland, BT13 3QF
Email: support@sellexa.app
This document is in force and applies today. We write and maintain it ourselves, no outside solicitor has reviewed it, and nothing here is legal advice.