Logistr · Legal
Data Processing Addendum
Last updated November 17, 2026
- Part of our Terms for every business. Nothing to sign.
- You decide what happens to your data. We process it only to run Logistr for you.
- We tell you within 72 hours about a breach affecting your data.
- When you leave, you can take everything; then we delete it.
This Data Processing Addendum (“DPA”) forms part of the Terms of Service between Logistr LLC (“Logistr”, the “processor”) and the Business (the “controller”). It applies automatically. If you need a countersigned copy, email legal@logistr.com. Words defined in the Terms or in the GDPR have the same meaning here. If this DPA and the Terms disagree about personal data, this DPA wins.
1. Scope and roles
This DPA covers personal data in Business Data that Logistr processes for the Business (“Personal Data”). The Business is the controller (or a processor acting for its own customer, in which case Logistr is a subprocessor). Logistr is the processor. Each party will comply with the data protection laws that apply to it, including, where relevant, the GDPR, UK GDPR, Swiss FADP, CCPA/CPRA and the Saudi PDPL.
2. Instructions
Logistr processes Personal Data only on the Business’s documented instructions. The Terms, this DPA and the Business’s use and configuration of the Service (including its Rules, Settings and Connections) are those instructions. Logistr will tell the Business if it believes an instruction breaks the law. Under the CCPA, Logistr is a service provider and will not sell or share Personal Data, or retain, use or disclose it outside the direct business relationship.
3. Our people
Everyone at Logistr who can access Personal Data is bound by confidentiality, trained on data protection, and given access only as needed.
4. Security
Logistr maintains the technical and organizational measures in Annex 2, and may improve them over time without lowering overall protection.
5. Subprocessors
The Business authorizes Logistr to use the subprocessors listed on Subprocessors. Logistr has a written contract with each that protects Personal Data at least as well as this DPA, and remains responsible for them. Logistr will give at least 30 days’ notice of a new subprocessor by updating that page and emailing account owners who ask for updates at legal@logistr.com. The Business may object on reasonable data protection grounds within that time; if we cannot resolve the objection, the Business may end the affected service and receive a refund of prepaid fees for the unused period.
6. Helping with requests
Logistr gives owners tools to find, export, correct and delete Personal Data, and will help further with requests from Workers, Customers or other individuals. If someone contacts Logistr directly about Business Data, Logistr will pass the request to the Business without answering it, unless the Business asks us to. Logistr will also reasonably help with data protection impact assessments and consultations with authorities.
7. Personal data breaches
Logistr will notify the Business without undue delay, and in any case within 72 hours, after becoming aware of a breach affecting its Personal Data. The notice will say what happened, the data and people likely affected, the likely consequences, and what we are doing, and we will update it as we learn more. Notifying is not an admission of fault.
8. Return and deletion
At any time the Business can export its Personal Data. When the Business deletes its account or the Terms end, Logistr deletes Personal Data from live systems within 30 days and from backups within a further 35 days, unless the law requires keeping it. On request, Logistr will confirm deletion in writing.
9. Audits
Logistr will make available the information needed to show compliance with this DPA, including answers to reasonable security questionnaires and any third-party audit reports it holds. If that is not enough, or an authority requires it, the Business may audit once a year with 30 days’ notice, during business hours, at its own cost, under confidentiality, and without access to other customers’ data.
10. International transfers
Where Personal Data is transferred from the EEA, UK or Switzerland to a country without an adequacy decision, the Standard Contractual Clauses (Commission Decision 2021/914) are incorporated by reference: Module 2 (controller to processor) or Module 3 (processor to processor), with clause 7 included, option 2 in clause 9 (general authorization, 30 days’ notice), the optional language in clause 11 deleted, and clauses 17 and 18 governed by Irish law and Irish courts. For UK transfers the UK International Data Transfer Addendum applies; for Swiss transfers the FDPIC is the competent authority. Annexes 1 and 2 below complete the clauses. Other countries’ transfer rules are met by equivalent safeguards.
Annex 1: Details of processing
| Subject matter and purpose | Providing Logistr: importing work, planning routes, running the worker app and tracking pages, sending customer updates from the Business’s mailbox, recording proof, analytics for the Business, and support. |
| Duration | The term of the Terms, plus the deletion periods in section 8. |
| Nature | Collection, storage, organization, analysis (including by AI models), display, transmission and deletion. |
| Data subjects | The Business’s managers and leads, Workers, and Customers (including their contacts at places). |
| Categories of data | Names, work and customer email addresses, phone numbers, addresses and places, task details and notes, access notes, worker location while a task is On the way, proof photos and signatures, chat messages, ratings, problem reports, and logs of changes. |
| Special categories | None intended. The Business should not upload them (Terms, section 6). |
| Frequency | Continuous, while the Service is used. |
| Location | AWS, primary region [AWS region, e.g. Middle East (Bahrain) me-south-1]; subprocessors as listed. |
| Controller contact | The account owner’s email on file. |
| Processor contact | Logistr LLC, [Registered address], legal@logistr.com |
Annex 2: Security measures
- Hosting: Amazon Web Services, in data centers with physical security, redundancy and independent certifications (such as ISO 27001 and SOC 2) held by AWS.
- Encryption: TLS 1.2 or higher in transit; AES-256 at rest for databases, backups and S3.
- Proof storage: a private Amazon S3 bucket with all public access blocked; files reach users only through the authenticated API or short-lived signed links.
- Access control: least privilege; production access limited to named staff with multi-factor sign-in; access logged and reviewed.
- Separation: every request is scoped to one Business; worker, lead and tracking links are long random tokens that expose only what that person needs.
- Data minimization: live location is collected only while a task is On the way and is discarded after arrival; signatures are stored as drawings, not device data.
- Resilience: automated encrypted backups, tested restores, and monitoring with alerts.
- Secure development: code review, dependency updates, input validation (for example, uploaded photos must be real JPEGs), and separated environments.
- Incident response: a documented process, with notification as in section 7.
Questions about this page? Email legal@logistr.com. For help with your account, support@logistr.com.