Data Processing Addendum

Last updated: September 27, 2026. This page summarizes the Offsight AI Data Processing Addendum. The executed DPA is the operative document and governs wherever this summary differs from it. Published for information; it is not legal advice.

1. When the DPA applies

The DPA applies where Offsight Inc. (“Offsight”) processes personal data on a customer’s behalf in the course of providing the Service. It is entered into alongside the Terms of Service and the customer’s Order Form, and forms part of that agreement.

It does not apply to data Offsight handles for its own purposes — a demo request, a sales enquiry, a support message from a visitor. For that, Offsight is the controller and the Privacy Policy is the full description.

2. Roles

• Customer is the controller. You decide what goes into your tenant, who has access to it, and how long it stays.
• Offsight is the processor. We process it on your documented instructions — which, in practice, are the configuration of your tenant and the actions your users take in the product — and for no other purpose.
• Sub-processors are engaged under Offsight’s responsibility. Offsight uses sub-processors to deliver the Service, on terms no less protective than those we owe you, and we remain answerable to you for their performance. The categories are in section 7.

3. Processing particulars

4. AI processing under the DPA

This is the part that is new relative to a conventional MES, so the DPA addresses it explicitly.

• Model providers are sub-processors. Model inference is performed on Offsight’s behalf by third-party providers engaged as sub-processors under section 7, under commercial API terms.
• Scoped transmission. An AI request transmits the content of the request and the records, documents or images retrieved to answer it — not the tenant.
• No foundation-model training. Offsight does not use Customer Data to train, fine-tune or develop general-purpose AI models, and inference requests are made under commercial API terms under which customer content is not used to train the provider’s models.
• Permissions and attribution. An AI request executes in the context of the user who made it, bounded by that user’s per-module and per-user-group permissions, and the resulting actions are recorded in the audit trail against that user.
• Session records are Customer Data. Requests, actions and output are stored in your tenant, are subject to your retention decisions, and are exported and deleted with everything else.
• Human review. AI output is decision support and requires review by a qualified person before it is relied on. The requirement is set out in the Terms of Service, and is a controller obligation you retain.

Vision AI

• Detection runs on Offsight’s infrastructure. Vision AI detection, and the training of Customer Models, are performed on computing infrastructure Offsight operates in its cloud hosting environment, not by an AI model inference sub-processor.
• Customer Models are per customer. Each Customer Model starts from a shared, publicly available open-source base model that contains no Offsight customer’s data, is trained only on your Visual Data, and is used only to process your Visual Data. Training runs with credentials limited to your Visual Data, and your Visual Data is not used to train a model for any other customer. This is processing on your instructions to deliver the Service, not the development of a general-purpose model.
• Optional second-opinion review. Only if you turn on the account setting “Improve Vision AI capability and accuracy” — off unless turned on — Vision AI may send up to eight camera frames, the state being checked, and the related notes attached to training captures and to the area the camera watches to an AI model inference sub-processor, when a detection’s confidence falls just short of its threshold. The request is made with the provider’s response-storage option turned off, and the verdict is recorded beside the detection without overwriting it. With the setting off, Vision AI itself does not send Visual Data to a model provider. Visual Data that a user shares with, or asks, the AI assistant about — for example, the notes on a training capture, or an image attached to a chat — is transmitted as a scoped AI request, as described above, whether or not the setting is on.
• Your cameras, your notices. As controller, you decide where cameras are placed and what they capture, and you are responsible for giving the notices and obtaining the consents the law requires from the people in view. The Acceptable Use Policy sets out where cameras may not be placed and prohibits using Vision AI to identify people.

5. Confidentiality and personnel

Offsight personnel who can access Customer Data are subject to confidentiality obligations, are granted access on a need-to-perform basis, and that access is logged. Support access to a tenant is auditable.

6. Security measures

The technical and organizational measures set out in the DPA include:

• encryption in transit (TLS) and encryption at rest;
• two-factor authentication;
• per-module and per-user-group permissions administered by customer admins;
• tenant isolation and per-tenant data separation;
• audited access, including administrative and support access;
• API keys with rotation, live usage metering and enforceable limits;
• for Vision AI: camera uploads over encrypted FTPS, with unencrypted FTP and older TLS versions refused; upload-only camera credentials that cannot read back, list or delete; camera images written to server-generated storage paths under the customer’s tenant; Visual Data encrypted at rest; Vision AI images kept private rather than given public links, with training captures opened through short-lived signed links; and model training with credentials limited to that customer’s Visual Data; and
• managed cloud infrastructure in the United States — containerized services, a managed relational database with a read replica, and a caching tier.

Offsight will respond to reasonable written security questionnaires from a customer and its assessors, subject to confidentiality, and will describe the architecture and the parties involved in delivering it under that cover.

7. Sub-processors and notice

Offsight engages sub-processors to deliver the Service. They fall into a small number of categories: cloud hosting and storage, AI model inference, design-file processing, transactional and notification email, subscription billing and payment processing, and DNS and edge delivery for our public website.

Vision AI adds a new type of data — images — but no new category. Visual Data is stored and processed within cloud hosting and storage, and reaches AI model inference only through the optional second-opinion review described in section 4. Cameras are hardware the customer procures from third parties; camera manufacturers are not Offsight sub-processors, and anything a camera sends anywhere other than to the Service is not processing by Offsight.

Each is engaged under a written contract imposing data-protection obligations no less protective than those in the DPA, is permitted to use the information only to provide its service to Offsight, and is bound to confidentiality. Offsight remains responsible to the customer for their performance.

The identified list of sub-processors, with the data categories each one receives, is provided to customers and their assessors under the executed DPA. Request it — and email notice of additions or replacements — at support@offsight.com. The DPA sets out the mechanism for objecting to a new sub-processor on reasonable data-protection grounds.

8. International transfers

Offsight is based in the United States and the Service is operated on infrastructure in the United States. Where personal data is transferred out of a jurisdiction that restricts such transfers, the DPA incorporates the applicable transfer mechanism and the associated commitments.

9. Data subject requests

As controller, you handle requests from your own people. Offsight will provide reasonable assistance — and the product itself does much of the work, since an administrator can search, export and delete records directly. Where a data subject contacts Offsight instead, we will direct them to you rather than act on your data.

Visual Data is found by camera and time rather than by name, because Vision AI does not identify the people in an image. Offsight will assist with that search; raw camera frames older than thirty days will already have been deleted.

10. Incident notification

Offsight will notify the customer without undue delay after becoming aware of a personal data breach affecting Customer Data, and will provide the information reasonably available to it so that the customer can meet its own notification obligations, together with reasonable cooperation in investigation and remediation.

11. Return and deletion

On termination, the customer can export Customer Data using the export functions of the Service, with assistance available. Once the export window has passed, Customer Data is deleted in accordance with the agreement. Note that Customer Data may be irretrievably deleted if an account is ninety (90) days or more delinquent.

For Visual Data, raw camera frames and detection overlay images are deleted automatically on the schedule in the processing particulars (section 3). Training captures, their markups, annotations and notes, and Customer Models are deleted in accordance with the agreement at termination or on your request. Removing a training capture in the product does not by itself immediately erase the stored image.

12. Contact

Questions about this policy: support@offsight.com. Contract questions: sales@offsight.com.

Offsight Inc.
650 California St
San Francisco, California 94108