FSFullStart Social
Contents

Privacy Policy

Version 1In force from 1 Dec 2026Last updated 1 Dec 2026

1. Who we are

Product name (the "Service") is a social media management and customer relationship management service for businesses. It is provided by Full Start Co., Ltd. ("FullStart", "we", "us"), a company registered in Thailand under registration number company registration number.

This policy explains what personal data we collect, why, how long we keep it, who we share it with, and the rights you have under Thailand's Personal Data Protection Act B.E. 2562 (2019) ("PDPA") and other applicable laws. It covers the Service at social.fullstart.net, our website, and our support channels.

2. Our two roles: controller and processor

Under the PDPA, a data controller decides why and how personal data is used. A data processor handles personal data only on a controller's instructions.

Whose dataExamplesFullStart's role
People who use the Service ("Account Users"): the person who signs up, team members, billing contacts, people who contact our supportName, work e-mail, password hash, role, login history, invoicesController
Our customers' audiences ("Customer Contact Data"): people who comment on, message or follow our customers' pages and accounts, and contacts our customers addPlatform user ID, display name, profile picture, comments, messages, notes, tags, deal stageProcessor for our customer. The customer (the business that uses the Service) is the controller.
Content our customers create ("Customer Content"): posts, captions, images, videos, schedulesAny personal data inside a postProcessor for our customer

