Unlock Your Lock
Unlocking has two parts: the session must allow release, then you reveal your combination or send the physical device's unlock command. A finished countdown alone does not open a box or device.
When Unlocking Is Allowed
| Release route | What must happen |
|---|---|
| Timer lock | Time has expired, the minimum duration has passed, and any required task points, public votes, or extension conditions are satisfied. An ordinary freeze blocks timer-based release. |
| Card-game lock | Complete the required green-card release flow. The displayed time estimate reaching zero is not enough. |
| Maximum duration | The separately configured hard maximum is reached. This applies to timer and card-game locks, including while frozen. |
| Keyholder release | Your keyholder explicitly releases the session. |
| Permanent emergency or safety release | Complete an available permanent emergency-release or safety-release flow. Soft emergency release provides temporary access without ending the session. |
Task-point and public-vote requirements gate ordinary timer-based release. They do not add those requirements to the green-card release flow or override the hard maximum. Some sessions can also require pending device commands to be completed before ordinary release.
See Public Voting for vote requirements, repeat-vote cooldowns, and closing or disabling a voting round.
If Blind Unlock Gamble is active, use its attempt flow; natural timer expiry alone does not reveal the combination. The app shows the available action and any attempt limit. See Card Game for green-card rules.
Minimum Time Enforced
Minimum time enforced is the notice shown before joining a shared timer lock whose creator has set Minimum time locked. The same minimum-duration setting is available when creating a self-lock.
It sets the earliest release date that ordinary timer reductions can reach, measured from the start of your own lock session. Time removed by games, rewards, bots, or your keyholder cannot move the timer's release date before that point.
For example, if your session starts on Monday at 18:00 with a 7-day minimum, the earliest ordinary timer release is the following Monday at 18:00. If the session initially lasts 10 days and a reward removes 5 days, the reduction stops at the 7-day minimum. The displayed 7 days is the total minimum from the start, not seven extra days or a countdown of what remains.
Setting and Changing the Minimum
- Configure Minimum time locked before starting a timer lock or publishing a shared template. Set it to zero to disable it.
- The minimum cannot exceed the starting duration or an enabled maximum duration. A random starting duration's minimum only controls the initial draw; it does not replace Minimum time locked.
- Once a session starts, its enforced minimum cannot be changed. Editing a shared template affects future starts, not existing sessions.
- This setting does not apply to card-game locks, which use their green-card release rules.
What Happens When the Minimum Passes?
Passing the minimum does not automatically release you. Added time, an ordinary freeze, required task points, votes, or other configured unlock conditions can still keep the session active.
The minimum does not disable an available emergency release, an explicit keyholder release, or the maximum-time safety limit. Removing time as a keyholder is different from explicitly releasing the session: time removal respects the minimum, while an explicit release can end the session early. Emergency release must still be available under that lock's settings.
After release becomes available, follow the unlock steps below to retrieve your combination or open your connected device.
How to Unlock
For a combination photo or generated code:
- Open your lock from the dashboard.
- Choose Reveal Combination when it becomes available and confirm if prompted.
- Wait for the photo or digits to load successfully. A successful reveal finalizes a session that was ready to unlock.
- Use the displayed combination to open the physical box. Keep the combination available until you have opened it.
For a connected-device lock, choose Unlock Device, then use Unlock in the device controls. Keep the device nearby, follow any connection prompts, and check that it actually opens. A release status in Chastify is not confirmation of physical unlocking.
If a photo or code fails to load, keep the session and contact Support. If a device command fails, use Device Connection Troubleshooting. Do not delete the session to try to recover a missing combination.
Ready to Unlock
Ready to unlock means the current rules allow release. For ordinary timer expiry, the session may remain available until you reveal the combination or complete another supported ending action. This allows actions such as adding time to continue a session before it is finalized.
An explicit keyholder release, permanent emergency release, or hard maximum can end the session before you reveal anything. You still need to retrieve the combination or physically unlock the device. A soft emergency release keeps the session active instead.
When the session ends, Chastify closes its active lock-tracking period. Ending the digital session and opening the physical lock are separate steps.
Things to Keep in Mind
- Check Unlock blocked and its explanation if release is unavailable. It may identify required votes or an extension condition. Status Overview keeps the timer visible alongside this notice for viewers allowed to see remaining time, including the keyholder. A zero countdown does not override the block. When time is hidden from the wearer, the countdown, initial duration, and progress percentage stay hidden.
- A hygienic unlock is a temporary break with a relock deadline; it does not end the session.
- A soft emergency release is temporary access without a re-lock deadline. Timers keep running by default; optional settings can pause the timer, require a re-lock photo and shared-keyholder approval, or add unlocked time multiplied by a configured amount. Cooldowns and randomized replenishment are optional too. Approval is off by default.
- Review emergency release and paid keys before starting. Their availability depends on your settings.
- Reveal and use the combination before archiving, deleting, or starting over.
Early Unlock Requests
Use the release options already available in the app first. Support can investigate a lock that is stuck because of a bug or misconfiguration; contacting support does not itself release a session.
Self Locks
Open Emergency Release to see the enabled options. Choose soft release for temporary access and re-locking, or permanent release to end the session. The paid-key flow provides a permanent release only when available for the session. If a configuration error prevents completion and no available flow resolves it, contact Support with the lock details and the message shown. Preserve the session so the problem can be investigated.
Keyholder Locks
Ask your keyholder to release you when appropriate. Chastify also has an inactive-keyholder safety release based on the keyholder's recorded activity.
Before a session, the wearer can set Inactive keyholder safety release delay in settings to 7–14 days, with 7 days as the default. It cannot be changed while a lock is active. Use the displayed countdown and next-check information; a lack of chat replies alone is not the inactivity test.
When the inactive-keyholder decision becomes available, choose:
- End session safely: end the digital session, then reveal your combination or unlock the device.
- Merge to self lock: keep the session running under your own control. This does not itself reveal the combination or open the device.
- Continue with inactive keyholder: keep the current session and keyholder. You can revisit the decision while the inactivity conditions still apply.
If an admin removes a keyholder, the app presents a separate decision with End session safely or Continue session. Continuing closes that particular admin-removal decision. Follow the options shown instead of assuming every account restriction provides the same release flow.
Removed Locks
Archiving and deleting are cleanup actions with different consequences:
- Wearer archives: enter the displayed confirmation code, which includes
REMOVEfollowed by four digits. Hardcore Mode prevents archiving an active lock. Archiving before release hides the combination from the wearer in archived history, and wearer archiving deletes the stored combination photo. - Keyholder archives: removes the lock from their active view and makes release available to the wearer if it was still active. The wearer must still retrieve the combination or unlock the device.
- Delete session: is available once the session's rules allow it to end or it has already ended. Deletion removes session data and stored combination photos. Read and complete the displayed confirmation.
Reveal the combination and open the box before removing a session. Archived history does not guarantee access to a code, and deleted combination photos cannot be recovered through the app.