SupaTalkerSuper AI Customer Service Agent

Privacy Policy

Last updated: 2026-11-12

This page is a translation; the Traditional Chinese version prevails.

This policy explains how SupaTalker (the "Service") handles personal data. The Service has two parts: the SupaTalker website and membership service, and the Meta messaging integration offered to service providers (connecting Facebook Pages and Instagram professional accounts). Each part handles different data, so they are described separately below.

1. Website and membership service

Data we handle

  • Account data: name or display name, email address, password (stored only as an irreversible hash), email verification status, member role and creation time.
  • When you sign in with Google: your Google account ID, email address, name, profile picture URL, and the sign-in tokens issued by Google (stored encrypted).
  • When you sign in with LINE: your LINE user ID and display name. The Service does not obtain your email address or profile picture from LINE; you enter your email address yourself and confirm it with a verification code.
  • Sign-in records: the IP address and browser information (User-Agent) of each sign-in. You can review them on the "Devices" page in the admin console and sign out of any device.
  • Subscription data: Stripe customer and subscription IDs, plan, billing cycle and subscription status. Card numbers are collected directly by Stripe and never pass through or are stored by the Service; card brand, last four digits and invoices are read from Stripe only when you open the billing page.
  • Contact form: the inquiry type, preferred days and hours, email address, phone number and extension, LINE / Facebook / Instagram accounts (optional), your name and message, plus the submission time and interface language. To prevent abuse we also keep a hash computed from your IP address; the IP address itself is not stored.
  • Contact support (member area): the issue type you choose and the name, phone number and extension (optional) and message you provide. We also keep your account email address and account ID, plus the submission time and interface language. No IP address is collected and no IP hash is stored.
  • Trial requests: the contact name, email address (confirmed with a verification code), company or business name, industry and questionnaire answers you provide, the version and time of the Terms of Service you agreed to, and the submission time and interface language. After review we also record the result, our reply, the trial site URL and trial period, and the account ID of the reviewer. To prevent abuse, we also keep a hash calculated from your IP address; we do not keep the IP address itself.
  • Security records: to prevent abuse, the system temporarily keeps request counts by IP address and path, and the times verification codes were sent.

How we use it

  • Creating and maintaining member accounts, verifying identity and signing you in.
  • Sending service notices such as verification codes, password resets, account creation notices and welcome emails.
  • Processing subscription payments and billing.
  • Responding to inquiries submitted through the contact form and sending a confirmation email.
  • Responding to questions submitted through Contact support in the member area and sending a confirmation email.
  • To review your trial request, set up your trial site, send verification codes, the request confirmation and the review result, and let you check the progress of your request.
  • Preventing bots, brute-force attacks and other abuse.

The Service does not use member data for advertising and does not sell or rent it to third parties. This website does not use Google Analytics or any other analytics or ad-tracking tools.

Processors and third-party services

To provide the Service, the following companies handle some data within their roles:

  • Vercel: website hosting and execution.
  • Neon: database (PostgreSQL).
  • Stripe: subscription payments. The Service provides your email address, name, member ID and language.
  • Amazon Web Services (SES): sending email.
  • Cloudflare Turnstile: bot verification for the sign-in, sign-up, verification-code and contact forms. Verification data and your IP address are sent to it.
  • Google and LINE: used only when you choose to sign in with those accounts.
  • SupaTalker AI customer service: the chat window embedded in website pages. Messages you type there are sent to that service to generate replies.

Cookies

This website uses only functional cookies: keeping you signed in (valid for 7 days and extended while you keep using it), protecting the Google and LINE sign-in flows (expire within minutes), remembering your language, and the open/closed state of the admin sidebar. Your admin theme preference (light, dark, or system) is kept separately in your browser's local storage (localStorage) and is not sent to our servers. This website does not use advertising or tracking cookies; Cloudflare Turnstile and the AI customer service chat window may set their own cookies.

