Read me first.

PixelBlocker+ censors explicit content on your own screen, live. A neural detector watches your display on-device, finds skin, and paints a censor over it in real time. Nothing is recorded and nothing leaves your machine (chapter 09 covers exactly what does and does not cross the network).

• Sub is the main app. You run sessions on your own screen: solo with your own rules, or paired, where a dom sets them for you.
• Dom is the controller app. It pairs with one or more subs and configures their sessions remotely: targets, style, duration, lock level, toys, chastity.
• Broadcast (formerly the separate Creator app) censors a camera feed into a virtual webcam for platforms like Chaturbate and Fansly. It is a tab in the Sub app; Creator and Full Bundle licences include it.

You can use the Sub app entirely solo forever. Pairing is optional and always consent-gated: a dom can never start anything on your machine without you approving it first.

The Filter tab is where sessions are built. A status card sits at the top; below it, one row per kind of setting shows what it is set to now. Click a row to open its page, and the live preview shows what your censor will look like before you commit.

Pairing hands the controls to someone else. Your dom runs the Dom app; you exchange a short code once, and from then on they can propose sessions to you.

What a dom can do once you accept: set every session option, change them live mid-session, drive your toys, and hold chastity keys. What a dom can never do: see your screen, start anything without your consent, or remove your safety rails.

Almost everything on the Filter tab can be changed while a session is running: censor style, borders, text, targets, beat track, even the detection preset and monitors (those restart the pipeline for a second or two). Just click and it applies.

• Duration can always be extended. Shortening is only allowed on no-lock and soft-lock sessions, and never below 30 seconds.
• Lock level only goes up during a session. You can lock yourself harder mid-session; you cannot talk yourself back down.
• The challenge module is frozen once armed. Changing a bet mid-game would defeat the point.
• When a dom controls the session, your controls lock and theirs take over. You always keep END (subject to the lock level) and the toy RELEASE button.

PixelBlocker+ drives vibrators, strokers, and chastity hardware, all locally over Bluetooth. No phone tether and no cloud.

The CHASTITY tab runs long-term chastity locks: days, not hours. You set a minimum and maximum duration and the real unlock date is drawn somewhere between them, hidden from you. Lock yourself, or let a paired dom hold the key.

• Self-lock: build the lock yourself. Your cage combination goes into local escrow and is revealed back to you when the lock releases.
• Keyholder lock: a dom proposes the lock and you get a full-disclosure consent dialog: the duration window, what they can do, and what they can never do. They can add time, freeze, and run games; the ceiling you agreed to always wins.
• Games: dice, a wheel, tasks, random events, verification photos, and penalties, including one that adds time when the detector catches you peeking.

Your safety rails are wearer-held and a dom can never loosen them: the maximum date ceiling beats everything including freezes, desert always ends enforcement now (with a 7 day cooloff before the combination is revealed, and it goes on your record), and if your keyholder goes silent the lock auto-releases after the inactivity window you agreed to.

The STATS tab answers two questions in one scroll: how you are doing, and where you rank. Your own numbers come first (sessions, total time blocked, streak), then the boards.

• MOST TIME: doms ranked by total controlled time, in days. Weekly and lifetime views.
• MOST SUBS: doms by how many different subs they have run.
• MOST LOCKED: the chastity board. Total time doms have held subs locked.

Boards poll live every 20 seconds. Only your username and the aggregated numbers are ever on the board; nothing about what was on your screen.

The detector, the censor, and every frame of your screen stay on your device. Full stop. What does cross the network is small and boring:

• Session metadata between you and your dom: the timer, the censor style, targets. Settings, never pictures.
• Chastity verification photos go directly from your machine to your dom over the encrypted peer connection, are held in their app's memory only, and are dropped the moment they give a verdict. They never touch a server.
• Leaderboard numbers: your username and durations, nothing else.

The consent model in one line: nothing starts without your explicit yes, every lock has a wearer-held escape (desert, hardware release, the ceiling), and a vanished dom can never strand you.

• Nothing gets censored / detector sees nothing. Screen permission is missing or was granted to an old build. On macOS remove PixelBlocker+ from Screen Recording in System Settings entirely (the minus button, not the toggle), then relaunch and re-grant.
• "Signed in on another device." Your username is connected elsewhere. Hit Reconnect to reclaim it here; the other device yields.
• Pairing code will not take. Codes expire after 10 minutes; generate a fresh one. If you sit on "pending", your dom is offline. The request waits for them and times out on its own.
• The censor lags or flickers. Drop one preset tier. The benchmark's suggestion is the safe ceiling for your machine.
• Licence key not found. Check the purchase email for typos and keep the dashes. Still stuck? The Discord is the fastest support channel, or email support@pixelblockerplus.com.

The in-app Guide (under Settings) has more, with live search. The website FAQ covers accounts, billing, and privacy questions.