How HallGuard processes sensitive documents and where data goes.

HallGuard is built around a process-and-delete model. We collect the minimum data needed to run hallucination and claim verification, retain raw documents briefly, and keep only the verification history needed for auditability and customer access.

Raw files

24 hours

Maximum retention before purge from temporary storage.

Encryption

TLS 1.3 / AES-256

In transit and at rest across our production stack.

What HallGuard collects

The platform stores only the data required to run verification, associate work to a tenant, and preserve audit evidence.

Document content uploaded for verification, stored temporarily while processing runs.
Filename hash, tenant ID, and user ID to tie each verification to the correct workspace.
Verification metadata such as status, confidence output, source attribution, and audit records.

Why HallGuard processes it

Every field in the workflow supports one job: generating verifiable claim-checking reports for legal and financial teams.

Document content is processed so HallGuard can extract claims, compare them against reference sources, and produce a structured verification report.

Tenant and user identifiers ensure results, billing controls, and audit events stay attached to the correct workspace.

Verification metadata is retained so customers can review prior outcomes, prove what happened, and demonstrate who accepted the DPA or initiated a verification.

Retention and controls

Process-and-delete is the default operating model.

Raw documents

Deleted from Cloudflare R2 within 24 hours of verification completion. HallGuard is process-and-delete by default.

Metadata retention

Verification metadata is retained by plan: 30-day history on Standard and 12-month history on Professional and Enterprise.

Encryption

TLS 1.3 protects data in transit. AES-256 encryption protects data at rest in Neon and Cloudflare R2.

Residency

HallGuard runs on a US-first infrastructure footprint today. EU data residency is targeted in Year 2.

Third-party services that receive data

These providers are used to deliver verification, storage, hosting, and billing.

Anthropic Claude API

Claim extraction and verification. Relevant document content is sent for model processing.

Cloudflare R2

Temporary document storage with a 24-hour lifecycle policy for raw files.

Neon PostgreSQL

Stores verification metadata, tenant configuration, and immutable audit logs.

Render

Runs HallGuard application servers and document processing workloads.

Polar.sh / Stripe

Handles billing and payment data only. No document content is sent to billing providers.

Questions about your data?

For security, privacy, or DPA questions, contact the HallGuard team directly.

aniketmandloi.dev@gmail.com

Summary commitments

HallGuard does not use billing providers for document processing.

Document handling is limited to verification workflows and the resulting reports.

Audit records are retained to prove who accepted terms and what processing activity occurred.

Data promise24h purge · TLS 1.3 · AES-256

Want to review the DPA before upgrading?

Professional and Enterprise workspaces must accept the DPA before their first protected upload.

Start with HallGuard