Privacy Policy

minute3 AI is provided by Penson Digital Co., Ltd. (บริษัท เพนซัน ดิจิทัล จำกัด, Thai company registration no. 0205568036231) (“we”). This policy explains what we collect, how we use it and how we protect it when you use minute3, under Thailand’s Personal Data Protection Act B.E. 2562 (2019) (PDPA).

What we collect

• Your account: email address, name and sign-in times (by email code or Google).
• Meta advertising data you authorize through Facebook Login: ad accounts, Pages, campaigns, performance figures and the access token (stored encrypted).
• LINE: the user ID and display name of each person who confirmed, with an invitation code, that they want the summaries.
• What you type to the AI assistant and its answers, to show you your conversation history.
• Payments: handled by Stripe. We never see or store card numbers.
• A change log: who changed what in an ad account and when, so it can be checked and undone.
• Real sales you record or pull from online shops: the number of orders and the amount per day, per channel.
• Data from the features you choose to switch on: leads from ad forms, chats and comments, customer lists for audiences, and online shops. Each has its own section below.

How we use it

• To read your ad figures, find problems, propose budget changes and send the summaries you set up.
• To carry out the changes you or your team confirm, and record them.
• To bill your plan and contact you about your account.
• To send workspace owners a few getting-started emails. Reply “stop” and they end.

We do not sell data, we do not use your advertising data to advertise for anyone else, and we never show one workspace’s data to another workspace.

Processors we use

• Meta Platforms (the advertising data you authorize, leads, chats and comments when switched on, and measuring our own ads when you accept cookies) · LINE (message delivery) · Anthropic (processing the AI assistant’s messages and the drafts you ask AI for) · Google (reading the Google Sheets shared with minute3, and turning summaries into speech) · Shopee / Lazada / TikTok Shop (only the shops you connect) · Stripe (payments) · DigitalOcean (servers and backups, in Singapore) · Brevo (email) · Cloudflare (domain and incoming email)

Cookies and ad measurement

• Essential cookies: your sign-in (m3_session), light/dark theme and your cookie choice (m3_consent). They are used without asking because the site cannot work without them.
• Meta’s ad-measurement cookies (Meta Pixel): only after you press “ยอมรับ” (accept), to measure minute3’s own ads, such as how many people saw an ad and then signed up or started a trial.
• With your yes, when you sign up, start a trial and make the first payment we send Meta, through the Conversions API: your email as a SHA-256 hash, Meta’s cookie ids (_fbp, _fbc), the IP address and browser of the sign-in, and the plan and price. Nothing about your ad accounts or your clients.
• Change your mind at any time with ตั้งค่าคุกกี้ (at the foot of the home page). With a no we do not load the Meta Pixel and send none of the above. Legal basis: your consent.

minute3 Chrome extension

• It reads the address (URL) of an Ads Manager or Business Suite tab to know which ad account you have open, and sends that account number and the selected campaign or ad set IDs to minute3 to show that client’s information. It does not read the content of Ads Manager pages.
• Ad receipts: when you press the button, the extension opens Meta’s billing page in a tab you can see, reads the payment table of the ad accounts you chose, and downloads Meta’s receipt files to your computer. If you choose Google Drive, it uploads those files and a summary sheet from your browser straight to your own Google Drive, with Google’s drive.file permission (it can only see files it created). Payment data and receipt files are never sent to minute3.
• The extension keeps your minute3 session and, if you connect Google Drive, a short-lived Google access token on your computer. It never stores Meta passwords or tokens. Revoke the minute3 session in Settings → Connected devices, and Google access in the extension or in your Google account.

Leads from ad forms (Instant Forms)

• When you switch it on and allow it through Facebook Login, we read the leads from the forms of the client Pages you manage.
• We keep only: Meta’s lead ID, the form, ad and campaign names, when the lead came in, its pipeline stage, who handles it, the notes and follow-ups your team writes, and the value of a won deal.
• The answers in the form (such as name, phone and email) are not kept in our system: they go into the LINE message for the recipients your workspace set up as soon as the lead arrives, and are read from Meta again each time a team member opens a lead or the workspace owner downloads a CSV. We record who opened or downloaded which lead (the lead ID only).
• When you switch on sending results back, we send each lead’s stage (such as contacted or won) to the client’s own dataset (Pixel) through the Conversions API, with Meta’s lead ID only and no other personal data.
• For leads a team adds itself (a call, a walk-in, a chat) we keep only the source, the time, the branch, the appointment, the pipeline stage and the business’s own reference code (such as a patient or booking number). There is no field for a name, phone or email, and a reference code or note containing a phone number or email is refused. These leads are never sent to Meta.
• Appointment reminders in LINE go only to the workspace’s recipients and name the source, the reference code and the time, never the customer’s contact details.

