Reports and requests

The company warrenBrowse is being incorporated. Until it is registered, the responsible entity is referred to in this document as "the Warren team".

This page is addressed to rights holders, hosting providers, security teams and authorities. It describes what the Warren team can do when you report abuse to it, what it cannot do, and why.

The Warren team answers every admissible report within 24 business hours.

Contact: abuse@warrenbrowse.com

1. What Warren is, technically and legally

Warren is a virtual private network. The traffic of the Warren team's users crosses its exit servers encrypted, and leaves for the Internet under the server's IP address.

Warren provides a mere conduit service within the meaning of Article 4 of Regulation (EU) 2022/2065 on digital services, a category that recitals 28 and 29 of that regulation name explicitly for virtual private networks. In the United States this corresponds to transitory digital network communications under 17 U.S.C. § 512(a).

Concretely:

• the Warren team does not initiate the transmissions;
• it does not select their recipients;
• it neither selects nor modifies the information transmitted;
• it hosts no content on behalf of its users.

2. What the Warren team cannot do

The Warren team cannot take down any content. A tunnel stores nothing. No copy of what crosses its servers exists on them, so no takedown is materially possible. A notice-and-takedown procedure has no object here.

The Warren team cannot identify anyone. It logs no traffic, no DNS queries, no connections and no source IP addresses. Its exit servers run in memory, with no disk. A request about an IP address and a timestamp therefore cannot be matched to an account: the data that would allow that match is written nowhere.

This is not a commercial policy the Warren team could relax case by case. It is a property of the architecture, and it has been tested in court at other operators who apply it.

3. What the Warren team can do, and does

When a report targets a port opened through port forwarding, the Warren team has a real action available, and it takes it.

• The Warren team closes the reported port. Without identifying its holder, without inspecting traffic.
• It records a strike against the account that held that port at the time of the report.
• Three strikes within a rolling ninety-day window revoke the account, which loses network access. A strike older than that window stops counting.
• Every strike is decided by a human, never automatically.

This counter is a bounded and deliberate exception to the Warren team's no-logging commitment. It holds the account identifier, a number of recent strikes and the last report category. It holds no destination, no port, no timestamp and no per-event history, it lives in memory and disappears on every service restart. It therefore answers no question about what a user did, and it lets the Warren team answer a hosting provider. It is declared in the team's Privacy Policy.

4. How to write to the Warren team

Send to abuse@warrenbrowse.com a message containing:

• the IP address concerned and the port;
• the date and time with the time zone;
• the nature of the abuse observed;
• anything allowing the observation to be verified (log excerpt, headers).

The Warren team acknowledges receipt with a case reference and answers within 24 business hours. A report about a forwarded port, precise enough to be verified, leads to the port being closed.

5. Contesting a strike

If your account has been struck or revoked and you believe this is a mistake, write to abuse@warrenbrowse.com from the application, signing with your account key. The Warren team re-examines the report behind the strike. A withdrawn strike immediately stops counting, and a revocation issued in error is lifted.

6. Requests from authorities

The Warren team answers requests addressed to it in the forms provided by Romanian law, its seat and its forum.

The Warren team's answer is the same in every case, because its architecture leaves it no latitude: it has no traffic log, no connection log and no source IP log to produce. It cannot link an exit IP address and a timestamp to an account, nor an account to a person.

The Warren team carries out no general monitoring and is not required to (Article 8 of Regulation (EU) 2022/2065). It installs no interception capability at the request of a third party.

An admissible request receives a reasoned answer. A request outside the legal forms, or seeking data the Warren team does not hold, receives an answer explaining why it cannot be satisfied.

7. Hosting providers

If you host the Warren team and receive a complaint about one of its addresses, forward it to abuse@warrenbrowse.com. It handles it directly and answers you.

The Warren team blocks outbound port 25 by construction on every exit server, and its port forwarding feature only assigns high ports (49152 to 65535), with a per account cap. No service can therefore be exposed on the usual infrastructure ports from its addresses.