Wigo Privacy Policy
Courtesy translation. This English version is provided for convenience only. The Vietnamese version is the legally binding text and prevails in case of any difference.
This document will be updated when the law or the service changes. See also: Terms of Use · Payment Policy · Affiliate Program.
Summary:
- We collect only the data needed to operate Wigo, and we do not sell personal data.
- DeliVN's application servers, database, backups and email-sending server are located in Vietnam. Published sites, however, are delivered through Cloudflare, and some other services (Telegram, Google, the AI model providers Anthropic, OpenAI and Google) may be located abroad. See sections 7 and 8.
- Traffic statistics for sites you create use no cookies and do not store raw IP addresses. The Wigo pages themselves (home page, templates, pricing, the app) use an anonymous cookie only if you agree (section 12).
- You have the right to access, correct, delete, withdraw consent, object and complain (section 10).
- For data of visitors to your site, you are the controller and DeliVN is the processor (section 5).
- Wigo administrators cannot read your site content, posts or form data through the admin area (section 11a).
1. Who is responsible and who this applies to
- DeliVN (Deli Vietnam Informatics Services Company Limited (Công ty TNHH Dịch vụ Tin học Deli Việt Nam), details in section 16) is the controller and processor of the personal data of Wigo users (site owners, collaborators, affiliates, and people who contact us): accounts, payments, and activity in the app.
- For data of visitors to a site created by a site owner (such as contact forms and newsletter sign-ups), the site owner is the controller and DeliVN is the processor (section 5).
- This Policy applies together with Vietnam's Personal Data Protection Law 2025 (91/2025/QH15) and Decree 356/2025/NĐ-CP, and other applicable laws. Foreign laws (such as the GDPR) are applied only to the extent stated in section 13a.
2. Data we collect, purposes and bases
| Data category | Includes | Purpose |
|---|---|---|
| Account and sign-in | Email or phone number (phone numbers are verified through Telegram, together with the Telegram ID), sign-in time, IP address and browser information when you sign in or request an OTP, and the OTP and sign-in link code in hashed form. If you sign in with Google: your Google account ID, email and name (section 6a). | Verifying sign-in, preventing abuse, security. |
| Profile | Display name, avatar (if any), fields of interest; the version, time, IP and device when you agree to the terms. | Personalisation, template suggestions, keeping proof of consent. |
| Site content | Text, images, posts, translations, site settings and site versions. | Providing the service for building and publishing sites. |
| Payments | Order ID, plan, amount; full name or organisation name, tax code, address, and email for receiving invoices; images of transfer receipts you upload; bank transactions matched to orders (description, amount, time). | Reconciliation, plan activation, invoicing, accounting, tax obligations. |
| AI use | Questions you enter, related site information (page structure, block content, the site's AI profile), requests to generate images with AI and the images generated, feedback you rate, and the number of requests and tokens used. | Producing AI results, applying plan limits, improving quality. |
| Logs | Important actions (sign-in, plan change, site deletion, site suspension, etc.) with timestamps, and IP or device for some actions. | Security, incident investigation, legal compliance. |
| Affiliates | Display name, type (individual or business), tax code, bank account details for payouts, visits through referral links (counted only), and a one-way hash of the IP to detect self-referral. | Paying commissions, tax, fraud prevention. |
| Abuse reports | Site address, type, description, reporter's email (optional), and a hash of the reporter's IP. | Handling violations, preventing report spam. |
| Notifications and email preferences | The language you choose, your choice to turn nurture emails and weekly reports on or off, history of emails sent (email type, channel, time, result), and the mail-delivery log passed to the mail server (recipient address, subject, result; not the email content); for weekly reports: the number of views and distinct visitors to your site during the week. | Sending the right email in the right language, respecting your choices, limiting frequency, troubleshooting email delivery. |
| Support contact | Content you send to support@ or abuse@. | Support, resolving complaints. |
We do not intentionally collect sensitive personal data and do not ask you to provide it. Do not put other people's sensitive data into the AI or into a site without a lawful basis.
3. Basis for processing and consent
- We process data based on your consent (when you accept the Terms and this Policy; we keep the version, time and IP as proof), to perform the contract for using the service, to comply with legal obligations (invoices, accounting, requests from state authorities), and in other cases permitted by law.
- You may withdraw consent at any time (section 10). Withdrawing consent does not affect processing already carried out; if the data is necessary to provide the service, you may no longer be able to use the service.
- We send two kinds of email. Mandatory emails about your account, payments, expiry, violations and support: these are needed to operate the service and cannot be turned off. Nurture emails and weekly reports: guidance and suggestions when you are new to Wigo, and a weekly report of your site's views (sent to the site owner only). Both are part of providing the service to you, and you can turn them off at any time using the "Stop receiving this email" link at the bottom of the email (one tap, no sign-in needed) or in Profile, under Notifications. We keep the frequency low (no more than one nurture email per week, none sent between 21:00 and 07:00 Vietnam time, and the onboarding series stops once you buy a plan) and we do not send third-party advertising. If we have separate promotional offers, we will ask for separate consent and give you a way to decline.
4. Site traffic statistics
- Traffic statistics for your site use no cookies and do not store raw IP addresses. Each view records: the page viewed, the referring domain (if any), the country, the device type, and a one-way daily hash (computed from the IP, browser and date, using a secret key) used only to count distinct visitors within a day. The IP cannot be derived from this hash, and the hash changes every day.
- When a visitor views a site, the IP address is still handled temporarily by Cloudflare's infrastructure in order to deliver the page (see section 7).
- Site owners cannot see visitors' personal identities through the statistics.
5. Site visitor data (DeliVN as processor)
- The data includes: information visitors enter into contact forms or newsletter sign-up forms on your site (full name, email, phone number, message content, etc., depending on the form you design), the page it was submitted from, and the time; for shop or booking sites: order contents, totals, booked time slots; the lead notes and status that the site owner enters; and the visitor's email used to receive booking or order confirmations.
- Forwarding to Telegram (if the site owner enables it): when you connect Telegram to your site, each new contact or order (all the fields the visitor filled in) is forwarded to the Telegram chat or group you choose, through either your own bot or Wigo's shared bot. That data then sits on Telegram, outside Wigo's control. You are responsible for informing your visitors about this.
- The site owner is the controller: you decide what to collect, why, and for how long. You are responsible for informing visitors clearly, having a lawful basis or consent as required, publishing a privacy policy on your site, and responding to visitors' requests (access, correction, deletion, etc.). Do not collect sensitive data or children's data through forms unless the legal conditions are fully met.
- DeliVN is the processor: we only store this data and pass it to the site owner (viewable in the dashboard, through email, and through Telegram if you enable it) following your instructions; we apply the security measures in section 11; we do not use visitor data for our own purposes or for advertising; we assist you in responding to visitors' requests when reasonably asked; we notify you when an incident affecting the data occurs; and we delete the data when you delete it or when the site is deleted under the expiry lifecycle. We use only the sub-processors listed in section 7.
- Content of the data processing agreement. This section, together with the Terms of Use, forms the data processing agreement between you and DeliVN, covering: (1) subject matter, duration and nature of processing (storing and passing on your site visitors' data while you use Wigo); (2) the types of data and categories of people concerned (listed above); (3) processing on your instructions; (4) security measures (section 11); (5) sub-processors (section 7) and notice of changes; (6) assisting you in responding to data subjects' requests; (7) notifying you of incidents; (8) deletion or return of data at the end (section 9); (9) providing information so you can check compliance, on request. If you need a separate agreement, please contact us.
- Visitors who have a request about their own data on a site should contact the site owner directly. If the owner cannot be reached, send it to [email protected] and we will forward it to the site owner.
6. AI assistant
- When you use AI features, the content you enter and the related site information that helps the AI understand context are sent to the AI Center operated by DeliVN, and from there may be sent to a third-party AI model provider, which may be located abroad, to produce results. The automatic translation feature and the AI image generation feature likewise send the text or description to be processed in the same way. The AI Center routes AI requests to the model providers Anthropic (Claude), OpenAI and Google (Gemini), companies based in the United States; processing may take place outside Vietnam. Personal data in AI requests is limited to what you type and related site information. You should therefore not enter sensitive personal data of other people into AI requests.
- The system does not proactively send your passwords, OTPs or payment data to the AI. Do not enter unnecessary sensitive information into the AI.
- This feature is not available on plans that do not include AI. AI results may be wrong, and you must check them before publishing (see Terms, section 8). AI-generated text and images may be mistaken for real or human-made content; the site owner is responsible for reviewing and labelling AI-generated content where the law requires (Vietnam's 2025 Artificial Intelligence Law).
6a. Data from your Google account (the “Connect Google” feature)
- Sign in with Google: we only receive your email address, display name and Google account identifier (the basic
openid,email,profilepermissions) to create or open your Wigo account; these three items (Google account ID, email, name) are stored as your sign-in identity and are deleted when you delete your account. Wigo accesses no other Google data and stores no Google token when you only sign in. - Only when you click “Connect Google” and consent. Wigo requests these permissions: view the email of the connected Google account; manage and view Google Analytics (
analytics.edit,analytics.readonly); when you enable ad tracking, manage Google Ads (adwords). Each group is requested only when you turn on the corresponding feature. - What Wigo uses it for: creating or selecting a Google Analytics property and data stream for your website and marking key events (contact leads); creating a conversion action in your Google Ads account and obtaining the tracking tag to place on your website. Wigo does not create or modify campaigns, ads, budgets or bids, and does not read your Google Ads performance or customer data.
- Storage: we store the Google account email, account identifier, the list of granted permissions, identifiers of the items Wigo created (such as property and conversion IDs) and a refresh token that is encrypted (AES-256-GCM). The token is used only to perform the actions above, is never written to logs and is never shown to anyone.
- Limited Use: Wigo’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically: the data is used only to provide and improve these user-facing features; it is not sold, not transferred to data brokers, not used for advertising and not used to train AI models; DeliVN staff do not read it unless you allow it for support, it is required by law, or to handle abuse.
- Google data stays in your account. The property, conversions and statistics belong to your Google account and remain if you leave Wigo.
- Revocation: click “Disconnect” in Site settings → Technical (Wigo revokes the token at Google and deletes it from our systems), or revoke it at myaccount.google.com/permissions. When you delete your Wigo account, the Google connection (including the refresh token) and your Google sign-in identity are deleted. Items Wigo created in your Google account are not deleted; you may delete them yourself.
6b. Sign-in with Facebook
If you choose to sign in with Facebook, we only receive what you allow: your Facebook ID, display name and email address (if you share it). The sole purpose is to authenticate you and create or sign in to your Wigo account. Wigo does not post, and does not read your friends, messages or any other data on your Facebook, and does not sell this data. If Facebook does not return an email (for example a phone-only account) we do not create an account and ask you to sign in with email instead. We do not store Facebook access tokens. You can revoke access at any time in Facebook (Settings → Apps and Websites).
7. Data sharing and processors
We share data only when needed to operate the service, and we do not sell personal data. The list of sub-processors below is kept up to date on this page, and we will announce material changes. Recipients of data include:
| Party | Role | Data |
|---|---|---|
| Cloudflare (Worker, R2, KV, Cloudflare for SaaS, possibly Web Analytics/Insights) | Storing and delivering published sites, attaching custom domains; may be located abroad | Published site content, custom domains, technical access data (such as the IP when a visitor views a site) |
| Server, database, backup and file-storage (MinIO/storage-service) infrastructure operated by DeliVN; location: application servers, database, backups and the email-sending server (DeliVN's own mail server) are located in Vietnam | Running the app, storing accounts, content and backups | All data categories in section 2 |
| Email delivery service (operated by DeliVN) | Sending OTPs, receipts, expiry reminders, notifications, nurture emails and weekly reports | Email address and email content |
| Telegram | Verifying phone numbers when signing in by phone number; sending notifications; forwarding site visitors' contacts and orders to the Telegram chat the site owner chooses (the owner's own bot or Wigo's shared bot); may be located abroad | Phone number and Telegram ID that you share with the bot; all fields a visitor filled in a contact or order (name, phone, email, message, items, etc.) |
| Google Drive (encrypted backups only) | Holds the second copy of the database for disaster recovery; may be located abroad | Encrypted backup files (they contain the data in section 2 but Google cannot read them) |
| Google (sign-in and Google APIs) | Sign in with Google; “Connect Google” (Analytics, Ads) when you enable it | Data described in section 6a |
| img.vietqr.io | Generating the bank-transfer QR image shown on a site's “bank transfer” block; the image is loaded from this service | The image address contains the bank account number, amount and transfer note set by the site owner; this service also sees the viewer's IP |
| Unsplash | Source of stock photos used in templates and sites | Technical data when the browser loads an image (such as the IP) |
| Meta, Google (Analytics, Ads, Tag Manager) on a site owner's site | Only when the site owner enables them or uses “Connect Google”; the site owner is the controller | Visit data of visitors to that site (see section 12) |
| AI Center and AI model providers | Producing AI results, AI images, translation | Content described in section 6; providers: Anthropic (Claude), OpenAI, Google (Gemini), based in the United States, processing may be outside Vietnam |
| Banks, transaction-notification services and the e-invoice service | Payment reconciliation, issuing invoices | Payment and invoice data described in section 2 |
| DeliVN's partners (if your plan is provided by a partner) | Managing members under their contract | The partner knows you are their member, your email, plan status and published site information (such as name and site address) |
| People co-editing a site | Collaboration you invited yourself | Content and permissions within that site |
| Competent state authorities | Upon a lawful written request | Data as requested |
We require processors to protect data under their contracts or terms of service.
7a. Requests from public authorities
- Basis. We provide personal data to a public authority only on a written request from a competent authority under Vietnamese law (such as cybersecurity, personal data protection or procedural law), stating the legal basis, the scope of data and the purpose. The Personal Data Protection Law allows processing without your consent in certain cases (such as preventing and combating crime and violations of law, or serving the activities of state agencies); we still apply the steps below.
- Legality review. DeliVN's data protection officer reviews every request before we respond: proper authority, proper form, legal basis and scope. We consult counsel where needed.
- Challenge and clarification. If a request lacks a legal basis, exceeds authority or is overly broad, we ask the authority to clarify or narrow it, and object to or decline the part without sufficient basis through the procedures the law allows.
- Data minimization. We disclose only what is necessary within the scope of the request (never the whole database), and we cannot provide encrypted content for which we hold no key.
- Documentation. We record the request, the requesting authority, the legal basis, who handled it, the data provided and the date, and keep the records as required by law.
- Notice to you. Where the law permits and notice would not obstruct an investigation, we will notify you. We do not provide user data to foreign public authorities without a basis under Vietnamese law.
8. Transfer of data abroad
Some data (published site content, technical delivery data, content sent to the AI, phone numbers verified through Telegram, site visitors' contacts and orders forwarded to Telegram if the site owner enables it, and Google data when you use sign-in or “Connect Google”) may be stored or processed on servers outside the territory of Vietnam. DeliVN's application servers, database, backups and email-sending server are located in Vietnam; content sent to the AI is routed by the AI Center to Anthropic, OpenAI and Google (US companies). By agreeing to this Policy, you agree to such transfers. DeliVN performs the related obligations under the law on transferring personal data abroad where the law requires it.
9. Retention periods and deletion
| Data | Retention period |
|---|---|
| Account, profile, site content | For as long as the account remains active. When a plan expires, the site and its data are permanently deleted from day 45 after the expiry date (Terms, section 4). |
| When you delete a site | The site stops being served and its data (content, backups, images, visitor form data) is permanently deleted right after; if the deletion step hits a system error it is retried automatically. A site in the deleted state that has not yet been cleaned up is permanently removed after at most 30 days. |
| When you delete your account | The account is anonymised: identifying information (email, phone number, name, avatar) is removed, sign-in sessions are deleted, and the Google connection (refresh token) and Google sign-in identity are deleted. Some records are kept as shown in the rows below. |
| Visitors' form data | Same lifecycle as the site, or until the site owner deletes it. |
| Orders, receipts, invoices, accounting data, commission payout and tax information | For the retention periods the law sets for accounting documents, invoices and tax records, including after you delete your account. |
| Administrative logs and proof of consent (including IP and device) | 24 months, to meet system-log retention duties and to resolve disputes. Proof of consent is also kept as the version and time in the account record while the account exists. |
| OTP codes and sign-in link codes | Valid for 10 minutes; records are deleted automatically after 7 days. Telegram sign-in data is deleted 1 day after it expires. |
| Sign-in sessions | Sessions that expired more than 30 days ago are removed automatically. |
| Mail-delivery log (recipient address, subject, result) | 90 days (deleted automatically), to investigate when you report not receiving an email; the email content (including confirmation codes) is not stored. |
Wigo traffic statistics (anonymous wg_vid ID) | 13 months. |
| AI conversations | Kept with the site; the conversation content is deleted when the site is deleted. |
| Abuse reports (including the reporter's email) | The reporter's email is deleted 90 days after the report is handled (a one-way hash is kept to prevent spam). |
| Database backups | Taken daily and encrypted (AES-256). One copy is kept on a DeliVN machine in Vietnam for 14 days; a second copy is kept in DeliVN's Google Drive (encrypted, Google does not hold the key), for the latest 14 days and one copy per week for 8 weeks. Backups are not edited for each deletion request: deleted data disappears from backups when that backup expires (about 10 weeks at most). Site files and images are deleted together with the site. |
Deleted data cannot be recovered. You can delete your account yourself on the Profile page (after deleting or transferring all of your sites), or request it through [email protected].
10. Your rights
Under personal data protection law, you have the right to: be informed about processing; consent or not consent; access; correct (or request correction); request a copy; withdraw consent; delete or request deletion; restrict processing; object to processing; complain, report violations, and sue, and claim compensation for damage as provided by law; and protect your own rights.
- How to exercise them: edit your profile yourself, download your content (if your plan includes site export) and delete your account in the app; or send a request to [email protected] (subject "Personal data"), with information to verify that you are the account owner (for example, replying from the registered email). We may ask for more information to verify your identity before acting, and we process requests without undue delay and within the period set by law. Privacy contact: [email protected] (currently the shared support mailbox; if we set up a dedicated address we will update it here).
- Requests about visitors to a site owner's site: we forward the request to the site owner, who is the data controller, to handle (section 5).
- We may refuse or retain part of the data where the law requires retention (for example invoices and receipts) or where a request is invalid, and we will explain the reasons.
- If you believe your rights have been violated, you may complain to us or to the competent state authority for personal data protection.
- You are responsible for providing accurate data and respecting other people's personal data.
10a. Deleting your data (including when you signed in with Facebook)
- Delete it yourself in Wigo: sign in → Profile → Data & account → Delete account, and type your email to confirm. You must first delete or transfer the sites you own. Deletion removes your email, name, profile picture, sign-in links (Google, Facebook, Telegram) and collaboration access.
- Send a request: email [email protected] with the subject “Delete my data”, from your registered email (or tell us the Facebook display name you signed in with). We verify that you own the account and process the request without undue delay, within the period required by law.
- About Facebook: removing the Wigo app in Facebook (Settings → Apps and Websites) only revokes access and does not delete your Wigo account; to delete your data use one of the two ways above. After deletion we erase the data received from Facebook (ID, name, picture, email).
- Data we may keep: accounting records and invoices as required by law, and security logs for the period stated in section 9; we will explain whenever we decline or keep part of the data.
11. Security measures and incident notification
- Encrypted connections (HTTPS); OTPs, sign-in link codes and session codes are stored in hashed form; Google and Telegram tokens of site owners are encrypted (AES-256-GCM); internal access is permissioned by role and administrative actions are logged; rate limiting to prevent password guessing and spam; backups of site content; checking and scanning for scam patterns when sites are published.
- No system is completely secure. When an incident affecting personal data occurs, we will handle it, notify affected users without undue delay (and the site owner if it concerns their visitors' data), and report to the competent authority within the period required by law.
- You help protect your account by keeping your email, phone number and sign-in devices secure.
11a. Who at Wigo can see what
- Wigo administrators (admin, view-only and accountant roles) can see in the admin area: user emails, plans, site names and addresses, site owner emails, usage statistics and each user's usage journey, abuse reporters' emails; billing and order data (buyer name, tax code, address, payment proof images, invoices); affiliates' bank details for commission payouts; and the mail delivery log (recipient and subject, no email body). The accountant role sees only billing and affiliates.
- Administrators cannot read through the admin area: drafts, pages, posts and media in your sites; visitors' form or order data; OTP codes; Telegram or Google tokens. Administrators cannot log in as a user. Administrators' write actions (blocking a user, disabling a site, granting a plan, etc.) are logged.
- Engineers who operate the servers and databases can technically access stored data (except OTP and session codes, which are stored only as hashes, and tokens, which are encrypted). They do so only to operate, fix and restore the service, under confidentiality commitments and the principle of least privilege.
- Affiliates' identity documents (ID card photos, business registration certificate, phone number): only the file owner, administrators and the accountant can view them, to approve applications and pay commission; every view is logged. Read-only admin accounts and other users cannot view the documents; in the admin list the ID number shows only its last 4 digits.
12. Cookies and browser storage
The table below lists what Wigo stores in your browser when you use the Wigo pages and app themselves.
| Name | Purpose | Duration | Consent needed? |
|---|---|---|---|
| Sign-in session cookie | Keeps you signed in | 14 days | No (necessary) |
wg_consent | Remembers your cookie choice | 13 months | No (necessary) |
wg_dev | Random device ID, set when you sign in, to recognise a new device (security, audit) | 2 years | No (necessary for security) |
wg_gstate | State during Google sign-in | A few minutes | No (necessary) |
wg_vid (and its localStorage copy) | Anonymous ID to improve Wigo (described below) | 13 months | Yes (only if you click “Agree”) |
wg_int | Internal-device flag, set only for Wigo administrators | 5 years | Not applicable to ordinary users |
localStorage wigo.ref | An affiliate's referral code when you arrive through a referral link, so it can be credited when you sign up | 90 days | No separate prompt at present; stored only when you arrive through a referral link |
localStorage wigo.lang | The interface language you choose | Until you clear it | No (interface setting) |
| sessionStorage (some technical entries) | Temporary memory within a session (for example that a referral visit was already counted, sign-in state) | Ends when you close the tab | No |
- Anonymous cookie to improve Wigo (only when you click "Agree" on the notice bar):
wg_vidis a random string containing no personal information. We use it to know how many people return, where they come from (referring page, campaign) and at which step they stop when using Wigo. We do not store IP addresses, do not sell data, and do not use it for advertising. When you sign in, the anonymous ID is linked to your account to understand the journey from first visit to use; this data is visible only to Wigo administrators and is deleted after 13 months of inactivity. - If you have not chosen, or choose "Necessary cookies only": no anonymous cookie is set; we count only total daily visits (page, source, country, device type), with no person ID and no IP stored.
- You can change your choice at any time: Change cookie choices. Choosing "Necessary cookies only" deletes the anonymous ID on this device.
- User-created sites: Wigo's own runtime on the site sets no cookies by itself. However, when a site owner enables Google Analytics, Google Ads, Meta or Google Tag Manager (including through “Connect Google”), those tags load on the site: while the site's cookie bar is on, the tags load only after the visitor agrees (the visitor's choice is kept in the browser as
wg_cons, 365 days); the site owner can turn the cookie bar off, in which case the site owner is responsible for obtaining consent. The site owner is the controller and is responsible for publishing their own privacy notice to their visitors.
13. People under 18
Wigo is intended for people aged 18 or over (or with a guardian's consent). If we find that we have collected data of a person under the permitted age without appropriate consent, we will delete that data.
13a. Other regions
We mainly serve customers in Vietnam. If you are in the EU/UK/US, you can still send an access/deletion request under section 10; we will handle it under the law that applies to us. Wigo does not sell personal data and is not directed at people under 18 (section 13). We do not claim to have fully implemented every requirement of the GDPR or the CCPA.
14. Changes to this Policy
When there is a material change, we will notify you in the app or by email a reasonable time before it applies, and ask for consent again where required by law. The version and effective date are always shown at the top of the page.
15. Contact about personal data
Contact point for personal data requests and complaints: [email protected] (subject "Personal data"). To report violating content on a site: the Report Abuse page or [email protected].
16. Data controller information
- Deli Vietnam Informatics Services Company Limited (Công ty TNHH Dịch vụ Tin học Deli Việt Nam) (DeliVN).
- Registered address: 791/21/2/13 Tran Xuan Soan, Tan Hung Ward, Ho Chi Minh City · Tax code: 0313333712 · DeliVN's personal data protection contact point: Nguyen Thai Binh (Legal representative) — contact [email protected], subject “Personal data”
Change history
- 2026-11-30: Version 2026-11-30: effective from 30 November 2026; we notified users by email and in the app; existing users agree again with a single click. Clarified server location (Vietnam), AI model providers, the 24-month log retention period and the personal data contact point.
- 2026-11-13 (addition): legal basis updated to Vietnam's Personal Data Protection Law 2025 and Decree 356/2025/NĐ-CP; section 5 now states data forwarded to Telegram and the content of the data processing agreement; section 6 adds AI images and the labelling responsibility; section 7 adds sub-processors (Telegram, Google, img.vietqr.io, Unsplash, Cloudflare, tags enabled by site owners); section 9 retention table corrected to actual behaviour (site deletion, account deletion, OTP 7 days, etc.); section 10 how to send requests; new section 11a “Who at Wigo can see what”; section 12 full cookie table; new section 13a “Other regions”.
- 2026-11-12 (addition): section 6a now covers “Sign in with Google” (email, name and account identifier only; no token stored).
- 2026-11-12 (addition): added section 6a on data from your Google account when using “Connect Google” (permissions requested, purposes, encrypted storage, Limited Use commitment, revocation).
- 2026-11-06 (addition): added the cookie notice bar and section 12: anonymous cookie
wg_vid(13 months, only if you agree) to understand the user journey; if you do not agree, only total visits are counted, with no person ID and no IP. - 2026-11-01 (addition, version unchanged): clarified the two kinds of email sent to users (mandatory; nurture and weekly reports that can be turned off with one tap), and added the data category "Notifications and email preferences". No new processing purpose was added, so no new consent is needed.
- 2026-11-01: full review and rewrite: data table, purposes and bases for processing; roles of controller and processor (site visitor data); cookie-free statistics and daily hash; AI sending to the AI Center and third parties; list of data recipients; transfer of data abroad; retention table; full data subject rights; security measures and incident notification; cookies; people under 18.
- 2026-10-29: previous version.