← Back to Tokyo Playbook
Privacy

Privacy Policy

Last updated: November 15, 2026

Overview

Tokyo Playbook LLC, doing business as Tokyo Playbook (“we”, “us”, “our”), operates tokyoplaybook.com. This policy explains what data we collect, how we use it, and your rights.

Mailing address: Tokyo Playbook LLC, 30 N Gould St Ste N, Sheridan, WY 82801, USA.

Copyright requests

If you submit a creator request, copyright notice or counter-notice, we collect the post link, handle, contact details and information you provide to verify and process it. Formal notices also include your legal name, statements and signature. Our private review queue is stored with Upstash; Resend delivers request and response emails. These are functional services, not optional analytics. We retain request and action records as reasonably necessary to handle claims, enforce our repeat-infringer policy and meet legal obligations. We may disclose notice or counter-notice information to the affected parties where needed for the DMCA process. These forms are excluded from analytics capture and session replay. See Copyright & DMCA for the process and agent contact details.

Information We Collect

Account Information: When you create an account, we collect your email address, display name, and password (stored as a secure hash). If you sign in with Google, we receive your name and email from Google. We also store your chosen avatar preference.

Onboarding Answers (Before You Sign Up): As soon as you start using the app, we begin recording your onboarding answers (trip type, cities, dates, interests, food preferences, travel companions) and any spots you save, attached to a temporary anonymous session, before you create an account, and even if you never complete signup. We use this to make the product work for guests and to understand where new visitors drop off. If you later create an account, this data carries forward and attaches to it automatically. This is first-party product data, not third-party tracking, and you can ask us to delete it even if you never completed signup.

Country: The first time the app or website creates your profile (including the temporary anonymous profile used before you sign up), we save the country you appear to be connecting from as a two-letter code, for example “US” or “JP”. Our hosting provider works this out from the network address of your request; we do not store the address itself, a city, or any more precise location with it. The code is saved once and not updated as you travel. We use it to understand which countries Tokyo Playbook is used from and to apply the right regional defaults (such as marketing-email consent). It is kept with your profile regardless of your optional-analytics choice, is not sent to analytics services, and is deleted with your account or on request.

Trip & Planning Data: You may provide travel dates, trip names, personal trip notes, private custom collection names and their saved-place membership, saved/bookmarked spots (restaurants, hotels, attractions, day trips), custom spots you add manually, selected interest preferences, and booking checklist progress. If you add a free-text note about yourself (for example, dietary needs, mobility considerations, or a special occasion), we store that in your profile and use it to personalize recommendations. This data is stored server-side in your account (or against your anonymous session, as described above).

Booking & Visiting Research: When you request a booking check, we send the selected venue and location, along with trip dates and party size when available, to OpenAI for web research. We do not send your account email or make a reservation. Research queries are processed through OpenAI's web-search service. We keep up to ten recent reports in an account-linked rolling 30-day cache so you can reopen them without a new search. Your successful free preview and its usage record remain until account deletion. Deleting your account removes these research records. Opening a booking or source link takes you to that provider's website and privacy terms.

AI Chat Messages: Messages you send to our AI assistant and the responses it generates are stored in your account profile to preserve your conversation history across sessions. This data is directly linked to your account. Separately from your saved conversation history, we also keep an internal operational log of each chat question and answer, including the full text, linked to your account (or a session identifier, for guests). We use this log for cost tracking, abuse prevention, debugging, and improving AI response quality; it may be reviewed by our team, including in full-text form. It is retained until you delete your account. When you submit feedback on a specific response (thumbs up/down or the feedback form), that feedback, including the relevant message context, is reviewed together with your account so we can investigate it.

Photos You Upload: If you take or upload a photo in the AI chat (for example, a menu, sign, or storefront), the image is sent to OpenAI to generate a response. We do not store the image itself on our servers or in your account, only a “[Photo]” placeholder is kept in your conversation history so the thread reads correctly. For place identification, the last screenshot may remain temporarily in app memory for up to ten minutes and be sent again for up to three related follow-up questions. It is cleared when you leave the app session or change accounts. We do not automatically capture your screen; social-link processing is explained below. Please do not upload photos containing sensitive personal documents (passports, IDs, financial documents) or images of other people who have not consented.

