Privacy Policy

https://mylamduan.com/ is operated by Lamduan, the data controller under Thailand's Personal Data Protection Act B.E. 2562 (PDPA).

For anything to do with your personal data, write to admin@mylamduan.com — access requests, corrections, deletion, or withdrawing consent.

Account data

• Username, email and password (the password is stored as a one-way hash — nobody can read it back, not even the site owner)
• Your display name and the gender you selected
• Date of birth and height (both optional — used for age, BMI, BMR and TDEE)
• Your language choice and the date you registered

Health data (sensitive personal data under PDPA section 26)

• Weight, body fat percentage, muscle mass, neck, waist and hip measurements, cycle day, bowel movements and daily notes
• Carbs, protein, fat, times, meal types and the names of foods you ate
• Activity types, training times and minutes spent in each heart-rate zone
• Your fasting and eating windows
• A daily answer for whether you drank alcohol and what kind (spirits, beer, wine, cocktail) — only whether and what, never how much
• Only if you connect your phone's health app yourself — weight and body-fat percentage read from Apple Health or Health Connect. They land in the same fields you type into; only the source differs. See the health-app section below
• Only if you import workouts yourself (iPhone) — the kind of activity, date, start time and minutes in each heart-rate zone of workouts in Apple Health. No heart-rate figures are kept: heart rate is used on your phone to count the minutes, then discarded

Technical data

• Your IP address temporarily, for at most 15 minutes, purely to rate-limit failed logins, then deleted automatically
• Mobile app tokens, stored only as hashes — never the token itself
• Only if you turn notifications on in the mobile app — a device token for delivering them, alongside the platform, app version, language and the time that device was last used. The notifications section below has the detail

Site statistics

• The site uses Google Analytics 4 to record which pages get opened, where visitors arrive from, what device they use and roughly which country they are in. GA4 does not store IP addresses in its reports; it uses them briefly to estimate a city-level location and then discards them.
• The site is also connected to Google Search Console, which collects nothing from your browser at all and sets no cookies. It reports to the site owner which search terms led people here, as aggregate counts that identify nobody.
• Inside the mobile app nothing is measured at all. Google Analytics runs only when the site is opened in a web browser. Opened as the app, the whole statistics layer is switched off.

• Account data — necessary to provide the service; without it there is no way to tell whose rows are whose
• Health data — held on the basis of the explicit consent you give at registration, as PDPA section 26 requires. You may withdraw it at any time
• Technical data — legitimate interest in keeping the system secure
• Site statistics (Google Analytics) — legitimate interest in knowing which writing gets read and which screens are hard to use. Not sensitive data, and not tied to your account. You can refuse it — see the cookies section

Everything is used only to show you your own history, averages and charts. It is never used for advertising, never sold, never traded. No automated decision-making with legal effect is performed on it.

• You — you see only your own data; every query is scoped to your account
• The site owner — technically has database access as the server owner, but only looks when a system problem requires it
• The hosting provider — keeps the server the data sits on
• Google Analytics — sees which pages were opened, when, from what kind of device, and roughly which country. It is processed on Google servers that may sit outside Thailand, under the safeguards Google publishes. No health data goes with it
• Google Search Console — receives nothing from your browser. It works from Google's own search logs and reports aggregate counts to the site owner
• Google Firebase Cloud Messaging — only if you turn notifications on. Google carries the message to your device, so it sees the device token and the text. It runs on Google servers that may sit outside Thailand. No health figures travel with the message

Beyond that, data is disclosed only where the law compels it.

• Health and account data are kept as long as the account exists — long-term history is the entire point of the service
• Deleting your account deletes every row in every system immediately and permanently. No copy is retained
• Rate-limiting IP records are deleted automatically within 15 minutes
• App tokens expire automatically after 30 days of no use
• Notification device tokens are deleted the moment you turn notifications off, sign that device out, delete your account, or Google reports the app was uninstalled there

Under the PDPA you have the rights below, and most of them are wired into the site so you can exercise them yourself:

• Access and get a copy — do it yourself on the export page, as CSV or a full backup. No permission needed
• Correct your data — every row is editable from its own page; name and gender from your profile
• Erasure — delete rows yourself, delete the whole account permanently from the mobile app, or ask by email
• Withdraw consent — new health data then stops being recorded, and you can ask for the existing data to be deleted
• Object to or restrict processing
• Complain — to Thailand's Personal Data Protection Committee office if you believe this site is in the wrong

Email requests are handled within 30 days.

Mobile notifications are off until you turn them on. Nothing about them is stored before that.

What is stored once they are on

• A device token Google issues to the app on that device — the thing that makes delivery possible. It is not your device name or serial number, and it does not say where you are
• The platform (iOS or Android), the app version, the language, and when that device was last used
• Which notifications you asked for, and the time of day you asked for them

