Legal
Privacy Policy
Last updated: 30 September 2026
How Schengen Tracker processes account, driver, and location information to support Schengen 90/180-day compliance.
This Privacy Policy explains how Schengen Tracker ("Schengen Tracker", "we", "us") processes personal information when Organizations, users, and drivers use the Schengen Tracker web platform and Android driver application (the "Service").
This Privacy Policy should be read together with our Terms and Conditions.
Schengen Tracker is a compliance-support tool for the Schengen 90/180-day rule. It is not a surveillance tool and is not designed to track drivers' routes.
1. Privacy Policy
We aim to process only the information that is needed to operate the Service, and to be transparent about what that information is, why it is processed, and who can see it.
By using the Service you acknowledge the practices described in this Privacy Policy. Processing of personal information is also subject to applicable data-protection law, and nothing in this Privacy Policy removes rights or obligations that apply to you under that law.
2. About Schengen Tracker
Schengen Tracker is business software used primarily by transport companies, fleet operators, dispatchers, employers, and other organizations managing professional drivers. It helps them monitor and organize information relevant to the Schengen 90/180-day rule, including calculated used and remaining days, country and border-transition events, and historical stays.
Schengen Tracker provides informational and operational assistance only. It is not an immigration authority, border authority, government service, or legal adviser.
3. Information We Process
Depending on how the Service is used, we may process the following categories of information:
- account and organization information;
- driver information;
- location information, including GPS or other device-location data;
- country, border-transition, and stay information derived from location or entered manually;
- Schengen 90/180-day calculations and related warnings or statuses;
- support requests and correspondence;
- subscription, plan, and invoicing information;
- audit and security records relating to actions taken in the Service;
- technical information needed to operate and secure the Service.
4. Account and Organization Information
When an Organization is created or users are invited, we process information such as names, email addresses, phone numbers, roles and permissions, the Organization's name and country, sign-in credentials (stored in protected form), and plan and billing details.
This information is used to create and secure accounts, to manage access for owners, admins, dispatchers, and other authorized users, and to administer subscriptions and support.
5. Driver Information
Organizations may add drivers to the Service. Driver information may include a driver's name, contact details, employment status, passport or travel-document details entered for compliance workflows, manually entered travel history, entry and exit dates, and stay history.
Drivers who use the Android application may also generate location and country-detection information as described below.
6. Location Information
Where a driver activates tracking in the Android application and grants the required permissions, Schengen Tracker may process GPS or other device-location information.
Location information is processed for compliance purposes: to determine the country in which a driver is located, to detect possible country changes and possible Schengen entry or exit events, and to support Schengen 90/180-day calculations.
Schengen Tracker is a compliance-support tool, not a surveillance tool. It is not a route-surveillance product, and it is not designed to give Organizations continuous detailed monitoring of a driver's exact route, private stops, private visits, personal movement history, or movements unrelated to Schengen compliance.
7. How Location Information Is Used
Location information is used primarily to determine country presence and possible transitions relevant to Schengen compliance. We use it to:
- identify the country a driver is in;
- detect possible country changes and possible Schengen entry or exit events;
- update stay history and Schengen 90/180-day calculations;
- generate compliance warnings and statuses;
- operate, maintain, troubleshoot, and secure the Service.
We do not sell location information.
8. Country and Border Detection
Country and border detection are technical assistance features. Detection may be delayed, inaccurate, incomplete, or unavailable because of factors such as GPS accuracy, device settings, permissions, battery optimization, network availability, or operating-system restrictions.
A detected country or border crossing is a software-generated, informational result. It is not official proof of a person's physical location or of a border crossing, and a missed detection does not mean that a crossing did not occur.
9. Offline Synchronization
The Android application may temporarily store location or travel information on the device while Internet access is unavailable and attempt to synchronize it to the Service later.
Information stored on the device is subject to the device's own settings and security. It may be lost or fail to synchronize if, for example, the application is removed, application data is cleared, or the device is reset or fails.
10. Information Visible to the Organization
Information processed for a driver is made available to the driver's Organization and its authorized users (such as owners, admins, and dispatchers) according to their roles and permissions.
This generally includes driver records, stay history, detected countries, country transitions and border events, and calculated Schengen days used and remaining. The Service is designed so that Organizations see compliance-relevant information rather than a detailed record of a driver's routes.
Organizations should not be able to access another Organization's data; each Organization's workspace is kept separate.
11. Purpose of Processing
We process personal information in order to:
- provide, operate, and maintain the Service, including Schengen 90/180-day calculations and country and border-transition detection;
- create and manage accounts, organizations, and user access;
- send notifications and compliance warnings;
- provide customer support;
- administer plans, driver limits, and invoicing;
- protect the security and integrity of the Service, prevent misuse, and keep audit records;
- improve the reliability of the Service and fix errors;
- comply with legal obligations where applicable.
12. Data Retention
Raw location samples are normally retained for up to 24 hours before they are deleted or cleaned up by an automated process. Raw location samples are not kept as a long-term route history.
Derived compliance information, such as country transitions, border events, stay history, and related audit records, may be retained for longer so that Schengen 90/180-day calculations remain possible and so that Organizations have a reliable compliance history.
Resolved support tickets and their messages are normally retained for up to 7 days after resolution and are then automatically deleted during our scheduled cleanup process. If a resolved conversation is reopened before deletion, the retention period begins again after it is resolved again.
For other information, including user, driver, stay, audit, and invoice records, we do not apply fixed retention periods. We retain this information for as long as reasonably necessary to provide the Service, to meet legal, accounting, security, and dispute-resolution needs, and to preserve historical compliance records that an Organization relies on.
Historical information may remain preserved during a suspension where supported by the Service.
13. Service Providers
We rely on third-party technology and infrastructure providers to operate the Service, including providers of hosting, databases, scheduled jobs, email delivery, notification delivery, networks, geographic data, and mobile operating systems.
These providers process information only as needed to supply their services to us. Problems or restrictions affecting them may affect the Service. We do not sell personal information.
14. Security
We use reasonable technical and organizational measures to protect information, including access controls based on roles, separation of Organization workspaces, and encrypted connections.
No system is completely secure, and we cannot guarantee absolute security. Users are responsible for protecting their passwords, login credentials, devices, and account access, and Organizations are responsible for managing the access they grant to their own users.
15. Organization Responsibilities
In this Privacy Policy, an "Organization" means the transport company, fleet operator, employer, or other business that creates a Schengen Tracker workspace.
Each Organization is responsible for ensuring that its use of Schengen Tracker in relation to its own drivers and employees complies with applicable laws and internal company requirements. Where required by applicable law, the Organization is responsible for informing its drivers that location information may be processed for country detection and Schengen compliance purposes.
Schengen Tracker must not be used by an Organization for unlawful or covert surveillance.
Schengen Tracker remains responsible for how the Service itself processes and protects the information it holds, as described in this Privacy Policy.
16. Data Access, Correction, and Deletion
Depending on applicable law, you may have the right to ask about the personal information we hold about you, to request that it be corrected, or to request that it be deleted or restricted.
Because Organizations manage their drivers' records, drivers should generally contact their Organization first. Organizations and users can also contact us to make a request, and we will respond in line with applicable law. We may need to verify identity, and we may retain information that we are required or permitted to keep, for example for legal, security, or accounting purposes.
17. Changes to This Privacy Policy
We may update this Privacy Policy to reflect product changes, legal or security requirements, or changes in how we process information. The date of the latest update is shown at the top of this page. Where appropriate or required, we will take additional steps to inform affected users.
18. Contact
If you have questions about this Privacy Policy or want to make a data request, please reach out through our Contact page.