← Back to home

No-Logs Policy

CredoVPN service

Revision dated 11 April 2026.

This No-Logs Policy describes how the CredoVPN service approaches collection, processing, storage, and non-retention of data related to user network activity when using the service provided by Dolphin LLC (ООО «Дельфин»), INN 6633019190, OGRN 1126633001153, Russian Federation, Yekaterinburg, hereinafter the “Contractor.”

This Policy applies together with the Public Offer, Privacy Policy, Refund Policy, User Agreement, Service Usage Rules, Subscription Terms, and other CredoVPN documents.

By using CredoVPN, the user confirms they have read this Policy, understand it, and accept the principles it describes.

1. General provisions

1.1. A core principle of CredoVPN is that the Contractor does not keep logs of user network activity to an extent that would allow reconstruction of what the user did on the Internet.

1.2. For this document, a no-logs policy means refraining from permanently storing and maintaining logs that contain information about:

  • which websites the user visited;
  • what content the user viewed;
  • what data the user transmitted over the network;
  • what DNS queries the user made;
  • what specific actions the user performed on the Internet while using the service.

1.3. This Policy governs user network activity in connection with use of the VPN service and must be read together with the Privacy Policy, which governs processing of contact, technical, payment, and service data.

1.4. Not logging user network activity does not mean there is no technical data processing in the service infrastructure. Limited technical information may be used for operation, security, and support, but such information must not be used as a log of the user’s Internet activity.

2. Data CredoVPN does not log or store as activity logs

2.1. CredoVPN does not maintain or store permanent logs containing:

  • history of visited websites;
  • URLs of pages opened by the user;
  • contents of Internet traffic;
  • contents of messages the user sends through third-party services;
  • contents of files the user uploads or transfers;
  • lists of apps, sites, and resources the user accessed over the VPN connection;
  • contents of the user’s DNS queries;
  • a full history of the user’s network activity;
  • substantive logs of the user’s actions on the Internet.

2.2. CredoVPN does not use the service to monitor user behavior on the Internet and does not build databases intended for later analysis of user traffic content.

2.3. CredoVPN does not store the user’s Internet activity in a form that, under ordinary procedures, would allow determining what the user did online through the service.

3. Data that may be processed in a limited way for technical purposes

3.1. To keep the service stable, protect infrastructure, diagnose technical failures, run anti-abuse mechanisms, and support connections, limited technical information that is not intended to record the substance of Internet activity may be processed.

3.2. Such information may include:

  • the technical fact of an active session;
  • technical connection state;
  • timestamps needed for server operation, routing, protection, or diagnostics;
  • anonymized or aggregated technical load indicators;
  • information that a connection fault occurred;
  • technical details about client version, device type, or operating system where needed for support;
  • error information when using the site, bot, interface, or access-provisioning flow;
  • data needed to limit abuse, fraud, or attacks on infrastructure.

3.3. Such information is used only to the extent necessary to:

  • keep the service available;
  • detect technical faults;
  • prevent overload and abuse;
  • protect servers and service interfaces;
  • provide technical support;
  • meet legal obligations to an appropriate extent.

3.4. Such technical information must not be used by the Contractor as a full log of the user’s actions online.

4. Temporary technical processing and memory

4.1. During operation, certain technical data may be processed temporarily in RAM, caches, system buffers, processing queues, monitoring components, and other technical parts of the infrastructure.

4.2. Temporary technical processing required for network infrastructure to function is not treated as logging user activity if the data:

  • is not stored as permanent Internet-activity logs;
  • is not used to analyze the substance of the user’s actions;
  • does not build visit history or traffic contents;
  • is not intended for later profiling of the user’s online behavior.

4.3. The Contractor seeks to limit such temporary technical data to the minimum scope and lifetime needed.

5. No-Logs Policy vs. other processing

5.1. This Policy does not mean the Contractor processes no user data at all.

5.2. To provide the service, the following may be processed and stored:

  • account data;
  • Telegram ID, email, and other contact details;
  • payment information;
  • support requests;
  • subscription and plan information;
  • limited technical information about the site, bot, and infrastructure;
  • information related to security and antifraud.

5.3. That processing is governed primarily by the Privacy Policy and other service documents.

5.4. Not logging user network activity does not mean the Contractor refuses to process:

  • payment information to the extent required for payments;
  • technical data for the website and Telegram bot;
  • support requests;
  • data needed to perform the contract and protect infrastructure.

5.5. The user should distinguish between:

  • network activity through the VPN, which is not logged as an action history;
  • technical and service data, which may be processed in a limited way to run the service.

6. DNS, routing, and traffic