These are kept per device, not per person. A phone and a tablet belonging to the same person are two rows, so turning one off never silences the other.

Who carries them

They go through Google's Firebase Cloud Messaging, the only route iOS and Android permit for delivering notifications. Google therefore sees the device token and the text. It runs on Google servers that may sit outside Thailand.

What is inside a notification

One short line — that a fast reached its target, or an hour milestone during a long one.

The reminder the phone schedules itself — the server is not involved

One of them works a different way entirely: "Remind me to start my fast", on the profile page. Switch it on and the app hands the time to the phone's own operating system, which then reminds itself every day.

• No device token, nothing sent to the server, and Google plays no part — it arrives with the network switched off
• The time you chose lives on that one device. It is not attached to your account: set it on a phone and a tablet knows nothing about it
• The text is one line — that it is time to start — with no figure of yours in it, same as the rest
• Turn the switch off, or uninstall the app, and the scheduled time goes with the device

Stopping

Turn them off in the app, or in the device settings. The device token is deleted from the database immediately, and if Google reports the app was uninstalled from a device, the token there is dropped without waiting to be told.

Mobile app only, and off until you turn it on — nothing happens unless you press "Connect" on the weight page or "Import workouts" on the exercise page yourself. The two ask for permission separately.

What is read

• Weight page: weight and body-fat percentage. What is read becomes a weight entry in this site's database, exactly as if you had typed it
• Exercise page (iPhone only): workouts and heart rate during them. The minutes in each zone are the ones Apple worked out when it has them (iOS 27 and later); otherwise the app counts them on your phone from heart rate (zones from 220 minus your age). Only the kind of activity, date, start time and minutes per zone are sent. Heart-rate figures never leave your phone and are not stored by this site. Workouts with neither zones nor heart rate are not imported. After you press Import the first time, new workouts are brought in by themselves when you open the app (at most every 10 minutes); withdrawing permission in your phone's settings stops it at once
• Not steps, sleep, cycle, or anything else your health app holds
• Nothing you filled in yourself is overwritten or duplicated. Yours always wins. An imported workout you delete is not brought back by a later import

What is written back

One thing: the weight you record in Lamduan, so the other apps you use can see it too. Nothing else is written.

Who grants it

Your phone asks and your phone keeps the answer — not this website. Lamduan can only ask. You may refuse, and you may withdraw later at any time in your device settings (iOS: Settings > Health > Data Access & Devices · Android: Health Connect > App permissions). Withdrawing stops the import immediately; data already imported stays in your log and can be deleted exactly like any other entry.

Cookies the site needs to work

• lamduan_lang — remembers your language, one year
• lamduan_app — remembers you opened the site as an installed app, one year
• lamduan_theme — remembers the colour theme you picked
• WordPress standard login cookies — keep you signed in

Browser storage (localStorage)

All of it stays on the device. None of it is sent to the server and none of it is attached to your account; clearing browser data or uninstalling the app takes all of it with you:

• lamduan_install_dismissed — whether you dismissed the install banner
• lamduan_push_asked and lamduan_push_pending — whether the notification permission has already been asked for, so you are not asked over and over
• lamduan_lock — whether "Lock the app on this device" is on. No face, no fingerprint and no device passcode is in here. Those belong to the operating system and the app never sees them; what is stored is a single 1 meaning "ask first"
• lamduan_unlocked — whether the lock has already been passed in this visit, so it does not ask again on every page · kept in temporary storage (sessionStorage), gone when the app is closed and cleared when you leave the app for more than a minute
• lamduan_remind_fast and lamduan_remind_at — whether the start-your-fast reminder is on, and the time you set
• lamduan_health_on and lamduan_health_sent — whether you have connected your phone's health app, and the date of the last weight written back to it. Only the date, never the number — used only when the app is not allowed to read from the health app, so the same day is not written twice

Statistics cookies

• _ga and _ga_XXXXXXXX — Google Analytics, used to tell a returning browser from a new one. Two years.

No advertising cookies, and no cross-site tracking for retargeting.

• HTTPS on every page
• Passwords are one-way hashes; so are app tokens. A database leak cannot be replayed as a login
• More than 10 failed logins from one IP triggers a 15-minute lockout

No system is completely safe. Use a password you do not reuse elsewhere, and download your own backup from time to time.

Minors — under the PDPA, anyone under 20 needs a guardian's consent before providing personal data. This site is not designed for children under 13; if data from a child under 13 is found to have been collected without guardian consent, it will be deleted immediately.

If the substance changes, the version number at the foot of this page moves and members are asked to consent again before continuing. Minor wording fixes only update the effective date.