Data Processing Addendum

Version
1.5
In effect from
# 86X Data Processing Addendum

**Version 1.5 · `app.86xventures.com/legal/dpa`**

*The version and effective date shown on this page are recorded with this document and displayed from that record.*


---

This Addendum forms part of the **86X Platform Terms** at `app.86xventures.com/legal/platform-terms` and is accepted at the same time as those Terms. Capitalized terms not defined here have the meaning given in the Platform Terms.

**"86X"** means **86X Ventures LLC**, a Georgia limited liability company. **"Client"** or **"Customer"** means the organization on whose behalf the Platform Terms were accepted.

---

## 1. Roles and scope

**1.1** This Addendum applies where 86X processes personal data contained in Customer Content on Customer's behalf in providing the Software (**"Client Personal Data"**).

**1.2** As to Client Personal Data, **Customer is the controller and 86X is the processor.** 86X processes Client Personal Data only on Customer's documented instructions, which consist of the Platform Terms, this Addendum, and Customer's use of the Software's features.

**1.3** 86X will inform Customer if, in 86X's opinion, an instruction infringes applicable data protection law, and may suspend the affected processing until the instruction is withdrawn or amended.

**1.4 What this Addendum does not cover.** 86X acts as a **controller in its own right**, and not as a processor, with respect to: (a) records of Customer's acceptance of the Platform Terms and this Addendum (see §6.5); (b) account and billing administration records; and (c) 86X's own security, audit, and operational logs. 86X's handling of that data is described in the **86X Privacy Notice**.

**1.5 Demonstration and test data.** 86X operates demonstration, test, and development organizations within the Software that are designated as such in 86X's systems and are not operated on behalf of any Customer (**"Demonstration Organizations"**). Data in a Demonstration Organization is fabricated by or for 86X and does not relate to an identified or identifiable natural person (**"Demonstration Data"**). Demonstration Data is not Client Personal Data, and this Addendum does not apply to it. 86X will not copy, load, or derive Demonstration Data from Client Personal Data, including in de-identified or modified form, and Customer will not enter personal data of real individuals into a Demonstration Organization or into any organization 86X has designated for demonstration or testing.

**1.6 Product schedules.** Schedule P applies only where Customer holds an Entitlement to People Partner, and Schedule V applies only where Customer holds an Entitlement to Compliance Boards AI. Each is accepted when Customer activates that product. Where a schedule and the rest of this Addendum conflict on that product's data, the schedule governs.

---

## 2. Details of processing

**2.1 Subject matter and duration.** 86X processes Client Personal Data to provide the Software, for the duration of Customer's Entitlement and the retention periods in §6.

**2.2 Nature and purpose.** Hosting, storage, transmission, text extraction, generation of content from extracted text, automatic reading of documents, determination of jurisdictions from business addresses, and delivery of messages and notifications, in each case to provide, maintain, and support the Software for Customer.

**2.3 Categories of data subjects.** Customer's personnel, including current and former employees, applicants, and managers; personnel of operators of Customer's locations; Customer's contacts, customers, and prospective customers; and any individual identified in material Customer uploads or records in the Software.

**2.4 Categories of Client Personal Data.** Contact records and identifiers; rosters and personnel records; interaction data; the content and metadata of messages sent to and received from Customer's contacts on Customer's behalf, including inbound reply bodies, as stored in the interaction timeline; and **documents and records that Customer uploads or otherwise makes available to 86X for the purpose of preparing Customer's playbook — including employee handbooks, personnel and workplace policies, organizational charts, and similar operational documents — together with text extracted by 86X from those documents and content generated from that extracted text.**

**Customer determines what it uploads.** 86X processes uploaded documents, extracted text, and generated content solely to prepare and maintain Customer's playbook under Customer's instructions, and discloses extracted text to the AI sub-processor identified in §4.2 for that purpose only.

Where Customer holds an Entitlement to People Partner or to Compliance Boards AI, 86X also processes the categories described in **Schedule P** or **Schedule V**, as applicable.

**2.5 Special categories.** Except as described in **Schedule P** for Customers holding an Entitlement to People Partner, 86X's processing is **not** intended to include special categories of personal data. See §5 (Excluded Materials).

---

## 3. 86X's obligations

