This policy explains the information that Doggygo VPN (“we”, “us”, or “our”) collects and processes when providing our website, accounts, and network proxy services.
Key Policy Points
- We record connection and destination metadata, including user IDs, source IP addresses, connection times, nodes used, protocols, destination domains, destination IP addresses, and ports. We are not a “no-logs” service.
- Logs can be linked to accounts and used for operations, troubleshooting, abuse detection, subscription management, and handling complaints. A user ID does not make a log anonymous.
- Destination domains are different from communication content: logs may reveal websites or application services you connected to, but these fields alone do not reveal HTTPS-encrypted page contents, search queries, or chat contents.
- Connection counts are different from traffic byte counts: not every protocol or log entry includes upload or download bytes. Connection counts alone cannot establish usage or charges.
- The central log database currently has a 60-day expiry configuration for access and service events and a 7-day configuration for parsing failure records. See Data Retention and Deletion for the scope.
Table of Contents
- Key Policy Points
- Basic Data Collection Principles
- Types of Information Collected
- How We Use Information
- What Logs Can and Cannot Show
- Data Retention and Deletion
- Communication Records
- Data Access and Processing
- Security Measures
- Cookies and Website Analytics
- Third-Party Websites
- Access Correction and Deletion Requests
- Policy Updates
- Contact Us
Basic Data Collection Principles
We process data as needed to provide services, administer subscriptions, troubleshoot problems, and protect network security, and restrict unrelated uses. We do not describe logs that can be linked to user IDs, source IP addresses, or connection times as anonymous, nor do we promise that an account’s connection activity cannot be partially reconstructed.
Fields may vary by node, proxy protocol, and software version. A missing or uncollected field does not establish that an activity did not occur. Logs also do not represent a device’s complete browsing history outside our service.
Types of Information Collected
1. Account Information
- Your registered email address, used for account verification, service notifications, and communication.
- Your user ID, subscription type, validity period, and service status, used to associate service permissions, usage records, and subscription management with your account.
2. Traffic and Subscription Information
- Traffic usage data and service availability status used to administer subscriptions.
- Upload and download byte counts, traffic reporting batches, reporting times, and processing status, where supported by the protocol, node, and reporting mechanism.
- Traffic reports may cover batches of multiple users. Some logs record only a batch and its user count, without byte totals for individual users.
Usage reconciliation requires byte records attributable to the account together with the applicable subscription and node billing rules. Counts of destination connections, domain connections, or client connections are not byte counts and cannot directly establish MB or GB usage or a billing multiplier.
3. Connection and Destination Logs
Node services may record the following information:
- Account and source: user ID, source IPv4/IPv6 address, and source port.
- Times and events: event time, log ingestion time, and event types such as client connection, disconnection, destination connection, and UDP transmission.
- Nodes used: node number, server identifier, server address or hostname, and associated service and process identifiers.
- Connection details: proxy protocol, transport protocol, connection ID, stream ID, session ID, and similar identifiers, as produced by protocols such as HY2, AnyTLS, Mieru, and Naive.
- Destinations: the domain requested by the client, destination domain, destination IPv4/IPv6 address, destination port, and available protocol information.
This information can be used to summarize the nodes, source addresses, and destination domains associated with an account during a particular period. Domain information may come from client requests or proxy processing and may reflect information related to name resolution. We do not promise that destination information or all DNS-related information is excluded from logging.
4. Service Operation and Diagnostic Logs
- Service status, errors, account permission updates, permission revocations, and connection closure events.
- Traffic reporting attempts, batch identifiers, batch user counts, and available upload and download byte fields.
- Original log text, parsing failure reasons, log versions, event identifiers, and server and process identifiers retained to diagnose collection problems.
Original text and parsing failure records may also contain user IDs, source addresses, destinations, or connection identifiers. They should not be treated as system logs that contain no user information.
How We Use Information
We use this information to:
- Provide account verification, node connectivity, and subscription services, and enforce traffic, validity, and service permission limits.
- Investigate connection failures, node problems, access difficulties, and user questions about traffic or billing.
- Detect port scanning, attack traffic, unusually frequent connections, and abnormal account use; conduct security audits; and apply service restrictions when necessary.
- Analyze node load, protocol stability, and service quality, and handle complaints, disputes, and security incidents.
Assessing abnormal activity requires considering timing, destinations, protocols, and other available evidence. A connection-count threshold or IP address count alone does not prove an attack, account sharing, or a particular number of devices.
What Logs Can and Cannot Show
Destination domains, IP addresses, and ports may reveal websites or application services connected to. Background applications, synchronization, connectivity checks, and automatic retries also generate connections. Each destination connection should not be interpreted as a deliberate page visit, one HTTP request, or one successful application call.
The structured fields in these connection logs do not contain full URL paths or query parameters, HTTP request or response bodies, search terms, chat text, or transferred file contents. This metadata alone cannot reveal HTTPS-encrypted content. We do not routinely collect such communication bodies as part of these connection logs. Text, screenshots, and diagnostic materials that you choose to submit to support are instead part of the communication information you provide.
Source IP addresses may belong to a device, shared network, changing network exit, or relay server. IPv4/IPv6 dual-stack connectivity and address changes can cause one client to appear under multiple IP addresses; shared exits can place multiple clients behind one IP address. Domains, IP attribution, and connection counts alone cannot establish a user’s identity, precise location, or number of devices.
Data Retention and Deletion
The central log database currently uses the following automatic expiry settings:
- Access and service events: become eligible for expiry cleanup 60 days after the event time.
- Parsing failure records: become eligible for expiry cleanup 7 days after ingestion.
Background tasks remove expired records asynchronously; deletion is not guaranteed at the exact moment the period ends. These periods apply only to the central log database. They do not mean that node-local original logs, separately exported diagnostic or audit records, account and billing records, support materials, or backups, if any, are all deleted within the same periods.
Separately retained records should be limited in scope and duration to what is needed for account services, troubleshooting, dispute resolution, or security investigations, and deleted or anonymized once those purposes are complete and retention is no longer necessary. Contact us to ask about retention related to your account or to request deletion.
Communication Records
We retain the email address you provide at registration and the inquiries, text, voice messages, screenshots, and diagnostic materials you submit through email, the website, or support channels, as applicable. These are used to verify accounts, provide service notifications, answer questions, and resolve disputes.
Please do not include unrelated passwords, verification codes, or private communications in diagnostic materials. If you receive marketing emails, you can use the unsubscribe method provided in them.
Data Access and Processing
Logs and account information should be accessed only by authorized personnel who need them for operations, security, billing investigations, or support, and only within their responsibilities. Troubleshooting and audits may involve querying, summarizing, or exporting records related to an incident.
Hosting, email, support, log analysis, or technical support tools and their providers may process relevant information as needed to provide those services. External disclosures should be checked for their purpose, basis, and necessary scope. Account-linked access details are not to be disclosed in public channels. Website analytics services are described below.
Security Measures
We use access controls and operational measures to protect data and restrict the scope of log queries, exports, and use. Because connection logs can be associated with accounts, they must be treated as information requiring protection.
No system can guarantee absolute security. We do not promise that all storage is inaccessible or that account activity cannot be reconstructed if a server or access permissions are compromised.
Cookies and Website Analytics
The website may use cookies or similar identifiers to save language preferences, manage login sessions, and measure website usage. These identifiers may distinguish browsers or sessions and should not automatically be treated as anonymous data that cannot be associated with users.
The website is configured to use Google Analytics for website statistics. This service may process visits to pages on this website, device or browser information, and identifiers such as cookies. This is separate from destination logging by proxy nodes. See Google Analytics’ data safeguards documentation for information about its processing.
You can restrict or delete cookies through browser settings or use browser tracking protection. Doing so may affect login, saved preferences, or analytics functionality. Disabling website cookies does not disable connection logging by proxy nodes.
Third-Party Websites
Third-party websites and applications linked from this website or accessed through the proxy service have their own data processing rules. Please review their privacy policies. Our connection logs do not replace those third parties’ disclosures about their own processing.
Access Correction and Deletion Requests
You can contact us to ask about data associated with your account, correct inaccurate information, or request deletion. We may need to verify account ownership to prevent others from obtaining your records. When handling a request, we will explain the scope of data that can be provided or processed and any information still needed for services, disputes, security investigations, or applicable requirements.
Policy Updates
We will revise this policy to reflect changes in actual data processing and services and update the date below. Important changes to data processing will be explained through the website or service notices. Where separate notice or consent is required, we will follow the applicable requirements.
Contact Us
For questions about privacy, data records, or traffic investigations, contact:
📮 Email: [email protected]
Last Updated: November 15, 2026
