Skip to content

Documentation

What leaves your device

Source files stay local during Protect and Detect. Fingerprints, authorization and operational metadata still reach services.

Protect and Detect

Protect sends fingerprints, identity authorization and registration metadata. Images and video also produce a signed public capsule. Writing sends fingerprints rather than prose. Detect sends image fingerprints and, when available, visual descriptors for matching.

These measurements are not a copy of the source file, but they are not confidential or anonymous. They can reveal a match to known content, visual similarities and links between registrations. Do not treat similarity descriptors as a secrecy guarantee.

Public records and search results

Search results use an owner reference to group work from the same identity. That reduces direct identity exposure in the search response; it does not prevent correlation through public capsules, asset identifiers, public keys or other information.

Contacting an owner

The contact form encrypts your name, reply email, subject and message to the owner’s published key before delivery. The recipient can read your reply email and the other details you include.

Your email is also sent over HTTPS to the service to deliver a verification code, and temporarily held during that flow. Contact requires an available owner inbox and email delivery. It is not anonymous communication.

Other service traffic

Sign-in, payment, model downloads, human verification and operational monitoring involve network requests. Providers can process the information needed for those requests, such as network addresses and request timing. Local file processing does not hide all service activity.

← All documentation