LedgerGuard uses a small set of subprocessors to run core infrastructure, billing, monitoring, and optional document-processing capabilities.
These providers may process or store data to deliver the service. Features marked optional are used only when enabled in deployment configuration.
| Vendor | Purpose | Data categories | When used | Region / notes |
|---|---|---|---|---|
| Supabase | Database, authentication, and object storage | User identity; Tenant metadata; Document files and extracted records | Always (core) | — |
| Stripe | Payment processing and subscription billing | Billing identifiers; Subscription and invoice state | When billing is enabled | — |
| Sentry | Error monitoring and tracing | Application error telemetry; Operational trace metadata | When SENTRY_DSN / NEXT_PUBLIC_SENTRY_DSN is configured | — |
| AWS Textract | OCR for document text extraction | Document images/PDF text content for OCR | When ENABLE_TEXTRACT=true | — |
| OpenAI | LLM-assisted structured extraction | Document-derived text and extraction prompts | When ENABLE_LLM=true | — |
| Redis hosting provider | Queue infrastructure for BullMQ jobs | Job payload metadata (org/document ids and processing pointers) | Always (core queue infrastructure) | Deployment-specific provider and region; add trust URL in your subprocessors addendum if required. |
| Hosting provider | Web, API, and worker runtime hosting | Runtime environment data; Operational logs and telemetry | Always (core runtime hosting) | Deployment-specific provider and region; add trust URL in your subprocessors addendum if required. |
We update this list when providers, processing categories, or deployment posture changes.
Questions about subprocessors or data handling can be sent to support. support@ledgerguard.io.