Back to site

Privacy policy

Last updated 21 October 2026

This policy explains what personal data Out There Together collects, why, and what you can do about it. It covers both this website and the Out There mobile app.

The short version. We collect what we need to show you sailings and connect you with other people. With your permission, we also tell Meta about visits to this website and, in the app, when you open it and first sign in, so we can measure our Facebook and Instagram advertising. We do not sell your data for money. Anything about your identity or who you are looking to meet is optional, kept separate from your public profile, and only stored if you explicitly ask us to. We do not take payments, so we never hold your card details.

1. Who we are

Out There Together is a cruise discovery and social planning service for LGBTQ+ travellers, operated by Blockbeam Ltd of 6 Moulton Close, Knutsford, WA16 8BJ, United Kingdom.

Blockbeam Ltd is the data controller for the personal data described in this policy. We are registered with the Information Commissioner's Office under reference ZC056342. You can find us at blockbeam.co.uk.

You can reach us about anything in this policy at hello@outtheretogether.com.

2. What we collect

When you use this website

The website does not ask you to create an account. Our analytics provider, Metricool, records a page view when you load a page. That record contains the address of the page, the size of your browser window, your IP address and your browser user agent. It does not store anything on your device and does not follow you to other websites.

If you choose to accept marketing cookies, we also use Meta Pixel. It sends Meta a PageView event and information about your visit, such as the page address, browser and device information, IP address and referrer. Meta may use cookies and similar identifiers to associate this with information it already holds about you. We use the Pixel to measure the performance of our Facebook and Instagram advertising and to improve who sees those ads. We do not send Meta your waitlist email address through the Pixel.

Marketing cookies are optional and the legal basis is your consent. You can reject them without affecting your use of the site, or change your mind at any time through Cookie settings. Meta explains its own processing in its Privacy Policy.

If you join the waitlist, we store the email address you enter, the date you gave it and the wording you agreed to. We also keep technical records of passing it to our email provider. We use it only to email you about Out There, starting with when the app opens. We pass your address to our email provider, Sender, which sends those emails for us, together with your first name if you gave one and a reference code that identifies your sign-up. We do not pass it to anyone else and we do not use it to advertise to you elsewhere. Consent is the lawful basis, and you can withdraw it at any time by emailing hello@outtheretogether.com, which removes your address from the list.

When you use the app

WhatDetail
AccountEmail address and a password, which is stored only as a secure hash and is never visible to us.
ProfileDisplay name, a unique @handle, and optionally a home port, a photo, interests and a short description you write yourself.
HandleYour @handle, which other members can see and search for. We also keep a coded fingerprint of the handles of deleted accounts, and a record of every handle change for 2 years. See sections 8 and 10.
MentionsIf you type someone's @handle in a sailing chat or an event chat, they are notified, and the notification names you and the sailing or event. If they are not yet in that chat but you are allowed to reach them (a friend, for a sailing chat; someone who can see the event, for an event chat), we also keep a short-lived mention invitation: who mentioned them, who was mentioned, which chat and which message. It holds no message text. It lets them see a Join prompt on that sailing or event page. Nobody is ever joined to a chat or marked as going because of a mention. We also keep a short record of who mentioned whom, with no message text, to cap how many mention notifications one member can send in an hour. See sections 8 and 10.
Handle availability checkThe check that tells you whether a handle is free, including before you have an account, is limited to a number of tries a minute and an hour so that it cannot be used to guess at handles. To do this we count the tries from your network address, or from your account if you are signed in. We never store the address itself, only a coded fingerprint (a one-way hash) of it. We do not store the handles you try. See section 8.
Links to other membersA relationship link, or a travelling-with link for a particular sailing, that you and another member have both agreed to. We also keep a record of each request: who asked, who replied, the answer and the dates. The other member is notified of a request, and the notification names you. See section 4.
SailingsWhich sailings you join, and whether you have marked yourself as planning or booked. Changes to that status are recorded.
CrewsWhich crews you belong to, invitations you send or accept, and shared sailing shortlists.
EventsEvents you host or are invited to, and your replies to them.
MessagesThe content of messages you send in sailing chats, crew chats and one-to-one messages, and when you sent them.
PhotosPhotos you add to your gallery or send in chats are checked when you upload them against a database of known child sexual abuse images. We keep a record of each upload: when it happened, whether it passed, the result of the automatic nudity check, and for a photo sent in a chat the text of the message sent with it. See section 5.
Photo rules confirmationThe first time you add a photo to your private gallery, and the first time you send a photo in a chat, the app asks you to confirm the photo rules. We record that you confirmed, the date, and the version of the wording. See section 5.
Identity verificationOptional. If you choose to verify, our provider Didit checks your identity document and your face. We keep only whether the check passed, failed or is waiting, when, and a reference to it. See section 5.
EmailSign-in emails are sent for you through our email provider, Sender. Members are also signed up by default to occasional marketing email about new features and offers, and can turn that off in Settings. If you do, or if you delete your account, your address is removed from Sender.
Identity and intentOptional. See section 4, which explains how this is treated differently.
SafetyReports you make, accounts you block or mute, and the outcome of any moderation decision. A report can be about a single gallery photo or chat image, and the reported image file is kept with the report as evidence.
Partner clicksWhen you tap through to a booking partner we record that it happened, which sailing and partner it was for, and a reference code. See section 7.
TechnicalBasic device and app information needed to keep the service working and to sync your data when you reconnect.
App usage analytics (only if you turn it on)If you choose to turn it on, we use PostHog, an analytics provider hosted in the EU, to understand how the Out There Together app is used, for example which screens are opened and how often. This is switched off by default and only starts if you say yes. You are identified by your account's internal ID number, the same kind of reference number the app uses behind the scenes for your account generally, never by your name, email address or any profile detail. We never send PostHog your messages, your photos, or anything about your gender identity, sexual orientation, dating preferences or intent to date. Screens related to those things, and to safety reports, blocking, muting or identity verification, are excluded entirely and are never reported to PostHog, whether or not you have turned analytics on. You can turn this off at any time in Settings, which stops sending this information immediately and clears what PostHog holds locally on your phone.
Measuring our adverts (Meta, only if you agree)