**3.1 Instructions only.** 86X will not process Client Personal Data for its own purposes, will not sell it, and will not share it for cross-context behavioural advertising.

**3.2 Confidentiality of personnel.** 86X ensures that personnel authorized to process Client Personal Data are bound by an obligation of confidentiality and access it only as needed to provide the Software.

**3.3 Security.** 86X maintains technical and organizational measures appropriate to the risk, including encryption of data in transit and at rest, access controls that restrict access to Client Personal Data to authorized personnel, tenant isolation between customer organizations, logical separation of environments, and logging of administrative access. **86X does not hold a SOC 2, ISO 27001, or comparable third-party certification, and makes no representation that it does.**

**3.4 Assistance.** Taking into account the nature of the processing and the information available to it, 86X will provide reasonable assistance to Customer in responding to requests from individuals exercising their rights, and in Customer's obligations relating to security, breach notification, and data protection impact assessments.

**3.5 Disclosure to the AI sub-processor.** Content disclosed to the AI sub-processor, including extracted text and, for Compliance Boards AI, document images, is processed by that sub-processor to generate output and is **not used by it to train its models**. That sub-processor does not retain inputs or outputs beyond its ordinary retention cycle, which is **no more than thirty (30) days from receipt**, and does not retain them at all where zero-retention terms apply, in each case **subject to that sub-processor's retention of flagged content and safety records as required for legal compliance and misuse prevention.** 86X cannot issue a per-customer deletion instruction for those inputs, and §6.1 is qualified accordingly.

---

## 4. Sub-processors

**4.1 Authorization.** Customer authorizes 86X to engage the sub-processors listed in §4.2. 86X imposes data protection obligations on each sub-processor that are no less protective than those in this Addendum, and remains responsible for their performance.

**4.2 Current sub-processors.**

| Sub-processor | What it does | Where |
|---|---|---|
| **Supabase, Inc.** | Application database and file storage — hosts Client Personal Data | United States (us-east-1) |
| **Anthropic, PBC** | AI processing — (i) receives text extracted from documents Customer uploads, to generate playbook content; and (ii) for Compliance Boards AI, receives images and text of documents Customer uploads, to read document type, dates, numbers, and names. Only copies 86X has re-encoded without embedded metadata, or extracted text, are sent; original files are not. Employee certification records are sent only where Customer has turned this on, as described in Schedule V, V3.1, and those of minors are never sent. Documents are sent for reading according to the category they were uploaded under; if a document is uploaded under the wrong category, it may be sent before it is recognised, and 86X then discards the result and stores nothing read from it | United States |
| **Cloudflare, Inc.** | Encrypted backup archive — stores an independent backup copy. **Encrypted by 86X before transmission; Cloudflare holds ciphertext it cannot read.** For Compliance Boards AI, will route inbound email sent to store intake addresses, including attachments, to 86X, and protect inspector pages against network abuse, once those features are enabled | North America |
| **Vercel Inc.** | Application hosting and delivery, including the server functions of the Compliance Boards AI web application | United States |
| **Railway Corporation** | Hosting of 86X's back-end services: document processing (receives documents Customer uploads, to extract text and prepare display and export copies); evaluation of which compliance requirements may apply to Customer's locations (receives location and business-profile details); preparation of PDF copies of Customer's playbook; jurisdiction lookup (receives business addresses only); and 86X's backup service, which reads Client Personal Data, including uploaded documents, and encrypts it before sending it to the backup archive | United States |
| **Twilio Inc.** | SMS delivery — applies only where Customer uses messaging features | United States |
| **Resend (Plus Five Five, Inc.)** | Email delivery — sign-in codes and account emails, including invitations; Compliance Boards AI notifications; and messages, where Customer uses messaging features | United States |

**Public government services.** To determine which jurisdictions a Compliance Boards AI location is in, 86X sends the location's business address, and no other data, to the U.S. Census Bureau's public Geocoder. The Census Bureau is not engaged by 86X under contract and is not a sub-processor. Its handling of requests is governed by its own privacy policy.

**4.3 Changes.** Before a new sub-processor begins processing Client Personal Data — **and before an existing sub-processor's processing is materially expanded** — 86X will publish an updated version of this Addendum and notify Customer by email to the address associated with Customer's account. Customer may object on reasonable data-protection grounds within **thirty (30) days** of notice. The parties will work in good faith to resolve the objection, and if it cannot be resolved Customer may terminate the affected Software without penalty.

