Privacy policy

Last updated 16 October 2026

Who is responsible for your data

Reece McAllion, trading as Rewear, is the data controller for personal data collected through the Rewear app and website. Contact address: 68 Bolton Road, PR6 9NA.

Questions about your data go to support@rewearuk.com.

This policy explains, in plain terms, what we collect, why, who sees it, and what you can do about it.

What we collect

Only what the service needs to work. Specifically:

• Account: your email address, username and a hashed version of your password. We cannot see the password itself.
• Profile, if you fill it in: a photo, a short bio, your town and country, and whether you want activity emails. And, where your app offers them, a banner photo, a status line with the day it ends, up to five style vibes, up to ten favourite brands, the sizes you wear and up to three of your pieces pinned to the top of your profile. All of it is optional, and you can change or remove any of it at any time under Account → Edit profile.
• Business seller, if you sell as a business and switch the label on: that you do, the name you trade under and an address buyers can write to. None of it is collected unless you switch it on yourself or ask us to.
• Body measurements, optionally: if you save them, we use them to tell you how a piece will fit, and to favour pieces that should fit you under Picked for you. You can clear them at any time.
• Listings: photographs, descriptions, brand, size, condition, measurements, declared flaws and price.
• If you set up payouts: your legal first and last name, date of birth, home address, bank sort code and account number, the IP address you accepted Stripe’s terms from and, if Stripe asks for one, a photo of your identity document. These go to Stripe, which has to verify who you are before it can pay you. We do not keep your bank details or the photo, which passes straight through to Stripe and is never saved on our systems. We do keep a one-way fingerprint of your name and date of birth — a value the originals cannot be recovered from — so that one person cannot quietly run several selling accounts.
• Messages and offers you exchange with other members, including the automatic messages the app posts into a conversation when an order changes, and the photos you send in a conversation.
• Orders: what was bought, from whom, the price, fees, delivery service, tracking number, the parcel’s progress as the carrier reports it (each stage, when it happened, the carrier’s own notes about it and, for a locker or pickup shop, which one), and the last four digits of the card used.
• Delivery addresses you save, and the address a buyer gives for an order, with a UK mobile number if you add one. The number is optional: InPost needs it to deliver, so without one InPost is not offered.
• Reviews, favourites, follows, saved searches, blocks and reports.
• When you were last active on Rewear: the time of your latest visit while signed in to the app or the website, updated at most every couple of minutes while you are using it. Other members are only ever shown a rough label made from it — see Who sees it.
• Searches you make and listings you open while signed in — see Recommendations below.
• Where you heard about Rewear, if you answer that question when you sign up, and the short link you arrived by if you came through one (an address starting www.rewearuk.com/go/). Both are optional. If you reached the shop from one of our own pages, such as www.rewearuk.com/welcome, we note which one.
• If you join through a member’s invite link (an address starting www.rewearuk.com/invite/) or with their invite code, or add their invite code within 7 days of joining, we record whose link or code it was, how you used it and when. If that member’s invites can be rewarded when you join or add their code, they see your username and how far you are towards the reward: whether you have confirmed your email, set up payouts and had a listing up, and when the reward was given. Otherwise they are shown only a count of the people who joined through their link or with their code and how many of them have listed something, never who they are. We also keep a record of the invite rewards given to you and what you used them on, and of when you pressed “Not now” on an invite card on Home, so that it stays away on every device you use. If you set up payouts, we keep Stripe’s reference for the bank account you are paid into (a value your account number cannot be recovered from), to tell whether two accounts are paid into the same one. When an invite is rewarded, we keep a one-way marker of each of the two members’ email address, name and date of birth as Stripe checked them, bank account and phone (from the device checks described below), made with a secret key so that nothing can be read back from it, so that somebody who closes their account and joins again is not rewarded again.
• How often our pages are visited and each listing is opened. Nothing is stored on your device for this, and your IP address is not kept: a visit is counted against a code made from your connection and browser, or from your account if you are signed in, mixed with a random key that is held only in our server’s memory, is never written down and is replaced every day. Once the day is over the key is gone, so the code cannot be traced back to you, by us or anyone else, or connected with your visits on other days. Your own opens of your own listings are never counted.
• Free Bumps we give you in a promotion: how many, which promotion they were for, when they were given and when they expire, our note of how you claimed them (which can include the Instagram username you messaged us from), and which of your listings you used them on.
• Emails we have sent you, which we keep as a record of what you were told.
• Whether you want emails with Rewear news and offers: your answer, the basis on which we may send them, when and where you gave or changed it (when you signed up, in Settings, on the card in the app, or from an unsubscribe link) and the words you were shown, with a short history of each change.
• If you use the app and allow notifications: your phone’s push token, and whether it is an iPhone or an Android phone, so that notifications reach it.
• When you sign in with your password: the type of device and the browser or app you used (such as “iPhone app” or “Desktop · Chrome”), in the apps a one-way code for your phone from the device checks described below, and when each was first and last used to sign in to your account, so that we can email you if your account is signed in to from a device it has not used before. We do not keep your IP address for this.
• Technical details sent by your phone or browser with every request — an IP address and the app or browser version — which appear in our server logs.
• When a request from your phone or browser fails on our side, is given up before we have answered it (an upload your phone stops sending, for example) or takes 20 seconds or more, while you are signed in: what kind of action it was (such as a photo upload or checkout), when, how long it took, how much had been sent, and the type of device and the browser or app it came from (such as “Android · Instagram’s browser” or “iPhone app 1.0.5”). We also keep which type of device and browser or app you used last, and when. We do not keep your IP address or what you were sending for this.
• Device checks, when you sign up or sign in: a one-way code made from your internet address and its network, and in the apps from your phone’s app identifier, with the kind of device and app version. See Device checks to stop duplicate accounts and reward abuse below.

