DomBound

Control punishments: forced check-in and app restriction

The punishments that act on your use of the platform: how app restriction works, its two levels, and what stays available no matter what.

Reviewed on

Control punishments do not ask you to do something: they limit what you can do. They are the most intrusive in the catalogue, so it is worth understanding exactly how far they reach.

Forced check-in

Requires you to confirm where you are at a given moment, with a location check-in. What your Dom sees of that check-in depends on the visibility you have configured: only the category of the place, a map with no names, or the exact spot.

App restriction

Temporarily suspends your activity on the platform. It has two levels:

While it lasts you see the «Restricted access» screen with two pieces of information: the time remaining and the reason. Plus the «Talk to [Owner]» button, which is never removed.

What no punishment can touch

This is the hard limit of the design, and it does not depend on what you agree with anyone:

If someone presents a restriction as something that leaves you «unable to tell anyone», they are lying to you about how the platform works — and that, by itself, is grounds for a report.

Frequently asked questions

Can I be locked out of the app?

Total restriction limits your activity for the set period, but it always leaves a route open to your Owner with «Talk to…». It is not an expulsion or an account block.

Can I still ask for help while restricted?

Yes. Emergency and safety alerts are always sent, and the safety exits — emergency release, emergency block and reporting — cannot be disabled by a punishment.

Who can impose an app restriction?

It is a control punishment, and total restriction is a power of the Owner/Slave bond, included in DomBound+.

Can I see how long is left?

Yes. The restricted-access screen shows the time remaining and the reason.

Did not find your answer?

Write to us from Support inside the app, or to hola@dombound.com. We reply, and we add whatever is missing here.

Contact support

In this section