**4.4** An update to §4.2 is a non-material change under §12.1 of the Platform Terms and does not require re-acceptance. The notice and objection right in §4.3 applies regardless.

---

## 5. Excluded Materials and Customer's obligations

**5.1 Excluded Materials.** This §5.1 applies to documents and files Customer uploads, and to content Customer transmits through messaging features. Records Customer creates through People Partner's features are governed by **Schedule P**, and documents uploaded to Compliance Boards AI are further governed by **Schedule V**, each of which includes its own scoping. Customer will not upload or otherwise make available to 86X any of the following:

(a) individual employee medical, health, disability, accommodation, workers' compensation, or leave-of-absence records;

(b) individual disciplinary, grievance, or workplace-investigation files;

(c) benefits enrolment or claims files;

(d) payroll files, tax forms, Forms I-9, or any document containing Social Security or other government identification numbers;

(e) records of any individual's racial or ethnic origin, religious or philosophical beliefs, political opinions, trade-union membership, sex life or sexual orientation, or genetic or biometric data; or

(f) any personal data relating to a data subject located in the European Economic Area, the United Kingdom, or Switzerland, unless the parties have first executed appropriate cross-border transfer terms.

**5.2** Customer represents that materials it uploads are limited to organizational and policy documents of the kinds described in §2.4, or, for Compliance Boards AI, the documents described in Schedule V, and are free of Excluded Materials.

**5.3** **86X does not request Excluded Materials and does not review uploads for them.** On becoming aware that Excluded Materials have been uploaded, 86X will delete the document and any text extracted from it and notify Customer.

**5.4 Notices and lawful basis.** Customer is the controller of personal data contained in materials it uploads. **Customer represents that it has provided all notices and has a lawful basis required for 86X to process those materials as described in this Addendum, including any notice to Customer's personnel regarding processing by 86X and its sub-processors.**

---

## 6. Retention and deletion

**6.1 Return and deletion on termination.** Within **ninety (90) days** after termination or expiration of Customer's Entitlement, or on Customer's earlier written request, 86X will, at Customer's election, return and/or delete all Client Personal Data from 86X's production systems, **including the interaction timeline (inbound and outbound message content and metadata), documents uploaded by Customer, text extracted by 86X from those documents, and playbook content generated from that extracted text.** Deletion from production is performed on a defined internal runbook and **verified** — confirming no Customer records remain — and includes purging Customer's message logs held by 86X's messaging sub-processors.

86X will instruct its sub-processors to do the same, **except that inputs disclosed to 86X's AI sub-processor are deleted on that sub-processor's ordinary retention cycle as described in §3.5, rather than on 86X's instruction.**

**Excluded from return and deletion.** The following are not subject to return or deletion under this §6.1:

**(a) Acceptance, confirmation and acknowledgment records.** 86X's records of (i) Customer's acceptance of the Platform Terms, this Addendum, and any product schedule or subscription terms; (ii) confirmations given on Customer's behalf in the Software, such as a confirmation that Customer has the right to see an operator's documents; and (iii) acknowledgments of notices shown in the Software — comprising Customer's organization, the individual who accepted, confirmed or acknowledged, the operator a confirmation or acknowledgment relates to, the date and time, and the version of each text — are records of the formation and terms of the agreement between the parties (together, **"acceptance records"**). **86X holds these records as a controller in its own right, and not as a processor acting on Customer's instructions**, and retains them to evidence the terms in force between the parties and for the establishment, exercise and defence of legal claims. They are retained in accordance with §6.5.

**(b) De-Identified data**, to the extent §6.4 applies.

**6.2 Backup retention and roll-off.** Client Personal Data may persist in 86X's **encrypted, access-restricted** backup systems after deletion from production, solely for disaster-recovery and business-continuity purposes, until those backups expire or are overwritten on their ordinary retention cycle. 86X maintains (a) managed database backups on a rolling **seven (7) day** cycle and (b) an independent, encrypted backup archive covering both database records and uploaded files, retained on a tiered schedule under which the oldest copy is retained no longer than **thirteen (13) months**.

