Back to overview

Manual for Wearers

As a wearer (the "user" role) you document your lockup and work through the directives your keyholder sets. This section walks you through logging events, managing your devices, fulfilling inspections, reading your personal statistics, and installing the app on your phone. Every function is built to keep working offline and even when the optional AI is switched off.

Log a lockup or opening

Use the log button to create a new entry: choose whether it is a lockup or an opening, confirm the timestamp, select the device you are wearing, and optionally attach a photo and a note.

After a lockup the live wear timer starts automatically and counts up the running wear time. If a lock period is active, you also see a countdown of the remaining locked time. An opening ends the current session and writes its duration into your statistics.

Manage your devices

Under Devices you add your chastity belts — each with a name, description, photo, and an optional purchase price. You can keep several devices in parallel and pick the one being worn each time you log an event.

For every device the app keeps a wear statistic automatically and, if you entered a purchase price, the cost per hour worn. Over time this shows you which belt has "paid off" most for you.

Cleaning openings

If your keyholder permits cleaning, you can record a cleaning opening without breaking the running lock period. Cleaning is subject to a configurable daily limit, a maximum duration per opening and, where set, permitted times of day.

The cleaning time is treated as a break and subtracted from the pure wear duration instead of ending the session entirely. During the break the dashboard shows the remaining time and a button to lock up again. With automatic inspections switched on, the re-lock is followed by an inspection of its own accord — 15 to 45 minutes later, or after just 5 to 15 within the sleep window. Exceeding the limit or the maximum duration is noted accordingly.

Track additional categories

Beyond the chastity belt you can log additional categories such as plugs through separate wear sessions. Each category runs independently with its own timer and its own statistics.

This keeps your belt tracking cleanly separated from other worn toys, and you keep an overview of frequency and duration per category.

Log orgasms

In orgasm tracking you create an entry with a type and a sub-type — the two dropdowns depend on each other, so the second adapts to your first choice.

If your keyholder granted an orgasm window with a required type, pick the matching type when logging to fulfil the requirement. Your keyholder can customise these selection lists for you.

Fulfil inspection requests

When your keyholder requests an inspection, submit a photo within the given deadline. If it requires a code, write the five-digit number down by hand and photograph it alongside — this proves the photo is live and not pulled from your archive. You may read the code off a screen, for instance from the push notification on a smartwatch. Whether a device requires a code at all is your keyholder's decision; without one, the photo is enough. Inspections can also target a wear category such as plug or collar instead of the chastity device.

If the optional AI is active, it reads the handwritten code, recognises the seal number and checks which device is shown. If your inspection is not confirmed, you see the reason — a missing code, different digits recognised, or a wrong seal number — and can try again. With the AI off, your keyholder checks the photo by hand.

Follow lock periods and directives

Your keyholder's lock requirements can include a minimum wear time, a mandatory device, and whether cleaning is permitted. An active lock period always shows you a countdown until the earliest possible opening.

Scheduled directives only become visible to you when they trigger — before that you do not know they exist. Use orgasm windows within the given time frame and, if required, with the requested type.

Complete a task

The task card on the dashboard lists the conditions, the deadline and — as "Start by" — the point at which you must have got ready. Establish all conditions first; the card continuously shows what is still missing and what to do next. If that start-by time passes without them being in place, the task counts as missed.

With conditions that have to hold continuously, "Report as done" only appears once the holding period has elapsed; until then the same spot shows the remaining time. If the task requires a photo, upload it when reporting, and your keyholder will review and judge it. Completed, missed and withdrawn tasks are in the list below the card.

Inbox: read your messages

The bell in the app header opens your inbox and shows the number of unread messages — from a hundred onwards it reads "99+". You see the same counter as a badge on the app icon. The inbox holds penalty texts with their reasoning, your keyholder's comments on inspections, messages about requirements and lock periods, reminders, and automatic entries that concern you.

The inbox answers what was said to you; the dashboard banners answer what you have to do now — which is why the inbox deliberately has no countdown and no urgency. Messages that come from system texts appear in your account language, while anything your keyholder typed freely stays exactly as written. This matters most for the offence record: only your keyholder sees it, and without the inbox a missed mail would leave you unaware of what you were penalised for.

Code vault and image safe

Optionally you can store a sealed photo of your key-box code in the image safe. That image stays hidden from you as the wearer until the permitted opening or the end of the lock period is reached.

Your keyholder, by contrast, can see the stored image at any time. This lets you "lock yourself out" without keeping the code in your head or in plain sight — the feature is opt-in and off by default.

Personal statistics

The statistics area offers a calendar heatmap, a monthly overview, your progress against training goals, and usage per device. The heatmap shows at a glance on which days you wore.

The training-goal display compares your actual wear hours with the minimums your keyholder set per day, week, or month, so you can tell early whether you are on track.

Getting the app onto your phone

The tracker is a PWA — a website that behaves like an app once installed: its own icon on the home screen, full screen without a browser bar, works offline, and can send push notifications. No app store, no install package and no approval from Apple or Google is needed for it.

On iPhone and iPad, open your instance in Safari — the install works most reliably there. Tap the share icon, choose “Add to Home Screen” and confirm. On Android, open your instance in Chrome and choose “Install app” or “Add to home screen” from the three-dot menu; Chrome often suggests the install on its own through a banner. On a computer, Chrome and Edge show an install icon in the address bar.

Pay attention to which address you install: it has to be your own instance, for example yoursub.chastitytracker.ch, not the marketing website chastitytracker.ch. This is the most common mistake — installing the marketing site leaves you with the info page on your home screen and no access to your data. Your instance address is in your invitation or registration email and is the same one you use to sign in through the browser.

Besides the PWA there are native apps: the iOS app is in development and is not distributed through the App Store because of the adult-content rules, though a test build can be handed out via TestFlight; for Android there is an APK file on request. For everyday use the PWA is enough. If you would like one of the native builds, get in touch through the Feedback button in the header or footer of the website (type “Question”) or by email to info@trublue.ch — stating whether you need iOS or Android, and for iOS the email address for the TestFlight invitation.

Account, language, and notifications

In settings you choose your account language (German or English) — it controls both the interface and the wording of all notifications. Notifications can be toggled per event type and arrive as web push in the installed PWA; on iPhone and iPad, web push only works once the site has been installed via “Add to Home Screen”.

For login you can set up a passkey alongside your password (Face ID, Touch ID, fingerprint, or Windows Hello). You change your password and email yourself in self-service. The app is offline-first and installable, and you can review your own offence record at any time.