For people who read the fine print

Your financial life is yours.

OWN helps you understand your money — without the power to move it or sell your profile. Trust is the architecture, not the promise.

We can't move your money.Every bank connection is read-only.
We don't sell your profile.No ads. No brokers. No model training.
Protected stays protected.Sensitive documents and records are encrypted at rest before storage.

The trust model

Built around your skepticism.

You should think twice before linking financial accounts or uploading sensitive documents. OWN is designed around that instinct — not around asking you to set it aside.

01

Read-only money access.

Linked accounts let OWN show you what's happening. OWN cannot initiate transfers, withdraw funds, or move money from your accounts.

02

Protected records.

Sensitive documents and protected records are encrypted before storage. Documents and sensitive records are held as ciphertext at rest, not readable files.

03

No hidden data business.

OWN is not an advertising platform. We don't sell your financial profile, run ads against your data, or train models on your documents.

Plain answers

Can OWN do this?

The cleanest way to earn trust is to answer the questions people are actually asking — before they connect anything.

Can OWN move money from my bank account?
No.
Bank linking is read-only. OWN exists to help you understand your finances — not to transact on your behalf.
Does OWN store my bank password?
No.
Credentials are handled through secure bank-linking infrastructure. OWN never stores your online banking password.
Can OWN sell my financial profile?
No.
OWN does not sell your profile, and advertising is not its business model.
Can OWN staff browse my protected records?
Restricted.
Records are encrypted at rest and access is restricted, logged, and limited to operating the service — access requires authorization, is limited to operating the service, and is logged.
Is my sensitive data encrypted?
Yes.
Documents and sensitive records are encrypted at rest with AES-256; keys are managed server-side and access is restricted and logged.
Does OWN need some data to run the service?
Yes.
OWN needs limited operational information for accounts, security, billing, support, and compliance.

Boundaries

What OWN can see.

A privacy claim only matters when the boundaries are clear. Your most sensitive data is protected differently from the operational data that runs the service.

Protected records are treated like vault contents.

Sensitive documents and protected records are encrypted before storage. Documents and sensitive records are held as ciphertext at rest, never readable files.

ExamplesUploaded documents, sensitive financial records, protected records.
Access modelEncrypted at rest, access-controlled, and limited to operating the service.
BoundarySupport access requires authorization, is limited to operating the service, and is logged.

Bank access is for visibility, not control.

Linking is read-only. OWN uses authorized account information to help you understand balances, transactions, cash flow, and patterns. It cannot initiate a transfer.

ExamplesBalances, transactions, account names, account metadata.
Access modelRead-only connection through secure bank-linking infrastructure.
BoundaryOWN does not store your online banking password.

Some data is needed to run the product.

No serious service operates on zero information. OWN keeps limited operational data for accounts, login security, billing, support, consent records, audit logs, and reliability.

ExamplesEmail, subscription status, support history, consent records, device and session signals.
Access modelLimited to operating, securing, supporting, and improving OWN.
BoundaryOperational data is not a licence to sell your profile.

Insight processing is scoped to the service you asked for.

OWN uses authorized information to produce your dashboards, planning insights, and Atlas guidance. That isn't staff reading your records, selling your profile, or training models on your documents.

ExamplesCash-flow analysis, tax estimates, benefits matching, goal projections, Atlas explanations.
Access modelControlled, limited, and tied to providing the product experience.
BoundaryYour documents are not used to train AI models.

Security architecture, in plain English

From your device to your dashboard.

A chain of custody: user-controlled access, read-only connections, encrypted storage for documents and sensitive records, and scoped processing to deliver the service.

Step 01

You authorize.

You choose what to connect, upload, or protect inside OWN.

Step 02

OWN protects.

Read-only links and encrypted-at-rest storage reduce unnecessary exposure.

Step 03

You understand.

Dashboards and Atlas explain your financial life — without turning it into a product sold to others.

Atlas / AI

Useful intelligence. Not training data.

Atlas works from your authorized financial information to explain your situation, surface opportunities, and model planning scenarios for you.

OWN does not train models on your documents. OWN does not sell your financial profile. Access to information is limited to providing the service you asked for and operating the platform securely.

Documents and sensitive records stay encrypted at rest. When information must be processed to generate insights, that processing is scoped to the product and governed by the Privacy Policy.

Designed for the bad day

Security is a failure plan — not a slogan.

OWN assumes sensitive systems must limit damage even when something goes wrong. Protected records are encrypted, access is minimized and logged, and sensitive activity is monitored.

If a security incident ever affects users, OWN will investigate, contain it, notify those affected where required, and explain what happened in plain language.

MinimizeCollect and expose only what's needed to provide the service.
ProtectEncrypt protected records and restrict sensitive access.
ContainInvestigate and limit damage if something goes wrong.
NotifyTell affected users where required, and communicate clearly.