Privacy Policy

Kona Cash Pipeline · Effective 2026-06-23

1. Scope

This policy describes how the Kona Cash Pipeline (the "Application"), operated by Nickles Arcade LLC (the "Operator"), handles data. The Application is a private, single-tenant tool used only by the Operator. It has no external end users, no public sign-up, and no third-party sharing.

2. Data the Application accesses

The Application reads accounting reports from a single QuickBooks Online company owned and controlled by the Operator. Specifically, it reads:

• Balance Sheet (used to derive aggregate book cash on hand)
• Aged Payable Summary (used to derive non-advertising payables; the "Amazon Advertising" vendor is explicitly excluded to avoid double-counting against an authoritative ad-spend source)
• Aged Receivable Summary (used to derive expected inflows)
• Bank-account metadata (used to surface bank-feed staleness so the Operator knows the freshness of the cash position)

All access is read-only. The Application does not write to, modify, or delete any data in QuickBooks Online.

3. Data the Application does not access

• Customer payment instruments, card numbers, or bank account numbers.
• Personal identifiable information about the Operator's customers, employees, or vendors beyond what appears as a counterparty name in aggregated A/P or A/R totals (which is treated internally and not published).
• Payroll detail. Payroll is read from a separate provider (Gusto) under a separate OAuth scope and is summarized at the aggregate cash-outlay level only.
• Any QuickBooks Online company other than the Operator's.

4. How data is used

Data accessed by the Application is used solely to:

• Compute aggregate cash-on-hand, projected cash position, accrued advertising spend, and runway.
• Render a small set of rounded aggregate figures on an internal, access-controlled dashboard used only by the Operator's team.

No data is sold, rented, shared with third parties for marketing, or used for any purpose other than internal cash-position reporting.

5. Where data is stored

Data is stored locally on hardware controlled by the Operator, inside a single SQLite database that does not leave the Operator's network. The internal dashboard publishes only rounded aggregate figures behind an authentication gate. Raw accounting data, per-account balances, account or routing numbers, transaction-level detail, and the source database itself are never published to any public URL.

6. Third-party services

The Application relies on the following third-party services to perform its read-only function. Each service's own privacy practices apply to data the Application reads from that service:

• Intuit QuickBooks Online (Accounting API, scope com.intuit.quickbooks.accounting) — accounting reports.
• Gusto (payroll API) — aggregate payroll cash outlay.
• Shopify (Admin API, Shopify Payments) — aggregate payout balance and dates.
• Amazon Selling Partner API and Amazon Advertising API — disbursement and ad-spend totals.

The Application uses these APIs read-only and stores only the aggregate figures needed to compute the cash position.

7. Retention

Data accessed by the Application is retained locally for as long as the Operator finds it useful for internal reporting. The Operator may revoke the Application's OAuth access at any time inside QuickBooks Online; doing so stops further data collection. Locally stored historical snapshots may then be retained or deleted at the Operator's discretion.

8. Security

OAuth credentials (client secrets, refresh tokens) are stored only in the operating-system user-scope environment of the operator's machine and are never committed to source control or published to a public URL. Refresh tokens are rotated by Intuit on each grant; the Application persists the rotated value to the same user-scope environment.

9. Changes

This policy may be updated from time to time. The Operator will post any updated version at this URL.