Requests for account or payment data
Identify the authority or request category, the reporting period, the information sought and the outcome. Distinguish a request received from information actually disclosed.
Read the record, understand its scope.
Transparency means knowing which period a statement covers, what was counted and what action followed. This page explains how to assess service disclosures, data requests and incident records without relying on unexplained numbers.
The public record
No dated SilentVPS operational report or request dataset is published here. There are therefore no verified request totals, incident counts or uptime figures to display. This is a description of the evidence available, not a statement that the corresponding events never occurred.
Keep different requests distinct
A data-disclosure request, an abuse report and a service interruption answer different questions. Combining them into one total hides information a reader needs.
Abuse and takedown reports
Describe the reported conduct and the action taken separately from a demand for customer data. Several messages about one issue should not automatically become several incidents.
Operational incidents
Explain the affected service, start and end times, impact and recovery. A maintenance notice and an unexpected outage should remain distinguishable.
What makes a report comparable
- Exact start and end dates, with the timezone used.
- The services and systems included in the report.
- Definitions of received, rejected, answered and disclosed.
- How duplicate reports and requests spanning periods are counted.
- Any legal or technical publication limits affecting the figures.
- A dated correction when the scope or previously published figures change.
Read outcomes alongside the data model
The information available to answer a request depends on what the service actually stores. Account records, payment evidence and logs created inside a customer's applications are different categories. A transparency total alone does not demonstrate that a particular category is absent.
Use the privacy policy and VPS logging explanation alongside any report. For a specific concern, describe the service or record involved in the contact form. Keep private order references and transaction details out of public comments.
Questions, answered
Does an empty reporting archive mean zero requests?+
No. A zero is meaningful only when an actual report defines the period and category it measures. The absence of a dataset does not establish a total.
Is a transparency report the same as a security audit?+
No. A report describes a set of events or requests. An audit examines a defined system or process under its own scope and method. Neither replaces the other.
What should an incident record include?+
The affected service, time period, user impact, recovery and any corrections. An explanation is more useful when it distinguishes observations from assumptions.