Not a statement of intent. A list of controls.
Most of the items below are enforced in the data layer, not in application code. The rule survives even if the application changes. Where it says "Cannot be turned off", there really is no switch.
Ten controls and where each one sits
A provider does not go live until licence, insurance and authorisation documents are verified.
The pre-flight check is enforced by a database trigger; the application cannot skip it.
When a document expires, the provider's listings and offers stop on their own.
A daily job scans documents; an expired record suspends the chain.
The full address is not shared until the provider accepts the booking.
Before acceptance only the approximate area is visible.
Media containing images of children is held in permanent quarantine.
No setting and no permission level can open it.
People are not identified by face or any other biometric data.
No such capability exists in the product.
A job cannot be closed without proof being uploaded.
An attempt to close without proof is rejected at the database level.
Money and audit records are added to, never edited.
A correction is made only by a reversing entry; the history always stays readable.
Sending the same request twice still produces a single record.
Every write request must carry a request key; one without it is rejected.
No step in the workflow can be skipped or reversed.
Valid transitions are declared in the database; an undeclared transition returns an error.
A page with no supply behind it is not opened to indexing.
In this environment the entire site is closed to indexing.
What it does, what it does not
AI is part of how this product describes itself, which makes stating its limits more necessary, not less.
Here is the actual work it does: turning the messy thing you described into a structured request a provider can read, and asking about whatever is missing. That alone makes most survey visits unnecessary.
- It does not diagnoseIt ranks possibilities from what you described and says when it is unsure. What the fault actually is gets decided by the tradesperson who sees it in person.
- It does not give a binding priceThe range shown is an estimate. The binding amount is in the offer the provider sends.
- It does not commit to an outcomeIt makes no promise about how the job will end; the promise comes from the party doing the work.
- It does not replace your decisionYou choose the provider; the system only shows which ones are eligible and why they are eligible.
- It does not close a job by itselfClosing happens with proof and with your acceptance.
Who sees what
A provider sees the minimum needed to do the job. This is not a privacy preference; it is how the system works.
- Category and job description
- Approximate area
- Requested time window
- Uploaded images (scanned for personal data)
- Full address
- Contact details
- Door and floor notes
- Payment card details
- National ID number
- The history of your other requests
- Biometric data
Think one of these controls is not working?
Writing a control is not the end of it; someone has to measure that it works. Every guard in this product came out of a mistake — none came out of a design document.