The first time you open the app, we ask whether you agree to us telling Meta, which runs Facebook and Instagram, when you open the app and when you first sign in. We use this only to see which of our Facebook and Instagram adverts bring people to Out There Together, and so that Meta can show our adverts to people more likely to want them. If you say no, nothing is sent to Meta.

If you say yes, the app sends Meta two things: that the app was opened (each time it is opened), and, once only, that a new account signed in for the first time. Meta's software sends these with basic details about your phone, such as its model, operating system, app version and IP address, and a random reference it creates for the app on your phone. On iPhone, Meta also receives your phone's advertising identifier, but only if you also allow it when Apple asks. On Android, the advertising ID is included once you have agreed.

We never send Meta your name, email address, account number, profile, sailings, messages or photos, or anything about your gender, orientation, Meet preferences or identity check.

Because Out There Together is an app for LGBTQ+ people, Meta could infer from these events that someone using your phone may be LGBTQ+. That is why we only do this with your explicit consent. Meta may link what it receives to a Facebook or Instagram account you have, under Meta's own privacy policy.

You can change your mind at any time in the app under You, Settings, Our adverts. Turning it off stops anything further being sent straight away. On iPhone you can also stop tracking for the app in Settings, Privacy and Security, Tracking. Turning it off does not delete what Meta already has. To clear the link between apps and your Meta account, use "Your activity off Meta technologies" in your Facebook or Instagram settings. Signing out also stops it, and the app asks again the next time it is opened. The app does not show adverts.

When you browse the app as a guest

You can look through sailings in the app without creating an account. As a guest you see sailings, ships, cruise lines, dates, itineraries and how many members have marked each sailing. You never see who they are: names, handles, photos and profiles stay hidden, and so do chats, events and Meet. We do not create an account or a profile for you, and app usage analytics never runs for a guest. Each time the app fetches sailings for you, our hosting provider logs the request in the ordinary way, including your IP address and basic device and app details, for security and to keep the service running. The app keeps a copy of the sailing list on your phone for up to 15 minutes, along with a note that you are browsing as a guest. Creating an account, signing in or deleting the app clears both.

3. Why we use it, and our legal basis

