Privacy policy

This policy explains how Flow Agricultural Finance Co., Ltd. (บริษัท Flow Agricultural Finance จำกัด), TIN 0105874155509, with head office at 68/4,Hang Dong Road,Hang Dong, 50230 Chiang Mai, Thailand, processes personal data under Thailand’s Personal Data Protection Act (PDPA).

Data controller

The controller is Flow Agricultural Finance Co., Ltd. Contact: info@content-flowcore.click, phone +66-53-442-718.

What we collect

When you submit the contact form, we receive your name, email address, optional phone number, and message text. When you use the cookie banner, your accept or reject choice is stored locally in your browser under the key faf_consent_choice — we do not receive that value on our servers unless you separately tell us.

We do not use analytics, advertising pixels, or third-party tracking on this website.

Purposes and legal bases

We process inquiry data to read your request, respond by email or phone, and keep a record of the conversation where needed for ordinary business administration. Under the PDPA, this is based on your request to contact us and our legitimate interest in operating a financial planning practice, or consent where applicable for optional fields.

Retention

Inquiry records are kept only as long as needed to handle your request and any follow-up planning relationship, then deleted or anonymised unless law requires longer storage.

Your rights

You may request access, correction, deletion, restriction, or portability of your personal data, and object to certain processing. Contact us at the email above. You may lodge a complaint with the Office of the Personal Data Protection Committee (PDPC) in Thailand.

International transfers

Form data is handled on infrastructure serving content-flowcore.click; if processing moves outside Thailand, we will apply PDPA-compliant safeguards.

Security

We use proportionate technical and organisational measures for data sent through our same-domain form handler at /api/inquiry. No method of transmission is perfectly secure; please avoid sending highly sensitive identifiers in the first message.

Changes

We may update this policy; the current version is published on this page with a review date noted in our internal records.