Customer Documentation

Use ProofTrace before you trust.

ProofTrace helps you turn public-source signals into a clear review before you reply, meet, pay, share information or accept a new relationship. This guide explains what to search, how to read results, what is allowed and how teams can connect ProofTrace to their own workflows.

Start a trace Open API reference
01 Enter email, phone or username
02 Confirm permitted public-source use
03 Trace public signals only
04 Review summary and evidence
05 Monitor follow future changes
06 Integrate API or custom workflow

Overview

What ProofTrace does.

ProofTrace is a public-source review service. You provide one or more identifiers, such as an email address, username or phone number. ProofTrace checks public signals connected to those identifiers and presents a readable review so you can act with more context.

The goal is simple: reduce blind trust. ProofTrace does not replace human judgment, legal review or platform safety tools. It gives you structured public context before you make a decision.

Permitted Use

Use ProofTrace for clean public-source review.

Public sources only

ProofTrace is built for public web signals and visible public context, not private accounts or hidden communications.

Personal and business safety

Use it to add context before conversation, meeting, payment, onboarding, partnership or internal review.

No eligibility decisions

Do not use ProofTrace for employment, tenant, credit, insurance, benefits or other regulated eligibility decisions.

No invasive tracking

ProofTrace is not for private account access, live location tracking, facial recognition decisioning or stalking.

Start A Trace

One identifier is enough.

1

Choose what you know

Enter an email address, username, nickname or phone number. Add the clearest identifier first.

2

Confirm permitted use

Confirm that you are using ProofTrace for a permitted public-source review.

3

Run the review

ProofTrace starts the search and shows progress while public signals are collected and organized.

4

Read before acting

Review the summary, matched identifiers, public sources, confidence and next-step context.

Results

How to read a ProofTrace review.

A review is designed to be clear, not overwhelming. Look first at the summary, then check matched identifiers, public source count and confidence. Strong results should show consistent signals across multiple public references. Weak results mean there is not enough public context yet.

  • Matched identifiers show which email, phone or username signals were connected.
  • Public sources show how much visible context was found.
  • Confidence helps separate strong signal from weak or incomplete context.
  • Archive links help teams keep an approved review package when available.
Read results in this order:

1. Summary
2. Matched identifiers
3. Public source count
4. Confidence
5. Evidence archive
6. Human decision

Account

Your cabinet keeps review history organized.

Profile

See your account details and review access from the personal cabinet after login.

History

Return to recent reviews without repeating the same work when history is available for your account.

Cleanup

Clear saved search history when you no longer need it.

Deletion

Request account deletion and restore it during the recovery window when supported.

API

Use the API when ProofTrace should run inside your product.

Teams can use ProofTrace through the hosted interface or through API access. API users can create a public-source review, check its status and retrieve available report links for approved workflows. The live API reference is available at /docs, and the OpenAPI document is available at /openapi.json.

API access should follow the same permitted-use rules as the website. Every review must stay within public-source, consent-aware and legally appropriate boundaries. 

Typical API flow:

Create a review
Check status
Read summary
Retrieve report link
Store only what your policy allows

Integration

Connect ProofTrace to the systems your team already uses.

ProofTrace can fit into customer support, fraud review, onboarding, marketplace safety, investigations, trust-and-safety operations and internal case workflows. Use the standard API when your team can create reviews and read results directly. Request custom integration when ProofTrace should connect to your existing tools.

  • Standard API access for product and operations teams.
  • Custom API shapes for specific request and response formats.
  • Custom webhooks for status changes, completed reviews and report readiness.
  • Custom connectors for CRM, case systems, support desks, risk tools and internal dashboards.
  • Custom exports for approved reporting and data workflows.
Integration examples:

CRM note
Support ticket
Fraud review task
Onboarding check
Case-management record
Internal dashboard event

Monitoring

Monitor public signals, data changes and new activity.

Monitoring is for approved ongoing awareness after the first review. Add an authorized person, identifier or data set to a watchlist, then let ProofTrace watch permitted public-source signals for meaningful changes: new records, changed public details, fresh mentions, profile movement or activity that should return to a human review queue.

  • Online watchlists for permitted users, identifiers, entities or customer-owned data sets.
  • Notifications when public data is added, removed, changed or becomes newly visible.
  • Activity alerts for new public mentions, profile updates, source changes and review-relevant events.
  • Delivery through dashboard alerts, email notifications, webhooks or API polling.
  • Change history that shows what changed, when it changed and which public source produced the signal.
Monitoring flow:

Create an approved watchlist
Attach identifiers or data sets
Choose notification channels
Receive change or activity alerts
Review source-backed evidence
Keep only what your policy allows

Privacy And Safety

Boundaries protect the user and the ecosystem.

Consent notice

Review creation requires acknowledgement of permitted use and legal boundaries.

Public-source boundary

ProofTrace avoids private accounts, hidden communications and invasive surveillance behavior.

Purpose limitation

Use results only for the purpose that made the review appropriate in the first place.

Human responsibility

ProofTrace gives context. Final action remains a human responsibility.

FAQ

Common questions.

Question Answer
Can I start with only one identifier? Yes. One email, username or phone number is enough to begin.
Does ProofTrace access private accounts? No. ProofTrace is built around public-source review boundaries.
Can businesses integrate ProofTrace? Yes. Teams can use the API, request custom APIs, add webhooks or build custom integrations.
Can I use ProofTrace for employment or tenant screening? No. ProofTrace is not for regulated eligibility decisions.
Where is the API reference? The API reference is available at /docs, with OpenAPI JSON at /openapi.json.

Operating Principle

Use public context before you move.

ProofTrace exists to make the next action cleaner: reply with context, meet with awareness, pay with caution, share with judgment and integrate public-source review where trust decisions already happen.

Start a trace