How NWT handles connected account data

Connecting accounts is a trust decision. The answer should be specific, not vague.

The short version

NWT account connectivity is read-only. NWT retrieves account, balance, and transaction information for tracking; it does not initiate transfers or move money.

Bank credentials are entered through Plaid's connection flow, not directly into NWT. Sensitive financial data is encrypted at rest using AES-256, and transmissions are protected using TLS. NWT does not sell user data; kept data is used only for product/user experience.

No method of storage or transmission is 100% secure, but NWT uses safeguards to protect personal data.

Why NWT asks to connect accounts

NWT is meant to show where your money stands across accounts, balances, transactions, and net worth movement. That view works best when it can read the financial information needed for tracking instead of asking you to rebuild the picture by hand.

The connection is not the product by itself. The point is the clearer view after connection: fewer scattered checks, less manual stitching, and a dashboard that reflects more of your real financial life.

What NWT can access

After you connect an account, NWT can retrieve account, balance, and transaction information. That is the information used to keep your net worth view and related product experience useful.

This is the practical boundary to remember: NWT is built to read financial data for tracking, not to act as a banking control panel.

What NWT cannot do

NWT does not initiate transfers or move money. Read-only account connectivity means the product can help organize and explain your view without becoming a tool that sends money out of an account.

That distinction matters because the main user fear is not only privacy. It is control. NWT should help you understand your money, not take action with it.

Where bank sign-in happens

Bank credentials are entered through Plaid's connection flow, not directly into NWT. Use that distinction as the mental model: Plaid handles the bank connection flow; NWT receives the read-only account information needed for tracking.

That does not mean trust is automatic. It means the roles are clearer: Plaid connection flow for sign-in, NWT for the money clarity view.

How data is protected

Sensitive financial data is encrypted at rest using AES-256, and transmissions are protected using TLS.

The practical takeaway is simple: NWT focuses on specific safeguards instead of asking you to rely on vague promises.

How data is used

NWT does not sell user data. Kept data is used only for product/user experience.

Your connected account information is used to make the dashboard, history, insights, and account views more useful to you.

The honest security note

No method of storage or transmission is 100% secure, but NWT uses safeguards to protect personal data.

That is why the most important details are concrete: read-only account connectivity, Plaid's connection flow, encryption at rest, and TLS-protected transmission.

A clearer view without giving NWT control of your money

The useful version of NWT is simple: connect read-only accounts, see a cleaner picture, and make decisions with less scattered context switching.

If you have been delaying account connection because the boundary felt unclear, the key boundary is this: NWT can retrieve account information for tracking, but it does not initiate transfers or move money.