Voice Input: If you use the hold-to-talk microphone button, your spoken audio is converted to text by your browser's built-in speech-recognition service, operated by your browser vendor (Google for Chrome/Edge, Apple for Safari) and governed by their respective privacy policies. That audio is processed by the browser vendor's service, not by us; we never receive or store the audio recording. Only the resulting text transcript enters the chat, where it is handled the same as any typed message.

Payment Information: Payments on the website are processed securely by Stripe. In our iOS app, Japan Passes and existing subscriptions are purchased through Apple In-App Purchase, billed to your Apple ID, and RevenueCat processes the purchase receipt to activate your access. We never see or store credit card numbers on either path. We receive and store a customer identifier (your Stripe customer ID, or a RevenueCat app-user ID) and your email to link purchases to your account.

Trip Sharing (“Plan Together”): If you share your trip and someone joins it (or you join someone else's), the trip's members can see the shared trip's contents, saved places, day plans, and trip notes, and each member's display name (taken from your profile name, or the part of your email before the @ if you haven't set one). Only share a trip with people you want to plan with; a member can leave a trip at any time, and deleting your account removes your memberships and display name from all shared trips.

Japan stamp book: Planned stamps are derived from your trip. Visits are recorded only when you confirm them. Guest stamps stay on your device; signed-in stamps, confirmation dates, trip identifiers and estimated completed walking distances sync privately through Supabase. Stamps are not shared with trip collaborators automatically. Share cards and recap videos are created on your device and leave it only when you choose to share or save them. They use original stamp artwork, not Google place photos. Stamp collection does not request or record your device location. Deleting your account deletes its synced stamps. Optional stamp and sharing analytics follow your privacy choice.

Usage Data: We track basic usage metrics such as AI message counts to enforce usage limits. Standard server logs (IP address, browser type, pages visited) are generated by our hosting provider and retained transiently for security and operations; we do not store your IP address in your account.

Device Location: Tokyo Playbook has two optional location features. Both are off until you choose to use them, and your browser always asks your permission first.

“Near me” on the map: shows your current position on your trip map. This is processed on your device within your current browser session, it is not sent to our servers, not stored, and not used to influence recommendations.

“Right Now” nearby recommendations: if you ask what's good around you right now, your device's approximate coordinates are sent to our server to look up your neighborhood (a reverse-geocoding step) and are included in that chat message so the assistant can recommend places near you. Because this travels as part of a chat message, that location is also sent to our AI provider (OpenAI), saved in your conversation history along with the rest of the message, and included in the internal operational chat log described under “AI Chat Messages.” The reverse-geocoding lookup sends the coordinates to Google's Geocoding service to resolve a neighborhood name. We do not create a separate location-history record from that lookup, but the coordinates remain within the saved chat message and operational log until you delete that data or your account. We use your location only to answer that request, we do not track your location in the background and do not build a location profile.

You can decline the browser prompt, or revoke the permission at any time in your browser settings, without affecting any other feature.

Push Notifications: If you enable browser notifications, we store your browser's push endpoint and encryption keys, tied to your account. If you enable consultation reply alerts in the iPhone app, we store an Apple push token, a random installation identifier, a hashed installation secret and your account identifier with Supabase. Apple processes the token to deliver a generic message alert and a conversation identifier that opens the correct conversation; notification payloads do not include your message text or trip details. Device registrations expire after 30 days without refresh. If you turn on crew updates for a shared trip, we store an Apple push token and a random installation identifier with your account identifier in our cache (Upstash Redis) for up to 90 days without use. Those alerts name the travel partner and, for places, the place name and trip name (for example “Mia added Ichiran to Tokyo trip”); turn them off anytime in the trip's crew sheet. Signing out or disabling alerts removes the registration when the device can reach our server. You can disable notifications in the app or iPhone Settings. Email reply alerts remain available independently. We use these registrations only for notifications you have opted into, not advertising.

Acquisition Attribution: After you allow optional analytics, we may record bounded campaign labels, the referring site's origin and a generalized landing route. We do not collect full referring URLs, advertising click IDs or search terms for this attribution. A device copy expires after 90 days; account-linked attribution follows account retention and deletion. Declining analytics prevents this optional capture.

How We Use Your Information

We use your information to:

Optional AI Assistant Connections

When you connect an external assistant, you choose which owned trips it may read and whether it may send drafts. The connector shares trip titles, dates, stop names, cities and scheduled times. It does not export private notes, booking references, photos, Google summaries, payment details or collaborator identities. Copying a trip brief shares nothing until you paste it into another service. That service processes the information under its own terms and privacy policy.

Assistant proposals remain drafts until you approve them. Proposals can contain notes or reservation references you provide; approved additions to shared trips are visible to collaborators. Pending drafts expire after seven days. Connection permissions expire after 30 days and can be revoked earlier in Account. Revocation blocks future access but cannot erase copies held by another service. Account deletion removes connection grants and draft content; saved additions are deleted with the trip. We retain an internal draft identifier with the account and trip to prevent duplicate saves. Tokyo Playbook does not make travel bookings or collect travel-payment card details through these connections.

AI Chat & Data Sent to Third Parties

When you use our AI chat assistant, your messages are sent to OpenAI for processing. OpenAI processes your message to generate a response, which is then returned to you. We disable response storage for these API requests. This does not eliminate provider retention: OpenAI may retain content in abuse-monitoring logs for up to 30 days, with exceptions for legal or safety requirements. API content is not used for model training by default. Anthropic may process requests if we explicitly restore our previous provider; we do not automatically send failed requests to a second provider. OpenAI's use of this data is governed by their own privacy policy. We do not share your name, email, or other account details with OpenAI, only the chat message content and relevant trip context needed to generate a useful response. That context can include your travel dates, cities, stated interests and food preferences, travel-companion mix, travel style, saved spots, and any free-text note you've added to your profile (for example dietary needs, mobility considerations, or an occasion). This means information you choose to share about yourself, including health-related details like allergies or dietary restrictions, is sent to OpenAI as part of generating your answers (including photo answers, so the assistant can flag dishes that conflict with your note). Only share what you're comfortable disclosing; you can edit or remove the note in your profile at any time. If you upload a photo in the chat, that image is also sent to OpenAI for analysis. Voice input is transcribed by your browser's speech service before any text is sent, see “Voice Input” under “Information We Collect” above.

Social Post Imports

When you share a public Instagram, TikTok or YouTube link, including as a guest, we send that link to Bright Data, a third-party data provider, to identify the places mentioned. Available post information may include the caption, hashtags, location tag, creator handle, thumbnail, video URL and transcript. We remove supported tracking parameters. We do not send your account email, password, itinerary or social-platform login credentials to the provider.

Relevant post text, slideshow images, a thumbnail and three to five sampled video frames may be sent to OpenAI to read venue names and place-specific tips. When no transcript is available, temporary audio may be sent for transcription. Korean, Chinese, Japanese and English source text may be translated. Video, audio and processing frames stay in memory and are not saved or re-hosted. We do not use imported content to train models. For credited source cards, we may retain one compressed Instagram thumbnail of at most 480 pixels for up to 30 days; TikTok source previews use its official oEmbed service. Tapping a source opens the original platform; we do not play imported videos. Our post cache retains place IDs, names and city/area hints extracted from the post, our own short summary and canonical tips, distinct-post tip counts, creator credit, the source link and a snippet of no more than 140 characters. It does not retain Google ratings, opening hours, photos or addresses. Anonymous aggregate confirmed-save counts are kept for up to 40 days, without raw account or device identifiers. A creator or platform may request removal through our copyright page. Removal deletes the source thumbnail, snippet, summary and tip contributions and recalculates counts; users retain their saved places without that source content. Provider job handles are kept for up to 24 hours to avoid duplicate collections; this does not describe the provider's own retention. If you choose “Notify me when it’s ready”, iOS may finish the import using a background transfer and show a local notification with your permission. The pending result stays on your device for review; it does not automatically save new places. Original source links stay attached to saved places. Provider processing is governed by Bright Data's privacy policy.

Google place data storage

Google place IDs may be retained to reconnect your saved places. Google display details, photos, review excerpts and review-derived Local Intel are fetched for active views rather than kept in a durable content archive. Map coordinates have a separate 29-day expiry. Your own trip plans, notes and photographs are stored separately. Anonymous operational photo counts contain place IDs and totals, without account IDs, device IDs or IP addresses, and expire after 40 days.

Third-Party Services

Functional providers support maps, sign-in, trip features, payments, hosting and security when those features are used. They are separate from optional analytics and replay, and remain available before a choice or after Decline. They may receive the information described below:
Affiliate Links: Some outbound links (to Klook, Airalo, Agoda, and others) are affiliate links. When you click these links, the destination site may set its own cookies and track your visit according to their own privacy policies. We do not control or have access to data collected by affiliate partners.

Business Transfers

If Tokyo Playbook LLC is involved in a merger, acquisition, financing, reorganization, bankruptcy, receivership, sale of company assets, or transition of service to another provider, your information may be transferred or disclosed as part of that transaction or proceeding. Such a transfer is permitted under applicable law (including the carve-outs for asset transfers under the California Consumer Privacy Act and the European Union General Data Protection Regulation) and is not considered a “sale” of personal information. We will notify affected users of any such change in ownership or control (for example, via email or a prominent notice on this site) and the successor entity will be bound by the commitments in this Privacy Policy, or you will be given an opportunity to opt out before any materially different terms apply.

Data Storage & International Transfers

Your data is stored securely using Supabase (hosted on AWS in the United States) and Stripe (United States). If you are located outside the United States, your data will be transferred to and processed in the United States. Where personal data of EEA, UK, or Swiss residents is transferred outside those regions, that transfer is protected by appropriate safeguards, principally the European Commission's Standard Contractual Clauses (with the UK International Data Transfer Addendum where applicable), incorporated into our data processing agreements with these providers, and, where a provider is certified, the EU-US Data Privacy Framework. You may request more information about these safeguards by contacting us. We implement industry-standard security measures including encryption in transit (TLS) and at rest, and row-level security policies on our database.

Cookies, Analytics & Your Choices

Essential cookies: We use strictly-necessary cookies for authentication and session management. These are required for the site to function and do not require consent.

Local storage: We use your browser's localStorage to remember preferences (such as premium status, UI state, and your cookie choice). Essential preferences stay on your device. If you allow optional analytics, we also store bounded campaign labels and a referring-site origin for up to 90 days on your device and may associate them with your account. We do not store full referring URLs or advertising click IDs for this purpose.

Analytics (off until you allow it): We use Google Analytics and PostHog to understand how the site is used so we can improve it. Google Analytics, PostHog, Vercel traffic/performance monitoring and browser error reporting remain blocked until you accept optional services. Google Maps loads when you use a map, including if you decline optional analytics. Our app fonts are served from our own site; Google Maps may load its own functional map fonts from Google Fonts when a map is opened. We do not send pre-consent Google Analytics measurements. Optional product events describe actions and counts rather than chat text, reel captions or precise location. If you sign in, PostHog may associate consented events with your account ID; this is pseudonymous, not anonymous. Advertising signals stay disabled, and we do not use these analytics for cross-context behavioral advertising. You can change or withdraw your choice at any time:

Anonymous service counts (always on): To know whether Tokyo Playbook works for new travellers, the app tells our server when a device reaches a few steps: a fresh iPhone install opening the app, finishing setup, a first trip or saved place, a successful post import, joining a trip someone shared with you, and opening a Trip Pass offer. We keep only a daily total per step and per platform (app or web). No account ID, device ID, cookie, IP address, place or content is stored with these counts, and nothing is written to your device for them, so they cannot be linked to you.


(You can also withdraw consent by clearing this site's data in your browser. Declining keeps analytics, replay and optional performance monitoring off. Maps, place photos, routes, sign-in and payment features remain available. Account → Help & privacy → Privacy choices opens the same control.)

Vercel Analytics: Only after you accept optional services, our host, Vercel, provides cookieless aggregate traffic and performance metrics (such as page-view counts, loading time, and responsiveness). It sets no cookies, does not track you across sites, and does not build a personal profile.

Global Privacy Control (GPC): When your browser sends navigator.globalPrivacyControl=true, we automatically treat optional tracking as declined, including when an earlier Accept was saved. We do not prompt you with the banner. Privacy choices explains that GPC is active; you must disable the browser signal before opting in. Your choice is remembered on that browser/device; a different browser or fresh install has its own choice. Before you choose, analytics and replay remain off. Accept and Decline are equally prominent and no option is pre-selected.

No advertising pixels are currently installed. Any future advertising integration must use the same opt-in/opt-out and GPC gate and expose a “Do Not Sell or Share My Personal Information” control in the website footer and Account.

We do not sell or “share” (as defined under California law) your personal information, and we do not use it for cross-context behavioral advertising.

Your Rights

All users may:
For EU/EEA & UK Residents (GDPR / UK GDPR): You have additional rights including the right to data portability, the right to restrict processing, the right to object to processing based on legitimate interests, and the right to lodge a complaint with your local data protection authority (in the UK, the Information Commissioner's Office, ico.org.uk). Our legal basis for processing is (a) your consent (for optional analytics), (b) contractual necessity for providing the service, and (c) our legitimate interest in securing and improving the service. You may withdraw consent at any time without affecting prior processing.

For California Residents (CCPA/CPRA): You have the right to know what personal information we collect and how it is used, the right to access and to request correction or deletion, and the right to opt out of the “sale” or “sharing” of personal information. We do not sell or share your personal information, we do not use sensitive personal information to infer characteristics, and we honor the Global Privacy Control (GPC) browser signal as a valid opt-out. We will not discriminate against you for exercising these rights.

For Other U.S. State Residents: If you reside in a state with a comprehensive privacy law (including Virginia, Colorado, Connecticut, Utah, Texas, Oregon, and others as they take effect), you have comparable rights to access, correct, delete, and obtain a portable copy of your personal data, and to opt out of targeted advertising and sale (we do neither). Contact us using the details below to exercise them.

For Residents of Other Countries: If you are located in Canada (PIPEDA), Brazil (LGPD), Australia (Privacy Act), Japan (APPI), or another jurisdiction with data-protection law, you may have similar rights. We will honor verified requests consistent with applicable law, contact us using the details below.

Personal Japan advice

If you use Ask Tokyo Playbook, your messages and the trip details you choose to include are stored with Supabase and read by the authorised human adviser to respond to you. We do not automatically share your other trips or location, or send these conversations to an AI provider. The adviser may record time spent, follow-up counts and private service-quality ratings to manage and improve the consultation service; these records follow the same account deletion policy. Resend sends incoming-message alerts to our adviser and reply notifications to your verified account email; the emails contain no message text or trip details. Optional iPhone alerts are described under Push Notifications above. Conversation history remains available after your pass ends and follows the account deletion and retention policy below.

Data Retention

We retain your account data, trip planning data, and chat history (including the internal operational chat log) for as long as your account is active. If you delete your account, we will delete your personal data, including your profile, trips, saved spots, chat history and logs, usage counters, feedback and feedback screenshots, and push-notification subscription, within 30 days, except where we are required by law to retain it.

Payment records: Stripe, our payment processor, independently retains transaction records (such as invoices and charges) for its own tax, accounting, and fraud-prevention obligations even after you delete your Tokyo Playbook account. Those records are governed by Stripe's own privacy policy.

Uploaded photos: Photos you send to the AI chat (for example, to translate a menu) are forwarded to OpenAI for processing and are not stored on our servers after the response is generated. Screenshots you upload to import a booking, or attach to feedback, are kept in a private storage bucket as part of your account or feedback record and are deleted when you delete your account (within the 30-day window above) or sooner upon request.

Anonymized, aggregated data (such as usage statistics) may be retained indefinitely.

Data Breach Notification

We maintain reasonable safeguards to protect your data. In the event of a personal-data breach that is likely to result in a risk to your rights, we will notify the relevant supervisory authority and affected users without undue delay, and within the timeframes required by applicable law (for example, within 72 hours of becoming aware, where GDPR applies).

Children's Privacy

Tokyo Playbook is not directed at children under 13 (or under 16 in the EU/EEA). We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, please contact us and we will delete it.

Changes to This Policy

We may update this policy from time to time. We will notify users of material changes via email or a prominent notice on our website. Your continued use of the Service after changes constitutes acceptance of the updated policy.

Contact Us

For privacy-related questions, data access requests, or account deletion requests, email us at contact@tokyoplaybook.com.

See also our Terms of Service.
Back to Tokyo Playbook →