Privacy Policy

Effective date: October 5, 2026

Data controller: Grandlink LLC · New York

Privacy contact: han8andy@gmail.com · +1 347-957-6888

This policy explains what Grandlink collects, why, who receives it, how long we keep it, and what rights you have.

First, understand our role. Grandlink is a booking, matching and referral platform. The transportation itself is performed by independent, licensed Partner Fleets (see Section 1 of the Terms of Service). Some of your trip information therefore has to be passed to the Partner Fleet performing your trip — without that step, no car can reach you.

1. What we collect

1.1 What you give us when you book

⚠️ Addresses are precise, street-level location data with coordinates attached. They are the core data of this service — without them we cannot quote or dispatch.

If a passenger is under 18, the booking also collects the information described in Section 8.

1.2 Your account (only if you create one)

If you register, we keep your name, email, phone, a hashed password (never the password itself), or — if you sign in with Google — your Google account identifier instead of a password. We also keep your personal referral code, the referral code you signed up with (if any), your membership level, the credits issued to your account, and your account status.

1.3 Payment data

• Payments, including any tip you choose to give your driver, are processed by Stripe.
• Your card number, CVV and expiry never pass through and are never stored on Grandlink's servers.
• We store only what Stripe returns: transaction identifiers, amount, currency, payment status and payment time. For minor-passenger bookings we also keep the cardholder name and last 4 digits returned by Stripe, to check them against the guardian who signed (Section 8).

1.4 Location data (important)

• Driver location. The Partner Fleet driver performing your trip uses the Grandlink driver app (a mobile web app). Only while the trip is "in progress", the app reports latitude, longitude, accuracy, speed and heading about every 30 seconds. When a trip is not in progress, the system rejects all location reports.
• What you can see. You receive a trip tracking link. While the trip is in progress it shows your driver's live location, the vehicle details, and the driver's name and phone number.
• The tracking link stops showing location once the trip is completed or cancelled.
• The link is secured by a randomly generated 64-character hexadecimal token that contains no order number and cannot be guessed or enumerated. Do not share it publicly.
• We do not collect GPS location from passengers' phones. Passenger location comes only from the addresses you enter.

1.5 What our systems record automatically

• Order action logs (booking, payment, dispatch, status changes — with timestamps and actor)
• Email delivery logs (recipient, subject, delivery status)
• Server access and security logs (IP address, time, request path), used for fraud prevention and troubleshooting
• The time, IP address and policy version at which you accepted the Terms of Service and the Cancellation & Refund Policy (needed as evidence in a dispute)
• Website error reports: a cleaned error message, the page path with identifiers removed, and a general browser label (for example "Chrome · Windows") — no query strings and no full browser identification string
• If you turn on push notifications: the push address your browser gives us, your language, and your browser identification string, so we can deliver notifications to that device

1.6 The website AI assistant

If you use the AI assistant on our website, the question you type is sent to a third-party AI model provider so it can match your question to one of our pre-approved answers. The assistant only receives what you type into it; it does not receive your booking form, account, payment or minor-passenger information. Please do not type sensitive personal information into it.

We keep the question, the answer shown, the language, a session identifier (held in your browser for the current tab only — see Section 2.3), a one-way hash of your IP address, and whether you marked the answer helpful or clicked a link from it. If a request fails or is blocked, we also record the request, including your IP address, in our security audit log. We use this to improve our answers and to prevent abuse. If you type personal details (such as your name, phone or order number) into a question, that text is sent to the AI model provider and stored as written.

1.7 Reviews

If you leave a review, we keep your rating, comment and the display name you choose. Reviews may be shown publicly on our website under that display name.

1.8 Partner Fleet and driver data

For Partner Fleets and their drivers: company name, contact person, licence and insurance details, driver name, phone, vehicle type, plate number, driver's licence details, taxpayer identification number (for tax reporting), approval status, trip and settlement records, and location traces while a trip is in progress.

2. Cookies and browser storage

We use two kinds of cookies: necessary and analytics.

2.1 Cookies

2.2 Your choice about analytics cookies

• In regions where the law requires consent (the European Economic Area, the United Kingdom and Switzerland), analytics cookies are off by default and are used only after you agree. We recognise these regions from your browser's time zone and show you a cookie notice; Google Analytics is not loaded until you agree. In addition, Google applies the same default based on your IP address; where it does, Google Analytics does not set cookies but may receive basic measurement signals without them.
• Anywhere, you can change your choice from the "Cookie settings" link at the bottom of each page. If you decline, we remove the analytics cookies already set on our site, and we do not report your bookings to Google Analytics (Section 4).
• Elsewhere, including the United States, analytics cookies are loaded when you visit. You can block them in your browser settings or with Google's Analytics opt-out browser add-on.
• Necessary cookies are required for sign-in and security and cannot be switched off.

2.3 Data kept in your browser (not cookies)

The items below are stored on your device, in your browser. They are not stored on our servers unless stated.

Referral codes — what is in your browser and what is on our server. The referral code you arrived with stays only in your browser (`gl.ref`) until you register or book. When you do, it is sent with that registration or booking and kept on our server with your account ("signed up with") or with that order. Separately, our server keeps your own personal referral code (if you have an account) and a record of referral rewards: the referrer's account, the referred customer's email address, the order number, the reward amount and status, and any credit issued. These referral records are kept with the related account and order records (Section 7); closing an account does not remove them.

2.4 Advertising

