Privacy
How AutoScope handles inspection information
Effective 2026-09-02. This page describes the data paths implemented by the AutoScope platform.
Information collected
Booking data includes customer contact details, vehicle and listing information, seller contact, appointment preferences, location, package selection, notes, and agreement records. Technicians add checklist results, notes, photos, and report content.
How information is used
Information is used to schedule and perform the inspection, collect payment, assign staff, produce and deliver the report, address support or refund requests, and protect the service against misuse.
Payments
Card details are entered in Stripe Checkout and are not stored by AutoScope. AutoScope stores payment identifiers, payment state, amount, currency, and signed webhook event identifiers needed to reconcile the job.
Photos and reports
Inspection photos are stored in a private S3-compatible bucket. Short-lived signed URLs are created when authorized staff or a valid report link needs access. Completed reports are point-in-time snapshots with unguessable public tokens.
AI-assisted summary
The server may send vehicle basics and inspection findings to OpenAI to draft the customer summary. Customer email, phone, VIN, plate, and inspection photos are excluded from that request. The summary is reviewed as part of report completion.
Security and access
Staff routes require a valid role-bearing session and server-side authorization. Technicians can access assigned jobs; administrators and secretaries have operations access appropriate to their roles. Customer status and report links use separate opaque tokens. Keep those links private.
Retention and requests
Retention periods and a formal privacy-request contact must be set by the business before public launch. Contact details published on the Contact page should be used for access, correction, or deletion requests.