Manual for Keyholders
As a keyholder you are assigned to one or more subs and control their directives, inspections, and consequences. Your access is clearly scoped to the data, photos, and notifications of your assigned subs. This section explains the directives available to you. If you are also an in-app admin, the user-management rights from the admin section are added on top.
Keyholder overview
After login you land on the keyholder overview with one tile per assigned sub. Each tile shows the current status, active directives, and quick actions.
From here you open a sub's detail view or trigger common actions directly. If you keep several subs, this lets you stay on top of things without switching into each profile individually.
Request inspections
An inspection asks the sub to photograph a handwritten five-digit code within a deadline. Only one inspection can be active per sub at a time — this overlap protection prevents duplicate requests from a human, the AI, and automation.
Optionally you enable a two-stage escalation (off by default): first a reminder, then an automatic mark as "not fulfilled" via a system entry that lands in the offence record. If an uploaded photo is not confirmed, you see the reason, such as a missing code or a wrong seal number.
Automatic inspections
Instead of triggering every inspection by hand, you can enable automatic inspections. These are distributed randomly across the day, within a waking window you can configure.
This keeps inspections unpredictable without waking the sub at night. The overlap protection applies here too: an automatic inspection will not start while one is already open.
Lock periods and lock requirements
With a lock requirement you set a minimum wear time, a mandatory device, and the "cleaning permitted" flag. The sub then sees a countdown until the earliest possible opening.
If a mandatory device is set, wearing a different device is detected. Hard, system-side enforcement of a wrong device is an admin function (see the admin section); as a plain keyholder you specify the device as a requirement.
Scheduled directives
You can schedule directives with a delay or for a fixed point in time. Until it triggers, a scheduled directive stays invisible to the sub so they cannot anticipate it.
As long as it has not fired yet, you can cancel a scheduled directive in advance. This suits surprise locks or staggered directives spread across several days.
Orgasm requirements and training goals
An orgasm requirement defines a time window, optionally a mandatory type, and whether an opening is permitted for it. The sub fulfils it by logging a matching entry within the window.
With training goals you set a minimum wear time per day, week, or month. The sub sees their progress in the statistics, and you can tell early if they are falling behind the target.
Keep the offence record
Offences — whether logged by you or generated automatically by missed inspections — land in the offence record. Through the judgement loop you assess an entry and set the consequence.
The sub can view their own offence record, so directives and consequences stay transparent for both sides.
Manage and personalise subs
You can set a sub's account language — useful when a sub receives German mail but prefers English; the language controls both the interface and notifications. Per user you adjust the selection lists, such as the orgasm types or the opening reasons.
The start page after login is configurable. If you are a pure keyholder without your own chastity practice, use the "no own tracker" mode to hide your own green tracker.
Advanced options
Two functions are opt-in: via MCP you can integrate an AI keyholder as a virtual keyholder that acts by your rules. With the Heimdall hardware key box you enforce a lock period physically instead of only agreeing to it digitally.
Both functions are off by default and enabled deliberately. Broader rights such as user management require the admin role — described in the admin section.