About LookRange
A private face-analysis product with a public method.
LookRange is built to separate visible facial structure from photo conditions, keep uncertainty readable, and show exactly where the current evidence stops.
Operator and responsibility
VSpark AI LLC operates LookRange.
The company is responsible for the product, its published methods, service boundaries, privacy explanations, and correction process. Names, credentials, affiliations, and endorsements appear only after they can be verified for publication.
Product, privacy, and evidence questions can be sent to support@lookrange.com.
Why the product exists
One photo should lead to a better question and a kinder reading.
Camera distance, angle, light, expression, crop, and image quality can all change the way one face appears. LookRange starts with those conditions, then uses additional controlled views to identify what appears more stable.
The intended benefit is practical: understand the image, decide whether a retake would help, and separate reversible presentation choices from relatively stable observations.
Read the LookRange methodEditorial standard
Claims are written to match the evidence that is actually available.
Every public page should distinguish product behavior, external research, internal interpretation, and future validation. Sources provide context; they are not treated as endorsements or as proof that LookRange is accurate.
Drafting may use software assistance, but the accountable internal team reviews claims, source fit, product status, safety language, and visible structured data before publication.
- Visible evidence. Important limitations and source links appear in the page, not only in metadata or internal documents.
- No invented authority. Names, credentials, testimonials, study results, and affiliations are published only when they can be verified.
- Material updates. A page date changes when its claims, evidence, product behavior, or user guidance changes materially.
Source and claim policy
The strength of the wording follows the strength of the record.
Product behavior is checked against the current implementation. Research claims should point to a direct paper, standard, or official technical document. Internal interpretation is labeled as interpretation, and an unfinished item stays unfinished.
Swipe sideways to view the full table.
| Evidence level | Allowed use | Required wording |
|---|---|---|
| Current product behavior | Explain a field, workflow, limit, or privacy boundary that exists now | Name the relevant Beta version or product state |
| Direct external source | Explain an underlying technical or research concept | Link the source and avoid treating it as an endorsement |
| Internal interpretation | Explain why LookRange uses a product or safety choice | Identify it as a design choice rather than settled science |
| Unfinished evidence | Describe the open question and present status | State only the completion, accuracy, fairness, or approval evidence that exists |
Current evidence status
The MVP is implemented; population validation remains open.
The current Beta can run one-photo Quick Scan and three-view LookRange locally on a supported device. Deterministic fixtures and browser tests verify the software contract and rejection paths.
Real-participant calibration has not started. The locked blind holdout and demographic fairness evaluation remain open, so the site makes no population accuracy or parity claim.
Swipe sideways to view the full table.
| Evidence layer | Current status | Public interpretation |
|---|---|---|
| Product workflow | Implemented in Beta | Supported browsers can run the documented local analysis flow. |
| Synthetic contract fixtures | Implemented | The frozen code produces the documented fields and bounded outputs. |
| Real-participant calibration | Not started | No population accuracy claim is supported. |
Corrections and accountability
Specific evidence questions receive a specific review path.
Send the page URL, disputed statement, and supporting source to support@lookrange.com. The team reviews whether the claim matches the source, the current product, and the published evidence status. Material corrections should update both visible content and any matching structured data.
Evidence and next reading
Read the records behind the product.
Review the method, privacy boundary, or paid-report contract directly.
Questions, answered plainly
Questions about accountability
Who operates LookRange?
VSpark AI LLC operates LookRange and is responsible for its product, privacy, evidence, and correction records.
How is LookRange content reviewed?
The LookRange Method & Safety Team checks product behavior, source fit, measurement language, and safety boundaries before publication. Public pages identify the internal review and provide a correction route.
How can I request a correction?
Email support@lookrange.com with the page URL, the statement in question, and the evidence you believe should be reviewed.