Privacy

A plain-language account of the data SecondTrip handles.

This notice separates current behavior from planned controls so private-beta users can make an informed decision.

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 roles for counsel review

The product has been designed around a proposed model in which SecondTrip would manage the limited processing needed to provide and secure accounts, while a customer organization would direct the use of any customer or technician information and SecondTrip would process it on that organization’s instructions. The legal role for each data category, along with responsibility for lawful bases, notices, and instructions, remains pending qualified counsel and operator confirmation.

Data categories

Account details and contact-form submissions are real personal data. SecondTrip processes account details to provide and secure accounts, and sends contact details and messages through its email provider so the operator can respond.

  • Account data such as name, email, password hash, sessions, and membership.
  • Private-beta test imports. These must contain only fictional or properly anonymized data—not real customer, technician, employee, address, phone, email, free-text note, or other production personal data.
  • Derived callback candidates, signal evidence, scores, and human review decisions.
  • Operational records such as audit events, task status, request IDs, and hashed IP addresses.
  • Contact-form name, email, company, subject, and message. Contact messages are sent through the email provider and are not stored in the application database.

Why data is processed

SecondTrip uses data to authenticate users, isolate workspaces, import and validate job history, identify possible repeat visits with deterministic rules, show the supporting evidence, preserve review history, operate the service, prevent abuse, and respond to enquiries. Imported personal data is not pooled across organizations.

Service providers

SecondTrip currently relies on Neon, Render, Vercel, Cloudflare/R2, and Resend to provide database, API hosting, frontend hosting, DNS/object storage, and transactional email. See the draft provider list for purposes and configuration notes. Whether each provider has a particular legal role remains part of qualified review.

Security posture

Current controls include encrypted HTTPS connections, scoped production credentials, server-side sessions, CSRF protection, forced database row-level security for tenant tables, organization-scoped object keys, access controls, and append-only review and audit records where implemented. No internet service can promise absolute security.

Retention and deletion reality

The architecture defines retention periods for imported jobs, source files, raw rows, reviews, audit events, sessions, and operational jobs. However, scheduled retention purges, full organization deletion, user anonymisation, end-customer erasure tooling, and full organization exports are not yet implemented. Until those controls ship, requests are handled through the contact form and may require manual assessment.

SecondTrip does not describe these planned controls as available. Private-beta users must not upload real production personal data. This restriction remains until lawyer-reviewed privacy documentation is published, the required lifecycle controls are implemented, and SecondTrip explicitly lifts the restriction.

Cross-border processing

Infrastructure regions and support access may involve processing outside a user’s country. Exact regions and legal transfer terms depend on the production configuration and the applicable provider agreement. Production customer data remains prohibited until qualified review, confirmed transfer terms, and every product launch gate are complete; contacting SecondTrip does not lift that restriction.

Rights and requests

Account users and customer organizations may ask about access, correction, deletion, portability, or processing restrictions through the contact form. A final responsibility and assistance process for requests involving future production imports remains pending qualified counsel and operator confirmation.

Children

SecondTrip is a business operations product and is not directed to children. Users must not upload children’s personal data during the private beta. The fictional or properly anonymized test-data restriction applies without exception.

Changes and contact

This notice may change as the private beta and its controls mature. The date above will be updated when material wording changes. Privacy and data-rights questions use the contact form.

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