Skip to content
Ledgerline Help

Data residency and retention

Updated 26 August 20263 min read

On this page

Where your data is stored, and for how long, matters for regulation and for contracts. Ledgerline lets you pick a region when you create your organization and keeps each kind of data for a fixed, documented period.

Regions

Region code Location Regional API host
us Virginia, United States https://api.ledgerline.dev/v1
eu Frankfurt, Germany https://eu.api.ledgerline.dev/v1
ap Singapore https://ap.api.ledgerline.dev/v1

Choose the region when you create the organization. Your ledgers, accounts, transactions, counterparties, verification documents, statements, webhook delivery logs and backups are stored in that region, and encrypted with keys that stay in it.

The default host https://api.ledgerline.dev/v1 accepts requests from anywhere and routes them to your home region. Requests are processed in the home region only, so using the default host never moves data. If you want to keep traffic inside a geography end to end, call the regional host for your region.

Note

Sandbox data is stored in the United States regardless of your live region. Do not put production personal data in the sandbox.

Changing region

The region cannot be changed from the dashboard. Moving an organization is a planned migration that needs the Scale plan and a support ticket. It takes about 2 weeks: we copy data to the new region, verify it, schedule a short write freeze and cut over. API keys, ledger ids and webhook endpoints stay the same, and statements for past periods move with the data.

If you think you will need another region later, create separate organizations per region from the start, each with its own ledgers, instead of migrating.

What leaves the region

A small amount of operational data is processed outside the home region:

  • Account identifiers and billing data used to issue invoices.
  • Aggregate, non-personal metrics used to run the service.
  • Sanctions screening requests, which include the counterparty name and country but no bank details.

Payments travel on the network of the rail you choose, which has its own location, regardless of where Ledgerline stores your data.

Retention periods

Data Retained for
Ledger entries, transactions and statements 7 years after the account is closed
Daily balance snapshots 7 years
Business verification documents (KYB) 7 years after the organization is closed
API request logs 30 days
Webhook events and delivery logs 30 days
Audit log 90 days on Starter, 400 days on Growth and Scale
Support tickets 2 years
Sandbox data Until you reset it or close the organization

Ledger data is kept for seven years to meet financial record-keeping rules, and Ledgerline cannot delete it earlier on request, even if you close your account. After the period, it is deleted from live systems within 30 days and from backups within 90.

Personal data

Counterparty names, addresses and bank details are personal data when they identify an individual. Ledgerline acts as a processor for it under the data processing agreement that is part of the customer agreement. You decide what you send us, so avoid putting more into free-text fields and metadata than you need. To remove a counterparty from active use, delete it: it stops appearing in lists and cannot be paid, while the payment history required for record-keeping is kept.

Backups and recovery

Databases are backed up continuously with point-in-time recovery for 35 days. Backups stay in the home region and are encrypted like the primary data. Recovery targets: data loss of at most 5 minutes (RPO) and service restoration within 4 hours (RTO). See Status and incidents for service commitments.