PurposeLegal basis
Creating and running your account, showing you sailings, crews, events and messagesPerformance of a contract with you
Showing sailings, itineraries and member counts to someone browsing the app without an accountOur legitimate interests in letting people see what Out There offers before they join
Showing your @handle to other members and letting them search for itPerformance of a contract with you
Letting you know when you are mentioned in a chat, and showing a Join prompt if you are not yet in itPerformance of a contract with you
Keeping a short record of mention notifications sent, so that no member can send more than 30 an hourOur legitimate interests in protecting members from spam and harassment
Limiting how often the handle availability check can be used, using a coded fingerprint of the caller's network addressOur legitimate interests in protecting members from handle guessing and keeping the service available
Keeping a coded fingerprint of deleted members' handles, and a record of handle changes for 2 years, so that nobody can take a deleted member's handle and pass as them, and so that we can show what changed, who changed it and whyOur legitimate interests in preventing impersonation and protecting members
Showing relationship links and travelling-with links that you and another member have agreed toYour agreement, which you give when you send or accept a request and can withdraw at any time by removing the link. See section 4 for why relationship links are sensitive.
Keeping a record of link requests, so that we can enforce the 30 day wait before someone can ask againOur legitimate interests in protecting members from repeated unwanted requests
Storing your identity and intent preferencesYour explicit consent, which you can withdraw at any time
Keeping the community safe: reports, blocking, moderation, and preventing abuseOur legitimate interests in protecting members, and our legal obligations
Checking uploaded photos against known child abuse imagesOur legitimate interests in protecting children and preventing crime
Checking uploaded photos automatically for nudity, through SightengineOur legitimate interests in protecting members and keeping the service safe
Recording that you have confirmed the photo rules, which is required before you can add photos to your private gallery or send photos in chatsOur legitimate interests in protecting members and being able to show what each member agreed to
Checking your identity through Didit, if you choose to verifyYour consent, which we record against a numbered version of the wording you agreed to, and which you can withdraw at any time
Sending sign-in and account emailsPerformance of a contract with you
Sending marketing email to membersOur legitimate interests in telling members about the service, under the "soft opt-in" rule for email. You can turn it off at any time in Settings.
Recording clicks through to booking partners so we are paid correctlyOur legitimate interests in running a viable service
Understanding how the website is used, in aggregateOur legitimate interests in improving what we offer
Understanding how the app is used, if you turn on app usage analyticsYour consent, which you can withdraw at any time in Settings
Measuring Meta advertising and improving who sees it, on the websiteYour consent to marketing cookies
Telling Meta when the app is opened and when a new account first signs in, to measure and improve our Facebook and Instagram advertsYour explicit consent (UK GDPR Article 6(1)(a) and, because it could reveal that you use an LGBTQ+ app, Article 9(2)(a)). Consent is also what allows the app to store and read Meta's information on your phone (the Privacy and Electronic Communications Regulations). You can withdraw it at any time in Settings.
Meeting our legal and regulatory obligationsCompliance with a legal obligation

Where we rely on legitimate interests, we have considered whether that interest is overridden by your rights, and you can object at any time using the contact details below.

4. Identity and intent data

Information about your gender, your sexual orientation, and what you are looking for on a sailing is special category data under UK data protection law. We treat it differently from everything else.

Relationship links

You can ask another member to show on both of your profiles that you are in a relationship with each other. A relationship link can reveal something about your sexual orientation, for example if you link to someone of the same sex. That makes it special category data, like the information above, so please read this before you send or accept a request.

Travelling-with links work in a similar way for one sailing at a time, and only between members of the app. Both of you must agree. A travelling-with link shows on that sailing's list of people to the members who have joined the sailing, and on the sailing card on your profile if you have chosen to show your sailings. It is removed if either of you leaves the sailing, blocks the other, or deletes your account.

5. Photo checks and identity verification

Known child abuse images (PhotoDNA)

Every photo you upload to a gallery or a chat goes first to a private holding area, and is published only if it passes a check against a database of known child sexual abuse images. The check uses PhotoDNA, which is provided by Microsoft. A private scanner that we run, hosted by Hetzner in Germany, turns the photo into a hash, which is a short string of numbers that works like a fingerprint and cannot be turned back into the picture. The scanner works on the photo in memory and sends only the hashes to Microsoft's PhotoDNA service in the UK. Microsoft does not receive the photo.

