Legal

Privacy Policy

Last updated: 5 November 2026

This notice explains what personal data AIRPORTELs collects when you use this website, why we collect it, who we share it with, and what rights you have under the Personal Data Protection Act B.E. 2562 (2019) ("PDPA").

This notice applies to visitors and customers of the AIRPORTELs customer portal (luggage storage and delivery booking). It does not cover the separate partner or operations systems.

1. Who we are

Airportels Co., Ltd. (company registration no. 0105565098687) ("we", "us", "our") is the data controller for the personal data described in this notice. Our head office is at 6 Pailin Park Village, Soi Rattanathibet 28 Yak 2, Bang Kraso, Mueang Nonthaburi, Nonthaburi 11000, Thailand.

You can reach us at Center@airportels.asia or +66 2 026 6927 for any question about this notice.

2. What personal data we collect

We collect the following categories of personal data. We do not collect more than we need for the purpose stated against each category.

Booking and contact details
Name, email address, phone number, nationality, ID or passport type and number, pickup and delivery address (for delivery orders)
Purpose: To create and manage your booking, confirm your identity when you drop off or collect your luggage, and contact you about your order
Legal basis: Necessary for the performance of a contract with you, or to take steps you request before entering into one (PDPA s.24(3))
Payment data
We do not store your card number. When you pay, your browser is redirected to a checkout page hosted by Omise, our payment service provider. We only receive the order reference and the payment result (paid / not paid) back from Omise.
Purpose: To process payment for your booking
Legal basis: Necessary for the performance of a contract with you (PDPA s.24(3))
Anonymous session identifier
A Firebase-issued anonymous user ID, and device/browser signals used for bot-detection (see "Google" in the table below)
Purpose: To keep your booking session working as you move between pages, and to protect our booking and payment system from automated abuse
Legal basis: Necessary for the performance of a contract with you, and our legitimate interest in keeping the service secure (PDPA s.24(3) and s.24(5))
Website usage and advertising data (only with your consent)
Pages you visit and buttons you use on this website, device and browser type, approximate location from a shortened IP address, the advert or link that brought you here (for example a Google, Meta, TikTok or LINE click ID), and, if you are signed in, a pseudonymous customer number that is not your name, email or phone number. We never send your name, email, phone number, ID or passport number, address or payment details to these services.
Purpose: Analytics: to understand how the website is used and improve it. Marketing: to measure which adverts lead to bookings and to show you relevant adverts.
Legal basis: Your consent, given separately for the "Analytics" and "Marketing" categories in our cookie preferences (PDPA s.19). You can say no and still use the whole website.

3. Who we share your data with

We share limited personal data with the third-party service providers below, only for the purposes stated. Where a provider processes your data outside Thailand, that country is not currently included on a list of countries the Thai Personal Data Protection Committee ("PDPC") recognises as having adequate data protection — the PDPC has not published such a list at all as of this notice's last-updated date.

