Data Lifecycle & System Specification
1. System Architecture & Data Storage
1.1 Private Setup
This site runs on a private VPS managed entirely by me (LeaveMeTheTruckAlone). There are no user accounts, registration pages, or backdoors for the community or TruckersMP staff. Remote access to the server is locked behind a private VPN and requires SSH public-key authentication.
1.2 Collected Data
The server only handles two types of data:
- Media Assets: Video clips I record and upload via Medal.tv. External uploads are completely blocked.
- Access Logs: Standard web server logs (IP addresses, timestamps, and requested URLs) used strictly for security monitoring.
This site does not use databases, user profiles, or tracking cookies.
2. How Automated Deletion Works
2.1 Retention Limits
Every video file has a strict expiration date. Standard evidence is deleted after 120 days, calculated from the date the report was submitted to TruckersMP. For severe infractions where TruckersMP rules require permanent proof, the files are kept indefinitely to keep the report valid.
2.2 Direct File Purging
A local cron job script runs on the server to check file ages against the system clock. Once a file hits its expiration limit, the script permanently wipes it from the disk. There are no backups, caches, or recycle bins; when it is deleted, it is completely gone.
3. System Constraints & Policy Finality
3.1 No Admin Panels
This site has no web-based control panels, dashboards, or database interfaces. Because there is no web interface to interact with, it is technically impossible to manually change or stop the automated deletion schedules over the web.
3.2 Deletion Finality
I retain the right to manually delete or change files directly on the server at any time, but files will usually clear out naturally through the automated schedule. Once a file is wiped from this server, that link is permanently dead. I may keep separate copies of the evidence on external profiles like Medal.tv or YouTube. How I manage or delete files on those third-party sites is entirely up to me, and I owe no guarantees to anyone else.
4. Network Security & Traffic Limits
4.1 Traffic Logs
Every connection goes through a standard reverse proxy that logs incoming IP addresses, requested URLs, user agents, and timestamps. I use these logs strictly to monitor server health and track traffic patterns.
4.2 Automated IP Bans
To protect server stability, the system monitors traffic in real time. If you scan for hidden directories, try to brute-force URLs, or probe the backend, Fail2Ban will trigger an immediate firewall ban. These bans happen automatically at the network layer, and I will not review or listen to requests to unban your IP.
5. Third-Party Integrations
5.1 Independent Platform
This site is entirely standalone. It does not integrate or sync with APIs for TruckersMP, Discord, YouTube, or Medal. While some pages link directly to TruckersMP report URLs, I am not staff, I have zero visibility into their internal moderation systems, and I share no data with them.
6. Development Tools & AI Transparency
6.1 Assisted Code & Configuration
This site's layout and routing scripts were built with the assistance of AI models. However, the logic and architectural limits are entirely mine. Every line of code on this server was manually vetted and approved before deployment; no unverified or automated logic is allowed to run on this host.