BankTalker Privacy Policy

Effective October 21, 2026. BankTalker is in private founder testing. Qualified counsel must review this policy before commercial launch.

Information in the current build

We store your email, password hash, verified phone, consent choices, normalized subscription projection, secure sessions, limited audit and security context, normalized planning and financial data, and minimized SMS, voice, AI, and billing-event metadata. Bank credentials stay with the financial provider; provider access tokens are encrypted.

How information is used

We use information to secure accounts, bill for BankTalker membership, verify phone ownership, enforce feature and channel consent, maintain read-only bank connections, calculate deterministic financial results, explain questions through allow-listed tools, send enabled alerts, prevent abuse, and retain minimized evidence of meaningful changes.

SMS privacy

We do not sell or rent mobile information. Text messaging originator opt-in data and consent will not be shared with any third parties. Service providers may process this data only as necessary to deliver BankTalker messages and support the service; they may not use it for their own marketing. SMS consent is not a condition of purchasing BankTalker membership.

Payment and AI minimization

Stripe hosts subscription checkout and billing management; BankTalker does not receive or store full card numbers, CVCs, or payment credentials. Raw SMS text is not retained after its bounded operational need. Voice calls are not recorded, raw audio is not stored, and complete speech transcripts are not retained. The configured AI provider receives only the minimum authorized context needed for a request.

Retention and deletion

Successful deletion removes user-linked local billing, financial, planning, SMS, voice, AI, preference, notification, and usage data. Minimal audit, security, and billing-event evidence may remain de-identified under approved retention rules. Production retention windows require legal review.

Questions

Email [email protected]. Do not send passwords, verification codes, bank credentials, or full financial identifiers.