Cookie Policy
Effective date: Date of publication on this page · Last updated: October 12, 2026
1. Scope
SOLA INTERNATIONAL K.K. (the “Company,” “we,” “us,” or “our”) establishes this Cookie Policy for cookies and similar technologies used on the TOKYO LIMOUSINE SERVICE main website (www.tokyolimoservice.com) and booking website (booking.tokyolimoservice.com) (collectively, the “Site”).
This Policy applies together with our Privacy Policy. After a visitor follows a link to an external site, the external operator’s privacy and cookie policies also apply.
2. What cookies are
A cookie is a small item of data stored by a website in a visitor’s browser or device. The Site also uses local storage, session storage, tags, tokens, and similar technologies. This Policy refers to all of them as “cookies.”
3. Categories
3.1 Necessary
These cookies are needed to display and secure the Site and to provide login, booking, payment, chat, display-setting, and cookie-choice functions requested by the visitor. Disabling them may prevent the requested function from working.
3.2 Statistics
These cookies help us understand Site use and improve quality and usability. They are off by default, and the relevant scripts are not loaded until the visitor consents.
Google Analytics 4 (GA4) is not currently connected to the booking website, and no Measurement ID has been issued. Before activating GA4, we will add the Measurement ID and the cookies actually used to this Policy and enable the appropriate consent settings.
3.3 Marketing
These cookies may measure advertising effectiveness. They are off by default. We do not currently operate advertising pixels, retargeting, or Google Ads conversion measurement. _gcl_au appears only as a possible future item and is not currently in use. We will update this Policy and the consent settings before introducing it.
The booking website has no separate “Functional” category. Storage needed for login, an unfinished booking, or display settings is classified as Necessary because it provides a function requested by the visitor.
4. Consent banners and changing choices
4.1 Booking website
The booking website uses our internally developed banner and supports Google Consent Mode v2. It displays “Necessary only,” “Accept all,” and “Settings.” “Necessary only” and “Accept all” use the same size and design, so refusal is as easy as consent.
Under “Settings,” visitors can switch Statistics and Marketing on or off separately. Both are off by default, and the related services are not loaded before consent. The choice, date and time, and version of the consent text are retained in a cookie for 365 days. Our server-side record of the choice is retained for up to 395 days so that the choice can still be demonstrated shortly after the cookie expires.
4.2 Main website
The main website uses the standard Squarespace banner and displays “Manage Cookies,” “Decline All,” and “Accept All.” Optional Performance and Analytics and Advertising categories are off by default.
4.3 Changes and withdrawal
Visitors can review, change, or withdraw their choices at any time through “Cookie Settings” in each site’s footer. If Statistics or Marketing consent is withdrawn on the booking website, we immediately delete the Google cookies set through that consent. Withdrawal does not affect processing that was lawful before withdrawal.
5. Cookies used on the booking website
Public pages generally store only tls_cookie_consent. Other necessary items are stored or loaded when a visitor enters the member area, signs in, books, chats, or pays.
| Name | Provider | Category and purpose | Retention | When used |
|---|---|---|---|---|
tls_cookie_consent | Company | Necessary / stores choices, date and time, and consent-text version | Cookie: 365 days / server-side consent record: up to 395 days | Public pages |
PHPSESSID | Company | Necessary / member-area session, including Google or LINE sign-in | Until browser closes | Member area |
csrf_https-contao_csrf_token | Company | Necessary / protects forms against forged requests | Until browser closes | Admin/member functions |
access_token, refresh_token | Company | Necessary / maintains sign-in and identifies the user to the server | Until sign-out | Browser storage |
tls_booking_wizard | Company | Necessary / keeps an unfinished booking after reload | Until booking is sent or restarted; otherwise no more than 7 days | Booking |
tls_booking_wizard_guest | Company | Necessary / holds guest booking details during booking | Until browser closes | Session storage |
tls_support_token | Company | Necessary / links chat messages to a support case | Until the browser tab or window is closed | Session storage after chat starts |
tls-theme, tls-bookings-view, tls_bookings_filters, tls_bookings_columns | Company | Necessary / remembers display, filters, and columns | Until user deletes | Browser storage |
tls-admin-trip-order, tls-affiliate-bookings-view, tls-affiliate-requests-view | Company | Necessary / remembers admin and affiliate views and sorting | Until user deletes | Relevant screens |
tls_chat_view_mode, tls_chat_language, tls_chat_pending | Company | Necessary / remembers chat display, language, and pending state | Until user deletes | Chat use |
__stripe_mid | Stripe | Necessary / payment fraud prevention and security | 1 year | Payment step |
__stripe_sid | Stripe | Necessary / payment fraud prevention and security | 30 minutes | Payment step |
m | Stripe (m.stripe.com) | Necessary / payment fraud prevention and security | 13 months | Payment step |
__cf_bm | Stripe / hCaptcha | Necessary / bot protection in card form | 30 minutes | Payment form |
tls_booking_wizard is stored only on the visitor’s device and is never sent to us. It is deleted when the booking is sent or the visitor starts over. Otherwise, after seven days it is deleted on the visitor’s next visit to any page of the booking website. It does not contain the visitor’s name, email address, or telephone number; during booking, those details are stored in tls_booking_wizard_guest in session storage.
6. Cookies used on the main website
The main website runs on Squarespace and uses Squarespace Analytics and Activity Log. Analytics cookies operate only after the visitor consents to analytics.
| Name | Provider | Category and purpose | Retention | Notes |
|---|---|---|---|---|
ss_performancecookiesAllowed | Squarespace | Necessary / stores analytics-cookie choice | 30 days | Squarespace banner |
ss_marketingcookiesAllowed | Squarespace | Necessary / stores advertising-cookie choice | 30 days | Squarespace banner |
ss_cid, ss_cpvisit, ss_cvr | Squarespace Analytics | Statistics / visit and conversion analytics | 2 years | Only after analytics consent |
ss_cvisit, ss_cvt | Squarespace Analytics | Statistics / visit-session analytics | 30 minutes | Only after analytics consent |
tls_support_token | Company | Necessary / links chat to a support case | Until the browser tab or window is closed | Session storage after chat starts |
7. Data sent to external services
The use of cookies or loading of external functions may send the following information to the relevant provider. The exact processing depends on the provider’s configuration, the visitor’s device, and the function selected.
| Provider/service | Main data sent | Purpose | Loading and storage |
|---|---|---|---|
| Google Maps / Places | IP address, device data, addresses and route data entered, etc. | Maps, address suggestions, route entry | Loaded only at route step; no item stored on device |
| Stripe | IP address, device/browser, payment and transaction data, fraud signals, etc. | Payment, fraud prevention, authentication, security | Loaded only at payment step; Company does not retain card data |
| YouTube | IP address, device/browser, video viewing and interaction data, etc. | Embedded video playback | Not loaded until user selects “Load YouTube video” |
| Squarespace Activity Log | IP address, approximate location, browser, OS, referrer, page and date/time | Traffic, operation, and security | Server-side record, not a cookie; retained for 7 days |
We select providers that are contractually required to protect personal information to a standard equivalent to that required under Japan’s Act on the Protection of Personal Information. Where the GDPR applies, we use the Standard Contractual Clauses (SCCs) or other appropriate safeguards. Information about individual providers, the countries concerned, and the safeguards used is available on request through the Contact Form.
8. YouTube videos
The main website initially displays only a thumbnail and a “Load YouTube video” button and does not load the player. The YouTube player is loaded only after the visitor selects the button. Google/YouTube may then set cookies and process the visitor’s IP address, device and browser information, and video viewing and interaction data.
9. Browser settings
Visitors can delete or reject cookies through their browser settings. Deleting or rejecting necessary cookies may prevent login, unfinished booking, chat, payment, or other functions from working. Clearing browser storage may also delete an unfinished booking.
10. Changes to this Policy
We may revise this Policy when technologies, providers, applicable laws, or Site functions change. We will provide advance notice of material changes through a prominent Site notice or another appropriate method and obtain renewed consent where required. Minor changes will be announced by publication on this page and an updated revision date.
11. Language
The Japanese version of this Policy is the governing text. If a translated version differs from the Japanese version, the Japanese version prevails to the extent permitted by law.
12. Contact
For questions about cookies, settings, international transfers, or this Policy, please contact:
SOLA INTERNATIONAL K.K.
Tokyo Limousine Service Privacy Desk
7-14-9 Minami-Aoyama, Minato-ku, Tokyo, Japan
Contact Form
External policies and references
© 2026 Tokyo Limousine Service. All rights reserved.