Privacy policy
Version 1.3, effective 18 November 2026
1. Introduction and scope
1.1 This Privacy Policy ("Policy") explains how D & G Staffing Co., Ltd. (trading as Studio R7) collects, uses, discloses, transfers and otherwise processes personal data, in line with the Personal Data Protection Act B.E. 2562 (2019) of Thailand and its subordinate regulations ("PDPA").
1.2 This Policy applies to personal data processed through:
- (a) our website at
https://studior7.comand any preview or successor domain ("Site"); - (b) the "Start a project" intake, the project planner, the channel-setup order form and the quote calculator ("Intake");
- (c) "save for later" links and app waiting lists ("notify me");
- (d) file uploads made through the Intake;
- (e) first-party site analytics and lead attribution;
- (f) our chat channels on LINE, WhatsApp and Telegram;
- (g) our own LINE Front-end Framework apps ("LIFF apps"), including the LINE demo and the LINE contact form;
- (h) the Studio R7 app marketplace and apps listed there ("Marketplace Apps");
- (i) confidential technology-for-equity applications ("Equity Applications");
- (j) our dealings with clients, prospective clients and their staff ("Client Relationship Data");
- (k) our free tools, optional R7 accounts, and account credits and referrals (section 4A);
- (l) business accounts that a client connects to Studio R7, such as a WhatsApp Business Account, Facebook Page, Instagram account, LINE Official Account or Google Business Profile (section 4B).
1.3 This Policy does not cover personal data that we process on behalf of a client inside a system we build or operate for that client (for example, the client's own customers' bookings or messages), except for what section 4B says about it. For that data the client is the data controller and we act as its data processor. Those individuals should read the client's own privacy notice.
1.4 Short notices at the point of collection (for example, the chat-channel notice and the intake consent text) supplement this Policy. Our Cookie Notice explains browser storage in detail.
2. Who we are (data controller)
2.1 The data controller is:
| Legal name | D & G Staffing Co., Ltd. |
|---|---|
| Trading name | Studio R7 |
| Registration no. | 0105567080475 |
| Registered address | 3082 Sukhumvit Road, Bang Na, Bangkok 10260, Thailand (เลขที่ 3082 ถนนสุขุมวิท เขตบางนา กรุงเทพมหานคร 10260) |
| Privacy contact | privacy@studior7.com (general enquiries: hello@studior7.com) |
| Chat | LINE OA @studior7; WhatsApp +66 97 170 9226; Telegram @StudioR7 |
2.2 Data protection contact. You can reach the person responsible for data protection at Studio R7 at privacy@studior7.com. This is a role, not a named person, and it handles every privacy question and request.
2.3 Representative. We are established in Thailand, so no PDPA representative under s.37(5) is required.
3. Definitions
3.1 In this Policy: "personal data" means information relating to an identifiable living person, as defined in PDPA s.6; "sensitive data" means the categories listed in PDPA s.26; "processing" means any operation on personal data; "you" means the individual whose data we process; "processor" means a person that processes personal data on our instructions; "PDPC" means the Personal Data Protection Committee and its Office.
4. Personal data we collect, by touchpoint
4.1 Website (general browsing)
- (a) Technical request data received by our hosting provider (Vercel) when any web page is served: IP address, browser type, requested URL, time. Vercel keeps these request logs for a short period set by its plan (between 1 hour and 30 days under Vercel's published log limits); we do not copy them into our own database.
- (b) Spam and abuse protection. When you submit a form or trigger a tracking call, our server derives a one-way hash of your network address and keeps it in short-lived memory as a rate-limit counter (typically a window of 10 minutes). It is not written to our database, not logged with your submission and is discarded when the server instance restarts.
- (c) Preferences on your device, such as a reduced-motion setting and whether the homepage intro animation has played in this session. These stay in your browser. See the Cookie Notice.
4.2 Intake ("Start a project", planner, channel-setup form, quote calculator)
When you press send, we receive:
- (a) identity and contact data: your name; optional company name; your chosen contact route (LINE, WhatsApp, Telegram or email) and the matching LINE ID or phone number, WhatsApp number, Telegram handle or email address;
- (b) project data: your answers about the business problem, goals, current tools (including, if you choose, their monthly cost and number of seats), what you must keep, channels, timeline, budget band, preferred way of working, roles, volumes, modules, integrations, privacy needs, AI needs, languages, deadline and free-text notes;
- (c) submission data: language, a random submission ID, time received, source channel (web, LINE, WhatsApp, Telegram), and a consent record (the version of the consent wording you accepted and the time);
- (d) attribution data captured when you first landed on the Site (see 4.5);
- (e) generated summaries: a client summary and an internal team summary of your enquiry, produced by rules or by an AI provider (see section 9).
Before you press send, your non-personal answers are autosaved in your browser so you can come back later, and a "save for later" link carries only those answers. Your name, company and contact details are never autosaved and never put in a link. If you switch the page language while filling in the form, everything you typed, including those fields, is passed to the new page once through your browser's session storage and deleted as soon as the page opens. Nothing is sent to us until you press send.
4.3 Saved drafts ("save for later") and app waiting lists
If you ask us to email you a link to continue later and tick the consent box, we receive the email address you enter, the resume link (which encodes your saved answers in the link itself) and your language. We send that one email through our email provider and do not keep the address afterwards or use it for anything else. We do not send reminders or text messages. Anyone who has the link can open the saved answers; please keep it private.
If you ask to be notified when one of our apps opens ("notify me") and tick the consent box, we store the email address or LINE ID you enter, which app it is for, your language, the time and the version of the consent wording. We use it only to tell you once that the app is open, then delete it. You can ask us to remove it at any time.
4.4 File uploads
You may upload images (JPEG, PNG, WebP), PDFs and brand-kit files (for example SVG, fonts, ZIP, AI, EPS) up to about 4 MB each. We may:
- (a) extract the text layer of PDFs on our server;
- (b) send images to an AI vision provider to transcribe visible text and briefly describe what is shown (only the image itself is sent, never your name or contact details);
- (c) store the original file in a private storage bucket and link it, with the extracted text, to your submission. Stored files and their separate upload records are deleted automatically after 90 days (see section 11).
Please do not upload identity documents, payment card data, medical records or files containing other people's personal data unless strictly necessary and lawful.
4.5 Analytics and attribution (first-party, only with your consent)
- (a) Site analytics. Only after you choose Accept analytics in our privacy choices banner, our own code records page views, scroll depth (25/50/75/100 %), sections viewed, the text and link of buttons or links clicked, time on page, the last section seen on exit, the referring page, any UTM parameters in the URL, language, and whether the browser is a mobile device. Each event carries a random session ID (kept in session storage) and a random browser ID (kept in local storage). We do not store your IP address with these events and do not use third-party analytics or advertising pixels. If you choose Only necessary, or make no choice, no IDs are created and no analytics events are sent. Analytics are also not sent if your browser signals "Do Not Track". You can change your choice at any time with Privacy choices at the bottom of every page.
- (b) Lead attribution. Only if you accepted analytics, we store in your browser where you came from: UTM source, medium, campaign, content and term, Google or Meta click identifiers (
gclid,fbclid) if present in the link, the external referring page, the landing path and the time. If you later send an enquiry, this attribution is attached to it. Without that consent we store nothing; an enquiry then carries only the UTM parameters present in the address of the page you send it from, and no click identifiers.
- (c) Marketplace events. If you accepted analytics, on marketplace pages we record views, likes, downloads, installs, starts and call-to-action clicks with the app, the random browser ID, language, page path and UTM data.
- (d) Anonymous usage counts. When you download or share a finished card in Namecard Maker, we record one count with only the app name, the word "exported", the page language and the time: no browser ID, page path, UTM data, IP address or anything you typed, and nothing is stored on your device. Because it cannot identify you, it does not depend on your analytics choice. We use it only to show a rounded total such as "1,200+ cards made".
- (e) We produce weekly aggregate reports from these events.
4.6 Optional visitor profile ("personalise this site")
If you choose to fill in a profile, we save your name, business type and goal in your browser only. A first-party cookie r7_profile holds the same three fields for up to 180 days so pages can be personalised. The profile stays on your device and is never sent to our servers. We do not ask for your email here.
4.7 Chat channels (LINE OA, WhatsApp, Telegram)
When you message us we receive: your display name and profile picture as shown by the platform; your platform identifier (LINE user ID, WhatsApp phone number, Telegram user ID and/or username); the content of messages, files, images and voice notes you send; message times; the buttons or keywords you used; your answers to our short qualification questions; tags we apply (for example "opted in", "opted out", "handed to a person"); and your marketing opt-in or opt-out with its time.
The platform operators (LY Corporation for LINE, Meta/WhatsApp, Telegram) process your data under their own terms and privacy policies as independent controllers. See our Chat Channels Notice.
4.8 LIFF apps (LINE demo and LINE contact form)
If you open one of our LIFF apps inside LINE and allow it, LINE shares your LINE display name, profile picture and LINE user ID with the app (the profile permission). Both apps use them only to greet you on screen and do not send them to our servers or store them. The LINE contact form also uses the chat_message.write permission: when you press send, it posts the details you typed (your name, business, optional phone number and choices) as a message from you into your chat with our LINE Official Account, so it is handled as a chat message (4.7). The LINE demo can open LINE's own share screen if you choose to share it with friends; we do not see who you share it with.
4.9 Marketplace Apps
When a business registers as the owner of a Marketplace App instance, we process: the owner's LINE user ID, business name, chosen plan (free by default) and app settings. End users of an app may provide data that the app needs to work (for example queue check-ins, bookings, orders, loyalty points or reminders).
- (a) Where a business uses an app to serve its own customers, that business is generally the controller of its customers' data and we are its processor (Data Processing Addendum and Marketplace Terms apply).
- (b) Where an individual uses a consumer app for personal purposes, we are the controller of the data needed to run the app.
Health data. The marketplace lists a planned consumer app, "Fever log", for recording a child's temperature and medicines. That would be health data (PDPA s.26) about a minor. It will not launch until it has its own privacy notice and asks for explicit consent, including a parent's or guardian's consent (s.20). This Policy does not cover it.
4.10 Equity Applications
If you apply for technology-for-equity, we receive the general Intake data plus your answers about the venture: stage, need, traction, team, what you bring, capital structure, funding, and why you are applying (and, in the planner flow, problem, connection to the problem, expertise, business plan, monetisation, scale and investment notes). We treat Equity Applications as confidential and restrict access to them separately from ordinary project enquiries. We ask you not to send detailed financial, identity or legal documents until we provide a secure channel.
4.11 Clients and prospective clients
For client work we process the business contact details, job titles, signatures, communications, meeting notes, proposals, contracts, invoices, payment and tax records of client representatives and staff, and access credentials and logs for systems we operate.
4.12 Sources other than you
We may receive your data from: the person who referred you; a colleague who named you as a contact; the messaging platforms (4.7); and public business registries for verifying a client company. We do not buy personal data lists.
4A. Free tools, R7 accounts and credits
Free tools without an account
4A.1 When you use a free tool (for example Namecard Maker or Invoice Maker) without signing in, everything you enter (business profile, logo, customers and documents) is stored only in your browser on your device. We do not receive it. You can export a backup and erase it at any time in the tool's settings or by clearing your browser's site data. If you accepted analytics, we count anonymous events such as "document downloaded", without any document content, as described in section 4.
R7 accounts
4A.2 An R7 account is optional and free. One account works across the Studio R7 apps; each app keeps its own data. If you create one, we process:
- (a) account data: your email address (or, if you sign in only with LINE and LINE does not share an email, a non-deliverable placeholder address), the sign-in method you chose (Google, Microsoft, LINE or an email code), the identifier that provider gives us, and, if the provider shares it, your name and profile picture. With LINE we ask for your profile and, where LINE allows it, your email address (LINE Login permissions
openid,profile,email); - (b) security data: sign-in times, IP address and device or browser information recorded by our authentication provider to keep your account safe;
- (c) business profile: business name, address, tax ID, branch, contact details, logo, brand colour, bank account and PromptPay details, and your default notes and terms;
- (d) about-you answers (optional): your name as you give it, the kind of business you run, your main goal, and which channels customers use to find you (for example LINE or Google). You can skip every question.
- (e) documents and customers: the quotations, invoices and receipts you save and the customer details on them;
- (f) credits and referrals: your credit balance and history (vouchers redeemed, credits earned, used or expired), your personal invite code, and which account invited which (referrals).
4A.3 Purpose and lawful basis: to provide the account, keep your documents available on your devices and run the credit and referral programme (performance of a contract, PDPA section 24(3)), and to secure the service and prevent abuse of credits and referrals (legitimate interests, section 24(5)). We use the about-you answers only to greet you and show examples on our own website while you are signed in. We do not sell them, share them with other businesses, or use them for advertising. You can change or delete them on your account page at any time; deleting your account removes them too.
4A.4 Who can see it: only you. Every database row is tied to your account and protected by row-level security; logos are kept in a private storage folder. An invite page never shows the inviting person's name or details. Studio R7 staff access account data only to give support you ask for, to investigate abuse, or when the law requires it.
Your customers' data: we act as your processor
4A.5 Your documents can contain personal data about your customers. For that data you are the data controller and Studio R7 acts as your data processor (PDPA section 40): we store it only to provide the service to you, follow your instructions, keep it confidential and secure, and do not use it for our own purposes such as marketing. You are responsible for having a lawful basis to record your customers' data and for answering their requests. We will tell you without undue delay if we become aware of a personal data breach affecting your data.
Service providers for accounts
| Provider | Role | Location |
|---|---|---|
| Supabase | Database, authentication and private file storage (processor) | Singapore (AWS ap-southeast-1) |
| Vercel | Website hosting (processor) | United States (server functions); pages served from Vercel's global network |
| Google, Microsoft, LINE (LY Corporation) | Sign-in, only if you choose that method (independent controllers for their own accounts) | Their own locations |
| Google (Google Workspace mailbox hello@studior7.com) | Sends sign-in codes and links (processor) | Google's data centres (several countries) |
4A.6 Where data is transferred outside Thailand, we rely on the provider's contractual safeguards as described in section 10.
Keeping and deleting account data
4A.7 We keep account data while your account exists. You can delete documents, customers and your logo yourself at any time. To delete your whole account, use Delete my account on your account page, email privacy@studior7.com or follow the steps at https://studior7.com/en/data-deletion; we delete the account and its data within 30 days and confirm by email. The credit history of a deleted account is deleted with it. Copies in our database provider's backups are overwritten automatically within 7 days.
4A.8 Studio R7 does not keep accounting records on your behalf. Thai law may require you to keep business documents for several years: download your PDFs or a backup before you delete anything.
4B. Business accounts you connect to Studio R7
4B.1 What this covers. If your business uses Studio R7 to run its customer messages or online presence, you can connect your own business accounts: a WhatsApp Business Account, a Facebook Page or Instagram professional account (Meta), a LINE Official Account (LY Corporation) or a Google Business Profile (Google). You connect an account yourself, by signing in with that platform and approving the access it shows you, or by adding Studio R7 as an admin of the account. The account stays yours and you can disconnect it at any time. We will update this section before we offer connections to any other platform.
4B.2 What we receive. Only what the platform shares within the permissions you approved:
- (a) connection data: the account, page, phone-number or profile ID and name, the access token the platform issues (stored encrypted), the permissions granted, and when the account was connected;
- (b) who connected it: the platform user ID and name of the person who approved the connection;
- (c) content and performance data: posts, comments, reviews and our replies, and statistics such as views, searches, clicks and calls for the connected account;
- (d) messages: for WhatsApp, Messenger, Instagram and LINE, the messages your customers send to your business and the replies sent, with the customer's platform ID, display name and, for WhatsApp, phone number.
We never receive your platform password.
4B.3 Why we use it. Only to provide the services your business asked for: answer and route your customers' messages, publish posts and replies you approved or that follow the rules you set, reply to reviews, and report results to you. We do not sell this data, do not use it for advertising, do not combine it with other clients' data, and do not use it to train general-purpose AI models. Any AI-drafted reply follows section 9: drafts, rules you set and human hand-off.
4B.4 Roles. For your customers' data (4B.2 (c) and (d)) your business is the data controller and Studio R7 is your data processor (PDPA s.40): we act only on your instructions under our contract with you, keep the data confidential and secure, help you answer your customers' requests and tell you without undue delay about a breach (as in 4A.5). For connection data and the identity of the person who connected the account (4B.2 (a) and (b)), Studio R7 is the controller (contract, s.24(3), and legitimate interest in securing the service, s.24(5)). Meta, Google and LY Corporation remain independent controllers of the data on their own platforms.
4B.5 Data from Google APIs. Studio R7's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements (https://developers.google.com/terms/api-services-user-data-policy). In particular: we use Google user data only to provide or improve the features you see and use in Studio R7; we transfer it to others only to provide those features, with your consent, for security, to comply with law, or as part of a merger, acquisition or sale of assets after asking for your explicit consent; we do not use or transfer it for advertising, and never sell it or give it to data brokers or for credit decisions; no person at Studio R7 reads it unless you have asked us to (for example for support), it is needed for security or to comply with law, or it is aggregated for internal operations; and we do not use it to create, train or improve generalised AI or machine-learning models.
4B.6 How long we keep it. Access tokens: until you disconnect, or until they expire and are not renewed. Content, statistics and messages: while our service to your business runs; message content for at most 12 months unless our contract with you sets another period. After the service ends we offer you an export and delete the data within 30 days. Invoices and tax records are kept as section 11 states.
4B.7 Disconnect and delete. You can disconnect an account in your Studio R7 workspace, by asking us, or in the platform's own settings (for example the business integrations list in Facebook, or the third-party connections in your Google Account). When an account is disconnected we stop using it at once and delete its access token. To have all data from a connected account deleted, follow https://studior7.com/en/data-deletion or email privacy@studior7.com.
5. Purposes and lawful bases
5.1 We rely on the lawful bases in PDPA s.24 (and s.26 for sensitive data). The table below states, for each purpose, the data used and the basis.
| # | Purpose | Data | Lawful basis (PDPA s.24) |
|---|---|---|---|
| P1 | Reply to your enquiry on the channel you chose | 4.2, 4.3, 4.7, 4.8 | Steps at your request before entering a contract (s.24(3)); for people who are not contracting, legitimate interest (s.24(5)). The intake also records that you agreed to this Policy and when. |
| P2 | Prepare a solution brief, indicative estimate and proposal | 4.2, 4.4, 4.11 | Pre-contractual steps (s.24(3)) |
| P3 | Generate AI-assisted summaries for our team and for you | 4.2, 4.4 | Legitimate interest (s.24(5)) — see balancing note 5.3(a) |
| P4 | Perform a contract with a client and manage the relationship | 4.11 | Contract (s.24(3)); for client staff, legitimate interest of the client and us (s.24(5)) |
| P5 | Send the save-for-later link you requested, and tell you once when an app you asked about opens | 4.3 | Your request / pre-contractual steps (s.24(3)) |
| P6 | Assess Equity Applications | 4.10 | Pre-contractual steps (s.24(3)) and legitimate interest (s.24(5)) |
| P7 | Operate Marketplace Apps you use or register, and run the business accounts a client connects | 4.9, 4B | Contract (s.24(3)); as processor, on the client's instructions (s.40); explicit consent (s.26) for any health data |
| P8 | Measure and improve the Site and our marketing (analytics, attribution, weekly reports) | 4.5 | Consent (s.19), given with Accept analytics and withdrawable at any time through Privacy choices (see 5.3(b)) |
| P9 | Personalise the Site using an optional profile | 4.6 | Consent (s.19) |
| P10 | Send updates, news and offers (LINE, WhatsApp, Telegram, email) | contact data, opt-in record | Consent (s.19), opt-in only |
| P11 | Protect the Site from spam, fraud and abuse; keep systems secure | 4.1, request data | Legitimate interest (s.24(5)) |
| P12 | Keep accounting, tax and corporate records; respond to lawful requests | 4.11, invoices | Legal obligation (s.24(6)) |
| P13 | Establish, exercise or defend legal claims | relevant records | Legitimate interest (s.24(5)) and s.26(4) where sensitive data is involved |
| P14 | Keep a record of consents and opt-outs | consent records | Legal obligation and legitimate interest |
5.2 If you do not provide data marked as required (name and a contact route), we cannot reply to your enquiry. All other fields are optional.
5.3 Legitimate interest balancing notes (summary of our assessments):
- (a) *AI summaries (P3).* Interest: respond faster and more consistently. Safeguards: only your project answers (and text extracted from files you attached) are sent to the AI provider; your name, company name, contact route, contact details and attribution data are removed first; summaries are drafts; a person reviews before any binding proposal; no automated decision with legal effect is made. You may object (section 11).
- (b) *Analytics (P8).* Analytics rely on your consent rather than legitimate interest. Safeguards: first-party only, no IP stored with events, no advertising pixels, random IDs not linked to your name unless you later send an enquiry together with attribution data, Do Not Track honoured, aggregate reporting. Choosing Only necessary deletes the IDs from your browser.
- (c) *Security (P11).* Interest: keep the Site available. Safeguards: hashed address held in memory only, for minutes.
5.4 We will not use your data for a new purpose incompatible with the original purpose without telling you and, where required, asking for consent (PDPA s.21).
6. Sensitive data
6.1 We do not seek sensitive data (racial or ethnic origin, political opinions, religious or philosophical beliefs, sexual behaviour, criminal records, health, disability, trade union information, genetic or biometric data). Please do not include it in forms, uploads or chats.
6.2 If you send it anyway, we will delete it where practicable or process it only where a PDPA s.26 condition applies.
6.3 Any Marketplace App designed to process sensitive data (see 4.9) will carry its own notice and request explicit consent before use.
7. Children and minors
7.1 The Site, Intake and chat channels are intended for business users and adults. We do not knowingly collect personal data from persons under 20 (minors under the Thai Civil and Commercial Code) without the consent required by PDPA s.20.
7.2 If you believe a minor has given us personal data without the required consent, contact us and we will delete it.
7.3 Consumer Marketplace Apps that may concern children (see 4.9) will not launch until they have a way to check age and obtain a parent's or guardian's consent.
8. Recipients and processors
8.1 We share personal data only as needed for the purposes above, with:
- (a) our authorised personnel, on a need-to-know basis and under confidentiality obligations; Equity Applications are restricted to a smaller group;
- (b) processors acting on our instructions under written contracts (section 8.2);
- (c) messaging platforms as independent controllers when you use them (section 4.7);
- (d) professional advisers (lawyers, accountants, auditors) under confidentiality;
- (e) authorities where required by law, court order or lawful request;
- (f) a successor in a merger, acquisition or restructuring, subject to this Policy.
8.2 Processors and other recipients. These are the providers our code uses today. Optional ones are used only where they are switched on.
| What for | Provider | Role | Where the data is processed |
|---|---|---|---|
| Website hosting and server functions | Vercel Inc. | Processor | United States (server functions, Vercel's default region Washington, D.C.); pages served from Vercel's global network |
| Database, accounts and private file storage | Supabase Inc. (Studio R7's own project) | Processor | Singapore (AWS ap-southeast-1) |
| Email: sign-in codes, enquiry alerts to our team, save-for-later links | Google LLC (Google Workspace mailbox hello@studior7.com) | Processor | Google's data centres (several countries) |
| Back-up email sender, only if our Google mailbox is not available | Resend | Processor | United States |
| AI: enquiry summaries and reading text in uploaded images | OpenAI (API, model gpt-4o-mini) | Processor | United States |
| AI: build suggestion for our team and English translation of Thai free text | Vercel AI Gateway, routing to Anthropic (model claude-sonnet-5.5) | Processor | United States |
| Enquiry alerts to our own team chats | Telegram Bot API (Telegram); LINE Messaging API (LY Corporation) | Used to send alerts to our own chats; independent controllers of their platforms | Telegram's data centres outside Thailand; LY Corporation in Japan and its affiliates |
| Accounting and invoices for clients | FlowAccount | Processor | Thailand |
| Sign-in, if you choose it | Google, Microsoft, LINE (LY Corporation) | Independent controllers of their own accounts | Their own locations |
| Business accounts a client connects (4B) | Meta (WhatsApp, Facebook, Instagram), Google (Business Profile), LY Corporation (LINE Official Account) | Independent controllers; we send them posts, replies and messages on the client's instructions | Their own locations |
8.3 The table above is our current list of processors. We update this Policy before we start using a processor for a new purpose or in a new category.
8.4 We do not sell personal data and do not share it with advertisers.
9. AI-assisted processing and automated decisions
9.1 We use AI models to: (a) draft a summary of your enquiry for you and an internal summary for our team; (b) draft a build suggestion for our team and translate Thai free-text answers into English for our team; (c) read text in and briefly describe uploaded images; and (d) in some chat flows and client systems, draft replies.
9.2 Safeguards:
- (a) we send the AI provider only your project answers: your name, company name, contact route, contact details, consent record and attribution data are removed before the request. Uploaded images are sent only to transcribe them, on their own, without your identity;
- (b) the AI is instructed never to state prices, savings, returns or legal terms, and never to discuss equity terms;
- (c) AI output is a draft. A person reviews it before any proposal, price or commitment is issued. Binding proposals require human commercial approval;
- (d) if the AI provider is not configured or fails, a rule-based summary is used instead.
9.3 We do not make decisions based solely on automated processing that produce legal or similarly significant effects on you. If this changes, we will tell you in advance, explain the logic, and give you the right to human review.
9.4 We do not use your data, or client data, to train public or general-purpose AI models. Under their published API terms, OpenAI and Anthropic do not use data sent through their APIs to train their models by default, and keep it for up to 30 days to detect abuse before deleting it; Vercel AI Gateway does not keep prompts or answers after a request is completed.
10. International transfers
10.1 Our database is in Singapore. Hosting functions, email, AI and alert providers (section 8.2) process data in the United States or in several countries.
10.2 We transfer personal data abroad only in accordance with PDPA s.28–29 and the PDPC's notifications on cross-border transfers, using one or more of: (a) a destination with adequate protection standards as determined by the PDPC; (b) appropriate safeguards such as PDPC-recognised standard contractual clauses or binding corporate rules; (c) your explicit consent after being informed of the inadequate standards of the destination; (d) performance of a contract with you or steps at your request; or (e) another exception under s.28.
10.3 For each processor we rely on its data processing terms, which include contractual safeguards for international transfers (s.29), and, where they apply, on the s.28 exceptions for performing a contract with you or steps you asked for.
10.4 You may ask us for information about the safeguards used (section 13).
11. Retention
11.1 We keep personal data only as long as needed for the purpose, then delete or anonymise it:
| Category | How long we keep it | Notes |
|---|---|---|
| Enquiries and chat histories that do not lead to a contract | 24 months from our last contact with you | Earlier on request |
| Uploaded files (private bucket) and their upload records | 90 days from upload | Deleted by a daily clean-up job. Text extracted from a file you attached to a sent enquiry stays with that enquiry |
| Save-for-later requests | Not stored: the email is sent once and the address is not kept | Link content lives in the link itself |
| App waiting list ("notify me") | Until we have told you the app is open, or 12 months, whichever is sooner | Deleted after the one notice, or earlier on request |
| Equity Applications declined or withdrawn | 12 months from the decision or withdrawal | Earlier on request |
| Client Relationship Data | Contract term + 10 years | The general limitation period for contract claims (Civil and Commercial Code s.193/30) |
| Accounting and tax records | At least 5 years from the end of the accounting period, longer where the Revenue Department or the Accounting Act B.E. 2543 requires (up to 7 years) | |
| R7 account data | While the account exists; deleted within 30 days of a deletion request | See 4A.7 |
| Connected business accounts (4B) | Tokens until disconnected; content and statistics while the service runs; message content at most 12 months; all deleted within 30 days after the service ends | See 4B.6 |
| Site analytics events (raw) | 13 months | Collected only with consent; anonymous aggregate reports may be kept longer |
| Marketplace events | 13 months | Collected only with consent |
| Consent and opt-out records | As long as we rely on the consent, plus 3 years | The PDPA limitation period for claims (s.78). An opt-out is kept as long as needed to keep honouring it |
| Rate-limit counters | Minutes, in memory | Not stored |
| Browser storage on your device | Until you clear it; r7_profile cookie 180 days; analytics IDs deleted when you choose Only necessary | See Cookie Notice |
11.2 We may keep data longer where required by law or to establish, exercise or defend legal claims.
12. Security
12.1 We apply technical and organisational measures appropriate to the risk (PDPA s.37(1)), including:
- (a) encryption in transit (HTTPS) for the Site and APIs;
- (b) database tables with row-level security enabled and no public access policies; only our server, using a secret key kept in server-side configuration, can read or write leads, uploads and analytics;
- (c) a private file bucket for uploads;
- (d) origin checks, rate limits, request-size limits, input validation and a honeypot on submission endpoints;
- (e) signed webhooks (HMAC SHA-256) for lead delivery where configured;
- (f) separation of client environments (tenant isolation) for systems we operate;
- (g) least-privilege access, role-based permissions and access reviews for personnel;
- (h) confidentiality obligations for personnel and processors;
- (i) backups and monitoring for managed systems;
- (j) encryption of stored data by our database and hosting providers, and encryption of access tokens for connected business accounts (4B);
- (k) an incident response procedure led by our data protection contact (section 15);
- (l) two-step verification on every administrator account we use to run the Site and connected services.
12.2 No system is completely secure. Please use the contact channel you trust and avoid sending sensitive information in free text.
13. Your rights
13.1 Subject to the PDPA's conditions and exceptions, you have the right to:
- (a) withdraw consent at any time, without affecting processing before withdrawal (s.19);
- (b) access and obtain a copy of your data, and ask how we obtained data you did not consent to (s.30);
- (c) data portability: receive your data in a structured, commonly used, machine-readable format, or have it sent to another controller where technically feasible (s.31);
- (d) object to processing based on legitimate interest, for direct marketing (always honoured), or for research or statistics (s.32);
- (e) erasure, destruction or anonymisation (s.33);
- (f) restriction of use (s.34);
- (g) rectification: have inaccurate data corrected and incomplete data completed (s.35–36);
- (h) complain to the PDPC (s.73): Office of the Personal Data Protection Committee (สำนักงานคณะกรรมการคุ้มครองข้อมูลส่วนบุคคล), 120 Moo 3, 5th–7th floors, Government Complex Commemorating His Majesty the King's 80th Birthday Anniversary (Building C), Soi Chaeng Watthana 7, Chaeng Watthana Road, Thung Song Hong, Lak Si, Bangkok 10210; phone 02 111 8800;
https://www.pdpc.or.th.
13.2 How to exercise them. Write to privacy@studior7.com, or message us on LINE, WhatsApp or Telegram and ask for a person. Say which right you are exercising and which channel you used with us. To delete your data you can also follow https://studior7.com/en/data-deletion. We may ask for reasonable information to verify your identity, and we will not ask for more than necessary.
13.3 Response time. We confirm receipt within 7 days and respond without undue delay, and in any event within 30 days of receiving your request (PDPA s.30), and tell you the reason if we refuse, together with how to complain.
13.4 Exercising rights is free. We may refuse or charge a reasonable fee for requests that are manifestly unfounded or excessive, where the law allows.
13.5 Browser data (autosaved answers, profile, IDs) is on your device and under your control. Use "Clear my answers", "Forget my profile", Privacy choices, or your browser settings.
14. Marketing
14.1 We send updates only if you opt in with a clear action: an unticked checkbox on a form, or replying "updates", "YES" or pressing an opt-in button in chat. We record when and how you opted in.
14.2 You can opt out at any time by typing "stop updates" / "หยุดข่าวสาร" (LINE), "STOP" (WhatsApp), /stop (Telegram), by using an unsubscribe link, or by contacting us. Opt-outs take effect immediately for automated sends and within 7 days for any list we keep by hand.
14.3 Quiet hours. We do not send automatic outbound messages between 22:00 and 08:00 Asia/Bangkok time. Replies to a message you send us may still arrive at any time.
14.4 Frequency: at most two update messages a month on each channel.
15. Personal data breaches
15.1 We maintain a procedure to detect, assess, contain and record personal data breaches.
15.2 Where a breach is likely to result in a risk to your rights and freedoms, we will notify the PDPC without delay and, where feasible, within 72 hours of becoming aware of it (PDPA s.37(4)). Where the risk is high, we will also notify you without delay, with information about the breach and remedial measures.
15.3 Where we are processor for a client, we notify the client as set out in the Data Processing Addendum.
16. Cookies and similar technologies
16.1 We use browser storage (local storage, session storage) and one optional first-party cookie. Analytics and attribution storage is used only after you accept it in the privacy choices banner. We do not use advertising cookies or third-party analytics. Details, keys and controls are in our Cookie Notice.
17. Links to other services
17.1 The Site links to LINE, WhatsApp, Telegram and other services. Their privacy practices are governed by their own policies.
18. Changes to this Policy
18.1 We will post changes on this page with a new version date. If changes materially affect how we use data collected under consent, we will ask for consent again. The intake consent record stores the version you accepted.
19. Language
19.1 This Policy is published in English, with a Thai summary at the top of the page. A full Thai translation will be published after review. Until then, and if the two versions ever differ, the English version prevails.
20. Contact
D & G Staffing Co., Ltd., 3082 Sukhumvit Road, Bang Na, Bangkok 10260, Thailand.
Privacy requests, by role: our data protection contact, privacy@studior7.com · LINE @studior7 · WhatsApp +66 97 170 9226 · Telegram @StudioR7 · data deletion: https://studior7.com/en/data-deletion.
Version 1.3, effective 18 November 2026