Privacy Policy
Effective date: 7 October 2026
Last updated: 7 October 2026
Version: 2026-10-07
Tuners Cafe (“we”, “us”, “our”) operates the Cruise platform, available at tunerscafe.com and through the Cruise mobile web application (“the App”). This policy explains what personal data we collect, why we collect it, who we share it with, and your rights under UK data protection law.
During account setup you’ll be asked to confirm you’ve read this policy before you can use the App. See also our Cookie Policy for details on the third-party network requests the App makes.
If you have questions, contact us at cruise@tuners.cafe.
1. Who is the Data Controller?
Tuners Cafe
United Kingdom
Contact: cruise@tuners.cafe
2. What Data We Collect and Why
2.1 Account and Identity
When you register or sign in, we collect:
| Data | Source | Purpose |
|---|---|---|
| Display name | You / Google or Facebook sign-in | Identify you within the App |
| Email address | You / Google or Facebook sign-in | Account authentication and communications |
| Phone number | You (optional) | Alternative authentication method |
| Email / phone verification status | Authentication system | Confirm account ownership |
| Date of birth | You | Confirm you meet our minimum age requirement (Section 8) |
Legal basis: Performance of contract (account creation and management); legal obligation (age verification).
2.2 Vehicle Data
When you add a vehicle to your garage, we collect:
| Data | Source | Purpose |
|---|---|---|
| UK registration mark (number plate) | You | Identify the vehicle |
| Make, model, variant | You / DVLA | Populate your garage with accurate vehicle details |
| Tax status and due date | DVLA | Informational display |
| MOT status and expiry date | DVLA | Informational display |
| Year of manufacture | DVLA | Display and categorisation |
| Engine capacity and fuel type | DVLA | Display and categorisation |
| CO₂ emissions and Euro status | DVLA | Display and categorisation |
| Colour | You / DVLA | Display and discrepancy flags |
| Date of last V5C issue | DVLA | Display |
We use your registration mark to query the DVLA Vehicle Enquiry Service (a UK government API). The full set of data returned by that query is stored against your vehicle record.
We also store your ownership status (current owner, previous owner, aspiring owner, or future owner) so you can accurately represent your relationship with each vehicle.
Legal basis: Performance of contract (garage feature); legitimate interests (providing accurate vehicle information).
2.3 Location Data (Cruising Activity)
When you start a cruising session, the App records:
| Data | Source | Purpose |
|---|---|---|
| GPS latitude and longitude | Your device | Log your cruising activity against a vehicle |
| Vehicle being driven | You | Link activity to the correct garage entry |
| Timestamp | System | Record when the activity occurred |
Location data is stored permanently in your activity history. You can delete your account to request removal.
Legal basis: Legitimate interests (providing the cruising activity feature); consent (you explicitly start a session).
2.4 Events
When you propose or attend an event, we collect:
| Data | Source | Purpose |
|---|---|---|
| Your profile ID | Account | Associate you with the event as organiser or attendee |
| Event name, location, dates | You | Create and display the event |
| Event details URL | You | Research and populate event information automatically |
| Event poster image | You | Read the poster to populate event information automatically |
| Event picture | You | Display the event on the events feed |
| Attendee list | App interactions | Show who is attending |
When you provide an event URL, we fetch the page content from that URL to extract event details automatically (see Section 4 — OpenAI).
When you upload an event poster, we read the text on the poster to extract event details automatically, and may create a version of the poster artwork without text to use as the event picture (see Section 4 — OpenAI). The poster is sent for processing with its photo metadata removed. Images you upload, and the metadata they contain, are covered in Section 2.11.
Legal basis: Performance of contract (event feature); legitimate interests (automating event data entry).
2.5 Chats and Chat Messages
When you join a chat and send messages, we collect:
| Data | Source | Purpose |
|---|---|---|
| Your profile ID and display name | Account | Identify message author |
| Message content | You | Display messages to chat members |
| Censored version of message content | Automated | Store a safe version where profanity has been masked |
| Profanity score | Automated | Enforce community standards |
| Profanity violation tally | Automated | Track repeat violations; trigger moderation actions |
Messages are analysed automatically for profanity. If a message contains profanity, both the original and a censored version are stored. Your violation count is tracked on your profile; repeated violations may trigger automatic suspension from chat.
Legal basis: Performance of contract (messaging feature); legitimate interests (maintaining community safety).
2.6 Subscription and Billing
If you subscribe to a paid plan:
| Data | Source | Purpose |
|---|---|---|
| Email address | Account | Stripe customer creation |
| Stripe customer ID | Stripe | Link your account to billing |
| Stripe subscription ID | Stripe | Manage your subscription |
| Subscription plan, status, and billing cycle | Stripe | Display your current plan |
| Billing period start and end dates | Stripe | Show when your plan renews |
We do not store your payment card details. All payment processing is handled directly by Stripe, which acts as a data processor under its own compliance frameworks.
Legal basis: Performance of contract (subscription management).
2.7 Friend Invitations and Connections
When you invite someone to connect:
| Data | Source | Purpose |
|---|---|---|
| Invitee email address or phone number | You | Deliver the invitation |
| Invitation token and expiry | System | Validate the invitation |
| Connection record | App interaction | Track accepted connections |
Legal basis: Legitimate interests (social connectivity feature).
2.8 Kudos (Reputation System)
We maintain a reputation score for your account. Each Kudos transaction records:
| Data | Source | Purpose |
|---|---|---|
| Points awarded or revoked | System / admin | Your reputation history |
| Reason for award | System | Explain why Kudos were given |
| Timestamp | System | Audit trail |
Legal basis: Legitimate interests (community reputation and engagement).
2.9 Notifications
We store in-app notifications triggered by platform activity (e.g., someone accepted your invitation, you received Kudos). These are tied to your profile and retained until dismissed or your account is deleted.
Legal basis: Performance of contract (in-app notification delivery).
2.10 Local Storage (Your Device)
The App stores the following data locally on your device:
| Key | Data | Purpose |
|---|---|---|
emailForSignIn |
Your email address | Temporarily held during email sign-in flow; cleared after sign-in |
cruise:defaultVehicleId |
Your last-selected vehicle ID | Restore your garage context between sessions |
| Upgrade banner dismissed | A flag (true/false) | Remember that you dismissed the upgrade prompt |
| Notification and install prompts | When you dismissed them | Avoid asking again too soon (up to 30 days) |
cruise:analyticsOptOut |
Whether you turned usage statistics off | Keep analytics off on this device |
cruise:visitCount |
How many times the App has been opened on this device | Wait until your second visit before suggesting adding Cruise to your home screen |
cruise:gettingStartedPendingSteps |
Which getting started steps were still to do | Count a step as completed only once, for the usage statistics in Section 2.14 |
This data lives only on your device and is not transmitted to our servers independently.
2.11 Images You Upload
When you upload or take a photo in the App (for example an event poster or an event picture), we collect:
| Data | Source | Purpose |
|---|---|---|
| The image | You | Display it in the App and, for posters, read event details from it |
| Date and time the photo was taken | Photo metadata (EXIF) | Associate the image with events and activity on the platform |
| GPS location where the photo was taken | Photo metadata (EXIF) | Associate the image with events and locations on the platform |
| Camera make and model | Photo metadata (EXIF) | Understand the image’s source and quality |
| Your profile ID and upload time | Account / System | Link the image to you and to what you uploaded it for |
Photos taken on phones and cameras often contain hidden metadata (known as EXIF), which can include the precise location where the photo was taken. We keep this metadata with the original image you upload.
- The original image and its metadata are private. They’re stored securely and are not shown to other members.
- Images shown publicly have metadata removed. Event pictures, thumbnails, and any image we send to a processor (see Section 4) are created without metadata, so other members can’t see where your photo was taken.
- You can choose not to share location. Turn off location tagging in your camera app before taking the photo, or upload a screenshot instead. Images without metadata work in exactly the same way.
The App resizes images on your device before uploading them to keep uploads fast, but it keeps the metadata described above.
Legal basis: Performance of contract (image features); legitimate interests (associating images with events and locations on the platform). You can object to this use at any time (see Section 6).
2.12 Push Notifications
If you allow notifications, we store a notification token for each device or browser you allow them on. The token is created by your browser’s push service. It doesn’t identify you outside Cruise, and we use it only to send notifications to that device.
| Data | Source | Purpose |
|---|---|---|
| Notification token for each device | Your browser, when you allow notifications | Send notifications to that device |
| Your notification settings (on/off, muted chats, chats you’ve opted into) | You | Only notify you about what you’ve asked for |
We send notifications for new messages in your private chats, and in any public chats you choose to turn them on for. A notification shows the sender’s name and a short preview of the message, with any bad language hidden. You’ll see the sender’s real name only if they’re your friend, otherwise their Cruise pseudonym. Nothing else from your account is included.
You can turn notifications off at any time in your Profile, mute any chat, or block notifications in your browser or phone settings. When a token stops working, for example because you’ve blocked notifications or cleared your browser data, we delete it.
Legal basis: Consent. We only ask for permission on your device after you’ve used chats, never when you sign in, and you can withdraw it at any time.
2.13 Activity Emails
We record when you last used the App. If you haven’t visited for a while, we may email you at most once a week with a summary of what you’ve missed: unread messages in your chats, upcoming events in your region and your Kudos balance. We don’t send one if there’s nothing new. We keep a record of each email we send, and whether you came back afterwards, so we can tell whether these emails are useful.
| Data | Source | Purpose |
|---|---|---|
| When you last used the App | System | Decide whether to send you an activity email |
| Activity emails sent to you, and whether you returned | System | Avoid sending too many, and measure whether they’re useful |
Every activity email has a link to stop them, and you can turn them off in your Profile. Turning them off doesn’t affect emails you need to use your account, such as sign-in links.
Legal basis: Legitimate interests (keeping members informed about activity in their own chats and region), with an easy opt-out in every email.
2.14 Usage Analytics
We use Google Analytics for Firebase to understand how the App is used, so we can see which features are useful and fix what isn’t working. It records:
| Data | Source | Purpose |
|---|---|---|
| The screens you visit in the App, and when | Your browser | See which features are used |
| How you respond to prompts in the App: whether an upgrade offer was shown, opened or closed (and which feature it was for), whether you allowed notifications or added Cruise to your home screen when asked, and which getting started steps you viewed or completed | Your browser | Improve these prompts and the getting started steps |
| A random ID stored in a cookie on your device | Google Analytics | Count returning visits without knowing who you are |
| Type of device, operating system and browser | Your browser | Make sure the App works on the devices people use |
| Approximate location (country and city) | Worked out by Google from your IP address, which isn’t stored | Understand where members are |
We don’t link analytics to your Cruise account. We don’t send your name, email address or messages to Google Analytics, and we don’t use it for advertising. The records of how you respond to prompts contain no message content and no personal details, only which prompt or step it was and what you chose.
You can turn analytics off at any time in your Profile (Share usage statistics from this device). It’s switched off for that device and browser, so turn it off on each device you use.
Legal basis: Legitimate interests (improving the App), relying on the exemption for cookies used only to produce statistics under the Data (Use and Access) Act 2025, with an easy way to turn it off.
2.15 How You Use the App
For each day you use the App while signed in, we keep a short record of that day: that you visited, whether you took part (for example by sending a message, reacting, giving Kudos, adding a vehicle, suggesting or saving an event, or inviting a friend), and how many of each of those things you did. It doesn’t include what you wrote, which chats or events were involved, or where you were.
| Data | Source | Purpose |
|---|---|---|
| The days you used the App, and when you were first and last active that day | System | Count how many members use Cruise each day, week and month |
| Whether you took part that day, and how many of each kind of action you took | System | Understand which features members use and how well we keep new members, so we can improve Cruise |
These records are kept by us, linked to your account, and are separate from the usage analytics in Section 2.14. We only use them in totals across members, never to single you out, and we delete each day’s record after 13 months.
Legal basis: Legitimate interests (understanding how members use Cruise so we can improve it).
3. Data We Do Not Collect
- Payment card details — handled exclusively by Stripe
- IP addresses — not logged or stored by our application. Google Analytics uses your IP address to estimate your country and city, then discards it (see Section 2.14)
- Device fingerprints — not collected. Google Analytics stores a random ID in a cookie, which you can turn off (see Section 2.14)
- Device model — not collected by our application. Google Analytics records the type of device, operating system and browser (see Section 2.14). If a photo you upload contains the make and model of the camera that took it, we keep that with the image (see Section 2.11)
- Advertising identifiers — not collected
- Third-party tracking — we don’t use any advertising or cross-site tracking tools. Google Analytics is our only analytics tool (see Section 2.14)
4. Data Processors
We use the following third parties to operate the App. Each acts as a data processor under a data processing agreement or applicable terms.
| Processor | Role | Data Shared | Location |
|---|---|---|---|
| Google Firebase | Cloud infrastructure (Authentication, database, storage, functions) | All platform data | UK / EU (europe-west2 region) |
| DVLA (Driver and Vehicle Licensing Agency) | UK vehicle registration lookup | Vehicle registration mark | United Kingdom |
| Google Places API | Address autocomplete for event locations | Address search queries | Google infrastructure |
| OpenAI | AI vehicle image generation; event URL and poster content analysis; event picture creation from posters | Vehicle make/model prompts; scraped event page content; event poster images (with photo metadata removed) | United States |
| Stripe | Payment processing and subscription management | Email address, subscription metadata | United States (EU Standard Contractual Clauses apply) |
| Google (Sign-In) | Google account authentication | Name, email address, profile photo | Google infrastructure |
| Meta (Facebook Login) | Facebook account authentication | Name, email address | Meta infrastructure |
| Google Fonts | Loads the App’s typeface | Your device’s IP address (via the font request) | Google infrastructure |
| Google reCAPTCHA | Bot protection for phone number sign-in | Device/browser signals used for bot scoring | Google infrastructure |
| Browser push services (Google for Chrome and Android, Apple for Safari and iOS, Mozilla for Firefox) | Deliver notifications to your device | Notification token; notification text (sender name and message preview) | The push service’s infrastructure, which may be outside the UK |
| Google Analytics for Firebase | Usage statistics for the App | Screens visited, how you respond to prompts in the App, a random device ID, device and browser type, approximate location (see Section 2.14) | Google infrastructure, which may be outside the UK |
| Twilio SendGrid | Sends emails, such as sign-in links and activity emails | Your email address; the email’s content | United States (UK International Data Transfer Agreement / Standard Contractual Clauses apply) |
Notes on international transfers
Where data is transferred outside the UK (to OpenAI, Stripe and SendGrid in the United States, and browser push services and Google Analytics where they’re outside the UK), we rely on UK International Data Transfer Agreements or Standard Contractual Clauses, as applicable under UK GDPR.
5. How Long We Keep Your Data
| Data type | Retention |
|---|---|
| Account and profile | Until you delete your account |
| Vehicle and ownership records | Until you delete your account |
| Activity (location) history | Until you delete your account |
| Chat messages | Until deleted by you or a moderator, or your account is deleted |
| Event records | Until you delete the event or your account |
| Uploaded images and their metadata | Until you delete the event or item they belong to, or your account |
| Uploaded images not used | 30 days after upload |
| Subscription records | 7 years (legal/tax compliance) |
| Invitation records | 90 days after expiry or acceptance |
| Notification tokens | Until you turn off notifications, the token stops working, or your account is deleted |
| When you last used the App | Until your account is deleted |
| Activity email records | 12 months after sending |
| Daily usage records | 13 months |
| Usage analytics | 14 months, kept by Google Analytics |
6. Your Rights
Under UK GDPR you have the right to:
- Access — request a copy of the personal data we hold about you
- Rectification — correct inaccurate data
- Erasure — request deletion of your data (“right to be forgotten”)
- Restriction — ask us to limit how we use your data while a dispute is resolved
- Data portability — receive your data in a structured, machine-readable format
- Object — object to processing based on legitimate interests
- Withdraw consent — where processing relies on consent, withdraw it at any time (e.g., location tracking)
These rights cover the images you upload and the metadata they contain (Section 2.11).
Erasure can be requested directly in the App (Profile → Delete my account), which queues your account for deletion — we aim to complete it within 30 days. For Access, Rectification, Restriction, Portability, or Object requests, contact cruise@tuners.cafe; we aim to respond within one month, as required by UK GDPR.
You also have the right to lodge a complaint with the Information Commissioner’s Office (ICO) at ico.org.uk.
7. Cookies
The App does not set advertising cookies. It uses three third-party Google services as part of normal operation, which are covered in full in our Cookie Policy:
- Google Fonts, to load the App’s typeface
- Google reCAPTCHA, to protect phone number sign-in from automated abuse — this can set a cookie in your browser
- Google Analytics for Firebase, for usage statistics (Section 2.14) — this sets cookies, which you can turn off in your Profile
We use browser localStorage (described in Section 2.10) solely for functional purposes to improve your experience.
8. Children
Cruise requires users to be at least 13 years old, and we ask for your date of birth when you set up your account to enforce this. If you are 13–17, we also require confirmation that a parent or legal guardian has given permission for you to use Cruise, in line with our Terms and Conditions.
We do not knowingly collect personal data from anyone under 13. If you believe we have inadvertently collected data from a child under 13, or that a user aged 13–17 is using Cruise without appropriate permission, please contact us at cruise@tuners.cafe so we can review the account.
9. Changes to This Policy
We may update this policy from time to time. When we do, we will update the “Last updated” date and version number at the top of this page. For material changes, we will ask you to re-confirm your agreement in the App before you can continue using it.
10. Related Documents
11. Contact Us
Tuners Cafe
cruise@tuners.cafe