Privacy notice
This notice says what this website collects, when, who receives it, how long it is kept, and how you can use your rights. Every point describes what the system actually does. It is published to inform you under Thailand's Personal Data Protection Act B.E. 2562 (2019) and, for visitors from Europe, under the GDPR.
1. Who is responsible for your data
The data controller of this website is Sukhothai Province (
To contact us about personal data:
- Nong Plaka, the site's chat (the chat button at the bottom right of every page) — type, for example, “delete my data”: Nong Plaka tells you what you can do yourself at once, and how to reach a member of staff
- Sukhothai Provincial Office (
สำนักงานจังหวัดสุโขทัย ), phone 055-611-619 - Send a message to the admin (Facebook)
- The other channels on the Contact page
2. What we collect, and when
In this notice “admin” means the organiser's admins and the system operators assigned by the province. They reach the data through the admin pages, or through a system connection (MCP) that needs their own Google sign-in and an explicit consent step before it connects. The chat log, the chat feedback, the visitor-group statistics, the “near me” counts and the stay searches can be opened only by system-owner accounts; ordinary admin accounts cannot see them.
| When you… | What is kept | What is not kept |
|---|---|---|
| open a page | How many times each page is opened per day, and how many times some content is seen or tapped (for example news, films, directions links) · Taps on a directions link Nong Plaka gives in the chat, in the “What's new” list, and on a gallery post's or promotion's directions button: counted per day by the place's or the shop's code (the link itself is not kept) — shops in “ครั้งหนึ่ง ณ สุโขทัย” see how many times people tapped the way to their own shop · A visitor-count code, computed one way from the IP address and browser details with the system's secret key, used to tell whether it is the same device (it cannot be turned back into an IP address without that key) · Daily counters by category: country, province (within Thailand only), device type, operating system, browser, page language, how you arrived (for example Facebook, LINE, a search, a QR code on print) and whether this is a first visit — counters, not a record of each person (visitors from Europe: see section 6) | IP address, the full browser string (User-Agent), the full referring link, city, coordinates |
| chat with Nong Plaka | The question and the answer, time, language, the page you asked on, the question's place in the conversation, and a random conversation code that links the questions of one conversation (the code stays on your device until you close the tab or tap “Clear conversation”) · Phone numbers, e-mail addresses and ids containing @ in a question are masked before it is kept · The same categories as the row above (country, province, device, operating system, browser, how you arrived, first visit or not), kept with that question · When you share your location for a “near me” question: only a count is kept — the day, the hour, a broad zone (in the old town, a sub-area about 300 m across named after the nearest landmark, such as Wat Mahathat or Wat Traphang Thong / town / other district / outside the province / outside Thailand) and what you looked for. The position is not kept, and the count is not tied to you or your conversation | IP address, name or account, a photo you attach (sent to the AI to answer, then not kept), your approximate location (once you allow location, the chat uses your approximate position with your questions while the page is open; used to answer, then not kept; the stored answer has no distances in it) |
| answer Nong Plaka's short questions (no longer asked) | Since 23 October 2026 Nong Plaka no longer asks the short questions in the chat, so no new answers are collected · Answers tapped before then (age band, who you came with, gender, the province or country you came from, and whether it was your first time — only the ones tapped, as broad choices, linked to that conversation's code only) are kept as in section 7, and your rights in section 8 apply to them · They were never asked of visitors from the European Union, the European Economic Area, the United Kingdom and Switzerland | Name, date of birth, phone number |
| rate your satisfaction / write us a comment | The 1–5 satisfaction score you tap, the text you write (if any), the number of questions in the conversation, language, page, and a code computed one way from the IP address (to stop repeated sending) · Nong Plaka asks for it once per conversation, at the end (after at least 2 answers, when you go quiet or say thanks); you can ignore it and keep chatting · The score is not linked to the conversation's code, and no question or answer is kept with it (the retired 👍/👎 under each answer also kept that question and answer) | Name |
| teach Nong Plaka | What you teach: knowledge, or a shop's details (name, details, hours, map link and an attached photo), and a code computed one way from the IP address (a daily limit) · What you teach waits for an admin's review before Nong Plaka uses it; once approved it is information Nong Plaka uses to answer everyone · An attached photo is stored as a file of the site from the moment it is attached; the camera data in the file is removed before it is stored | The teacher's name |
| save a trip / comment on a trip | The plan, saved shops, the trip's title, language · Comments: the name you type, the text, an attached photo (camera data removed before it is stored) and votes · a code computed one way from the IP address | A user account (there is none) — anyone with the trip link can open it, edit it and comment, and a trip you make public is shown on the trip board, so do not put personal details in it |
| order through Nong Plaka | The items, quantity, your name, a contact, how you will receive the goods, extra details, language, and a code computed one way from the IP address | Payment details (the site takes no payment) |
| apply as a partner shop | Shop name, contact person, phone, LINE ID, e-mail, district, address, map link and shop location, website, products, PromptPay number (if given), a note, a shop-front photo, the consent text and when you gave it, and a code computed one way from the IP address · Copies of identity documents: kept apart from the site's public files, opened only by admins, and every opening is logged | — |
| apply to join “ครั้งหนึ่ง ณ สุโขทัย” | Display name, a phone number (required) and a LINE ID (if given) — seen only by admins and the system operators assigned by the province · for a shop: what it sells, the festival zone it chose, and its location (shared with the button, or a pin the shop or an admin placed on the map / read from a Google Maps link, with who placed it and when), used for the directions link shown with its photos — until 25 Nov 2026 a shop whose location is outside the festival grounds is linked to the zone it chose · 1–3 sample product photos of the shop (resized on your phone before sending, and the camera data removed before they are kept): only an admin sees them, they are shown nowhere on the site · a link to the shop's page (optional): an admin sees it before approving, and once the shop is approved it is shown as a “Shop page” link beside the shop's photos — it is a link the shop entered itself and we do not check what it leads to · Details that are not complete yet are kept and asked for again when you open the status or come to post — an admin can approve once they are complete: team member = name and phone, shop = shop name, phone, what it sells, sample product photos and the shop location · The version of the agreement you accepted, and when · The device key: only a one-way transformed value is kept | — |
| register as a visitor to share photos (in the Nong Plaka chat) | Display name · the version of the agreement you accepted (the text that makes you responsible for the photos you post), and when · The device key: only a one-way transformed value is kept · a code computed one way from the IP address (limits registrations per day) · The photos and clips you send are kept aside and shown nowhere on the site (the gallery, the “What's new” list, Nong Plaka's answers) until an admin has reviewed and approved them (an admin plays a clip before approving it) — one that is not approved is deleted; an approved one is shown with the label “Photo from a visitor: display name” or “Clip from a visitor: display name” | A phone number, e-mail or any contact — there is no password and no account |
| register as a visitor with a LINE or Google account (optional — registering with a name only works too) | The display name the provider sends back (you can change it before confirming) · a code computed one way from that account's id with the system's secret key, with the name of the provider used (LINE or Google) — used to recognise the same account, to give a new phone a new key (the older phone can no longer post) and so that a block stays with the account · You are sent to LINE's or Google's own sign-in page; no code of the provider runs on our pages · when the provider sends you back, the page's address carries a temporary one-time code, which is removed from the address bar as soon as the page opens · When you stop being registered the account code is erased, except for an account an admin has blocked: that code is kept so that the block still holds | The e-mail address, the profile picture, the real account id, and any token or password of that account — the e-mail permission is not requested |
| give a heart, share, or look at the ranking in “ครั้งหนึ่ง ณ สุโขทัย” | Hearts: the account id of the person who gave the heart (an account registered with LINE or Google, or a team member or shop an admin has approved), kept with the post and the time — when the heart is taken back the entry is deleted · the names of people who gave hearts are not shown anywhere, only the counts · The counts and the nightly ranking are public, and are shown with the poster's public label (the display name, or the shop's name) — when the counting time of a night has passed, the system records the closed ranking (the posts, their hearts and the closing time) once, and does not change it again · Registering only to give hearts: what is received from LINE or Google is the same as in the sign-in row above (the display name and the one-way code), but the consent that makes you responsible for the photos is not asked until you post a photo or clip for the first time — then it is asked once · Share buttons: when you tap one, the system counts one tap (not who, and not whether the share was completed) — each tap is also counted per day against the post's id, and the post's owner sees only that number, not who tapped · The page of each post (/m/post-id): it shows only a post that is publicly visible, and holds no key or account data of anyone | The names of people who gave hearts, shown to others · who tapped share · the site sends nothing to LINE, Facebook or X until you tap that service's own button (section 5) |
| comment under a photo or clip in “ครั้งหนึ่ง ณ สุโขทัย”, and report a comment | Comments: the text you type, kept with the writer's account id, the post it is on, the time and the state (shown, waiting for an admin, hidden, removed, or deleted by the writer) — shown to everyone with the account's public label (the display name, or the shop's name) and the time · For safety, text that passes the system's first check (only the text, with no name, account id or post) is sent to OpenAI's automated safety-check service (section 5). A comment that the system or the service marks is read by an admin before anyone else can see it. A comment the system does not accept (for example one with a swear word, a link or a phone number) is not kept; the system counts only how many · Reports: the reason chosen, the time and who reported (the account id of a registered reporter, or a code computed one way from the network address of a reporter who is not registered — that code is replaced by a random code after 30 days) · Daily counters not linked to a person: comments shown, not accepted, waiting, removed, reports, and comments the automated check could not read · Words an admin adds to the check list: the word, its level, who added it and when | The text of a comment the system does not accept · names and account ids sent to OpenAI (none are sent) · the network address of a reporter · the text of a comment in the system's moderation log · the text of a comment an admin removed or its writer deleted (it is erased) |
| a shop puts up a promotion, a visitor reports one · a shop turns on “Message the shop on LINE” | Promotions: the text the shop typed, kept with the shop's id, the time, the end time, the attached post (if any) and the state (shown, waiting for an admin, hidden, or ended) — shown to everyone with the shop's name and marked as the shop's own words; the organiser has not checked prices or conditions. A text the system does not accept (for example one with a swear word, a link or a phone number, or about alcohol, tobacco, cannabis or a prize draw) is not kept · Reports about a promotion: the reason chosen, the time and who reported (the account id of a registered reporter, or a code computed one way from the network address of a reporter who is not registered — that code is replaced by a random code after 30 days) · Taps on “Directions to the shop” and “Message the shop on LINE”: counted per day per shop (not who) · Hearts and comments under a promotion: kept and shown under the same rules as under a post (the hearts and comments rows above) · The “Message the shop on LINE” button: the LINE id a shop gives (when it applies, or later on its posting page) is shown as a link under the shop's photos and promotions because the shop gives it for this — the form says so beside the LINE ID field, and the shop (or the organiser's admins) can turn the button off at any time. The site sends nothing to LINE until you tap that link yourself | The text of a promotion the system does not accept · the network address of a reporter · who tapped directions or the LINE button · the text of a promotion in the system's moderation log · the LINE id of a shop that has turned the button off (admins only, as in the application row) |
| post a photo to “ครั้งหนึ่ง ณ สุโขทัย” | The photo (resized on the phone before sending), caption, photographer's name, place, the activity or topic chosen, when it was posted, and who posted it (a staff link, an application or a visitor registration) — a team member's or a shop's photo appears in the public gallery at once; a visitor's photo is kept aside and appears in the gallery only after an admin has reviewed it · A short clip (up to 30 seconds): the clip file you send (with its sound), a poster image your phone makes from it, its length, and the confirmation you ticked for that clip (that the people who appear or are heard in it agreed to its publication) together with the version of that confirmation — a team member's or a shop's clip appears in the public gallery as soon as the file has arrived; a visitor's clip appears after an admin has reviewed it · a clip whose file never fully arrives is deleted in the system's daily deletion run · clips are kept and deleted like photos (sections 5 and 8) · Profile page: the live posts and running promotions of one approved account (a team member, a shop or a visitor) are gathered on one page under its display name or the shop's name when that name is tapped — it only groups what is already public and adds no data | Camera data and coordinates in the image file (dropped when the phone resizes it, and anything left is removed by the system before storing) · The location and capture time in the original file: your phone reads them to suggest the place (you can change it), and they are never sent to us · If the photo or clip you chose has no location in the file, your phone asks for the device's current position (the browser asks you first) to suggest the place — used on the device and then thrown away; it is never sent to us and never kept · In a clip file: the file's location and camera information boxes, and its recording times — the system erases them before storing; the picture and the sound of the clip stay |
| ask Nong Plaka to remove someone else's photo | The photo reported, the reason you type (if any), the time, and a code computed one way from the IP address (at most 5 a day) | Name, contact |
| search for a stay on the Getting there page, or ask Nong Plaka about a stay | The search words or the stay asked about, how many times, found or not (or found only by a similar spelling, and the stay shown first), language, time, and which stay was tapped after the search — counters of the search words, not linked to who searched · A search containing an e-mail, an @ or a phone-like run of digits is not kept · A search that is a spelling of a stay on the list may be kept as an “other name” of that stay and shown on the page, so the next person finds it — it is a search term, not information about the person who typed it | Who searched (IP address, a user id, browser details) |
3. Why we may collect it
- Visit statistics, category counters, the chat log, ratings and comments, and stay searches: to run the festival, inform its visitors and improve the festival's information (a task carried out in the public interest)
- Codes computed one way from the IP address, and the limits on how often something can be done: to prevent misuse and keep the system secure (legitimate interests)
- Answers to the short questions, applications to “ครั้งหนึ่ง ณ สุโขทัย”, partner-shop applications, and what you send to be published yourself (photos, trip comments, what you teach Nong Plaka): your consent — without it you can use the site as usual, and you can withdraw it as in section 8
- Orders: taking steps at your request before a sale
4. What we do not do
- We do not keep IP addresses in the site's database. Where misuse has to be prevented we keep only a code computed one way with the system's secret key, and remove that code after 30 days (except for an entry that is currently blocked, and votes on trip comments, which are deleted whole as in section 7)
- There are no visitor accounts (a visitor who registers to share photos has only a display name and a device key, and, if they choose to register with LINE or Google, one more value: a code computed one way from the account id — no password or e-mail). We do not ask for a date of birth or sensitive data (religion, health and so on) — only partner shops send a copy of an identity card to prove who they are (the application page advises covering religion and blood group before sending)
- We do not guess age, gender or identity from text or photos
- We do not track your location — the site asks for the device's current position only (1) when a shop itself presses the button that shares the shop's location (in its application or in the form for missing details), and that position is sent and kept as the shop's pin, and (2) after you have chosen a photo or clip on the posting page, if that file has no location in it, to suggest the place — the browser asks you first and if you refuse the site does not ask again; the position in (2) is read and used on the device only, never sent and never kept. The location in an image or clip file chosen for posting is read on the phone to suggest the place, and is likewise never sent · and (3) when you ask Nong Plaka for something “near me” (shops, places to stay, car parks, toilets and more) or tap “📍 Use my location” / “📍 Show what's near me” in the chat — the browser asks you first, and once you allow it the chat sends your approximate position (rounded to about 11 metres) with your questions while the page is open (without asking again), to find the nearest places and answer follow-up questions; it is used to answer and not kept (only a count by broad zone is kept, see section 2); for a shop question, the centre of the roughly 160-metre grid square you are in is sent to Google (Places) to search around you (see section 5); the coordinates are not sent to the AI provider (when the question needs the AI to answer, it gets only the nearest area's name and the approximate distance to the festival grounds), and the stored answer has no distances in it
- We do not sell data or give it to advertisers
- We set no cookies for ordinary visitors (only the admins' sign-in cookie, and the cookie loy_team=1 on a device a team member marks with ?team=1 — no identifier in it; it only tells the system not to count that device in the statistics), and there are no analytics or advertising tools of other companies on the pages — an outside service in section 5 that a page uses (such as the Google map on the trip page) may set its own cookies under its own policy
- We do not send a poster's device key, a removal report, the answers to the short questions or a request to delete a conversation to the AI providers · Some kinds of question (the programme, “what's on now”, festival walking tours, listed stays, removing a photo, sharing a photo, personal-data requests) are answered by the site's own code without calling an AI — but if you go on chatting in the same conversation, the earlier messages are sent along with the next question
5. Who receives your data
| Provider | What it receives | What for |
|---|---|---|
| Cloudflare | Every request that reaches the site, including the IP address at network level, and the data kept in the site's database and files | Summed visit statistics from Cloudflare's own records (country, page, device, operating system, browser) shown to the admins · Runs the website, the database and file storage, and tells the site the country and province of a request |
| OpenAI | The text of the conversation and a photo you attach · a trip plan or trip comment when you tap “Translate” · the text of a comment under a photo that passed the system's first check (only the text, with no name or code) | Writing Nong Plaka's answers, translating text, and checking comments for safety automatically |
| Anthropic, Google (Gemini) | The text of the conversation (no photo) | Backup systems, used only when the main provider cannot answer |
| Cloudflare (Workers AI) | The text of the conversation, and a photo you attached (if any) | The last backup, used only when the providers above cannot answer |
| Google (Places) | Stay searches that found nothing and are not a spelling of a listed stay (sent with the word “ | Checking that the stay exists before adding it to the list — while this notice is in effect Google refuses the requests (the account has not enabled this service), and after every refusal the system stops asking until the next day |
| Google (Places — places and services around you) | When you share your location to ask for a shop, a place or a service “near me” (cafés, restaurants, souvenirs, places to visit, a place to buy, repair or rent a vehicle, a pharmacy, a hospital, an ATM, fuel …): every time, the site sends the centre of the roughly 160-metre grid square you are in (not the position your device gave) and the kind of place you asked for — or, for something not on the list of kinds, only the words you used for it (such as “shoe repair”, the rest of your message removed) — so that Google can search around that point; nothing else about you, and not the conversation, is sent · The results are kept in Cloudflare's cache for up to 6 hours per grid square, so that people in the same square do not cause another search; they are not linked to you, and the site does not store this position anywhere · at most 100 searches a day by kind and 100 by words | Finding the places really near you on Google Maps (name, rating, opening hours, phone), then merging them with Nong Plaka's own guide |
| Google (Routes) | The coordinates of places on the site's own list that a question mentions · When you share your location for a “near me” question: your approximate position (rounded to about 11 metres) and the coordinates of the places to be suggested, to work out the walking distance (and the driving distance when it is over 2 km) along the real route, for that answer only; nothing else about you is sent · The results are kept in Cloudflare's cache for up to 6 hours per roughly 160-metre grid square and place, not linked to you, and the site does not store this position anywhere | Distances and travel times in answers |
| Google (Maps) | A Google Maps link you give when teaching a shop or applying as a partner shop (the site's server opens that link) | Reading the shop's coordinates |
| Google (Maps) | Requests from your browser when you open a trip page with a map (only the site's address is sent, not the trip link) | Showing the route map |
| Adobe (Fonts) | Requests from your browser (including the IP address) | Showing the site's typefaces |
| OpenStreetMap, cdnjs | Requests from your browser when you open the rental-shop map | Showing the map |
| The shop you order from | The items, your name and the contact in the order, when the team passes it to the shop | Contacting you to confirm the goods, price and delivery cost |
| LINE (LINE Login) | When you choose to register with LINE: you are sent to LINE's sign-in page (LINE sees your IP address and browser data under its own policy) · the site's server sends the temporary code that comes back to LINE to be exchanged and checked — nothing else about you · we get back only the account id and the display name, and keep only a one-way code and the display name | To confirm that you own the account when you register as a visitor |
| Google (Sign in with Google) | When you choose to register with Google: you are sent to Google's sign-in page (Google sees your IP address and browser data under its own policy) · the site's server sends the temporary code that comes back to Google to be exchanged and checked — nothing else about you · we get back only the account id and the display name (the e-mail permission is not requested), and keep only a one-way code and the display name | To confirm that you own the account when you register as a visitor |
| LINE, Facebook, X (when you tap a share button) | Only when you tap the share button of that service yourself: you are taken to the service's share page with the link to the post's page (https://sukhothailoykrathong.com/m/post-id) and, for X, a title text — that service sees your IP and browser data under its own policy · our site sends nothing before you tap, and does not know whether you shared · if your browser has its own share sheet, the site opens that instead (the data goes to the app you choose) | So you can pass the post on |
| The organiser's admins, and the system operators assigned by the province | The data in section 2, through the admin pages that need a sign-in (chat logs, chat feedback, visitor group statistics, the “near me” counts and stay searches only to system-owner accounts, not to general admins) — visitor data only as group totals · The system operators reach the same data through the admin pages or through a system connection (MCP) that needs their own Google sign-in and an explicit consent step before it connects | Running the system, checking what is sent in, and improving the festival's information |
The providers in the table are foreign companies or organisations, so data sent to them may be processed outside Thailand. (Google Fonts is loaded only when the fish-band page /band.html is opened on its own; no other page loads it.)
Links to Google Maps, Facebook, LINE, booking sites and the feedback survey lead off this site; once you follow one, that service's own policy applies.
6. What is kept on your device
- In this tab only (gone when the tab is closed): the chat history, the conversation code, whether you have been greeted and the suggested-question buttons, the display state of list boxes, and how this tab arrived
- Only on a team member's device opened with ?team=1 by that person: the mark loy_team in the browser and the cookie loy_team=1 (no identifier) — that device is left out of every statistic of the site (visits, taps, chat, ratings, searches); open a page with ?team=0 to undo it
- In this tab only, once Nong Plaka has asked how satisfied you are: the code of the conversation it asked in, so it is not asked again in the same conversation — gone when you close the tab
- In this tab only, once you have allowed the chat to use your location: the last approximate position your browser gave, so that a follow-up question (such as “and restaurants?” or “3 more, please”) does not ask for it again — valid for 10 minutes, and gone when the tab is closed
- In this tab only, when you press register with LINE or Google: a random code of the registration in progress (used to match it when the provider sends you back, removed as soon as it is used) — kept even for a visitor from Europe, because it is needed to finish a registration you started yourself, and gone when the tab is closed
- In this tab only, when you give a heart without being registered: the post you hearted and the address of the page to return to after registering (used once, expires in 15 minutes, removed when used) — kept even for a visitor from Europe, because it is needed to finish a heart you gave yourself, and gone when the tab is closed
- In this tab only, when you start writing a comment without being registered: the text you typed so far and the post it is for (so it is back in the box after you register; it expires in 15 minutes and is removed when the comment is sent) — kept even for a visitor from Europe, because it is needed to finish a comment you are writing yourself, and gone when the tab is closed
- In this tab only, when you tap the gallery's “+” without being registered: the time you tapped it (so that registering brings you back to the gallery; it expires in 30 minutes and is removed when used) — not used for visitors from Europe, and gone when the tab is closed
- In the browser until you delete it: the language you chose, saved trip codes, marks that you have seen or voted on trip comments, a mark that this device has visited before, a mark that you were already asked for feedback on the chat or answered the short questions (only on devices that stored it before 23 October 2026 — the site no longer writes either), and when you last opened the chat's “What's new” list (written only when you open the list; used to show how many new posts you have not seen)
- In the browser until you delete it, only on a device that holds a visitor key or an application key: the hearts, comments and share taps on your posts and promotions (and, for a shop, the 7-day count of taps on its directions link and which posting suggestion was shown that night) as you last saw them, written when you open the “What's new” list and used to show on the chat's bell what has gone up — only the numbers, kept on this device, never sent to a server, and not kept for visitors from Europe
- For applicants of “ครั้งหนึ่ง ณ สุโขทัย”: the device key that proves it is the same applicant (removed from the device when you withdraw) and the photographer's name typed on the posting page · Team members who opened an admin's posting link: that link's key (at most 5 links), so that photos posted with it can be deleted through Nong Plaka — a link the admin has cancelled is removed from the device when the site finds it no longer works
- For visitors who register in the chat to share photos: the device key (removed from the device when you stop being registered) — visitors from the EU, the EEA, the United Kingdom and Switzerland: the site does not keep this key on the device; it stays only in the address of the posting page, and if you close that page you register again · so that a heart you give during this visit works, the site keeps a copy of this key in this tab only (gone when the tab closes, never written to the device) · the status of each photo you sent as you last saw it (the photo's id with “waiting / in the gallery / not approved”), so that Nong Plaka can tell you when an admin has reviewed it — not kept for visitors from Europe
All of it is in your browser, none of it is a cookie, and it can be deleted in the browser's settings.
Visitors from the European Union, the European Economic Area (Iceland, Liechtenstein, Norway), the United Kingdom and Switzerland, and visitors whose country the system cannot tell: the site stores no measurement marks on your device (no “visited before”, no “how you arrived”, and the short questions are not asked), so whether it is a first visit is not recorded, and how you arrived is counted on the first page only — what you use yourself (chat history, saved trips, language) works as usual, and when you last opened the “What's new” list is kept in this tab only (not stored on the device)
7. How long it is kept
- Conversations (with the categories kept with each question), answers to the short questions, ratings and comments, orders, trips and trip comments (with votes), the system's moderation log, partner-shop applications (with their documents) and applications to “ครั้งหนึ่ง ณ สุโขทัย”: deleted 1 year after the festival's last day () — data created after that day is deleted 1 year after it was recorded; the system deletes once a day
- An application to “ครั้งหนึ่ง ณ สุโขทัย” whose photos are still shown: at that time the contact, the shop location, the sample product photos and the shop-page link are erased, and only what is already shown with the photos stays (the display name, and for a shop: what it sells and which spot it is near)
- An application's sample product photos: deleted when an admin does not approve it, when you withdraw it, or at the same time limit as the application · the shop-page link: deleted when you withdraw or at the same time limit · the account code of a visitor who registered with LINE or Google: deleted with the registration (when you stop being registered or at the same time limit), except for an account an admin has blocked — that code is kept until the same time limit
- Photos and clips in “ครั้งหนึ่ง ณ สุโขทัย”: kept as the festival's record until their owner, or someone in the photo or clip, asks for removal (section 8)
- A visitor registration: deleted at the same time as the applications above (while a photo is still shown, the display name stays with it) · A visitor's photo that has not been reviewed: kept (shown nowhere) until an admin approves or deletes it, or you delete it
- Hearts: deleted when the post is deleted, when the person takes the heart back, or when they stop being registered (the system's daily purge checks once more) · a closed ranking (the posts, their hearts, the closing time): kept as a record of the event, without the name or code of anyone who gave a heart
- Comments under photos and clips: deleted when the post is deleted, when the writer deletes them, when the writer stops being registered, or 1 year after the festival's last day like the other comments (the system's daily purge checks once more) · a comment an admin removed or its writer deleted: the text is erased at once, leaving only an empty row that counts towards the daily limit until the time above · reports: deleted with the comment, or when an admin decides, and the one-way network code of a reporter is replaced by a random code after 30 days · the daily counters of comments: kept
- Photos attached to trip comments: deleted with the comment, unless the same picture is used elsewhere on the site · A partner shop's front photo shown on the site: not deleted with the application; removal can be asked for as in section 8
- Codes computed one way from the IP address: removed after 30 days (except an entry that is currently blocked, and votes on trip comments as in the first point)
- Answers the system remembers to answer faster (including translations): 14 days — a question with a phone number or e-mail address is not remembered
- What is taught to Nong Plaka (waiting for review, approved or not approved): kept until an admin deletes it
- Counters not linked to a person (page views, daily category counters, stay searches, the “near me” counters by day, hour and zone): kept
- The visitor-count code (section 2): not deleted automatically yet — kept to report the festival's cumulative number of visitors
8. Your rights, and how to use them
- Delete a photo or video you posted: tell Nong Plaka, for example “delete my photo”, on the phone you posted from. Nong Plaka shows that device's photos; tap “Delete” on the one you want, and the photo and its files are deleted from the system at once — only the one you choose (team members who posted with an admin's link: the photos posted with it are in the same list on the phone that opened the link, or use “My photos” on the posting page)
- Delete a comment you wrote: tap “Delete” and then “Confirm” under the comment, on the phone you registered on — the text is erased at once. For someone else's comment that does not belong, use its “Report” button (see the community rules)
- Someone else's photo with you in it: open the photo in the “ครั้งหนึ่ง ณ สุโขทัย” gallery and tap “Ask Nong Plaka to remove this photo”. The photo leaves the site at once and an admin checks it for permanent deletion (for a photo an admin has just checked and kept, a new report within 24 hours goes straight to the admin instead of hiding it at once)
- Visitors who registered to share photos: delete a photo you sent, whether it is still waiting for review or already in the gallery, the same way as in the first point (in the chat on the phone you registered on, or “My photos” on the posting page — visitors from Europe: “My photos”, while that page is open), and stop being registered to erase your name yourself on the posting page, choosing whether the photos you sent are kept or deleted
- Withdraw an application and erase your contact: on the apply page, on the phone you applied from; you choose whether your posted photos stay as the festival's record or are all deleted
- Clear the conversation on your device: the ⋯ menu in the chat → “Clear conversation”
- Delete the conversation from the system: the ⋯ menu in the chat → “Delete this conversation from the system” removes the questions and answers (and the short-question answers) of the conversation open in that tab from the database at once (ratings or comments you sent are not linked to a conversation, so this button cannot delete them — ask as in the next point)
- See, get a copy of, correct or delete other data, restrict its use, object, or withdraw consent: contact Sukhothai Provincial Office, phone 055-611-619, or the channels on the Contact page, or tell Nong Plaka (Nong Plaka tells you these ways and channels — Nong Plaka cannot open or change data in the system itself). The chat log has no name or account attached, so we can find your conversation when you tell us roughly when it was and what you asked. Withdrawing consent does not affect what was done before you withdrew it.
- Complaints: if you believe your data is used against the law, you may complain to Thailand's Office of the Personal Data Protection Committee; visitors from Europe may complain to the data protection authority of the country they live in
9. Children and young people
The website is not designed to collect data from children and does not ask anyone's age — the short questions that asked for an age band were retired on 23 October 2026. While they were in use, if a user chose the age band “Under 20” (a minor under Thai law), Nong Plaka asked nothing more and the system kept only that age band.
10. Changes to this notice
This notice is in effect from (version privacy-2026-10-23). When the system changes how it collects or uses data, we will change this notice before or at the same time, and change the date at the top.
