Privacy policy
OpsBench is a personal, non-commercial project. It has no public sign-up, no advertising, no analytics and no tracking.
Accounts are created by the operator by invitation.
What is stored
| Data | Why | How long |
|---|---|---|
| Dashboard accounts: username, password hash, section permissions | Sign-in and access control | Until the account is deleted |
| Two-step sign-in: the authenticator-app secret (encrypted), one-way hashes of recovery codes, and the time of the last code used | Account security (required for accounts that can reach bank data) | Until two-step sign-in is turned off or reset |
| Automation settings: Brink's/PAR POS client names, usernames and passwords, store names; Windows (RDP) connection details; email sender settings | Running the report automation you configure | Until changed or deleted. All passwords are encrypted at rest. |
| Run history and logs, download coverage (store, business date, success/failure) | Showing what ran, troubleshooting, retrying failures | Deleted automatically after 2 months |
| Audit log: who revealed a stored password, from which IP address | Security | Deleted automatically after 2 months; anonymised when the account is deleted |
| Bank connections made through Plaid: the bank's name, an encrypted Plaid access token, and each linked checking/savings account's name, type and last 4 digits, plus the store it is assigned to. Bank usernames and passwords are entered at Plaid and are never seen or stored by OpsBench. | Bank Data feature, only if an administrator connects a bank | Until the connection is removed (which also revokes access at Plaid) |
| Bank transactions of connected checking/savings accounts (date, amount, description, merchant, category), and the export files (CSV/Excel) generated from them, plus a record of each download job and who started it. Optional summary emails list account names, statuses and transaction counts only (never transactions or files). | Bank Data feature: Run now, schedules and summary emails | Transactions until the bank connection is removed; export files are deleted automatically after 30 days (configurable) |
| Dropbox connection (account name, email, an encrypted access token) and an index of tracked file/folder names; parsed figures from tracked P&L PDFs | Analytics Hub, only if an administrator connects Dropbox | Until Dropbox is disconnected or folders are untracked |
| Bank Data cloud storage: the connected Dropbox account's name and email, an encrypted access token, the folder and file-name settings, and a log of which exported files were saved where | Bank Data, only if a user connects their own cloud storage (exported transaction files are then copied to that user's own Dropbox) | Until the user disconnects it (which also revokes OpsBench's access) |
| Excel macros: the macro files (.bas) a user uploads and every earlier version of them, the files those macros open (for example a client list), the bank files a user uploads to run them on, the bank statement files made from them, and a record of where each file was saved in Dropbox | Bank Data, only for users given the Excel macros permission: running the user's own macros on their bank data and saving the results to their own Dropbox | Macro files until the user replaces or deletes them; bank files and finished statement files are deleted from OpsBench automatically after 30 days (configurable), the saved copies stay in the user's Dropbox |
| Web server access logs (IP address, time, page requested) | Security and diagnosing problems | Rotated by the server's system log (normally a few weeks) |
No more data is collected than the features above need. Nothing is sold, shared for marketing or used for profiling.
Who processes it
- Oracle Cloud — hosts the server and database.
- Gmail (Google) — sends run-summary emails to the notification address set in Settings.
- Dropbox — only if an administrator connects it (Analytics Hub), or a user connects their own Dropbox to save Bank Data exports.
- Plaid — connects to banks for the Bank Data feature, only if an administrator connects a bank. Plaid's own end-user privacy policy applies to the sign-in inside Plaid Link.
- Microsoft Azure — runs the Excel machine for Excel macros: a private Windows computer (United States, East US) with licensed Microsoft Excel. For each statement file it receives only that file's bank transactions, the user's macro and the files the macro opens, runs the macro and deletes them right afterwards. It has no access to bank connections, Dropbox or the OpsBench database. Used only when a user has the Excel macros permission.
- PAR POS / Brink and the reporting portal configured for Step 4 — the automation signs in to them with the credentials you store.
- jsDelivr, cdnjs (Cloudflare) and the Plotly CDN — deliver three open-source scripts; like any website they receive your IP address when your browser downloads them. See Credits.
- DuckDNS and Let's Encrypt — domain name and HTTPS certificate.
Cookies
Only essential cookies — see the Cookie policy.
Children
OpsBench is a business-operations tool for adults. It is not directed at children, does not knowingly collect data about anyone under 16, and has no feature that collects data from or about children. No age consent is therefore needed.
Your rights and deletion requests
You can ask for a copy of the data held about you, ask for it to be corrected, or ask for it to be deleted. Contact the site administrator and the request is handled within 30 days. Deleting an account removes the account record and anonymises its audit-log entries; run history stored for the automation itself is removed by the retention rule above.
Security
HTTPS everywhere, passwords stored as salted hashes or encrypted at rest, CSRF protection on every form, rate-limited sign-in, and two-step sign-in (authenticator app) for every account that can reach bank data.