Google — Firebase Authentication
Always active — required for every booking, quote, and payment step on this site to work; the service cannot function without it and it cannot be turned off from cookie preferences
Receives: An anonymous session identifier and basic browser information
Purpose: To sign you in anonymously so we can process your booking
Legal basis: Necessary for the performance of a contract with you (PDPA s.24(3))
Cross-border transfer: Processed on Google servers in the United States. The United States is not currently recognised by the PDPC as providing adequate protection for personal data. We rely on PDPA s.28(4)/(5) as the basis for this transfer — it is necessary to perform our contract with you and for your benefit as the person requesting the booking.
Google — Firebase App Check / reCAPTCHA Enterprise
Always active — this runs on every page action and cannot be switched off from cookie preferences without breaking the ability to make a booking, get a quote, or pay
Receives: Device and behavioural signals (for example approximate mouse movement, timing, and browser fingerprint) used to tell a real visitor apart from an automated script
Purpose: To protect our booking and payment system from bots and abuse
Legal basis: Necessary for the performance of a contract with you, and our legitimate interest in preventing fraud and abuse of the service (PDPA s.24(3) and s.24(5))
Cross-border transfer: Processed on Google servers in the United States. The United States is not currently recognised by the PDPC as providing adequate protection for personal data. We rely on PDPA s.28(4)/(5) as the basis for this transfer — it is necessary to perform our contract with you and for your benefit as the person requesting the booking.
Google Maps
Only loads after you actively enable it in cookie preferences. If you decline or have not chosen yet, we show a static map and the address as a link instead — the site works fully without it.
Receives: Your IP address, browser identifiers, and cookies Google sets once the map loads
Purpose: To show an interactive map of our storage and delivery locations
Legal basis: Your consent, given through our cookie preferences (PDPA s.19)
Cross-border transfer: By enabling this, you consent to your IP address, browser identifiers and cookies being processed by Google in the United States, a country not currently recognised by the PDPC as providing adequate personal data protection.
CookieHub
Always active, so the site can ask for and remember your choice
Receives: An anonymous consent ID, the choices you make in the cookie banner, when you made them, and basic browser information
Purpose: To show the cookie banner, remember your choices, and keep a record that you gave or refused consent
Legal basis: Our legitimate interest in recording consent so we can show we respect your choices (PDPA s.24(5))
Cross-border transfer: Processed by CookieHub ehf. in Iceland, within the European Economic Area where the GDPR applies. Iceland is not on a PDPC adequacy list (no such list has been published).
Our tagging server (Google Cloud, Singapore)
Only after you allow "Analytics" or "Marketing"
Receives: The website usage and advertising data described in §2
Purpose: Website data first goes to our own server, which removes personal details from page addresses and shortens your IP address, then forwards it only to the services below that you allowed
Legal basis: Your consent for "Analytics" or "Marketing" in cookie preferences (PDPA s.19)
Cross-border transfer: Processed for us by Google Cloud in Singapore. By allowing these categories, you consent to this data being processed in Singapore, which the PDPC does not currently recognise as providing adequate personal data protection.
Google Analytics 4
Only after you allow "Analytics". If you decline, Google receives only signals without cookies or identifiers, used to estimate totals.
Receives: The website usage data described in §2, with a random device ID
Purpose: To produce statistics on how the website is used. We keep a copy of the raw statistics in our own Google Cloud project (BigQuery, Singapore) for longer-term analysis.
Legal basis: Your consent for "Analytics" in cookie preferences (PDPA s.19)
Cross-border transfer: By allowing "Analytics", you consent to this data being processed by Google in the United States, which the PDPC does not currently recognise as providing adequate personal data protection.
Google Ads, Meta (Facebook, Instagram), TikTok and LINE (LY Corporation)
Only after you allow "Marketing"
Receives: The advertising data described in §2: which pages you viewed, whether you made a booking and its value, and the ad click ID that brought you here
Purpose: To measure which adverts lead to bookings, and to show you relevant adverts on those platforms
Legal basis: Your consent for "Marketing" in cookie preferences (PDPA s.19)
Cross-border transfer: By allowing "Marketing", you consent to this data being processed by these companies outside Thailand, including the United States, Ireland, Singapore and Japan, which the PDPC does not currently recognise as providing adequate personal data protection. Each company also handles the data under its own privacy policy.
Omise
Only when you choose to pay
Receives: Your order reference (sent by us); once you reach Omise's own checkout page, whatever payment details you choose to enter there go directly to Omise, not to us
Purpose: To process payment for your booking
Legal basis: Necessary for the performance of a contract with you (PDPA s.24(3))

4. Data stored on your own device

While you are filling in a booking, we save your progress — including your name, email, phone number, and pickup/delivery address — in your browser's local storage (key: apts2-booking), so you don't lose it if you refresh the page. This stays only on your device until you submit the booking; it is not sent to our servers until then.

We also store your cookie preference choice on your device (the cookiehub cookie, for up to 365 days, or the apts2-cookie-consent key when our own banner is shown) so we don't ask you again on every visit. Analytics cookies (for example _ga) and advertising cookies (for example _gcl_au, _fbp, _ttp) are only set after you allow the matching category.

If you use a shared or public computer, we recommend clearing your browser's local storage after use, since this data remains on the device until cleared or the booking is submitted.

5. How long we keep your data

The schedules below are what apply automatically if we don't hear otherwise from you. You can also ask us to delete your account sooner — see §7 for that separate, faster process, which runs on its own 90-day countdown rather than these schedules.

