Trust Center

Built to be trusted.

Security, privacy, compliance, and resilience are built into Light from the ground up. Explore our controls, certifications, policies, and documentation.

Request documents See the controls

5 control areas, 6 frameworks · reviewed 2026-08-27

Independently examined

Not self-assessed. Each of these was tested by an outside party, over a period rather than at a point in time.

Documents

The public documents are linked below. The reports are confidential and go out under NDA, usually within one business day.

SOC 2 Type II report 🔒 Full report, including the auditor's opinion and test results. Request → SOC 1 Type II report 🔒 ICFR-relevant controls, for your auditors. Request → Penetration test summary 🔒 Most recent independent test, with remediation status. Request → Security whitepaper 🔒 Architecture, data flows and control detail in full. Request → Data Processing Agreement Standing Article 28 terms, including sub-processors. Read → Privacy Policy How Light handles personal data as a controller. Read → Terms of Service The agreement governing use of the platform. Read → Sub-processor list Current sub-processors, purpose and region — Exhibit 3 of the DPA. Read →

Controls

The measures behind the certificates, grouped by what they protect.

Infrastructure security How the platform your ledger runs on is built, isolated and watched. 12
  • Encryption key access restricted The company restricts privileged access to encryption keys to authorized users with a business need.
  • Unique account authentication enforced The company requires authentication to systems and applications to use unique username and password or authorized Secure Socket Shell (SSH) keys.
  • Production application access restricted System access restricted to authorized access only.
  • Access control procedures established The company's access control policy documents the requirements for the following access control functions: adding new users; modifying users; and/or removing an existing user's access.
  • Remote access MFA enforced The company's production systems can only be remotely accessed by authorized employees possessing a valid multi-factor authentication (MFA) method.
  • Infrastructure performance monitored An infrastructure monitoring tool is utilized to monitor systems, infrastructure, and performance and generates alerts when specific predefined thresholds are met.
  • Network segmentation implemented The company's network is segmented to prevent unauthorized access to customer data.
  • Network firewalls reviewed The company reviews its firewall rulesets at least annually. Required changes are tracked to completion.
  • Network firewalls utilized The company uses firewalls and configures them to prevent unauthorized access.
  • Unique network system authentication enforced The company requires authentication to the production network to use unique usernames and passwords or authorized Secure Socket Shell (SSH) keys.
  • Firewall access restricted The company restricts privileged access to the firewall to authorized users with a business need.
  • Remote access encrypted enforced The company's production systems can only be remotely accessed by authorized employees via an approved encrypted connection.
Organizational security The people side: hiring, devices, conduct and disposal. 10
  • Asset disposal procedures utilized The company has electronic media containing confidential information purged or destroyed in accordance with best practices, and certificates of destruction are issued for each device destroyed.
  • Anti-malware technology utilized The company deploys anti-malware technology to environments commonly susceptible to malicious attacks and configures this to be updated routinely, logged, and installed on all relevant systems.
  • Confidentiality Agreement acknowledged by employees The company requires employees to sign a confidentiality agreement during onboarding.
  • Performance evaluations conducted The company managers are required to complete performance evaluations for direct reports at least annually.
  • MDM system utilized The company has a mobile device management (MDM) system in place to centrally manage mobile devices supporting the service.
  • Employee background checks performed through extensive screening process The company performs background checks on new employees.
  • Code of Conduct acknowledged by employees and enforced The company requires employees to acknowledge a code of conduct at the time of hire. Employees who violate the code of conduct are subject to disciplinary actions in accordance with a disciplinary policy.
  • Visitor procedures enforced The company requires visitors to sign-in, wear a visitor badge, and be escorted by an authorized employee when accessing the data center or secure areas.
  • Code of Conduct acknowledged by contractors The company requires contractor agreements to include a code of conduct or reference to the company code of conduct.
  • Confidentiality Agreement acknowledged by contractors The company requires contractors to sign a confidentiality agreement at the time of engagement.
