# OpenPlaceRules — Privacy Policy

**Draft v0.1 · 22 November 2026 · Not yet reviewed by a lawyer.**

This policy explains what personal data OpenPlaceRules (the website, map, API and MCP server) collects, why, and your rights under Thailand's Personal Data Protection Act B.E. 2562 (PDPA), the EU/UK GDPR and similar laws.

**Controller:** the OpenPlaceRules maintainers, Bangkok, Thailand. **Contact:** [hello@openplacerules.org](mailto:hello@openplacerules.org) or [GitHub issues](https://github.com/openplacerules/openplacerules.github.io/issues).

## 1. What we collect

| Where | Data | Required? |
|---|---|---|
| Browsing the map, spec or data; calling the read API or MCP server | No account. Our hosting provider processes your IP address, user agent and request time in short-lived server logs for security and abuse prevention. We do not use advertising or tracking cookies or analytics that identify you. | automatic |
| **Claim your place** form | Your website domain; the registry entry you claim (optional); **a contact email (optional)**; the verification token we issue and the result of checking your file, meta tag or DNS record. | domain only |
| **Report a place** form | Place details, rule summary and source URL (not personal data, unless you include some); **your email (optional)**, used only for moderator questions. | email optional |
| Emails you send us | Your email address and message. | — |
| GitHub issues you open (claims, reports, corrections) | Your GitHub username and the text of the issue, held on GitHub under GitHub's terms. | — |

Please **do not include other people's personal data** (names, photos, contact details of staff or visitors) in reports.

The rules a place publishes in its own `/.well-known/place-rules.json` (including any contact email it chooses to publish there) are public by design; we copy them into the registry.

## 2. Why we use it (purpose and legal basis)

- Verify domain ownership and show owner-verified rules — to provide the service you requested (contract / PDPA s.24(3)).
- Contact you about your claim or report — our legitimate interest in accurate data (PDPA s.24(5); GDPR Art. 6(1)(f)); you can leave the email blank.
- Keep the service secure and prevent abuse — legitimate interest.
- Comply with law — legal obligation.

We do **not** sell personal data, use it for advertising, or make automated decisions with legal effects about you.

## 3. Who sees it

- Moderators (currently only the operator).
- Service providers acting for us, e.g. web hosting and email providers, under their data-processing terms. They may be outside Thailand or the EU; where required we rely on appropriate safeguards (e.g. standard contractual clauses or the provider's adequacy mechanisms).
- Authorities, if the law requires.

Your **email is never published**. A claimed domain and the owner's published file are public.

## 4. How long we keep it

- Claim and report emails: up to **24 months** after the claim or report is closed, then deleted.
- Verification records (domain, token, result, time): kept while the entry is owner-verified, plus 24 months as history.
- Server logs at the host: per the host's retention, normally no more than 30 days.

## 5. Your rights

Subject to the law, you may ask to access, correct, delete, or receive a copy of your data, object to or restrict processing, and withdraw consent where we rely on it. Email us; we answer within 30 days. You may complain to Thailand's Personal Data Protection Committee (https://www.pdpc.or.th/) or to your local data-protection authority (in the EU/EEA, your national supervisory authority).

## 6. Security

We collect as little as possible, keep claim data on a server under our control, and use HTTPS. No method is perfect; if a breach affects you we will notify you and regulators as the law requires.

## 7. Children

The Service is not directed at children under 13 (or the age required in your country), and we do not knowingly collect their data.

## 8. Changes

We will post changes here with a new date. If a future feature (for example accounts or wallets) collects more data, we will update this policy **before** launching it.
