> For the complete documentation index, see [llms.txt](https://www.locksmith.guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.locksmith.guide/policies/data-processing-agreement.md).

# Data Processing Agreement

Lightward Data Processing Addendum (Locksmith)

#### Last updated: 18 November 2025

This Data Processing Addendum is part of the agreement between Lightward and the customer who uses our services.

By using Locksmith, the customer agrees to this DPA.

## 1. Roles

The customer (as the controller) determines why and how Personal Data is processed.

Lightward (as the processor) processes Personal Data only as needed to provide our services and support the customer's use of them.

Lightward processes Personal Data only according to: (a) the customer's subscription, (b) the customer's configuration of Locksmith inside their shop, and (c) the customer's use of Locksmith's features.

## 2. Purpose

Lightward processes Personal Data only as needed to provide Locksmith and as otherwise allowed under the agreement.

## 3. Security

Lightward uses technical and organizational measures designed to keep Personal Data secure.

## 4. Confidentiality

Lightward ensures that team members who access Personal Data are bound by confidentiality obligations.

## 5. Sub-Processors

The customer allows Lightward to use sub-processors to help provide Locksmith.

## 6. International Transfers

Lightward may transfer Personal Data internationally as needed to provide the service, using lawful transfer mechanisms when required.

## 7. Assistance

Where required by law and technically feasible, Lightward will help the customer respond to data-subject requests.

## 8. Deletion

When the customer stops using Locksmith, Lightward will delete or return Personal Data according to the agreement unless the law requires us to keep it.

## 9. Breach Notification

Lightward will notify the customer without undue delay if we become aware of a Personal Data Breach.

***

### Sub-Processors for Locksmith

### Last updated: 20 November 2026

Lightward works with a small group of trusted service providers to operate Locksmith. These companies may process limited Personal Data as part of providing the service.

**Infrastructure & Hosting**

* Fly.io — application hosting
* crunchybridge — Storage, hosting, retrieval, backup, replication, and transmission of data
* Redis Ltd (Redis Cloud) — application cache and background job queue

**Platform Integrations**

* Shopify, Inc. — authentication, API platform, webhook delivery

**Monitoring**

* Rollbar, Inc. — error monitoring and diagnostics
* New Relic, Inc. — application performance monitoring and diagnostics
* Cronitor — scheduled job monitoring

**Customer Support**

* Help Scout PBC — customer support correspondence, when the customer contacts Locksmith support

**Optional Service Providers (enabled only when the merchant connects these integrations or uses these features)**

* Google LLC — file storage (Google Drive for access lists)
* Mailchimp (Intuit Inc.) — email marketing list integration
* Klaviyo — email marketing list integration
* Mechanic (Lightward, Inc.) — automation platform integration
* MaxMind — IP geolocation services


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.locksmith.guide/policies/data-processing-agreement.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
