Your journey.
Your privacy.

01. Who we are

Book D (“we”, “us”) provides the Book D Luxury Car Service app. This policy covers the Book D app and our public website, including customer accounts and operator accounts.

We are responsible for deciding how personal information is used to operate Book D. You can reach us at jongreat177@gmail.com.

A transport operator may also be responsible for information it uses to deliver your journey, receive direct payment or meet its own legal obligations. Its own privacy information applies to that separate handling.

02. Information we handle

Account and profile information

When you sign in, we receive an account identifier and the identity information described below. We store the name, phone number and optional LINE ID you save to your profile, together with your account email. Operators and staff also have access-role and business-association records.

Journey and service information

When you request a journey, we handle your contact details, pickup and destination addresses, dates and times, selected vehicle and service, passenger and luggage counts, and optional flight number or notes. Records also include booking references, quotes, your acceptance or cancellation decisions, policy versions you accepted, status changes, and driver contact or meeting details supplied for a confirmed trip.

Please provide only information needed for the journey. Avoid entering identity-document numbers, payment-card details or sensitive personal information in free-text notes. If you provide another person’s details, ensure you are entitled to do so and share this policy with them.

Operator content

Authorized operators can provide business contact details, vehicle specifications and registration plates, rates, photographs selected for upload, photo descriptions, and declarations about their right to use those photographs. Book D also records listing reviews and operational actions. Approved vehicle listings and photographs are shown to people browsing the app.

Support correspondence

If you email us, we receive your email address, message and any attachments you choose to include. We use these to respond to your enquiry, resolve an issue or handle a privacy request. Please avoid sending information that is not needed for your request.

Local data and technical information

The app stores saved-vehicle identifiers, local preferences, cached trip details and unresolved request data on your device. Hosting and authentication services process technical information such as IP addresses, request times, browser or device information, and security or error records needed to deliver and protect the service. Account and booking records are linked to your user identifier; a guest session, where available, has a session identifier.

Book D does not collect payment-card details or process fares in the app. Payment is arranged directly with the transport operator. The current app does not request device GPS location, contacts, microphone access or background location. Choosing an operator photograph uses Apple’s photo picker; Book D receives the image selected for upload, not general access to your photo library.

03. Google & Apple sign-in

Google: we request basic sign-in scopes (openid, email and profile). Google may provide your account identifier, email address and verification status, name and profile image URL. These details are used to authenticate you and associate your Book D account with your profile and journeys. We do not request Gmail messages, contacts, calendars or Google Drive files.

The native Google Sign-In SDK also processes technical information used to provide and improve sign-in, including device and app information, identifiers, sign-in usage and diagnostic information, and approximate location inferred from network information. Google’s SDK uses some of this information for its own service analytics. This does not give Book D access to your device’s precise GPS location.

Apple: Apple provides an account identifier and, when authorized and available, your name and email address. If you choose Hide My Email, we receive Apple’s relay address. Apple may provide your name only at your first authorization.

Our authentication provider, Supabase, verifies the sign-in and maintains the Book D account and session. Book D does not receive your Google or Apple password. Signing in with either provider does not authorize advertising or unrelated use of your account data. Google and Apple handle their own services under their respective privacy policies.

You can manage or revoke the connection in your Google Account or your Apple Account’s Sign in with Apple settings. Revoking provider access does not by itself delete your existing Book D account or booking records; use the deletion options below as well.

04. How we use information

• Create and secure your account, verify sign-in and restore access to your profile and journeys.
• Process booking requests, obtain quotes, record your decisions and coordinate the requested journey.
• Show relevant listings and allow authorized operators to manage their vehicles and trips.
• Answer support and privacy requests, investigate errors and prevent fraud or unauthorized access.
• Keep necessary service records, resolve disputes and meet applicable legal obligations.

Where applicable privacy law requires a legal basis, we rely on steps you request before a contract and performance of the service, compliance with legal obligations, and legitimate interests in operating and securing Book D, balanced against your rights. When a use requires consent, we ask for it and you may withdraw it. Acknowledging this policy is not blanket consent to unrelated processing.

