Security & data
Where your data lives.
Site photos are project records and often personal information. Here is exactly how Wenvar handles them, including what we do not claim.
Hosted in Sydney
Wenvar’s database, photo storage and the application itself all run in the Sydney region. Your records are stored in Australia.
Captured in-app, measured at the shutter
Photos taken with the Wenvar camera have their time and GPS position measured at the moment the shutter fires, written into the record before anything could re-encode, forward or strip the file. That is a data-quality strength: the record is far less likely to be wrong than a photo pulled from a camera roll or a chat thread, where re-encoding and file-date fallbacks quietly corrupt the story.
Photos imported from elsewhere are accepted too, and the register labels every record’s provenance so an in-app capture and an import are never confused.
What leaves Australia
When a caption is suggested for a photo, a downsized copy of that photo and the project name are sent to our AI provider to draft the caption. Captions are suggestions: your team can edit or replace every one.
Two smaller lookups also cross the border: turning a photo’s coordinates into a street address uses a mapping service, and the register’s map view loads its background imagery in your browser from a map provider. The photos themselves stay in Sydney for both.
What we do not claim
Wenvar is a trustworthy site record, not a certified or forensic one. We do not claim compliance with a specific standard, and we do not claim a photo can never be altered after it is taken.
The stamp records what the device reported at the moment of capture. If a dispute ever turns on more than that, you will want more than any photo app can honestly promise, and we would rather say so here than in a dispute.
Access is invited, never open
There is no public sign-up. Every account is created by invitation, belongs to one person, and holds only the projects that person was added to. Offboarding is immediate: remove someone from a project and their access ends, while their records stay attributed to them.
Access is enforced in the database
Who can see what is decided in the database itself, not just hidden in the interface. A person who is not on a project sees “not found”, never a hint that the project exists.
Links that expire
Images are served through the app’s own authenticated routes rather than long-lived shareable links. Downloading an original mints a 60-second link at the moment of the click. Emailed links do exactly two things, invite and password reset; there is no magic-link sign-in.
Capture facts are locked
A record’s time, position and source are locked the moment it is filed and cannot be edited afterwards, by anyone. Captions and tags stay editable, because they are working notes; the capture facts are not.
Questions we welcome
If your project or company has specific requirements, security questionnaires included, get in touch and we will answer them directly, in writing.
Questions answered in writing.
Ask us anything about where your records would live. We reply in writing.