Looking is part of the contract, especially NSFW. Ownedgaze puts that rule on Android: allowed content stays allowed, Soft or Hard gate when you want a cover, Soft/Hard minutes and evidence when something else slips through, and readable gaps when the ownership agent goes dark. Role-first Dom/sub for any genders. Invite-only closed beta.
Ready to make a screen part of the dynamic?
Request closed-beta accessPaired: a Dom owns a sub’s gaze. The Dom sets the allowlist and Soft/Hard gate, then reviews Soft/Hard minutes, evidence, and downtime.
Solo: a sub runs the same Soft/Hard gate on their own phone, with a practice library and a local Today view. You do not need a Dom to start.
The path we care about most is solo practice, then handing control to a Dom when you both want it. Same app either way.
Ownedgaze puts the gaze contract on the sub’s Android screen. The Dom (or the solo sub) decides what NSFW is allowed, typically Dom media when paired, and whether the cover is Off, Soft, or Hard. Soft covers Soft and Hard. Hard covers Hard only. When something else slips through, Soft/Hard minutes and evidence can surface. The sub knows the rule is live, and that tension is the product.
Your rules. Their screens.
Redeem a sub invite, grant screen capture, and run the NSFW gate on your own phone. Pick Off, Soft, or Hard. Upload a practice library. Open Today for Soft/Hard minutes, a score timeline, and evidence. Live with the cover when content trips the gate. Useful for self-discipline, and for learning the product before a Dom holds the keys.
When you pair later, control moves to the Dom. Your practice library and local day stay private on your phone. That handoff is the intended path, not an afterthought.
Upload what the sub is allowed to look at, usually the Dom’s own photos and clips. Ownedgaze learns that set so it can recognize it on the sub device. Everything else that reads as Soft or Hard can surface for Dom review. This is not a porn feed for other Doms, and strangers never browse your library.
Delete something when you want it gone from what is allowed. The line stays yours. Solo uses the same idea with a practice library before pairing.
Detection is not perfect. On Soft/Hard evidence, Dom and solo can label a frame Safe, Soft, or Hard. Safe clears similar screens for the gate. Soft and Hard tell us how the band should read for future models.
Optionally check Send this frame to Ownedgaze so we can use that image when we retrain. Default is off. Labels alone do not change the live gate on your phone; they feed the next detection pass.
Ownership covers more than what was watched. It also covers whether the agent was allowed to run. If the sub force-stops the app, revokes capture, or powers the phone off, the Dom can see when ownership went dark and for how long. What that gap means (a talk, a punishment, mercy) is yours to decide.
Airplane mode is a different signal. The phone can stay owned offline: activity queues on device and syncs when back online. That delay is not the same as killing the agent or shutting the phone down.
Gaps are for judgment. We don’t claim unbreakable control; see honest limits.
The dynamic is between the people in it. Monitoring summaries, evidence, and chat are built so operators are not meant to casually read intimate payloads. Day data is sealed for the Dom; chat is end-to-end between the pair. Treat the Dom invite code like a key to the dynamic. It is not a throwaway password.
Evidence and day summaries live in a 14-day window. Frames you choose to send for detection stay under that ops path, not a public gallery. Consent stays non-negotiable; see Consent, not spyware.
Invite-only, small cohort, English UI. We’re building this with Doms and subs who want screen ownership done properly, not a habit tracker with a collar sticker. Labels and optional frame sends are part of that: better detection comes from people who use the product. Feedback in-app. Request access: beta@ownedgaze.com.