Privacy notice
What Trip Caddie holds about you, why, and what you can do about it. Written from the code, so it describes what actually happens.
Last updated 2 September 2026
If somebody added you to a golf trip and you never signed up
You are in the right place, and you have not agreed to anything. Skip to people who never signed up. It explains what the organiser can see and how to get your details removed without going through them.
1.Who is responsible for your data
Trip Caddie is operated by LuxVibeWeb Limited, trading as Trip Caddie. Private company limited by shares, registered in England and Wales.
| Detail | Value |
|---|---|
| Company number | 16954810 |
| Registered address | 12 Beech Road, Epsom KT17 4NH |
| Post for privacy requests | 12 Beech Road, Epsom KT17 4NH |
| Email for privacy requests | privacy@luxvibeweb.co.uk |
| ICO registration | ZC211919 |
Detail
Company number
Value
16954810
Detail
Registered address
Value
12 Beech Road, Epsom KT17 4NH
Detail
Post for privacy requests
Value
12 Beech Road, Epsom KT17 4NH
Detail
Email for privacy requests
Value
privacy@luxvibeweb.co.uk
Detail
ICO registration
Value
ZC211919
We are the data controller for everything described here. That includes data about people on a trip, not only account holders, because we decide what the service records, we send reminder emails on our own schedule, and we run our own referral programme. Those are decisions we make, not instructions we follow.
If you organise trips for a club, society or business rather than for friends, you are likely to be a controller for your own group's data as well. That means the organiser answers to their members for how they use the trip, and we answer for the platform. See organisers.
2.What we collect, and where it comes from
| What | Fields | Who provides it | Optional |
|---|---|---|---|
| Account details | Email address, display name, and optionally a photo, phone number, short bio and location. | You, when you create an account and edit your profile. | Everything except the email address. |
| Golfer profile | Handicap, home postcode and approximate coordinates, how far you will travel, preferred days and times, notification preferences. | You, on your profile page. | All of it. |
| People on a trip | Name, and optionally email, mobile, handicap, team, where they travel from, room preference, dietary notes, RSVP status and payment status. | The organiser types this in when they build the trip. The person can then correct their own record from their private link. | Everything except the name. |
| An organiser's address book | Name, email, mobile, usual handicap, usual role, and free-text notes. | The organiser, so they do not retype the same group every year. | Everything except the name. |
| Trip content | Trip name, dates, location, itinerary, teams, rules, FAQs, cover photo, costs, payments recorded against people, scores and match results. | The organiser, and players entering their own scores. | Most of it. |
| Chat and uploads | Messages posted in a trip chat, and any image attached to one. Profile and trip photos. | Whoever posts them. | Yes, chat can be switched off per trip. |
| Email records | Recipient address and name, subject, when it was sent, and whether it succeeded. Not the body. | Generated when the service sends an email. | No, this is how repeat sends are prevented. |
| Usage events | Named events such as an invite being sent or a private link being opened, with the trip and participant id, and a timestamp. | Generated as the service is used. | No. It records no IP address, no device details and no browser details. |
| Referrals | Your share code, who signed up from it, whether they went on to run a trip, and a count of how many browsers opened your link. | Generated when a share link is used. | The link is optional. Counting opens needs your consent. |
What
Account details
Fields
Email address, display name, and optionally a photo, phone number, short bio and location.
Who provides it
You, when you create an account and edit your profile.
Optional
Everything except the email address.
What
Golfer profile
Fields
Handicap, home postcode and approximate coordinates, how far you will travel, preferred days and times, notification preferences.
Who provides it
You, on your profile page.
Optional
All of it.
What
People on a trip
Fields
Name, and optionally email, mobile, handicap, team, where they travel from, room preference, dietary notes, RSVP status and payment status.
Who provides it
The organiser types this in when they build the trip. The person can then correct their own record from their private link.
Optional
Everything except the name.
What
An organiser's address book
Fields
Name, email, mobile, usual handicap, usual role, and free-text notes.
Who provides it
The organiser, so they do not retype the same group every year.
Optional
Everything except the name.
What
Trip content
Fields
Trip name, dates, location, itinerary, teams, rules, FAQs, cover photo, costs, payments recorded against people, scores and match results.
Who provides it
The organiser, and players entering their own scores.
Optional
Most of it.
What
Chat and uploads
Fields
Messages posted in a trip chat, and any image attached to one. Profile and trip photos.
Who provides it
Whoever posts them.
Optional
Yes, chat can be switched off per trip.
What
Email records
Fields
Recipient address and name, subject, when it was sent, and whether it succeeded. Not the body.
Who provides it
Generated when the service sends an email.
Optional
No, this is how repeat sends are prevented.
What
Usage events
Fields
Named events such as an invite being sent or a private link being opened, with the trip and participant id, and a timestamp.
Who provides it
Generated as the service is used.
Optional
No. It records no IP address, no device details and no browser details.
What
Referrals
Fields
Your share code, who signed up from it, whether they went on to run a trip, and a count of how many browsers opened your link.
Who provides it
Generated when a share link is used.
Optional
The link is optional. Counting opens needs your consent.
We do not collect your IP address, device type, browser or screen size, and we run no advertising or third-party tracking scripts. There are none in the code.
3.Dietary notes, and why they need extra care
A trip has an optional dietary notes field. Free text about food is capable of revealing health information, such as an allergy or coeliac disease, and religious belief, such as halal or kosher. UK GDPR treats both as special category data, which needs a specific condition on top of an ordinary lawful basis.
Dietary notes on a trip
- Why it is sensitive
- Free text about food. An allergy or coeliac disease is health data. Halal or kosher reveals religious belief.
- Who enters it
- The person themselves, from their own private link.
- Our condition for holding it
- Article 9(2)(a), explicit consent, given by the person when they choose to type it. The field is optional and labelled so, and the form says what it is used for.
Notes in an organiser's address book
- Why it is sensitive
- A free-text field an organiser may use for dietary needs, which is health data.
- Who enters it
- The organiser, about somebody else.
- Our condition for holding it
- No sound Article 9 condition. We cannot obtain explicit consent from a person who does not know the record exists, and no other condition fits.
You never have to fill the dietary field in. If you have already, clear it from your private trip link and it is gone. If you would rather the organiser knew by another route entirely, tell them directly and leave the field empty.
Organisers: the notes field in your address book is not the place for somebody's allergies. Ask them to enter it themselves on the trip, where they are the one deciding to share it.
4.Why we use it, and our legal basis
| Purpose | Legal basis | Detail |
|---|---|---|
| Running your account and showing you your trips | Contract | Necessary to provide the service you signed up for. |
| Letting an organiser build a trip and manage who is on it | Contract, with the organiser | For the people on that trip who have no account, our basis is legitimate interests: the interest is enabling somebody to organise a group trip, which cannot be done without recording who is going. Weighed against the fact that a participant supplies little data, can correct it themselves, and can ask us to remove it directly. |
| Sending invites, RSVP reminders, payment reminders and the end-of-trip recap | Legitimate interests | The interest is that a trip only works if the group is told about it, chased for an answer and reminded to pay. Capped in code to a small number of messages per trip, and switchable off per trip and per person. |
| Dietary notes | Explicit consent, Article 9(2)(a) | Optional, entered by the person themselves, and used only to tell the organiser about catering. |
| Counting how the service is used | Legitimate interests | The interest is knowing whether invites are reaching people, so the product can be fixed when they are not. Records no IP address, no device and no browser details. |
| Referral measurement on your device | Consent | Asked before anything is stored, and refusable without losing anything else. |
| Keeping accounts and trips secure, and investigating misuse | Legitimate interests | The interest is preventing somebody reaching a trip they were not invited to. |
| Meeting our legal obligations | Legal obligation | For example responding to a valid data subject request. |
Purpose
Running your account and showing you your trips
Legal basis
Contract
Detail
Necessary to provide the service you signed up for.
Purpose
Letting an organiser build a trip and manage who is on it
Legal basis
Contract, with the organiser
Detail
For the people on that trip who have no account, our basis is legitimate interests: the interest is enabling somebody to organise a group trip, which cannot be done without recording who is going. Weighed against the fact that a participant supplies little data, can correct it themselves, and can ask us to remove it directly.
Purpose
Sending invites, RSVP reminders, payment reminders and the end-of-trip recap
Legal basis
Legitimate interests
Detail
The interest is that a trip only works if the group is told about it, chased for an answer and reminded to pay. Capped in code to a small number of messages per trip, and switchable off per trip and per person.
Purpose
Dietary notes
Legal basis
Explicit consent, Article 9(2)(a)
Detail
Optional, entered by the person themselves, and used only to tell the organiser about catering.
Purpose
Counting how the service is used
Legal basis
Legitimate interests
Detail
The interest is knowing whether invites are reaching people, so the product can be fixed when they are not. Records no IP address, no device and no browser details.
Purpose
Referral measurement on your device
Legal basis
Consent
Detail
Asked before anything is stored, and refusable without losing anything else.
Purpose
Keeping accounts and trips secure, and investigating misuse
Legal basis
Legitimate interests
Detail
The interest is preventing somebody reaching a trip they were not invited to.
Purpose
Meeting our legal obligations
Legal basis
Legal obligation
Detail
For example responding to a valid data subject request.
6.Data leaving the UK
Some of the services above operate outside the UK, so your data is transferred there. The safeguard we rely on is the UK International Data Transfer Addendum to the EU Standard Contractual Clauses, or the UK Addendum where the provider offers it.
[TO CONFIRM: confirm the transfer mechanism actually in place with each provider named above]
7.How long we keep it
Told plainly: there is no automatic deletion yet
Trip Caddie has no scheduled job that deletes old data. We are not going to promise you a retention period that nothing enforces, so the table below is current practice, not a policy we have built. Deleting your account works immediately, and so does an organiser deleting a trip.
| What | How long we actually keep it |
|---|---|
| Your account and profile | Kept until you delete your account. Deleting it from the Account tab removes it immediately. |
| Trips and everyone on them | Kept until the organiser deletes the trip. There is no automatic deletion after a trip finishes.Not automatically deleted. Ask us and we will remove it. |
| An organiser's address book | Kept until the organiser deletes the entry, or deletes their account. |
| Email send records | Kept indefinitely at present. They are what stops the same reminder going out twice.Not automatically deleted. Ask us and we will remove it. |
| Usage events and referral records | Kept indefinitely at present.Not automatically deleted. Ask us and we will remove it. |
| In-app notifications | Kept indefinitely at present, read or unread.Not automatically deleted. Ask us and we will remove it. |
What
Your account and profile
How long we actually keep it
Kept until you delete your account. Deleting it from the Account tab removes it immediately.
What
Trips and everyone on them
How long we actually keep it
Kept until the organiser deletes the trip. There is no automatic deletion after a trip finishes.Not automatically deleted. Ask us and we will remove it.
What
An organiser's address book
How long we actually keep it
Kept until the organiser deletes the entry, or deletes their account.
What
Email send records
How long we actually keep it
Kept indefinitely at present. They are what stops the same reminder going out twice.Not automatically deleted. Ask us and we will remove it.
What
Usage events and referral records
How long we actually keep it
Kept indefinitely at present.Not automatically deleted. Ask us and we will remove it.
What
In-app notifications
How long we actually keep it
Kept indefinitely at present, read or unread.Not automatically deleted. Ask us and we will remove it.
8.Your rights
| Right | What it means here |
|---|---|
| Get a copy of your data | We will send what we hold about you. |
| Correct it | Your profile is editable directly. For a trip record, your private link lets you fix your own details. |
| Delete it | Delete your account from the Account tab and it goes immediately. For a trip record you did not create, write to us and we will remove it, or tell you plainly why we cannot. |
| Restrict how we use it | You can ask us to stop using it while a complaint is looked at. |
| Object to us using it | Where our basis is legitimate interests, you can object and we must stop unless we can show a compelling reason not to. |
| Take it elsewhere | For data you gave us under contract or consent, in a machine-readable form. |
| Withdraw consent | For dietary notes, clear the field. For referral measurement, change your choice on the Cookies and storage page. Withdrawing is as easy as giving it, and does not affect anything done beforehand. |
| Not be subject to automated decisions | We make none. The AI suggestions are text an organiser reads and chooses to act on. Nothing is decided about anybody automatically. |
Right
Get a copy of your data
What it means here
We will send what we hold about you.
Right
Correct it
What it means here
Your profile is editable directly. For a trip record, your private link lets you fix your own details.
Right
Delete it
What it means here
Delete your account from the Account tab and it goes immediately. For a trip record you did not create, write to us and we will remove it, or tell you plainly why we cannot.
Right
Restrict how we use it
What it means here
You can ask us to stop using it while a complaint is looked at.
Right
Object to us using it
What it means here
Where our basis is legitimate interests, you can object and we must stop unless we can show a compelling reason not to.
Right
Take it elsewhere
What it means here
For data you gave us under contract or consent, in a machine-readable form.
Right
Withdraw consent
What it means here
For dietary notes, clear the field. For referral measurement, change your choice on the Cookies and storage page. Withdrawing is as easy as giving it, and does not affect anything done beforehand.
Right
Not be subject to automated decisions
What it means here
We make none. The AI suggestions are text an organiser reads and chooses to act on. Nothing is decided about anybody automatically.
Write to privacy@luxvibeweb.co.uk and we will respond within one month. There is no charge. We may ask you to confirm who you are, but only enough to be sure we are not handing your data to somebody else.
9.People who never signed up
You did not agree to anything, and you do not need an account to fix this
Somebody organising a golf trip typed your details into Trip Caddie. That is how the service works: only the organiser needs an account, and everyone else gets a private link. It also means your data arrived here without you being asked.
What is held about you
Your name, and whichever of these the organiser filled in: email, mobile, handicap, which team you are on, where you travel from, room preference, dietary notes, whether you have said yes, and what you have paid. Plus your scores if the trip is being scored.
What the organiser can see
All of it, including your email, mobile and dietary notes. They can also see when you last opened your private link. They cannot see anything about your device, your location, or any other trip you are on.
What other players can see
Your name, team, handicap, scores and whether you are coming. Not your email, mobile or dietary notes.
What you can do
- Correct your own details. Open your private link and edit them. You do not need an account and you do not need to ask the organiser.
- Say no to the trip. Decline from your link and the reminders stop.
- Get your details removed. Email privacy@luxvibeweb.co.uk with the trip name. We will remove your record and we will not tell the organiser it was you who asked, unless removing you from a trip they run makes that obvious, which it usually will. If you would rather they did not know, say so and we will tell you what we can do.
- Object to us emailing you. Tell us and we will stop, for that trip or for good.
- Ask what we hold. Same address, and we will send it.
Removing your record from a trip deletes your details. It does not delete the payment history the organiser recorded against you, because that is their financial record of money they handled, and deleting it would leave their books wrong. Tell us if that is a problem for you and we will look at it case by case.
10.If you organise trips
When you type somebody else's details in, you are responsible for having a reason to hold them. In practice that means telling your group that you use Trip Caddie, and not entering things they have not agreed to share, particularly anything about their health.
If you organise as a private individual for friends, UK GDPR mostly does not apply to you, because of the exemption for purely personal or household activity.
If you organise for a club, society, employer or as a business, that exemption almost certainly does not cover you. You would be a controller in your own right, with your own obligations to your members, and you would need your own privacy notice. We cannot give you legal advice on this and you should take your own.
11.Emails we send
Everything we send relates to a trip you are on: your invite, a reminder if you have not replied, a reminder if a payment is due, and the results once the trip finishes. Organisers also get a summary of who has paid and occasional prompts about a trip they have not finished setting up.
We send no newsletters, no product marketing and no promotional email to anybody.
Being honest about opting out
If you have an account, you control every category of email from the Alerts tab on your profile, and the code honours those settings.
If you do not have an account there is currently no unsubscribe link in the email itself. To stop them, decline the trip from your private link, ask the organiser, or email privacy@luxvibeweb.co.uk and we will suppress your address. We know a link in the email would be better and it is on the list to build.
12.Private links, and how to look after them
Your invite link contains a long random token. Anybody holding that link can see the trip and edit your record, which is what makes it work without a password. Treat it like a key:
- Do not post it in a public group, on social media or anywhere it could be indexed.
- It is fine to keep it in your own messages, which is where it arrived.
- If you think it has gone astray, ask the organiser to reset your link. The old one stops working straight away.
- The token is never written into our usage records and is never sent to any third party.
A trip can also have a group password on top of the links. Organisers should share that separately from the link, not in the same message.
13.Who can reach a trip page
Two pages show a trip without anybody signing in. This is deliberate, because the whole point is that players do not need an account, but it is worth understanding exactly how open it is.
| Page | Who can open it | What it shows |
|---|---|---|
| The attendee page | Anyone with the link. If the organiser has set a group password, anyone with the link and the password. | The trip, the itinerary, the teams and the names, handicaps and scores of the people on it. Emails, mobiles and dietary notes are not shown to other players. |
| The public trip page | Anyone with the link. There is no password option on this one. | The trip, the itinerary, the organiser, and the team lists with player names. |
Page
The attendee page
Who can open it
Anyone with the link. If the organiser has set a group password, anyone with the link and the password.
What it shows
The trip, the itinerary, the teams and the names, handicaps and scores of the people on it. Emails, mobiles and dietary notes are not shown to other players.
Page
The public trip page
Who can open it
Anyone with the link. There is no password option on this one.
What it shows
The trip, the itinerary, the organiser, and the team lists with player names.
The link is the control. Anyone who has it can look, and anyone can pass it on. That is how a link works, and it is why we ask organisers not to post one publicly.
These pages are not in search engines
Trip pages are excluded from search indexes: they send a no-index instruction, our robots file disallows them, and our sitemap does not list them. So a trip is reachable by anyone holding the link, but it will not turn up when somebody searches a player's name.
If an organiser wants a trip properly private rather than just unlisted, they should turn on the group password in Trip Settings.
14.How we protect it
What is actually in place:
- Sign-in is handled by the platform, not by us. We never see or store your password.
- Trip data is readable only by people on that trip: an account with access, or somebody holding a valid private link.
- Private links use a random 32-character token that is checked on the server every time, never in the browser.
- A trip can have a group password on top of the private links. It is stored as a salted hash, never in plain text.
- Withdrawing somebody from a trip clears their token, so their old link stops working.
- Anything that can hand out access, change money records or send email runs on the server, where the browser cannot reach it.
- Traffic to the site uses HTTPS.
What we do not claim
Plenty of privacy notices imply more than is true. To be straight with you:
- We hold no security certification. We are not ISO 27001 certified and have not completed a SOC 2 audit.
- We have not had an independent penetration test.
- We do not encrypt individual database fields beyond what the platform provides at rest and in transit.
- Images you upload are served from public URLs. Anyone given the URL can open the image without signing in.
15.Age
Trip Caddie is for people aged 16 and over. We do not ask your age and we have no way to check it, so this is a condition of use rather than something the site enforces. We do not knowingly hold data about children.
An organiser can add anyone to a trip, including someone under 16. If you are a parent or guardian and your child's details are on a trip, email privacy@luxvibeweb.co.uk and we will remove them.
16.Storage on your device
We store a small number of things in your browser, and one of them needs your permission. The cookies and storage page lists every key by name and is also where you change your choice.
17.Complaining
Please raise it with us first at privacy@luxvibeweb.co.uk. If we do not sort it out, you can complain to the Information Commissioner's Office, who regulate this in the UK.
| Route | Detail |
|---|---|
| Online | https://ico.org.uk/make-a-complaint/ |
| Phone | 0303 123 1113 |
| Post | Information Commissioner's Office, Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF |
Route
Online
Route
Phone
Detail
0303 123 1113
Route
Post
Detail
Information Commissioner's Office, Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF
Complaining to the ICO does not cost anything and you do not need to go through us first, though it usually gets sorted faster if you do.
18.Changes to this notice
If we start doing something this notice does not cover, we will update it and change the date at the top. If the change affects something you consented to, we will ask you again rather than assume the old answer still applies.
