Flatly has implemented a high security architecture on par with that of online banking, including HTTPS TLS 1.2, encryption at-rest and in-transit.
Connection information is encrypted using Advanced Encryption Standard (AES256) and stored in an encrypted database (Firebase) operated by Google. Flatly operates mostly server-side, with a minimal amount of information available client-side. Flatly relies on Cloudflare to protect client-side infrastucture.
No. Unlike many other online services, Flatly does not store business data (examples: CRM opportunities, banking transactions, etc.) on any of our infrastucture. Flatly is a Conduit Architecture which means your data passes through Flatly infrastucture temporarily, but is not persisted.
A conduit architecture is one through which data passes but is not stored or persisted for ongoing processing.
Flatly staff do not access your business data unless (a) you explicitly permit such access via a support ticket, or (b) your business data causes infrastructure outages or stability issues.
Read online resources about (a) Google Security, (b) Firebase Security, (c) client versus server architecture, (d) Cloudflare. (e) AES 256 and (f) TLS 1.2
Making data more accessible for everyone.