Policy
Privacy Policy (Detailed)
This page provides the detailed privacy framework for privtools.io: what data is processed, why it is processed, how long it may be retained, and how to submit privacy requests.
Last updated: February 08, 2026
This detailed policy expands the summary version and is written for users who want a deeper explanation of data processing, operational logging, cookies, and privacy request handling.
Processing Scope
privtools.io processes data only to deliver requested functionality, secure the service, and maintain stability. The core input is the URL you submit to the Service. The Service may also process technical request metadata to prevent abuse and investigate errors.
- Primary purpose: process URLs and return output options/results.
- Operational purpose: reliability, debugging, and performance monitoring.
- Security purpose: abuse detection, rate limiting, and incident response.
Data Categories
We aim to minimize data collection. The table below describes typical categories processed when you use the Service.
| Category | Examples | Purpose | Notes |
|---|---|---|---|
| User-submitted input | URL submitted to the Service | Generate results and downloads | Not intended as a personal โhistoryโ feature |
| Request metadata | IP, user-agent, timestamps, request size | Rate limiting, abuse prevention, debugging | Short-lived operational/security logs may exist |
| Diagnostics | Error traces, status codes, latency metrics | Uptime monitoring and troubleshooting | Aggregated where possible |
| Support messages (optional) | Email you send us | Respond to user requests | Stored as needed to handle your case |
We do not sell personal data. We avoid collecting unnecessary personal identifiers.
Diagnostics & Logs
Temporary diagnostics may include request metadata and error traces. These records support uptime monitoring, abuse mitigation, incident response, and debugging. Logging levels may increase temporarily during service incidents or attacks.
- Uptime & reliability: detect outages and performance regressions.
- Abuse mitigation: throttle or block suspicious traffic patterns.
- Debugging: identify errors and fix service issues.
Retention
We retain information only as long as necessary for service operation, security, troubleshooting, dispute resolution, and legal compliance. Retention periods may vary based on incident response needs and operational requirements.
We aim to keep operational/security logs short-lived and to aggregate metrics where possible to reduce identifiability.
Security Safeguards
We apply reasonable safeguards to protect the Service, including monitoring and abuse controls. No system is perfectly secure, but we work to reduce risk through defensive measures and operational practices.
User Requests
Privacy questions and lawful requests can be sent to support@privtools.io or via /contact/.
Depending on your location, you may have additional rights (access, deletion, objection, restriction). We will respond as required by applicable law.
Policy Changes
We may update this policy when legal, security, or product requirements change. The โLast updatedโ date reflects the most recent revision.
For a shorter overview, visit the summary privacy page.