We do not collect your location beyond the town you choose to show, we do not read your contacts or photos other than the ones you pick to upload, and we do not use advertising trackers. Your phone may store where and when a photo was taken, and on what camera, inside the photo itself: we remove that from every photo you upload before anybody else can see it.

Why we use it, and on what basis

UK data protection law requires a lawful basis for each use. Ours are:

• To run the marketplace — accounts, listings, messages, orders, delivery, refunds, emails about your orders, including following each parcel with the carrier to know when it has been posted and delivered. Basis: performing our contract with you.
• To run promotions you enter, such as checking a claim for free Bumps, making sure each person claims once, and giving and recording the Bumps. Basis: performing our contract with you, which is the promotion’s terms.
• To keep the platform safe — investigating reports, spotting fraud, enforcing the terms, keeping logs that let us diagnose problems. Basis: our legitimate interest in running a trustworthy service, balanced against your rights.
• To hold a listing for a person at Rewear to look at before it goes live, or take it down while they do, when what it says, its price or how many of the same design its seller has listed in a day suggest it may not be made by the brand or club it names. This is done automatically from the listing, the seller’s other listings of that day and whether they sell as a business, and a person decides what happens to the listing. A receipt you send us for this check is used only to decide about that listing; you can cover your address and card details before you send it. Basis: our legitimate interest in keeping counterfeits off Rewear, balanced against your rights.
• To keep your account safe: to email you when your account is signed in to from a device it has not used before, and to pause signing in to an account for a few minutes after many wrong passwords. Basis: our legitimate interest, and yours, in stopping somebody else getting into your account.
• To tell you about activity on your account — a new offer, a message, a follower listing something — by email and, if you allow them, by notifications on your phone. Basis: our legitimate interest in the service being useful. You can switch these emails off under Account → Settings → Edit profile, and notifications off in your phone’s settings; emails about orders you are part of continue because you need them.
• To email you Rewear news and offers — new features, events, offers and requests to try something new on Rewear — only if you opt in, or if you joined on or after 14 October 2026 and did not tick “No thanks, don’t email me news” when you signed up. If you joined that way, the basis is our legitimate interest in telling our members about Rewear’s own similar services, which the law allows without asking first because we offered you the choice to say no when you signed up and offer it again in every one of these emails (the “soft opt-in” in regulation 22(3) of the Privacy and Electronic Communications Regulations 2003). Otherwise the basis is your consent, given when you say yes in the app or on the website. You can withdraw at any time and it takes effect at once: use the unsubscribe link in any of these emails, which works without signing in, or switch off Email me Rewear news and offers under Account → Settings. These emails are sent through Resend, like the rest of our email, and we never give your address to anyone else for their marketing.
• To compare a piece against your saved measurements, and to favour pieces that should fit you under Picked for you. Basis: your consent, given when you choose to save them, and withdrawn by clearing them.
• To show the Business seller label and your trading name on your listings and profile, and your address on your profile, once you have told us you sell as a business. Basis: performing our contract with you, and your own legal obligation as a trader, under the Consumer Contracts Regulations 2013, to tell buyers who you are and give them an address.
• To keep records of sales. Basis: our legal obligation to keep accounting records.
• To pay sellers, and to let Stripe check who they are. Basis: performing our contract with you, and Stripe’s own legal obligations under the Money Laundering Regulations 2017.
• To stop one person running several selling accounts, using the name-and-date-of-birth fingerprint described above. Basis: our legitimate interest in preventing fraud and ban evasion, balanced against your rights.
• To stop one person opening several accounts, and invite rewards being collected with a second account, using the device checks described below. Basis: our legitimate interest in preventing fraud and abuse, balanced against your rights.
• To learn which places bring people to Rewear, and whether buyers find sellers they did not come for, from your answer to "How did you hear about Rewear?" and the short link you arrived by. Basis: our legitimate interest in knowing where to spend our effort. Nobody but us sees your answer, and you can skip the question.
• To count visits and listing views as described above, so sellers can see how often their pieces are opened and we can see which pages people use. Basis: our legitimate interest in running a useful service. Nothing that can be traced back to you is kept for it once the day is over.
• To find and fix problems with Rewear, and to help you when something is not working for you, from the record of failed, abandoned and very slow requests described under What we collect. Only the people who run Rewear see it. Basis: our legitimate interest in a service that works, balanced against your rights.
• To show other members roughly when you were last active, so that they can tell whether you are likely to reply soon, and to help us with support and with keeping the platform safe. Basis: our legitimate interest in a marketplace where members can tell who is around, balanced against your rights: other members see only a rough label, never the time, and you can turn it off.