Product security How the software itself is written, tested and proven before it reaches you. 4
  • Data encryption utilized The company's datastores housing sensitive customer data are encrypted at rest.
  • Control self-assessments conducted The company performs control self-assessments at least annually to gain assurance that controls are in place and operating effectively. Corrective actions are taken based on relevant findings. If the company has committed to an SLA for a finding, the corrective action is completed within that SLA.
  • Penetration testing performed The company's penetration testing is performed at least annually. A remediation plan is developed and changes are implemented to remediate vulnerabilities in accordance with SLAs.
  • Vulnerability and system monitoring procedures established The company's formal policies outline the requirements for the following functions related to IT / Engineering: vulnerability management; system monitoring.
Internal security procedures The programme behind the controls — governance, risk, incidents, vendors and continuity. 30
  • Continuity and Disaster Recovery plans established The company has Business Continuity and Disaster Recovery Plans in place that outline communication plans in order to maintain information security continuity in the event of the unavailability of key personnel.
  • Continuity and Disaster Recovery plans tested The company has a documented Business Continuity/Disaster Recovery (BC/DR) plan and tests it at least annually.
  • Cybersecurity insurance maintained The company maintains cybersecurity insurance to mitigate the financial impact of business disruptions.
  • Configuration management system established The company has a configuration management procedure in place to ensure that system configurations are deployed consistently throughout the environment.
  • Development lifecycle established The company has a formal systems development life cycle (SDLC) methodology in place that governs the development, acquisition, implementation, changes (including emergency changes), and maintenance of information systems and related technology requirements.
  • Whistleblower policy established The company has established a formalized whistleblower policy, and an anonymous communication channel is in place for users to report potential issues or fraud concerns.
  • Board oversight briefings conducted The company's board of directors or a relevant subcommittee is briefed by senior management at least annually on the state of the company's cybersecurity and privacy risk. The board provides feedback and direction to management as needed.
  • Board charter documented The company's board of directors has a documented charter that outlines its oversight responsibilities for internal control.
  • Board expertise developed The company's board members have sufficient expertise to oversee management's ability to design, implement and operate information security controls. The board engages third-party information security experts and consultants as needed.
  • Board meetings conducted The company's board of directors meets at least annually and maintains formal meeting minutes. The board includes directors that are independent of the company.
  • Backup processes established The company's data backup policy documents requirements for backup and recovery of customer data.
  • Management roles and responsibilities defined The company management has established defined roles and responsibilities to oversee the design and implementation of information security controls.
  • Organization structure documented The company maintains an organizational chart that describes the organizational structure and reporting lines.
  • Roles and responsibilities specified Roles and responsibilities for the design, development, implementation, operation, maintenance, and monitoring of information security controls are formally assigned in job descriptions and/or the Roles and Responsibilities policy.
  • Security policies established and reviewed The company's information security policies and procedures are documented and reviewed at least annually.
  • Access requests required The company ensures that user access to in-scope system components is based on job role and function or requires a documented access request form and manager approval prior to access being provisioned.
  • Incident response plan tested The company tests their incident response plan at least annually.
  • Incident response policies established The company has security and privacy incident response policies and procedures that are documented and communicated to authorized users.
  • Incident management procedures followed The company's security and privacy incidents are logged, tracked, resolved, and communicated to affected or relevant parties by management according to the company's security incident response policy and procedures.
  • Company commitments externally communicated The company's security commitments are communicated to customers in Master Service Agreements (MSA) or Terms of Service (TOS).
  • External support resources available The company provides guidelines and technical support resources relating to system operations to customers.
  • Service description communicated The company provides a description of its products and services to internal and external users.
  • Risks assessments performed The company's risk assessments are performed at least annually. As part of this process, threats and changes (environmental, regulatory, and technological) to service commitments are identified and the risks are formally assessed. The risk assessment includes a consideration of the potential for fraud and how fraud may impact the achievement of objectives.
  • Risk management program established The company has a documented risk management program in place that includes guidance on the identification of potential threats, rating the significance of the risks associated with the identified threats, and mitigation strategies for those risks.
  • Risk assessment objectives specified The company specifies its objectives to enable the identification and assessment of risk related to the objectives.
  • Third-party agreements established The company has written agreements in place with vendors and related third-parties. These agreements include confidentiality and privacy commitments applicable to that entity.
  • Vendor management program established The company has a vendor management program in place. Components of this program include: critical third-party vendor inventory; vendor's security and privacy requirements; and review of critical third-party vendors at least annually.
  • System changes externally communicated The company notifies customers of critical system changes that may affect their processing.
  • System changes communicated The company communicates system changes to authorized internal users.
  • Support system available The company has an external-facing support system in place that allows users to report system information on failures, incidents, concerns, and other complaints to appropriate personnel.
