The mobile app is technician-only, and Pistonlog enforces the PII rule at the API layer for any caller in the Technician role — the strip is role-based, not platform-specific. The same data the mobile app sees is what a technician would see on the web jobcard view. The data isn't there to display, on either platform.
What's stripped
On the surfaces below, these fields are removed from the response before it leaves the server:
- Customer first name and last name
- Customer email and phone
- Customer address
- Customer notes (internal)
- Business account name and address (for business jobcards)
- Business account internal notes
Where the strip applies
The guarantee covers the places a technician actually works: the jobcard (list and detail), My Work, search results, and anything the AI assistant says back to them. Those are the surfaces the mobile app is built on, and they're stripped server-side, so even a future version of the app couldn't display what isn't in the payload.
It is not a blanket rule across every endpoint. A technician holds customers.view, so opening the customer records area directly still returns full customer details. If you need a role that genuinely never sees contact details, don't give it customers.view at all. Roles other than Technician (including Owner) bypass the strip everywhere.
What's visible
- Vehicle: registration, make/model, year, colour, fuel type, mileage, MOT due date
- Jobs: descriptions, labour, parts, statuses, your assignments
- Inspections: full template, full fill, photos, videos, signatures
- Messages: jobcard threads. These are internal team chats — they don't have a customer name to substitute. Mentions and posts from other team members show as normal
Dates that relate to the work itself (jobcard creation date, inspection completion date, work-completed date) are visible — only customer-side dates aren't relevant in the technician model since technicians work from assignments, not the calendar.
Why so strict
A workshop is a busy environment. Photos get taken of cars with screens visible behind them. Phones get left on benches. Customer PII on a mobile screen used in that environment is a leak risk. Stripping the data at the API means there's no copy to leak.
What this means for techs talking to customers
Technicians don't typically call customers in the Pistonlog model — that's reception's job. If a technician needs to ask the customer a question, they post on the jobcard message thread (which is internal — reception then relays to the customer through the appropriate channel).