Policy
Privacy policy
Effective 12 October 2026 · Version 2.0
This is an English translation for convenience. The Vietnamese version is the legally binding version; if the two differ, the Vietnamese version prevails.
Version 2.0 compared with 1.9: only adds a Meta Ads part for when you connect Meta Ads — section 2.5 (data we store), section 5a (data received from Meta), one row in section 7 and one item in section 9, with links to the data deletion instructions; section 12 adds the address on the business registration certificate (the certificate has not yet been updated after the administrative-unit merger). AdPilot does not connect to Meta Ads yet. This version changes nothing for Google Ads, does not change how existing data is handled and does not narrow any of your rights, so it is not a significant change under section 11. Version 1.9 compared with 1.8: section 3 adds two cookies that remember and guess your language (alfa_ngon_ngu, alfa_ngon_ngu_doan); section 3.2 corrects the default interface after deleting the cookie to dark, not light. Version 1.8 compared with 1.7: section 2.4 makes clear the change log is append-only for 24 months and then deleted automatically on the schedule in section 7 — the previous version said “not deleted”, contradicting the retention table in section 7 itself. Version 1.7 compared with 1.6: lists every field of the log of rejected tool calls in section 7 — adding the AI app that made the call, the permission level at the time, the number of times that day and the first and last time; the log already recorded these fields. Version 1.6 compared with 1.5: adds the error message of a failed tool call to sections 2.4 and 7 — kept 30 days to find out why the call failed. Version 1.5 compared with 1.4: adds section 2.3 — referral data stored on the server; it was already running but section 2 hadn’t declared it (the “Technical data” section is now 2.4). Version 1.4 compared with 1.3: adds the alfa_ref key (localStorage) to section 3 — remembering a referral code; it was already running but the table hadn’t declared it. Version 1.3 compared with 1.2: adds the alfa_giao_dien cookie to section 3 — remembering your light or dark mode choice. Version 1.2 compared with 1.1 (30/09/2026): adds section 3 — listing every cookie and piece of data stored in your browser, and the files loaded from elsewhere. Version 1.1 compared with 1.0 (20/09/2026): makes clear the 90 days of conversation retention count from the last message in the conversation (now section 7). No version has narrowed your rights.
This document explains what data ALFA AdPilot collects, what it is used for, how long it is kept, and how you can make it stop.
1. Who is responsible
ALFA Media Co., Ltd. (Công ty TNHH ALFA Media — “ALFA”, “we”), Vietnam, operates the ALFA AdPilot service at alfasoftwares.com.
2. What we collect
2.1 Information you provide
- Your name, email and phone number when you create an account or contact us.
- Payment information when you buy a plan. We don’t store card numbers — that is handled by the payment gateway.
2.2 Google Ads data, obtained through the Google Ads API
After you grant access through Google’s consent screen, AdPilot reads the following data from the Google Ads accounts that you already have access to:
- The list of accounts: ID, name, currency, time zone, status.
- Structure: campaigns, ad groups, ads, keywords, negative keyword lists, assets.
- Performance: spend, impressions, clicks, conversions, broken down by device, location and network.
- Budgets and billing status.
- Approval status and policy warnings for ads and accounts.
- Change history, including changes made by other people outside AdPilot.
- Keyword research data provided by Google.
We also store Google’s authorisation tokens to keep the connection alive. Tokens are encrypted at rest.
2.3 Referral data
If you arrive through a link with a referral code (?ref=) and your account is created after that first visit, then when you sign in we store on the server — once only — the referral code, the time, the source (the utm_source parameter, or the domain of the page that sent you), the channel (utm_medium) and the address of the page you landed on, for both the first and the most recent touch. If your account already existed, or the code refers your own organisation, no record is stored.
This record is tied to your organisation, not to you personally, and it exists for one reason only: to credit the referrer’s commission correctly. Because it is the basis of a payment, we keep it for as long as the organisation exists — unlike the copy in your browser (section 3), which is deleted as soon as it has been sent.
If you come straight to alfasoftwares.com without a referral link, no record is created.
2.4 Technical data
- Usage log: which tool you called, when, and whether it succeeded or failed — to apply your plan’s limits and to help when something goes wrong.
- The error message when a tool call fails: what AdPilot replied to you, and Google’s explanation with Google’s request ID if there is one. That message may include your organisation name, sign-in email and the part of the data you sent that Google quoted back. Kept for 30 days (section 7).
- Change log: every proposal, approval, apply and undo. This log is append-only — nobody can edit or delete it for 24 months, administrators included; after 24 months the system deletes it automatically on the schedule in section 7. That is a safety feature, not an oversight.
- IP addresses are hashed one-way to prevent abuse. We don’t store the original IP address.
2.5 Meta Ads data, when you connect Meta Ads
AdPilot does not connect to Meta Ads yet. When you connect your Meta account, we store:
- Your Meta user ID and display name.
- The ad accounts you authorize ALFA AdPilot to access.
- The access token issued by Meta, stored encrypted.
- Cached advertising metrics used to generate reports.
- A log of the proposals and changes you approved in ALFA AdPilot.
How to request deletion: see the data deletion instructions.
3. Cookies and data stored in your browser
Below is everything ALFA Software stores in your browser. Each item does one specific job: keeping you signed in, bringing you back to the right place after signing in, or remembering an interface choice you made yourself.
| Name | Type | What it’s for | How long it’s kept |
|---|---|---|---|
__Secure-alfa-phien | Cookie | Keeps you signed in while you use the app. The server reads it to know who is acting. Only sent to pages under /ung-dung and only over HTTPS; it carries a short-lived access token, not the session refresh token. | Up to 1 hour, renewed automatically while you’re using it. Signing out deletes it immediately. |
alfa_ben | Cookie | Remembers whether you collapsed or expanded the sidebar, so you don’t have to set it again next time. | 365 days from the last time you changed it |
alfa_giao_dien | Cookie | Remembers whether you chose light or dark mode, shared by the members area and the AdPilot app — one choice, followed everywhere. | 365 days from the last time you changed it |
alfa_ngon_ngu | Cookie | Remembers the language you chose (Vietnamese or English) for the public pages, the members area and the app — one choice, followed everywhere. | 365 days from the last time you chose |
alfa_ngon_ngu_doan | Cookie | The language the system guesses from your country when you haven’t chosen one yourself, so the page shows the right language the first time. Only a suggestion, not your choice, and it contains no information about you. | 1 day |
alfa_dn | localStorage | Marks that you have a session, so the public pages show the right button — “Go to the app” instead of “Sign in”. Just a marker; it contains no information about you. | Until you sign out |
alfa_quay_lai | sessionStorage | Remembers the page you were on before you clicked sign in, so you’re taken back to it after returning from Google. Keeping it here rather than in the URL is deliberate: a URL can be tampered with to send you to a fake page. | 15 minutes, only in the open tab |
alfa_ref | localStorage | Only written when you arrive through a link with a referral code (?ref=) and that code is real — the code is sent to the server once to be checked. Remembers the code so that when you sign in, the referrer is credited with the commission. The record holds: the referral code, the time, the source (the utm_source parameter on the link, or failing that the domain of the page that sent you), the channel (the utm_medium parameter) and the address of the page you landed on — both the first time and the most recent. Nothing about your identity. When you sign in, the record is sent to be credited and then deleted from your browser. | 30 days from the first touch; deleted from your browser as soon as it has been sent when you sign in |
alfa_goi_chon | sessionStorage | Remembers the plan you just clicked “Choose this plan” on in the price list while you sign in, so that card opens afterwards. It only opens and points to the card — it never places an order by itself; you still click to order. | 15 minutes, only in the open tab |
| Sign-in session | localStorage | Keeps you signed in between visits. Managed by Supabase’s authentication library; our servers can’t read this area. | Until you sign out |
We don’t set advertising cookies, behavioural tracking cookies, or cookies from third-party analytics tools.
The table above is checked automatically against the source code before every release: if the code stores something this table doesn’t list, or the table lists something the code no longer stores, that release is blocked. In other words, this table isn’t a hand-copied list left to go stale.
Because the items above are all needed for signing in to work, or are your own interface choices, we don’t show a cookie consent banner — it wouldn’t be honest to ask a question where answering “no” means you can’t sign in.
3.1 Files loaded from elsewhere
Our pages load fonts from fonts.googleapis.com and fonts.gstatic.com (Google Fonts), and the account page loads the authentication library from cdn.jsdelivr.net. When your browser fetches these files, your IP address is visible to those services, as with any website you open. These files don’t set cookies, and we don’t send any information about you with them.
3.2 How to delete them
Your browser settings let you view and delete cookies and site data per domain. Delete alfa_ben and the sidebar goes back to its default; delete alfa_giao_dien and the interface goes back to the default (dark) mode. Delete the session cookie or the localStorage area and you’ll be signed out and need to sign in again — no data in your account is lost.
4. What we use it for
- Running exactly the features described on the home page: finding what needs attention, pre-checking changes, carrying out changes you’ve approved, undoing them.
- Authenticating you and applying your plan’s limits.
- Technical support when you ask for it.
- Detecting and preventing abuse.
We do not use your data to advertise to you or to anyone else.
5. Compliance with Google’s API user data policy
ALFA AdPilot’s use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically, your Google data:
- Is not sold to anyone.
- Is not transferred to third parties for advertising, marketing, or building user profiles.
- Is not used to train AI models.
- Is not read by anyone at ALFA, except in three cases: you ask for support and agree to it, the law requires it, or it is necessary to investigate a security incident.
5a. Data received from Meta (when you connect Meta Ads)
When you connect Meta Ads, the data ALFA AdPilot receives through the Meta Marketing API is used only for the purposes in section 4: reading advertising metrics and building proposals for you to approve. That data:
- Is not sold to anyone.
- Is not used for any other advertising purpose.
- Is not used to train AI models.
How to revoke access and request deletion: see the data deletion instructions.
6. Who it is shared with
We don’t sell data. We use a few infrastructure providers to run the service, and they only process data on our instructions:
| Type | Used for |
|---|---|
| Server and CDN providers | Running the website and service |
| Database provider | Storing accounts, settings and logs |
| AI model providers | Generating replies when you chat with AdPilot on the ALFA platform. Under these providers’ API terms, data sent through the API is not used to train models |
| Payment gateway | Processing transactions. We never receive your card number |
If you use AdPilot from your own Claude or ChatGPT, the conversation stays in your AI account and is governed by that provider’s privacy policy. We only receive the tool calls.
7. How long we keep it
| Type of data | Retention |
|---|---|
| Google authorisation tokens | Until you revoke access or delete your account |
| Cached Google Ads data | Up to 30 days, then deleted automatically |
| Meta Ads data (when you connect) | See the data deletion instructions |
| Conversations on the ALFA platform | 90 days from the last message in the conversation, then deleted automatically — a conversation you’re still using isn’t deleted halfway through. A conversation with no messages counts from when it was created. |
| Change log and approval log | 24 months — needed for tracing and undo |
| Log of rejected tool calls | 30 days — records only the organisation ID, the AI app that made the call, the permission level at the time, the tool name, the error type, the number of times that day and the first and last time, so we can find broken configurations. Doesn’t record what you sent. |
| Error messages of failed tool calls | 30 days, then deleted automatically — what AdPilot replied to you and Google’s explanation if there is one, so we can find out why the call failed. The message may include your organisation name, sign-in email and the part of the data you sent that Google quoted back. Only ALFA’s operations team can see it, when looking into a fault. |
| Account records and invoices | For as long as Vietnamese accounting law requires |
8. Security
- Encryption in transit end to end, and encryption at rest.
- Tokens and sensitive fields are never written to logs or shown in error messages.
- Internal access on a least-privilege basis.
Being straight about limits: no system is perfectly secure. We put up barriers and keep records; we don’t promise what nobody can guarantee.
9. Your rights
- Revoke Google access at any time on the access management page of your Google Account. Once revoked, AdPilot can’t read anything any more.
- Remove Meta Ads access if you have connected it: see the data deletion instructions.
- Request a copy of the data we hold about you.
- Request deletion of your account and data. We handle it within 30 days, except for what the law requires us to keep. Step by step for Google Ads and Meta Ads: see the data deletion instructions.
- Request correction of wrong information.
Send requests to the address in section 12.
10. Children
The service is for organisations and adults. We don’t knowingly collect data from anyone under 18.
11. Changes to this policy
When there’s a significant change, we update the date at the top of this page and notify active users by email before the change takes effect.
12. Contact
ALFA MEDIA COMPANY LIMITED — registered name:
CÔNG TY TNHH ALFA MEDIA
Mã số thuế: 4500659694 (tax ID)
Địa chỉ trụ sở: Lô 60, Khu quy hoạch giống thủy sản An Hải, thôn Hòa Thạnh, xã Phước Dinh, Tỉnh Khánh Hòa (registered address, Khanh Hoa Province, Vietnam)
Địa chỉ trên Giấy chứng nhận đăng ký doanh nghiệp: Lô 60 Khu quy hoạch giống thủy sản An Hải, thôn Hòa Thạnh, xã An Hải, huyện Ninh Phước, tỉnh Ninh Thuận (address on the business registration certificate, before the 2025 administrative-unit merger)
Email: —
Phone & Zalo: —