1. Marketplace Readiness Statement

LedgerPilot.com is owned and operated by LedgerPilot Inc., a Canadian company.
Multi-tenant SaaS with logical isolation by organization and client workspace.
Role-based access control enforced across APIs and administration workflows; mandatory MFA for administrators.
Production secrets managed in Azure Key Vault; configuration via Azure App Configuration; telemetry via Application Insights.
Public Privacy, Terms, and Service Level documents maintained on this site.
Usage-based credit billing with purchase and consumption history available to customers.
Audit-relevant events (approvals, postings, deletions, deliveries, token revocations) recorded in platform data.

2. Current Integrations

LedgerPilot currently integrates with the following providers as subprocessors under our Privacy & Data Protection Policy:

Microsoft Azure — hosting, storage, queues, document intelligence, OpenAI, Speech, SignalR.
Stripe — credit pack checkout, billing portal, and signed webhook events.
SendGrid — transactional email and invoice delivery.

Data exports (CSV, PDF) are provided for use with Excel, QuickBooks, Xero, and advisor workflows. These are file-based handoffs; no credentials to those systems are stored by LedgerPilot today.

3. Principles for Future Connectors and API Access

As direct connectors (accounting software, bank feeds, marketplaces) are introduced, the following principles apply:

Explicit consent: an organization administrator must authorize each connection, see the data scopes requested, and may revoke it at any time.
Least privilege: integrations receive only the scopes required for their stated purpose.
OAuth 2.0 / token-based access: no storage of third-party passwords; tokens are encrypted at rest and rotated or revoked per provider rules.
Tenant boundaries: connected data is bound to the authorizing organization and client workspace and never shared across tenants.
Transparency: active connections, granted scopes, and last-sync activity are visible to administrators.
Data minimization: we transmit only the fields needed for the integration to function.

4. Responsibilities of Third-Party Apps and Partners

Any third party that connects to LedgerPilot, whether as a connector, affiliate, or marketplace listing partner, must:

describe clearly what data it accesses and why;
use LedgerPilot data only for the purpose the customer authorized;
not sell, re-identify, or use customer financial data for advertising or model training;
maintain security controls appropriate to financial data, including encryption in transit and at rest;
notify us without undue delay (and no later than 72 hours) of any security incident affecting LedgerPilot customer data;
honour revocation immediately and delete customer data when authorization ends, except where retention is required by law;
comply with applicable privacy law (PIPEDA, GDPR, CCPA/CPRA) and marketplace policies.

5. Security Expectations for Integrations

TLS 1.2+ for all traffic; signed or authenticated webhooks (as currently enforced for Stripe).
Rate limits and abuse controls on inbound API traffic.
Logging of integration events for audit and incident response.
Vulnerability disclosure: report issues to support@ledgerpilot.com.
We may suspend any integration that presents security, legal, or operational risk.

6. Affiliate and Referral Program

Referral codes captured from links are used only to attribute sign-ups to partners. Affiliates receive aggregate referral counts, never customer financial data. Affiliates must represent LedgerPilot accurately and may not make guarantees about accounting, tax, or financial outcomes.

7. Marketplace Listing Transparency

Where LedgerPilot is listed on a commercial marketplace (for example, Microsoft commercial marketplace), listing descriptions, pricing, and support commitments will be consistent with this site. Marketplace-specific purchase terms, if any, are governed by the marketplace agreement in addition to our Terms.

Marketplace & Integration Compliance