What the visible date stamp actually is
The stamp a timestamp camera app prints is text drawn on top of the image. It usually reads the time from the phone clock, which the user can change, so a photo taken today can carry yesterday's date simply by setting the clock back first. Once the stamp is in the picture, it is pixels like any other, and photo editors can add, move or rewrite that text after the fact.
So a stamped photo answers almost nothing on its own. The date can be set, the stamp can be edited, and nothing ties the file to the moment beyond a line of text that anyone could reproduce. It is a label, not a check.
What makes a photo hold when it is disputed
Proof needs a time the sender cannot set and a file that breaks if it is altered. Danaya seals a photo the instant it is captured: it computes a SHA-256 fingerprint of the file and binds it to a server timestamp, which comes from the server and not the phone clock, plus the GPS position. Capture is live only, so you cannot import an older or edited file, and anyone can confirm the result from a public verification link you send to the customer.
That is the difference from a stamp app. Where the app prints a date you could have set, a sealed capture fixes a time you could not, and where the stamp is text that can be rewritten, the fingerprint breaks the moment the file changes. If you already use a timestamp app and know its weak spot, this is the part it was missing.
Why the phone clock is the weak link
Every timestamp-camera app leans on the same foundation: the phone's own clock. That clock is a setting, not a fact. A user can open the date settings, move the phone to yesterday or last month, take the photo, and the stamp will read whatever was set, with nothing to flag that it was changed. It is the same reason a screenshot's time or a file's modified date proves nothing on its own.
This is not a flaw in any one app; it is where the whole approach sits. A time anyone can set is a time no one else should trust. What breaks the pattern is a clock the sender does not control, which is why a server timestamp bound to the file at capture is a different kind of claim from a date printed on the pixels.
What a timestamp camera photo actually proves
Be honest about the limit. A sealed capture proves when the file was captured and that it has not changed since, verifiable by anyone. It is not a qualified eIDAS timestamp, so it is strong verifiable evidence rather than a regulated legal timestamp, and the GPS position is declarative, read from the phone, exactly as in a stamp app.
It also does not vouch for the scene. Nothing stops someone from filming a staged situation, so a sealed capture proves when and what was captured, not that what you are looking at is the honest truth. That is why we are upfront that no seal is beyond faking. For the detail on why the hidden file metadata is no better, see our post on photo metadata, and for the legal tiers of timestamps, see what a trusted timestamp proves.