Frequently asked questions

Wintertrace is open-source software for documenting winter service operations digitally. It captures GPS tracks, weather data, and photos automatically, and generates PDF service proofs. Wintertrace is the international (English-language) brand — Schneespur is the German variant of the same software.

Nothing. The core software is open source and free under GNU AGPLv3. Only the standard cost of web hosting applies — typically a few dollars per month. Optional premium modules may become available later; the core software remains free.

Wintertrace is maintained as a private open-source project by an independent maintainer based in Germany. The full operator details are listed on the imprint page.

Both brands run on the same software underneath. Schneespur is the German-language brand with vocabulary suited to German legal context (Verkehrssicherungspflicht, GDPR). Wintertrace is the international brand with broader compliance vocabulary suited to multiple jurisdictions.

Wintertrace is not an order management system, a routing optimiser, or an ERP. It focuses on operation documentation. If you need a full solution for dispatch, accounting, and customer relationship management, Wintertrace is not the right tool on its own.

PHP 8.2 or higher, MySQL 5.7+ (or MariaDB 10.3+), the PHP extensions pdo_mysql and gd, plus cron job support. Most shared hosting providers support these by default.

No. Installation runs via FTP and a browser assistant. A cron job is required for background tasks, which most hosts expose through a web interface.

The recommended path is the Wintertrace installer: a small ZIP with a single install.php inside. Upload that one file to your hosting via WebFTP, open it in your browser, and the installer pulls the full signed core onto the webspace automatically. A browser assistant then asks for database credentials and creates the admin account. Add a cron job that runs every minute, and you’re done. A detailed walkthrough lives on the installation page.

Yes, in the vast majority of cases. The installer is one file. Every reasonable hosting panel has a built-in file manager or WebFTP — that is enough to upload it. From there, opening the file in your browser does the heavy lifting: the hundreds of core files are pulled onto the webspace for you, and a browser assistant collects database credentials and creates the admin account. The whole flow is workable from a phone or tablet if that is all you have.

Any reputable shared hosting that supports the requirements above. There is no preferred provider — pick one local to your region with a good support reputation.

No. Docker works but is not required. Standard shared hosting is sufficient.

Roughly 10 minutes once you have your hosting credentials and the release archive.

Wintertrace can check for new versions (the check is disableable). With one click in the admin area, the update is downloaded, verified against an Ed25519 signature, and installed. No FTP upload or command line needed.

The software stays in maintenance mode and the next attempt resumes without data loss. A database backup before update is recommended.

OwnTracks — free, open source, available on iOS and Android. Setup via QR code takes seconds per driver.

No. OwnTracks sends location data directly to your Wintertrace installation over HTTPS. There is no cloud detour and no third-party processor involved in the GPS data path.

Operations can be entered manually after the fact. Weather data is fetched retroactively. Missing GPS is flagged as an alert in the dashboard.

No. GPS points are locked after operation end and are immutable. This protects the integrity of the service proof.

OwnTracks uses the smartphone GPS hardware. Typical accuracy is in the 5–10 metre range. The per-point accuracy is recorded with each fix.

OwnTracks is optimised for low battery use. Consumption is elevated during an active operation, but for typical shifts it is manageable on modern phones.

The driver app captures operations offline and syncs once connectivity returns. GPS via OwnTracks runs independently of the browser connection.

Temperature, precipitation, snow depth, wind speed, humidity, and a textual condition (for example "Light snowfall"). Automatically at operation start and end.

Open-Meteo is the default provider (free, global, no API key). Configurable alternatives include Bright Sky (DWD data for Germany) and MET Norway. The provider architecture is extensible.

In liability cases, objective weather data is a key part of the record. Because the data comes from independent weather services — not from the operator — it carries more weight than a self-reported note.

Wintertrace fetches weather data asynchronously. If the API is briefly unavailable, the fetch retries on the next cron run. Missing data is flagged on the dashboard.

Not as a primary path in the current version — the architecture is designed for automatic API retrieval. Manual entry could be added as a module or extension later (vision).

