Privacy Policy

This English version is a translation provided for convenience. If it differs from the Vietnamese version, the Vietnamese version prevails.

This page explains what personal data 1Go.vn collects, why, how long we keep it, and how you can exercise your rights. Key points: we do not store the IP addresses of people who click shortened links, we do not use advertising or analytics cookies, and we do not sell data.

Legal entity information

The personal data controller is Công ty TNHH Đầu tư Công nghệ KDIGI (hereinafter referred to as “1Go” or “we”).

Legal entity name: Công ty TNHH Đầu tư Công nghệ KDIGI
Registered address: Số 69 đường 8C2, KDC Hưng Phú 1, Phường Hưng Phú, Quận Cái Răng, TP. Cần Thơ
Tax ID: 1801724493
Data privacy email: [email protected]
Abuse report email: [email protected]
Security vulnerability email: [email protected]

1. Scope and legal basis

This policy applies to three groups of people:

visitors to shortened links: you click a link created by our customer and do not need an account;
users with accounts: workspace owners and members, administrators;
people who submit abuse reports: you use the /report page or email [email protected].

We process personal data in accordance with Vietnamese personal data protection law, including Law No. 91/2025/QH15 on Personal Data Protection (Luật Bảo vệ dữ liệu cá nhân số 91/2025/QH15) and Decree 356/2025/ND-CP (Nghị định 356/2025/NĐ-CP). We are reviewing, together with legal counsel, the classification of visit statistics data under these instruments and the accompanying filing procedures; this policy may be updated based on the outcome of that review.

2. Data we process

2.1 Visitors to shortened links

For each click on a link, we record an entry containing:

country, city, region (estimated from the connection), autonomous system number (ASN), and the data center serving you;
device type, operating system, browser (classified from the User-Agent);
referring page domain (if any) and UTM parameters set by the link owner;
access channel (link or QR code) and bot flag;
a daily anonymous visitor ID.

We do not store your IP address. The IP address and User-Agent are used only at that moment to redirect and calculate the anonymous ID, and then discarded. The anonymous ID is a 16-character hash calculated from the network address, the User-Agent, and a secret value that changes every day (Vietnam time); this secret value is not stored. Therefore, the ID for the same person differs from day to day, and the number of “unique” visitors is meaningful only within each day.

Cloudflare, our redirect network provider, still sees your IP address when forwarding traffic (see section 5).

2.2 Users with accounts

Account: email, display name, profile picture (if you sign in with Google), role, memberships, and workspaces.
Login sessions: IP address, User-Agent, and session creation time.
Account security: two-factor authentication settings (TOTP, backup codes), passkeys (public key and device name), Google account links, email confirmation codes (stored as hashes).
Consent history: the version of the Terms and this Policy you agreed to and the time (UTC).
Content you create: links (destination URL, title, link password stored as a hash), domains, folders, tags, API keys (stored only as hashes), vouchers used.
Aggregated daily statistics for links (not personally identifying).
Audit logs: record important actions, such as blocking or unblocking a link. For system administrator actions, the log also includes the administrator's IP address and User-Agent.

2.3 People who submit abuse reports

The address of the link reported, the reason, your notes, contact email (optional), and a hash of the IP address you used to submit the report, keyed with a secret; we do not store the raw IP. Emails sent to [email protected] are handled using the email content itself and the sender's address.

2.4 Technical logs

Operational logs from the redirect infrastructure (5% sampled, containing no IP addresses and no destination addresses) and metrics, traces, and logs from the monitoring system (containing no raw IPs, tokens, API keys, or destination addresses with parameters). Login rate-limit counters may contain IP addresses for a short period.

2.5 Visitors to bio pages, forms, and pixel integrations

For each bio page view, we record technical statistics (country, region, device, access channel, and daily anonymous visitor ID); we do not record the city in bio view records. We do not store visitors' raw IP addresses in the bio view analytics system.

If the bio page owner configures a server-side pixel (Meta Conversions API, TikTok Events API, or Google Analytics 4 Measurement Protocol), 1Go's server forwards the visitor's raw connection IP address and User-Agent to the configured platform to send events. The bio page owner decides the pixel configuration and is the data controller for that activity; 1Go processes the events at the owner's direction. These platforms are located abroad; see section 5.

When you fill in information in an information collection form or place a product order on a bio page, the data you enter (such as full name, email, phone number, and notes) is transferred to the bio page owner for management under the Creator Policy.

3. Purposes and legal bases for processing

Link redirection and service operation: to perform the service you or our customer requests.
Account creation and management, login, and security: to perform the Terms of Use and based on your consent at registration.
Visit statistics for link owners: legitimate interests in providing analytics services to customers, with data minimized as described in section 2.1.
Fraud and abuse prevention (safety checks, report handling, rate limiting, anti-bot): legitimate interests and the obligation to protect visitors.
Security and auditing of administrative actions: legitimate interests and the obligation to protect data.
Evidence of your consent: the obligation to demonstrate consent.

We do not sell personal data, do not use data for advertising, and do not create personal profiles of link visitors.

When you register, you yourself check the box agreeing to the Terms of Use and this Policy; this box is never pre-checked. We record the version you agreed to (currently 2026-10) and the time of consent in UTC. When the version changes, you are taken to a re-consent page on your next login, and each consent is recorded in the consent history.

You can withdraw consent by requesting account deletion (section 8). Withdrawal does not affect processing already lawfully carried out before that.

5. Processors and cross-border data transfers

We use the following providers; some operate abroad or on global infrastructure for which we cannot choose the region:

Cloudflare (Workers, KV, Analytics Engine, R2, Turnstile): redirection and traffic protection, storage of link records, storage of visit records (90 days), storage of encrypted backups (we hold the encryption keys), and Turnstile bot protection on some forms. Cloudflare sees your IP because it is the traffic forwarder; we do not record that IP.
Google: Google sign-in (if you choose it; Google provides us with your email, name, and picture) and Google Web Risk to check the destination address of new or edited links. The address sent has the fragment and credentials removed but retains query parameters, and does not include the creator's identity. Therefore, do not put other people's personal data in destination addresses.
Email delivery provider: receives your email address and message content (confirmation codes, workspace invitations). The provider's name and country are currently provided when you send a request to [email protected].
Telegram (internal operational alerts): does not receive your personal data.

For cross-border transfers of personal data, we prepare an impact assessment dossier and submit it to the competent authority when required by law.

6. Retention periods

Link visit records (section 2.1): 90 days, after which they are automatically deleted; individual records cannot be deleted separately.
Aggregated daily statistics: until the workspace is deleted.
Account (email, name, picture): until you request deletion. On deletion, the account is anonymized: the email is replaced with an unusable address under the 1go.invalid domain.
Workspaces of deleted accounts: stop being served within 1 day and are permanently deleted 30 days after that.
Deleted links: recoverable for 7 days, then permanently deleted.
Login sessions: valid for 7 days; the session's IP address and User-Agent are deleted from records after 90 days.
Rate-limit counters (containing IP addresses): deleted when idle for more than 24 hours.
Audit logs: 12 months; IP addresses and User-Agents in the logs are deleted after 90 days.
Abuse reports, IP hash values: deleted after 90 days.
Abuse reports, contact email: deleted after 180 days.
Abuse reports, content and notes: retained to handle and cross-check cases; deleted when you request it under section 8.
Consent history: retained to demonstrate consent for the period required by law; after the account is anonymized, only an internal ID not linked to identity remains.
Email confirmation codes: valid for 10 minutes, stored as hashes; workspace invitations are valid for 48 hours.
Redirect infrastructure operational logs: 7 days.
Monitoring system traces and logs: 15 days; metrics: 90 days.
Database backups (encrypted): 14 days. Data you request to delete will disappear from backups within up to 14 days.

Emails and data at the email provider are retained under that provider's policy.

7. Cookies and similar technologies

We use only cookies necessary for functionality and apply strict security standards:

Essential cookies: Better Auth session cookie __Host-1go.*; __Host-1go.vch (voucher, 30 minutes); __Host-1go_ag (age gate, 30 days); __Host-1go_acc (member access); password-protected link unlock cookie u_<8 hex> (1800 seconds). __Host- cookies use Secure, HttpOnly, SameSite=Lax, Path=/, and no Domain; u_* cookies use Secure, HttpOnly, SameSite=Lax, and are host-only. There are no analytics/advertising cookies.

Cloudflare's Turnstile widget on the login, registration, and report forms to distinguish people from bots; Turnstile is processed by Cloudflare under Cloudflare's policy.
No user JavaScript: bio pages are built securely with a strict Content Security Policy (CSP) that does not allow third-party JavaScript or arbitrary code from the page owner to be inserted, ensuring there is no cross-page malicious code attack risk.

We do not use advertising cookies, do not use analytics cookies, and do not measure user experience (RUM) with third-party tools.

8. Your rights and how to exercise them

To the extent permitted by law, you have the right to access and receive a copy of your data, to rectify, delete, withdraw consent, restrict, or object to processing.

How to exercise them. Send an email to [email protected] stating your request clearly. To protect your account, we verify identity using a code sent to the exact email address of the account; you reply with the code within 24 hours. A deletion request also requires a written confirmation sentence in the reply email. We cannot verify if the email comes from an address other than the account address.

Time limits for our action:

respond within 2 business days of receipt;
provide a copy or rectify data within 72 hours after verification is complete;
delete (anonymize) the account within 7 days after verification is complete; in any case, not exceeding the time limit prescribed by law;
data remaining in backups expires within up to 14 days; visit records expire within up to 90 days.

Visitors to shortened links. Because we do not store IP addresses and the anonymous ID changes every day, we generally cannot identify which records are yours. When you submit a request, we will explain the specific situation and inform you that the data expires automatically after 90 days.

People who submit abuse reports. You can request deletion of your contact email and report content in the manner described above.

If you are not satisfied with how we handle your request, you can submit a complaint to [email protected] and have the right to complain to the competent state authority for personal data protection.

9. Security measures

Encryption in transit (HTTPS) between your browser and our systems.
Database backups are encrypted before being uploaded to storage; we hold the encryption keys.
Link passwords, API keys, vouchers, and email confirmation codes are stored only as hashes.
Role-based database permissions; the API application can read only the necessary columns of account data.
System administrators must use two-factor authentication.
Rate limiting and anti-bot protection on the login, registration, and report forms.
Visit data is anonymized daily and has no IP address column.

No system is completely secure. If a personal data breach occurs, we will notify the competent authority and you as required by law. To report a security vulnerability, email [email protected].

10. Children

The service is not intended for children, and we do not intentionally collect children's data. If you are a parent or guardian and believe that a child has provided data to us, please email [email protected] so that we can delete it.

11. Changes to this policy

We update this policy when the service, providers, or legal regulations change. Changes with legal significance increase the version number, and you will be asked to read and agree again. Changes only to spelling or presentation do not require re-consent.

Contact

Personal data (access, rectification, deletion, withdrawal of consent, complaints): [email protected]
Abuse reports and appeals: [email protected] or the /report page
Security vulnerability reports: [email protected]

Version: 2026-10