How BNI Ledger handles chapter, member, payer, and payment-related information.

BNI Ledger is a chapter operations and dues collection application for BNI-style networking groups. The service helps chapters manage dues, invoices, payment status, member records, speaker rotation, reporting, and chapter administration.

BNI Ledger is an independently created software application. It is not created by, endorsed by, sponsored by, approved by, or affiliated with Business Network International (BNI) or any BNI franchise, region, or chapter unless a written agreement says otherwise. References to BNI-style chapters are descriptive only. BNI and related names and marks are trademarks of their respective owners.

This policy applies to BNI Ledger websites, applications, dashboards, payment pages, payer portals, communications, and related services that link to this policy.

This policy does not apply to third-party websites or services that BNI Ledger does not control. For example, Stripe and Clerk may process information under their own privacy policies when they provide payment or authentication services.

Chapters may have their own privacy, dues, finance, or recordkeeping obligations. Chapter leaders are responsible for using BNI Ledger consistently with applicable chapter policies, laws, and member expectations.

BNI Ledger collects information that users provide directly, information supplied by chapter administrators or authorized payers, information generated through use of the service, and information received from service providers such as Stripe or Clerk.

BNI Ledger uses personal information and chapter data to provide, secure, support, and improve the service. This includes the following uses:

• Create, maintain, and secure user accounts.
• Set up chapters, members, roles, dues schedules, and chapter records.
• Generate invoices, payment links, receipts, exports, and payment-status views.
• Process card payments through Stripe and reconcile payment status in BNI Ledger.
• Support third-party payer workflows, including employer payment links and payer autopay preferences.
• Send operational emails such as invitations, invoices, reminders, confirmations, and support messages.
• Maintain speaker rotation and chapter administration workflows.
• Monitor, debug, protect, and improve the reliability and security of the service.
• Comply with legal, tax, accounting, payment-network, and dispute-resolution obligations.

Where privacy laws require a legal basis, BNI Ledger may rely on performance of a contract, legitimate interests, consent, compliance with legal obligations, or another lawful basis depending on the context.

BNI Ledger uses Stripe to support online card payments, Stripe Connect account setup, stored payment method workflows, and platform subscription billing. Stripe may collect and process payment information directly, including card details, authentication details, bank or account information, fraud signals, and transaction data.

BNI Ledger may store Stripe-generated identifiers and limited payment method metadata, such as Stripe customer IDs, payment intent IDs, payment method IDs, card brand, last four digits, expiration month/year, default-payment-method status, and transaction status. This information helps BNI Ledger show payment status, generate receipts, support refunds or disputes, and keep chapter records accurate.

Online card payers may be charged the invoice amount plus the applicable BNI Ledger transaction fee and Stripe processing fee shown during checkout. BNI Ledger does not store full card numbers or CVV codes on its servers.

BNI Ledger does not sell personal information. BNI Ledger may share information only as needed to operate the service, support chapters, comply with obligations, and protect users. Sharing may include:

• Chapter administrators and authorized users: chapter leaders may access member, payer, invoice, payment-status, speaker rotation, and reporting data needed to operate their chapter.
• Members and third-party payers: users may see invoices, payment links, receipts, payment status, and payer information relevant to their own authorized workflows.
• Service providers: vendors may process information to provide hosting, authentication, payments, email delivery, database infrastructure, file storage, monitoring, support, and security.
• Legal, compliance, and safety: information may be disclosed if required by law, subpoena, court order, payment-network rule, dispute process, or to protect rights, safety, security, or service integrity.
• Business transfers: information may be transferred as part of a merger, acquisition, financing, reorganization, or sale of assets, subject to appropriate confidentiality protections.

BNI Ledger may use cookies, local storage, and similar technologies for essential site functions such as authentication, session management, security, payment flow reliability, preference storage, and diagnostics.

The cookie banner lets visitors accept all cookies, continue with essential cookies only, or customize optional analytics and marketing preferences. BNI Ledger stores the selected preference in a consent cookie and local storage so the banner does not need to be shown on every page load.

BNI Ledger retains information for as long as reasonably needed to provide the service, maintain chapter records, comply with legal, tax, accounting, payment, audit, and dispute obligations, resolve issues, prevent fraud, and enforce agreements.

Chapter financial records, invoices, payment records, and receipts may need to be retained longer than ordinary account information because they support accounting, tax, audit, chargeback, and chapter recordkeeping needs.

Placeholder to verify before launch: final retention periods, backup retention, deletion workflow, and any chapter-specific export or deletion process.

BNI Ledger uses reasonable administrative, technical, and organizational safeguards designed to protect personal information and chapter records. These safeguards may include authentication controls, role-based access, encrypted transport, provider security controls, logging, and operational monitoring.

No online service can guarantee absolute security. Users should protect their account credentials, use secure devices, maintain access only for authorized chapter leaders, and report suspected unauthorized access promptly.

Depending on where a user lives, privacy laws may provide rights to request access, correction, deletion, portability, restriction, objection, withdrawal of consent, or information about how personal information is processed.

Users may also request that chapter administrators correct chapter-controlled records. Some records may need to be retained for legal, accounting, payment, tax, dispute, or security reasons even after an account is closed.

BNI Ledger will not discriminate against users for exercising applicable privacy rights. To submit a request, use the contact method listed below. Placeholder to verify before launch: final request intake email, identity verification process, response timelines, and any appeal process required by applicable law.

BNI Ledger is designed for business and chapter operations. It is not intended for children under 13, and BNI Ledger does not knowingly collect personal information from children under 13. If you believe a child has provided personal information, contact BNI Ledger so the information can be reviewed and deleted if required.

BNI Ledger may update this Privacy Policy from time to time. The updated version will be posted on this page with a revised effective date. If changes are material, BNI Ledger may provide additional notice through the application, email, or another appropriate channel.

For privacy questions, access or deletion requests, or concerns about how BNI Ledger handles information, contact BNI Ledger using the verified privacy contact listed below once available.