Privacy Policy
Effective date: 30 October 2026 · Last updated: 30 October 2026
This Privacy Policy explains how Cipher Co., Ltd. (“Cipher”, “we”, “us”) collects, uses, shares and protects personal data when you use SerpV, including the website at serpv.com and the application at app.serpv.com (together, the “Service”). It also describes your rights under Thailand’s Personal Data Protection Act B.E. 2562 (2019) (“PDPA”).
Contents
- Who we are
- Data we collect
- How we use data
- Google user data
- Legal bases
- Sharing and service providers
- International transfers
- Retention
- Security
- Your rights
- Cookies
- Children
- Changes
- Contact us
1. Who we are
SerpV is operated by Cipher Co., Ltd., 99/103 Racha Thewa, Bang Phli District, Samut Prakan 10540, Thailand. For personal data in your account, Cipher is the data controller. When an agency uses SerpV on behalf of its own clients, the agency decides what client data to put into SerpV, and Cipher processes that data to provide the Service to the agency.
2. Data we collect
Account data
Your name, email address and password (stored only as a salted hash), the organization (workspace) you belong to, and your role in it.
Workspace data you provide
Projects, brand and competitor names and their aliases, website domains, keywords, the questions (“prompts”) you track, report settings and alert recipients.
Data the Service collects for you
Answers that AI platforms (such as ChatGPT, Gemini and Perplexity) return to the questions you track, the sources they cite, Google search results for your tracked keywords, and the metrics we calculate from them. This is information that is generally available to the public, not personal data about you. It may occasionally contain names of people that appear in public web content.
Google user data (only if you connect Google)
See section 4.
Usage and technical data
IP address, browser user agent, timestamps of sign-in and actions, and error logs. We use these for security, troubleshooting and audit.
Communications
Messages you send us, for example to support@cipher.co.th.
3. How we use data
- To provide the Service: run scheduled data collection, calculate metrics, show dashboards and reports, and send the alerts you configure.
- To create and secure your account, authenticate you and prevent abuse.
- To bill your organization for its subscription.
- To provide support and tell you about important changes to the Service.
- To maintain and improve the reliability and accuracy of the Service. We do this using aggregated or de-identified information, and never using Google user data.
- To comply with legal obligations.
We do not sell personal data, and we do not use personal data for third-party advertising.
4. Google user data
You can choose to connect a Google account to SerpV to bring Google Search Console and Google Analytics data into your reports. This section describes exactly what we do with data received through Google APIs (“Google user data”).
4.1 What we access
| Permission (scope) | Data |
|---|---|
openid, email, profile |
Your Google account email and name, so you can see which Google account is connected. |
https://www.googleapis.com/auth/webmasters.readonly |
The list of Search Console properties you can access and, for the properties you choose to connect, search performance data: queries, pages, countries, devices, clicks, impressions, click-through rate and average position. |
https://www.googleapis.com/auth/analytics.readonly |
The list of Google Analytics 4 properties you can access and, for the properties you choose to connect, report data: sessions, engaged sessions and conversions by date, source, medium and landing page. |
All access is read-only. SerpV never creates, changes or deletes anything in your Google account, Search Console or Google Analytics.
4.2 How we use it
We use Google user data only to provide and improve user-facing features of SerpV that you can see: showing your Search Console and Analytics data in your dashboards and reports, next to your rankings and AI visibility, for the projects you connect them to. That includes identifying traffic referred by AI assistants, and including this data in exports and scheduled reports you configure.
4.3 How we store and protect it
OAuth tokens are encrypted at rest using AES-256-GCM. Google user data is stored in our database in Singapore and is visible only to members of the organization that connected it, according to their roles.
4.4 Sharing
We do not sell Google user data. We do not use it for advertising, retargeting or interest-based advertising. We do not use it to develop, improve or train generalized AI or machine-learning models. We do not share it with AI model providers. We transfer Google user data to others only:
- to the members of your organization, and to recipients of reports that you choose to send;
- to our infrastructure providers (Cloudflare and Neon), who process it on our behalf solely to host the Service;
- when required to comply with applicable law; or
- as part of a merger, acquisition or sale of assets, with notice to you.
4.5 Human access
Our staff do not read Google user data, except when you give us explicit permission for a specific support request, when necessary for security purposes (such as investigating abuse), or when required by law.
4.6 Retention and deletion
We keep Google user data while the Google connection is active. When you disconnect Google in SerpV, delete the project, or close your account, we delete the related tokens immediately and the related Google user data within 30 days. You can also revoke SerpV’s access at any time at myaccount.google.com/permissions. When SerpV detects that access was revoked, it stops syncing and deletes the data on the same schedule.
4.7 Limited Use
SerpV’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
5. Legal bases
Under the PDPA we process personal data:
- to perform our contract with you or your organization (providing the Service);
- on the basis of our legitimate interests in securing and improving the Service, where these are not overridden by your rights;
- with your consent, when you connect a Google account (you can withdraw consent by disconnecting it); and
- to comply with legal obligations, such as accounting and tax law.
6. Sharing and service providers
We share personal data only with service providers that help us run the Service, under contracts that require them to protect it:
| Provider | Purpose | Data involved |
|---|---|---|
| Cloudflare, Inc. | Hosting, content delivery, security, file storage | All Service data in transit; stored files and reports |
| Neon, Inc. (on AWS, Singapore) | Database hosting | Account, workspace and Service data |
| OpenAI, Google (Gemini API), Perplexity | Answering the questions you track; analysing those answers | The tracked questions, brand names and aliases, and public AI answers. Not your account data and never Google user data. |
| DataForSEO | Google search results, keyword volumes and other public search data | Tracked keywords, locations and domains |
| Email and messaging providers | Sending alerts and reports you configure (email, LINE) | Recipient address and report contents |
We may also disclose data if required by law or a valid order from a competent authority, or to protect the rights and safety of our users or the public.
7. International transfers
Our database is in Singapore, and our providers may process data in other countries where they operate. When we transfer personal data outside Thailand, we rely on contractual safeguards with the provider and the other mechanisms permitted under the PDPA.
8. Retention
- Account and workspace data: while your account is active, then deleted within 30 days after the account is closed, unless we must keep it longer by law.
- Collected AI answers and search results: raw data for up to 12 months; aggregated metrics for as long as your organization keeps its account.
- Google user data: see section 4.6.
- Security and access logs: up to 12 months.
- Billing records: as long as required by Thai accounting and tax law.
9. Security
We encrypt data in transit (TLS) and at rest, encrypt OAuth tokens separately, isolate each organization’s data, restrict internal administrative access to authorised staff behind single sign-on, and keep audit logs of important changes. No system is completely secure. If a breach affects your personal data, we will notify you and the authorities as required by the PDPA.
10. Your rights
Under the PDPA you have the right to: access and obtain a copy of your personal data; ask us to correct it; ask us to delete or anonymise it; restrict or object to processing; receive your data in a portable format; withdraw consent at any time (this does not affect processing that happened before); and lodge a complaint with the Personal Data Protection Committee of Thailand. To use these rights, email support@cipher.co.th. We will respond within 30 days. If your data was put into SerpV by an agency you work with, we may forward your request to that agency.
11. Cookies
The application uses only strictly necessary cookies: a session cookie that keeps you signed in, and security cookies used by Cloudflare. We do not use advertising or cross-site tracking cookies. This website does not set cookies.
12. Children
The Service is designed for businesses and is not directed to anyone under 18. We do not knowingly collect personal data from children.
13. Changes to this policy
We may update this policy. We will post the new version on this page and change the “Last updated” date. If a change is significant, we will notify account owners by email before it takes effect.
14. Contact us
Cipher Co., Ltd.
99/103 Racha Thewa, Bang Phli District, Samut Prakan 10540, Thailand
Email: support@cipher.co.th
A Thai version of this policy is available at serpv.com/privacy/th. If the two versions differ, the English version prevails.