Wintertrace includes integrated tools that support GDPR-aligned data handling: consent records with audit history, driver-data anonymisation, configurable retention policies, automated deletion, and full data export. Because data stays on your own server, no processor agreement with a cloud provider is needed regarding the software itself. GDPR compliance is established through correct usage in your organisation — Wintertrace is not a certification.

Only the operator and the users they create (admin, drivers, customers). Wintertrace does not send data to the publisher or to any third party.

Configurable per data category. A common default is three years — close to the liability statute of limitations in many jurisdictions. Expired data is automatically aggregated and deleted.

Yes — through the anonymisation function. Personal data is irreversibly replaced with placeholders while operation records remain intact.

Yes — as a ZIP archive containing profile data and consent records.

Only functionally necessary cookies (session). No tracking cookies, no analytics cookies, no advertising cookies. This is verifiable in the code.

The PDF bundles GPS track, weather data, and photos in a verifiable form. It can be used as evidence in liability cases. Admissibility in each specific case should be assessed by qualified counsel in the relevant jurisdiction.

Typically: date and time of service, weather conditions at that time, and evidence that service was actually performed. Wintertrace captures all of these. Specific requirements vary by jurisdiction — qualified counsel can clarify what applies to you.

Limitation periods for claims arising from inadequate winter service vary by jurisdiction (often two to six years). Wintertrace has a three-year retention default, configurable. Specific terms should be reviewed with qualified counsel.

The GPS track demonstrates presence at the location. Combined with weather data and photos, it forms a complete record. Standalone, the track is typically not sufficient.

Yes — through the optional customer portal. Customers see their operations, the weather data, and (optionally) GPS tracks and photos. They can also generate their own PDF reports.

No artificial limits. The only ceiling is the capacity of your web hosting.

Yes. Manual operations can be entered in the admin area or driver app. Weather data is fetched retroactively. Manual operations are flagged as such in the service proof.

24 hours after operation end — after that the operation is locked. This protects the integrity of the service proof. Every change is logged in the audit trail.

Yes. Email notifications with PDF attachment can be configured per customer or per service location.

Every update is signed with Ed25519. A root verification key is embedded in the application. SHA-256 checksums verify file integrity. Tampering is mathematically excluded as long as the root key is safe.

No. The admin decides whether and when to install an update. Even the daily update check can be disabled.

Security-relevant updates are marked in the changelog. Critical issues are highlighted in the update notification inside the application.

Wintertrace is released under the GNU Affero General Public License v3 (AGPLv3). You may use, modify, and distribute the software freely. If you run a modified version as a network service for third parties, the copyleft clause requires you to publish your changes under the same licence. The full text is in the repository.

Yes. AGPLv3 allows unrestricted modification for your own operations. If you make the modified version available publicly as a service to third parties, the copyleft clause applies and your changes must be published under AGPLv3 as well.

Yes. The module system is live and the first add-on — the Diagnostic module — is published. Modules are optional: the Wintertrace core runs without any of them. The catalogue lives at /modules/ and is fed by the central add-on registry, so new add-ons appear automatically as they are released.

The module interface is in place and the first official add-on is shipping. Developer documentation for third-party modules is still in preparation — when it is ready, it will be published alongside the existing module docs.

On GitHub — the link is on the open-source page and in the website footer.

The software includes an integrated, context-sensitive help system on each admin page. Additional documentation lives in the repository on GitHub. For specific questions, open a GitHub issue.

Install the optional Diagnostic module. Once a free API key has been requested by email and pasted into the module settings, the installation submits a structured fault report directly to the maintainer — error message, stack trace, version numbers, and active modules. This replaces the slow back-and-forth that vague "doesn't work" support emails usually start with. The module is opt-in, transmits no personal data, and can be stopped at any time.

Not currently. Optional services (managed hosting, installation, enterprise support) are conceivable long-term. For now, Wintertrace is self-service.

In the GitHub issue tracker.

GitHub Issues and Discussions are the primary touchpoints. A dedicated forum does not exist yet.