Data and privacy What Light does with your data, how it is classified, and when it goes away. 3
  • Data retention procedures established The company has formal retention and disposal procedures in place to guide the secure retention and disposal of company and customer data.
  • Data classification policy established The company has a data classification policy in place to help ensure that confidential data is properly secured and restricted to authorized personnel.
  • Customer data deleted upon leaving The company purges or removes customer data containing confidential information from the application environment, in accordance with best practices, when customers leave the service.

Where your data lives

One answer, and it does not change depending on who is asking.

In the European Union

Light’s core backend runs on AWS in Ireland, inside a HIPAA-compliant deployment. Backups are held in separate locations so a single failure cannot take both. Light works only with cloud providers whose data centres hold SOC 2 and ISO 27001 attestations.

Encrypted end to end

Recent TLS on every connection — browser to application, application to your ERP or bank, and internally between Light’s own services and databases. Data at rest is encrypted, and credentials sit in AWS Secrets Manager rather than in code.

Held as briefly as possible

Light is designed not to store personally identifiable information during synchronisation: it exists to move data, not to profile it. When a contract ends you are offered an export, and the data is deleted 90 days later unless the law requires otherwise.

Agents, and what they are allowed to do

Light runs a workforce of agents on your ledger. That raises questions a conventional ERP never had to answer.

Your data does not train anyone else’s model

Customer data is never contributed to third-party foundation model training. The providers Light calls process it under agreements that prohibit training on it, and each sees only the minimum its task requires. Light does reserve the right to train and improve models on your data where that makes the service better for you — the DPA sets out the terms.

Every action is attributable

Agents work inside the same permission model as people. Each change lands in the same immutable audit trail — who or what made it, when, and why — and a read-only audit agent verifies the work independently.

You set the boundaries

Approval thresholds, segregation of duties and role-based permissions are configurable per entity, so an agent’s authority is a decision your controller makes rather than a default you inherit.

Questions we get asked

Where is our data stored?

In the European Union. Light's core backend runs on AWS in Ireland, and backups are held in separate locations for resilience. Light only works with cloud providers whose data centres hold SOC 2 and ISO 27001 attestations.

Is our data used to train AI models?

Not by anyone else. Customer data is never contributed to third-party foundation model training: the model providers Light calls process data under agreements that prohibit training on it, and Light applies least privilege to every sub-processor so each system sees only the minimum data required. Light itself does reserve the right to train and improve models on customer data where doing so makes the service better for the customer it belongs to. The Data Processing Agreement sets out the governing terms.

Can agents act on our ledger without a human?

Agents operate within the same permission model as people, and every action they take is written to the same immutable audit trail: who or what made the change, when, and why. A read-only audit agent verifies the work. Approval thresholds and segregation of duties are configurable per entity.

How do we get the SOC 2 report?

Request it below. The full SOC 2 Type II and SOC 1 Type II reports are confidential and shared with customers, prospects and their auditors under NDA, usually within one business day.

How quickly are we told about a security incident?

Affected customers are notified without undue delay and no later than 36 hours after discovery, ahead of the 72 hours the GDPR requires of controllers.

Do you support single sign-on?

Light offers role-based permissions and multi-factor authentication out of the box, with authentication handled by Auth0. Talk to us about your identity provider and provisioning requirements and we will confirm what is supported for your setup.

What happens to our data if we leave?

You are offered an export first. Customer data is then deleted 90 days after contract termination, unless a longer retention period is legally required.

Who do we contact about a vulnerability?

Email security@light.inc. Light investigates every report, and will not pursue researchers who test in good faith, act within the scope of their own account, and avoid privacy violations or service degradation.

Any questions? Write to security@light.inc

Book a demo