Privacy & cookies
Last updated September 2026
First-party analytics
We use Google Analytics 4 to understand how the product is used — which pages are visited, how often, and where people get stuck — so we can improve it. Analytics is configured to identify your firm only; we never set a per-user identifier, email, or name. We also measure how quickly pages load, through Vercel Speed Insights, our hosting provider. It sets no cookies and follows the same opt-out.
We do not send your ward data to analytics
Inside the application, URLs and page titles can contain ward and person identifiers. Before any analytics event is sent, those identifiers are stripped from the page address, and automatic page-tracking is turned off so the raw URL is never beaconed. Names, ward details, and document contents are never sent to Google.
Cookies & advertising
Analytics uses first-party cookies. We run no advertising and do not sell or share personal data for targeted advertising — advertising and ad-personalization signals are disabled by default through Google Consent Mode.
Your choices
You can decline analytics at any time using the cookie notice on our public pages, or — once signed in — from Settings → Privacy. We also honor your browser’s Global Privacy Control (GPC) signal: if GPC is enabled, analytics stays off automatically. Visitors in the EEA, the UK, and Switzerland are opted out by default until they consent.
Bank connections
When a firm connects a bank login, Fidura uses Plaid to reach the bank. You sign in to the bank inside Plaid’s window, and we never see or store the bank password. Plaid passes us each account’s name, last four digits and balance, and the posted transactions of the accounts you bring in. We keep only what the Sync bank screen shows, and none of it is sent to analytics. Disconnecting a login in Settings removes it at Plaid. Plaid’s own handling is described in its End User Privacy Policy.
Contact
Questions about privacy, or to exercise a data right, email developer@fidura.app.