Privacy Policy

AHN Financial OS · Last updated 8 September 2026

What this application is

AHN Financial OS is an internal financial operations system built and used by AHN Media LLC and AHN Vietnam Co. Ltd (together, “AHN”). It is not a consumer product and is not offered to the public. It reads AHN’s financial accounts, and it pays AHN’s own staff and contractors — see below.

The only financial accounts connected to it are AHN’s own company accounts. The only people who use it are AHN’s own staff and contractors, each with a named login. There are no external end users, and we do not process anyone else’s personal financial data.

What we collect, and from where

We read data from financial providers that AHN has connected to its own accounts:

  • Plaid — bank and credit-card transactions, account balances, account names, types and the last four digits of account numbers.
  • QuickBooks Online — cash-affecting entries, invoices and bills.
  • Stripe — balance transactions and processing fees.
  • VietinBank, Finverse, VEEM — Vietnamese bank statements and cross-border payments, where configured.
  • Files AHN uploads — bank and payroll statements imported as CSV.

Some of this necessarily includes the names of people and businesses AHN pays or is paid by, because that is what appears on a bank statement. Where AHN records what its own staff cost, that information is restricted to the owner and finance roles by database-level access rules.

Why we hold it

To run AHN’s finances: cash position, burn rate, runway, break-even, budgets, project profitability, receivables and payables, and alerts when money moves. It is bookkeeping and internal reporting for our own company.

We never use it to make decisions about anyone outside AHN. It is not used for lending, credit scoring, identity verification, marketing, or any automated decision about a person.

What we never do

  • We do not sell data, and we do not share it with third parties.
  • We do not use it for advertising or marketing of any kind.
  • We do not send payments to anyone who is not an AHN worker. The system pays our own staff and contractors, and nobody else.
  • There is no export feature — no route in the application produces a data file.

Paying our own people

AHN uses this system to pay its own staff and contractors through VEEM. Only the recipient’s name, email address and country are sent to VEEM, together with the amount — the same details that would appear on any payment instruction.

No payment can be sent by one person acting alone: a run is prepared by one member of finance and must be approved by a different one before anything leaves. Every step is written to the audit trail, and we never send payments to anyone who is not an AHN worker.

We do not read bank credentials to do this, and we hold no card or bank account numbers for recipients — VEEM holds those, under its own policy.

How it is protected

  • Data is held in a managed Supabase Postgres database, encrypted at rest at the storage layer.
  • Provider access and refresh tokens are additionally encrypted at the application layer with AES-256-GCM before being written, using a key that is never stored in the database. A database copy alone does not yield a working bank connection.
  • Row Level Security is enabled on every table, so who may read what is enforced by the database itself rather than by the interface. Staff see only what their role permits; compensation is restricted further.
  • Every change to a financial record is written to an append-only audit trail recording who changed what, when, and from what to what.
  • All access requires an individual named login. Transport is HTTPS throughout.

How long we keep it

Financial records are kept for as long as AHN needs them for accounting, tax and audit purposes, and for any period required by law in the United States and Vietnam.

Disconnecting a provider deletes the stored credentials for it, as described below. It does not delete financial records already imported — those are AHN’s own accounting history rather than the provider’s copy of it.

QuickBooks Online (Intuit)

AHN connects its own QuickBooks company to this system through Intuit’s OAuth 2.0 flow. No QuickBooks credentials are entered into, or pass through, this application — sign-in happens on Intuit’s own page, and what this system receives back is an access token, which is encrypted before it is stored.

The scope requested is com.intuit.quickbooks.accounting, and what is read from it is listed above. Data from QuickBooks is used only for AHN’s own internal reporting. It is not sold, not shared, and not sent to any third party.

Disconnecting works from either side. From inside QuickBooks (Apps → My Apps → Disconnect), Intuit revokes the connection and this system stops receiving data. From the Integrations page in this application, disconnecting calls Intuit’s token revocation endpoint and deletes the stored tokens here, so the grant is ended at both ends.

AHN Financial OS is an independent application. It is not produced, endorsed or supported by Intuit Inc., whose handling of QuickBooks data is governed by Intuit’s own privacy statement.

Plaid

When AHN connects a bank account, that connection is made through Plaid Inc. Plaid collects the credentials entered in its own interface — those credentials are never seen by, or passed through, this application. Plaid’s handling of that information is governed by its own policy: plaid.com/legal.

AHN can disconnect any linked account at any time from the Integrations page, which deletes the stored access token.

Contact

Questions about this policy, or a request concerning data held about you, can be sent to team@asianhustlenetwork.com.

See also the End-User License Agreement. This page describes how the system actually behaves. If the system changes, this page is updated with it.