1. Who we are, and how to reach us

The data controller is N.J. Travel and Transport Limited Partnership, registration number 0203557004978, registered office at 3/5 Moo 3, Nong Chak Subdistrict, Ban Bueng District, Chon Buri 20170, Thailand.

For anything about your personal data or your rights, contact the managing partner by email at contact@nj-phuyaipu.com, by telephone on 08 1428 4492, or in person at the office above.

2. What we collect

• Account details — your name, surname, email address, telephone number and password (stored as a one-way hash that cannot be turned back into your password). If you sign in with Google, we receive your name and email address from Google.
• Record of your acknowledgement of this notice — when you acknowledge a version of this notice (at sign-up, when booking without an account, or after the notice changes), we record when, which version, your IP address in hashed form and your browser's user agent.
• Travel details — route, date and time, boarding and drop-off points, seat number, and passenger type (male passenger, female passenger, monk or nun), which you may leave blank. We use it to show your passenger type on your ticket, in your confirmation email, and in the booking list our staff see, and on services with numbered seats we also use it when seats are arranged, avoiding seating a monk next to a female passenger or a nun next to a male passenger. Some seats may therefore be closed to you, and where the system allocates a seat for you it avoids such a pairing as far as the free seats allow; where it cannot, it allocates a seat as usual without telling you. If you leave passenger type blank it is not used to arrange seating at all. It is not used to calculate any discount. Because monk and nun state a religious status, we collect and use those two answers only if you give explicit consent on the passenger details page. If you do not, you can still book as usual - we simply do not record your passenger type at all.
• Payment details — amount, method, status and the reference issued by our payment provider. We do not store your card number in our systems. When you pay by card, you type the card details into a secure payment window provided by our payment provider (Omise), not into a page of ours. The card number, expiry date and security code go directly to the provider without passing through our systems; we receive only a one-time token that stands for the card.
• Parcel details — the names and telephone numbers of the sender and the recipient, what is being sent, and the origin and destination, and a photograph of the parcel at the drop-off point, taken by the driver as proof of delivery. The photograph may incidentally capture the surroundings of the public place where it was left.
• What you tell us — the issues you report, your messages, and any images you attach.
• Usage records — sign-in times, successful and failed sign-in attempts, and the actions taken in your account, kept for account security and for later investigation.
• Data stored in your browser — see section 7.
• Location — the site asks your browser for your position only when you press the button to find the nearest boarding point. That value is used on your own device to choose a stop; we do not send it to our systems and we do not store it. The coordinates our systems do store are the positions of the vehicle (see section 6), not the position of your device; combined with your booking, however, they can show where you were during that trip.

3. What we use it for, and on what legal basis

• Providing the booking and parcel service, issuing tickets, taking payment, making refunds and contacting you about your own journey — performance of a contract (section 24(3)).
• Verifying identity, sending one-time passcodes, preventing account takeover and keeping the system secure — legitimate interest (section 24(5)).
• Producing accounting and tax records and meeting our obligations as a licensed transport operator — legal obligation (section 24(6)).
• Tracking and keeping a history of vehicle positions for operational safety, to show service status to passengers and to check vehicle operations after the fact — legitimate interest (section 24(5)).
• Measuring how the website is used, and recording screen activity (mouse movement, clicks and scrolling) for later replay, so we can find which steps are hard to use and fix the right ones — your consent only (section 19), and only while analytics is switched on — see section 7. You may decline, and declining does not affect searching, booking or payment in any way.
• Collecting and using the passenger types monk and nun, which are sensitive data under section 26 because they state a religious status, to show them on your ticket, in your confirmation email and in the booking list our staff see, and on services with numbered seats to help arrange seats as described in section 2 - your explicit consent only (section 26). You may decline, and declining does not affect searching, booking, seat selection or payment in any way.

We do not use your data for marketing and we do not send advertising messages. Everything we send you is about your own transaction — one-time passcodes, booking confirmations, schedule changes and receipts. If we ever begin sending promotional messages, we will ask for your consent separately first.

If you book without an account, you choose one channel — email or SMS — for every notice about that booking, and we use only that channel. The exceptions: when our staff cancel your booking or refund you, and for account security alerts, we also send an SMS for your security; and if the chosen channel cannot carry a particular message, we use the usual channel for it rather than not telling you.

4. Other people's data you give us, and data we receive about you

When you book for someone else or send a parcel to someone else, you must have that person's permission before giving us their details, and the permission of a parent or guardian if they are under 16.

Conversely, if your details reached us because someone else booked a seat or sent a parcel for you, we received them from that person. We use them only as needed to deliver the service that was booked and for safety during the journey, on the basis of contract and legitimate interest — and you have the same rights under section 8 as a customer who contacted us directly.

