Privacy Policy

The short version

• We never sell your data. No advertising, no data brokers, no third-party tracking, no profiling of your visits.
• Hosts never learn who you are. Access is verified with a one-time code; your name and profile are never shared with the host.
• Location only when you use the map. We ask for your location just in time, use it on the spot, and do not build a location history or track you in the background.
• Payments stay with Stripe. Card details never reach us; payments are processed by Stripe, a regulated payment institution, and we only ever see references, amounts and statuses.
• You are in control. Export your data or delete your account directly in your profile, at any time; if you still have purchased Credit, first request its repayment via support@relievedapp.com and delete afterwards.

The rest of this policy explains everything in detail: what we process in each situation, why, with whom we share it, how long we keep it, and your rights.

1. Who we are

The Relieved platform (relievedapp.com and the Relieved app) is operated by REBA Software, a sole proprietorship established in the Netherlands, registered with the Dutch Chamber of Commerce under number 42051273, Prins Hendrikstraat 51, Egmond aan Zee, the Netherlands. REBA Software is the data controller for the processing described in this policy. Our privacy contact point is support@relievedapp.com. We are established in the EU, so no EU or UK representative is required, and we are not required to appoint a data protection officer; the owner personally handles privacy matters.

One important exception: payments. Stripe Technology Europe, Limited, a payment institution authorised by the Central Bank of Ireland, is the independent data controller for payment data. Card and bank details go directly to Stripe and never reach our systems; we only receive transaction references, amounts, and statuses. Stripe’s own privacy policy (stripe.com/privacy) applies to that processing. Your Relieved Credit balance is different: it is a prepayment that we owe you, and we administer that balance ourselves, so this policy applies to it.

2. What we process, in each situation

2.1 Creating and using an account

Email address, password (stored only as a hash), your country and your currency, your language, your marketing preference, and the time and version of your acceptance of the Terms and of this policy. Optionally: your name, an emoji avatar, a profile photo (reviewed by our moderation before publication and visible only to you), a short bio and the languages you speak, a referral code and who referred you, and in the app the token we use to send you notifications. We keep the number of completed visits, which you see in your own profile, and the cancellation count described in section 3. If you enable two-factor authentication, we store the authentication secret needed to verify your codes. An account is optional: you can also book as a guest (section 2.5).

Signing in with Google or Apple (where offered). If you choose to sign in with Google or Apple, we receive from that provider only your email address and, the first time, your name; Google also sends a profile picture address, which we do not use and delete immediately. We use these details solely to create your account and sign you in; we share them with no one, do not use them for advertising or profiling, and keep them for as long as your account exists. You can change or remove your name in your profile. For the sign-in itself, Google and Apple are controllers under their own privacy policies; both participate in the EU-US Data Privacy Framework (section 6). If you choose 'Hide My Email' with Apple, you receive our messages through Apple's relay address. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

2.2 The map and your location

When you open the map, your device or browser asks for permission to use your location. We use it at that moment to show nearby toilets and, when you book, to check that you are within walking distance. We do not track you in the background, we do not build a location history, and we do not use your location for anything else. The map on the website is drawn by an open-source library that sends no usage data; Mapbox, our map provider, receives only the map tiles, styles, address lookups, and static map images you request (your IP address, the area of the map you view, and what you type into the address search) and processes those as our processor. Your own location never goes to us, and not to Mapbox unless you switch on Mapbox Telemetry yourself (see below); what does go to us is the map area you are viewing, to fetch the toilets within it, and we do not store it.

In the app, the map loads only after you tap 'Show map'. Mapbox's map library then keeps an anonymous number on your device with which Mapbox counts map usage and bills us; that number is not linked to you or your account and is not used for advertising or tracking. The sending of location and usage data to Mapbox (Mapbox Telemetry) is switched off in our app and we never switch it on for you; only if you switch it on yourself in Mapbox's menu on the map does Mapbox receive de-identified location and usage data. If you switch the map off (the line under the map or the info screen), the app no longer loads the map library and erases the number. Mapbox processes this data under its own terms, data processing agreement and privacy policy: mapbox.com/legal/tos, mapbox.com/legal/dpa and mapbox.com/legal/privacy.

2.3 Booking and visiting

A booking record contains the booking reference, the chosen toilet, timestamps and status, the price breakdown, and your one-time access code. The host verifies your code, never your identity: your name, profile, and contact details are not shared with the host, and the Host Addendum forbids hosts from collecting visitor data. Because a booking links a place to a time, we treat this data with the same care as location data.

2.4 Paying