6.1. CredoVPN does not keep permanent logs of user DNS queries as a history of Internet activity.

6.2. CredoVPN does not use user traffic contents to build behavioral profiles, visit history, or marketing analytics.

6.3. Technical processes of routing, packet handling, data transfer, connection setup, and tunnel maintenance must not be read as logging user activity where there is no permanent substantive storage as a history of the user’s actions.

6.4. If parts of the network infrastructure technically create brief system traces needed for hardware or software to operate, those traces are treated as an incidental technical by-product of infrastructure, not intentional user-activity logging, provided they are not used as a log of user behavior.

7. Antifraud, security, and abuse

7.1. The Contractor may apply reasonable technical and organizational measures to:

  • protect infrastructure;
  • prevent attacks;
  • limit abuse;
  • protect payments;
  • prevent repeat bad-faith use of trial access;
  • counter automated malicious activity.

7.2. Such measures may include limited technical indicators, counters, risk signals, anomaly monitoring, and other security mechanisms.

7.3. Antifraud and protective measures do not mean the Contractor keeps full logs of user Internet activity.

7.4. The Contractor may restrict, block, or suspend access if there is:

  • abuse;
  • attempts to attack infrastructure;
  • circumvention of service limits;
  • fraud;
  • use of the service in breach of binding documents.

8. User support and diagnostics

8.1. When the user contacts support, the Contractor may request and process:

  • a problem description;
  • screenshots;
  • app version information;
  • device details;
  • network details;
  • information on steps already taken;
  • other technical details needed for diagnosis.

8.2. Such diagnostics aim to resolve a specific issue and do not mean maintaining historical logs of the user’s Internet activity.

8.3. CredoVPN support is provided only for using the service through the WireGuard application.

8.4. If the user relies on unsupported apps, the Contractor may limit assistance to general guidance and not perform in-depth diagnosis of those setups.

9. Disclosure to third parties

9.1. Because CredoVPN does not keep user network-activity logs within the meaning of this Policy, the Contractor does not hold a history of the user’s Internet actions intended for routine disclosure to third parties as a working dataset.

9.2. This does not rule out transfer of other data where provided for by:

  • law;
  • the Privacy Policy;
  • the Public Offer;
  • mandatory requirements of competent authorities;
  • the need to protect the Contractor’s rights and lawful interests.

9.3. If the Contractor must provide data under a mandatory legal procedure, it acts within the data it actually holds and is required or permitted to provide by law.

10. Limits of this Policy

10.1. This Policy must not be read as an absolute guarantee that no technical traces of network infrastructure ever arise under any circumstances.

10.2. The Policy means the Contractor:

  • does not keep permanent substantive logs of user network activity;
  • does not store the user’s Internet action history as a systematic journal;
  • does not design the service around collecting and storing that kind of activity.

10.3. Temporary, technically unavoidable, system, and purpose-limited data needed for equipment operation, protection, availability monitoring, and service operation must not automatically be treated as a breach of this Policy if it is not used as a log of the user’s Internet activity.

10.4. This Policy does not replace the Privacy Policy and does not cover all processing related to the website, Telegram bot, payments, and support.

11. Lifetime of technical data

11.1. CredoVPN seeks to limit how long technical data that is not activity logging is kept to the minimum period needed for:

  • infrastructure operation;
  • security;
  • incident diagnostics;
  • service stabilization;
  • resolving technical and payment disputes.

11.2. Technical information no longer needed for those purposes is deleted, replaced, aggregated, anonymized, or allowed to become obsolete according to the Contractor’s internal processes.

12. Policy changes

12.1. The Contractor may amend this Policy at any time.

12.2. A new version takes effect upon publication unless the text states a different effective date.

12.3. The user shall independently monitor the current version of the document on official service channels.

12.4. Continued use of the service after a new version is published means acceptance of its terms.

13. Relationship to other documents

13.1. This Policy applies together with:

  • the Public Offer;
  • the Privacy Policy;
  • the Refund Policy;
  • the User Agreement;
  • the Service Usage Rules;
  • the Subscription Terms;
  • other official CredoVPN documents.

13.2. If the same matter is covered by several service documents, the provisions should be read together.

13.3. For contact, payment, service, and other personal data, the Privacy Policy prevails; this Policy governs primarily the absence of permanent logging of user network activity.

14. Contractor contacts

Contractor: Dolphin LLC (ООО «Дельфин»).

INN: 6633019190.

OGRN: 1126633001153.

Country: Russian Federation.

City: Yekaterinburg.

Website: credovpn.ru.

Support email: support@credovpn.ru.

Support Telegram: @credovpnsupportbot.