Privacy

Who operates this

Ownedgaze is the product name for this service. For closed beta there is no separate company entity named on this page. Contact: beta@ownedgaze.com.

The service is hosted in the EU (currently an OVH VPS). We intend EU-oriented privacy expectations for beta.

What we process

• Account: username, display name, role (Dom/Sub), invite redemption records.
• Operational: last sync / health-style flags needed to run pairing and monitoring, Dom web library session records.
• Monitoring: day summaries and NSFW evidence packages stored as ciphertext sealed to the Dom. Operators are not meant to casually read plaintext frames or intimate breakdowns.
• Chat: end-to-end ciphertext between Dom and Sub. Operators cannot read message bodies by design.
• Allowlist library: Dom-uploaded images/videos (originals) so we can build fingerprint indexes for the paired Sub device.
• On the Sub device: screen capture, on-device classification, fingerprint matching, and a local encrypted queue before sync.

Dom allowlist media — stays on our servers

When a Dom uploads allowlist media, the original files stay on Ownedgaze servers for that Dom’s library and re-indexing. They are not redistributed to other Dommes, not published as a content platform, and the media contents themselves do not leave our servers to Sub phones or third parties for browsing.

Paired Sub devices receive a compact fingerprint / embedding pack derived from that media so matching can run on-device — not a copy of the originals. Delete an asset in the library when you want it gone from indexing; treat Dom uploads as high-sensitivity personal media.

Retention

• Evidence and summaries: about a 14-day sliding window.
• Chat ciphertext: kept until deleted (or the product later defines another purge) — not on the 14-day evidence window.
• Allowlist originals: until the Dom deletes them (no automatic 14-day purge in beta).
• Account / operational records: for as long as the account is active and needed to operate the beta.

Cookies and local storage

Browsing the public pages (home, About, Privacy, Terms) does not set cookies for normal use. We do not use advertising or analytics cookies in closed beta.

The Dom library browser link stores a scoped session token in the browser’s localStorage (sent as a Bearer token to the API) — not as a cookie. Django may set session or CSRF cookies for admin tools or future cookie-backed forms; if public pages start relying on cookies, we will update this section.

Consent and age

Ownedgaze is for adults (18+) in a consensual Dom/sub dynamic. The Sub must knowingly install the app and grant screen-capture permission. This is not designed as covert stalkerware.

How to stop

• Sub: uninstall the app and/or revoke screen-capture permission; ask the Dom to cancel the contract.
• Dom: cancel contracts, revoke linked library browsers in the app, delete allowlist assets, contact us to close an account.

Contact

Privacy questions or deletion requests during beta: beta@ownedgaze.com.