Ginkgo Platform · Data Security

Data security
& privacy

Sensitive-field encryption, access permissions and login verification help family offices manage everyday data access and sharing.

Request a 30-Minute Demo

Protection across access and storage

Product capabilities address who can access data, how users verify their identity, and how sensitive information is stored.

Access permissions

Access that fits the role

Authorize feature modules and client data separately for different users.

Manage feature and data permissions separately
Asset data access includes permission checks

An extra check at login

Multi-factor authentication supports an additional verification step through account settings.

TOTP, SMS and email verification supported
Enable an additional verification step in account settings

Field encryption

Protect sensitive information

Sensitive fields, including account names and numbers, support encryption in storage.

Encryption keys are managed by AWS
Ginkgo employees do not hold the encryption keys

Protection during data processing

Zero data retention for AI model processing and PDF content masking during file ingestion.

Zero data retention for AI models

All AI model services currently used by Ginkgo operate under zero data retention (ZDR) arrangements.

Data processed by the models is not retained on the model service side

Mask specified PDF content

Mask specified content in bank statement PDFs.

Available within the bank statement ingestion workflow

Security FAQ

Is data sent to AI models retained by the model service?

All AI model services currently used by Ginkgo operate under zero data retention (ZDR) arrangements. Data processed by the models is not retained on the model service side.

How does Ginkgo manage data access for different users?

Feature modules and client data can be authorized separately to match user permissions to their work. Asset data access includes permission checks.

What identity verification methods are available at login?

Login supports multi-factor authentication. An additional verification step can be enabled through account settings using TOTP, SMS or email.

Which sensitive information supports encryption in storage?

Sensitive fields, including account names and numbers, support encryption in storage, alongside permissions for data access.

Who manages the encryption keys?

Encryption keys are managed by Amazon Web Services (AWS). Ginkgo employees do not hold the encryption keys.

What privacy measures are available for bank statement processing?

Bank statement ingestion supports masking specified content in PDFs.

Start with your security requirements

Explore sensitive-field encryption, access permissions, login verification, zero data retention for AI models and file processing.