When we act as a processor, we handle the data only to provide the Service to our customer and on that customer's instructions, under our Data Processing Agreement. If you are a member of a business's audience (for example, you sent a message to a shop's Facebook Page and the shop uses our Service), please contact that business first; it decides how your data is used. If you contact us instead, we will pass your request to the business and help it respond.

3. What we collect

3.1 Data you give us

  • Account and workspace: name, work e-mail, phone number (optional), company name, job role, language and time zone, password (stored only as a one-way hash), two-factor authentication settings.
  • Team: e-mail addresses of colleagues you invite and the roles you give them.
  • Billing (when paid plans start): billing contact, company tax ID, billing address, invoices and payment status. Card details are handled by our payment provider payment provider; we do not store full card numbers.
  • Support: what you write to us and the files you attach.
  • Customer Content: the posts, captions, images, videos, templates and brand rules you create or upload.

3.2 Data collected automatically

  • Logs and security events: IP address, browser and device type, pages and API calls requested, time stamps, sign-in attempts, and actions taken in a workspace (audit trail).
  • Cookies and local storage: see section 12.

3.3 Data from the social platforms you connect

You choose which accounts to connect. We ask each platform only for the permissions we need for the features you use. We never ask for or store your platform passwords. Access and refresh tokens are encrypted (section 10).

PlatformWhat we receiveWhy
Facebook Pages (Meta)Your Facebook user ID for our app, name; the Pages you manage, their IDs, names and Page access tokens; posts published through the Service and their status; Page and post insights. If you use the inbox and contacts features: comments on your Pages' posts, Messenger conversations with your Page, and the sender's Page-scoped ID, name and profile picture.Connect your Pages, publish and schedule posts, show results, and (if you use them) show and reply to comments and messages and keep contact records for you
Instagram (Meta)Your Instagram professional account ID, username and profile picture; media published through the Service; media and account insights. If you use the inbox and contacts features: comments, mentions and direct messages, with the sender's Instagram-scoped ID, username and profile picture.As above
Threads (Meta)Your Threads user ID, username and profile picture; posts published through the Service and their insights. If you use the inbox features: replies to your posts.As above
TikTokYour TikTok open ID, display name and avatar; creator information needed to post (allowed privacy levels, interaction settings, maximum video length); publishing status of videos you post through the Service; video statistics if you use analytics.Post videos and photos to your TikTok account on your instruction, and show their status and results
YouTube (Google)Your YouTube channel ID, title and thumbnail; upload permission; the videos you upload through the Service, their status and statistics.Upload videos and Shorts to your channel on your instruction, and show their status and results
LinkedInYour LinkedIn member ID, name and profile photo; the LinkedIn Pages you administer; posts published through the Service and Page statistics. If you use the inbox features: comments on your Page's posts, with the commenter's name and profile, cached only for the short periods LinkedIn allows (section 7.4).Post to your LinkedIn Page, show results and comments
LINE Official AccountThe Messaging API channel credentials you enter for your OA; the LINE user IDs of people who add your OA as a friend, their display name and profile picture, messages they send to your OA, and follow/unfollow events.Send broadcasts and replies from your OA, show conversations in the inbox, and keep contact records for you

Data marked "if you use the inbox and contacts features" is Customer Contact Data. We process it as your processor (section 2).

4. How we use personal data and our legal bases

PurposeLegal basis under the PDPA
Create and run your account, sign you in, keep it secureContract (s.24(3))
Connect your social accounts and publish, schedule, read and reply on your instructionContract (s.24(3))
Bill you and keep accounting and tax recordsContract; legal obligation (s.24(6))
Answer support requestsContract; legitimate interests (s.24(5))
Detect and stop abuse, fraud and security incidents; keep logsLegitimate interests; legal obligation
Improve the Service using usage statistics about how features are used (not the content of your posts, comments or messages)Legitimate interests
Send service notices (security, changes to this policy, billing)Contract; legal obligation
Send product news and offersConsent (s.19), which you can withdraw at any time

What we never do

  • We do not sell personal data, and we do not share it with advertising networks, data brokers or information resellers.
  • We do not use data from the social platforms to serve or target advertising, to build profiles for anyone other than the customer who owns the account, or to decide anyone's creditworthiness, employment, insurance, housing or eligibility for any benefit.
  • We do not use data from the social platforms, or our customers' content, comments or messages, to train artificial-intelligence models.
  • We do not use platform data for surveillance.

5. AI features

The Service can help you draft and translate captions using an AI provider, currently Anthropic PBC (United States), through its commercial API.

  • When you use an AI feature, we send the provider the text and instructions needed for that request: for example, your draft caption, your brand's tone and rules, and the target language.
  • We do not send comments, messages or contact records to the AI provider unless you use an AI feature on them (for example, "suggest a reply"), and then only the text needed.
  • We do not send data received from YouTube or other Google services to the AI provider.
  • Anthropic acts as our sub-processor. Under its commercial terms, it does not use API inputs and outputs to train its models confirm against Anthropic's commercial terms at signing and keeps them for confirm retention period for trust and safety.
  • AI output can be wrong. You review and approve every post before it is published. Where a platform or the law requires it, you must label content as AI-generated (see our Terms of Service).

6. Who we share personal data with

We share personal data only as described here.

Sub-processors (service providers who process data for us, under written contracts that restrict them to our instructions and require security and deletion when the service ends):

Sub-processorWhat they doLocation
hosting providerServers, storage and backups for the Servicecountry of data centre
e-mail providerSending sign-in, notification and service e-mailscountry
Anthropic PBCAI caption drafting and translation, only when you use AI featuresUnited States
payment provider (from paid launch)Taking paymentscountry

We will keep this list up to date at URL of sub-processor list and tell customers before adding a new sub-processor.

Others

  • The social platforms you connect. When you publish, your content goes to that platform and is then governed by the platform's own terms and privacy policy.
  • Your own team. People you invite to your workspace see the data their role allows.
  • Authorities, when Thai law or a valid court or government order requires it.
  • A buyer or successor, if FullStart is merged or sold. We will tell you first and, where required (including for data received from Google), ask for your consent.

7. Platform-specific information

7.1 YouTube and Google

  • The Service uses YouTube API Services. By connecting a YouTube channel you agree to be bound by the YouTube Terms of Service.
  • Google's handling of your data is described in the Google Privacy Policy.
  • Limited Use. Product name's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular, we use Google user data only to provide the features you see in the Service (uploading your videos and showing their status and statistics); we do not transfer it except as needed for those features, for security, to comply with law, or in a merger with your prior consent; our staff do not read it unless you ask us to, for security, or where the law requires; and we never use it for advertising, for credit decisions, or to train AI models.
  • How to remove our access. You can disconnect your channel in the Service at any time, or revoke our access on the Google security settings page.
  • Deletion. If you disconnect in the Service, we revoke the token straight away and delete the YouTube data we stored within 7 days. If you revoke access on Google's page, we delete it within 30 days. Data we keep (other than tokens and statistics) is refreshed or deleted at least every 30 days. Deleting data in our Service does not delete videos on YouTube; delete those on YouTube.
  • For privacy questions about our use of YouTube data, contact privacy@fullstart.net.

7.2 Facebook, Instagram and Threads (Meta)

  • We access Meta data through Meta's APIs under the Meta Platform Terms and use it only to provide the features described in section 3.3.
  • We act as a technology provider for our customers: we keep each customer's data separate and use it only for that customer.
  • How to remove our access: in Facebook, go to Settings & privacy → Settings → Apps and websites, and remove FullStart Social. You can then use Send request to ask us to delete your data; you will receive a confirmation code and a link to check the status. You can also disconnect in the Service or e-mail us. See our Data Deletion Instructions.

7.3 TikTok

  • We use TikTok's Login Kit and Content Posting API, under the TikTok Developer Terms of Service, only to post content you choose to your account and show its status.
  • Before anything is posted, you see a preview, choose the privacy level and interaction settings yourself, and confirm TikTok's Music Usage Confirmation (and, for branded content, TikTok's Branded Content Policy).
  • You can disconnect in the Service or remove our access in the TikTok app's settings verify menu path: Settings and privacy → Security → Apps and services. We delete your TikTok tokens when you disconnect and the related data within 7 days.

7.4 LinkedIn

  • We use LinkedIn's APIs under the LinkedIn API Terms of Use and the LinkedIn Marketing API terms.
  • We ask for your consent before connecting your LinkedIn account. We use LinkedIn data only to show it to you inside the Service; we do not sell, share or combine it with other data for advertising.
  • We follow LinkedIn's storage limits. In particular, profile details of other LinkedIn members (for example, people who comment on your Page) are cached for no more than 24 hours, and their posts and comments are kept for no more than 48 hours. They are not saved as contacts.
  • If you ask us to delete your data or close your account, we delete your LinkedIn tokens and LinkedIn data immediately. You can also remove our access in your LinkedIn settings verify URL: Settings → Data privacy → Permitted services.

