Security & data handling

How Truence connects to your systems.

Bank connectivity is provided by Plaid, which you authorise with your bank. Data flows one way — into Truence, where it is reconciled. This page describes that boundary plainly and tells you how to request written documentation for a security review.

Bank connectivity provided by PlaidYou authorise the connection with your bankData flows one way, into TruenceWritten documentation available on request
Store platforms
Advertising accounts
Payment processors
Bank accounts via Plaid
Truencereads and reconciles
Reconciled revenue view
Exceptions and gaps
Exports you request
  • Bank connectivity is provided by Plaid; you authorise it with your bank.
  • Data flows one way: into Truence for reconciliation.
  • No entries are written back to a store, ledger or bank.
  • Written security documentation is available on request.
Direction of data. Connected systems are read; Truence reconciles what it reads; nothing is written back to a connected system.
The problem

Connecting financial accounts deserves a straight answer

Founders evaluating a financial tool usually want three things answered before anything is connected: what is read, which direction the data moves, and what can be put in writing for a security review.

Before Truence
What is readUnclear from marketing copy
Direction of dataNot described
DocumentationNo stated route to request it
Review processEstimated
With Truence
What is readStores, ads, processors, bank records
Direction of dataOne way, into Truence
DocumentationRequested at Sales@truence.com
Review processDocumented before you connect

We won't claim certifications we haven't earned

Truence describes the connection boundary rather than asserting certifications it has not published. Where you need controls, sub-processors, retention, or deletion terms in writing for a review, request them and they will be provided directly.

Bank connectivity

Plaid provides the bank connection

Truence uses Plaid-powered connectivity to connect authorised bank accounts and reconcile platform activity against bank transactions. You complete the authorisation with your bank through Plaid.

  • You choose which accounts to authorise
  • The authorisation is completed with your bank through Plaid
  • Plaid's own terms govern the connection it provides
Direction of data

Data moves into Truence, not back out

Truence reads the records your systems already produce and reconciles them. It does not post entries into a store, an accounting ledger, or a bank account.

  • Store, advertising, processor and bank records are read
  • Reconciled output stays inside Truence until you export it
  • Nothing is written back into a connected system
Documentation

What we will put in writing

For a security review, request the current written documentation covering data handling, retention, sub-processors, and deletion. Anything not yet published is stated as such rather than implied.

  • Request documentation at Sales@truence.com
  • Ask for the specific artefacts your review requires
  • Terms of use and the privacy policy are published on this site
Your accounts

Disconnecting and deletion

You can disconnect an authorised account, and you can ask what happens to the data associated with it. Contact Support@truence.com and the current retention and deletion terms will be confirmed in writing.

  • Disconnect an account you no longer want connected
  • Ask for retention and deletion terms in writing
  • Support@truence.com handles account-level requests
How it works

Before you connect anything

01

Read the boundary

Confirm what is read and which direction the data flows.

02

Request documentation

Email Sales@truence.com for the written material your review needs.

03

Authorise selectively

Connect only the accounts you want reconciled.

04

Keep control

Disconnect an account or ask about deletion at any time.

Reviewing Truence before you connect?

Email Sales@truence.com and ask for the documentation your security review needs.

Sign up →