What an automatic inspection is
An inspection is a photo request the keyholder triggers to verify the state of the device. The Chastity Tracker offers two routes to one: the manual inspection, which the keyholder starts on the spot, and the automatic inspection, which the system distributes across the day on its own.
With the automatic variant, the keyholder sets a framework, not the individual moment. He decides how many inspections should happen per day, and the system rolls the exact times itself. Nobody sits at the other end typing out each request by hand.
The sleep window
Randomly spread across the day does not mean at any time. The keyholder defines a sleep window, a span in which no inspections fire. That way the next request doesn't land at three in the morning.
This isn't a side detail. It's the difference between a system that fits into daily life and one that sabotages it. Missing an inspection because you were exhausted teaches nothing but frustration. The sleep window keeps the dynamic where it belongs: in the waking, consensual part of the day.
Every inspection carries a code and a deadline
A triggered inspection is not a vague "send me a photo." It arrives with two fixed components:
- A code that must be visible in the photo. This prevents an old image from being recycled. The photo has to be taken in the moment of the request.
- A deadline by which the inspection must be fulfilled. If it expires, the inspection counts as missed.
Both values are locked in the moment the inspection appears. The sub knows exactly what to do and by when.
Why randomness lands differently
A manual inspection always carries a message: the keyholder just thought of you. That's lovely, but it's also predictable. You learn to read patterns and arrange yourself around them.
An automatic, randomly timed inspection escapes that calculation. The sub knows a request will come sometime today, but not when. That uncertainty shifts something subtle: attention stays present across the whole day, instead of only in the moments when a message is expected.
It's the difference between "I get checked when he has time" and "I am checkable in principle." For many couples, the latter is exactly the mental space they're after. And it relieves the keyholder of having to be constantly active without letting presence fade.
An honest framing
Automation sounds like control without participation. It isn't. The system generates requests, but it does not generate coercion. No software pushes anyone into something they didn't agree to beforehand.
The rules at work here are rules the couple set together. How many inspections, which sleep window, which deadlines, what happens on a missed inspection: all of that is negotiated before the first automatic request ever fires. The tracker simply carries out those agreements reliably.
For that reason, automatic inspections don't belong at the start of a dynamic but in a relationship where communication already holds. Talk about how the cadence feels. Adjust it. A good dynamic is one both people still want once the novelty has worn off.
Where your data lives
Run the Chastity Tracker as your own Docker container (self-hosting) and you keep full control over all data, including the inspection photos. Use the free portal and you run on trublue's server: a friendship service with no guarantees and no data control on your part. Both routes are permanently free. Which one fits depends on how much control over the infrastructure you want to hold yourselves.