Why the guarantees belong in the database
Application checks answer "did we remember here". That question accumulates with every endpoint you add.
A photo uploaded from a gallery proves that a photo exists. Everything else about it is an assumption.
Draw documentation in home improvement is largely photographic. The industry treats a photograph as proof of work, and for most purposes that is a reasonable working assumption, because faking one is inconvenient rather than impossible.
Inconvenient is a weak security property. It holds until someone has a strong incentive, which is exactly the circumstance where the evidence matters.
Three properties, in increasing order of difficulty, and worth naming precisely rather than gesturing at:
The third requires a native mobile application and platform attestation services. It is a substantial piece of work, and any platform that has it will tell you specifically. Any platform that describes "secure photo capture" without distinguishing these levels is describing the first.
"Secure photo capture" is not a claim. Ask which of the three levels it means.
Renny does the first two today. The third is on our roadmap and needs a native application, and we would rather write that here than let a lender assume otherwise and find out during diligence.
Ask a vendor whether a contractor can upload a photograph from their camera roll. The answer tells you which level of evidence you are actually buying.
Pick a closed project. We will show you the document you would hand a regulator. If it does not answer the question, nothing else matters.