# Terms of use
Terms of use
Last updated: October 12, 2026
These Terms govern your use of dlpbench.com and related service hosts (no-ssl.dlpbench.com, s3.dlpbench.com, ftp.dlpbench.com, and others). By visiting the site or using the test channels, you accept these Terms. If you do not agree, do not use the service.
Author and operator: Dmitry Baranov (Reddit), email: info@dlpbench.com (the “operator,” “we,” or “us”).
What is intentional on the bench, and how to report security issues, is described in the Security policy.
1. What this service is
The service is free. It is a test bench for data loss prevention (DLP) systems and related traffic controls—mail gateways, proxies, CASB, and similar tools.
On the site you can find:
- synthetic test data, document samples, and a generator;
- HTTPS POST and file upload with a short-lived result view in your browser;
- unencrypted HTTP POST on
no-ssl.dlpbench.com; - public FTP (
ftp.dlpbench.com) and object PUT ons3.dlpbench.com; - a test mailbox with message viewing by sender address;
- clipboard checks that are not stored on the server;
- an MCP endpoint for exercising AI-agent traffic;
- reference materials.
The service is not for bypassing someone else’s security policies and is not a substitute for commercial DLP. We do not promise that any particular system will detect or block a given payload. A “received” response on a test endpoint only means the request reached our bench—not that your DLP fired.
2. Acceptable use
You may use the service only to:
- lawfully test DLP and related controls on systems you own or are authorized to test;
- train, run pilots, regress, or prepare materials for internal review—using synthetic data only.
You may not:
- send real personal data, banking secrets, trade secrets, classified information, or other protected information through the service;
- use the channels as a file drop, software warehouse, CDN, or means to distribute malware or illegal content;
- overload the infrastructure beyond ordinary testing (including denial-of-service, filling disk, or probing other users’ results or mail);
- attempt to open another user’s result buffer, mail, or files outside intentionally public listings;
- present the site’s synthetic data as information about real people, or use it for fraud, social engineering, or filing documents in someone else’s name.
If you abuse the service, we may rate-limit or size-limit requests, apply IP limits, rotate public passwords, block an address, or disable a channel.
3. Synthetic data only
Samples, generator output, examples in site copy, and MCP responses are fictional. Check digits (SSN, IBAN, Luhn, and similar) exist so detectors can fire. If a number happens to match a living person’s credentials, that is a format coincidence—not “real” data about that person.
Do not use these values in applications, contracts, production databases, or any scenario outside the testing and training described in section 2.
4. Channels and test results
Files and mail on the bench are short-lived by design; this is a test surface, not a secure vault. Retention times below are guidelines and may change.
| Channel | Who can see the result | Retention |
|---|---|---|
| HTTPS POST and upload on the main site | only your browser (session cookie) | up to 1 hour |
HTTP POST on no-ssl.dlpbench.com | metadata in a shared list, no download | up to 1 hour |
| FTP and object PUT | listings and files visible to all visitors | about 15 minutes |
| Mail to the test inbox | on the site after you enter your sender address | up to 1 hour |
| Clipboard; MCP | not stored on the server | — |
FTP credentials are published on purpose. Upload limits for the site and object channel are 20 MB, unless a channel page says otherwise. We do not promise durability: cleanup, failure, or manual deletion may remove data sooner.
Do not put anything in a shared listing that you cannot afford to lose or that should not be visible to others until cleanup. You are responsible for what you send.
5. Information about visitors
There is no registration or personal account. We do not ask for real personal data to run a test.
The hosting provider (Fornex) may, in the ordinary course, log IP addresses, request times, URLs, User-Agent strings, and other standard headers—to operate the site, protect infrastructure, and investigate abuse. We do not build advertising profiles from that information.
A technical cookie dlpbench_vid ties the HTTPS result buffer to your browser (up to 7 days, or until you clear it); the buffer itself is cleared sooner—see section 4. The cookie is not available to page scripts.
The site uses Umami Cloud (cloud.umami.is) for privacy-focused page analytics (no session replay, no advertising pixels). Umami processes technical data about page views under its own terms. We do not add other third-party analytics products.
Some libraries (for example, styles or SheetJS) may load from a CDN; your browser then contacts CDN servers over HTTPS.
For HTTPS and object PUT we count successes “for the day” and “all time”; /api/stats.json and the site footer show whole numbers only—no request bodies and no IPs. Short-lived service records keyed by IP may be used to limit abuse and are not exposed publicly.
If you write to info@dlpbench.com or use the contact form, we use the details you provide only to reply.
For questions about information we process, email info@dlpbench.com.
6. No warranty; limitation of liability
The service is provided “as is.” We do not warrant uninterrupted availability, compatibility with your DLP, complete detection, retention of test results, or fitness for a particular purpose.
To the fullest extent permitted by applicable law, the operator is not liable for losses arising from use of—or inability to use—the service, including false positives, policy misses, or another visitor downloading a file from a shared listing before cleanup. In plain terms: you use a free public test bench at your own risk; we are not responsible for how your tools behave or for anything you (or others) put on shared channels.
7. Intellectual property and attribution
Site text, design, and code belong to the author or are used under valid licenses. In testing reports you may quote the service and cite it as a source. Do not copy the service as a competing product without permission, except as open licenses for individual components (for example, CDN libraries) already allow.
If you reuse substantial materials from the site in publications, training decks, or similar work, give clear attribution to dlpbench.com.
8. Changes and discontinuation
We may change features, limits, and these Terms, and may stop the service in whole or in part, without prior notice. The current version is always on this page. Continued use after a new version is posted means you accept it, unless applicable law requires otherwise.
9. Governing law
These Terms are governed by the laws of the State of California, USA, without regard to conflict-of-law rules. Disputes should first be addressed informally. If that fails, they will be resolved in the courts of California, to the extent permitted by law.
10. Contact
Email: info@dlpbench.com
Author: Dmitry Baranov