Privacy Policy
Truck Pulse ("we", "us") is a management platform for virtual trucking companies ("Hubs"). This policy explains what personal data we process when you use the platform, why we process it, how long we keep it, and the rights you have over it. Much of our user base is in the European Union, and we operate the platform to GDPR standards for everyone, wherever you are.
Who is responsible for your data
Responsibility depends on where the data lives:
- Truck Pulse is the data controller for your platform account (sign-in identities, email, billing) and for platform-level operations such as abuse handling, security and service telemetry.
- Each Hub you join is the data controller for the data it collects about you as its member — your roster record, applications you send it, leave requests, points, delivery history and reports handled by its staff. Truck Pulse processes that data on the Hub's behalf, as its data processor.
If you have a question about how a specific Hub uses your data, contact that Hub's staff first; for anything about the platform itself, contact us (see "Contact and requests" below).
What we store, why, and on what legal basis
| Data | Purpose | Lawful basis |
|---|---|---|
| Steam ID and persona (name, avatar) | Sign-in, matching your deliveries from connected trackers to your roster profile | Contract (providing the service) |
| Discord ID and username | Sign-in, Hub Discord role sync and notifications you opt into | Contract |
| Email address | Account notifications, fallback sign-in codes, billing receipts | Contract |
| TruckersMP ID and public profile snapshot | Verifying your TruckersMP identity for Hubs that require it | Contract |
| Delivery-tracker job data (routes, cargo, distances, timestamps, raw tracker payloads) | Your Hub's logbook, statistics, points and leaderboards — received from trackers (Trucky, TruckersHub) your Hub connects | Contract (processed for your Hub) |
| Content you write (applications, leave reasons, reports) | Handled by the Hub (or, for abuse reports, our safety team) you sent it to | Contract / legitimate interest (platform safety) |
| IP address on submitted reports | Investigating misuse of the public report forms (flooding, ban evasion) | Legitimate interest (abuse prevention) |
| Billing data (name, address, payment method via Stripe) | Subscriptions and invoicing for paid Hub plans | Contract / legal obligation (tax records) |
We never see or store your card number — payment details go directly to Stripe. We do not sell personal data, run advertising, or profile you beyond the Hub statistics described above.
How long we keep data
Retention is enforced automatically by scheduled cleanup jobs. The current windows are:
| Data | Kept for |
|---|---|
| Raw delivery-tracker payloads | 90 days, then stripped from the job record |
| Route replay breadcrumbs | 90 days by default (each Hub can tune its own window) |
| Audit / activity logs | 365 days |
| Discord delivery logs | 90 days |
| IP addresses on reports | 180 days, then removed from the report |
| One-time sign-in codes | Valid for minutes; expired codes are purged daily |
| Personal data export archives | 3 days, then deleted automatically |
Everything else is kept while your account or the owning Hub exists, and handled as described under "Deleting your account" when it goes. Deleted data can persist in our encrypted backups until those backups rotate out on their own schedule (a matter of weeks); backups are never used to restore deleted personal data except in disaster recovery.
Cookies and analytics
We set only strictly necessary cookies: a session cookie (keeping you signed in) and a security (CSRF) token. There are no advertising or cross-site tracking cookies, which is why you see no cookie banner. Our website analytics (Pirsch) are cookieless — they count visits to our public pages from our own servers, never store your IP address, and do not identify or fingerprint you. Signed-in areas of the app are not tracked by Pirsch.
Who processes data for us (subprocessors)
- Hosting provider and Laravel Forge — running the servers the platform lives on
- Stripe — payment processing and invoicing
- Our transactional email provider — delivering account and notification emails
- Cloudflare — content delivery and custom Hub domains
- Pirsch — cookieless, EU-hosted website analytics
- Laravel Nightwatch — application performance monitoring; telemetry is scrubbed of emails and gaming identities before it leaves our servers
Your rights
You can exercise your GDPR rights (access, rectification, erasure, restriction, portability, objection) directly in the app:
- Access & portability: request a machine-readable export of your data from your profile page ("Your data"). We compile it and email you a download link.
- Rectification: edit your profile at any time; identity details from Steam, Discord and TruckersMP can be re-synced or unlinked.
- Erasure: delete your account from your profile page. You leave all Hubs immediately, and after a 30-day grace period every personal identifier is permanently removed. Your delivery history stays with your Hubs in anonymized form so their records remain consistent. You can cancel within the grace period by signing back in and confirming the cancellation. If you own a Hub you must transfer or close it first — contact us and we will help.
You also have the right to complain to your local data protection authority.
Contact and requests
For any privacy question or request the self-service tools do not cover, email [email protected]. We answer data-subject requests within one month.
We will announce material changes to this policy by email or in-app notice before they take effect.