5. Who we share it with, and whether it leaves Thailand

We do not sell your personal data. We disclose only what is necessary to the following categories of service provider, who process it on our instructions:

• Payment service provider (in Thailand)
• SMS delivery provider (in Thailand)
• Email delivery provider (outside Thailand)
• Vehicle tracking provider (in Thailand)
• Cloud infrastructure and database providers (outside Thailand)
• Sign-in and mapping provider, only when you use those features (outside Thailand)
• Website analytics and screen-recording providers (outside Thailand) — only if you consent

Some of these providers are outside Thailand. Those transfers rely on the necessity of performing the contract you have with us, under section 28(3), and we send only what that service requires. You may ask us for the current list of providers in each category through the contact details in section 1.

We may also disclose data where the law requires it, where a competent authority orders it, or where it is necessary to establish or defend a legal claim.

We do not send passenger or parcel-recipient data to our accountants. What they receive is daily income and expenditure per vehicle, which carries no name, telephone number or journey detail of any individual.

6. How long we keep it

• Your account, when you close it — kept until you close it. When you close your account under item 5 of the "Your account" section of the Terms and Conditions of Service, we immediately delete its name, telephone number and password, replace its email address with a value that does not identify you, and remove its link to your Google account.
• When we suspend or close an account — a suspension or closure by us under item 4 of the same section is not a closure by you. The account's data stays, so that we can tell you the reason and reopen the account. A suspended account is kept until it is reopened or closed, and you may dispute a suspension at any time. You may dispute a closure within 60 days of being notified, or of the closure date if we could not send the notice. An account we close is kept for 90 days from the closure; if it has not been reopened within that time, we delete or blank (replace with a value that does not identify you) its data in the same way as when you close your account yourself, and it can no longer be reopened, unless your dispute is still being considered, in which case we do not delete it until we have told you the outcome.
• Record of a suspension, closure or reopening by us — we record which member of staff acted and when, the status before and after, the reason under item 4 and the staff member's internal note, so that a dispute can be considered and the action checked afterwards (legitimate interest, section 24(5)). We keep it for as long as your account exists and for 3 years from the date the account's data is deleted or blanked.
• Bookings, tickets, receipts and accounting records — 5 years from the end of the accounting year in which the transaction occurred. Our accounting year ends on 31 December (so a 2026 transaction is kept until 31 December 2031), as required by the Accounting Act B.E. 2543 and the Revenue Code.
• Monk and nun passenger types — kept with the ticket for the uses in section 2. When that booking's data is deleted or blanked, for example when an account is closed or when you ask us to erase your data under section 8, we change it to a neutral code that does not reveal religion; the amounts and the consent version stay as evidence.
• Parcel drop-off photograph — 395 days from the date the parcel was left at the stop, after which we delete only the photograph. The record of when the parcel was left there and by whom stays for the period given for booking data above.
• Messages you send us — what you reported, the text you wrote and the images you attached. We keep them until the matter is closed, and 90 days after that we delete the attached images and remove the text you wrote. If a matter is never closed, we delete them two years after you sent it.
• When an account is closed — immediately when the account is closed, the name, telephone number and email address recorded in its bookings are blanked, except in bookings that are not finished yet: a booking with a trip that has not yet reached its destination or reached it less than 24 hours ago, a booking still awaiting payment, a parcel not yet delivered, and a booking with a payment, refund or damage claim still open. We keep the contact details in those bookings until that matter is finished, so that we can tell you about changes to your trip and contact you about refunds; the system then blanks them in its nightly run. Once blanked, those bookings no longer name you. The money figures of those bookings are kept for the retention period for accounting records above: 5 years from the end of the accounting year.
• Backup copies — data we delete or blank also leaves our backups when those backups expire, about 42 days after the deletion.
• Record of your acknowledgement of this notice — when you acknowledge a version of this notice, we record the time, the version, your IP address in hashed (one-way scrambled) form and your browser's identification string (user agent), so that we can show which version you were told about (legitimate interest, section 24(5)). We keep it for as long as your account exists and for 3 years after it is closed. When the account is closed we delete the user agent straight away; the hashed IP address, the time and the version stay for those 3 years. For a booking made without an account, the record is kept for 3 years after the booking's last travel date.
• Bookings made without an account — kept for the periods above, unless you erase their personal data yourself (section 8). A booking that is not finished yet is erased automatically once it finishes.
• Usage records — 90 days.
• Data-export audit records — 1 year. We record which member of staff exported which dataset and when, so that improper access to personal data can be traced after the fact. The search filters used for the export are erased after 90 days.
• Vehicle position — our systems keep the position history of each vehicle received from its GPS device, so that vehicle operations can be checked after the fact, and delete history older than 180 days every night.
• Website usage statistics — if any is collected, held by the analytics providers for the periods they set, and you may withdraw your consent at any time under section 8. While analytics is not switched on there is none of this data at all.

