Privacy Policy
1. Overview
CityLink Global provides user-initiated network connectivity service, along with account management, membership status, device binding, diagnostics, and support workflows. This policy explains what data we collect, why we collect it, how long we keep it, and how you can request data deletion or account closure.
2. Data We Collect
2.1 Account Data
We may collect account information used for registration, sign-in, account recovery, and support, such as:
- Username or account identifier;
- Email address, phone number, or other contact details when those features are enabled;
- Sign-in verification data (we do not store plaintext passwords);
- Sign-in times, account status, and role.
2.2 Membership and Purchase Data
We may collect and retain membership and entitlement information, such as:
- Membership plan, status, start and expiry times;
- Manual grants or extensions during beta or operations;
- Membership audit records for support and abuse prevention.
In versions that offer in-store purchases, payment is processed by the applicable app store, such as Google Play or the Apple App Store. The current Apple beta does not offer a purchase option and only displays membership entitlements already associated with the account. When a store purchase is actually initiated, CityLink may process the following purchase-related data:
- App-store product or plan ID;
- Store-provided purchase token or receipt;
- Order or transaction reference (where provided by the store);
- Purchase time and purchase status;
- Membership entitlement status and expiry time;
- Store and platform identifiers.
This purchase data is used only to: verify purchases; activate and maintain membership entitlements; prevent fraud and support security and compliance; and handle refunds, purchase restoration, and customer support.
2.3 Device Data
For device binding and device limits, we may collect:
- App-generated device identifier;
- Device display name you provide;
- Platform type and basic device information within available scope;
- Binding status, creation time, last online time, and revocation status.
2.4 Connection Configuration Data
To provide network connectivity service, we process configuration-related data, such as:
- Selected node ID and node region or type;
- Device connection identifier and assigned connection address;
- Server address and DNS settings needed to establish encrypted connection service;
- Device identifier associated with the generated connection configuration.
Connection-related device configuration is generated on your device. We do not intentionally store complete copies of that configuration. Diagnostic and app logs remove personal sensitive content and other sign-in credentials.
2.5 Connection Status Data
For service stability and support, we may collect limited connection status information, such as:
- Connection success or failure status;
- Selected node ID;
- Error codes and user-visible error categories;
- Connection and diagnostic timestamps;
- App version and platform information when needed for troubleshooting.
2.6 Diagnostic Logs
You may voluntarily export or submit diagnostic logs, which may include:
- App version, platform, selected node, and connection stage;
- API request status and structured error codes;
- Native connection status, probe results, and recent client events;
- Cached configuration summaries with personal sensitive content removed.
If you choose to send diagnostic exports, do not include passwords, verification codes, payment details, chat content, or web page content in your message or attachments. See the data categories above for more detail.
2.7 Administrative Action Logs
For operational accountability, admin actions on beta accounts may produce audit logs, such as:
- Administrator account identifier;
- Target user identifier;
- Action type (e.g., membership grant, device revocation, user disable or enable);
- Reason, timestamp, and before/after metadata where available.
2.8 Website Analytics Data
We may use Google Analytics or similar tools on the website to understand aggregated visits, page usage, device categories, and traffic sources. Website analytics are not used to collect passwords, verification codes, payment information, in-app connection content, or web page content accessed through the network connection service.
2.9 App Store Privacy Disclosures
These disclosures apply to Apple App Store privacy labels and Google Play Data Safety declarations. The declaration for each platform reflects the features enabled in that version.
Data collected but not disclosed as shared with third parties:
- Email address;
- User ID;
- Purchase history / transaction records;
- App interactions;
- Diagnostics;
- Device ID or other IDs.
Not collected:
- Approximate or precise location;
- Browsing history;
- Contacts;
- Messages;
- Photos and videos;
- Audio;
- Files and documents;
- Calendar;
- Health and fitness data.
Additional notes:
- The device ID is an app-generated device identifier, not an advertising ID;
- Diagnostics are optional and only when you choose to submit them;
- Purchase history is generated only when you actually make a store purchase;
- Data is transmitted over encrypted connections.
3. What We Do Not Collect (Important)
We do not intentionally collect or store the following content related to your browsing behavior for the purpose of providing this service:
- Browsing content (web pages, in-app content, or similar material accessed through the connection service);
- Visited site lists (complete browsing history of sites or domains you visited);
- DNS query history (DNS resolution records used for browsing behavior);
- Chat content, web page content, or in-app content (messages, files, or pages transmitted through the connection service).
Network quality may vary by node, region, carrier, and device settings, but we do not inspect user traffic content to provide this service.
4. How We Use Data
We use collected data to:
- Provide network connections and configuration generation;
- Support account sign-in, membership status, and device binding;
- Provide customer support and beta troubleshooting;
- Prevent fraud, abuse, and account security risks;
- Maintain operational audit trails;
- Understand website visits and page usage;
- Improve service stability and reliability.
For applicable app-store privacy disclosures, each data type maps to these purposes:
- Email, User ID: app functionality, account management, fraud prevention / security / compliance;
- Purchase history: app functionality, account management, fraud prevention / security / compliance;
- App interactions: app functionality, fraud prevention / security / compliance;
- Diagnostics: app functionality, analytics, fraud prevention / security / compliance;
- Device ID: app functionality, account management, fraud prevention / security / compliance.
5. Data Sharing and Payment Boundaries
We do not sell user data or user traffic data, and we do not use VPN data for advertising or cross-app tracking.
Where applicable, actual payment is processed by the relevant app store. CityLink does not collect or store full card numbers, bank account numbers, CVV, or app-store payment credentials. Google Play or the Apple App Store applies its own privacy policy to the payment data it processes. The current Apple beta does not offer a purchase option.
The app does not include advertising SDKs and is not used for ad tracking. We do not collect or log web page content, visited-site lists, chat or communication content, or DNS query history accessed through the VPN. VPN traffic and browsing-content data are not sold, used for advertising or tracking, or disclosed to third parties (see Section 3).
Account, device, connection-status, and diagnostic data are processed only for the purposes described in Section 4. Service providers acting on our behalf for infrastructure or customer support must follow confidentiality and data-protection obligations and may not use the data for their own purposes. Legally required disclosure is limited to information we are required to provide. If our processing changes materially, we will update this policy and the corresponding in-app disclosure before the change takes effect.
6. Data Security
We apply reasonable technical and administrative safeguards, including:
- Transport encryption where applicable;
- Storing sign-in verification data instead of plaintext passwords;
- Removing sign-in session information and other sensitive credential details from logs;
- Administrator access controls for user and membership management;
- Audit logs for sensitive administrative actions.
We continue to improve secure storage of client credentials to reduce exposure risk.
7. Data Retention
Retention periods may change with business and legal requirements. Current principles:
- Account data: retained while the account is active;
- Membership and order records: retained as needed for support, audit, and dispute handling;
- Device binding records: retained while the account is active or until removed;
- Diagnostic logs: retained only as long as needed for troubleshooting;
- Administrative audit logs: retained as needed for operational accountability and abuse prevention.
8. Data Deletion and Account Closure
You may request:
- Account deletion;
- Removal of device bindings;
- Deletion of diagnostic logs where applicable;
- Review of membership data subject to operational and legal retention requirements.
Contact [email protected], or see our Account Deletion page. If the app provides self-service deletion or closure, you may also follow in-app instructions.
9. Children and Restricted Users
CityLink Global is not designed specifically for children. Confirm the minimum applicable age under your local laws and use the service only if you meet those requirements.
10. Changes to This Policy
We may update this policy as features, payment methods, infrastructure, or legal requirements change. For material changes, we will notify users in a reasonable manner before they take effect.
11. Contact Us
Controller / operator: CityLink Global Technology Limited
Support email: [email protected]
Privacy policy URL: https://speedcn.citylink.club/en/privacy/