Daily SOA Pull Companion
Privacy policy
Effective August 27, 2026 · Extension version 0.2.0
Policy summary
Bank statement processing stays on your computer.
Daily SOA Pull Companion connects selected, signed-in business-bank pages to the Daily SOA Pull desktop app. It has no publisher-operated server and does not collect credentials or OTPs.
What the extension handles
When the user starts a run in the Daily SOA Pull desktop app, the extension reads only the supported bank statement pages the user has selected. This can include account numbers, account labels, transaction dates, transaction descriptions, balances, amounts, date-range fields, statement search results, and available download controls.
How the information is used
The information is used only to find allowlisted accounts, search the requested statement period, download available statement files, and create local run reports.
Where information goes
The extension sends run commands and bank-page results only to the Daily SOA Pull desktop app running on the same computer through a local connection at 127.0.0.1. The extension and desktop app do not send bank-page data to the publisher or to third parties.
Information not collected
The extension does not read, store, or transmit bank login credentials, passwords, one-time passwords, authentication cookies, or complete browsing history. It does not sell data, use data for advertising, or use data for credit decisions.
Storage and retention
The extension stores the user-provided local pairing code and the user’s data-use consent in Chrome extension storage. Downloaded statements and run reports are stored only in locations chosen or managed by the desktop app on the user’s computer. The extension does not keep a remote copy.
User control
The user can withdraw consent from the extension popup, remove the pairing code by clearing the extension’s site data, or uninstall the extension. Withdrawing consent turns off the local desktop connection.
Security
The extension is limited to the supported bank domains listed in its permissions and to the local Daily SOA Pull connection. Bank sessions remain inside the user’s Chrome profile.
Changes and contact
Material changes will be reflected in an updated policy and, when required, a new consent request. Privacy questions can be sent through the support contact shown on the extension’s Chrome Web Store listing.