If a photo matches, it is not published. It stays in a restricted store, which ordinary members and ordinary app access cannot reach, so that it can be reviewed and so that the law can be followed. There is currently no fixed end date for this, which we are reviewing. We do not tell you the detail of why an upload failed.

Automatic nudity check (Sightengine)

Photos you upload are also checked automatically for nudity by Sightengine, a service of Kozelo SAS in France. We do this to help keep the service safe for members. We send Sightengine the photo itself and nothing else about you: no name, email address or member number. Sightengine sends back a result, and we record it. The result affects what happens to your photo in these ways:

The check can be wrong, and a photo may be moved or declined by mistake.

Sightengine deletes images after processing by default, and we do not use any of its features that keep images. Photos may be processed in any of Sightengine's data centres, including outside the UK and the European Economic Area. Where that happens, the transfer is protected by the EU standard contractual clauses and the UK addendum in our data processing agreement with Sightengine.

You can report a single gallery photo or chat image from the full-screen view of the photo (in the newest versions of the app). A reported image file is kept as evidence and cannot be deleted, by you or by account deletion, while the report exists. Who made a report stays confidential, as for any other report.

Only full administrators on our staff can view a member's image. They can do so only through our private admin website, and only to deal with a report or a safety review. The image stays hidden until the reviewer clicks Reveal. Every reveal is logged: who, which image, when and why. The log cannot be edited or deleted by staff.

If you think we have made a wrong decision about one of your photos, email hello@outtheretogether.com and a person will review it.

Confirming the photo rules

The first time you add a photo to your private gallery, and the first time you send a photo in a chat, the app asks you to confirm the photo rules: that you are 18 or over, that everyone shown is an adult who agreed to be pictured, that you own the photo or have permission to share it, and that sharing someone else's intimate images without their consent is not allowed and will lead to action on your account. We record your confirmation with the date and the version of the wording, and ask again only if the wording changes. Without the confirmation, the photo cannot be added to your private gallery or sent in a chat.

Identity verification (Didit)

Verification is optional, and it is needed to send, view or share photos. It is run by Didit, which is an identity verification provider. Inside Didit's own screens you show a photo of an identity document and a photo of your face. Didit holds that information. We give Didit a reference number for your account so that the result comes back to the right person, and we receive only whether you passed, failed or are waiting, and when. We never receive or keep your document, your face image, the name on the document or your date of birth.

Didit decides how long it keeps what you show it, under its own terms and privacy notice. If you withdraw your verification consent in the app, we delete our result and your badge. If you delete your account, we delete our result. In neither case do we currently ask Didit to delete its own copy. If you want that, email hello@outtheretogether.com and we will request it.

6. Who we share it with

We do not sell your personal data, and we never will.

We share it only with service providers who process it on our instructions:

Meta Platforms Ireland Limited, which runs Facebook and Instagram, receives data only if you agree: on the website when you accept marketing cookies, and in the app when you say yes to the question on first open. Meta uses what it receives for its own purposes as well as ours, so it is not only acting on our instructions. It is responsible for its own use under Meta's privacy policy.

We may also disclose personal data where we are legally required to, or where it is necessary to protect the safety of our members.

Other members see only what your settings allow: your display name, your photo if you have added one, your home port if you have added one, your status on a sailing you have both joined, and anything you post in a chat you are both part of. They can also see your @handle, and any relationship links you have agreed to, whatever your settings (see section 4). Travelling-with links are described in section 4.

7. What happens when you click through to book

Out There is an introducer, not a travel agent. We never take payments, hold deposits or confirm bookings.

When you tap through to a booking partner, we record that the click happened, along with the sailing, the partner and a reference code that lets the partner tell us the referral came from you. We do this so that we are paid the referral fee we are owed.

Once you arrive on the partner's website you are dealing with them, under their privacy policy, not ours. We have no visibility of what you book or what you pay.

The same applies to tours and activities. Where we show things to do at a port of call, those come from Viator, a Tripadvisor company, and tapping one takes you to Viator's website to book. The link identifies Out There rather than you, so no personal information about you is sent to Viator when you tap it. From that point Viator's own privacy policy applies and they may set their own cookies.

We earn a commission on bookings made this way. Our affiliate disclosure explains which links earn us money, and why it does not change what you pay or the order things are shown in.

8. How long we keep it

