Strictly necessary cookies
Used for login sessions, base-path routing, account security, abuse prevention, and reliable form submission. The service cannot work correctly without these.
Cookie Policy
BillGutter uses cookies and product events to run the service, protect accounts, understand the signup and upload flow, and keep proof-first workflows reliable.
Last updated: September 7, 2026
Based on the current source scan, BillGutter uses necessary cookies and first-party operational events. A full opt-in marketing-cookie banner should be added before any non-essential ad tracking, cross-site tracking, or international launch.
Used for login sessions, base-path routing, account security, abuse prevention, and reliable form submission. The service cannot work correctly without these.
Used to understand failed requests, rate limits, uptime, errors, and suspicious activity. These signals help protect accounts, workspaces, and uploaded bill data.
BillGutter may record product events such as landing-page visits, signup progress, plan selection, upload steps, billing actions, and feature use. These records are used to improve the product and launch funnel, not to sell personal bill data.
When a user opens Stripe checkout, invoices, or the billing portal, Stripe may use cookies and similar technologies under Stripe's own policies. BillGutter does not store full card numbers.
A source-code scan found no obvious Google Tag Manager, Meta Pixel, TikTok Pixel, cross-site ad network, or third-party remarketing embed in the public BillGutter app code at the time this policy was updated.
If BillGutter later adds non-essential analytics, advertising pixels, cross-site tracking, or third-party embeds that require consent, the site should add a clear consent banner or preference center before those tools run.
Consent and controls