Skip to content
Sign in

Licenseware security

Licenseware is hosted on Google Cloud Platform and Microsoft Azure, behind Cloudflare. There are three separate production regions: European Union (West), United States (East) and Australia (APAC). Each region is its own environment, with its own data stores.

LICENSEWARE holds a SOC 2 Type 2 attestation. SOC 2 is an independent auditing standard from the AICPA, and a Type 2 report attests that the controls are designed well and work over an observation period. To get the SOC 2 Type 2 report, ask your account representative.

Your data is protected in layers, so it never relies on a single safeguard.

  • At the edge. Cloudflare screens every request for attacks and bots before it reaches Licenseware.
  • On the move. Every connection to Licenseware is encrypted.
  • At rest. Your data and its backups are encrypted, and the most sensitive fields get a second layer.
  • Yours alone. Every request and every query is limited to your organisation. Nobody else sees a project unless someone on it invites them.
  • At sign-in. Sign in with Microsoft or Google, turn on multi-factor authentication, and get a bot check at login.
  • Watched. The platform is monitored continuously, including at runtime.
  • Backed up. Every hour, in multiple locations within your region.
  • Independently audited. SOC 2 Type 2, on cloud providers that hold their own ISO 27001 and SOC 2 accreditations.

Each instance keeps its data in its own region. Sign up on the one where you want your data kept.

InstanceRegion
app.licenseware.ioEuropean Union, West
us.licenseware.ioUnited States, East
au.licenseware.ioAustralia, APAC

Both hosting providers undergo independent third-party audits. These are the providers’ own accreditations, from Google Cloud compliance and Azure compliance.

Google CloudMicrosoft Azure
ISO/IEC 27001, 27017 and 27018, SOC 1, 2 and 3, PCI DSS, HIPAA, FedRAMP and GDPR readinessISO/IEC 27001, 27017 and 27018, SOC 1, SOC 2 and SOC 3, PCI DSS, HIPAA, FedRAMP and EU GDPR

All traffic passes through Cloudflare. That includes DDoS protection, a web application firewall and bot management.

Connections use TLS 1.2 or higher. Network rules restrict what can reach the application.

Your data is encrypted at rest, and so are its backups.

Credentials you give us for an integration, such as an API key, an OAuth token or a password, are encrypted in the application and kept separate for each customer. OAuth tokens refresh on their own.

Sensitive fields have an extra layer of encryption in the application. Secrets are held in a managed secrets vault. They are not stored in source code.

We comply with applicable data protection regulations, including the General Data Protection Regulation (GDPR).

Every request is checked for a valid session and for the customer it belongs to. Every data query is limited to that customer. Uploaded files are stored separately per customer.

A project is shared with someone else only when a person on the project invites them.

Sign in with email and password, after you verify the email, or with Microsoft or Google. Multi-factor authentication is supported. Every request is authenticated before it reaches the application. A revoked account is blocked.

Passwords are stored with strong one-way hashing, never in plain text. Sign-in has a bot check, multi-factor authentication comes with recovery codes, and sensitive account changes need a recent sign-in.

To turn on two-factor authentication for your own account, see Two-factor authentication. Single sign-on is under Create an account.

NEO and the other AI features run on Google Vertex AI.

Every AI request passes through a safety layer. It filters requests that are out of scope, and it screens what you send and what comes back for prompt injection, personal data and malicious links. The safety layer is on for every AI request.

How data is used with AI is on AI use and data protection.

Code changes go through a reviewed pull request on a protected main branch.

Software is scanned for vulnerabilities before it ships. Security patches for servers and dependencies are applied automatically.

We test the platform against the OWASP Top Ten, such as injection and cross-site scripting.

The platform is monitored continuously, including runtime security monitoring and alerting.

We maintain a formal incident response framework, with defined escalation procedures, communication protocols and remediation steps.

Your data is backed up every hour, in multiple locations within your region. Backups are encrypted.

The platform can be rebuilt from code and restored from backup.

For a security questionnaire, or for detail under a non-disclosure agreement, email support@licenseware.io or use Contact at the bottom of the sidebar.