7.5 LINE

  • To connect a LINE Official Account, the OA owner creates a Messaging API channel in LINE Developers and gives us its credentials. We use them only to send and receive messages for that OA, under the LINE Developers Agreement.
  • For people who add a business's OA as a friend, the business is the controller and we are its processor. Messages and profiles are also handled by LINE under LINE's privacy policy verify the Thai privacy policy URL.
  • An OA owner can disconnect in the Service or reissue the channel's access token in LINE Developers. A LINE user can block the OA in LINE, or ask the business to delete their data.

8. Transfers outside Thailand

Some of our sub-processors and all of the social platforms process data outside Thailand, including in country of hosting provider and the United States. When we transfer personal data abroad, we do so only as the PDPA allows (sections 28 and 29): for example, where needed to perform our contract with you, or with appropriate safeguards such as standard contractual clauses recognised under the Personal Data Protection Committee's notifications on cross-border transfers lawyer to confirm the current notification and wording. You can ask us for a copy of the safeguards we use.

9. How long we keep data

DataHow long
Account dataWhile your account is open, then deleted within 90 days after it is closed
Social platform tokensUntil you disconnect the account, or the platform tells us access was revoked. Deleted immediately then
Customer Content and Customer Contact DataAs the customer decides while the account is open; deleted within 30 days after the account is closed (after an export window), unless a shorter platform limit applies
YouTube data (other than tokens and statistics)Refreshed or deleted at least every 30 days
LinkedIn data about other membersProfile: up to 24 hours. Posts and comments: up to 48 hours
Billing and tax records5 years, or longer if Thai accounting or tax law requires lawyer to confirm the period
Logs and security recordsAt least 90 days and normally no more than 1 year lawyer to confirm whether the Computer-Related Crime Act B.E. 2550 applies to us
BackupsOverwritten within 14 days after the data leaves our live systems

Data that cannot identify anyone (for example, total posts published per day) may be kept longer.

10. Security

  • All traffic to the Service uses HTTPS (TLS).
  • Social platform tokens are encrypted with AES-256-GCM using a dedicated key that is stored separately from the database and can be rotated. Tokens are never shown on screen, returned by our API, written to logs or included in audit records.
  • Each customer's data is kept separate; every query is limited to the customer's own workspace.
  • Messages that platforms send to us (webhooks) are checked against the platform's signature before we read them.
  • Staff access is limited to what each person needs. Accounts can use two-factor authentication.
  • Servers run with security controls enabled, are patched regularly, and are backed up confirm backup encryption.

No system is perfectly secure. If a personal data breach happens, we will:

  • as controller, notify the Office of the Personal Data Protection Committee within 72 hours of becoming aware of it where the PDPA requires, and notify affected people without delay where the risk is high;
  • as processor, notify the affected customer without undue delay so it can meet its own duties;
  • notify the affected social platforms as their terms require.

To report a security vulnerability, write to security contact e-mail.

11. Your rights

Under the PDPA you have the right to:

  • withdraw consent you gave us, at any time (this does not affect what was done before);
  • access your personal data and get a copy;
  • receive your data in a common electronic format, or have it sent to another controller;
  • object to processing;
  • ask us to delete, destroy or anonymise your data;
  • ask us to restrict processing;
  • ask us to correct your data;
  • complain to the Office of the Personal Data Protection Committee (www.pdpc.or.th).

To use these rights, write to privacy@fullstart.net. We may need to confirm your identity. We will reply within 30 days. Some rights have legal limits; if we cannot do what you ask, we will explain why.

If we hold your data as a processor for one of our customers (section 2), we will forward your request to that customer and help it respond.

12. Cookies and similar technology

We use cookies and browser storage that are strictly necessary for the Service: to keep you signed in, protect forms against forgery, and remember your language and time zone. These do not need consent and cannot be switched off without breaking sign-in.

We do not use advertising cookies. If we add analytics cookies in the future, we will ask for your consent first and update this section.

13. Children

The Service is for businesses. Account Users must be at least 20 years old (the age of majority in Thailand) or have the authority to act for their business. We do not knowingly collect personal data from children as Account Users. If you think a child has given us personal data, contact us and we will delete it.

Our customers are responsible for their own audiences, including content made for children (for example, YouTube's "made for kids" setting).

14. Changes to this policy

If we change this policy, we will post the new version here with a new "last updated" date. If a change is significant, we will tell you by e-mail or in the Service before it applies, and where the law or a platform's terms require (for example, a new use of Google user data), we will ask for your consent.

15. Contact us

Full Start Co., Ltd.
Privacy: privacy@fullstart.net
DPO: DPO name and contact e-mail

16. Language

This policy is published in Thai and English. Lawyer to decide: "If the two versions differ, the Thai version prevails."