Account identity research
Expand a reported identifier into relevant public context for a specialist investigation.
For child safety & platform integrity teams
More context behind a reported account.
Give specialist reviewers a clearer picture of the identity behind an account. Research connected aliases and available age evidence, with sources and uncertainty kept in view.
Specialist review brief Needs review
Reported account
Source connectionDirect link
@cedar_27Public profile
cedar.exampleLinked website
The website is linked directly in the profile.
Still to establish
2 open- Account ownership
- Unresolved
- Age evidence
- Unresolved
For specialist reviewDecisions stay with your team.
Built for the questions your team faces.
- Child safety operations
- Platform integrity
- Specialist investigations
Child safety
The report is one part of the picture.
Safety teams may need to understand who is behind an account and whether it connects to other relevant identities. Sixtyfour supports that research with source-cited findings, helping specialists distinguish known information from leads that need further review.
Evidence before conclusions
Clarity includes what the research cannot establish.
Identity research supports the team reviewing a case. Findings should preserve ambiguity, source gaps and possible false matches.
Content assessment, enforcement and escalation stay within your specialist safety process.
Documentation
How age evidence research works
Read the documented endpoint, its source-based approach and the fields returned for review.
Keep the subject, sources and uncertainty together.
Follow the reported identifier through the available sources and into specialist review.
01 Start from the account
Use the reported account’s identifier and the reliable context available to the investigating team.
- Subject @cedar_27 Known
- Starting point Public profile identifier Input
- Scope Identity context for specialist review Research
The existence of a report is not a finding. Keep the report and the identity research distinct.
02 Research connected aliases
Look for corroborating links across public profiles and records, while retaining the basis for each match.
- Public profile Links directly to cedar.example Found
- Second alias Same website appears in a biography Review
- Attribution Account ownership not yet established Unresolved
Shared details can support a lead, but an alias match alone does not establish the person behind it.
03 Review age evidence
Where appropriate, research available public age evidence and keep confidence and sources visible.
- Self-reported age Not corroborated by available sources Unverified
- Public records No reliable date of birth established Unresolved
- Reviewer action Use the platform’s established verification process Review
Research cannot establish an age for every subject. An unresolved result should not be treated as verified age.
In your workflow
Support the specialist behind the decision.
Alias and relationship research
Investigate possible connections between accounts, with the supporting details available for review.
Age evidence research
Use the documented age-verification endpoint to research a date of birth or grounded estimate, with evidence and confidence where available.
A little more context
Questions, answered.
Does this page describe harmful-content detection?
No. The workflow here is identity research: understanding account identifiers, possible aliases and available age evidence. It complements the specialist tools and processes your team uses for content review.
Can an age always be established?
No. The age-verification endpoint researches public evidence for a date of birth or grounded estimate. Availability varies, and unresolved or low-confidence results need an appropriate next step in your existing process.
Does an identity match trigger enforcement?
No. A possible match is research for specialist review. Your team assesses the sources, applies platform policy and decides on any further action.
