TorSentinel TorSentinel

No-Logs Policy

Effective Date: May 31, 2026

Our Commitment: TorSentinel does not log, store, or monitor your activity, traffic, or connections. This is not just a policy — it is the technical architecture of our service.

1. Overview

TorSentinel is built on a strict no-logs architecture. We do not record, collect, store, or share any data that could be used to identify what you did online, when you were connected, or where your traffic was directed. This policy applies to all plans and all services including the Monitor plan, the Armor SOCKS5 proxy, and the Armor WireGuard VPN.

2. What We Never Log

The following data is never recorded or stored on any TorSentinel system:

VPN & Proxy Activity
  • Your originating IP address
  • The destination IPs or hostnames you connect to
  • The contents of your traffic
  • DNS queries you make through our servers
  • Ports or protocols used
  • Bandwidth usage per session
  • Timestamps of individual connections
  • Session duration
Torrent Monitor Activity
  • Which torrents you are seeding or downloading
  • Your torrent client activity
  • Swarm data or peer lists beyond your private test magnets
  • Files transferred through our infrastructure

3. What We Do Store

To operate and maintain your account, we store the minimum data necessary. This is account data only, not activity data:

  • Email address — used for account login and service notifications
  • Hashed password — stored with industry-standard bcrypt hashing; we cannot read your password
  • Subscription and billing records — plan type, payment dates, renewal status; payment details are stored and processed by gateway, not by us
  • WireGuard public keys — the public portion of your key pair only; your private key never leaves your device
  • SOCKS5 credentials — your proxy username and hashed password for authentication
  • Monitor configuration — your safelist IPs, notification preferences, and webhook URLs
  • Monitor alert events — when an unexpected IP appeared in your private test torrent's swarm; this is the core function of the Monitor service. These events contain the detected IP and timestamp, not your real IP or traffic.
None of the above data links your account identity to any specific VPN session, proxy connection, or online activity.

4. VPN & Proxy Infrastructure Design

Our servers are configured so that logging is technically disabled, not just switched off in software:

  • WireGuard: Our WireGuard server configurations do not retain peer handshake timestamps, allowed IPs, or traffic counters beyond what is held transiently in kernel memory during an active session. When a session ends, this data is discarded.
  • Dante SOCKS5: Our Dante proxy instances run with logging disabled at the configuration level. No connection logs, no access logs, no error logs containing client IP or destination data are written to disk.
  • RADIUS: Our RADIUS authentication system logs only successful or failed authentication events (username + result). It does not log when, where, or what you connected to.
  • No traffic inspection: We do not perform deep packet inspection, traffic shaping analysis, or any form of traffic content analysis on user connections.
What this means: Even if compelled by a legal request, we have no activity data to provide. We can confirm an account exists, but we cannot state what that account did, when it connected, or where its traffic went.

5. Third-Party Services

We use a small number of third-party services strictly for account and billing functions:

  • Stripe — payment processing for card payments. Stripe stores billing information per their own privacy policy. We receive only a transaction token, not your full card details.
  • Crypto Gateway — cryptocurrency payment gateway. Crypto transactions are processed on-chain; Crypto gateway does not associate your wallet address with your TorSentinel account.
  • PHPMailer / SMTP — used to send account-related emails (signup confirmation, alerts, renewal notices). We do not share your email address with marketing platforms.

We do not use any analytics, advertising, or tracking third-party services on our VPN infrastructure. We have no Google Analytics, no Facebook pixel, and no telemetry SDKs embedded in our VPN server code.

6. Legal Requests & Jurisdiction

TorSentinel os registered in the RAK Free Zone, United Arab Emirates. UAE law governs our legal obligations regarding data disclosure.

  • We will comply with valid legal requests issued under UAE jurisdiction
  • We will resist requests that we consider overbroad, unlawful, or outside our jurisdiction
  • In all cases, we can only produce data that we actually have — which is limited to account data as described in Section 3
  • We have no VPN session logs, connection timestamps, or traffic data to disclose to any party
Note: If you are concerned about account-level information (your email or billing records), consider using a non-personally-identifying email address and paying with cryptocurrency.

7. Aggregate & Operational Statistics

We collect high-level, non-attributable operational metrics to monitor server health — such as total active WireGuard peers, total bytes forwarded per server, and CPU/memory utilization. These metrics are aggregated at the server level and cannot be traced to any individual user, session, or account.

8. Transparency

We are committed to transparency about how our service operates. If we are ever compelled by a court order or government authority to alter our logging practices, we will do our best to notify users in advance to the extent legally permitted.

We have never:

  • Placed a backdoor in our VPN or proxy software
  • Provided session or connection data to any government or third party
  • Enabled or been asked to enable traffic monitoring on our network

9. Changes to This Policy

If we make material changes to this No-Logs Policy, we will update the Effective Date and post a notice on our website. We will never retroactively apply a weakened policy to data that was handled under a stricter policy. Continued use of the Service after a policy update constitutes your acceptance of the revised policy.

10. Questions

If you have questions about our no-logs practices or data handling, we welcome the conversation.

Email: [email protected]