DataKept for
Account and profileWhile your account is open. Deleted within 30 days of you closing it, except for the handle records below.
Relationship and travelling-with linksUntil either of you removes the link, either of you blocks the other, or either of you deletes your account. A travelling-with link also ends when either of you leaves the sailing.
Records of link requestsThe request, who asked, who replied, the answer and the dates. We keep these so that we can show a waiting request and enforce the 30 day wait before someone can ask again. A request nobody answers lapses after 30 days. A declined or removed request is deleted 30 days after the answer. They are also deleted when either of you blocks the other or deletes your account. An accepted link stays until either of you removes it. A record is never shown to anyone.
Handles of deleted accountsThe register keeps only a coded fingerprint of the handle, not the handle itself, so that nobody else can use it. The fingerprint holds no readable handle, no account number and no date, and cannot be turned back into the handle or linked to you. It is never deleted.
A handle you give upHeld for 30 days so that nobody else can take it and pass as you. During those 30 days only you can take it back. After that it is released and any member can take it.
Handle change recordEach time a handle is chosen, changed or retired because an account was deleted, we record the old and new handle, the internal account number and the date. For a change made by our staff, we also record which administrator made it and the reason. It cannot be edited. It is deleted 2 years after the change, except that it is kept for longer while a safety report about the member is open or under review. It is not removed when you delete your account, but it is deleted at the same 2 year point.
Messages12 months from when you sent them, then permanently deleted, whether or not the sailing or crew still exists. A message under an open safety report is kept until the report is closed, then follows the same 12-month clock. A message a moderator has hidden for breaking the rules is kept for as long as it stays hidden, which today means indefinitely, because it is the record of what was acted on.
Mention invitationsDeleted when you join that sailing or event chat, when either of you blocks the other, or when either of you deletes your account. Otherwise deleted after 30 days. The clean-up runs nightly, so a record can last a few hours longer than that. It also goes if the message it refers to is deleted.
Record of mentions sent2 days, or until either of you deletes your account if that is sooner. It holds who mentioned whom and when, with no message text.
Handle availability check counters3 hours. Each counter is a number against a coded fingerprint of a network address, or against an account number, for one minute or one hour. The clean-up runs hourly, so a counter can last a little longer than 3 hours.
Identity and intent preferencesUntil you withdraw consent, then deleted.
Identity verification resultUntil you withdraw your verification consent or delete your account, then deleted. Didit's own copy is kept under Didit's rules (section 5).
Staff image access logEach time a member of staff views a member's image, we record who, which image, when and why. See section 5.
Images you have reported, or that others have reportedKept as evidence while the report exists, and deleted when the report is deleted, 12 months after it was made. During that time the image file cannot be removed by the member who posted it, by a chat clean-up or by account deletion.
Staff image access log12 months, then deleted, unless the image is still held for a report that is open, under review or preserved, in which case it is kept for as long as that applies.
Photo rules confirmation recordsThe date and version of the wording you confirmed. Kept while your account is open, and for 12 months after you delete your account, then deleted automatically. During those 12 months they are linked only to an internal account number, not to your name or email address.
Photo upload recordsThese record when each upload happened and whether it passed, and for a chat photo the text of the message sent with it. They are not removed when you delete your account, and there is currently no automatic deletion date. We are reviewing this.
Photos matched by PhotoDNAHeld in a restricted store for review and for any preservation the law requires. There is currently no fixed end date, and this is under review.
Consent recordsWe keep these so we can show what was agreed and when. There is currently no automatic deletion date. They are not removed when you delete your account, and afterwards they are linked only to an internal account number, not to your name or email address. We are reviewing how long to keep them and will set a deletion schedule.
Safety reports and moderation decisions12 months from the report, then deleted, so repeat behaviour can be identified in that time.
Partner click recordsKept for commission reconciliation and tax records. There is currently no automatic deletion date. They are not removed when you delete your account, and afterwards they are linked only to an internal account number, not to your name or email address. We are reviewing how long to keep them and will set a deletion schedule.
Website analyticsAs set by Metricool's own retention policy.
App usage analytics (if turned on)12 months, the period PostHog guarantees on our current plan. PostHog may archive older data rather than delete it, so if you want yours removed, email hello@outtheretogether.com and we will delete it. Turning analytics off in Settings stops new information being sent; it does not delete what was already sent.
Meta Pixel advertising dataAs set by Meta's retention and account settings. We do not retain a separate identifiable copy of this Pixel data.
App events sent to Meta (if you agreed)Held by Meta under its own retention policy. They are not linked to your Out There account number, so we cannot look them up or delete them for you.
Record that your first sign-in was reported to MetaThe date it was reported, linked to your account's internal number, so it is never reported twice. Kept with your account record.
Your answer to the Meta questionAs other consent records, above.
Waitlist email addressUntil the app opens and we have told you, or until you ask to come off the list, whichever is first.

