Visit and Message Guide
A visit to Voapex can remain a reading session. The circuit dossiers and design notes do not require a player login, and there is no playable racing service collecting driving telemetry through these pages. The information described here comes from delivering the website, measuring visits and handling an optional message to the pit desk.
Arriving at a page
The systems that host and deliver Voapex receive technical request information, including an IP address, browser details and the address requested. Operational logs may help identify delivery problems or abusive requests. This infrastructure processing is different from the private message record created by the contact form. We do not state that all hosting records have the same retention period as that form record.
Loading the visitor measurement
Public pages include Histats under the central statistics configuration used by this website. Histats can receive technical visit information and may use cookies or similar identifiers to measure use. The counter is shared with other websites connected to that configuration, so its totals can combine their visits. Browser settings or privacy tools may block the counter or restrict cookies while the reading pages remain available.
Choosing to write to the pit desk
The contact form collects the name, email address and message you enter. The purpose is to understand the enquiry and reply when appropriate. A successful submission becomes a private WordPress entry accessible to website administrators. It is not added to the public Setup Notes or published as a comment. Do not place sensitive personal information, credentials or confidential documents in your message.
Keeping the channels separate
Contact fields are sent to this website. We do not intentionally transmit the name, email or message to Histats as visitor events. The form also uses a short-lived rate-limit marker derived from the request address to discourage repeated submissions. This protection does not turn an enquiry into a public profile. Choosing not to send a message avoids creating that optional private record.
Leaving the active message store
A scheduled cleanup removes private contact entries older than 90 days when WordPress scheduled tasks execute. This mechanism does not guarantee deletion at an exact minute. Copies in earlier operational backups may remain until those backups expire or are replaced. The acknowledgement shown after submission confirms acceptance, not human review or any immediate change to historical copies.
Asking for a correction or deletion
Use the Pit Desk to ask about information you previously submitted. Provide the same email address and enough context to identify the enquiry without sending identity documents. A clarifying exchange may be necessary before a record is changed. This guide should track the site’s actual services: if the form, cleanup process or visitor statistics change, the explanation needs to change with them.