Top-ups and payments run through Stripe as independent controller (section 1). We process the transaction references, amounts, currencies, fee breakdown, and payout references needed to operate the marketplace, plus fraud signals that Stripe's systems (such as Stripe Radar) return to us so that we can prevent abuse. If you pay in another currency, we process the exchange rate and margin shown to you before payment. To honour our repayment promise, we keep a ledger that links your Credit balance to the original payment references (top-up lots). Repayments go back to the original payment method through Stripe; only where that is no longer possible do we process the bank account number (IBAN) you provide for a documented bank repayment. The amounts, dates, and references involved fall under the seven-year tax retention in section 5.

2.5 Guest checkout

If you book without an account, we process only your email address (to send your access code and the legally required booking confirmation), the booking and payment references, and your recorded acceptance of the Terms. No account or payment profile is created; the data serves exactly one visit. Your email address is processed both to perform the booking and to meet our legal duty to confirm it on a durable medium (Article 6(1)(b) and (c) GDPR). Your country, needed to show you the legally required information, is derived from your IP address within our hosting provider Cloudflare's infrastructure; the IP address is not stored for this and not passed to any other party.

2.6 Reviews

A review contains your text, your rating, the publication date, and the date of the visit it concerns, linked to your account. When your account or the listing is deleted, the review is removed or anonymised. We never pay for reviews.

A host may also write a review about you as a visitor after a visit. That review is visible only to you, with the host's business name; it is never shown to other hosts and never combined into a score about you that others can see, and it follows the same retention as your own reviews.

2.7 Becoming and being a host

For hosts we process business and contact details, the toilet's location and photos (reviewed by our moderation before publication), the VAT number with its VIES verification result, your trader or non-trader declaration, your Stripe Connect account reference, payout and invoice data, and the tax fields (tax identification number, property address, and cadastral reference) that EU platform tax reporting rules (DAC7) may require us to collect, verify, and report to the Dutch tax authority, which exchanges them with the tax authority of your country. For sole-trader hosts, business data such as invoices are also personal data and are treated as such. Because you as a Host are the seller of the visit, we display your trader details (the name of your business, your registered address, the email address and telephone number you provide for visitors, and your registration and VAT numbers) at every live toilet before booking, as consumer law requires; for a sole trader these may be your own name and address. You give your bank account only to Stripe; we do not record it. To verify your business we query public registers (the Dutch, French, and Spanish cadastres, the French company register, and the Hungarian company register); we send them the business details you gave us and nothing about visitors. When you connect your Stripe account, we pass the business and contact details you gave us to Stripe so that you do not have to enter them again; you check and confirm them at Stripe before accepting Stripe's agreement. If you stop hosting, we keep your host data in full for a further 24 months for questions and disputes about visits, statements and reviews from that period; after that we reduce it to the fiscal core described in section 5. DAC7 data is kept for the statutory retention period of five to ten years, depending on the Member State, and we inform you before information about you is first reported to a tax authority.

2.8 Support, complaints, and disputes

When you contact us we process the correspondence, your booking reference, and the evidence needed to assess a claim, such as booking records and timestamps. If a complaint goes to out-of-court dispute resolution, the file is shared with the competent body, such as a consumer mediator or a conciliation board; these bodies act as independent controllers.

2.9 Reports, moderation, and serious incidents

Reports about listings, reviews, or users are processed under the Digital Services Act: we record the report, our assessment, and our reasoned decision. For reports of serious criminal offences, such as hidden recording equipment, we keep a separate, strictly access-controlled incident file that can include criminal-offence data and victim data; we process it under Article 10 GDPR in conjunction with Dutch implementing law, follow a fixed internal protocol, notify the competent authorities where the law requires, and destroy the material when it is no longer needed.

2.10 Legal records

To be able to demonstrate compliance, we keep server-side records of your acceptance of the Terms and of this policy (with the version of each) and any withdrawal declarations you submit through the withdrawal function, including the name, booking or contract reference, and email address you enter there and the acknowledgement of receipt we send with its date and time, each with timestamp and version. These records are kept no longer than needed to demonstrate compliance, at most until the applicable limitation periods expire.

2.11 Email

We send transactional email (access codes, booking confirmations, receipts, security messages) through our email service providers. Marketing email is sent only if you opted in, and every message contains a one-click unsubscribe; your opt-out is logged so we can honour it.

2.12 Local storage and technical logs

