Trust, Security & Data Handling

How Logic Bunting handles your data

Private module workspaces require an authenticated Logic Bunting account. Access to paid modules is checked against the account's current entitlement, and protected data operations are enforced through application and backend authorization controls.

Different tools handle different kinds of information. Persistent operational records stay within authenticated application workflows, while EEI's selected 835, 837, 999, and 277CA conversion/reconciliation workflows process those claim files locally in the browser rather than uploading the file contents for that processing.

Authentication & access controls

• Private workspaces require sign-in.
• Paid module access is checked against server-authoritative plan/entitlement state.
• Session and entitlement state is revalidated without granting access from browser state alone.
• Sign-in includes failed-attempt protection and normal password-reset/account-recovery flows.

Logic Bunting does not rely on hiding buttons as its only access control.

Private documents & file handling

Where a module supports private PDF or document workflows, document actions are scoped to the authenticated workspace. View, Download, and Delete behaviors use protected application flows rather than exposing customer documents through the public Preview environment.

EEI healthcare transaction files are different: selected 835/837/999/277CA file contents are processed locally in the browser for the supported conversion, combining, reconciliation, and acknowledgment workflows. See the Privacy Policy for the detailed local-processing description.

HTTPS & device responsibility

Logic Bunting is served over HTTPS so traffic between your browser and Logic Bunting service endpoints is protected in transit. Your device, browser, original source files, exported reports, local/cloud-sync settings, and organizational storage remain under your or your organization's control.

We intentionally avoid making broader certification or encryption-at-rest claims on this page that have not been separately established and documented.

Tally & AI data handling

Tally appears in both AI-powered and deterministic/non-AI experiences. Opening a module does not, by itself, send application data to an AI provider.

When you intentionally use an AI-powered Tally feature, the information required for that requested feature may be sent to the configured AI provider to generate the response. The exact context depends on the feature. Tally Guide experiences that are labeled local/no-AI do not make an AI request or consume Tally credits.

Public Preview sites use synthetic data only

The PCI, SPI, PEI, PPI, CCI, and UI public Preview workspaces are isolated read-only demonstrations populated with fictional sample data.

• They do not read Production customer records.
• They do not write to the Production database.
• They do not access private customer storage.
• They do not call live Tally/AI or consume Tally credits.
• They do not interact with live billing or entitlement services.

Billing & payments

Subscription checkout and payment processing are handled through Stripe. Logic Bunting receives the account/billing information needed to manage subscriptions and entitlements, but does not receive full payment-card numbers or card security codes.

Paid access is based on verified billing state rather than a browser return from checkout.

Data deletion & retention

Where a module provides record or document deletion controls, those actions follow that module's implemented workflow. Some operational records may intentionally be protected from deletion when removing them would damage historical integrity—for example, payroll configuration already referenced by compensation history.

Canceling a subscription does not automatically delete account or billing records. For account-level deletion or retained-record questions, contact support.