Question 1

Is my corporate document or data shared, stored, or processed on your servers?

Accepted Answer

No. Every document is analyzed directly inside the user's web browser using AI-powered local processing. No confidential files are uploaded, enabling privacy-first document verification while detecting document fraud in seconds.

Question 2

How does the Document Authenticator spot file anomalies and alterations client-side?

Accepted Answer

The Document Authenticator analyzes file formats directly inside the browser using HTML5 Canvas APIs and byte-level stream dissection. It reads the binary header, structure, and compression tables of uploaded PDFs and images. It looks for layered editing markers, mismatched JPEG quantization signatures, text position shifts, and local compression changes that indicate forged stamps or altered numbers.

Question 3

How does the Link Verifier analyze URLs and flag custom scam signals locally?

Accepted Answer

The Link Verifier runs local heuristics directly within your browser sandbox. When pasted message text is processed, the engine decomposes URLs to isolate top-level domains, checks for homograph attacks, evaluates domain registration age, and flags high-risk phishing keywords.

Question 4

How does the Audio & Video Forensic Shield analyze synthetic media on-device?

Accepted Answer

The Audio & Video engine uses the Web Audio API to process speech waves directly on your device. It extracts spectral attributes and checks for abnormal vocoder spikes, missing high-frequency harmonics, and robotic pitch changes. For video assets, the engine analyzes face boundaries and frame-by-frame color space shifts.