Your account and all associated personal data, including your ID or passport number (name, contact details, luggage details, pickup and delivery addresses)
Retention: 10 years from your last account activity — any sign-in resets the clock (5 years while inactive, then a further 5 years)
Rationale: The company's stated basis for this period is the general 10-year civil prescription period under Thai law, giving enough time to handle a claim, dispute, or complaint tied to your account
Bookings by customers who never create an account, including orders placed through a partner
Retention: 5 years from the date the service is completed
Rationale: This period reflects a business decision, aligned with our financial record-keeping practices
A guest booking later linked to an account (you register using the same email you booked with)
Retention: Switches to the 10-year account-based clock above, extending it from the 5 years that would otherwise apply
Rationale: Once you register with the same email you used to book as a guest, that booking becomes part of your account and is retained on the same 10-year, activity-based basis as any other account data
Payment references (order reference and paid/unpaid status only — we do not hold your card details; see "Payment data" in §2)
Retention: While still linked to the rest of your booking: 5 years from service completion for a guest booking, or 10 years from your last account activity for an account booking — the same clocks as the rows above, and the same whether that removal happens on these schedules or because you asked us to delete your account under §7. Once your name and other identifying details are removed, what remains — the order reference, amount, date, and paid/unpaid status — is no longer personal data, and is kept indefinitely as a business/accounting record. One exception: if the order was completed within the last 5 years at that point, we separately keep your name and billing address on file, for the rest of that 5-year window only, because a full tax invoice must legally show them — this copy is never linked back to your account, shown to you, or used for any other purpose, and is deleted once the window ends.
Rationale: Deleting a booking in our systems means removing its identifying details (your name, contact details, nationality, ID/passport number, addresses, and any notes), not destroying the underlying record. The 5-year Accounting Act B.E. 2543/Revenue Code minimum is the reason we separately hold your tax-invoice name and address for that long after removal — a specific legal requirement on that one detail, not a reason to keep anything else. Once it lapses, there is no personal data left in the record, so no personal-data retention limit applies to what remains.
Anonymous session identifiers (Firebase anonymous user ID, App Check/bot-detection signals)
Retention: For the duration of your booking session, plus 90 days
Rationale: To keep your session working, and to give us a window to investigate suspected fraud or abuse
Local-storage booking draft (browser key: apts2-booking)
Retention: Stays on your own device only — see §4 above
Rationale: This never reaches our servers until you submit your booking, so there is nothing for us to retain
Website usage and advertising data (see §2)
Retention: Up to 14 months in Google Analytics. Our own copy in Google Cloud (BigQuery, Singapore) is kept only as long as we need it to analyse how our service is used.
Rationale: To compare usage over time. This data never contains your name, contact details, ID or payment details. Advertising platforms keep their data under their own policies.
Records subject to an active or threatened legal claim
Retention: Until the claim is resolved, plus the applicable statutory limitation period
Rationale: We may need these records to defend or pursue a legal claim, even after the periods above would otherwise have passed

6. Your rights under the PDPA

Subject to the exceptions and conditions in the PDPA, you have the following rights over your personal data:

Access (s.30)
Ask us to confirm what personal data of yours we hold, and get a copy of it.
Rectification
Ask us to correct personal data that is inaccurate or incomplete.
Erasure (s.33)
Ask us to delete your personal data, in certain circumstances.
Restriction
Ask us to limit how we use your personal data, in certain circumstances.
Data portability (s.31)
Ask us to provide your data in a machine-readable format, or transmit it to another controller where technically feasible.
Objection (s.32)
Object to certain processing carried out on the basis of our legitimate interest.
Withdraw consent (s.19, s.30)
Withdraw any consent you have given (for example, for analytics, advertising or Google Maps) at any time through "Cookie preferences" in the footer, as easily as you gave it — this does not affect processing carried out before you withdrew.

7. How to exercise your rights

To exercise any of the rights above, or to ask any question about how we handle your personal data, please contact us at Center@airportels.asia or +66 2 026 6927.

For erasure of your account specifically, you can request it yourself: sign in and go to Account settings → Delete my account, and confirm with a one-time code sent to your email. This starts a 90-day countdown, shown on that page, during which your account is locked for new bookings and changes but nothing is removed yet — you can change your mind at any time by signing in and confirming cancellation with another one-time code, which restores your account with nothing lost. Once the 90 days pass without you cancelling, removal happens automatically as described in §5, and the request can no longer be cancelled.

  • We will confirm receipt of your request and aim to respond within 30 days, as contemplated by the PDPA.
  • We may need to verify your identity before acting on a request, to protect your data from being disclosed to the wrong person.
  • If we cannot fulfil a request (for example, because we are legally required to keep a record), we will explain why.

8. Complaints

If you are not satisfied with how we have handled your personal data, you may lodge a complaint with Thailand's Personal Data Protection Committee (PDPC), the government body responsible for enforcing the PDPA.

9. Changes to this notice

We may update this notice from time to time, for example if we change what data we collect or which third parties we use. The date at the top of this page shows when it was last updated.