All communications between the iBE.net server and your browser or "client" are encoded using https 128-byte encryption. We also compress larger files for improved performance. Service or API calls from your browser are only accepted on iBE.net's servers if you provide a secret token, which is stored in in encoded form in your browser.

Each customer or company using iBE.net gets their own unique transactional database or store, allowing data to be protected as well as exported (should you decide to stop using iBE.net in the future) more easily. Performance is also improved since indexes and locking concepts are unique to each company using iBE. Some data such as analytics, customizing settings and contact information are stored in shared databases.

Designed from the outset for the cloud, iBE.net run in Amazon's Type-70 SAS certified data centers in West Virginia and Oregon. Despite occasional well-publicized breaches, we feel that a company with Amazon's resources will do the best job possible of protecting your data.

You can build customized menus by job role, limiting what each employee or associate in your company can do. You can also hide individual fields, tabs or table columns by job role, so that two different users of the same application will see different data elements. Authorization within an application can be restricted to specific companies or business units, or on an individual document basis. Other people cannot access documents you mark as private.

While we provide the option to login to iBE.net using Gmail or LinkedIn account profiles, you system administrator can centrally disable these features for added security.