Privacy Notice
Draft version 0.2 · August 28, 2026
Demo-only legal hold. This draft improves transparency but is not a substitute for advice from a Kentucky-licensed business/technology attorney. Do not accept real customer financial data or charge customers until the legal entity, insurance, policies, consent records, and dispute terms are approved.
What this beta currently processes
Demo Mode uses sample information included with the application. When Plaid Sandbox is configured, the application can briefly process fake Sandbox account data through secure server routes. The included beta does not provide a production database for durable financial-data storage.
What this beta does not currently do
The private demo does not intentionally collect real bank credentials, persist Plaid access tokens, sell personal information, run advertising profiles, or authorize bill payments. The installable web app caches only the public icon and manifest. Product pages, financial APIs, and beta-access responses are marked private and no-store.
Cookies, cache, analytics, and notifications
The private beta uses one essential, HTTP-only access cookie and does not use advertising cookies. A separate browser preference records whether a visitor allowed or declined privacy-limited analytics. The Google tag initializes with analytics and advertising consent denied so installation can be verified without setting analytics storage; measurement events begin only after permission. Advertising personalization and Google Signals remain disabled. Analytics may receive page paths and a small set of product events, but must never receive names, email addresses, financial institution names, merchant or bill details, balances, account identifiers, Plaid tokens, or free-text entries. Visitors can reopen Privacy choices from any page. Production notification preferences must be stored with the authenticated user in protected database records, not marketing cookies or browser storage. Lock-screen push text is generic by default so merchants, amounts, balances, and account identifiers are not exposed.
Financial connections
Institution authentication occurs through Plaid Link. Fee-Fi does not ask for or receive the username and password you use with your financial institution. Production language must describe the specific Plaid products, data categories, purpose, retention, sharing, consent, and revocation mechanisms actually enabled.
Choice, revocation, and deletion
Production users must be able to see connected institutions, revoke access, request access or correction, export supported records, and request deletion subject to applicable law. Production systems must record consent purpose, scope, policy version, time, and withdrawal.
Vendors, security, and incidents
Production language must identify relevant categories of service providers, cross-border processing if any, retention periods, safeguards, and legally required incident-notification procedures. Security measures reduce risk but cannot guarantee that an incident will never occur.
Security and contact
We design for least-privilege access and server-side secrets. No system is perfectly secure. Security reports should be sent to security@fee-fi.com; privacy questions to privacy@fee-fi.com.
Company details still required
Insert the final legal entity name, business address, jurisdiction, effective date, data processors, regulatory disclosures, and official notices address before publication.