Relieved sets no cookies of its own and uses no analytics or advertising tools. What we do keep on your device is local storage that the site or the app needs to work or that you set yourself; none of it requires your consent under the ePrivacy rules, with one exception: the anonymous number of the map library in the app, which only reaches your device after you tap 'Show map' (section 2.2); that is why we show no consent banner. Specifically: your own preferences (interface language, display currency, the country whose terms apply to you and, as a host with several locations, the location you last chose on your dashboard, kept until you change them); what the site needs to work (a cached copy of our fee table, your last map position for ten minutes so the map returns where you left it when a browser reloads the page, your sign-in session while you are logged in, and the data of a host registration in progress for the duration of that browser session); small flags that remember you have already seen a one-time question; and your location only when you ask for it, where we remember whether you allowed the browser to share it, not the location itself. In the app these are joined by the encrypted sign-in session, a cache of map tiles that the map library itself refreshes and clears, your choice at 'Show map' with its time and, unless you switch it off, the system's screen snapshot when you switch apps. We do not read this storage for any other purpose and never share it. Fonts and scripts are served from our own domain. Security measures of our hosting provider (Cloudflare) may set a strictly necessary security cookie when it needs to distinguish a person from an automated request; Stripe sets its own fraud-prevention cookies during payment. Our infrastructure keeps standard security and access logs for a limited period. There are no advertising cookies and no third-party trackers.

3. Why we process your data, and on what legal basis

• Performance of our contract with you (Article 6(1)(b) GDPR): your account, the map and distance check, bookings and access codes, payments and payouts, reviews, and support.
• Legal obligations (Article 6(1)(c)): keeping the tax-relevant core of transactions, sending the consumer-law confirmations on a durable medium, displaying Hosts' trader details to visitors before booking, platform tax reporting where DAC7 requires it, and notifying authorities of serious offences where the Digital Services Act requires it.
• Legitimate interests (Article 6(1)(f)): preventing fraud and abuse, moderating photos and reports, handling disputes with the evidence described above, and securing our network. We have balanced these interests against your rights; the outcome is documented internally, the data used is data we already hold for the service, decisions are made by a person and not automatically, and you can object at any time (section 7). To prevent misuse of the free cancellation window, we keep a count of the cancellations you make within that window for 180 days; if it reaches three within thirty days, a member of our team decides whether to suspend the free cancellation window for ninety days. That decision is never automatic, and you can contest it via support@relievedapp.com.
• Consent (Article 6(1)(a)): marketing email. Your device's location permission is the technical layer required by privacy law; the processing itself is needed to perform the service you request.

We do not ourselves use automated decision-making with legal or similarly significant effects, and we do not profile your visiting behaviour; the counts we keep about your use are the number of completed visits, which you see yourself, and the cancellation count described in section 3, used solely to prevent misuse. Stripe, as independent controller, applies its own automated fraud scoring (Stripe Radar) to payments; if a payment is ever declined on that basis, you can ask us or Stripe for a human review. Our moderation decisions are made or reviewed by a person, and our default ranking (distance bands of 100 metres, and within a band availability, rating, and exact distance; price plays no role) has no legal or similarly significant effect on you. Visit patterns could in theory hint at health; we therefore deliberately never analyse visit frequency, never log your use of accessibility filters, and never share visit data with anyone.

4. Who we share data with

4.1 Processors working for us

• Supabase: database, authentication, and storage, hosted in the EU.
• Mapbox: map tiles, styles, address lookups, and static map images for the website and the app (United States, see section 6), with no usage data from our website; the counting of map usage in the app is done by Mapbox on its own account (section 4.2).
• Cloudflare: content delivery and security (United States, see section 6).
• Resend, Inc.: delivery of transactional and, with your consent, marketing email (United States, see section 6).
• Moneybird: bookkeeping and invoicing, in the Netherlands.

4.2 Independent controllers

• Stripe Technology Europe, Limited for payments and payment data (section 1); your Credit balance is administered by us.
• Mapbox, Inc. for counting map usage in the app with an anonymous number and for Mapbox Telemetry if you switch it on yourself (section 2.2), under Mapbox's own privacy policy (mapbox.com/legal/privacy).
• Public registers (cadastres and company registers) that we query to verify a host's business (section 2.7).
• Consumer mediators and dispute-resolution bodies when you escalate a complaint (section 2.8).
• Insurers and legal advisers if a claim or legal proceeding requires it.
• Public authorities where the law requires it: tax authorities, supervisory authorities, and law enforcement in response to valid legal requests or under our duty to report serious offences. We check every request and share no more than legally required.

4.3 Who we never share with

We never sell or rent your data. We share nothing with advertisers or data brokers. And hosts never receive your identity: not your name, not your email address, not your profile. The only thing a host can verify is your one-time access code.

5. How long we keep your data