Accordingly, residual copies of deleted Client Personal Data — **including uploaded documents, extracted text, and generated content** — are fully purged from all backup systems **no later than thirteen (13) months** after deletion from production. While held in backup, such data remains encrypted, access-restricted, and is **not used for any active processing**; 86X will not restore deleted Client Personal Data except as necessary to recover from a disaster or system-loss event, and any data so restored will be re-deleted in the ordinary course.

**6.3 Data location.** Client Personal Data and 86X's backups are hosted in the United States. If and when 86X offers the Software with respect to data subjects in the EEA, the United Kingdom, or Switzerland, the parties will enter appropriate cross-border transfer terms at that time. See §5.1(f).

**6.4 De-identified data.** This Addendum does **not** itself grant 86X any right to create, retain, or use de-identified data derived from Client Personal Data, and does not limit any such right expressly granted to 86X under a separately executed agreement between the parties. Where such a right applies, data de-identified in accordance with that agreement is not Client Personal Data for the purposes of §6.1.

**6.5 Retention of acceptance records.** 86X retains acceptance records until **seven (7) years** after the later of (a) termination or expiration of Customer's Entitlement and (b) the date on which the accepted, confirmed or acknowledged version of the relevant text ceased to be in force, after which they are deleted in the ordinary course. Technical metadata recorded at the time of acceptance, including the originating IP address and browser user-agent string, is held in 86X's audit records and is deleted on the audit-record retention cycle, which is **twenty-four (24) months** from the event, except where a record is subject to a legal hold or relates to an open security incident or dispute. Retention of these records is further described in the 86X Privacy Notice.

**6.6 What "delete my account" means.** Because 86X retains the acceptance records described in §6.1(a) and §6.5, closing Customer's account results in Customer's organization record being **emptied and closed rather than erased.** The retained record comprises Customer's organization name, the name and email address of each individual who accepted, confirmed or acknowledged, the operator a confirmation or acknowledgment relates to, the dates, and the versions. It contains no Customer Content.

---

## 7. Individual rights requests

**7.1** Where an individual makes a request to 86X relating to Client Personal Data, 86X will not respond directly except to confirm receipt and to direct the individual to Customer, and will notify Customer promptly.

**7.2** 86X will provide Customer with reasonable assistance, taking into account the nature of the processing, to enable Customer to respond to such requests, including by making Client Personal Data available to Customer through the Software.

**7.3** §7.1 does not apply to a request that concerns data 86X holds as a controller under §1.4; 86X handles those requests itself, as described in the 86X Privacy Notice.

**7.4** Where People Partner is designed so that Customer cannot access certain data (private Wellbeing Entries under Schedule P §P4), Customer's personnel may access, export, and delete that data themselves through the Software. 86X may respond directly to a verified request from the individual concerning their own private Wellbeing Entries and will notify Customer that a request was handled, without disclosing its content.

---

## 8. Security incidents

**8.1** 86X will notify Customer **without undue delay, and in any event within seventy-two (72) hours,** after becoming aware of a personal data breach affecting Client Personal Data.

**8.2** The notice will describe, to the extent known: the nature of the breach and the categories and approximate volume of data and individuals affected; the likely consequences; the measures 86X has taken or proposes to take; and a contact point. 86X will supplement the notice as further information becomes available.

**8.3** 86X will take reasonable steps to contain and remediate the breach and will cooperate with Customer's reasonable requests in connection with Customer's own notification obligations. A notification under this §8 is not an acknowledgement of fault or liability.

---

## 9. Information and audit

**9.1** On Customer's reasonable written request, and not more than once in any twelve (12) month period, 86X will make available information reasonably necessary to demonstrate compliance with this Addendum.

**9.2** 86X holds no third-party security certification or audit report (see §3.3). Where Customer requires an on-site or third-party audit, the parties will agree its scope, timing, and cost in advance, and Customer bears the cost.

---

## 10. Relationship to the Platform Terms

**10.1** This Addendum forms part of the Platform Terms. In the event of conflict between this Addendum and the rest of the Platform Terms regarding the processing of Client Personal Data, this Addendum governs.

**10.2** Each party's liability under this Addendum is subject to the limitations in §11 of the Platform Terms.

