On this page
Who is responsible for your information
RE is operated by ORYON LTD, company number 17248384, United Kingdom. We are responsible for deciding how personal information is used to provide RE. Our correspondence address is Eagle Point, City Road, London, EC1V 1AR, United Kingdom.
Contact privacy@reapps.uk about your information, support@reapps.uk for help, and legal@reapps.uk for legal matters. We aim to provide an initial response within 48 hours. This is not a promise to resolve every request within that time or a replacement for applicable legal deadlines. RE is not an emergency service.
RE is a marketplace and community service for people aged 16 or over at supported universities in the UK and US, including alumni who can still verify with their university email. We do not process payments, hold deposits or provide escrow for exchanges between users.
Information we use
- Account and verification: your name, login and academic email addresses, account identifiers, selected university, verification status and documents you submit for student verification. If you use phone sign-in, we process the number and verification events. We receive the information needed for the Apple or Google sign-in option you choose, not access to your email inbox or contacts.
- Private and public profile details: your display name, photo, bio, university and any course or year information you provide. Birthday and gender are optional private details. If no valid birthday is available, we ask for a private age band to determine eligibility and apply safeguards. These private details are not placed on your public profile.
- Posts and interactions: Selling and Wanted text, photos, price or budget, category, chosen location, status, saves, trade confirmations, reviews, searches and community activity. Reuse points describe product activity; they are not a certified environmental measurement.
- Conversations: messages and the photos, voice recordings, documents, links, contacts or locations you choose to share, together with participants, delivery/read status and reply or forwarding context. Unsent drafts are different from delivered messages.
- Roro: your prompts, relevant conversation context, selected attachments, generated responses, task results and request/usage records. Roro does not automatically receive your other private or group conversations. Automatic seller management is not currently active.
- Support and safety: the information you provide in a request, report or appeal, relevant content references, necessary evidence and decisions. Other users may provide information about you in a report.
- Technical information: installation and notification identifiers, authentication events, IP addresses, request timing, service errors and necessary device/browser information. Providers can also generate operational logs. We do not receive your Face ID template; device authentication is handled by the operating system.
Please avoid sending unnecessary sensitive information. Do not put identification documents, private contact details or other people's confidential information in posts or public channels. Do not send passwords, login codes or recovery keys to Support.
Why we use it
We use information to provide the features you request, establish account and student eligibility, deliver messages and notifications, display posts to their intended audience, operate Roro, and respond to support requests.
For UK users, our legal bases depend on the purpose:
| Purpose | Legal basis |
|---|---|
| Account, posting, messaging and requested service features | Performance of our agreement where the processing is necessary for that agreement. |
| Security, fraud prevention, proportionate content review and support | Our legitimate interests in protecting users and operating a reliable service, balanced against users' rights, with particular care for younger students. |
| Limited delivered-message records for original recipients after deletion | Legitimate interests in retaining necessary exchange correspondence, subject to restricted access, the period below and individual rights. |
| A specific legal requirement | Compliance with that obligation; this is not a justification to retain all information indefinitely. |
| An optional use that requires consent | Your specific consent, which you can withdraw. Device permission or acknowledging this policy is not blanket consent to every use. |
We do not sell personal information, use it for cross-context behavioural advertising or run third-party advertising in RE. We do not use a person's private details to make automated employment, credit, housing or similar consequential decisions.
Who can see your content
Public profile information and posts are shown according to their audience and visibility settings. A public share link can show a limited eligible post preview outside RE, including its cover, title, price and description excerpt. A Wanted post without an uploaded photo may use a category illustration. It is not a photograph of an actual item.
Private and invitation-only conversations are available to their authorised participants. University and city channels have broader eligible audiences. Replies, mentions and forwards do not grant access to another private conversation. Other people may copy or export content they can see; RE cannot retrieve copies they independently retain outside the service.
The authorised operator can access relevant information when necessary for verification, support, reports, security or a legal obligation. Access to sensitive evidence is restricted and authenticated. RE messages are not end-to-end encrypted. Role mailboxes are handled by the responsible operator and forwarded to the operator's controlled mailbox.
Location and device choices
You can select a city or transaction area manually. Using current location is a separate action that can request device permission; browsing does not require continuous location sharing. For public posts, accounts aged 16–17 and accounts missing required age information are restricted to an approximate area. Eligible adults can explicitly choose an exact transaction location. An approximate location can still reveal an area where you spend time.
A location you explicitly send in a conversation may be precise and is visible to that conversation's authorised recipients. Map display and place search involve the relevant platform map provider. You can take a photo or select photos and videos to share. When you record a voice message, your chosen chat or channel determines who can hear it. For example, eligible members of a city channel can play a voice message sent there. You can change permissions in device settings; this can prevent the corresponding feature from working.
Protected younger accounts cannot receive new unsolicited message requests under RE's safeguards. Existing friends and accepted conversations remain available. School verification and self-declared age do not amount to verified proof of identity or age.
Roro and public-content review
When Roro is available and you choose to use it, RE sends the inputs needed for your request to OpenAI. Review AI output before relying on it or publishing a draft. A generated answer does not publish a post or send another person a message. Usage limits and temporary service restrictions apply.
Before you share a post, a profile update, a review or a message in a campus or city channel, RE can check the text and photos for sensitive information about someone else. For example, a photo may show a name beside a medical diagnosis. If RE spots something on your device, you can cover it or edit the draft and try again. Checks can miss sensitive details or flag harmless content. This public-content check does not cover private chats.
The following server checks for public posts and channel media are being introduced in stages. At publication of this policy they are not yet enabled for ordinary accounts.
Where these checks are available, when you publish or edit a listing, event, public profile, review or public university or city channel message, RE checks the public fields and images on its own service infrastructure. The same process applies to eligible students aged 16–17 and adults. RE does not send these submissions to OpenAI for moderation. Your choice to use Roro is separate.
We check text against rules for harmful conduct and prohibited transactions. We read printed text in images, check for copies of confirmed violations, and use an image classifier to flag potentially explicit material. We do not use this check to identify people or estimate their age. Automated checks can miss harmful material or flag harmless material such as art. A flagged version can be held for review. Eligible readers can see a version once publication succeeds. You can report content or challenge a decision. A report is tied to the version it concerns. If only one public profile detail needs to be removed, the other details can remain visible. RE uses the minimum facts needed to handle the case. It does not routinely make a second copy of a sensitive original. If an original is necessary for a specific appeal or other justified preservation need, access is restricted and its retention has a review date.
When you send a voice message or video to a public university or city channel, RE checks that you can post there and verifies the file. We check any text you add and compare a digital fingerprint of the cleaned file with active records of media that RE has confirmed breaks its rules. These checks do not transcribe your speech or identify what happens in a new recording. We do not send the recording, its soundtrack, video frames or its fingerprint to an external AI service for this check.
Once the message is sent, other members who have access can play it. A specific safety concern can hold a message for review. An authorised RE reviewer may listen to or watch the relevant recording to investigate a safety concern, report or appeal. You can report a message, block a user or ask us to review a decision. This process applies to public channels. Your private chats and invitation-only groups are outside its scope.
We keep a restricted fingerprint of confirmed rule-breaking media for up to 30 days from the decision to detect exact copies and, for images, close visual matches for review. We stop using it for matching if the decision is overturned or the period expires. Where evidence must be preserved for an appeal or legal reason, access is restricted. Our separate retention periods for uploads, published messages and review decisions are described below.
New document attachments and document forwards are not available in public city or university channels; permitted private-chat and invitation-only-group files are separate.
Private conversations, invitation-only groups, identity documents and report attachments are outside the public posting check. It does not mean every piece of content is safe. You can report a problem and request review of a decision.
RE does not opt in to provider training with API content. The API's normal operational and safety handling still applies. Roro disables stored response state where supported; this is not a promise of zero provider retention. The Responses service may retain abuse-monitoring information for up to 30 days, subject to applicable exceptions. The Moderations endpoint has a different retention policy. Images or content subject to safety or legal exceptions may be handled differently. We do not claim that all API processing takes place in the UK or EU.
Providers and international processing
Providers include Supabase for authentication, database and file storage; Cloudflare for website/share delivery and encrypted recovery infrastructure; Hetzner for the German recovery host; Resend for service emails; Expo and Apple for push delivery; OpenAI for Roro; and Apple or Google for the platform features you choose. Google Sign-In also declares linked identifiers and usage information for analytics in its SDK privacy information.
Supabase may run RE’s public-content checks outside the UK or the EU, including in the United States. The location of our database can differ from the location where a check runs. Provider support and security systems may also process information outside your country. Where UK transfer restrictions apply, we use an applicable adequacy arrangement or appropriate contractual safeguards and assess the relevant transfer. Contact privacy@reapps.uk for information about the safeguards applicable to your data.
We can disclose limited information to advisers or authorities when necessary and lawful, and to the appropriate parties in a business transfer subject to applicable protections. We assess requests and limit disclosure to what is justified.
Offline access and local records
RE stores a limited, encrypted copy of content already available to your account so that supported pages remain readable without a connection. The cache is separated by account, lasts up to seven days and is limited to 10 MiB of structured content and 100 MiB of media. Older or excess entries may be removed sooner. Previously uncached content and actions that require the server may remain unavailable offline.
Signing out clears the account's local cache. When RE receives a confirmed loss of access, it removes the affected local content. A device that is offline cannot immediately receive a new withdrawal or access decision; reconnecting allows RE to reconcile access. Offline display is not permission to publish, send, or bypass an account restriction.
For troubleshooting interface operations, RE keeps up to 20 local records for 24 hours containing the error category, operation stage and elapsed time. These records do not include message text, account identifiers or credentials and are not uploaded by this feature.
Taking a screenshot of an eligible listing may show an optional sharing invitation. RE receives the system's screenshot event; this feature does not read or upload the screenshot. Selecting Share opens RE's sharing panel for the listing card or link. Nothing is sent to another person until you choose a destination and complete the sharing action.
Retention, deactivation and deletion
For public-content reviews, expired uploads that were never submitted and are no longer referenced become eligible for cleanup 24 hours after the upload deadline. Redundant temporary copies become eligible 24 hours after verified publication; the published content remains under its normal controls. Original review material for rejected or withdrawn submissions becomes eligible 30 days after closure. An open appeal or a documented preservation need pauses cleanup. This is not a 30-day limit on requesting review. We retain a minimal decision record for 24 months, without the original text, attachments or raw classifier output. Processing queues are reviewed rather than silently approved or erased when overdue. Cleanup runs in bounded batches, and failed or blocked deletion is tracked until resolved. These controls apply to new eligible review records. Removing a file may not immediately invalidate an existing link while caches expire, and cannot remove a copy someone has already saved.
We keep information for its purpose and any specific legal or safety requirement. Deactivation pauses an account; it is not deletion. Active-account posts, conversation history and Roro history remain available under their feature controls until removed or no longer needed. You can delete Roro conversations and request account deletion separately.
In Settings, choose Delete account to request permanent deletion. You do not have to deactivate first or give a reason, and you can cancel before confirming. Acceptance of a deletion request is not proof that every storage copy has already been erased. We remove the account identity, profile and associated content through the deletion process, subject to legitimate recipient records, other people's rights and any specific unresolved legal or safety dependency.
Original participants may retain a restricted, read-only private-chat record for up to 12 calendar months from the last successfully sent message. Reading it, deleting an account or registering again does not restart that period. Earlier cleanup can apply when no legitimate original participant remains. The sender is labelled “Deleted account”; that label does not make the message content anonymous. Withdrawn or safety-hidden content is not restored.
After verified deletion completion, the minimal result receipt is kept for 30 days. Verification documents normally become due for cleanup 30 days after a review decision, except for a documented hold. Technical AI accounting information is minimised 90 days after final settlement, subject to unresolved accounting or safety needs; this is not a 90-day expiry for Roro conversations.
Closed support/report records, limited removed-post audits and view records are reviewed for necessity under separate retention controls. We do not retain them merely because deletion is technically possible later. A specific hold or unresolved dependency is recorded and reviewed. A scheduled or failed cleanup is not treated as completed erasure.
Encrypted recovery copies use a seven-day retention policy. Provider backups and logs can have separate periods. Deleted data can remain temporarily in protected backups until expiry; protective changes must be reapplied before recovered data is returned to service. We do not promise immediate erasure of independent recipient exports or every provider copy.
Deleting RE does not delete your Apple or Google account. If a request cannot be completed in the app, contact privacy@reapps.uk. We may need proportionate identity or authority verification; never send a password.
Your rights and younger users
Depending on the applicable law and circumstances, you can request access, correction, deletion, restriction, a portable copy, or object to certain processing. Where processing depends on consent, you can withdraw it without affecting earlier lawful processing. You can complain to the UK Information Commissioner's Office at ico.org.uk/make-a-complaint.
US rights vary by state and the processing involved. Where applicable, we honour access, correction, deletion, portability, sensitive-data choices and appeal rights. Contact privacy@reapps.uk to make or appeal a request. We do not discriminate against you for exercising applicable rights. An authorised representative may need to establish authority, and a request does not entitle anyone to another person's private information.
For users aged 16 or 17, the first-use Roro notice asks them to confirm that a parent or guardian has given permission. We record the declaration, its wording version and the time it was made, linked to the account. This is a declaration by the user, not a check of the parent’s identity. We do not collect a parent’s identity document or contact details for this step. Withdrawing AI permission prevents new AI requests; it does not automatically delete existing conversations. We remove the active permission declaration when you withdraw AI permission or delete your account.
RE is not intended for anyone under 16. If you believe someone below the permitted age is using RE, or a younger student is at risk, contact Support or Privacy. We restrict access while establishing the minimum information needed to resolve an age concern and handle deletion or other rights as appropriate. We do not use a university affiliation as proof that someone is an adult.
Security and changes
We use authentication, access controls, restricted evidence access and encrypted recovery copies. No service is completely secure. Keep your account credentials private and report suspected misuse.
We will give appropriate notice of material changes and obtain further agreement or consent where required before those changes apply. Updating a policy does not by itself authorise an incompatible new use of existing data. The version and effective date shown with the published policy identify the terms in effect.