We do not make automated decisions about you that have legal or similarly significant effects. A photograph can be refused automatically by the check described below. If it is refused as you upload it, that upload does not go through, and nothing else changes. If it is refused after it went live, it is taken off Rewear: a listing that showed it is hidden until the photo is replaced, a profile photo or banner is removed, and a photo sent in a message is taken out of the conversation. If you think a photo was refused wrongly, email support@rewearuk.com within 30 days of the refusal and a person will look at it, with one exception. Nobody, not even us, looks at a photo the check refused with the words "this photo is sexual rather than a picture of an item for sale", "this photo shows nudity" or "we could not accept this photo", or at one it refused with a child in it, which we do not keep at all. If you think one of those was refused by mistake, tell us all the same: we will look at the record of the refusal, which says what the check decided, but not at the photo itself, and you can upload a different photo. We look at that record too for any other refused photo we no longer have.

Recommendations

While you are signed in, we note what you search for (the words and filters) and which listings you open, once a day per listing. With the pieces you save and buy and the sellers you follow, we use this to pick pieces for you under Picked for you, and each pick says why. We do not note maternity wear, or a search or listing whose words speak of a pregnancy, your health or your religion, and Picked for you never offers those pieces. Beauty and grooming searches can touch on health — acne, eczema, hair loss or the menopause, for example — and a search or listing that does is treated the same way. We keep your last 200 searches and 500 listings opened, for up to 180 days. Other members and sellers never see them, and our dashboard only shows the most common searches of the week, and only ones made by at least three members. Basis: our legitimate interest in showing you pieces you are likely to want. It is on unless you switch off Personalised recommendations under Account → Settings → Recommendations, which also deletes this history; you can clear it there at any time.

If you have saved your measurements, Picked for you also favours pieces that should fit you. That rests on the consent you gave when you saved them, not on our legitimate interest: clearing your measurements stops it, and so does switching off personalised recommendations.

If you have chosen style vibes, favourite brands or the sizes you wear on your profile, Picked for you uses them as a light hint too, never ahead of what you actually search for, open, save and buy, and never as the reason given for a pick. Only while personalised recommendations is switched on: switching it off stops it, and so does removing them from your profile. The sizes you wear are also what "In my size" uses, when you choose it in search, and are never shown to anyone else.

Device checks to stop duplicate accounts and reward abuse

One person, one account: that is what keeps reviews, sales and invite rewards honest. To spot somebody opening several accounts under different email addresses, we run two checks when you sign up and when you sign in:

