ThaiNamthip Corporation Limited respects the privacy of users of the ThaiNamThip Application (the “Application”). This Privacy Policy explains what personal data may be collected through the Application, how the data is used, how it may be shared, how long it is retained, and the choices available to users.
Privacy information at a glance
| Data Controller | ThaiNamthip Corporation Limited |
| Application developer / technical service provider | Eventthai Company Limited |
| Conference check-in date | 3 December 2026 |
| Check-in venue | PEACH Hall AB, Pattaya |
| Planned retention period | November 2026 through January 2027 |
| Account access model | Invitation-only. The event organizer provides the attendee information required to provision an account, and the system sends an invitation email with a temporary system-generated password for initial sign-in. |
| Profile management | After signing in, users may change their password and update their profile photo in the Application. |
| Location data and Beacon attendance flow | The Application may access Approximate Location, Precise Location, and Background Location, together with Bluetooth / Nearby Devices permissions, to support Bluetooth Low Energy (BLE) and Beacon detection. Background access may continue when the Application is not actively displayed so that automatic event check-in/check-out can function. For the event on 3 December 2026 at PEACH Hall AB, Pattaya, these permissions are used only for the attendance feature and status updates such as Waiting to Check In, Checked In, and Checked Out. |
1. Scope of this Privacy Policy
This Privacy Policy applies to the ThaiNamThip Application and the personal data processed through the Application in connection with attendee invitations, account access, profile management, event participation, attendee QR-code functions, application analytics, and beacon-based event check-in/check-out functionality.
This Policy is intended to describe the Application as operated for the relevant ThaiNamThip conference and related attendee activities. Where a third-party website or service is opened from the Application, that third party may process information under its own privacy policy.
2. Data Controller and Application Developer
Data Controller: ThaiNamthip Corporation Limited.
Application developer and technical service provider: Eventthai Company Limited.
Eventthai Company Limited may process personal data as necessary to develop, operate, maintain, support, and troubleshoot the Application on behalf of ThaiNamthip Corporation Limited and in accordance with the purposes described in this Privacy Policy.
3. Personal Data We May Collect
The categories of information collected depend on the features used and the information provided by the user. The Application may process the following categories of data:
3.1 Invitation, account access and profile information
- The ThaiNamThip Application is an invitation-only application for invited conference attendees. Before the event, the event organizer provides the attendee information required to provision an account, such as the attendee name and registered email address. The Application is not intended for open public self-registration.
- After an attendee account has been provisioned, an invitation email is sent to the attendee's registered email address. The invitation provides application access instructions and a temporary system-generated password for initial sign-in. The temporary password is used only to enable access to the invited account, and the user may change the password after signing in.
- The Application processes account and profile information necessary to provide access, including the attendee's name, registered email address, account status, authentication information, password-change information, and profile information. After signing in, the user may change the password and may replace or update the profile photo. The user may either select an existing image from the device or take a new photo using the device camera. The selected or captured image may be processed, stored, and displayed as part of the attendee profile for the duration of the conference service.
- Account access flow: (1) the attendee receives an invitation email, (2) the attendee signs in using the registered email address and temporary system-generated password, (3) the attendee may change the password in the Application, and (4) the attendee may update the profile photo. On the event date, beacon detection is used separately for automatic attendance check-in/check-out.
3.2 Event participation and attendee QR-code information
- Registration and attendee status.
- Attendee QR-code or attendee identifiers, event access status, and check-in/check-out status where used by the event.
- Information generated when the user opens or uses attendee access, event benefits, or attendee services within the Application.
- The attendee QR code and related attendee status may be used to support event access, attendee identification, and event operations where enabled by the organizer.
3.3 Location data and Bluetooth/Beacon-based event check-in and check-out
Location permissions used by the Application. On Android devices, the Application may request and access Approximate Location and Precise Location. The Application may also request Background Location permission and may use a location-related foreground service so that Bluetooth Low Energy (BLE) / Beacon detection can continue when the Application is not actively displayed on the screen. These permissions support the automatic event attendance feature described below.
Background location access. When the user has granted the relevant permission, the Application may access location-related information while the Application is in the background or while the user is using other applications. This background access is used only to maintain BLE / Beacon proximity detection for automatic check-in and check-out. It is not used for advertising, marketing profiles, navigation, or unrelated tracking.
Bluetooth and Nearby Devices. The Application may use Bluetooth permissions, including Bluetooth scanning, connection, and related BLE operations, to detect configured event Beacons. These Bluetooth permissions work together with location-related permissions where required by Android.
For the event held on 3 December 2026 at PEACH Hall AB, Pattaya, the Application uses Bluetooth / Nearby Devices and location-related permissions to determine whether an invited attendee is within proximity of the configured event Beacon area. Before a Beacon check-in is detected, the Application may display the attendee status as 'Waiting to Check In'. When the attendee enters the configured Beacon area, the Application may automatically update the status to 'Checked In'. When the system determines that the attendee has left the configured event area, the status may be updated to 'Checked Out'.
The purpose of location access is limited to enabling Bluetooth/Beacon detection and proximity-based automatic check-in/check-out for the conference. The Application does not use location data for advertising, marketing profiles, navigation, or unrelated analytics. The Application does not intentionally use the location permission to build a continuous GPS movement history. Attendance records may include check-in/check-out status and related timestamps generated from Beacon proximity detection.
Location data is not sold and is not shared with third parties for advertising purposes. Location-related information may be processed by ThaiNamthip Corporation Limited, Eventthai Company Limited, and technical service providers only where necessary to operate, support, secure, or troubleshoot the Beacon attendance function, subject to the safeguards described in this Privacy Policy.
3.4 Device and technical information
- Device type, operating system, application version, device or application identifiers, and technical diagnostic information.
- Crash, error, and performance information used to maintain the stability and security of the Application.
3.5 Analytics and technical usage information
The Application may use analytics technologies to understand application usage, measure feature engagement, diagnose issues, and improve application performance and reliability. Such information may include application interactions, event names, device or application identifiers, and technical metadata.
4. Purposes of Processing
Personal data may be processed for the following purposes:
- To provision invitation-only attendee accounts, send invitation emails and temporary access credentials, authenticate users, allow users to change their password, and provide access to the Application and conference services.
- To manage attendee identity, attendee QR codes, profile information and profile photos, event services, and attendance status.
- To access Approximate Location, Precise Location, and, where permission is granted, Background Location, and to use Bluetooth / Nearby Devices and Beacon proximity detection to perform automatic check-in and check-out and display the latest attendance status for the event on 3 December 2026 at PEACH Hall AB, Pattaya.
- To analyze application usage and improve usability, performance, reliability, and service quality.
- To understand application usage and feature engagement through analytics where enabled.
- To prevent misuse, investigate technical incidents, and protect the security of the Application and its users.
- To comply with applicable legal, regulatory, or contractual obligations.
5. Permissions Used by the Application
Depending on the user’s device and the features enabled, the Application may request permissions necessary to operate specific functions. These may include:
- Approximate Location: may be requested to support BLE / Beacon scanning and proximity-based attendance detection.
- Precise Location: may be requested where required by the Android device or operating-system version to support reliable BLE / Beacon detection for automatic check-in/check-out.
- Background Location: may be requested so that Beacon detection can continue when the Application is not actively displayed, allowing the Application to update check-in/check-out status when the user enters or leaves the configured event Beacon area.
- Location-related foreground service: the Application may run a foreground service associated with location / Beacon detection to maintain the event attendance function in accordance with Android requirements.
- Bluetooth / Nearby Devices: Bluetooth scanning, connection, and related BLE permissions may be used to discover and interact with configured event Beacons for automatic check-in and check-out.
- Notifications: the Android application may request notification permission where required by the operating system. Notification-based features will only be used if enabled for the event and may be managed by the user through device settings.
- Camera: may be accessed when the user chooses to take a new photo for use as the attendee profile picture. Camera access is used only for capturing the profile image initiated by the user and is not used for continuous recording, background capture, advertising, or unrelated monitoring.
- Photo or media access: may be requested when the user chooses to select or upload an existing profile photo from the device. The Application accesses the selected image only for the purpose of updating the attendee profile, unless another clearly identified media feature is enabled.
Permissions can generally be managed through the device settings. Disabling a permission may prevent the related feature from working correctly.
6. Analytics and Third-Party Service Providers
The Application may use third-party technology providers to operate, secure, analyze, and improve the Application. These providers may process limited technical or usage data necessary to provide their services.
- Firebase services, which may be used for application analytics, crash reporting, or related technical functions.
- Hosting, email delivery, attendee-service, and other technical service providers used to deliver invitation messages, account access, and enabled Application functions.
Third-party providers process data under their own terms and privacy practices and, where applicable, under agreements with the Data Controller or service provider. The Application should only enable third-party services that are required for the actual operation of the Application.
7. Disclosure and Sharing of Personal Data
Personal data may be shared only where necessary for the purposes described in this Policy, including with:
Location data: The Application may access Approximate Location, Precise Location, and Background Location for the Beacon-based attendance function. Location data is not sold and is not shared with third parties for advertising. Any location-related processing by ThaiNamthip Corporation Limited, Eventthai Company Limited, or technical service providers is limited to operating, supporting, securing, or troubleshooting the Beacon-based attendance function.
- ThaiNamthip Corporation Limited and authorized personnel involved in conference management.
- Eventthai Company Limited for application development, operation, maintenance, support, and troubleshooting.
- Technology, hosting, analytics, messaging, email delivery, and attendee-service providers that support the Application.
- Authorities or other parties where disclosure is required by applicable law, a lawful request, or to protect legal rights and security.
Personal data is not shared with third parties for unrelated purposes without an appropriate legal basis or the user’s consent where consent is required.
8. Data Retention
Personal data collected for the conference and the operation of the ThaiNamThip Application, including invitation and account information, profile information and profile photos, attendee QR-code information, and check-in/check-out records, is intended to be retained during the conference service period from November 2026 through January 2027. After the applicable retention period, personal data will be deleted, anonymized, or otherwise securely disposed of, unless continued retention is required for legal, security, dispute-resolution, or other legitimate purposes.
A user may request deletion earlier, subject to information that must be retained for legal, security, transaction, dispute-resolution, or other legitimate requirements.
The Application may access location-related information in the foreground and background as necessary for the Beacon attendance feature. The Application does not intentionally use this feature to build a continuous GPS movement history. Attendance records retained for the conference may include the resulting check-in/check-out status and related timestamps.
9. Data Security
Reasonable administrative, technical, and organizational measures are used to protect personal data against unauthorized access, loss, misuse, alteration, disclosure, or destruction. Access to personal data is limited to personnel and service providers who require access for authorized purposes.
No method of electronic transmission or storage can be guaranteed to be completely secure. The invitation email and temporary password are intended only for the invited attendee and should not be shared with other persons. Users may change the temporary password after signing in and should protect their account credentials and device access.
10. User Rights and Choices
Subject to applicable law, users may have the right to request access to, correction of, deletion of, restriction of, or objection to certain processing of their personal data, and may withdraw consent where processing is based on consent. Users may also manage device permissions and notification settings through their device settings.
Requests will be reviewed and handled in accordance with applicable law and may require reasonable identity verification.
11. Account and Data Deletion Requests
Accounts for this Application are provisioned for invited attendees by the event organizer rather than created through an open public self-registration flow. A user who no longer wishes to use the invited account may request deletion of the account or associated personal data by contacting Eventthai Support using the contact details below.
Upon a valid deletion request, personal data associated with the account will be deleted or anonymized unless specific information must be retained for legal, security, transaction, or dispute-resolution purposes.
12. International Processing
Some technology providers used by the Application may process or store data using systems located outside Thailand. Where cross-border processing occurs, reasonable measures will be used to protect personal data in accordance with applicable legal requirements and contractual safeguards.
13. Changes to this Privacy Policy
This Privacy Policy may be updated when the Application, conference services, legal requirements, or data-processing practices change. The current version will be made available through the Application or the official Privacy Policy webpage. The effective date shown at the top of this Policy will indicate the latest revision.
14. Location Permission Notice
Before requesting location permission, the Application may present an in-app notice explaining that location access, including background location where permitted, is used to enable Bluetooth Beacon detection for automatic event check-in and check-out. Users may deny or later revoke location permission through the device settings; however, the automatic Beacon attendance feature may then be unavailable or may not work reliably.
15. Contact Information
For questions, privacy requests, password/account assistance, or requests relating to personal data, please contact Eventthai Support using the contact details below:
| Company | Eventthai Company Limited |
| Contact person | Eventthai Support Staff |
| Address | 47/313 Kai Tak Building, 5th Floor, Popular Road, Pak Kret, Nontaburi 11120 |
| Phone | 064-185-2833 |
| LINE ID | @Eventpass |
| Data Controller | ThaiNamthip Corporation Limited |
End of Privacy Policy