A case beyond the individual report
Examine related accounts and activity across fraud, scam, coordinated-abuse and child-safety concerns. Retain the original reports so the wider investigation remains connected to what users and reviewers observed.
Investigate the networks harming your users.
Investigate coordinated abuse, fraud and child-safety concerns across accounts and services, with the context your safety team needs to respond.
Individual reports can hide a coordinated pattern.
A scam may use several accounts to reach users. An abusive group may move between services. Child-safety and violent-threat investigations can begin with a single report whose wider context is still unclear. Related material arrives at different times and in different queues.
Investigators need to understand which accounts and incidents belong together, examine the evidence behind those connections and preserve the original context. The resulting case must be useful to the internal team or authorised agency that receives it.
Across your platform’s safety priorities.
Coordinated abuse and harassment
Investigate related accounts targeting users or communities. Compare reported activity and relevant identifiers to assess the apparent coordination and retain the evidence behind it.
Fraud, scams and impersonation
Follow reported scam accounts, fraudulent offers or impersonation attempts beyond one report. Examine the related actors and sources so fraud and safety teams can assess the wider operation.
Child safety and exploitation
Develop reported grooming or exploitation concerns into an investigation with the original context preserved. Prepare reviewed findings for the people responsible for child safety and any authorised referral.
Extortion and threats of violence
Investigate sexual extortion, coercion or violent threats that may involve a network of accounts. Keep the chronology and supporting sources available as the team assesses the concern and prepares its response.
Example use case
Investigate a suspected sexual-extortion network.
Reports of threats against users may involve several accounts and services. Investigators need to establish whether the activity is connected, understand the immediate concern and decide whether an authorised agency referral is appropriate.
Illustrative example. Reports that belong together are linked; the rest stay in their queues.
Retain the reported threats
Bring the original reports and authorised account information into Vantage. Keep the context that prompted the concern, including what was reported and when.
Examine the apparent network
Compare the relevant accounts, identifiers and source material. Assess whether the similarities support a connection, and keep unanswered questions visible as the investigation develops.
Prepare a useful referral
Compile a reviewed record for authorised internal teams or an appropriate agency, with the supporting sources and a record of what was released.
What matters for
your team.
Review before attributing an actor
Inspect the material behind a proposed account relationship. Investigators assess what a connection supports and whether independent checks are needed.
Findings the receiving team can use
Prepare the relevant evidence and context for trust and safety, fraud operations or an authorised agency. A recipient should be able to examine the findings without reconstructing the original investigation.
Vantage
Develop a persistent investigation around reported accounts and activity, with the original material available as analysts examine the wider pattern.
Lighthouse
Keep watch across relevant actors and patterns while safety investigators focus on active cases, with every alert assessed by your team.
Putting Azonic
to work.
Can we start from reports already in our queues?
Yes. Vantage brings the relevant reports and authorised account information into one case and keeps each report’s context, so your investigators can work the related identifiers and sources together rather than one report at a time. How Vantage connects to your queues is agreed with each platform and set out in our agreement with them.
How do investigators check a proposed link between accounts?
Against the evidence behind it. The sources for each proposed link stay in the case, so your investigators can compare identifiers and activity in context, separate supported links from coincidence and record what still needs checking. Nothing is attributed to an actor until an investigator has reviewed it.
What does a referral outside the original safety team include?
A reviewed account of the relevant findings, with citations and any important uncertainty, prepared for a named recipient such as an internal team or an authorised agency. The case keeps the original reports, the supporting material and a record of what was released. Nothing leaves unreviewed.
How can an active investigation follow activity across services?
Vantage works across the external sources and internal records your organisation is authorised to use. While the case is open, Lighthouse keeps watch on the relevant actors and patterns, across categories such as adverts and offers, group activity, websites and the open web. Your team defines the watch rules, and we scope coverage with each platform.
How does this fit our existing trust and safety tools?
Vantage and Lighthouse connect two ways with your existing systems. Alerts can be delivered into your tools, and outcomes such as a takedown, block or referral can go back out. Your team decides every action. Which systems we connect is agreed with each platform and set out in our agreement with them.
Where does our data sit, and who can see it?
Vantage and Lighthouse run self-hosted in your infrastructure or in your own cloud environment. Access follows the roles your organisation sets. Hosting, region, retention, connected sources (including user data) and any access by Azonic are agreed with each platform and set out in our agreement with them.