Skip to content

ProductSecurity

We can read. We can never move money.

Abacus connects with view-only credentials, always. We hold no trading authority and no money movement authority on any account, and there is no configuration in which we could.

The controls

Four things that are true of every account.

These are not settings on which Abacus can compromise. They are how the platform is built, and they apply to the White Glove team as much as to you.

Human verification

The last control is a person.

Access controls stop the wrong people seeing your data. They do not stop the wrong number reaching your dashboard. Every figure we ingest is checked by a named team member before it is published, which is why a restated NAV or a misread notice does not become your reporting error.

100%
Of ingested data verified by a person before it reaches the dashboard
0
Accounts on which we hold trading or money movement authority
Diligence

What counsel asks first.

Security questionnaires are answered by the team that runs the platform, not by a vendor response desk.

What access does Abacus need?
View-only credentials, always. Abacus holds no trading authority and no money movement authority on any account, and the platform has no mechanism to place a trade or initiate a transfer.
Who inside Abacus can see our data?
The named White Glove team on your account, and nobody else by default. Team access to your Abacus is scoped the same way it is for your own people, and every view is logged.
What happens if we leave?
The record is yours. Your team walks you through the export, and you revoke credentials at the custodian yourself.
Can our counsel review your controls?
Yes. Send the questionnaire through the contact page and the team that runs the platform will answer it directly.

Send us your questionnaire.

We will answer it in your format, and walk your counsel through anything that needs a person.