How WideView keeps your sites safe

By default, nothing changes in your systems until a person approves it. You can allow small, routine actions to run inside limits you set. Every action is logged with who approved it and why, and can be reversed.

• Read only by default. Write access only for the actions you approve.
• A separate, scoped credential for every connector.
• Credentials are encrypted and never shown in the interface.
• For apps with no API, a Chrome extension that uses your team's existing login and never stores passwords. Coming soon.

WideView never needs inbound access to your network. Cloud software connects through its own API over TLS. Site data comes in through exports or the WideView API. Soon machines on site will connect through the WideView gateway, software on a computer you already have that connects out over TLS.

Data is encrypted in transit with TLS 1.2 or higher and at rest with AES-256.

• Our cloud, hosted in the United States.
• With Enterprise: your cloud (AWS, Microsoft Azure or Google Cloud), on premises inside your network, or fully offline and air gapped for defense and regulated sites. We set these up with you.

Email and password or a one-time sign-in link, two-step sign-in with an authenticator app, and roles that decide who can see, approve and change what. Enterprise adds single sign-on with SAML or OpenID Connect.

Your data is used to run your sites and is deleted when you ask. We never use it to train models for anyone else.

We will list audits and certifications here as they complete. Ask us for our current security overview.

Please give us a reasonable time to fix an issue before you share it. We will not take legal action against good faith research.