Data Processing Agreement
This document is available in English and Hebrew. If there is any difference between them, the English version governs.
This Data Processing Agreement ("DPA") forms part of the Terms of Use between 4X4Ops.com (reg. no. ) ("Processor", "4X4Ops") and the company using 4X4Ops ("Controller", "Customer"). It applies when 4X4Ops processes personal data on the Customer's behalf. It is accepted together with the Terms; a countersigned copy is available on request from support@4x4ops.com.
1. Subject matter and duration
Processing of personal data contained in Customer Data to provide the Service, for as long as the Customer's account exists and until deletion as described below.
2. Nature and purpose
Hosting, storage, synchronisation, display, backup, export and deletion of fleet-management records, solely to provide, secure and support the Service.
3. Data subjects and categories of data
- Data subjects: the Customer's team members (owners, managers, mechanics, guides/drivers), technicians and other contacts the Customer records.
- Categories: names, email addresses, phone numbers, roles, driver names linked to vehicle trips, fault reports and notes entered by the Customer. The Service is not designed for special-category data, and the Customer should not enter it.
4. Processor obligations
- Process personal data only on the Customer's documented instructions (these Terms and the Customer's use of the Service), unless required by law, in which case we will inform the Customer unless the law forbids it.
- Ensure that persons authorised to process the data are bound by confidentiality.
- Implement appropriate technical and organisational measures (Annex A).
- Assist the Customer, taking into account the nature of processing, in responding to data-subject requests and in meeting obligations regarding security, breach notification and impact assessments.
- Notify the Customer without undue delay, and where feasible within 72 hours, after becoming aware of a personal-data breach affecting Customer Data.
- At the end of the Service, delete Customer Data (the Customer can export it first at any time). Deletion from live systems is immediate on company deletion; residual backup copies expire within the provider's standard cycle.
- Make available information reasonably necessary to demonstrate compliance, and allow for reasonable audits (normally satisfied by our written answers and our providers' certifications), with at least 30 days' notice and at the Customer's cost.
5. Sub-processors
The Customer authorises the sub-processors below. We will give notice (in the app, by email or on this page) at least 14 days before adding or replacing a sub-processor, and the Customer may object on reasonable grounds; if we cannot accommodate the objection, the Customer may terminate and receive a prorated refund.
| Sub-processor | Purpose | Location |
|---|---|---|
| Google Cloud / Firebase (Google LLC, Google Ireland Ltd.) | Hosting, database, authentication, server functions | EU data region (europe-west) |
Paddle.com Market Ltd processes payment data as an independent controller and is not a sub-processor of Customer Data.
6. International transfers
Where personal data is transferred outside Israel or the EEA, the transfer relies on an adequacy decision or on the European Commission's Standard Contractual Clauses as incorporated in our providers' terms.
7. Liability and precedence
Liability under this DPA is subject to the limitations in the Terms. In case of conflict regarding personal data, this DPA prevails.
Annex A – Security measures
- Encryption in transit (TLS) and at rest (provider-managed).
- Tenant isolation: every company's data is stored separately and access is checked on the server for every request.
- Role-based access (owner, manager, mechanic, guide) enforced by server-side security rules; billing state can only be changed by our server.
- Password-based authentication with a minimum length, password-reset by email, re-authentication for destructive actions (account or company deletion).
- Administrative access limited to the platform owner, protected by two-factor authentication; secrets stored in a managed secret store, not in code.
- Payment webhooks verified with signed requests; no card data processed by 4X4Ops.
- Audit fields on records (who changed a record and when); self-service export and deletion.