• In the iPhone and Android apps, your phone’s app identifier: on iPhone the “identifier for vendor” that Apple gives our apps, on Android the Android ID, which is specific to our app on your phone. It is not your phone’s advertising identifier, and it cannot be used to follow you across other companies’ apps or websites. The website does not read or store anything like it: no fingerprinting and no cookies.
• The internet address (IP address) your request came from, and the network it belongs to, on the website and in the apps.

We never keep either as it is. Each is turned into a one-way code with a secret key, so it cannot be read back or matched against anything outside Rewear. With the code for a phone we keep the kind of device and app version (for example “iPhone app 1.0.5”) and when it was first and last used.

What we do with them. If a new account is opened in the app on a phone that already has an open Rewear account, we may refuse it and ask you to sign in to that account instead, or to email support@rewearuk.com if the phone was passed on to you. An internet address is shared by households, offices, universities and mobile networks, so on its own it never refuses an account: we use it only to limit how many new accounts one address can open in a day, to hold back an invite reward between two accounts used on the same address until we have checked it, and to point a person on our team at accounts worth a look. Invites between two accounts used on the same phone are never rewarded.

Why, and on what basis: to prevent fraud and abuse of Rewear and of invite rewards, which is our legitimate interest (UK GDPR Article 6(1)(f)), balanced against your rights. The checks use as little as they can, are kept only as one-way codes, are never used for advertising or to track you across other apps or websites, and are never shared with anyone else. Reading the app identifier is done only because it is strictly necessary to protect accounts and rewards on the service you asked us for. You can object by emailing support@rewearuk.com; we will look at it, although we may need to go on checking to stop fraud.

How long: the code for your phone while your account is open, deleted when you close it. The codes for internet addresses, 90 days after each was last used, and when you close your account. Where an invite of yours was rewarded, a one-way marker of each member’s phone is kept for two years after the reward, like the other invite markers, so that closing an account and joining again does not earn the reward again.

Who sees it

Other members. Your username, profile photo, bio, town, listings, reviews and ratings are visible to everyone using Rewear. When you buy something the seller sees the name and address to post it to; when you sell something the buyer sees your username and town. Messages, and the photos you send in them, are visible only to the two of you, and to us if either of you reports the conversation or a photo in it.

Unless you turn it off, other members who are signed in see roughly when you were last active, on your profile, on the page of each of your listings and at the top of a conversation with you: “Online now”, “Active in the last hour”, “Active today”, “Active yesterday”, “Active in the last week” or “Active in the last month”, and nothing once it has been longer than a month. They never see the time itself. Members you have blocked, and members who have blocked you, never see it. Turn it off under Account → Settings → Show when I’m online and no other member sees it, from then on. The people who run Rewear can see the time you were last active, to help with support and to keep the platform safe.

Your profile also shows everyone what you add to it: your banner photo, status line, style vibes, favourite brands and pinned pieces. And badges worked out afresh from your own listings and orders each time your profile is opened, never stored and only ever shown while they are true: "Measures everything" (every piece on sale that takes measurements has them, on at least three), "Posts within a day" (over your most recent posted orders, up to twenty and never fewer than ten, the middle time from payment to posting is under a day, and no order has been waiting more than a day to be posted) and how many of your pieces have sold and arrived. If you were one of the first 50 people to sell on Rewear, it also shows a Founding seller number, which is given once and kept, even after an account is closed, so that it is never given to anybody else. The sizes you wear are never shown on your profile.

If you switch on the Business seller label, everyone using Rewear can see it while it is on: your trading name on your listings and your profile, and the address you give on your profile. Switch it off and neither is shown, but we keep them so you need not type them again, until you close your account or ask us to delete them.

Service providers, each only for its job. These are all of them:

