Data processing agreement

Last updated: 15 October 2026

This is a translation for convenience. If there is any difference, the Spanish version prevails.

The key points

  • Your customers', suppliers' and team's data belongs to your business: you decide.
  • We only process it to provide the service, following your instructions.
  • We don't sell it, there is no advertising and we don't use it for anything else.
  • You can take it with you whenever you like.
  • If you leave, it is deleted.
  • If you don't subscribe, it is kept in view-only mode and not deleted without telling you.

Data processing agreement under Article 28 of the General Data Protection Regulation (GDPR) and Spanish Organic Law 3/2018 (LOPDGDD). It is part of the terms of use and is accepted when a business is set up. If you need to sign it separately, write to us at hola@pathing.app.

1. The parties

2. Subject, nature, duration and purpose

The processor processes the data only to provide the business with the Pathing service: tracking its jobs step by step, its customers, suppliers and partners, its appointments and materials, and the notices the business decides to send. The processing consists of storing the data, consulting it, sending notices, printing and making backups. The agreement lasts as long as the business uses the service.

3. Data and data subjects

4. Processor's obligations

  1. Process the data only on the business's instructions, which are the way the business uses the app, including as regards transfers outside the European Economic Area (only those in section 5). If an instruction seems unlawful, the processor will say so. If a law required it to process the data differently, it will tell the business first, unless that law forbids it.
  2. Not use the data for anything other than the service, nor disclose it, except to the sub-processors in section 5 or where required by law.
  3. Make sure anyone accessing the data on its side is bound by confidentiality.
  4. Apply security measures appropriate to the risk (Article 32 GDPR), including:
    • encrypted connections (HTTPS), and the database and files hosted in the European Union;
    • each business isolated from the rest in the database, so no one from another business can read or change its data;
    • roles per business, and outside partners who only see the jobs sent to them, with the data the business chooses;
    • two-step verification, passkeys and confirming your identity again before sensitive actions;
    • an email to each person when their account is used from a new device, with a button to close all their sessions;
    • a log of who changed what; what enters the workflow is never deleted, only cancelled or archived;
    • daily encrypted database backups, kept for 90 days and tested every week to make sure they can be restored (photos and attachments have no separate backup).
  5. Help the business respond to people's rights (access, rectification, erasure, objection, restriction and portability), and pass on any request it receives directly.
  6. Notify the business without undue delay, and in any case within 48 hours at most of becoming aware, of any security breach affecting its data, with the information available so the business can report it if needed.
  7. Help the business, as far as it can, with impact assessments and consultations with the supervisory authority.
  8. Make available the information needed to show it complies with this agreement and allow reasonable audits requested by the business.

5. Sub-processors

The business authorises the use of these providers, which process the data only to provide the service and under the same obligations:

ProviderWhat forWhere
SupabaseDatabase, files and sign-inEuropean Union (Stockholm), with occasional support access from the United States and Singapore, under the same safeguards. Company in Singapore: standard contractual clauses
CloudflareHosting of the app and the Claude connectorGlobal network. US company: EU-US Data Privacy Framework
ResendSending the emails the business sends. It keeps a copy of each email for 30 daysSends from the European Union (Ireland), but the company is in the United States: EU-US Data Privacy Framework and standard contractual clauses
Google (Gmail)Support email: what the business sends to hola@pathing.app reaches the owner's emailUnited States: EU-US Data Privacy Framework
GitHubDaily database backup, stored encryptedUnited States: Data Privacy Framework

If one is added or changed, we will give at least 30 days' notice, and the business may object and leave at no cost. The processor imposes the same obligations as this agreement on each sub-processor and is liable to the business for what they do (Article 28(4) GDPR).

If someone in the business connects Claude to their account, Claude can read and change, at most, the same things as that person; it does not touch the account, the platform or who sees what. What Claude reads from Pathing reaches Anthropic (United States) under the terms of the Claude account being used. We recommend business accounts with a data processing agreement. Anthropic is not a sub-processor of Pathing: the business chooses it, and can turn it off in Settings (“Allow connecting Claude”, on by default). The same goes for WhatsApp: if the business sends a message from its own phone, that is the business's decision, and WhatsApp is not a sub-processor either (see the privacy policy).

6. When it ends

When the business leaves the service, it decides whether its data is returned (in an open format), handed over to another provider or deleted. The rule in the terms of use (“Leaving and switching provider”) applies, which complies with the EU Data Act (Regulation (EU) 2023/2854):

The processor may only keep, blocked, what is needed while liabilities may arise from its relationship with the business (Article 33 of Spanish Organic Law 3/2018).

7. What the business is responsible for

8. Liability

If the processor uses the data for anything else, discloses it or breaches this agreement, it will be considered the controller for that processing and will be liable for the infringements committed.

Otherwise, liability under this agreement has the same cap as the terms of use: what was paid in the previous 12 months. The cap does not apply to wilful misconduct or gross negligence, or to anything the law does not allow to be limited.