← Back to Tokyo JDM Drive

Your details

Privacy notice

What happens to the details you send us in a booking request, in plain words.

Last updated 5 October 2026 (version 2026-10-05)

Who is responsible

Tokyo JDM Drive is run by S&Y LLC (合同会社S&Y), a company in Tokyo. S&Y LLC is responsible for the details you send us.

S&Y LLC — 合同会社S&Y

3-11-5 Minami-Ikebukuro, Toshima-ku, Tokyo 171-0022, Japan

〒171-0022 東京都豊島区南池袋3-11-5 アウル南池袋101

Representative: Yoshiaki Sakai

Email: tokyojdmdrive@gmail.com

What we collect

What you type into the booking form or the booking screen on this site:

The form and the booking screen also send which language version of this site you used, and a short name for the link that brought you here (see Cookies below).

We need your name, email address and date to reply. To book on the booking screen, we also need your phone number. Anything marked optional is up to you.

We don't ask for your passport, date of birth or card details on this site. The booking screen asks for the address or hotel name where you want to be picked up and dropped off; it does not ask whether either address is your home.

We may also have details about you that don't come from the form:

What we use it for

To reply to your request, to arrange the night with you, and to run the ride itself — for example, so your driver knows where to pick you up and where to drop you off. Before your ride, we may also email you a reminder of your booking details, including your pick-up and drop-off places. If you book on the booking screen on this site, also to take your payment, to send you the confirmation email and, if your booking is changed, a change notice and how to pay any change fee. On the booking screen, to stop slots being blocked or misused, we keep a coded form of your IP address, made with a key only we hold, only while your payment is in progress, and delete it when that step ends. We also record how your request reached us: which of our links you came through (see Cookies), including the links and QR codes we give to hotels. Our staff may also record this by hand, for example to note the hotel where you found out about us. We use this to see which of our links and which hotels bring us guests. After your ride, we may send you one email from our office asking for a review on Google. If you don't want it, write to us at any time (see Who is responsible), or reply "stop" to that email, and we won't send you review requests.

We reply by email. If you give us a WhatsApp number or Instagram handle, we may also message you there. If you book on the booking screen, we may also contact you about that booking on the phone number you gave there, including on WhatsApp.

If your driver takes photos of you on the night, we use them only to send them to you, through the app you choose. If you book on our booking page (reserva.be), its operator collects your booking details for us, and we use them for the purposes above.

Apart from the review request above, we don't send you marketing, and we don't sell your details. The conversion-event fields we explicitly send do not include the raw details you type into the booking form or booking screen. Automatic advanced matching is currently enabled for OpenAI Pixel, so it may detect supported customer details, such as names and contact details, in those forms, hash them in your browser and include the hashes with conversion events. Both Pixels are explained under Cookies.

If you are in the EU or UK: the legal basis is that you asked us to take these steps before a possible booking and, if you book, that we need your details to carry out that booking. Recording how your request reached us is based on our legitimate interest in knowing which of our links and which hotels bring us guests. Asking for a review after your ride is based on our legitimate interest in hearing how the ride went and in having honest reviews of our service. You can object to either at any time (see Your rights); for the review request, replying "stop" is enough. The coded record of your IP address that we keep on the booking screen to stop misuse is based on our legitimate interest in protecting our booking system.

Where your details go

OpenAI Pixel conversion data is provided to OpenAI OpCo, LLC in the United States. Under OpenAI's terms, OpenAI Ireland Limited in Ireland processes EEA and Swiss data. OpenAI generally acts as an independent controller and may use the data for ad measurement and reporting, creating custom audiences, and improving, optimizing, and delivering its services, including through affiliates and service providers. We view campaign results in Ads Manager.

U.S. privacy law includes federal rules for particular sectors and rules that differ by state. OpenAI's Ad Tools Data Processing Addendum describes its personal-data handling, security commitments and international transfers. You can read more in the following materials.

Your details are seen by the people at S&Y LLC who handle your request, including your driver, and by the company that builds and maintains this website for us.

So your details may be handled in the USA as well as in Japan. Data collected by Meta Pixel may also be handled by Meta in Ireland, and EEA or Swiss data collected by OpenAI Pixel by OpenAI Ireland Limited in Ireland.

How we look after your details

If you want to know more about how we look after your details, ask us and we will tell you.

Cookies

When you arrive through a link that carries a source tag — our own links do, for example on Instagram and in the QR codes we give to hotels, and so can a link made by someone else — this site sets a cookie called tjd_src. It is set by this site itself, not by another company. It holds only that short tag, such as "ig", "h-01" or "instagram": letters, numbers, - and _, up to 20 characters, and nothing you type in. It expires after 30 days. When you send a request or book on the booking screen, the tag is sent with it, so we can see which links bring people here.

When you start paying on the booking screen, this site itself sets a cookie called tjd_hold. It holds only a random code that links your booking in progress to this browser. The JavaScript on our pages, including Meta Pixel and OpenAI Pixel, can't read it. It is deleted when this site confirms your booking or when you cancel the payment, and after 2 hours at the latest.

