This policy explains how Tunder collects, uses and discloses the personal data of store owners, store staff, warehouse staff and billing managers who use Tunder POS, Tunder Warehouse, Tunder Billing, Tunder Auth and Tunder Print, in accordance with the Personal Data Protection Act B.E. 2562 (2019) (PDPA).
Data about customers that a store keeps in the system (for example members, delivery addresses and tax invoices) is not covered by this policy. See Store customer data. For customers and website visitors, see the privacy policy for customers and visitors.
Data controller and contact
The data controller under this policy is Jetniphan Pukkham ("we", "us")
- Address: 335/26 Moo 3 (DK Property), San Phak Wan Subdistrict, Hang Dong District, Chiang Mai 50230
- Telephone: 080-915-3786
- Email for personal data matters: jeni.pukkham@gmail.com
The contact details above handle every personal data matter.
Data we collect
We collect only the data the system actually uses, grouped by service as follows.
User account and profile
Shared by every app through Tunder Auth.
- Username, password (stored with one-way encryption, so nobody can read the actual password) and sign-in method (email, or a Google / LINE account)
- Profile: full name, email, telephone number and profile picture
- At sign-up: first name, last name, email, password and the OTP code sent by email (it expires in 5 minutes)
- When you forget your password: we send an OTP code by email (it expires in 5 minutes) and keep the unfinished password reset record (email, status, OTP code and the number of attempts left) temporarily, for no more than 15 minutes. We delete it as soon as the new password is set
- If you sign in with Google: we receive your name, email and profile picture from Google
- If you sign in with LINE: we receive your name, profile picture and LINE user ID from LINE (we do not receive an email from LINE). If there is no email, we use the LINE user ID as the username
- While we wait for you to confirm the OTP at sign-up, we keep the sign-up data (first name, last name, email and the password in encrypted form) temporarily, for no more than 24 hours
- Cookies needed to sign in: a cookie showing that you are signed in (lifetime 120 seconds) and a cookie for a pending sign-in (lifetime 300 seconds)
Store and store members
- Store name, the email of each store member, and each member's role
Tunder POS
- Sign-in system cookies: a cookie showing that you are signed in (lifetime 24 hours), a cookie that guards against forged requests, a cookie that remembers the state during the sign-in steps (lifetime 15 minutes) and a cookie that remembers the page to return to after sign-in. The forged-request cookie and the return-page cookie expire when the browser is closed
- Values remembered in the browser, such as printer settings, payment settings and notices the user has dismissed, plus list states remembered temporarily in the tab
- Uploaded files, such as product pictures, logos and payment QR codes
- Menu pictures that the user sends to the AI menu import feature (only when the user chooses to use this feature)
- Error data (Sentry). Only the user ID and the store ID are attached to an error, with no email, username or other name
- Screen recording (Sentry Session Replay) runs only when you allow the session replay category in the cookie banner. Once enabled, we record about 10% of sessions, and every session in which an error occurs
- Usage events (Google Tag Manager / Analytics) and usage logs from your browser sent to Sentry run only when you allow the analytics category. For example, when an order is created, the event carries the store ID, the order ID and the amount
- Server and edge logs of POS are always sent to Sentry, on the basis of our legitimate interests in operating and fixing the service
- Screen recording, usage events and browser usage logs run on your consent, to improve the service and fix errors. You can change your mind or withdraw consent at any time at Cookie settings. The details of each cookie and tool are in the cookie policy
Activity log
- When a user performs an action in the system, we record the email of the person who did it, the type of action, the data of the action, the IP address and the browser type
Tunder Warehouse
- The email and name of the person who performs a stock action, and supplier data (typed as free text)
- A sign-in token is kept temporarily in the browser tab (it disappears when the tab is closed). Tunder Warehouse does not use cookies, and loads fonts from Google Fonts
Tunder Billing
- The name and address used on receipts, the billing manager's email, the store owner's email (used to check trial eligibility so that a trial is not used twice) and the email contained in the code used to hand a sign-in over between apps
- Bills and receipts
- An email OTP code for billing managers to sign in
- We send the payment provider Opn only the amount and the bill number, not a name or an email
Tunder Print
The details of the Tunder Print app (device token, print job ID, IP address, on-device print history, the permissions the app asks for, and how to delete data) are in the Tunder Print annex at the end of this policy.
Purposes and legal bases
| Data | Purpose | Legal basis |
|---|---|---|
| User account, profile, store and store members, OTP | Create the account, verify identity, give access to the system and assign permissions by role | Contract (the service the user requested) |
| Device token, print job ID, IP address and print history of the Tunder Print app (history is kept on the device for 24 hours) | Pair the device with the store, verify the right to receive print jobs and send print jobs to the printer | Contract |
| Uploaded files, menu pictures sent to AI, settings remembered in the browser | Make the features the user asked for work | Contract |
| Name, email, address, bills and receipts of Billing | Issue bills and receipts, check trial eligibility | Contract, and legal obligation (keeping bills and receipts) |
| Activity log (email, action, IP, browser type) | Look back at who did what, keep the service secure and fix problems | Our legitimate interests and those of the store |
| Error data (Sentry), with the user ID and store ID attached, and POS server-side logs | Fix errors in the system | Legitimate interests |
| Screen recording (Session Replay), usage events (GTM / Analytics) and usage logs from your browser sent to Sentry | Improve the service and fix errors | Consent (through the cookie banner) |
| Email of the person who performs a stock action and supplier data in Warehouse | Record who performed an action and where the goods came from | Contract |
Consequences of not providing data
Account data (name, email, password or Google / LINE account) and the data needed to issue bills are necessary for the service contract. If you do not provide this data, we cannot create an account or issue a receipt for you. Screen recording and usage analytics are not necessary for the core use of the service, and run only when you allow them. If you do not allow them, or you withdraw consent at Cookie settings, the service works as normal.
Recipients and sub-processors
We use external providers to carry out some parts of the system. Each provider receives only the data listed.
| Provider | Used for | Data received | Country |
|---|---|---|---|
| Hostinger (VPS, Dokploy) | Servers and databases of every service | All server-side data | Indonesia |
| Amazon Web Services (S3) | Storing uploaded files | Product pictures, logos, QR codes | Australia |
| Sentry | Tunder POS | Errors with the user ID and store ID attached, POS server-side logs, usage logs from your browser and screen recordings (the last two with your consent) | Germany |
| Google Tag Manager / Analytics | The website tunderpos.com and Tunder POS | Usage events, such as store ID, order ID and amount (with your consent) | Data centers in many countries worldwide, including the United States |
| OpenRouter and the model providers that OpenRouter forwards to | The AI menu import feature of Tunder POS | Menu pictures (zero data retention mode is on by default) | United States, and forwarded to the AI model provider that is used |
| Opn (Omise) | Payments in Tunder Billing | We send only the amount and the bill number | Thailand |
| LINE | Sign-in with LINE in Tunder Auth | The authentication result from LINE and profile data (name, profile picture and LINE user ID) | Thailand |
| Sign-in with Google (Auth), ML Kit and Google Play (Print), Google Fonts (Warehouse) | Profile data from sign-in (name, email, profile picture), ML Kit diagnostic data and font load requests | Data centers in many countries worldwide, including the United States | |
| MailerSend (sending email through our mail system) | OTP emails of Auth and Billing | The recipient's email address and the content of the email. Our mail system also keeps a copy of the content and a send log | European Union |
| Cloudflare (DNS and proxy) | Some API domains, including the domain the Tunder Print app connects to (client-print.tunderpos.com) | Requests that pass through the proxy, which includes the Tunder Print device token and IP address | Cloudflare's global network, which may include the United States |
The store owner, and administrators that the store owner appoints, can see the email, role and activity log of the staff in their own store.
We do not sell personal data.
Transfer of data abroad
Our servers and databases are in Indonesia (Hostinger), so using the system means data is transferred for storage outside Thailand. In addition, some data is sent to the providers in the table in Recipients and sub-processors, who are in Australia, Germany, the European Union, the United States and other countries.
We transfer data abroad for two reasons: it is necessary to provide the service under the contract you made with us (PDPA Section 28 (3)), and each provider applies data protection measures under its own terms (Section 29). To ask for details, contact us as set out in Data controller and contact.
Data retention
We keep data as the system actually operates, as follows.
- Account data, profile, store and activity log: kept for as long as you use the service, and after you stop using it, kept until we receive a request to delete it
- Bills and receipts: kept for 5 years under our accounting policy, and not deleted on request until that period has passed
- Data that must be kept by law or as legal evidence: kept for as long as the law requires
- Sign-in cookies: for the lifetimes stated in Data we collect. The forged-request cookie and the return-page cookie expire when the browser is closed. The cookie that remembers the state during the sign-in steps lasts 15 minutes
- Values remembered in the browser (printer settings, payment settings, dismissed notices): they stay until you clear the browser's data. Signing out does not clear them
- Copies of emails sent through MailerSend: kept for the period MailerSend sets
- Copies of email content and send logs kept by our own mail system: we have not set a retention period, the system does not delete them automatically, and we delete them on your request
- Warehouse stock and supplier records, uploaded files (S3), the emails of billing managers and store owners in Billing, and other account data: kept for as long as you use the service, until you ask us to delete them
- Error data, usage logs and screen recordings at Sentry: kept for the period Sentry sets
- Sign-up data not yet confirmed with an OTP: no more than 24 hours
- Unfinished password reset records: no more than 15 minutes, and deleted as soon as the new password is set
- Tunder Print history on the device: 24 hours
- System logs of our services: the IP address from the Tunder Print app may appear in these logs. Each service keeps a limited log size, and older entries are overwritten automatically once it is full. We have not set a period as a number of days, and we do not use these logs for any other purpose (see the Tunder Print annex)
- Google Analytics data: kept for 2 months under the GA4 data retention setting
The only data the system deletes by itself is the following: sign-up data not yet confirmed with an OTP (24 hours), unfinished password reset records (15 minutes), Tunder Print history on the device (24 hours), system logs of our services whose older entries are overwritten once the limited log size is full, and cookies and sessions when they expire. The system does not automatically delete any other data when a period ends. We delete data on your request, as set out in Rights of the data subject. Data held by Sentry and MailerSend is kept for the period each provider sets, and Google Analytics data is kept for 2 months under the GA4 setting.
Rights of the data subject and how to exercise them
You have rights under the PDPA: to request access to and a copy of your data, to request correction, to request deletion or anonymization, to request that we restrict use, to receive your data or have it transferred to another controller, and to object to processing, for example screen recording and usage analytics, which you can also decline or withdraw consent for yourself at Cookie settings. Send a request by email to jeni.pukkham@gmail.com. We will reply and act within 30 days of the day we receive the request, and we may ask you to verify your identity first. Some data we must keep by law (for example bills and receipts), so we cannot delete it until the period has passed. At present the system has no delete-account button or request form in the app, so we accept requests by email only.
Withdrawal of consent
The data we keep with your consent is screen recording (Session Replay), usage events (Google Tag Manager / Analytics) and usage logs from your browser sent to Sentry. All of it runs only after you allow it in the cookie banner. Sentry error reports and POS server-side logs always run, on the basis of legitimate interests.
You may withdraw consent at any time (Section 19) by pressing Cookie settings and choosing again, category by category. Withdrawing is as easy as giving consent. For the details of the cookies, the tools and what happens when you withdraw, see the cookie policy, or contact us as set out in Data controller and contact. In Tunder POS, cookie settings are at the bottom of the side menu ("ตั้งค่าคุกกี้"), per user and per browser. On the website, use the cookie settings link or the button in the footer. Withdrawing consent does not affect processing that took place before you withdrew.
Right to complain to the PDPC
If you believe we have not complied with the PDPA, you have the right to complain to the Office of the Personal Data Protection Committee (PDPC). You may contact us first as set out in Data controller and contact, or complain to the PDPC at www.pdpc.or.th
Data security
- Account passwords are stored with one-way encryption
- The OTP code at sign-up and at password reset expires in 5 minutes, and a sign-in has a limited lifetime as stated in Data we collect
- Access is limited by the role of each store member
If a data breach that affects you occurs, we will notify you and the relevant authority as the law requires.
Store customer data
Data about customers that a store keeps in the system, such as name, telephone number, email, LINE, address, tax ID on a tax invoice, order history, members and coupons: the store is the data controller, and we are only a data processor that acts on the store's instructions, under the Data Processing Agreement (DPA), which is a separate document from this policy.
Changes to this policy
We may update this policy. Every version shows its version number and effective date, and older versions can still be viewed on the documents page. If the change is substantial, we will ask you to acknowledge or accept the new version in the system.
Tunder Print annex
Tunder Print is an app for stores that use the Tunder POS system. The app receives print jobs from the system and sends them to a receipt printer over Bluetooth or the device's built-in printer. This annex explains what data the app uses, where it is sent and how it can be deleted. The app provider is Jetniphan Pukkham, as set out in Data controller and contact
Summary of the app's data
| Data | Leaves the device | Shared with third parties | Purpose | Retention | How to delete |
|---|---|---|---|---|---|
| Device token (obtained by scanning the pairing QR) | Sent to our server, through Cloudflare's proxy | Not shared (Cloudflare is our service provider, see Recipients and sub-processors) | Verify that this device has the right to receive the store's print jobs | On the device: until the app's data is cleared or the app is uninstalled. On the server: until the store owner revokes it. After revocation the server still keeps a record that the token was revoked | The store owner revokes it in Tunder POS (see Deletion and contact) |
| Print job ID, such as the order ID | Sent to our server | Not shared | Request the document to print from the system | Not kept additionally by the app | No deletion needed |
| IP address (general connection data the server receives as normal) | Sent to our server, through Cloudflare's proxy | Not shared (the server is hosted by Hostinger and traffic passes through the proxy of Cloudflare, which are our service providers, see Recipients and sub-processors) | Connection and security of the service | The IP address may appear in the system logs of our services. Each service keeps a limited log size, and older entries are overwritten automatically | Nothing to do: older entries are overwritten automatically |
| Print history (order ID, document type, time, print result) | Not sent, kept on the device only | Not shared | Show what has already been printed in the app | 24 hours | Clear the app's data or uninstall the app |
| App settings and the paired printer ID | Not sent, kept on the device only | Not shared | Remember the printer and the values that were set | Until the app's data is cleared or the app is uninstalled | Clear the app's data or uninstall the app |
| The printed document itself (receipt, tax invoice, picking slip) | Does not leave; the app downloads it to print | Not shared | Print the document | The app does not save the document to the device | No deletion needed |
| Camera images | Not sent, not kept | Not shared | Scan the pairing QR only | Not kept | No deletion needed |
| Device location | Not sent, not kept | Not shared | Not used | Not kept | No deletion needed |
| Google ML Kit diagnostic data (Android only) | Sent by ML Kit to Google | Shared with Google | Google's QR reader sends diagnostic and usage data | As Google sets | Under Google's policy |
The data that leaves the device in the table above is necessary for the app to work. None of it is optional, except by not using the app at all.
Data the app sends to our server
- Device token: obtained by scanning a QR code to pair the app with the store. It is used to verify that this device has the right to receive the store's print jobs
- Route of the data: the app connects to the server through the domain client-print.tunderpos.com, which sits behind Cloudflare's proxy. The device token and the IP address therefore pass through this proxy before reaching our server. Cloudflare is a service provider acting for us, see Recipients and sub-processors
- Print job ID: such as the order ID, used to request the document to print from the system
- General connection data: such as the IP address, which the server receives as normal when a connection is made. The IP address may appear in the system logs of our services. Each service keeps a limited log size, and older entries are overwritten automatically. We have not set a period as a number of days, and we do not use these logs for any other purpose
Data the app receives from the system
The app downloads documents from the Tunder POS system to print, such as receipts, tax invoices and picking slips. These documents may contain order data or customer data that the store has recorded in the system. The app does not save the document to the device. The customer data in a document belongs to the store, as set out in Store customer data
Data stored on the device
- The device token and the app settings
- The ID of the paired printer
- Print history, such as order ID, document type, time and print result. The app keeps this history for 24 hours
This data is deleted when the app is uninstalled or the app's data is cleared.
Permissions the app asks for
- Camera: used only to scan a QR code to pair the app with the store. The app does not save images and does not send images to our server. On iPhone and iPad the app reads the QR code on the device with Apple Vision and sends nothing anywhere
- Nearby devices (Bluetooth): used to find and connect to the printer. The app does not use this permission to determine your location
- Location: asked for only on Android 11 and below, because the system requires this permission to scan for Bluetooth. The app does not keep or send location data
- Notifications and background operation: used to show status and to let the app keep receiving print jobs continuously
Google services
On Android only, the app uses Google ML Kit to read QR codes (on iPhone and iPad the app reads QR codes with Apple Vision on the device and does not use ML Kit). Google states that ML Kit sends diagnostic and usage data to Google over HTTPS, such as the device model and operating system, the app name and version, device or installation identifiers and performance metrics. See the details at Google ML Kit data disclosure
The app is installed through Google Play, so the use of Google Play is subject to Google's policies.
Disclosure and security
We do not sell data. The app has no advertising and does not include third-party analytics or crash-reporting services other than those stated above. The app connects to the server over HTTPS and encrypted connections.
Deletion and contact
The store owner can unpair a device in Tunder POS at the Service > Store Front > Print Client Pairing menu, then press "Revoke token" (store owners only). A store has a single token, so revoking it cuts off every device paired to that store: the app can no longer download documents and is refused when it reconnects. The server keeps a record that the token was revoked. Data on the device can be deleted by clearing the app's data or uninstalling the app.
To exercise rights regarding personal data or to ask a question, contact jeni.pukkham@gmail.com as set out in Rights of the data subject and how to exercise them.