Legal
Privacy Policy
Last updated: 12 October 2026
How Schengen Tracking processes account, driver, and location information to support Schengen 90/180 day compliance.
This Privacy Policy explains how Schengen Tracking ("Schengen Tracking", "we", "us") processes personal information when Organizations, users, and drivers use the Schengen Tracking web platform and mobile driver applications for Android and iOS, including personal-mode accounts (the "Service").
This Privacy Policy should be read together with our Terms and Conditions.
Schengen Tracking 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 Tracking
Schengen Tracking 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 Tracking 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, manually entered travel history, entry and exit dates, and stay history. We do not collect passport or travel-document numbers through current product forms.
Drivers who use the mobile applications (Android or iOS, including personal-mode accounts) may also generate location and country-detection information as described below.
6. Location Information
Where a driver activates tracking in a supported mobile application and grants the required permissions, Schengen Tracking may process precise GPS or other device-location information, including while the app is not open, when background location is enabled.
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. Precise coordinates are stored temporarily on our servers for processing and diagnostics and are not kept as a long-term route history.
Supported app versions may also send a limited operational diagnostic snapshot (for example app version, permission state, tracking service state, queue size, and upload timing) to help authorized administrators troubleshoot tracking. These snapshots do not include precise coordinates, credentials, or push tokens, and are retained only briefly (latest snapshot per device, typically up to seven days).
Schengen Tracking 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.
Drivers can turn tracking off in the app or through organization controls. Turning tracking off is not the same as deleting an account.
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
Supported mobile applications may temporarily store raw location samples (precise coordinates) on the device while Internet access is unavailable and attempt to synchronize them later. That local offline buffer is retained for up to 72 hours from each sample's original capture time, subject to a capacity limit and to cleanup when the app next runs (the operating system may delay cleanup while the app is not executing).
After the Service acknowledges a sample, the corresponding raw coordinates are removed from the device queue. Samples that expire locally without acknowledgment, or that the Service permanently rejects as too old, are deleted from the device without being treated as successfully uploaded; minimal non-coordinate gap metadata may be retained so compliance views can show that evidence is incomplete.
Server-side raw location samples, including precise coordinates, are kept long enough to finish country confirmation and late uploads from that same offline window. The Retention section states the current server-side period. Derived stay and gap metadata may remain longer as needed for compliance.
On logout or account deletion, the app clears that identity's offline location queues, gap metadata, and credentials on the device. If the device is offline during a deletion request, local data is cleared immediately and server-side deletion is completed when the authenticated request reaches our servers.
Information stored on the device is also subject to the device's own settings and security. Offline location queues are excluded from Android cloud backup where the platform allows that configuration.
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 (including precise coordinates) are deleted only after they can no longer be required by an upload the Service still accepts. The Service accepts a sample for 72 hours after the device captured it. Because a later sample in that same offline window can arrive about 72 hours after an earlier one was stored, the server keeps the raw sample until it is older than 144 hours from capture, and until it was received more than 6 hours ago. The 6-hour period is a grace for a request that has just arrived. It is not the longest supported gap between uploads. Samples stuck in processing are marked failed after 6 hours from receipt and are then kept until the same capture-time horizon. This temporary server storage is not ephemeral in-memory-only processing. Country, stay, and crossing records used for Schengen calculations are separate and are not deleted by this cleanup.
The production cleanup job is scheduled once per day. Samples that become eligible between runs are removed on the next successful cleanup. Under healthy operation that is the next daily run after the 144-hour capture horizon and the 6-hour receive grace. A failed run, a run that stops because of its time limit or batch limit, or rows skipped because another request holds them, can leave coordinates stored longer. That delay is not a guaranteed maximum, and precise coordinates are stored on the server during this period. If the phone app is not running, the on-device queue is not deleted until the app next runs.
Derived compliance information, such as country transitions, border events, and stay history needed for Schengen 90/180 calculations, may be retained for longer 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. Open tickets are not auto-deleted on that schedule. 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, organization audit, and invoice records, we do not apply a single fixed retention period. We retain this information for as long as reasonably necessary to provide the Service and to meet legal, accounting, security, and dispute-resolution needs. When a company-linked driver deletes their app login, personal contact fields and raw location samples tied to that login are cleared, but organization-held stay/crossing history and the driver display name are not automatically anonymized; those records remain for the Organization's Schengen compliance support, typically for at least 180 days after the last stay day that still affects a rolling 90/180 window, or until the Organization deletes the driver or workspace. Drivers may request further deletion of organization-held records through their Organization administrator or our Contact page.
Database backups maintained by our hosting providers may retain deleted data until those backups expire. Backup retention periods are controlled by the hosting provider and are not claimed as immediate erasure.
13. Service Providers
We rely on third-party technology and infrastructure providers to operate the Service, including hosting and edge deployment, managed PostgreSQL databases, scheduled jobs, email delivery, mobile push notification delivery (such as Firebase Cloud Messaging on Android), cookie consent tooling and website analytics where enabled, payment/merchant-of-record processing where used, 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 Tracking workspace.
Each Organization is responsible for ensuring that its use of Schengen Tracking 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 Tracking must not be used by an Organization for unlawful or covert surveillance.
Schengen Tracking 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.
Authenticated users can initiate account deletion in the mobile app account screen, in web account settings, or on our Delete account page after signing in. We do not reveal whether an arbitrary email address has an account before authentication.
Account deletion is different from removing or unlinking a driver, leaving an organization, deleting an organization, turning tracking off, or canceling a subscription. Organization owners with other members must transfer ownership (or use a separate organization deletion flow) before their personal login can be deleted. When a company-linked driver deletes their login, that deletes the app account/credentials and personal app data (devices, sessions, raw GPS samples, and personal contact/passport fields on the driver profile). It does not anonymize organization-held stay and crossing history; unlinking is not erasure of that compliance data. To request deletion of organization-held records, contact the Organization administrator or use our Contact page.
We may keep a minimal platform audit record that an account deletion occurred (without storing the deleted email or coordinates). Hosting backups may retain copies until they expire.
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.