**10.3** §13.2 of the Platform Terms (no displacement by silence) applies to this Addendum.

---

## 11. Changes to this Addendum

Changes to this Addendum are governed by §12 of the Platform Terms. Updates to the sub-processor list in §4.2 are non-material changes under §12.1 of the Platform Terms, subject to the notice and objection right in §4.3.

---

## 12. Survival

§§1.4, 1.5, 3.2, 6, 7.3, 7.4, 8, 10, **Schedule P §§P5.3, P6 and P8, Schedule V §§V6 and V7,** and this §12 survive termination.

---

## Schedule P — People Partner

**P1. Application.** This Schedule applies only where Customer holds an Entitlement to People Partner. It is accepted when Customer activates People Partner. If this Schedule and the rest of this Addendum conflict on People Partner data, this Schedule governs.

**P2. Data processed.** In addition to §2.4, 86X processes the following on Customer's behalf:

(a) **Employee records:** name, job title, work location, hire date, employment status, and Customer's own POS or HR system identifiers, plus the link between the record and the employee's sign-in, where one exists;

(b) **HR records** created in the Software: disciplinary records (step, category, incident date, description, manager, witness, signatures and acknowledgments, and the employee's written response), performance reviews (ratings, written assessments, goals, manager notes, signatures, and the employee's written response), corrections added to either, and People Partner role assignments;

(c) **Shift check-ins:** the employee's start- and end-of-shift scores and optional short reasons;

(d) **Wellbeing Entries:** voluntary self-assessments an employee completes about themselves, including self-rated physical and mental health and other life areas, with optional notes.

Wellbeing Entries, and any health information an employee chooses to include in a check-in reason or a written response, may include special categories of personal data. 86X processes them only as described in this Schedule.

**P3. Customer's responsibilities.** Customer is the employer and the controller of People Partner data. Customer:

(a) will give its personnel the notice required by applicable law before they use People Partner, covering what is collected, who in Customer's organization can see it, and that 86X processes it as Customer's service provider (86X provides a template notice on request);

(b) is solely responsible for its employment decisions and for meeting its own record-keeping, retention, personnel-file access, and employee-response obligations under applicable law, using the Software's export and retention features;

(c) will not use People Partner to record medical records, diagnoses, disability or accommodation information, workers' compensation information, leave-of-absence records, genetic information, or government identification numbers, and will instruct its managers accordingly;

(d) will not require, pressure, or reward any employee to complete, or to share, a Wellbeing Entry; and

(e) will not load real individuals' personal data into a Demonstration Organization (§1.5).

**P4. Wellbeing Entries.**

**P4.1 Private by default.** A Wellbeing Entry is visible only to the employee who created it unless that employee chooses to share it. Customer, Customer's managers, and 86X personnel acting through the Software cannot see an unshared Wellbeing Entry. See P7 for infrastructure access.

**P4.2 Sharing is the employee's choice.** An employee may share a Wellbeing Entry with authorized managers. Health-related areas and notes are shared only by a separate, specific choice. 86X records when an entry was shared or unshared and which version of the sharing notice the employee saw, but not the entry's content. Unsharing removes access from then on. It cannot recall what a manager has already seen.

**P4.3 No participation reporting.** The Software does not report to Customer whether, how often, or when an employee completes Wellbeing Entries.

**P4.4 Employee control.** An employee may export or delete their own Wellbeing Entries at any time while they have access to the Software.

**P4.5 No other use.** 86X does not use Wellbeing Entries for any purpose other than providing them to the employee, and to managers where shared. 86X does not create De-Identified Data from them, use them for product analytics, or disclose them to an AI sub-processor.

**P5. Integrity of HR records.**

**P5.1** An employee's acknowledgment of, refusal of, or written response to a disciplinary record or performance review is recorded only by that employee's own action in the Software. A refusal recorded by a manager in person is labelled in the Software as manager-recorded and requires a witness.

**P5.2** Disciplinary records cannot be altered after creation, except to add signatures, acknowledgments, and responses. Performance reviews lock once they are visible to the employee. Later corrections to either are added as separate amendments that the employee can see. Records that Customer removes are hidden from normal use and retained under P6.

