Driver App media contract
Driver App has separate flows for chat images, signatures, status photos, and received media. A visible control or preview does not confirm authorization, upload, storage, delivery, or proof.
Media paths
| Type | App boundary |
|---|---|
| Chat images | The photo library can provide a local image preview. Sending remains unavailable for integration use here; a cleared preview does not confirm upload or delivery. |
| Chat signatures | The canvas creates a local image candidate. It is not proof of identity, consent, or delivery, and sending remains unavailable here. |
| Documents | The current chat does not render a document action or include a selected document in its outgoing message. |
| Chat camera | Camera capture is unavailable in the current chat; a camera in another flow does not add it. |
| Status photos | Some configured statuses may require a camera capture before the status request. |
| Received media | A received image may appear in the app; continued access and retention depend on the storage provider. |
| PIN, location, and delivery proof | The presence of a media file does not validate the PIN, location, status, or delivery. |
Permissions and data
The operating system controls access to the camera, photo library, and location. App authorization, operating-system permission, and provider configuration are separate conditions. Do not share tokens, addresses, precise coordinates, media content, or order details outside authorized surfaces.
Image origin, network access, caching, storage lifecycle, and authorization can fail independently. If an image does not load, check connectivity and contact the project administrator or storage provider.
Related guides: Communication contract · Add and view chat media · Complete a delivery · Use force-status actions