Privacy.

Foundation placeholder. Do not store real customer invoice data until Phase 3.5 P0 security gates are complete.

Ledgerly AR collects only the invoice data needed for polite reminder follow-up — payer contact details, invoice amounts, due dates, statuses, and reply threads. Data is scoped per workspace by row-level security, and every side effect produces an audit event.

We do not sell, share, or train AI models on customer invoice data. Email is sent only from approved templates after explicit customer approval. Service-role secrets are never exposed to browser code.

On public marketing pages, Ledgerly may use third-party website visitor tools, including Apollo, to understand which companies are interested in Ledgerly. These tools may process technical visitor signals such as IP address, domain, browser metadata, pages viewed, and timestamps. Ledgerly does not use this marketing-site tracking on signed-in app pages, admin pages, payment links, or customer invoice workflows.

Person-level visitor identification is not enabled by default. If Ledgerly enables it later, it will be limited to jurisdictions and consent or notice requirements that allow that use, and it will remain separate from customer invoice data.