Right Lane Controller

Right Lane Controller

Privacy Policy

Effective date: October 12, 2026

Development draft. This policy describes the verified sandbox setup and intended initial production service. Production access is pending. Production data handling and contractual terms require verification before launch.

Scope and contact

Right Lane Controller is being developed for authorized accounting and operational review of QuickBooks Online records. The service contact is Right Lane Brands at keith@rightlanebrands.com. The responsible contracting legal entity will be identified in the applicable signed engagement agreement before production access.

Information processed

The service handles QuickBooks company identifiers, authorization tokens, and authorized business records. Those records may include balances, transactions, invoices, bills, journal entries, and reports, together with customer, vendor, or employee information contained in those records.

Operational records may include request outcomes, timestamps, and error details. Actual production permissions and available functions will be checked before production use.

Purpose of processing

Information is processed for authorized record retrieval and review, agreed reporting, connection maintenance, failure investigation, and service documentation. Any proposed use outside the agreed scope requires review and any necessary permission.

The initial service scope excludes publication of customer records and cross-client use of identifiable financial information. This policy grants no permission to train models on customer records. Third-party processing terms and settings require verification before production use.

Services involved

The verified sandbox uses Intuit and QuickBooks Online as the source of records, Render to host the connection, and Tasklet for authorized requests and retained work. GitHub stores deployment code. Credentials and customer financial records are outside the intended repository scope.

Production providers, service locations, personnel access, and applicable processing terms remain under review. This policy makes no claim about unverified third-party training settings, certification, or processing locations.

Access controls

Sandbox checks confirmed rejection of missing and incorrect gateway tokens, restricted credential-file permissions, disabled accounting writes, and preservation of saved credentials through restart and redeployment.

These findings apply to the sandbox deployment. Production access controls must be separately verified before live customer records are connected.

Retention and deletion

The sandbox setup retains connection credentials and service evidence, including retrieved responses and checkpoint reports. Production retention periods for credentials, financial responses, reports, logs, and backups have yet to be finalized. No fixed retention period or deletion deadline is represented in this development policy.

Disconnection stops future retrieval when authorization is revoked. It does not automatically delete previously retained information. Access, correction, disconnection, and deletion requests may be sent to keith@rightlanebrands.com. Identity and authority may need verification. Requests are addressed under applicable requirements and the signed engagement agreement.

Changes and questions

This policy may be revised as development proceeds. Production arrangements and any required notices about material changes will be established before launch.

Contact: keith@rightlanebrands.com