Book D does not include advertising or cross-app tracking. Google Sign-In’s service analytics are described in the sign-in section above. We do not sell personal information or share it for targeted advertising.

05. Who receives information

• Your transport operator and assigned personnel: relevant contact, journey and booking details needed to quote, confirm and deliver your requested service.
• Supabase: account authentication, database and vehicle-image storage for Book D.
• Google or Apple: when you choose their sign-in service. If you use optional Apple Maps address search, your search query is sent to Apple to return suggestions; you may enter an address manually instead.
• Cloudflare: delivery and security of our public website when hosted on its network. Visiting the website sends the normal connection and request information needed to serve the page.
• Our email provider: Google processes support correspondence sent to our Gmail support address. This is separate from the basic identity information provided when you choose Google sign-in.
• Authorized staff and professional advisers: where necessary for support, administration, security, legal or accounting purposes.
• Authorities or other parties: where required by law, or where necessary and lawful to address fraud, protect rights or safety, or resolve legal claims.

If ownership of Book D changes, information may be transferred as part of that transaction subject to applicable safeguards and any required notice. We do not make private customer profiles or trip records public.

Third-party privacy information: Supabase, Google, Apple and Cloudflare.

06. Storage & security

Book D uses encrypted network connections, account-based access controls and protected on-device storage. Authentication credentials are stored using the iOS Keychain. Access to private booking and operator records is restricted by account and role. No internet service or device can be guaranteed completely secure.

Our service providers may process information in countries other than where you live. Where applicable law requires safeguards for an international transfer, the transfer must be covered by an appropriate legal mechanism. We will provide information about the processing locations and safeguards relevant to your data when handling a privacy request.

The public policy pages themselves contain no advertising, analytics scripts or embedded sign-in. Infrastructure providers may use essential security mechanisms. Google and Apple may use cookies or similar technologies on their own sign-in pages. The app uses local storage and session credentials to remember settings and maintain access.

07. How long we keep information

We retain account and profile information while your account is active and as needed to provide the service. Journey, transaction-related and decision records are retained as needed to fulfill requests, handle cancellations or disputes, and meet applicable recordkeeping obligations. Security and support records are retained for the period needed to investigate issues, protect the service and resolve requests.

Retention depends on the type of record, the status of a journey, applicable legal periods and any unresolved claim. When information is no longer needed, we delete or anonymize it, subject to the exceptions described here. Some copies may remain in restricted backups until the provider’s backup lifecycle removes them. Data subject to a legal preservation requirement may be kept for that purpose.

The retention criteria depend on the specific record and the reason it is held. We will explain any information that must be retained when responding to a deletion request.

08. Your choices & account deletion

• Update your profile: sign in and open Profile to edit your saved name, phone number and LINE ID.
• Clear local details: in Profile, choose “Clear saved vehicles & local contact details”. This removes those local values, but does not delete your account, erase all cached records or cancel trips.
• Request account deletion: sign in, open Profile → Your data → Request account deletion, and confirm. The request is sent to the Book D team for processing.
• Manage provider access: revoke Google or Apple access in the provider’s account settings. This is separate from requesting deletion from Book D.

The in-app deletion action submits a request for processing; it does not immediately erase your information or cancel an active journey. We may need to verify account ownership, resolve outstanding service matters and identify records that must be retained by law. We will explain the outcome and any applicable exceptions. Uninstalling the app or signing out does not delete server records.

Depending on where you live and the law that applies, you may have rights to access or obtain a copy of your information, correct it, request deletion, restrict or object to processing, request portability, or withdraw consent. These rights may have legal limits. You may also complain to the relevant data-protection authority. We may request proportionate verification to protect your information when handling a rights request and will respond within the period required by applicable law. For privacy enquiries or to exercise your rights, email jongreat177@gmail.com.

09. Children’s information

Book D accounts and booking requests are intended for adults. A journey may include children as passengers, but please provide only the passenger counts and practical arrangements needed for their transport. If you believe a child has provided personal information without appropriate authorization, notify the Book D team so it can be investigated and addressed.

10. Updates & contact

We may update this policy as Book D or legal requirements change. The current version and effective date appear at the top of this page. We will provide additional notice or request consent for material changes where required.