Your data sits in a databasethat is only yours.
Your client history is a business asset. Each Emerson customer has a separate database and deployment, with distinct credentials. Review the controls, access paths and current certification status before you connect your firm.
Where we actually are.
Stated in week one rather than week six of a procurement review: exactly what is in place today, in plain words, with nothing hidden in an accordion at the bottom of the page.
Emerson runs on cloud infrastructure certified to SOC 2 Type II, with AES-256 encryption at rest and TLS in transit on every deployment.
Isolation at the credential level, not a tenant column in a shared table. There is no shared place for two customers to see each other.
Google and Microsoft own the login. Access is granted by you through their own consent screens and ends the moment you revoke it.
Mail leaves under your name and calls come from your number. Nothing routes through a shared sender another customer also uses.
If your review needs something that is not on this page, ask on the call. You will get a yes, a no, or a date, in those words and in writing.
One database per customer. Not a column in a shared one.
A shared database with a tenant column asks you to trust that every query in the product remembers to filter. This asks you to trust a credential boundary instead.
Think of it as your own building rather than a locked floor in a shared one. There is no master customer list with your firm on one row and somebody else on the next.
Another customer’s deployment uses different database credentials. This separates customer records at the database boundary; staff access and operational controls still need to be reviewed.
Isolation is at the credential level. Separate database, separate deployment, separate credentials per customer. There is no tenant discriminator to forget in a query, because there is no second tenant in the database to return.
The access path that does exist is ours, and it is named below: Emerson North staff can reach your deployment in order to support it.
Send us the questionnaire. Or just send these four.
Put your reviewer in touch directly. They will get straight answers in writing, in sentences they can paste into their own memo, with a date against anything that has one.
We will name the people, and we will remove the access when you ask.
You grant it through the Google or Microsoft consent screen yourself. We never ask for a password, and you can end it from your own admin console without going through us.
Your data is yours and you can have a full export of it at any point, not only at the end. Emerson itself, the software and the infrastructure it runs on, stays ours. What leaves with you is the record, not the system.
We answer diligence questions ourselves. There is no security desk to route you to, which is also why you get a straight answer in the same week you ask.
hello@emersonnorth.com