Daily Verification
Daily Verification asks the wearer to submit a photo showing that they are still locked. It belongs to the lock session. It is separate from Task Photo Verification, identity verification and account badges, and the combination photo used to secure a lock.
Configure the Module
Open Daily Verification Setup during lock setup, or use the module's settings on an existing lock when editing is available. Review these choices before enabling it:
- Verification schedule: calendar days or rolling 24 hours.
- Approval Settings: keyholder review, community review, or automatic approval, depending on the lock type.
- Penalty Settings: consequences for a rejected photo or a missed submission window.
- Reminder Settings: whether to send a reminder, and how many hours before the deadline.
The wearer can edit Daily Verification on a self lock. Editing an active shared lock requires the current keyholder and Trust Keyholder permission. If settings are locked or saving is refused, check the session's permissions.
Once Daily Verification is enabled on a self lock, the wearer cannot turn it off through the module settings. Review the schedule, visibility, and consequences before enabling it.
Reminders can be set from 1–12 hours before the deadline. They are a notification aid; the displayed deadline still applies if a reminder is delayed, dismissed, or not received.
Understand the Schedule
| Schedule | When a photo is due | What a successful submission does |
|---|---|---|
| Calendar days (default) | Before midnight in the lock's stored verification timezone. | Records the submission for that local day. The next day has its own check. |
| Rolling 24 hours | Within 24 hours of the window starting. The first window starts when the session or rolling schedule is activated. | Starts a fresh 24-hour window from the accepted submission time. |
Follow Next verification due, Deadline, and Time left in the current verification screen. A rolling window is exactly 24 hours; calendar days follow local midnight and can differ around daylight-saving changes.
For example, a rolling photo accepted at 18:20 makes the next photo due at 18:20 the following day. Submitting another at 16:00 moves the next deadline to 16:00 the day after that. You do not need to wait for the previous photo's review: use Submit new verification when available.
A successfully submitted rolling photo starts the next window even while review is pending. Approval does not restart the timer. A later rejection can apply its configured consequences without removing the submission's timing credit.
Changing the Schedule
Switching to Rolling 24 hours grants a fresh 24-hour window. Switching back to Calendar days resumes checks at the next local midnight, with the first deadline at the following midnight. Ordinary settings saves, such as changing reminders, do not restart the rolling deadline. Earlier missed checks still count.
The setup screen shows the stored timezone. Shared-lock configuration uses the wearer's account timezone when available. After travelling or changing account settings, check the timezone and deadline shown by the lock.
Submit a Verification Photo
- Open Daily Verification for the correct active lock.
- Check the current deadline and wait for the verification code to load if you will upload a photo.
- Choose Capture or upload photo. Show clearly that the device is secured, following any instructions from your keyholder.
- Check the selected photo and choose Submit Verification.
- Wait for Verification submitted, then check the submission status and next deadline. Selecting a file or taking a photo alone does not submit it.
For gallery, file, pasted, or dropped images, make the displayed verification code physically visible in the photo. Do not use yesterday's code or an old photo with a digitally added code.
Supported native in-app camera captures can omit the code when the screen explicitly says it is not required. That exception does not apply to a photo taken elsewhere and later selected from the gallery. Reviewers can see the photo's source and, where available, its capture details; a camera label is not an approval.
The upload accepts JPEG, PNG, GIF, WebP, HEIC, and HEIF images up to 10 MB. If processing fails, try a smaller JPEG or PNG. Submit with time to spare: taking the photo before the deadline is not enough if the upload is accepted afterward.
Review and Approval
| Setting or status | What to expect |
|---|---|
| Keyholder Approval | The shared lock's keyholder reviews the submitted photo and can approve it or reject it with a reason. |
| Community Verification | Other eligible users vote on the photo. A decision is made after at least five votes and a majority for approval or rejection. |
| Auto-Accept All | On shared locks, this option approves routine daily submissions immediately. It still requires a photo submission. |
| Auto-approve after | A configured review timer can approve an undecided daily submission after the saved period. Check the configuration summary; pending review does not mean it will wait indefinitely. |
| Verification Pending | The submission was received and has not yet received a final decision. |
| Verification Rejected | Read the reason and any consequences. Rejection is different from missing the submission deadline. |
On self locks, Enable community verification controls community participation. Turning community review off does not remove the daily photo requirement; the saved automatic-approval settings still matter.
A shared keyholder can decide a community submission while it is still pending, ending the voting. Once a keyholder, community, or automatic decision is final, the normal approval buttons cannot reverse it.
In calendar mode, the submitted photo remains the day's entry and the normal screen shows the next day's availability. In rolling mode, Submit new verification creates another submission and window; it does not delete the previous result or its consequences.
Missed Windows and Consequences
Apply penalty when verification is rejected also applies to missed submission windows. The configured duration can be 15 minutes to 24 hours. For card-game locks, the red-card penalty checkbox controls whether this adds cards; leave it off to use the configured time penalty. The checkbox reflects the saved setting, including existing locks where it was off.
Send wearer to Pillory on rejection can also apply when a window is missed, subject to the lock's Pillory configuration. A time/card penalty and Pillory can both apply. Review the separate Pillory settings before enabling this consequence.
For rolling schedules, each elapsed 24-hour deadline can count as another missed window. A later upload starts a fresh interval but does not erase previous misses or penalties. If A verification window was missed appears, submit a new photo and check the updated deadline and lock history.
For calendar schedules, a photo submitted after midnight belongs to the new day; it cannot fill the previous day's missed check. The initial partial session day is not treated as a missed full day.
Routine daily verification stops being required when the module is disabled where permitted, the session ends, or the wearer leaves the session. Old submissions and decisions may remain in history.
Hygienic Breaks and Relock Photos
During a Hygienic Unlock, routine verification pauses. Completing the break creates a separate lock-up verification request due within 30 minutes when Daily Verification is enabled.
Open that request and choose Submit Lock-Up Verification. It must show that you have relocked. A new combination photo, generated combination, or device relock confirmation does not submit this proof photo.
- Calendar days: routine daily checks resume at midnight after the day you relock. A submitted post-hygiene photo also records a daily submission for the local day it was submitted. Use View post-hygiene photo to see its existing review result.
- Rolling 24 hours: relocking starts a new routine 24-hour window. Successfully submitting the post-hygiene photo starts that window again from the submission time, including while review is pending.
The 30-minute lock-up deadline is a separate obligation. Submitting an ordinary daily photo does not complete that request. Once its window expires, the lock-up request can no longer be submitted and the configured missed-verification consequences can apply.
Timing credit is not approval: a pending or rejected post-hygiene photo can still be recorded as the daily submission. Check its review result as well as the routine deadline.
History and Photo Privacy
Use View history or View verification history, then select Daily. Lock-Up shows post-hygiene checks and the initial lock-up photo when available. History shows submission/review times, results, reasons, and available community feedback. Rolling misses can appear as Missed entries; also check lock history and notifications for consequences.
The wearer and lock owner can access this verification history. Photos may become unavailable while review details remain. Final community decisions may retain a photo and voting audit temporarily when that feature is enabled; do not use verification history as permanent photo storage.
When community verification is enabled, other reviewers receive the photo and can receive the wearer's username and avatar, the lock title, and keyholder profile details. Do not rely on the setup's “anonymous” wording. Check the visibility setting before submitting and keep unrelated identifying details out of the image.
Photos are uploaded for review; they are not kept only on your device. Authorized administrators or designated audit reviewers may access retained community review records. A final decision removing a photo from the voting queue does not guarantee that every stored copy is immediately deleted.
If Something Goes Wrong
| Problem | What to do |
|---|---|
| The verification code will not load | Reload the verification screen before taking a gallery photo. Use the current code. |
| The schedule changed or the request expired | Refresh the lock and check its current deadline before preparing and submitting a new photo. |
| A native capture cannot be verified | Take a fresh in-app photo. If instructed, update the app or use a gallery photo with the code physically visible. |
| Upload failed or the photo is too large | Check the connection and try a smaller supported image. Confirm that submission succeeded before closing the screen. |
| A photo is pending while the next deadline approaches | In rolling mode, submit the next photo on time; waiting for review does not pause the next window. |
| Daily Verification says it is paused | Check for an active hygienic break or the calendar-mode relock-day exemption. Complete any separate lock-up request. |
| A history photo is unavailable | Check the recorded decision and reason. History can remain after the photo is no longer available. |
For unresolved problems, contact Support with the schedule type, displayed deadline, error, and whether the photo is submitted or still selected. Do not send your lock combination or combination photo.