**P5.3 Legal hold.** Customer may place a legal hold on any record or employee. While a hold is in place, the held records are not purged under P6 and are not deleted under §6.1 until Customer releases the hold or 86X returns the records to Customer.

**P6. Retention.** Subject to P5.3, §6.1 (termination) and §6.2 (backups):

| Data | Retention while Customer is active |
|---|---|
| Employee records | Until Customer deletes them, or §6.1 applies |
| Disciplinary records and performance reviews, including removed ones | Purged three (3) years after the later of the record date and the employee's termination date |
| Shift check-ins | Rolling twenty-four (24) months |
| Unshared Wellbeing Entries | Deleted thirty (30) days after the employee's access to Customer's People Partner ends; the employee may export them before then |
| Shared Wellbeing Entries, including separately shared areas | Rolling twenty-four (24) months, and deleted with unshared entries when access ends |

Customer is responsible for exporting any records it must keep for longer, before they are purged. On termination of Customer's Entitlement, 86X makes a full export available before deletion under §6.1.

**P7. 86X access.** The Software gives 86X platform staff no access to People Partner data. A limited number of 86X personnel with infrastructure administration rights, currently the founders of 86X, directly or through tools they operate, can technically access the underlying database. That access is used only to operate, secure, and recover the Software, or where required by law, and is logged. Customer-requested support involving People Partner data is carried out only with Customer's authorization and is logged.

**P8. No sharing beyond Customer.** People Partner data is processed only by 86X Ventures LLC and the sub-processors listed in §4.2. It is not made available to any other 86X affiliate or product except where Customer has an Entitlement to that product, the shared employee records in P2(a) are needed for it, and the processing entity is bound by this Addendum. Disciplinary records, performance reviews, shift check-ins, and Wellbeing Entries are never shared with another product.

**P9. AI features.** 86X does not disclose People Partner data to an AI sub-processor. Any future feature that would do so requires an update to this Schedule under §4.3, and will never include Wellbeing Entries.

---

## Schedule V — Compliance Boards AI

This Schedule was previously titled 'Compliance Vault'; references to that name mean Compliance Boards AI.

**V1. Application.** This Schedule applies only where Customer holds an Entitlement to Compliance Boards AI. It is accepted when Customer activates Compliance Boards AI, together with the 86X Compliance Boards AI Schedule to the Platform Terms. If this Schedule and the rest of this Addendum conflict on Compliance Boards AI data, this Schedule governs.

**V2. Data processed.** In addition to §2.4, 86X processes the following on Customer's behalf:

(a) **Business documents:** permits, licences, registrations, certificates, inspection reports, insurance certificates, and similar documents Customer uploads, and the information read from them, such as document numbers, holder names, premises addresses, issuing agencies, and dates;

(b) **Employee certification records:** food-handler, food-protection-manager, and similar certificates, and employment certificates or work permits for minors, including the holder's name, certificate type, issuer, number, and dates, and any date of birth printed on the document. 86X does not read dates of birth into separate fields or keep them from automatic reading;

(c) **Image metadata** embedded in uploaded files, which may include the location where a photo was taken and information about the device that took it;

(d) **Location information:** business addresses, store contact email addresses, and Customer's answers to business-profile questions;

(e) **Activity records:** who uploaded, reviewed, confirmed, dismissed, or added each document or requirement, and when;

(f) **Inspector access records:** when an inspection packet or share link was issued, opened, or ended, and which documents were viewed. These records contain no IP addresses and no inspector names;

(g) **Board-check records,** where Customer turns Board check on: photos of a location's compliance board, when each was taken, who took and who reviewed it and the result, and, where the user allows their device to share its location, the distance between the device and the location. 86X does not store the device's coordinates.

**V3. How Compliance Boards AI data is processed.**

**V3.1 Automatic reading.** Documents in the categories 86X permits for automatic reading are sent to the AI sub-processor identified in §4.2, as described in its row there. Only copies 86X has re-encoded without embedded metadata, or extracted text, are sent. Original files are not sent. Employee certification records are sent only where Customer's account owner has turned on automatic reading of employee certificates for Customer's organization in the Software; it is off unless turned on. Employment certificates and work permits for minors are never sent, even where it is turned on. A copy sent may show a date of birth printed on the certificate; 86X does not read dates of birth into separate fields or keep them from the reading. Customer's account owner may turn automatic reading of employee certificates off at any time in the Software, and Customer may ask 86X to turn automatic reading off for its organization at any time.