Retention

  • Account data and sign-in methods: kept until the account is deleted.
  • Sign-in records (IP address, browser information): kept until that session is removed (by signing out, removing it on the "Devices" page, or deleting the account).
  • Verification codes: stored only as hashes and expire after a short time; temporary data for the LINE sign-in flow expires within 10 minutes.
  • Billing records: kept after the account is deleted, for accounting and legal review.
  • Website data after a paid subscription is canceled or deactivated: kept for 30 days, during which you may ask for early deletion through "Contact support". After deactivation, database data in backups is deleted within 30 days by default; if you ask for early deletion, it is also deleted immediately.
  • Contact form submissions: kept for 2 years, then deleted automatically.
  • Contact support submissions from the member area: kept for 2 years like contact form submissions, then deleted automatically.
  • Trial request data: kept for 2 years after the review result is final, then deleted automatically. During that time it is used to tell whether the same email address has already requested or been given a trial.

Your rights and account deletion

  • In the admin console you can change your display name and password, review and sign out of devices, and unlink LINE.
  • To request access to your data, correct your email address, export your data or delete your account, email support@supatalker.com. We will process the request after verifying your identity.
  • An account with an active subscription can be deleted only after the subscription is canceled and the billing period has ended.
  • When an account is deleted, its account data, sign-in methods and sign-in records are deleted together; billing records are kept as described above.

2. Meta messaging integration

About the service

The Service's provider console lets service providers, on behalf of their merchant clients, connect Meta platform accounts (Facebook Pages and Instagram professional accounts), receive messages from visitors and forward them to the merchant's own system, which replies. The Service does not offer features directly to consumers; messages are processed and stored long-term in each merchant's own system.

Data we handle

  • When a merchant authorizes: the Facebook Page ID and name, the Instagram professional account ID and username (or display name if there is no username), the ID of the Facebook user who completed the authorization, and the connection time and status.
  • Message events: webhook events sent by Meta, including the visitor's ID on that platform, message content, attachment links, and interactions such as reactions and button taps.
  • Access tokens: tokens obtained during authorization, handled as described in the next section.

How messages and access tokens are handled

  • Message events are forwarded to the merchant's system immediately after their signature is verified. When forwarding succeeds, the Service does not keep the message content.
  • In two cases the Service temporarily keeps the full message event (including content) so it can be resent: when forwarding fails, or when the account connection is not yet fully set up and forwarding is temporarily unavailable.
  • Page and Instagram access tokens are held only briefly during authorization and then handed to the merchant's system for storage; if the handover fails, they are discarded without retry. The Facebook user token obtained during authorization is not handed over and is discarded after use. Access tokens are not written to the Service's database, log files or error pages.
  • When a merchant manages several Pages, the Facebook user token is encrypted and kept in a cookie in the merchant's browser for up to 5 minutes so the merchant can choose which Page to connect; it is cleared once the choice is made.

Data sharing

  • The Service does not sell or rent data, and does not use messages for advertising or behavioral analysis.
  • Apart from Meta and the merchant's own system, data is handled only by the following processors within their roles: Vercel (service execution), Neon (database) and Amazon Web Services (database backups).

Retention

  • Account connection data: kept until the merchant disconnects.
  • Temporarily kept message events: deleted 7 days after a successful resend; events never resent are deleted automatically after at most 30 days.
  • Connection event records: events such as connecting, disconnecting and token invalidation (including account IDs) are kept for operational auditing.
  • Backups: the database is backed up daily; backups include the data above and are kept for up to 90 days.

Disconnection and data deletion

  • A merchant can disconnect at any time from their own system. After disconnection, the Service deletes that account's connection data and stops forwarding its message events; Facebook Pages are also unsubscribed from Meta, while unsubscribing Instagram accounts is handled by the merchant's system. Temporarily kept message events are deleted within the periods above.
  • Visitors who want their conversation data deleted should contact the merchant, because conversations are stored in the merchant's system.
  • To ask the Service to delete related records on its side, email support@supatalker.com. After verifying identity, we will delete the related records from the database; data in backups disappears when those backups expire.

3. Other

Changes to this policy

When this policy changes, we will update this page and the "Last updated" date above.

Contact

For any questions about this policy or how personal data is handled, contact support@supatalker.com.