• Account data: until you delete your account; deletion anonymises your profile once purchased Credit has been repaid to you and pending matters are settled. An account not confirmed within 30 days is erased.
• Abandoned host registration: 180 days, then erased.
• Host data after stopping: 24 months in full, for questions and disputes about visits, statements and reviews from that period; after that only the fiscal core below.
• Bookings and reviews: operationally until account deletion; reviews are then removed or anonymised.
• The tax-relevant core of transactions (amounts, dates, invoice data): seven years, as Dutch tax law requires, in minimised form and disconnected from your profile.
• Host records after account deletion: the fiscal core of a host record (legal name, business address, VAT and tax numbers, country, business status, and the date we collected them) for seven years after the end of the last year in which you had transactions, with restricted access, because tax law requires us to keep our administration; everything else in the host record is deleted immediately.
• Complaints, reports, and statements of reasons: three years after closure, then anonymised; where proceedings are pending, until they end and the limitation period has run.
• Confirmation emails sent: the content for thirteen months, after that only the proof of sending.
• Guest consent records: as long as the related visit, seven years.
• Consent, acceptance, and withdrawal records: as long as needed to demonstrate compliance.
• Support correspondence: up to two years after the file is closed.
• Serious-incident files: only as long as the investigation, proceedings, or legal claims require, reviewed at least yearly, then destroyed.
• Security and email delivery logs: for the limited standard periods of our infrastructure providers.

6. International transfers

Your data is stored in the EU. A limited set of providers processes some data in the United States. Mapbox, Cloudflare, and Resend are certified under the EU-US Data Privacy Framework, and Stripe participates in the Framework for its own processing as independent controller; with each of them we additionally have the EU Standard Contractual Clauses in place as a fallback, so transfers remain lawful even if the Framework is ever suspended or invalidated, in which case we would also carry out a renewed transfer assessment. Supabase hosts our data in the EU but can access it from the United States for support and administration; it does not participate in the Framework and works for us under the EU Standard Contractual Clauses with supplementary measures. Mapbox may engage an affiliate in Belarus (MapData OOO) as a sub-processor for development and operations; there is no adequacy decision for Belarus, and that transfer rests on the European standard contractual clauses Mapbox has concluded with its affiliates and on our transfer impact assessment. At most this concerns the IP address, the map area and the anonymous number described in section 2.2, never booking data. No other transfers outside the EEA take place.

7. Your rights

You have the right of access, the right to rectification, the right to erasure, the right to restriction of processing, the right to object (including to any processing based on legitimate interests, and always to direct marketing), the right to data portability, and the right to withdraw consent at any time without affecting earlier processing.

The two most common rights are built directly into the product: in your profile you can download a machine-readable copy of your data, and you can delete your account; if you still have purchased Credit, we repay it first at your request via support@relievedapp.com. For everything else, email support@relievedapp.com; we may ask you to confirm control of your account email, and we respond within one month. Exercising your rights is free.

8. Complaints

If you believe we handle your data incorrectly, contact us first at support@relievedapp.com and we will try to resolve it. You also always have the right to lodge a complaint with a supervisory authority (Article 77 GDPR): with the Dutch Autoriteit Persoonsgegevens as our lead authority, or with the authority of your own country, such as the CNIL in France, the NAIH in Hungary, the Garante in Italy, or the AEPD in Spain.

9. How we protect your data

All traffic is encrypted in transit (TLS with HSTS) and data is encrypted at rest. Database access is restricted with row-level security, passwords are stored only as hashes, two-factor authentication is available on every account and enforced on our own administrative access, and access codes are single-use. By design there is no background location, no location history, no third-party analytics, and no advertising identifiers. If a breach is ever likely to pose a risk to you, we will notify the supervisory authority within 72 hours and inform you where the law requires.

10. Children

Relieved is for adults. You must be at least 18 to use the platform, and you confirm this when registering or paying as a guest. We do not knowingly process children's data; if we learn that we do, we delete it. Parents or guardians can contact support@relievedapp.com.

11. Changes to this policy

We may update this policy. For material changes we will notify you at least 21 days before they take effect, by email or in the app, consistent with how we announce changes to our Terms; where required or appropriate we will ask you to actively confirm again. The current version is always available at relievedapp.com/privacy, and the version number at the top tells you what applies.

12. Contact

• REBA Software (operating as Relieved)
• Prins Hendrikstraat 51, Egmond aan Zee, the Netherlands
• Chamber of Commerce (KVK): 42051273
• Telephone: +31 72 369 0125
• Privacy contact: support@relievedapp.com · relievedapp.com

© 2026 REBA Software · Relieved · Privacy Policy version 2026-09.3

© 2026 REBA Software · Relieved · relievedapp.com · Last updated: October 2026 (version 2026-09.3)

← Relieved