/

How DocsLine Works

How DocsLine Works

Complete Transparency

Your Data Journey

Step 1

You Upload Invoice (PDF/Image)

Frontend (Hetzner - Nuremberg, Germany)

Step 2

File Stored Securely

Supabase Storage (Paris, France - AWS) Encrypted at rest (AES-256)

Step 3

OCR Processing

Our Backend (Hetzner - Nuremberg, Germany) Private OCR engine

Step 4

Data Extracted & Saved

Supabase Database (Paris, France - AWS) Encrypted, access-controlled

Step 5

You View Results

Frontend (Hetzner - Nuremberg, Germany)

Security at Every Step
TLS 1.3 encryption in transit
AES-256 encryption at rest
No third-party services
EU-only data storage
GDPR compliant by design

Our Infrastructure (as of 2026)

Supabase (EU Region)
  • PostgreSQL database
  • File storage (S3-compatible)
  • Location: West EU (Paris, France)
  • Infrastructure: AWS eu-west-3
Hetzner Cloud (Backend)
  • Datacenter: nbg1-dc3
  • Location: Nuremberg, Germany
  • Runs: Backend API, private OCR
Clerk
  • Authentication service
  • EU servers
Hetzner Cloud (Frontend)
  • Datacenter: nbg1-dc3
  • Location: Nuremberg, Germany
  • Runs: Next.js frontend
Privacy-First Processing

Our invoice processing uses a private OCR engine hosted on Hetzner Cloud (Nuremberg, Germany).

Your invoice data is NEVER sent to:

OpenAI (ChatGPT, GPT-4)Anthropic (Claude)Google GeminiAny third-party service

All OCR processing happens on our own servers in the EU. Your data stays in Germany.

Questions about our infrastructure?

Email: security@docsline.eu
How DocsLine Works | EU Infrastructure | Data Security | DocsLine