Data processing agreement

Production data remains prohibited while DPA review is incomplete.

SecondTrip does not publish a fabricated executed agreement. Private-beta organizations can start a scoped review through the contact form, but starting a review does not lift the data restriction.

Last updated

23 September 2026

Private-beta notice. Formal operator details are still being confirmed.

Document status

This page is AI-drafted and has not been reviewed by a lawyer. It is not final legal text or a representation that SecondTrip has completed every regulatory requirement.

Formal operator identity and contact details, governing jurisdiction, processing regions and international-transfer terms, and final retention and deletion obligations are still pending.

Proposed controller and processor model

The product has been designed around a proposed future model in which the customer organization would direct the use of customer and technician information and SecondTrip would process it to provide the import, callback-detection, evidence, and review workflow. The legal role for each data category remains pending qualified counsel and operator confirmation.

What the review covers

  • the categories of imported and derived data;
  • the processing purpose, duration, and documented instructions;
  • confidentiality and current technical controls;
  • the current subprocessor list;
  • assistance with rights requests, deletion, and incident response; and
  • deployment regions and transfer terms confirmed for the intended configuration.

Current security controls

The review can document HTTPS transport, server-side sessions, CSRF protection, scoped secrets, forced row-level security for tenant tables, tenant-scoped repositories, private object storage, access controls, and auditability. It must also record that automated organization deletion, user anonymisation, full exports, end-customer erasure, and scheduled retention purges are not yet complete.

Incident path

Suspected incidents should be reported through the contact form with “Security incident” in the subject. Do not include passwords, customer records, or other sensitive evidence in the initial message. SecondTrip will use the supplied reply address to coordinate containment and assessment.

How to request a DPA

Use the contact form with “DPA request” as the subject. Include the organization name, intended data categories, expected dataset size, and any required review deadline. The response will confirm what documentation is currently available and what must be resolved before production data can be accepted. Submitting a request does not authorize an organization to upload production data.

Start a DPA request
Next step: qualified counsel must approve final text and the product must implement every published promise before SecondTrip accepts real customer production data.