TraceLedger privacy policy

TraceLedger is a Google Apps Script application that processes personal accounting records in the user's Google Sheets workbook. For privacy inquiries, contact kartaltabak@gmail.com.

Data processed and its purpose

The application reads account definitions, transaction dates, descriptions, quantities, amounts, exchange rates and market prices entered in the workbook to perform accounting calculations. It derives journal entries, balances, FIFO lots, lot movements and reports. For invalid input or insufficient balances, it may produce diagnostic information identifying the source rows.

Google Sheets permission is used to read, create, format and update tables in the relevant workbook. The permission requested by the manifest is not restricted to a single file; access depends on the Google account's permissions and the operations performed by the running code. The application does not request bank or brokerage login credentials.

Storage and access

Accounting sources and derived tables are stored in the user's Google Sheets file. The application has no separate developer-operated server or central user database that collects these records. File access depends on the user's Google Drive and Sheets sharing settings. People with access to the Apps Script project can see the code and, subject to their permissions, execution logs.

A rebuild preserves source data and refreshes derived tables. The Delete initialized sheets command deletes the application's fixed accounting sheets and their contents after the user explicitly confirms the operation.

External market data

The optional fetchMarketHistory function sends HTTP requests to providers defined in the code to retrieve supported market history. Requests include query parameters such as instrument or fund information and the requested date or month range. The function does not send the workbook's account and transaction tables or Google OAuth tokens to those providers.

Providers may process requests in their own systems and retain technical access logs. Rebuilding accounting tables uses the visible exchange-rate and price tables; it does not itself call external providers.

Technical logs and automated tests

Apps Script execution logs may contain operation summaries and error messages. Error messages may include account codes, source cells or amounts needed to identify a problem. Retention and access depend on the Google services and the relevant Cloud project's settings.

Automated integration tests run in a separate test project using generated test data in dedicated disposable workbooks. CI uses separate Google authorization profiles to upload code and run tests; these credentials are stored in GitHub Secrets. The production code-publishing step does not read or rebuild accounting tables. Test results and technical errors may appear in CI logs.

Other uses of data

Information obtained from Google APIs is used and transferred only for the application functions described here, in accordance with the Google API Services User Data Policy, including its Limited Use requirements.

TraceLedger's application code does not collect or transfer Google Sheets data for advertising, data sales or AI model training. Information processed by Google, GitHub and the selected market-data providers as part of their own services is subject to those services' terms and policies.

Deletion and revoking access

Users can correct or delete source records in Sheets and then rebuild derived tables. The workbook can also be deleted through Google Drive. Authorization can be revoked through the Google account's third-party connections settings. Revoking authorization does not automatically delete the existing workbook, its revision history or technical logs.

TraceLedger does not promise a deletion schedule for Google Sheets revisions or technical logs independent of Google's retention rules. Sharing permissions, revision history and log-retention settings are managed through the relevant Google services.