Can my data ever end up in another company’s hands?
Isolation in the database itself, the automatic check of every table, a stopped module that closes its screens without erasing data, and demo removal that leaves what you entered untouched.
What you get
- Every company is isolated in the database itself: even a software bug won’t open anyone else’s rows.
- A stopped module closes its screens but doesn’t erase the data.
- Removing the demo leaves what you entered yourself untouched.
Transcript
Every company in the system is isolated at the level of the database itself. It isn't a filter a programmer has to remember; it's a rule the database applies to every table.
Even a bug in the software can't return a row belonging to another company: the database itself won't hand it over.
And an automatic check goes through every table and won't let a single one go into service without that rule.
The data belongs to your company. If you stop a module or your subscription, the screens close, but the data stays where it is: switch the module back on, and everything is there.
Even when the owner removes the demo data, only what was generated goes; everything you entered yourself stays.
Nothing is erased to make you stay.