1. Scope and purpose
Olivier & Yola Finance Reader (the “App”) is a private, owner-operated tool used only by Olivier Corbeil and Yola van Leeuwenkamp to review and analyze their own authorized QuickBooks Online company data. It is not offered to the public and does not provide services to other QuickBooks customers.
The App's sole purpose is to retrieve financial information on demand and present it for personal reporting, reconciliation, budgeting, and financial analysis.
2. Information accessed
With the owners' explicit QuickBooks authorization, the App may read:
- company and accounting profile information;
- financial reports and chart-of-accounts data;
- transactions and transaction line details;
- customer and vendor names, without exposing contact details; and
- the QuickBooks company identifier needed to direct API requests.
The App does not request Intuit passwords, payment-card data, or the QuickBooks Payments scope. It is technically restricted to read requests and cannot create, edit, or delete QuickBooks records.
3. How information is used
Authorized data is used only to answer the owners' financial questions, produce requested summaries, and verify that the App is connected to the correct company. When an owner asks Codex to perform an analysis, the selected QuickBooks data needed for that request is provided to OpenAI's Codex service. Data is not used by the App for advertising, credit decisions, or any purpose unrelated to the owners' requested financial analysis.
One QuickBooks customer's information is never combined with, compared to, or shared with another customer's information. The App has only one private owner-managed connection.
4. Storage and security
This public website does not receive or store QuickBooks accounting data, Intuit credentials, access tokens, or refresh tokens. It also uses no advertising pixels, behavioural analytics, account system, or contact form.
The local App stores its client credentials, rotating refresh token, and QuickBooks company identifier in the owner's encrypted macOS Keychain. Short-lived access tokens are kept only in volatile memory. Requests to Intuit and transfers to the owner-authorized analysis service use encrypted HTTPS connections. The App does not maintain a remote database of QuickBooks data.
5. Sharing and service providers
QuickBooks data is not sold, rented, licensed, or disclosed to advertisers or unrelated third parties. Data is transmitted to Intuit as required for authorization and API responses and, when an owner requests analysis, to OpenAI as the owner-selected processing service. OpenAI's handling of that data is governed by the owners' applicable OpenAI account terms, settings, and privacy policy.
The public policy and connection pages are hosted on secure web infrastructure. That host may process ordinary technical request data such as an IP address and browser headers to deliver the pages, but these pages do not send QuickBooks accounting data or OAuth tokens to the host.
6. Retention and deletion
QuickBooks responses are used on demand and are not retained by this website or in an App-operated cloud database. Data sent to Codex may be retained by OpenAI according to the owners' applicable account terms and settings. Any report or analysis the owners deliberately save on their own devices is controlled by them and may be deleted using their normal file-management tools.
OAuth credentials remain in macOS Keychain until the connection is revoked or the local disconnect process removes them. Disconnecting deletes the locally stored client ID, client secret, refresh token, company identifier, and environment setting. Access can also be revoked from QuickBooks Online. See the Disconnect page for steps.
7. Choices and rights
The owners may stop using the App, revoke QuickBooks access, or delete locally saved outputs at any time. Questions about access, correction, deletion, or this policy can be sent to yola@yolavanleeuwenkamp.com.
8. Changes
If the App's purpose, data access, storage, or sharing practices change, this policy will be updated before the new practice begins. The effective date at the top identifies the current version.