**V3.2 Original files.** 86X stores each uploaded file as received, so that it can show the file has not been altered. Original files are not sent to any AI sub-processor and are not shown in inspection packets or share links. Where the Software provides a file for download or export, it provides a copy with location and device information removed, unless an owner or administrator of Customer's organization specifically requests unaltered originals.

**V3.3 Jurisdictions.** To work out which jurisdictions a location is in, 86X uses the public government service described in §4.2 and boundary data from public sources.

**V3.4 Research.** The research that identifies potential requirements uses public government sources only. No Client Personal Data is used in it.

**V3.5 Board-check photos.** Board-check photos are not sent to any AI sub-processor.

**V4. Customer's responsibilities.** Customer:

(a) has the authority to upload each operator's documents and its personnel's certificates to Customer's account, and for Customer's administrators to see them as described in V5.1, and will give operators and their personnel any notice required by applicable law, including through the notice shown in the Software;

(b) will keep store email accounts used with the Software under its own control, as described in the Compliance Boards AI Schedule;

(c) will not upload documents containing Social Security numbers, Forms I-9, payroll or tax forms, or medical records. §5.1(d) does not apply to permit, licence, registration, or certificate numbers on documents uploaded to Compliance Boards AI.

**V5. Who can see what.**

**V5.1 Customer's administrators.** Customer's administrators see, and can review, the documents, employee certification records, board-check photos and related records of every location in Customer's account, including locations run by operators such as franchisees. For locations run by an operator other than Customer, this applies once Customer's account owner has confirmed in the Software, in the form shown there, that Customer has the authority described in V4(a). Until then, Customer's administrators see the status of each requirement at those locations. 86X records who confirmed it and when, and the operators' users are told through the notice shown in the Software.

**V5.2 Employee certification records and board-check photos.** V5.1 includes the names, images and details of employee certification records, including those of minors, and board-check photos, at every location to which it applies.

**V5.3 Inspectors.** An inspection packet shows only current copies of the documents in it, with location and device information removed. Employee certificates appear in a packet as a summary only (holder name, certificate type, issuer, number, and expiry date), with no image. Share links are limited to business documents and expire within seven (7) days.

**V5.4 Operators' own users.** An operator's own users see the documents and employee certificates of the locations that operator runs, and, where their role allows, its board-check photos.

**V6. Retention.** Subject to §6.1 (termination), §6.2 (backups), and any legal hold Customer places:

| Data | Retention while Customer is active |
|---|---|
| Current versions of documents | Until Customer deletes them, or §6.1 applies |
| Superseded versions of business documents | Seven (7) years after they are superseded |
| Employee certification records | Twelve (12) months after the later of the certificate's expiry and the date the employee is marked as departed or, for a certificate with no expiry date, twelve (12) months after the employee is marked as departed |
| Inspector access records | Two (2) years from the event |
| Board-check photos and their review records | Two (2) years from when the photo was taken, except that each location's most recent passed photo is kept until a newer photo passes |
| Activity records | As long as the document or requirement they relate to; copies in 86X's audit records follow the audit-record retention cycle in §6.5 |

Where an operator's access to Customer's account ends, the operator may export its locations' documents for ninety (90) days. After that, 86X deletes the operator's employee certification records from Customer's account. The operator's business documents remain with Customer only where Customer has the right to keep them.

Compliance Boards AI documents are included in the backup systems described in §6.2, including a write-protected copy that cannot be altered or deleted for up to thirty (30) days. The thirteen (13) month limit in §6.2 applies to them.

**V7. Aggregate counts.** 86X may compute aggregate counts of Customer's decisions about requirements, such as dismissals, together with other customers' decisions, solely to maintain the quality of its research. These counts contain no customer, location, or person names and no free-text reasons, are shown only where at least five (5) customers are counted, are used only by 86X, and are never shown to other customers.

**V8. 86X access.** 86X platform staff have no access to Customer's Compliance Boards AI documents through the Software. Infrastructure access is as described in Schedule P §P7, which applies equally to Compliance Boards AI data.

---

*86X Ventures LLC · Questions about this Addendum: privacy@86x.ai*