This site can also run Meta Pixel, a tool from Meta, the company behind Instagram and Facebook. When it runs, Meta's code stores Meta's own cookies on this site, such as _fbp, and can read cookies Meta has already put in your browser. It sends Meta the address of each page you open and the page you came from, your IP address, details of your browser and device, whether you looked at our prices or sent a request, whether you opened the booking-details step after choosing a course, night and pick-up time (InitiateCheckout), whether you clicked a WhatsApp or email enquiry link (Lead), whether you opened Stripe's card payment screen (AddPaymentInfo), and, after your booking is confirmed, that a payment was made with its amount and currency, Japanese yen (Purchase). For a WhatsApp or email enquiry link, it records only the click, not whether an external app opened or a message was sent. It does not send the course, night or pick-up time you chose, your name, email address, booking reference or ride date, anything you type into the booking form or booking screen, the message body, the payment method you selected or card information.

We use it to see which of our Instagram and Facebook ads bring people here and lead to requests. Meta also uses what it receives for its own purposes, under its own privacy policy — for example, to decide which ads to show.

If you are in the European Economic Area, the UK, Switzerland or Turkey, or in Andorra, the Faroe Islands, Gibraltar, Greenland, Guernsey, the Isle of Man, Jersey, Monaco, Saint Barthélemy, San Marino or Vatican City, or if we can't tell where you are, this site does not run Meta Pixel. Everywhere else it can run only after you allow optional advertising measurement. We tell where you are from your IP address, so with a VPN the site may treat you as being somewhere else. You can allow, reject or withdraw permission at any time with Cookie settings at the bottom of every page. Rejecting or withdrawing stops this site loading Meta Pixel in this browser; it does not delete what Meta has already received.

This site can also run OpenAI Pixel to measure ChatGPT ads. If you allow it, the Pixel stores the ChatGPT ad click reference from the oppref URL parameter in a first-party cookie called __oppref for up to 30 days, and a random browser reference in __obref for up to 365 days. Browser restrictions can shorten these periods. It records when you open the booking-details step after choosing a course, night and pick-up time (checkout_started), and, only after payment succeeds and the booking is confirmed, the completed order with its amount and currency (order_created). The event fields we explicitly send do not include your name, email, phone number, booking reference, ride date, form entries or card information. The Pixel can process the click reference, browser reference, page origin and technical connection data for attribution. Automatic advanced matching is currently enabled, so the Pixel may also include hashes of supported customer details, such as names and contact details, from forms, as described above. The same regional restrictions described above for Meta apply. You can allow, reject or withdraw OpenAI Pixel separately in Cookie settings. Withdrawal removes __oppref and __obref from this browser and stops future measurement, but does not delete events OpenAI has already received.

This site remembers your separate choices for Meta and OpenAI advertising measurement in its own cookies: tjd_px for Meta and tjd_oai_px for OpenAI. They hold only your choices. The Meta choice lasts up to 395 days and the OpenAI choice up to 395 days. Some browsers, including Safari and many in-app browsers on iPhone, delete them much sooner, sometimes after only a day. Once a choice is gone, that Pixel stays off until you choose again with Cookie settings.

After the OpenAI Pixel SDK has loaded, it also records the allow or reject state in a cookie called __oaiq_consent for up to 30 days and in browser local storage under oaiq_consent. The local storage entry may remain until you or the browser clears it. These SDK records alone do not make this site run the Pixel; this site still checks its separate OpenAI choice and regional restrictions.

How long we keep it

We keep your details while we need them to handle your request and any booking that comes from it.

If you ask us to delete them, we will, except for anything Japanese law requires us to keep, such as records of a ride that went ahead and of payments, which we keep for as long as the law requires. If you start a booking on the booking screen but don't pay, we blank out your name, email address, phone number and pick-up and drop-off places 30 days later. Emails about your request leave a separate copy at Resend, which Resend deletes 30 days after sending. If you have paid for a drive, Stripe keeps its own record of that payment for as long as its rules require. What Meta Pixel and OpenAI Pixel have sent is kept by each company under its own rules; deleting your request with us does not delete it. Your written booking record (運送引受書), both the email we sent you and our paper copies, and the instructions for your ride that we give your driver (運行指示書), which show your name and where we pick you up and drop you off, are records Japanese law requires us to keep. We keep them for the period the law sets, and during that period we do not erase them, even if your booking is later cancelled or you ask us to delete your details. The record of any change to your booking (when and how you contacted us, and the change fee and how refunds work) is kept with your booking record so we can handle questions and disputes about refunds and fees, and we do not erase it even if you ask us to delete your details.

Your rights

You can ask to see the details we hold about you, to correct them, or to delete them. Email us and tell us which request it is about:

tokyojdmdrive@gmail.com

We don't charge anything for these requests.

If you are in the EU or UK, you can also object to how we use your details, ask us to restrict that use, or ask for a copy in a format you can take elsewhere. You can also complain to the data protection authority where you live or work.

If something is wrong

If you are unhappy with anything we have done with your details, tell us and we will look into it and come back to you. Email:

tokyojdmdrive@gmail.com

Phone: +81 3-6687-7296 / +81 90-6865-2726