Privacy Policy

How PlanHitch collects, uses and protects your personal data, who we share it with, and the rights you have over it.

Last updated 25 October 2026

Contents14 sections

1.Introduction

PlanHitch Ltd ("PlanHitch", "we", "us", or "our") is committed to protecting your privacy and personal data. This Privacy Policy explains how we collect, use, store, and share your personal information when you use our wedding planning platform and related services (the "Service").

PlanHitch Ltd is a company registered in Scotland, company number SC869251, with its registered office at Office 1325, 3 Fitzroy Place, 1/1, Sauchiehall Street, Glasgow Central, United Kingdom, G3 7RH. We comply with the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018.

Who is responsible for what

Data protection law distinguishes between the party that decides why and how personal data is used (the "controller") and the party that handles it on that party's instructions (the "processor"). Two different kinds of data pass through the Service, and they are not in the same position:

  • Your account, billing and technical data, and requests to join our founding couples programme: we are the controller. We decide what we collect to run your account, take payment, keep the Service secure, fix faults, and choose founding couples.
  • The wedding data you enter, including your guest list: you are the controller and we are your processor. You decide who goes on your guest list, what you record about them, and what you use it for. The same applies to what your guests enter on your RSVP form, your wedding website and your gift list. We hold and process that information on your instructions, so that you can. Where a wedding planner runs the account, the planner is the controller for the guest data they enter on a couple's behalf.

Because you are the controller of your guest data, two obligations sit with you rather than with us. You must have a lawful basis under data protection law for holding and sharing the information you enter about your guests, and you must make sure your guests know their details are being held in a wedding planning tool and who to approach about them. We do not tell you which lawful basis to rely on — that depends on your circumstances — but you do need one. If a guest asks you to remove them, you can delete them from your guest list at any time, and you can contact us if you would like help.

The terms on which we process guest data for you are set out in the Data Processing Terms in our Terms of Service, which you accept when you create an account. They cover what we may do with that data, the security we apply to it, the other companies we use, and what happens to it when you leave.

By using PlanHitch, you acknowledge that you have read and understood this Privacy Policy. If you have any questions, please contact us at contact@planhitch.com.

2.What We Collect

We collect the following categories of personal data:

Account Information

  • Name (forename and surname), email address, and password (stored securely using one-way hashing)
  • Account type (couple or wedding planner)
  • Subscription plan and billing history
  • Support correspondence, including the messages and tickets you send us and our replies
  • If you signed up through a link carrying another user's referral code — for example the "Plan your own" link on a couple's wedding website or RSVP page — a record that they referred you, with your email address, so that their referral can be counted and credited
  • How you found us when you signed up: the website or link that sent you (such as a search engine or a couple's wedding website), and, if you allowed analytics cookies, the first page you visited. We use it only to see which ways of finding PlanHitch work.

Founding Couples Requests

  • When you ask for a place in our founding couples programme: your names and email address, and, if you choose to give them, when and where your wedding is, roughly how many guests you expect, what you plan with now, and anything you write in your message.
  • Whether we approved or declined the request, when, and which member of staff decided. If we approved it, the code we issued you, and whether and when it was redeemed.

Wedding Data

  • Wedding details including partner names, wedding date, venue information, and budget
  • Guest lists including names, email addresses, phone numbers, dietary requirements, and RSVP responses
  • Invitation designs, table plans, vendor contacts, and timeline events
  • Photographs, videos, and other media uploaded to the Service. When a photo is uploaded we remove its hidden metadata: the location it was taken, the phone or camera that took it and any owner name. We keep only the date and time it was taken, so it can be shown in order. Video wishes are converted to a standard format on our servers, which removes their location and device metadata in the same way. Once the converted copies are stored, the original upload is deleted (unless a print order still needs it).
  • Your wedding website, including any gift list, and, if you use one, the domain you have chosen for it
  • Gift list claims: when a guest marks a gift as theirs or says they have given to a fund, their name, how many they are buying, and any email address and message they choose to add. The couple can see these. Other guests see only that the gift has been taken.

Voice Recordings and Planning Transcripts

  • The written transcript of what you dictate or type to the planning assistant, which we do keep. The audio itself never reaches us — your browser turns speech into text before anything is sent, as section 5 explains. The transcript is the record of what you told the assistant, and everything the assistant adds to your plan is derived from it.
  • Your conversation with the planner: the messages you send it, spoken or typed, including the sentence you write when you first set up; its replies; and a record of each change it made to your plan, so that you can see it and undo it.
  • Whatever you happen to say while recording. In practice this includes guests' names, family relationships, dietary needs and allergies, accessibility needs, and your reasons for seating people together or apart.

Health and Accessibility Information

  • Food allergies and how severe they are, other dietary requirements, and accessibility needs recorded against a named guest.
  • This reaches us in one of two ways: a guest enters it on an RSVP form themselves, or you tell the planning assistant about it and it is recorded against that guest. Section 6 explains how we treat this category of information.

Technical Data

  • IP address, browser type and version, operating system
  • Device information and screen resolution
  • Pages visited, time spent on pages, and navigation paths
  • Referring website addresses
  • Diagnostic data when something goes wrong, which includes the error itself and, if you have allowed analytics cookies, a recording of the on-screen actions leading up to it. This is handled by our error monitoring provider, Sentry; section 7 explains how.
  • When you register, ask for a founding place, or start typing in the homepage's “describe your wedding” box, a bot check run by Cloudflare Turnstile, which looks at information about your browser and connection to tell people from automated scripts. Section 7 explains more.

Payment Data

Payment card details are collected and processed directly by our payment processor, Stripe. PlanHitch does not store your full card number, expiry date, or CVV. We receive only a truncated card reference and transaction confirmations from Stripe. Please refer to Stripe's Privacy Policy for details on how they handle your payment data.

Printed Orders

When you order a printed photobook, thank-you cards, a seating chart poster or printed invitations, we collect the name, delivery address, phone number and email address you give at checkout, with the photos, words and design that go into it. We use them to have your order printed and delivered: the photos and words go into the print file, and the address and phone number go to our print partner, Prodigi, and its courier, who need a phone number to deliver. We rely on the contract with you (you asked us to make and send the order) as the legal basis.

Thank-you cards posted to your guests.If you choose to have cards posted straight to your guests, you give us each chosen guest's name and postal address (from your guest list, where you can add or correct them) and the message for their card, which may mention a gift they gave or whether they came. You supply your guests' details and decide who gets a card, so you are the controller of that data and we process it for you, as for the rest of your guest list. We send each guest's name, address and card to Prodigi, who prints the card and hands it to Royal Mail to post. We don't send Prodigi your guests' email addresses or phone numbers, and neither we nor Prodigi use their details for anything else or contact them. Please only include guests who would expect a thank-you card from you.

3.How We Use Your Data

We use your personal data for the following purposes:

  • Providing the Service: To create and manage your account, process your wedding planning data, send invitations, manage RSVPs, and deliver all features of the platform.
  • Processing payments: To manage your subscription, process payments through Stripe, and send invoices and receipts.
  • Communication: To send transactional emails (account verification, password resets, invitation deliveries, RSVP confirmations), service notifications, and important updates about the Service.
  • Emails to a couple's guests: Invitations, save-the-dates, RSVP reminders and confirmations, and wedding reminders are sent on the couple's instructions, about their wedding. Unless the couple has turned it off, which Premium and above allow, each one ends with a single plain line saying it was sent with PlanHitch, with no link to sign up. That line is the same for every guest. We do not use a guest's email address to send them our own marketing, and we do not add guests to any mailing list of ours.
  • Wedding Wrapped:From the wedding date we make a set of story cards from the couple's own planning: totals such as guests invited and who said yes, meal choices, dietary needs, suppliers booked, timeline moments, guest photos, video messages and gifts claimed, and the first dance if they recorded one. Guests are only ever counted, never named. Budget figures and guest photos are left out unless the couple switches them on, and a photo card uses only a photo the couple has featured. The cards stay private to the couple. Sharing them, as images or through a share link that search engines are asked not to index, is the couple's choice, and switching the link off stops it and its images working. We email the couple when the cards are ready and once more on their first anniversary.
  • Founding couples programme: To read your request, decide whether we can offer you a place, reply to you, and, if we offer one, issue the code that puts your account on Premium.
  • Referrals:To record when someone signs up through another user's referral link, so the referral can be credited to them. Users who refer others may appear in the referral leaderboard shown to other users, by first name and surname initial only.
  • AI and voice features: To turn your recordings into text, to read your planning transcripts and pull structured details out of them, to analyse supplier contracts, quotes and budgets you upload, to let the planner answer you and make the changes you ask for, and to suggest a colour palette from your style quiz answers. Section 5 sets out exactly what is sent, and to whom.
  • Improving the Service: To analyse usage patterns, diagnose technical issues, and develop new features. We use anonymised and aggregated data for analytics wherever possible.
  • Security: To detect and prevent fraud, abuse, and unauthorised access to the Service.
  • Legal compliance: To comply with applicable laws, regulations, and legal processes.

5.AI, Voice and Automated Processing

Several features of the Service work by sending your data to an AI model. This section sets out which features do that, what leaves our systems, and who receives it.

Text sent to Anthropic

We use Claude, an AI model provided by Anthropic, to power the features below. In each case the text described is sent to Anthropic's API, processed, and returned to us. No audio is ever sent to Anthropic.

  • The planner:When you talk or type to the planner, including the sentence you write when you first set up, we send your message, your recent conversation with it, a summary of your plan (your names, the date, region and expected guest numbers, budget totals, and the names of your suppliers and venue), and whatever parts of your plan it looks up to answer you. Those can include guests' names, relationships, RSVP replies, table assignments, notes, dietary needs, allergies and accessibility needs, as well as budget lines, the timeline, and suppliers.
  • The homepage preview:If you describe your wedding on the homepage before making an account, that sentence is sent so the guest numbers, place, date, budget and anything already booked can be picked out. We don't store it. If you then sign up, your browser keeps it in that tab so the planner can start from it.
  • Planning assistant:The full transcript of your planning session is sent so that structured details can be pulled out of it. Because the transcript is whatever you said, this will often include guests' names, their relationship to you, their allergies and dietary needs, their accessibility needs, and any reason you gave for keeping two people apart.
  • Contract analysis: The text of a supplier or venue contract you upload is extracted from the PDF and sent for analysis. This includes anything written in that contract, such as supplier names, addresses, prices, and payment dates. Long contracts are truncated to roughly the first 12,000 words before being sent.
  • Quote reading:If you upload a supplier's quote as a PDF to fill in the quote check, its text, up to roughly the first 3,000 words, is sent so that the category, total and what is included can be picked out. The PDF is read in memory and not stored. The verdict on the price itself comes from published price figures, not from the AI model.
  • Budget intelligence: Your budget line items are sent — the name and category of each item, its estimated and actual cost, the supplier name where you have given one, and the region of your wedding.
  • Style quiz: Your five style-quiz answers are sent so that a colour palette can be generated. These answers do not identify anyone.

We use Anthropic's API under its published commercial terms. Those terms provide that what we send through the API is not used to train Anthropic's models, and that Anthropic keeps it only for a limited period before deleting it. We have no separate arrangement with Anthropic that changes this. Anthropic is a United States company, and we have not asked it to keep this processing in a particular region, so the text may be processed in the United States or elsewhere that Anthropic operates. Section 11 explains how that transfer is covered.

Voice recordings and speech-to-text

When you dictate to the planning assistant, speech recognition is performed by your own web browser, using its built-in dictation engine. Your audio is never sent to PlanHitch: we receive only the text, and only once you have read it over and pressed send.

Depending on your browser and device, the browser's engine may recognise speech on the device itself or by using the browser vendor's own speech service (for example, Google's for Chrome or Apple's for Safari). That processing happens between your browser and its vendor under the vendor's privacy policy — it is the same mechanism as the dictation built into your keyboard or operating system, and PlanHitch is not a party to it. If you prefer not to use it, typing works identically.

The transcript itself, once you send it, is kept — see section 8.

Automated decision-making

The AI changes your wedding only when you ask it to. Details pulled out of a dictated transcript are held as suggestions until you confirm them, and you can reject any of them, correct who they refer to, or undo them after they have been applied. The planner makes the changes you ask it for straight away, shows you what it changed, and lets you undo its most recent turn. Contract analyses, quote readings, budget ratings, and colour palettes are presented to you as output to read; they do not change anything by themselves. We do not make decisions about you that produce legal or similarly significant effects by automated means alone.

6.Health and Other Special Category Data

Information about a person's allergies, and information about their accessibility needs, is data concerning health. Under the UK GDPR this is "special category" data and needs more protection than ordinary personal data. We want to be plain about the fact that the Service collects it.

It reaches us in two ways. A guest may enter their own allergies and dietary requirements when they complete an RSVP form. Alternatively, you may mention them to the planning assistant, in which case they are recorded against that guest once you confirm them, or ask the planner to record them, in which case it does so straight away.

Once this information is on your plan, the planner may read it when it answers you — for example, if you ask who has a nut allergy — and it is then sent to Anthropic as section 5 describes.

The second route matters, because the person the information is about is usually not you. When you tell us about a guest's nut allergy, you are giving us health data about a third party who has no account with us and may not know we hold it.

The condition we rely on

Special category data needs a condition under Article 9 of the UK GDPR on top of an ordinary legal basis. The condition relied on here is explicit consent, under Article 9(2)(a). How that consent is obtained depends on which of the two routes the information arrived by.

  • Where a guest fills in the RSVP form themselves: the guest gives that consent directly. The form explains that the information is used to plan the wedding menu, and the dietary and allergy fields are optional — a guest who would rather not say can leave them blank and still send their reply. Filling them in is the guest's own choice.
  • Where the couple or planner enters it: whether typed in or dictated to the planning assistant, the couple is responsible for having obtained the guest's explicit consent before recording it, and for being able to show they have it. We act on the couple's instructions here and are not in a position to ask the guest ourselves. If you record a guest's allergy, you are confirming that the guest is content for it to be held for that purpose.

A guest can withdraw that consent at any time, either by asking the couple to remove the information or by contacting us directly. Because the information is recorded against a guest by the couple, it is usually the couple who must tell their guests that it is being held — the same transparency duty described in section 1.

We use this information only to show it back to you and your collaborators for catering and accessibility planning, and to put it in a venue pack when you choose to make one (below). We do not use it to profile anyone, we do not share it with anyone outside the providers listed in section 7 except the people you send a venue pack to, and we do not use it for any purpose beyond the one it was given for.

Venue packs

You can make a venue pack: a document for your venue, caterer and other suppliers with the day's timings, your table plan, meal numbers, and each guest's allergies and dietary needs. You decide whether to make one, which version to make, and who gets it. You can download it as a PDF or spreadsheet, or make a link to it.

  • A pack never contains your guests' postal addresses, email addresses or phone numbers. The all-suppliers version leaves out guests' names, the table plan and every dietary and allergy detail.
  • A link shows the pack to anyone who has it, without signing in, until you switch it off or delete it, and it stops working by itself 30 days after the wedding. We count how many times it has been opened and when it was last opened, so you can see that it arrived; we do not record who opened it. Links are not listed by search engines.
  • PlanHitch does not send the pack to anyone: you send the file or the link yourself. We only host the link. Once a supplier has downloaded a copy, what happens to it is between you and them, so send it only to people who need it to look after your guests.

If you are a guest and you would like to know what we hold about you, or would like it removed, contact us at contact@planhitch.com and we will deal with your request directly.

7.Data Sharing and Sub-processors

We do not sell your personal data. We use the following companies to run the Service. Each receives only the data it needs for the purpose described, and each processes that data on our behalf:

  • Hetzner: Hosting. The Service, its database, and the self-hosted systems described after this list run on servers provided by Hetzner in Europe. Hetzner supplies the infrastructure and does not access your data in the ordinary course.
  • Cloudflare:File storage. The files you upload — photographs, videos, uploaded contracts, supplier listing images, and data exports — are held in Cloudflare's R2 object storage. We use storage with a European Union jurisdiction restriction, which guarantees the files themselves are stored in EU datacentres. Cloudflare is nonetheless a United States company, and section 11 explains how that transfer is covered.
  • Cloudflare Turnstile: Bot checks. Our registration form, our founding couples request form and the homepage's “describe your wedding” box use Turnstile to tell people from automated scripts. To do that, Cloudflare collects information about your browser, device and connection, including your IP address, when the form loads. We receive only a pass or fail. Cloudflare processes this under its own Turnstile privacy addendum.
  • Stripe: Payment processing. Stripe receives the personal and payment data necessary to take your subscription payments. Stripe is certified as a PCI Level 1 Service Provider.
  • Prodigi:Printing and delivery of printed photobooks, cards, posters and invitations. When you order, Prodigi (Prodigi Group Ltd, United Kingdom) receives the print file made from your photos, words or design, and the recipient's name, delivery address, phone number and email address, and passes the address and phone number to the courier that delivers it. For thank-you cards posted to your guests, it receives each chosen guest's name and postal address (no email or phone) and their card, and passes the name and address to Royal Mail. Prodigi keeps its copy of the print files for 30 days. It receives nothing about anyone who isn't on an order.
  • Anthropic: AI text processing for the planner, the planning assistant, contract analysis, quote reading, budget intelligence, and the style quiz. Section 5 sets out what is sent for each.
  • Resend: Email delivery. Resend receives recipient email addresses and the content of the transactional and campaign emails we send, including account verification, password resets, invitations, and RSVP confirmations. When someone asks for a founding place, Resend also delivers the details of the request to our staff.
  • Sentry:Error monitoring. When something goes wrong in the Service, a report describing the failure is sent to Sentry, as the paragraph after this list explains. We use Sentry's European Union data region, so these reports are stored in EU datacentres. Sentry is nonetheless a United States company, and section 11 explains how that transfer is covered.
  • Spotify: Music search and playlist import. When you search for a track or import a playlist, your search terms and the playlist address you supply are sent to Spotify. We connect to Spotify as an application rather than as you, so no Spotify account of yours is linked and Spotify does not learn who you are from us.
  • Law enforcement and legal authorities: We may disclose your data if required by law, court order, or governmental regulation, or if we believe disclosure is necessary to protect our rights, your safety, or the safety of others.

When you send a venue pack to your venue, caterer or other suppliers, they receive what is in it, at your choice and from you rather than from us; section 6 explains what a pack contains.

Some things that are commonly outsourced, we instead run ourselves on the Hetzner servers described above, so no third party is involved: rate limiting; and background and scheduled jobs such as reminders, anniversary emails, and data exports. (Dictation is different again — it runs in your own browser and never reaches our servers at all; section 5 explains.) When something goes wrong, Sentry receives a report describing the failure, which can include the page you were on and the data your browser was sending at the time, and, for a sample of visitors who have allowed analytics cookies, a replay of on-screen activity. We filter these reports before they are sent, removing email addresses, telephone numbers, card-length number sequences, passwords, and tokens, and we exclude our sign-in and registration pages entirely; filtering of this kind reduces the risk but cannot be guaranteed to catch everything.

Each of these providers publishes standard data processing terms for its customers, and those terms are incorporated into our contract with the provider when we sign up for the service. That is the basis on which Stripe, Anthropic, Resend, Cloudflare, Sentry, Spotify and Hetzner process data for us. We rely on each provider's published terms rather than on separately negotiated agreements. Section 11 explains how transfers outside the UK are covered.

If we add a new provider that handles personal data, or replace one of those above, we will update this list and this policy before the change takes effect.

On analytics, to be clear: we do not currently use any third-party web analytics service. There is no Google Analytics, and no equivalent product, running on the Service. Usage information described in section 2 is collected by us, and the error monitoring described above is the only third-party measurement in place. Should we introduce an analytics provider we will name it here and update this policy first.

Connecting ChatGPT or Claude:you can choose to connect your wedding to an AI assistant you use, such as ChatGPT (OpenAI) or Claude (Anthropic). You sign in to PlanHitch and pick one wedding; the assistant can then read and change that wedding on your behalf, with the same permissions you have. When it does, the parts of your plan it reads to answer you (for example guest names, dietary needs, budget figures and the running order), and any contract text you give it, go to that assistant's provider, which handles them under your own agreement with it, as part of your conversation. In this case the provider is acting for you, not for us. We don't receive your conversation, only the requests the assistant makes to your plan, and every change it makes is recorded in your wedding's activity. We keep a record of each connection (which assistant, which wedding, when it was last used) until you disconnect it in Settings, which stops access at once; the access keys themselves are stored only in scrambled (hashed) form. How connecting works.

Wedding websites:the fonts used on a couple's public wedding website are served by us rather than fetched from Google Fonts, so a guest visiting that website does not make a request to a third-party font service. If a couple shows their website at their own domain, we obtain a security certificate for that domain from a public certificate authority. Certificate authorities publish the domain names they certify in public logs, so the domain itself becomes publicly listed.

Gift lists:a gift list links to shops and payment pages run by other businesses. When a guest follows one of those links, they leave PlanHitch, and that business's own privacy policy applies to what they do there. We do not receive anything about what a guest buys or pays, only what they tell us when they mark a gift as theirs. So that a guest can undo their own claim, their browser keeps a small record of it in local storage on their device.

Founding couples requests are read by PlanHitch staff — the founder, and anyone else with administrator access to the Service. They are not shared outside PlanHitch, other than with the providers above that host our systems and deliver our email.

8.Data Retention

We retain your personal data for as long as necessary to fulfil the purposes for which it was collected, including:

  • Active accounts: Your data is retained for the duration of your account. Wedding data is retained for as long as your account is active.
  • Planning transcripts: Transcripts of your planning sessions are kept for the life of the wedding they belong to. They are not deleted when the details in them are applied to your plan, because they are the record the plan was built from. Deleting the wedding or your account deletes them.
  • Planner conversations: Your messages to the planner, its replies, and the record of what it changed are kept for the life of the wedding they belong to. Deleting the wedding or your account deletes them.
  • Printed orders: We keep the order itself (what was ordered, paid and refunded) as a record of the sale. The delivery address, phone number and email on it, and the guests' names, addresses and messages on cards posted to guests, are removed automatically two years after the order is delivered, cancelled or closed, or 30 days after a checkout that was never paid. The print files are kept for 30 days after they go to the printer, so that a damaged item can be reprinted. An invitation design you upload for printing is kept until you upload another or delete your wedding.
  • Gift list claims:Kept with the couple's wedding. A claim is deleted when the guest undoes it, when the couple removes the gift or fund it belongs to, or when the wedding is deleted.
  • Founding couples requests: We keep a request, with the record of our decision and of any code we issued, so that we know who has asked and what we said. Requests are then deleted automatically:
    • a request we have not yet answered is deleted 12 months after you last sent it;
    • a request we declined is deleted 6 months after we declined it;
    • a request we approved is deleted 12 months after the code we sent you expires or the free Premium year it gave you ends, whichever is later. At the same time we remove your names and email address from our record of that code.
    Deleting your PlanHitch account also deletes any founding request made with the same email address, and removes your names and email address from any code we issued for it. You can ask us to delete your request sooner at any time by writing to contact@planhitch.com, and we will.
  • Referral records:Kept while the account of the person who referred you exists. If you delete your own account, the record no longer points to it, but the email address you signed up with stays on the record until the referrer's account is deleted. You can ask us to remove it sooner.
  • Voice recordings: Not held at all — dictation audio never reaches our servers (section 5).
  • After account deletion: When you delete your account from your settings, your account and the weddings you solely own are removed from our live database immediately, as part of the same operation. Where a wedding has another owner, that wedding remains and only your access to it is removed. Financial records are retained where the law requires it, for example for at least 6 years for tax purposes.
  • Data exports: Export files you request are deleted 30 days after they are produced.
  • Sample weddings: A sample wedding added at sign-up is kept until you remove it in settings, or until your account is deleted.
  • Anonymised data: Anonymised or aggregated data that cannot be used to identify you may be retained indefinitely for analytical and statistical purposes.
  • Backups: We keep routine backups of our database so that we can recover from a failure. Copies of your data may therefore persist in those backups for up to 30 days after you delete it, after which they are overwritten and gone. We do not restore deleted accounts from backup except where we are recovering the whole service from an incident.
  • Uploaded files: Deleting your account also deletes the files belonging to it — photographs, videos, uploaded contracts, and any data exports you had produced. These are removed from our file storage as part of the same operation that removes your account, not left behind. Files belonging to a wedding that has another owner stay with that wedding.

9.Your Rights

Under the UK GDPR, you have the following rights in relation to your personal data:

  • Right of access: You have the right to request a copy of the personal data we hold about you. You can request a data export through your account settings.
  • Right to rectification: You have the right to request correction of inaccurate or incomplete personal data. You can update most of your information directly through your account.
  • Right to erasure ("right to be forgotten"): You have the right to request deletion of your personal data, subject to certain legal exceptions. You can delete your account through your settings, or contact us to request erasure.
  • Right to data portability: You have the right to receive your personal data in a structured, commonly used, and machine-readable format (such as JSON or CSV) and to transmit that data to another controller.
  • Right to restrict processing: You have the right to request that we restrict the processing of your personal data in certain circumstances.
  • Right to object: You have the right to object to the processing of your personal data where we rely on legitimate interests as our legal basis.
  • Rights related to automated decision-making: You have the right not to be subject to decisions based solely on automated processing, including profiling, which produce legal effects or similarly significant effects on you.

To exercise any of these rights, please contact us at contact@planhitch.com. We will respond to your request within one month, as required by law. In complex cases, we may extend this period by up to two additional months, and we will notify you if this is necessary.

10.Cookies

We use cookies and similar technologies to provide, secure, and improve the Service. For detailed information about the cookies we use, their purposes, and how to manage them, please see our Cookie Policy.

11.International Data Transfers

The Service is hosted in the European Union. Some of the providers listed in section 7 are based outside the United Kingdom, so your data does leave the UK. Two different safeguards apply, depending on where the provider is:

  • Hetzner, which provides our hosting, is in the European Union. The UK government has determined that the EU provides an adequate level of data protection, so no additional safeguard is needed for the data held on our servers.
  • Stripe, Anthropic, Resend, Cloudflare and Sentry are headquartered in the United States. Transfers to them are covered by the UK International Data Transfer Addendum to the European Commission's standard contractual clauses, or by the UK International Data Transfer Agreement (IDTA), together with each provider's own published transfer terms. These are the mechanisms UK data protection law provides for sending personal data to a country without an adequacy decision. This applies to Cloudflare and Sentry even though the data they store for us is kept in EU datacentres: the storage location does not change the fact that a United States company processes it.
  • Spotify receives only your search terms and any playlist address you supply. As section 7 explains, we connect to Spotify as an application rather than as you, so it does not receive information that identifies you.

In each case the safeguard is intended to give your personal data essentially the same protection abroad that it has under UK law. You can ask us for more detail about the arrangements covering any particular provider by writing to contact@planhitch.com.

12.Children's Privacy

The Service is not intended for use by individuals under the age of 18. We do not knowingly collect personal data from children. If we become aware that we have collected personal data from a child under 18 without appropriate parental consent, we will take steps to delete that data as soon as possible. If you believe a child has provided us with personal data, please contact us at contact@planhitch.com.

13.Changes to This Policy

We may update this Privacy Policy from time to time to reflect changes in our practices, legal requirements, or the Service. When we make material changes, we will:

  • Update the "Last updated" date at the top of this page.
  • Notify you by email and/or by posting a prominent notice within the Service at least 30 days before the changes take effect.
  • Where required by law, seek your consent to any material changes in how we process your personal data.

14.Contact and Data Protection

If you have any questions about this Privacy Policy or wish to exercise your data protection rights, please contact us:

  • Company: PlanHitch Ltd, registered in Scotland
  • Company number: SC869251
  • Registered office: Office 1325, 3 Fitzroy Place, 1/1, Sauchiehall Street, Glasgow Central, United Kingdom, G3 7RH
  • Data Protection Contact: contact@planhitch.com
  • Website: planhitch.com
  • ICO registration: PlanHitch Ltd is registered with the Information Commissioner's Office, the UK's data protection regulator.

If you are not satisfied with our response, you have the right to lodge a complaint with the UK Information Commissioner's Office (ICO):

Questions about this policy? Email contact@planhitch.com

Back to top