How FilingLens handles your documents.

Uploaded documents

When you upload a document, it is stored temporarily on our server for the duration of your active session so that multiple analyses can be run without re-uploading. The file is permanently deleted when the session ends or when you begin a new analysis. Original filings are not archived in our database.

Processing

Extracted document text is sent to Anthropic's Claude API together with our analysis prompts to generate the output. Under Anthropic's API terms, inputs and outputs submitted via the API are not used to train their models. Anthropic may retain API data for up to 30 days for trust and safety review, which is standard practice across major LLM API providers.

What we store

We store the structured analysis output — the text FilingLens generates — when you choose to save it to your library. Saved analyses are scoped to your individual account and are not accessible to other users. FilingLens does not access the content of individual user analyses in the course of normal operations.

Your data rights

FilingLens is operated from Germany and processes personal data in accordance with the GDPR. You can request export or deletion of your account data at any time by emailing privacy@filinglens.io.

Hardened authentication and access controls.

Password security

Passwords are hashed with scrypt before storage. Plaintext passwords are never stored and are not written to application logs.

Rate limiting

Analysis routes are rate-limited per IP. Upload routes are independently capped. Compare and waitlist endpoints have additional per-IP limits. These limits protect against abuse and API drain.

Input sanitisation

Only PDF uploads are accepted, with PDF magic-byte verification, up to 25 MB per file (six files per batch). Filenames are sanitised server-side. Ticker symbols are validated against an alphanumeric-and-hyphen pattern (max 10 characters) before processing. Malformed inputs are rejected before reaching the analysis engine.

Authenticated access

Upload, analysis, library, and billing actions require a signed-in session. State-changing JSON endpoints use login protection and server-side validation before work is performed.

Payments handled by Stripe.

FilingLens does not store, process, or log your payment card details. All billing is handled exclusively by Stripe, a PCI DSS Level 1 certified payment processor used by millions of businesses globally.

Subscription plan changes are applied from verified Stripe webhook events. Visiting the checkout success page alone does not upgrade your account.

Stripe Payments Webhook Signature Verified No Card Data Stored

Infrastructure and transmission.

HTTPS / TLS

FilingLens is served at https://filinglens.io. Traffic between your browser and the application is encrypted in transit via HTTPS.

Database

User accounts and saved analyses are stored in PostgreSQL on Render. Database connection strings and credentials are loaded from environment variables, not hardcoded in source or committed to version control.

Environment isolation

API keys, database credentials, Stripe secrets, and webhook signing secrets are stored as server-side environment variables only. They are not exposed to the client and are not committed to version control.

Questions about security?

If you have specific security questions, compliance requirements, or responsible disclosure to report, contact us directly.

support@filinglens.io