When a person asks for a copy of their data, one action gathers every record that names them across towing, shop, taxi, money, the yard, documents, GPS trails and messages. You get a JSON file that other software can read and a PDF that the person can read.
Before you start #
- You need the owner or manager role.
- Confirm who is asking before you send anything. Pop Dispatch finds the records; checking identity is your step.
Steps #
- Open Privacy, choose Person data and search for the person.
- Choose Open, then Export their data. The screen says how many records were found.
- Choose Download the JSON file and Download the PDF. Send both to the person in the way your policy sets.
- Open Request log. The export is there as a done request with today's date.
What the export holds #
- The person's own record, plus invoices, invoice lines, payments and tax lines for a customer.
- Jobs, stops, events, estimates, signatures, yard and lien records, appointments, inspections and vehicles.
- Messages, notifications, enquiries and consent records.
- For a driver or staff member: GPS points, trips, fuel, expenses, advances, pay runs, hours, documents and the audit entries that carry their user number.
- Taxi trips, standing bookings, receipts and verification codes for a customer or rider, found by phone number or email.
- Photos and files appear by name and size. The JSON lists the pictures by name; send the picture files from the job if the person asks for them.
- Passwords, login tokens and similar secrets are never included.
Technical details
POST /privacy/export with {"person_kind": "customer", "person_id": 12}; a taxi rider takes {"person_kind": "rider", "contact": "name@example.com"}. The answer holds json, pdf_base64, total_records and counts per table. The PDF lists up to 150 records per table and says how many more are in the JSON file; GPS points are summarised by count and date range. The audit entry reads "exported the data held about a person" with the record number and the count.
If something goes wrong #
- "No such person" (404): the person was not found. For a rider, type the exact email or phone number used on the trip.