Privacy Policy

This page explains what data the platform processes, why it is processed, and how retention is limited. The goal is practical transparency for operators using public diagnostics.

Data minimization model

• Requester IP is transformed to a salted hash before persistence in run records.
• Raw requester IP is not retained long-term in diagnostic result storage.
• Run payload retention is intentionally short to reduce exposure surface.

What is stored with tool runs

• Tool key, locale, sanitized input, output summary, and runtime metrics.
• Short-lived technical output for troubleshooting and incident collaboration.
• Status and error metadata used for reliability analytics and abuse defense.

Retention controls

1. Tool runs expire by default after a short configured window.
2. Scheduled cleanup jobs remove expired records and detached events.
3. Visitor analytics retention is bounded by explicit policy settings.

FAQ

Does this service build personal profiles?

No. The system stores operational metadata needed for stability and abuse prevention, not personal profiling datasets.

Can I request immediate run deletion?

Run data is already short-lived by design; operational deletion requests can be handled through support workflow where applicable.

Are run links permanent?

No. Share links are intentionally temporary and expire automatically.

Is user-agent data kept forever?

No. It is retained only within bounded analytics windows for abuse and performance analysis.

Where should policy disputes be reported?

Use the abuse-policy and support channels to raise policy or handling concerns.