We do not use Google Ads, remarketing or ad personalization, and we do not use advertising cookies. Services we embed for specific functions — Google Maps for address entry and Google for "Sign in with Google" — may set or read their own cookies under their own privacy policies.

3. How we use the data

1. To quote, create orders, take payment (including tips), and issue receipts and invoices;
2. To refer and dispatch your trip to a Partner Fleet, and to give the driver performing it the information needed to collect you;
3. To email you confirmations, receipts, driver-assigned / driver-accepted / driver-arriving and trip-completed notices, and your tracking link; and, if you turn them on, to send push notifications;
4. For live tracking and dispatch during the trip;
5. To run your account, credits and the referral program;
6. To handle cancellations, reschedules, refunds and disputes — including submitting evidence to Stripe and card issuers in a chargeback;
7. To answer questions through the AI assistant (Section 1.6);
8. To understand how the site is used and how many visits lead to bookings, through Google Analytics (Section 2);
9. To find and fix website errors, prevent fraud and abuse;
10. For minor passengers, to carry out the authorization and handover process in Section 8;
11. To meet tax, accounting and legal obligations.

We do not sell your personal information, and we do not use it for third-party ad targeting.

4. Who we share it with

We require Partner Fleets to use your information solely to perform that trip, and not to retain it, resell it, or use it for any other purpose.

Third parties handle data under their own privacy policies. We do not control the data practices of Google, Stripe or the AI model provider.

5. Security

• Card data never lands on our servers (handled by Stripe, PCI-compliant).
• Tracking links use high-entropy random tokens and stop showing location when the trip ends.
• The admin console and driver app require sign-in and enforce role-based access; a driver can see the customer details of their own trip only.
• The location endpoint verifies "this is my trip and it is in progress" before accepting any report, and rejects everything else.
• Sign-in sessions are stored on our servers only as a hash of the session token, not the token itself.

No system is perfectly secure. If a breach occurs and notification is required by law (including the New York SHIELD Act), we will notify affected users and regulators as required.

6. Your rights

Wherever you live, you may ask us to:

• Access the personal information we hold about you;
• Correct anything inaccurate;
• Delete your personal information (subject to legal and tax retention duties — financial records of completed transactions, and minor-passenger records described in Section 8, must be kept);
• Receive a portable copy;
• Not have it sold (we do not sell it in any case).

Closing your account from your account page stops you from signing in and ends your sessions, but it does not by itself delete your account record, booking and payment records or referral records, which we keep as described in Section 7. To ask for deletion, email us.

California residents (CCPA/CPRA) additionally have the rights to know, delete, correct, opt out of sale or sharing, and not to be discriminated against for exercising those rights. We will not refuse service or raise your price because you exercised a right.

To exercise a right, email han8andy@gmail.com. We respond within 45 days of receiving the request. To protect your data we may first verify your identity, normally through the email address and order number used to book.

7. Retention

8. Minor passengers and children's data

Grandlink operates school transfer routes, so a passenger may be a minor student.

• This website is not directed to children under 13, and we do not knowingly collect personal information directly from children under 13 (COPPA). We do not accept unaccompanied passengers under 14.
• Bookings for passengers under 18 must be made by an adult — a parent, legal guardian, or authorized school staff — who signs the Unaccompanied Minor Guardian Authorization.
• What the guardian provides: the passenger's name, date of birth, phone (optional) and language ability; health notes the driver should know (optional); whether a child seat is needed; the guardian's name, relationship, phone, email and backup contact; a second emergency contact (optional); the named receiving party at the destination and their phone and building; the school's 24-hour phone, an alternate receiver and a fallback handover point; and consents to emergency medical care, in-vehicle recording and the no-receiver protocol.
• Why we need the date of birth: to confirm the passenger's age on the day of travel (we accept ages 14–17 under this process), to apply the authorization, and to arrange the service (for example the child-seat requirement). The driver sees the passenger's age, not the date of birth.
• Signature record: the guardian's typed name, the signing time, IP address, browser identification string (user agent), the language version signed, and the version and content hash of the authorization document.
• Identity check: after payment, the cardholder name and last 4 card digits returned by Stripe, compared with the guardian's name.
• Boarding PIN: we store only a protected (hashed) form of the PIN, never the PIN itself; the PIN is emailed to the guardian before the trip.
• What the driver performing the trip receives: the passenger's name, age, phone and language; the guardian's and emergency contacts' names and phones; the receiving party, building, alternate receiver, school phone and fallback point; child-seat needs; health notes; and the boarding PIN check.
• At handover we record the receiver's name, the time, the driver, a photo of the handover (stored on our servers and viewable only through the admin console) and its GPS position.
• Retention: these records, the handover photo and the trip's location trace are kept at least until the passenger turns 21, plus 3 years, because a minor's time to bring a claim does not start running until adulthood. We do not delete them automatically, and they are excluded from the 90-day location deletion.
• This information is used only for the authorization, safety and handover process above. It is not sent to the AI assistant or to Google Analytics.
• If you believe we have inadvertently collected information from a child under 13, contact han8andy@gmail.com and we will delete it promptly.

9. Users outside the United States

The service and its data are hosted in the United States. By using the service you consent to your information being transferred to and processed in the United States. Section 2.2 explains how analytics cookies work in regions that require consent.

10. Changes to this policy

We may update this policy. We will change the effective date and post the update on the website. Material changes will be announced by email or on-site notice.

11. Contact

Grandlink LLC · New York

Privacy email: han8andy@gmail.com · Phone: +1 347-957-6888