• Hosting: Railway runs our servers and stores the database, the photographs you upload and our server logs, in its Amsterdam region in the Netherlands. It holds everything we hold, but only to store it and run the service for us.
• Backups: Cloudflare keeps our backups — a copy of the database taken each day and a copy of each photograph you upload — in a private storage bucket in the European Union, so that Rewear can be put back if our servers fail. It holds what our database and photographs hold, but only to store it for us.
• Email: Resend sends our transactional email. It receives your email address and the content of the message.
• Postage: Sendcloud buys the label and gives us tracking. It receives the sender’s and recipient’s names and addresses, the recipient’s mobile number if one was given, and the parcel details, and passes them to the carrier you chose. If you sell with InPost, we give InPost your email address with the parcel, so they can email you the QR code to drop it off without a printer. For other carriers we use our own contact details. Sendcloud also tells us how each parcel is getting on, from the carrier’s scans. We can show that to the buyer and the seller of the order, and the carrier’s own notes about a delivery, such as a neighbour’s name or where it was left, only to the buyer. If you buy, we also give the carrier your email address with the parcel, if you have confirmed it, so the carrier can email you about the delivery, such as the code to collect it from an InPost locker.
• Postcode lookups: postcodes.io turns a postcode into a point on the map, so we can find the pickup points nearest to it. It receives only the postcode — never a name, a street or an order.
• Payments and payouts: Stripe processes card payments and pays sellers. Your card details go straight to Stripe; we never receive the full number. For sellers, Stripe also verifies identity, using the details and any photo of an identity document described above, and holds the bank details, and for that part it decides for itself what the law requires of it rather than simply acting on our instructions.
• Notifications and app updates: Expo sends our notifications to your phone and delivers updates to the apps. If you allow notifications, it receives your phone’s push token and each notification’s title and text — for a new message, that is who sent it and its first 140 characters, and for a photo, the words "Sent a photo", never the photo itself. It also receives the random IDs the app makes when it is installed, each time the app checks for an update and when it sets up notifications.
• Notifications on Android: Expo hands each notification to Google’s Firebase Cloud Messaging, which delivers it to the phone. It receives the push token and the notification, and your phone registers with it under an installation ID of its own.
• Notifications on iPhone: Expo hands each notification to the Apple Push Notification service, which delivers it to the phone. It receives the push token and the notification.
• Maps on iPhone: when you choose a pickup point in the iPhone app, Apple Maps draws the map above the list. Apple receives the area the map shows, around the postcode you searched, so that it can send the map for it — not your name, your address or your order. The website and the Android app show the list without a map.
• Fonts on some of our web pages: a few pages on www.rewearuk.com, such as Selling on Rewear, Fees compared and the page on deleting an account, load their typefaces from Google Fonts. Your browser fetches them from Google, which receives your IP address and browser details. The shop, your account and this policy use fonts we serve ourselves, and the apps have theirs built in.
• Automated checks and assistance: we use Anthropic as a processor. Every photograph uploaded — listing pictures, profile photos, banners and photos sent in messages alike — is checked automatically before it appears, to keep material off the site that should not be on it, and a photo sent in a message is also checked for phone numbers, email addresses, usernames on other apps and bank or payment details. When you publish a new listing that looks like one you already have on sale, one of its photographs is compared with a photograph and the title of each listing it resembles, so that we can warn you before one piece is listed twice. When another member searches with a photo, the first photograph of up to six listings that might match it is sent with their photo, so that the same item can be told from similar ones. Beyond that, the following are sent only when you choose to use the feature that needs them: the listing photographs, for the wear check and for the draft-from-photos and suggested-price tools, together with the listing details you have already entered; the sentence you type when you search by description; and the question you ask on the Ask about the rules screen. Anthropic processes this on our behalf, under contract, and does not use it to train their models.
• Photo search: a photo you search with is sent to Anthropic to describe the item in it and to compare it with the first photo of up to six listings that might match. It is used only to find similar listings, and is not kept by us.
• Nothing you write to another member is sent to Anthropic. A photo you send in a message is checked as described above, on its own, and nothing else from the conversation goes with it. Apart from the start of a new message, which its notification carries to the other member’s phone, messages and offers stay between the two of you, and are read by us only if one of you reports the conversation.

We do not sell personal data, and we do not share it with advertisers. We will disclose data where the law requires it — a court order, or a lawful request from the police or a regulator.

Some of that processing happens outside the United Kingdom. Specifically:

• Railway — the Netherlands, which UK law treats as providing adequate protection. Railway is an American company, and anything it handles from the United States is covered by the UK Addendum in its data processing agreement.
• Cloudflare — the European Union, which UK law treats as providing adequate protection. Cloudflare is an American company, and anything it handles from the United States is covered by the UK Addendum in its data processing agreement.
• Anthropic — United States, under the UK Addendum to the EU Standard Contractual Clauses.
• Stripe — United States and Ireland, under the UK Addendum.
• Resend — United States, under the UK Addendum.
• Sendcloud — Netherlands, which UK law treats as providing adequate protection, so no additional safeguard is needed.
• Expo — United States, under the UK Extension to the EU–US Data Privacy Framework.
• Google, for notifications on Android — United States, under the Data Privacy Framework and the Standard Contractual Clauses in Google’s data processing terms for Firebase.
• Apple, for notifications and maps on iPhone — United States, under the Standard Contractual Clauses.
• Google, for fonts on some of our web pages — United States, under the UK Extension to the EU–US Data Privacy Framework.