When you ask us to delete your data we act in two stages. First, we immediately delete or blank the details that identify you, such as name, email address and telephone number. Second, once the accounting retention period above has passed, we sever the link between the accounting records and the individual. Between those two stages the accounting records can still be traced back to you, as the law requires, so we do not describe the data in that period as anonymised.

7. Cookies and data stored in your browser

We set one cookie of our own: obrs_refresh, which keeps you signed in. It is strictly necessary, cannot be read by the page's scripts, is sent only to our sign-in endpoints, and expires after 7 days without use or when you sign out. What our site keeps in your browser storage is:

• A marker that you are signed in, plus your username and role — no password or sign-in token — until you sign out.
• Display preferences such as language and theme, and the routes you searched most recently — until you clear site data.
• Details of a booking or payment you have started — the trips you selected, the booking reference and its payment deadline and, for a booking made without signing in, a pass that lets this browser pay for that one booking (valid for one hour). They stay on your device after you close the tab, so that you can come back to the payment, until the booking no longer needs them, you sign out, or you clear site data. A few values used only during one visit are discarded when you close the tab.
• Your answer about usage statistics — stored so we do not ask again, whether you accepted or declined.

The site collects usage statistics only when analytics is switched on AND you consent — both, not either. While analytics is not switched on, nothing is collected and no analytics cookie is set on your device, whatever you answer. When both are true, the analytics providers set additional cookies on your device: _ga and _ga_ followed by the measurement id (Google Analytics), _clck and _clsk (Microsoft Clarity), plus _cltk in the tab's temporary storage. That list comes from measuring the live page on 1 August 2026. Before you press accept, not one of them is on your device.

You can clear all of it from your browser settings, and while the site is collecting usage statistics you will find a withdraw button at the end of this page.

8. Your rights, and how to use them

As a data subject you have the right to:

• Access your data and obtain a copy, including being told where we obtained it (section 30).
• Have your data transferred to another controller (section 31).
• Object to the collection, use or disclosure of your data (section 32).
• Have your data erased or destroyed (section 33). You can close your account yourself on the My Account page, which removes the details that identify you; booking history and receipts are retained as accounting law requires — see section 6. If you booked without an account, you can erase the personal data in your bookings yourself on the Erase my personal data page, by proving with a one-time code sent to the phone number or email address you booked with that you hold it. A booking that is not finished yet (a trip still to come, an unpaid booking, a parcel on its way, an open claim, or a payment or refund in progress) is erased automatically once it finishes, and the page gives you a reference number for the request.
• Have processing suspended (section 34).
• Have your data corrected and kept up to date (sections 35 and 36). You can change your name, surname, telephone number and email address yourself on the My Account page.
• Withdraw consent (section 19, paragraph five). For usage statistics, while the site is collecting, use the withdraw button at the end of this page (while analytics is not switched on there is no such button, because nothing is collected and there is no consent to withdraw). It takes effect immediately with no need to reload, and on your next visit the analytics scripts are not loaded at all. Withdrawing stops collection from that point on; it cannot recall data already sent, and it does not affect the lawfulness of processing carried out before it.
• Lodge a complaint with the Personal Data Protection Committee's office if you believe we are not complying with the law (section 73).

Use the contact details in section 1. We will act within 30 days of receiving a complete request. Where a request is complex or involves a large volume of data we may extend that by up to a further 30 days, telling you and giving our reasons before the original deadline expires.

For security we may ask you to confirm your identity first, and to protect other people we may have to redact third-party details from the copy we send you. An electronic copy is free of charge.

9. How we protect your data

We maintain reasonable and appropriate measures, including storing passwords as one-way hashes, temporarily locking an account after repeated failed sign-ins, transmitting data over an encrypted connection (HTTPS), not storing payment card numbers in our systems, and limiting access to those who need it for their work.

If a personal data breach occurs, we will notify the Office of the Personal Data Protection Committee within 72 hours of becoming aware of it and, where it poses a high risk to you, notify you without delay.

10. Changes to this notice

This notice carries a version number and effective date at the top of the page. When we change it in substance we publish a new version with its effective date, and the next time you use the service you will be shown the change and asked to acknowledge the new version.

This notice does not yet cover in-vehicle camera recording. That section is being prepared and will be added in a future version.