> ## Documentation Index
> Fetch the complete documentation index at: https://docs.integrateledger.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Privacy policy

> How Ledger handles account, workspace, and billing information.

**Effective date: October 29, 2026**

Ledger provides a dashboard and API for configuring credit billing and tracking usage in separate sandbox and live environments. This policy explains how Ledger handles information when you visit our documentation or dashboard, sign in, connect a Stripe account, or use the API. Live payment setup requires a separate live Stripe connection and activation; new live charges remain subject to Ledger's deployment gate.

## Information Ledger receives

* **Account and sign-in information.** When you sign in with Google, Ledger requests OpenID Connect and email information. Ledger receives your email address, Google's confirmation that the email is verified, and a Google account identifier. Ledger uses the identifier to recognize your account on future sign-ins. Ledger does not request access to your Google Drive, contacts, calendar, or other Google content. If you use an existing password account, Ledger stores a password hash rather than your password.
* **Workspace and API information.** Ledger stores your workspace name, the catalog you configure, customer identifiers supplied through the API, subscription and credit records, usage events, and API-key hashes. Your organization chooses the customer identifiers it sends to Ledger; avoid putting sensitive personal information in those identifiers.
* **Stripe information.** If you connect a Stripe test or live account, Ledger receives the secret key and related webhook secret, Stripe account identifier, and billing events needed to run Checkout and update credit balances in the selected environment. Ledger encrypts stored Stripe secrets. Stripe-hosted Checkout handles payment-entry pages; Ledger does not collect full payment-card details through its dashboard.
* **Technical information.** The service and its hosting providers may process request metadata, such as IP address, browser details, timestamps, and error information, to deliver and protect the service. The dashboard uses cookies for sign-in sessions, OAuth flow integrity, and protection against cross-site request forgery.

## How Ledger uses information

Ledger uses this information to authenticate users, create and maintain workspaces, provide the dashboard and API, connect the Stripe accounts you choose, apply billing events, enforce credit balances, troubleshoot failures, and protect accounts and the service. Ledger uses Google sign-in information for account access and does not use it for advertising.

## Sharing and service providers

Ledger uses Google to authenticate users, Render to host the application and database, Mintlify to host documentation, and Stripe when an organization chooses to connect a test or live account. These providers process information needed to provide their services under their own terms and privacy practices. Ledger does not sell Google sign-in information. Ledger may disclose information when required by law or to protect the service and its users.

## Retention and deletion

Ledger retains account, workspace, billing, and usage records while needed to operate the service and for legitimate security, accounting, and legal purposes. OAuth sign-in attempts become invalid after a short period, and dashboard sessions expire. To request access to or deletion of your account information, contact Ledger at the address below. Some records may need to be retained for legal or security reasons, and deletion from backups may follow the backup lifecycle.

## Security

Ledger uses HTTPS for the hosted dashboard, HTTP-only session cookies, hashed passwords and API keys, and encryption for stored Stripe secrets. No system can guarantee absolute security. Protect your Google account, Ledger API keys, and Stripe keys, and contact Ledger if you suspect unauthorized access.

## Your choices

You can sign out of Ledger, disconnect a Google authorization from your Google Account settings, and request help with your Ledger account using the contact address below. Removing Ledger's Google authorization does not by itself delete information already stored in Ledger; contact Ledger to request deletion.

## Changes and contact

Ledger may update this policy as the service changes. This page shows the effective date of the current version. For privacy questions or requests, contact **[privacy@monetization.company](mailto:privacy@monetization.company)**. Ledger is operated by **The Monetization Company**.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.