Identity, not impersonation
Any system that renders a human face has to answer for misuse. LookingPro is built by people who spent their careers on the other side of that problem, in biometric verification and deepfake detection. This page separates what the product does today from what we are building, so that nothing here has to be taken on faith.
How a profile is tied to a person
Enrolment, the profile itself, the check before a call and the switch that starts the proxy. The check is in development and marked as such.
What is true in the preview today
Two kinds of statement, kept apart on purpose: what the software does when you run it, and what we have bound ourselves to as a company. Neither is a plan.
What the software does
- The proxy runs only while you switch it on, for a call you chose to join. Close the application and it stops.
- Your microphone is untouched. Your voice goes to the call as it always did, so the proxy cannot speak for you or answer in your place.
- The rendering runs on our servers. The application sends your camera input over an encrypted connection and receives the rendered image back. This is set out on Technology and in our Privacy Policy.
- There is no public download. Access is by enquiry and builds go to named people.
What we commit to
- Enrolment is first person and consented. We require video of you, recorded for that purpose. We do not build a profile from photographs, social media or third party footage. The automated check that the person in front of the camera is live and is you is in development, so today this is a rule we hold to rather than something the software enforces.
- One profile, one person. A profile represents the person who enrolled. We do not offer anyone else's face, public figures included, and we do not accept a request to build one.
- We do not sell personal data. What happens to the video you record, and for how long it is kept, is set out in the terms you accept in the application before enrolment.
What we are building next
Stated as work in progress, because that is what it is. None of the three is in the preview builds today, and we will say so on this page when that changes.
Biometric binding
We are building a check that runs before a session starts and while it continues, so that a profile will run only for the person it belongs to. Until it ships, what keeps a profile from being run by someone else is procedural: the preview is closed and builds go to named people.
Not in the preview builds.
Liveness and anti-spoof
That check will also have to resist the obvious attacks: a photograph, a screen, a recording played back to the camera. Distinguishing a live person from a replay is the discipline our founders come from, and it belongs in the product rather than around it.
Not in the preview builds.
Telling the other side
We intend to make it possible for the people in a call to know that a proxy is in use, rather than leaving it to be discovered. How that is signalled, in the picture or alongside it, is a design question we are working through with our first users.
Intended direction, not a shipped feature.
Why we work in this order
Rendering a convincing face is the part the industry already knows how to do. Keeping that face attached to the person it belongs to is the part that decides whether the technology is useful or corrosive, and it is the part our founders spent their careers on: they built and sold a biometrics and deepfake detection company before starting this one.
That is why the preview is closed, why enrolment needs you in front of the camera, and why identity binding is the next thing we ship rather than a feature we discuss later.
Reporting misuse
If you believe a LookingPro or LooperPro proxy is being used to impersonate someone, or that a profile was built from material the person did not provide, write to us and we will investigate.
Tell us what you saw, when, and where. We answer from the same address.