Privacy Statement

Merge distribution and fleet operations software · Techsa FZC

Last updated: September 17, 2026

This Privacy Statement describes how Techsa FZC (“Techsa,” “we,” “us”) collects, uses, shares, and protects information in connection with the Merge services (“Service”). It applies to operators, administrators, drivers, and other users who interact with our web and mobile experiences. If you use the Service on behalf of an organization, that organization’s agreement with us may include additional or different terms about data processing.

1. Who we are and which products this covers

Techsa FZC is the developer and data controller for the Service, and is the developer listed for our applications on Google Play. For privacy inquiries: info@techsa.io.

This Privacy Statement applies to the following products:

2. Information we collect

Depending on how you use the Service, we may collect:

2a. Location data in the MERGE Driver app (including background location)

MERGE Driver (io.techsa.merge.driver) is a workforce application issued by an employer to its delivery drivers. It collects precise location data, including in the background — that is, while the app is minimised, the screen is locked, or the app is closed. The app declares the Android permissions ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION and ACCESS_BACKGROUND_LOCATION for this purpose.

Why we collect it. Background collection is required for the app’s core purpose — a delivery vehicle is in motion with the phone pocketed or mounted, so location must continue to be recorded when the app is not on screen. We use it to:

When it is collected. Location is recorded while the driver is clocked in to a shift. Clocking out of a shift stops collection. The app shows a persistent notification while location tracking is running, so it is always visible that tracking is active.

Consent. Before the app asks for any location permission, it shows an in-app disclosure explaining that location is collected in the background and why. The driver must affirmatively accept that disclosure before the Android permission prompt is shown. A driver who declines is not asked for the permission; location-dependent features will not work, and the driver should speak to their employer.

Who receives it. Location data is shared with the driver’s employer — the organization that issued the account — and with the infrastructure and mapping providers described in section 5. It is not sold, and it is not used for advertising.

Your control. You may revoke location permission at any time in Android Settings, and you may uninstall the app. Because this is an employer-issued workforce tool, revoking permission may prevent you from performing job functions; requests to access or delete location history should be directed to your employer, who controls the data, or to info@techsa.io.

3. How we use information

We use the information above to:

We do not sell your personal information. Techsa does not use operational logistics content to train public machine-learning models for unrelated third parties.

4. Legal bases (where GDPR or similar law applies)

Where required, we rely on: performance of a contract with your organization; legitimate interests (security, product improvement, internal analytics in aggregate form) not overridden by your rights; consent where we expressly ask for it (for example, certain device permissions); and legal obligations.

5. How we share information

We share information only as needed:

6. International transfers

We may process data in countries where Techsa or our providers operate. Where required, we use appropriate safeguards (such as standard contractual clauses) for transfers from the European Economic Area, UK, or Switzerland.

7. Retention

We retain information for as long as needed to provide the Service and fulfill the purposes in this Statement, unless a longer period is required by law or your organization’s agreement. Retention schedules may vary by data category and customer configuration (for example, archival exports or legal holds).

8. Security

We implement technical and organizational measures designed to protect data, including encryption in transit where appropriate for the Service architecture, access controls, and monitoring. No method of transmission or storage is completely secure; please use strong passwords and protect devices used to access the Service.

9. Your choices and rights

Depending on your location, you may have rights to access, correct, delete, or export personal data, or to object to or restrict certain processing. Many requests must be routed through your organization’s administrator where the Service is deployed for enterprise use. You may also contact us at info@techsa.io. We will respond consistent with applicable law.

10. Cookies and similar technologies

We use cookies and local storage as needed for session management, security (for example, CSRF protections where applicable), language preferences, and product functionality. Third-party scripts loaded by the Service (such as maps providers) may set their own cookies or identifiers governed by their policies.

11. Children

The Service is not directed to children under 16, and we do not knowingly collect their personal information.

12. Changes to this Statement

We may update this Privacy Statement from time to time. We will post the revised version and update the “Last updated” date. For material changes, we will provide additional notice as appropriate.

13. Related terms

Use of the Service is also governed by our Terms of Service.

This Privacy Statement is a general description for customers and users. It is not an exhaustive data-processing agreement (DPA). Enterprise customers requiring GDPR Article 28 terms or similar should execute Techsa FZC’s standard DPA or equivalent contractual provisions.