Subprocessors

Stripe

What it does: Processes subscription billing and payment for LastInspected accounts.

What it receives: The billing contact’s payment details and the identifiers needed to associate a subscription with your organisation (such as customer and subscription IDs). Stripe does not receive inspection records, photos, GPS coordinates, or any other operational data your organisation generates in the product — billing is entirely separate from the inspection data itself.

Resend

What it does: Delivers transactional email (account notifications, invites) and scheduled report emails your organisation sets up.

What it receives: The recipient’s email address and the content of the specific email being sent — which, for a scheduled report, means the inspection data that report is built from. Resend only ever sees the messages we ask it to deliver, addressed to recipients your organisation configured.

Dormant server-side error reporting

LastInspected also has a server-side error-reporting integration that speaks the GlitchTip/Sentry ingest protocol. It is currently not enabled becauseGLITCHTIP_DSN is unset, so it sends nothing today. If enabled, it would receive redacted error events from the server process: the event name, request id, tenant id, route, environment, release, and the other non-secret fields the logger already records. It never runs in the visitor’s browser; it is not a tracking script.

Where evidence photos and files actually live

Uploaded photos, signatures, and other inspection attachments are stored on our own infrastructure — a filesystem on servers we operate — not in a third-party cloud object store. There is no Amazon S3, Google Cloud Storage, or comparable subprocessor in this path, and none is planned; if that ever changed, this page would be updated first.

Questions

If you need more detail on any of the above for your own vendor review, contact [email protected]. See also our Privacy Policy and Terms of Service.