Privacy Policy

viseez is a personal financial dashboard. This policy describes what data the application handles and how, in plain terms.

What data we access

Using Plaid, viseez can request read-only access to your linked financial accounts: account names, types, balances, and transaction history. We do not request the ability to move money, and we never see your bank login credentials — those are entered directly into Plaid's own secure interface, never into this application.

Where your data lives

viseez has real user accounts, so each person who signs up gets their own private record. Plaid access tokens and linked-account details are stored server-side in a database (Supabase/Postgres), scoped to your account with row-level security so one user's data isn't reachable through another user's session. Transaction and balance data is fetched live from Plaid on request and returned to your browser — it isn't separately cached or stored beyond that request.

Who can see your data

Only you, and the AI client you personally authorize (e.g. Claude) if you choose to connect one. Each person's linked accounts are isolated to their own account; there's no shared or admin view of other users' transactions. Connecting an AI assistant goes through a standard OAuth login/consent flow you approve explicitly — it only ever sees your own data, never anyone else's.

Consent and control

You control which institutions are linked at all times. You can remove any linked account from the Accounts page, which revokes the associated Plaid access token and deletes its database record immediately. You can revoke an AI assistant's access the same way any OAuth connection is revoked — by removing the connector on the client side, or by deleting your account from Settings.

Data retention

Linked-account records persist in the database until you remove them or delete your account. Deleting your account removes your linked-account records and any AI-assistant tokens issued to you.

Contact

Questions about this policy or how your data is handled can be directed to REPLACE_WITH_YOUR_EMAIL.