⚖ Draft — describes current system behaviour, pending legal review.
Everything below was checked against the code, not written from a template. Where a protection is claimed here, it is implemented.
Email addresses and phone numbers are stored as SHA-256 hashes, not as text. Account identity is carried by a signed session cookie bound to whoever proved the address — a request cannot assert an identity by supplying a hash. Application logs are tested to ensure contact details do not appear in them.
Account type and display name; a hashed contact address; for service requests, the service address, trade, urgency and description; for dispatch, the work location and, where a job requires it, technician location while that job is active. Payment card details are never collected by this service — they go directly to the payment processor.
To dispatch work, to bill it, and to keep an audit record that can answer what happened on a job. Records are append-only, so a correction is added rather than a row rewritten.
A technician assigned to a job receives what the job requires: location, scope and contact routing. Client and technician identities are not sold, and are not shared beyond the parties to a contract and the payment processor.
Ask through your account and it will be answered against the audit record. What cannot be deleted without breaking the billing record will be said plainly rather than quietly refused.
← BackHome · Pricing · About · How it is built · Contact · Terms · Privacy · Sign up