9. Your rights

Under UK data protection law you have the right to:

Ask us at hello@outtheretogether.com and we will respond within one month. There is no charge.

10. Deleting your account

You can delete your Out There account and the personal data attached to it at any time. There are two ways:

When you delete your account we remove your profile, your profile picture, your gallery photos and the photos you sent in chats (except an image that has been reported, which is kept as evidence until its report is deleted after 12 months), your sailing and crew memberships, your event replies, your verification result, your identity and intent preferences, and your address from our email provider Sender, within 30 days. Your one-to-one chats are deleted in full at the same time, since with your account gone there is no one left who needs to read them.

We also remove your relationship links, your travelling-with links and the records of your link requests. Your @handle stops showing on your profile. We keep only a coded fingerprint of it, which holds no readable handle, no account number and no date, so that nobody else can take it and pass as you. Our record of handle changes, which does hold the readable handle and your internal account number, is deleted 2 years after each change (longer only while a safety report about you is open or under review). We also remove any mention invitations and mention records that involve you.

Some records are kept longer, and we explain why in section 8. In short: messages you sent in a sailing or crew chat stay visible to the people you were talking to, though they are no longer linked to your profile, until they reach the 12-month cut-off in section 8 like any other message; records of consent and of clicks through to booking partners are kept with no automatic deletion date yet, and safety reports for 12 months. Three things are not cleared straight away. A record of each photo upload, including the text of the message sent with a chat photo, is kept. A record that you confirmed the photo rules, with its date and version, is kept for 12 months after you delete your account, then deleted automatically. And if you verified your identity, Didit keeps its own copy under its own rules (section 5).

11. Where your data is held

Our database and files are hosted by Supabase. Our website is hosted by GitHub Pages. Sightengine, which checks photos for nudity, may process them in any of its data centres, including outside the UK and the European Economic Area, under the safeguards described in section 5. Our PhotoDNA scanner is hosted by Hetzner in Germany, and Microsoft's PhotoDNA service, which receives hashes only, is in the UK. Our analytics provider, Metricool, is based in Spain. Our app analytics provider, PostHog, holds app usage analytics in the EU. When you consent to marketing cookies on the website, or agree to the Meta question in the app, Meta may process Pixel data and app event data in the UK, the European Economic Area, the United States and elsewhere.

Where personal data is transferred outside the UK, we rely on the UK International Data Transfer Agreement or the UK Addendum to the European Commission's standard contractual clauses, together with the adequacy decisions that apply to the country concerned.

12. Security

Access to your data is controlled at the database level, so members can only read the records they are entitled to see. Passwords are hashed and never stored in a readable form. Identity and intent preferences are held in a separate restricted schema. Supplier credentials and tracked partner links are held on our servers and are never exposed to the app. Someone browsing the app without an account can read sailing details and member counts, and nothing about any person.

No system is perfectly secure. If a breach occurs that is likely to put your rights at risk, we will tell you and the ICO without undue delay.

13. Age

Out There is for adults. You must be 18 or over to hold an account. We do not knowingly collect data about anyone under 18, and we will delete any account we find belongs to someone under that age. You can browse sailings as a guest without an age check, because a guest sees nothing about any member. Anything involving other people needs an account, and seeing who is on board needs your age verified.

14. Changes

If we change this policy we will update the date at the top. If a change materially affects how we use your data, we will tell you in the app or by email before it takes effect.

15. Contact and complaints

Email hello@outtheretogether.com.

If you are unhappy with how we have handled your data you can complain to the Information Commissioner's Office at ico.org.uk/make-a-complaint, by calling 0303 123 1113, or by writing to Information Commissioner's Office, Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF. We would rather you came to us first so we can put it right.