CodingBand

Privacy Policy

CodingBand Command Center · Last updated: April 23, 2026
This page describes how CodingBand Command Center — an internal tool of CodingBand LLC — handles data. It is not a consumer product and is not distributed outside CodingBand personnel.

1. Scope

CodingBand Command Center (the “Application”) is an internal operations tool used exclusively by authorized CodingBand LLC employees to aggregate information from third-party services (e-mail, Jira, QuickBooks Online) into private management reports.

The Application is not offered to, installed by, or usable by any third party. There is no public sign-up.

2. Data processed

The Application reads the following data, strictly for internal reporting:

No personal data of any external end-user is collected, stored, or processed.

3. Access and authorization

Access to the QuickBooks Online data is granted via Intuit’s OAuth 2.0 flow, authorized by the CodingBand LLC company owner. Authorization can be revoked at any time by the company owner from the QuickBooks admin panel.

4. Storage and transmission

All data is processed locally on authorized CodingBand devices. Transient data (e.g., OAuth refresh tokens, IMAP credentials) is stored on the device file system with operating-system level protection. No data is sent to any third-party server other than the original source provider (Google, Atlassian, Intuit) via their official APIs.

5. Sharing

Data processed by the Application is never shared with any third party, advertiser, analytics provider, or data broker. There is no telemetry, no usage tracking, and no remote logging.

6. Retention

Aggregate reports are held only as long as they remain useful for operational decisions. Source data retention follows the policy of the originating system (Google, Atlassian, Intuit).

7. Cookies and tracking

This page and the Application do not use cookies, pixels, fingerprinting, or any form of behavioral tracking. This policy page itself instructs browsers, search engines, and archival services not to index or cache it.

8. Security

Credentials are stored locally with restrictive file permissions. Communication with third-party APIs is encrypted via TLS. Access to authorized CodingBand devices is governed by CodingBand’s internal security policy.

9. Changes

If this policy is updated, the “Last updated” date above will change. Because the Application is internal-only, users are notified directly through internal channels.

10. Contact

Questions regarding this policy: legal@codingband.com.