Email support@rewearuk.com if you would like a copy of the transfer agreement we rely on for any of these.

How long we keep it

• Your account, profile, listings and saved data: for as long as your account is open.
• Pieces you did not sell: taken down, and their photographs deleted, when your account is closed. What you wrote about them — the description, measurements and declared flaws — goes within 30 days. A title stays only where a conversation, an offer or a report refers to the piece.
• Messages and reviews: after your account is closed they stay for the other member, because they are that member’s record too, and show as coming from a deleted account.
• Photos you send in messages: kept with the conversation while your account is open, and deleted when you close it. The message stays for the other member and shows that a photo was removed. A photo we take out of a conversation because it was reported is deleted then. One we take out because our check refused it is kept as any photo the check refuses is: up to 30 days, where no other member can see it, or not at all if it has a child in it.
• Order and payment records: 6 years after the order, because UK tax and accounting rules require it, even if the account has been closed. After closure we keep only what those records need.
• Parcel progress: the stages and when they happened are kept with the order. The carrier’s own notes about a delivery are deleted 90 days after the order is completed or cancelled, or sooner if the buyer or the seller closes their account.
• Reports and records of enforcement action: up to 2 years after the account is closed, so a repeat offender cannot simply start again. That goes for reports you made as well as reports about you.
• Photos our automatic check refuses: up to 30 days after the refusal, where no other member can see them, and then deleted. A photo refused with a child in it is not kept at all.
• Search and browsing history: up to 180 days, or less if you clear it, switch off personalised recommendations or close your account.
• Where you heard about Rewear: while your account is open. It is cleared when you close it.
• Whose invite link or invite code you joined with, if you did, and how and when you used it, your invite rewards, Stripe’s reference for your bank account and any invite card you put away: while your account is open. They are cleared when you close it, and so are your own invite link and code. Where an invite was rewarded, a record that the other member had a reward for it stays, without your account on it, because it counts towards their limit, and the one-way markers of who each of you was stay for two years after the reward was given, even once you have closed your account, so that closing an account and joining again does not earn the reward again or start the limit again.
• The daily codes behind visit and listing-view counts: up to 180 days. After the day they were made on, they cannot be traced back to anybody.
• The devices you have signed in from, and their types: while your account is open. They are deleted when you close your account, and they are in the copy of your data you get from Account → Settings → Download my data. A count of recent wrong passwords for your account is held for 15 minutes and never written down.
• Push tokens: until you sign out on that phone, change or reset your password, or close your account.
• Your answer about news and offers emails: we act on it until you withdraw it or close your account. After you withdraw, we keep the record of your answers, so that we can show what you agreed to and do not email you news and offers again. It is deleted when you close your account, and it is in the copy of your data you get from Account → Settings → Download my data.
• Device checks: the code for your phone while your account is open; the codes for internet addresses 90 days after each was last used. Both go when you close your account, apart from the marker of a phone on a rewarded invite, which is kept for two years after the reward.
• Failed, abandoned and very slow requests: 30 days. The type of device and browser or app you used last, and when: while your account is open. Both are deleted when you close your account, and both are in the copy of your data you get from Account → Settings → Download my data.
• Server logs: kept by our hosting provider, Railway, under their retention policy rather than ours — we do not set a figure we cannot enforce. They hold IP addresses and request paths, not the contents of your account.
• Backups: each copy of the database is deleted after 30 days, and the copy of a photograph 30 days after the photograph is deleted from Rewear, so anything deleted can stay in a backup for up to 35 days. Backups are used only to put Rewear back after a failure.
• Free Bumps given to you in a promotion, with our note of how you claimed them and what you used them on: while your account is open. When you close it, a record that the promotion gave free Bumps stays, without your account, the note or your listings on it, so that its count of how many it gave stays right.
• When you were last active: only the latest time is kept, and each visit replaces the one before. It is cleared when you close your account.
• Everything else: deleted or anonymised within 30 days of your account being closed.

Your rights

You can ask us to:

• tell you what personal data we hold about you and give you a copy (access and portability)
• correct anything that is wrong — most of your profile you can edit yourself in the app
• delete your account and your data (erasure), subject to the records we must keep — you can also do this yourself, as below
• stop using your data for a particular purpose, or restrict what we do with it
• stop sending you activity emails — the switch is under Account → Settings → Edit profile
• stop sending you news and offers — use the unsubscribe link in any of those emails, or the switch under Account → Settings
• object to personalised recommendations, or clear the history behind them — both under Account → Settings → Recommendations

Email support@rewearuk.com from the address on your account and we will respond within one month. There is no charge.

You do not need to write to us to delete your account. In the app or on the website, go to Account → Settings → Delete account and confirm with your password. If you never confirmed your email address, Delete this account is at the bottom of the Confirm your email screen instead. www.rewearuk.com/delete-account sets out how, and what is deleted and what is kept, and works without the app or an account. If you cannot sign in, email support@rewearuk.com from the address on your account and we will delete it for you.

If you are unhappy with how we have handled your data you can complain to the Information Commissioner’s Office at ico.org.uk. We would rather you told us first so we can put it right.

Cookies and local storage

No tracking cookies, no advertising cookies and no analytics cookies. We count visits without storing anything on your device (see What we collect), and there is nothing here to consent to — everything below is needed to provide the service you asked for, which is why you are told about it rather than asked to agree to it.

The same code builds the website and the apps, so both store the same ten things. In a browser they sit in local storage; in the apps, in the app’s private storage, and the sign-in token goes into the device keychain instead. Of these ten, only the sign-in token leaves your device: you send it back to us to prove who you are.

• rewear.token — your sign-in token, so you are not asked to sign in every time. Removed when you sign out.
• rewear.lastUser — a copy of your own profile, so the app opens signed in when the network is slow. Removed when you sign out.
• rewear.appearance — light or dark.
• rewear.glass — whether the frosted-glass effect is on.
• rewear.onboarded — whether you have seen the three introduction slides, so you are not shown them again.
• rewear.recentSearches — your last few searches, shown under the search box. Clear them from that screen, or with Clear my browsing and search history.
• rewear.payoutNoteDismissed — whether you have dismissed the note about setting up payouts, so it stops nagging.
• rewear.addressReminder — which account pressed Later on the card asking for the address you post from, and when, so it waits a week before asking again on this device.
• rewear.sellNudge — which account pressed Not now on the “Got pieces you don’t wear?” card, and when, so it waits two weeks before showing again on this device.
• rewear.homeFeed — which account last chose For you, New in or another pill at the top of Home, and on which day, so Home opens there again for the rest of that day.

The apps also keep two things of their own that do leave your phone, both described under Who sees it: the random IDs made when the app is installed, which go to Expo, and, if you allow notifications, your phone’s push token, which goes to us and to Expo so that a notification can reach it. The website keeps neither.

The apps also read your phone’s app identifier when you sign up or sign in, for the device checks described above. It is sent to us only with that request, and we keep only a one-way code made from it. The website reads nothing of the kind.

On the website’s checkout page only, Stripe’s payment form (Stripe.js, loaded from js.stripe.com) sets two cookies of Stripe’s own, __stripe_mid (kept for a year) and __stripe_sid (kept for 30 minutes), and collects details of your browser and device, so that Stripe can detect and prevent fraud. Stripe uses them under its own privacy policy. They are strictly necessary to take your payment safely, so they are not asked for. While a payment is going through, the website also keeps rewear.pendingPayment in your browser tab’s session storage: the payment’s reference and the basket, delivery and address it is for, so that your order can still be placed if the page reloads or your bank sends you to its own page to approve the payment. It is removed once your order is placed, and goes when you close the tab. The apps keep neither.

Clearing site data in your browser, or deleting the app, removes all of it.

Children

Rewear is for adults. We do not knowingly collect data from anyone under 18. If you believe a child has created an account, tell us and we will remove it.

Security

Passwords are stored as salted hashes, never as plain text. Sign-in tokens are signed and expire. Access to the production database is limited to the people who run the service.

No system is perfectly secure. If we discover a breach that puts your data at risk we will tell you, and the ICO, as the law requires.

Changes to this policy

We will update this policy when the way we handle data changes — for example if we add a provider. The date at the top is the date of the last change. For anything significant we will email you.

Contact

Reece McAllion, 68 Bolton Road, PR6 9NA. Email: support@rewearuk.com.