Privacy Policy

TUKTUKVPN is operated by IDEACLE COMPANY LIMITED, a company registered in Thailand. This page describes what we keep, why, and how long.

What we keep

Our production logging system records connection events received from connected VPN servers and protocols. A recent production readback observed the event time, source network address and port, service, node label, and user or account mapping where available. That readback confirmed active ingestion, but an authoritative inventory of every production node and protocol has not yet been reconciled against the records.

The recent field inventory contained connection metadata rather than destination, DNS-query, or browsing-history fields. Connection records follow a 91-day operational retention schedule, satisfying the Thai-law minimum described below. A daily expiry job deletes eligible archives after that boundary; off-machine copies can complete their storage lifecycle later. A lawful preservation order can require a specific record to be retained longer.

The rest of what we keep belongs to your account:

• Your account: email address, display name, profile image, locale, and an account identifier.
• Your devices: a per-device identifier, the platform, and the hardware model — so we can enforce the device limit in your plan and let you revoke a device.
• A cumulative total of the data you have used against your plan. It is a quota counter, not a per-session history.
• Your subscription status.
• Crash reports, so we can fix defects. A report describes the failure — the app and system version, the device model and a stack trace — and can include details tied to your installation, such as where the app is installed (on a Mac, that location contains your macOS account name). Credentials are removed from reports before they are sent.
• Website measurement data — only after you accept the website cookie banner. Google Analytics 4 and PostHog measure page visits and product interactions so we can understand and improve the website. Meta Pixel measures visits to eligible public marketing pages for advertising measurement. We do not send form contents, email addresses, payment details, account pages, admin pages, or native sign-in pages to these tools. URL query strings are excluded except syntax-validated advertising campaign identifiers such as `fbclid` and `utm_*` on eligible public pages. Provider requests also include technical browser/device information and the network IP address; providers may derive a general region from that address and use their cookie or installation identifiers for measurement.
• When enabled, our own website measurement also connects a consented public-page visit to a payment confirmed by its payment provider. It records a random browser context, your consent version and choice, a public landing path without its query string, selected campaign categories, and the payment provider, amount and currency. A hashed payment reference prevents duplicate counts. These records are pseudonymous and can still be linked to operational payment records; they are not anonymous. The measurement tables do not contain your email, account ID, card details, VPN traffic or destinations. This internal measurement does not send purchase events to Google, Meta or PostHog. Its collection window is at most 30 days, does not extend on return visits, and is followed by scheduled deletion. Payment processing and accounting records have separate purposes and lifecycles.
• Optional app measurement — only after you accept the current app disclosure and enable Analytics in the privacy settings. Firebase Analytics measures app lifecycle/usage events and a manual app screen view on iOS and macOS. Android automatic screen reporting is disabled and this integration does not add a manual Android screen event. It uses an app installation identifier and can derive a general region from the network IP address. Where supported by the store integration, the SDK may also automatically measure in-app purchases/subscriptions, including product identifiers, names, and prices. Updated apps do not send Meta App Events and keep advertising storage, advertising user data, and ad personalization disabled even when Analytics is enabled. Older versions that include Meta App Events may send a manual activation event on iOS and Android until you update or disable Analytics. We do not add account details, email, payment credentials, or VPN traffic/destinations to these events. You can disable optional measurement in the app settings. Choosing Facebook Login is separate and does not enable Analytics.

Thai law and retention

As a service provider registered in Thailand, we are subject to Section 26 of the Computer-Related Crime Act B.E. 2550, which requires service providers to retain computer traffic data for not less than 90 days from the date the data enters the system, and allows a competent official to order retention of up to two years in an individual case. We comply with that obligation and with lawful requests made under it by Thai authorities.

Our retained connection-event schema identifies when a connection occurred, the source network address and port, the service and node label, and the associated user or account mapping where available. The records are held on a separate log server. Append-only audit records and a daily hash chain are designed to reveal alteration, and access through the query endpoint is logged. Authorized root administrators technically retain the ability to change the system.

This connection-event retention supports our legal duties under Section 26. It is separate from commercial analytics and advertising measurement.

Sharing

We do not sell your data. With your consent, we use limited website visit data for analytics and advertising measurement through Google Analytics 4, PostHog, and Meta Pixel. These providers process that website data for us under their applicable terms. If you enable optional app Analytics, Firebase processes the app measurement data described above. Older iOS/Android app versions that include Meta App Events may also send their manual activation event to Meta; updated apps remove that integration. This measurement never includes the traffic, destinations, DNS queries, or browsing activity that pass through the VPN tunnel. We also share the minimum necessary with service providers who perform a function for us — crash reporting, payment processing, and delivery of sign-in emails — and with Thai authorities to the extent the law compels.

Website analytics and advertising choices

Analytics and advertising scripts remain off until you accept, and Do Not Track is treated as a rejection. You can change or withdraw your choice at any time using the always-visible Cookie settings button. Withdrawal stops future website measurement; you may also clear existing cookies in your browser. Rejecting these cookies does not prevent you from using the VPN service or accessing the public website. For our own payment measurement, withdrawal also excludes the browser context from future conversion totals; the remaining measurement records expire through the scheduled deletion process described above.

Deleting your account

You can delete your account from Settings in the app, or request deletion using the instructions at tuktukvpn.com/delete-account. Deletion can be undone during a grace period, after which your account and its records are erased — except where Section 26 requires data to be kept for the statutory period.

Exact retention periods for account data, and our compliance programme under Thailand's PDPA, are being finalised with legal counsel.