Chats and comments (Messenger, Instagram and the business’s LINE Official Account)

• When a workspace owner connects a Page, we receive that Page’s chats and comments through Meta’s webhooks so the team can answer them in one place.
• We keep messages and comments only as long as the team needs them to reply: 30 days by default (7–90 days per client), then they are deleted automatically. People who write or comment are stored only by the ID Meta gives them for that Page: no names, usernames or pictures.
• AI drafts replies and sorts comments (spam, questions, complaints) by sending that text to Anthropic; a team member edits and sends. Automatic answers to frequent questions, hiding spam comments and alerts work only when the client switches them on, and any hidden comment can be shown again.
• An alert about an unhappy comment goes by LINE with an excerpt of at most 80 characters, only to that workspace’s recipients.
• We only send replies within the messaging window Meta allows.
• When a workspace owner connects the business’s LINE Official Account, we receive its one-to-one chats through LINE’s webhook (never group chats). The sender is stored only by the user ID LINE gives for that account: no names or pictures. Messages are kept and deleted on the same schedule as other chats. The account’s channel secret and channel access token are stored encrypted and used only to check LINE’s signature and to send replies.
• When the business switches on appointment reminders, a customer the team added as a lead from a LINE chat, with an appointment, gets one reminder in that chat before the day of the appointment.

Customer lists for audiences (Custom Audiences)

• A business uploads a CSV file or shares a Google Sheet, as a viewer, with the Google account minute3 shows. We read it and turn emails, phone numbers and names into SHA-256 hashes in memory, then send them to Meta to create or update a Custom Audience in that business’s ad account.
• We keep neither the raw values nor the hashes, only the number of rows, how many were sent, and any errors.
• For this data the business is the controller and must have the people’s consent first (minute3 asks it to confirm every time); minute3 processes it on the business’s behalf. A clinic’s customer list is health data (sensitive under PDPA section 26): the clinic must also confirm that everyone gave explicit consent.
• The Google account that reads sheets may only view Google Sheets, and sees only the sheets shared with it. A sheet is read again every week until the business removes the sync or stops sharing the sheet.

Drafts made with AI, and voice summaries

• Drafting a content calendar, a campaign plan, ad copy or chat replies sends the client’s brief, ad figures and the related text to Anthropic. Under Anthropic’s commercial terms, data sent through its API is not used to train models.
• Everything AI writes is a draft that a person checks and confirms. Campaigns and ads made in minute3 are created paused until you turn them on.
• Weekly voice summary: the script is made from the workspace’s ad figures and sales and sent to Google Cloud Text-to-Speech to become audio. Audio files are kept up to 8 days; the listening link expires after 7 days.
• Pictures for new creatives are resized and cropped from the client’s ad images on our servers and kept 7 days.
• Scheduled posting (when switched on) publishes only the posts your team approved and timed to the client’s Page or Instagram; it can be cancelled before then.

Sales from online shops

• When you connect Shopee, Lazada or TikTok Shop, we keep the shop’s access encrypted and read its orders every morning only to count the paid orders and the amount per day. We do not keep buyers’ names, addresses or phone numbers. You can disconnect on the client page.

Keeping and deleting data

• We keep your data while you use the service. When you disconnect Facebook, we delete the token at once.
• When you remove the minute3 app in Facebook, or ask Facebook to delete your data, we automatically delete that account’s connection and token and give you a confirmation code to check the status.
• You can ask us to delete your account and all its data at support@minute3.ai. We do it within 30 days.
• Chat messages and comments are deleted after the days set (30 by default), voice summary files within 8 days, and pictures for new creatives after 7 days.
• We back up data daily. Deleted data may stay in backups for up to 14 days, then it is removed.

Security

Meta tokens, online shop access and the Google access used to read sheets are encrypted with AES-256-GCM. Each workspace’s data is kept in its own database schema. Sign-in codes and sessions are stored only as hashes. Every connection uses HTTPS.

Your rights

You may ask to access, correct, delete or move your personal data, or object to how it is processed. Contact support@minute3.ai.

Data controller

Penson Digital Co., Ltd., 119/27 Moo 5, Soi 17, Pattaya-Naklua Road, Na Kluea, Bang Lamung, Chon Buri 20150, Thailand