Version 1.3 dated 17 November 2026
This DPA sets out S.G. Systems, LLC’s obligations when it processes personal data on a Customer’s behalf. It covers processing instructions, security, support and Sub-processors, return and deletion, international transfers and the method by which the parties incorporate these terms into their Agreement.
The applicable Order identifies the legal Customer, ordered service, processing role, actual deployment and locations, effective date and accepted document version. The DPA becomes binding through Section 13. Existing accepted agreements and mandatory rights retain their effect unless validly varied.
The London service timetable distinguishes retrieval, disposal of active and archive copies, expiry of recovery copies and expressly agreed supplier residue. Shorter accepted deadlines prevail. The service record identifies actual measures and any outstanding qualification limits; this document does not itself certify completion of customer deletion or a transfer arrangement.
Contents
- Sections 1–4 Parties, definitions, roles and instructions
- Sections 5–8 Confidentiality, security, Sub-processors, assistance and breach response
- Sections 9–13 Return and deletion, audits, locations, transfers, AI and incorporation
- Schedule 1 Processing details and London disposition periods
- Schedule 2 Technical and organisational measures
- Schedule 3 Supplier and support processing chain
- Schedule 4 Transfer mechanisms and annex information
1 Parties and scope
1.1 This Data Processing Addendum (DPA) is between S.G. Systems, LLC, a Texas limited liability company with its principal office at 6944 Meadowbriar Lane, Dallas, TX 75230, United States (SG Systems), and the Customer legally identified in the applicable Order. V5 Ultimate and V5 Classic are product names, not contracting parties.
1.2 This DPA applies to personal data in Customer Data that SG Systems processes on Customer’s behalf when providing the Software, Provider Hosted Services, support or other ordered Services (Customer Personal Data). It applies only to data SG Systems actually receives, holds or accesses for that purpose.
1.3 This DPA applies whoever the Seller is. Reselling alone does not make the Seller SG Systems’ Sub-processor, or SG Systems the Seller’s Sub-processor. A Seller processing data independently in its own systems is responsible under its own Customer agreement. If SG Systems engages that Seller to process on SG Systems’ behalf, Section 6 applies and the actual party must be identified in Schedule 3 before processing.
1.4 SG Systems acts as an independent controller only for genuinely independent purposes, such as its own business relationship contacts, billing, tax and legal obligations, and Usage Data to the extent lawfully used for its own purposes under the Agreement and Privacy Notice. Tenant authentication, workspace administration and service security performed on Customer’s behalf remain processor activities. Calling a record security or billing data does not determine its role or justify retaining customer content.
1.5 For Customer Personal Data, this DPA prevails over inconsistent Order, EULA and other commercial provisions. Mandatory applicable transfer terms prevail over this DPA. Licence and intellectual-property terms are unchanged. Section 13 preserves existing agreements and requires express incorporation of this exact master before it becomes operative.
2 Definitions and interpretation
2.1 Applicable Data Protection Law means laws applicable to the covered processing, including, where applicable, the EU GDPR, UK GDPR and Data Protection Act 2018, Swiss Federal Act on Data Protection and United States state privacy laws. Controller, processor, data subject, personal data and supervisory authority have their applicable statutory meanings; business and service-provider equivalents are read accordingly.
2.2 Agreement means the applicable Order, EULA, applicable Seller commercial terms and SLA. Customer Data, Usage Data, Software, Provider Hosted Services, On-Premises, AI Features, Order, Seller and Services have the meanings in those documents. Sub-processor means a third party engaged by SG Systems to process Customer Personal Data on SG Systems’ behalf.
2.3 Personal Data Breach means a security breach leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Customer Personal Data processed by SG Systems or its Sub-processors. A breach affecting Provider Hosted Services is also a Security Incident under the SLA. Days in the disposition schedules are calendar days unless expressly stated otherwise.
3 Roles and Customer responsibilities
3.1 Customer is controller or a processor for its own controller. SG Systems acts as Customer’s processor or Sub-processor accordingly. Where Customer is a processor, it warrants that its controller authorised these instructions, SG Systems’ appointment and the authorised Sub-processors, and passes required notices to that controller. The actual processing, rather than the invoice route, determines the roles.
3.2 For V5 Ultimate Cloud and Private Cloud, the scope and duration are in Schedule 1. For On-Premises deployments, including V5 Classic, data remaining solely in Customer-controlled systems is outside SG Systems’ processing. This DPA covers support materials, remote sessions, logs, screenshots, exports and implementation or migration data that SG Systems actually receives or accesses.
3.3 Customer is responsible for lawful data and instructions, notices and lawful bases, its users and settings, and the permitted use of optional integrations and AI. Customer must not provide excluded categories in Schedule 1 without written agreement on the required scope and safeguards. Customer’s duties do not relieve SG Systems of its own obligations.
4 Documented instructions
4.1 SG Systems processes Customer Personal Data only on documented instructions, including for transfers. The Agreement, this DPA, authorised service configuration and authorised support requests constitute instructions. Additional instructions must be recorded in writing; a change in service scope or cost follows the agreed change process without displacing mandatory rights.
4.2 If EU or Member State law, UK law or another law recognised for this purpose by Applicable Data Protection Law requires other processing, SG Systems informs Customer before processing unless legally prohibited on important public-interest grounds. Other-country requests are handled under Section 11 and the applicable safeguards; they do not by themselves override data-protection restrictions.
4.3 SG Systems immediately informs Customer if it considers an instruction unlawful and may suspend the affected processing pending lawful clarification. SG Systems is not required to provide legal advice. A suspension does not exclude liability that cannot lawfully be excluded or excuse non-compliance with mandatory transfer terms.
4.4 SG Systems does not sell or share Customer Personal Data as those terms are used in applicable United States state privacy law, use it outside the direct business relationship or retain, use or disclose it for purposes other than performing the Agreement or as law permits. SG Systems does not use Customer Data to train AI models.
5 Confidentiality and security
5.1 Authorised personnel must be bound by confidentiality or an appropriate statutory duty, receive instructions appropriate to their work and access data only as necessary. Separate Provider companies and individuals are covered according to their actual role and engagement; individual confidentiality does not replace a necessary agreement with the supplying company.
5.2 SG Systems implements appropriate technical and organisational measures, taking account of the state of the art, cost, nature and context of processing and risk to individuals, including Schedule 2. Measures may be updated without reducing the overall protection. Planned or partially deployed controls must not be represented as verified universal safeguards.
5.3 Customer remains responsible for its accounts, credentials, devices, networks, identity providers and integrations and, for On-Premises, its infrastructure, backups and keys. SG Systems remains responsible for the security of processing within its own scope.
6 Sub processors and objections
6.1 Customer gives general written authorisation for the actual Sub-processors in Schedule 3, as changed under this Section. Optional providers process Customer data only when the relevant feature is enabled or used. The public list may also describe independent controllers; listing them does not authorise them as processors. Actual processing determines the role, including when Customer credentials are used.
6.2 SG Systems imposes written duties providing at least the same level of data protection as this DPA, including sufficient guarantees for appropriate measures, and remains fully responsible to Customer for each Sub-processor’s performance of those duties. Authorised tasks, onward delegation, location and transfer safeguards must match the engagement.
6.3 SG Systems updates the list and emails Customer’s designated contact at least 30 days before a new or replacement Sub-processor begins processing. An emergency replacement necessary for security or continuity may use shorter notice, given as soon as practicable, preserving objection and mandatory rights. SG Systems coordinates shorter downstream supplier deadlines without shortening Customer’s rights.
6.4 Customer may object in writing on reasonable data-protection grounds within the notice period. SG Systems and, where relevant, the Seller coordinate one process; Customer need not object twice. The 30-day resolution period begins when either receives the objection. They assess an alternative provider, configuration or service scope in good faith.
6.5 If no suitable alternative is available within that period, Customer may terminate the affected processing Services by written notice. For direct SG sales, SG Systems waives future affected subscription charges and related early-termination or buyout charges and refunds unused prepaid affected subscription fees within 30 days after termination. Delivered services, unrelated hardware and implementation work are not refunded by this remedy; unaffected services continue.
6.6 For a qualifying reseller Order to which the executed D5 master and Annex A apply, its coordinated remedy governs: the Seller waives those future affected charges, including a four-year subscription, and makes the affected unused-prepayment refund within 30 calendar days. SG–Seller settlement does not delay Customer’s remedy. This DPA does not unilaterally bind a Seller that is not a party; application to an existing Order follows its amendment or renewal formalities. Mandatory statutory and transfer rights remain unaffected.
7 Assistance and rights
7.1 Taking account of the nature of processing, SG Systems assists through appropriate measures, insofar as possible, with data-subject requests. Standard administration and export functions are the primary means. SG Systems promptly refers direct requests to Customer and does not otherwise respond except as legally required.
7.2 Taking account of information available, SG Systems assists Customer with security, breach notification, impact assessment and supervisory-authority consultation, including reasonable information requests. Mandatory assistance is not conditional on extra payment. Reasonable pre-agreed charges may apply only beyond statutory or DPA duties or for assistance arising from Customer’s non-compliance, without delaying a mandatory deadline.
8 Breach response
8.1 SG Systems notifies Customer without undue delay and in any event within 72 hours after becoming aware of a Personal Data Breach. Awareness, not later confirmation, starts the period. A shorter applicable legal or agreed period prevails.
8.2 The notice provides the known nature, categories and approximate numbers of data subjects and records, likely consequences, mitigation and a contact. Missing information follows in phases without undue further delay. For Provider Hosted Services, a detailed incident report follows within three business days of the initial notice, supplemented as facts develop.
8.3 SG Systems takes reasonable containment and mitigation steps and cooperates with Customer’s notifications. Customer determines its regulatory and data-subject notices unless law requires SG Systems to notify directly. Notification does not admit fault. A Seller independently processing in its own systems remains responsible for those systems; coordination does not extend any deadline.
9 Return deletion and residual copies
9.1 At the end of covered Services, SG Systems, at Customer’s choice, deletes Customer Personal Data or returns it and then deletes remaining copies, subject to actual applicable legal retention and the expressly agreed finite residual periods in Schedule 1. Return does not authorise indefinite retention.
9.2 Standard supported exports are available during the subscription and the ordinary 90-day post-termination retrieval period for Provider Hosted Services, subject to agreed lawful restrictions and payment of undisputed amounts under the Agreement. Payment conditions do not defeat mandatory rights. Custom formats require separate agreement. A later internal case or approval does not restart the retrieval period.
9.3 Active systems and non-instructed archives are disposed of after retrieval or on an earlier written deletion instruction as stated in Schedule 1. An archive setting is an operational control, not a legal basis. Continued Customer-directed archival retention requires an identified purpose, records, restricted access and a fixed end date. There is no blanket 15-year post-termination retention rule for new London Orders.
9.4 Recovery copies remain protected and outside ordinary use, are used only for authorised disaster recovery and expire under the applicable finite schedule. Before restored service access, SG Systems applies the independent current disposition and hold register, checks suppression and verifies affected access. A case record restored from the same old backup is not the independent current register.
9.5 SG Systems records actual legal-retention grounds, minimum data, purpose, access restrictions, review date and release condition and informs Customer unless prohibited. Customer’s own regulated-record obligations do not automatically impose an independent SG retention duty. Technical latency, supplier policy and immutable audit design are not themselves legal holds.
9.6 Customer exports and retains its required regulated records under its quality system. Application immutability protects integrity but does not remove SG Systems’ obligation to implement lawful offboarding. Shared identities and unrelated customer/control records must be preserved while attributable customer content and access are addressed.
9.7 On request, SG Systems supplies a written statement of actual completed disposal, remaining recovery or supplier residue and retained exceptions. It distinguishes active deletion, SG irrecoverability and final supplier deletion. A certificate must not describe unverified classes as deleted. Obligations continue while copies remain. Mandatory SCC or other transfer deletion and certification duties are not reduced to an on-request-only obligation.
10 Information and audits
10.1 SG Systems supplies information necessary to demonstrate this DPA and applicable Article 28 compliance, including reasonable security answers and available hosting assurance reports under confidentiality. A hosting provider’s report covers that provider, not SG Systems as a whole.
10.2 Where that information is insufficient, a supervisory authority requires it or a breach warrants it, SG Systems allows and contributes to audits, including inspections, by Customer or its confidential independent auditor. Ordinarily these are remote where practicable, in business hours, on 30 days’ notice and no more than once in 12 months; urgent regulatory or breach circumstances and mandatory rights prevail.
10.3 Audits protect other customers, security-sensitive information and material SG Systems cannot lawfully disclose; a reasonable alternative is provided. Each party bears its own costs, except reasonable additional on-site audit costs requested beyond ordinary frequency where no non-compliance is found. No notice, frequency, format or cost term restricts mandatory audit or transfer rights.
11 Locations and transfers
11.1 The ordered service profile identifies actual hosting and support routes. The London UK/Europe profile places the core hosted application, database, sign-in, files, archives and backups in London, United Kingdom. The other-region profile uses Oregon application/database/sign-in/files and United States multi-region independent recovery copies. A profile is not proof that a particular Customer workspace uses it.
11.2 London does not mean all copies or access remain in the EU, EEA or UK. US-hosted HiVE support, authorised international personnel, infrastructure metadata and enabled email, SMS or AI involve the routes in Schedule 3. SG Systems records the actual service-specific parties, purposes and locations rather than treating a country field or website routing as residency evidence.
11.3 Before a restricted transfer, the actual parties establish an applicable lawful mechanism under Schedule 4, including eligibility, completed annexes and binding execution where required. SG Systems ensures lawful onward arrangements and supplementary safeguards for its Sub-processors. Incorporation of a form does not validate an ineligible instrument or permit unqualified access.
11.4 For public-authority requests SG Systems reviews legality, challenges where legally appropriate, notifies Customer unless prohibited and discloses only the minimum lawfully required, subject to the applicable instrument. SG Systems does not claim its own Data Privacy Framework certification.
12 AI features
12.1 AI processing occurs only for features within the ordered scope that Customer enables or uses; no AI feature is represented for V5 Classic. Submitted content may include personal data and is routed through the applicable gateway and model provider identified in Schedule 3.
12.2 Provider retention follows the actual applicable terms, which must be consistent with this DPA and law. This DPA makes no zero-retention or Europe-only AI commitment. SG Systems does not train models on Customer Data. Authorised human review is required before regulated or consequential action; AI output is not an electronic signature or release decision.
13 Incorporation term and continuity
13.1 This master binds the parties only when an Order, signed acceptance or other binding written agreement expressly identifies and incorporates its exact title, version and applicable schedules, with SG Systems’ signature or express acceptance. Publication, a website link or continued use alone does not incorporate it.
13.2 The executed Reseller DPA and SQA Master Agreement SG-UK-DPA-SQA-MASTER-2026-10-22-D5 and Annex A provide standing acceptance for qualifying Orders through Audit Trail Technologies Limited or SG Traceability Systems Limited. Their original covered versions are DPA 1.0 and, where selected, SQA 1.11. A later master requires express SG approval of that exact complete package and its applicable Order incorporation; D5 is not automatic approval of future versions. A conforming approved Order requires no further discretionary SG countersignature; registration is administrative evidence, not a new acceptance gate.
13.3 This DPA does not vary an existing Order, DPA, signed D5 or Provider agreement merely by its preparation or publication. Existing terms change only by their applicable renewal or written-amendment method. The commercial term, deposit and unrelated obligations are unchanged. A longer retention period does not override a shorter accepted commitment without express valid agreement.
13.4 Once incorporated, this DPA continues throughout covered processing, retrieval and residual retention. Later versions apply only through renewal or written agreement, except legally required changes notified and discussed in good faith. Accepted versions remain identifiable and available.
13.5 Liability follows the governing Agreement, including EULA Section 14 and applicable Commercial Terms Section 17, with no double recovery. Nothing limits non-excludable liability, data-subject rights or liability under mandatory transfer terms to the extent those terms prohibit limitation.
13.6 Data-protection notices go to support@sgsystemsglobal.com or the designated Order contact. Customer maintains its breach and change-notice contact. Governing law follows the Agreement except where Applicable Data Protection Law or mandatory transfer terms require otherwise.
Schedule 1 Processing details
This Schedule describes the ordered processing. The accepted Order identifies the actual service, deployment, legal Customer, role and dates. The London disposition periods below apply to the London service when this version is incorporated under Section 13, subject to shorter applicable commitments and the express exception requirements below.
| Field | Processing description |
|---|---|
| Subject matter | V5 Software, ordered hosted service, support and implementation, validation or migration Services actually ordered. |
| Duration | Service term, applicable retrieval period and finite residual retention; any instructed archive or actual legal hold is separately recorded. |
| Operations | Hosting, recording, storage, retrieval, display, transmission, authentication, permissions, audit and signature attribution, support, export, backup, recovery and deletion. |
| Purposes | Operating Customer-configured manufacturing, quality, inventory and traceability workflows; securing, supporting and maintaining the service; documented instructions. |
| Data subjects | Authorised users, operators and contractors; contacts at Customer, its customers and suppliers; other individuals whose data Customer lawfully submits. |
| Data categories | Business identity/contact data, user identifiers and authentication metadata, roles, permissions and training; audit/signature user, time, reason and before/after values; configured records, free text, files and enabled notification details. |
| Excluded categories | Special-category and health/patient data, criminal-offence data, government identifiers and payment-card data, unless separately agreed with additional safeguards. Merchant-of-record card processing is outside the application. |
| Frequency | Continuous for hosted services; case-specific for On-Premises support. Optional supplier transfers occur only with the relevant enabled/used service. |
London disposition timetable
The ordinary timetable runs from actual effective termination. An agreed earlier deletion instruction uses a 30-day active-disposal period from that instruction, subject to mandatory deadlines, actual legal retention and the agreed scope. A case created later does not reset a contractual clock.
| Copy or stage | Outer boundary | Required treatment |
|---|---|---|
| Return and retrieval | 90 days after termination | Provide the instructed supported return/export; keep data protected during retrieval. |
| Active and non-instructed archive copies | 30 days after retrieval ends, ordinarily day 120 | Dispose of attributable active/private records, protected before-images, files, managed exports, queues and SG-held support copies; verify each class. |
| SG-restorable recovery residue | 90 days after actual active disposal, ordinarily no later than day 210 | Keep outside ordinary use; apply current disposition/hold instructions and independently verify suppression before restored access. |
| Google final-system residue | Expressly agreed exception up to 180 days after the applicable SG-irrecoverability customer-deletion trigger | Record actual trigger and supplier completion boundary; distinguish supplier-inaccessible residue from SG-restorable copies. |
| Google required infrastructure audit metadata | Expressly agreed exception of 400 days after the event | Restrict to necessary security/administration metadata and purpose; global handling is disclosed. It is not an operational archive or statutory hold. |
| Customer-instructed archive or actual legal retention | Recorded fixed end date or specific lawful release condition | Identify records, authority, purpose, minimum fields, restrictions and review; dispose of data once the basis ends. |
A shorter applicable SLA, DPA, mandatory transfer instrument or accepted deletion deadline prevails. The 90-day recovery cap does not extend a shorter accepted backup or deletion period. A service requiring a different cap or the Google exceptions must expressly identify and accept that variation in the applicable Order and SLA. Existing agreements retain their accepted terms unless validly varied.
Disposition method and evidence
S1.1 SG Systems maintains an exact customer/workspace copy inventory, including active and private databases, shared identity/access, private objects and versions, SG-controlled exports, queues and in-flight work, US support, delivery/AI suppliers, recovery copies and independent-purpose security/billing records. An inventory of table references is not a count of unique copies.
S1.2 Execution uses recorded instructions and exact scope, screens holds and shared records, preserves unrelated data and attribution, and records class-specific receipts. Object disposal removes the instructed storage objects; a successful API acknowledgement is independently checked for authenticated absence and required metadata preservation. Source-row deletion or account disablement alone is insufficient.
S1.3 Support copies, chats, diagnostics, attachments and derived exports held in HiVE or other SG systems use the same active-disposal deadline. Shared records are classified before action. Unattributed, failed or uncertain outcomes are recorded and escalated; an uncertain deletion is not blindly replayed.
S1.4 Recovery expiry, soft-delete windows and supplier residue are tracked separately. Lifecycle settings do not prove irreversible purge. Google’s final-system period runs from its applicable customer-deletion trigger, not automatically from service termination or termination of SG’s entire Google agreement. Supplier latency is not relabelled a legal hold.
S1.5 Required audit metadata can contain account/principal, IP, user-agent and resource/change references. Unexpected operational content requires investigation and a defined treatment. Independent billing, suppression and security records require an actual role, minimal fields, purpose and finite retention or lawful review condition. No supplier’s general policy permits indefinite content retention.
S1.6 Completion statements separate actual active disposal, SG-restorable expiry, supplier final deletion and retained exceptions. Full completion is not asserted while a required class is unresolved. Independent-current-register recovery checks, denied application access where required and preservation evidence are retained with the case.
Schedule 2 Technical and organisational measures
These measures apply to the ordered processing. SG Systems maintains evidence of the measures implemented for that scope and supplies appropriate information under Section 10. A device-specific test, source test or provider report is not evidence of universal implementation.
S2 1 Service and data security
Connections to hosted services use TLS; hosted data and backups are encrypted. Service access enforces Customer workspace scope and role permissions, including database row-level controls where used. Administrative and service credentials remain server-side; secrets are stored in an encrypted secret manager. Technical algorithms and per-layer details are supplied through controlled security review rather than inferred from a hosting provider’s marketing or certification.
S2 2 Staff and support access
Access must have an identified person or supplying company, approved task, customer/workspace scope, working country, start, expiry and accountable approver. Privilege is limited to the task; elevated access is separately justified. The approved support-policy design uses up to seven days for read access and four hours for elevated access. A longer assignment needs an express documented exception, not an implicit renewal.
Staff access to Customer data requires appropriate MFA, an attributable identity and a device meeting the recorded encryption, credential-required return, locking and patch requirements. Download, export and local retention restrictions must be appropriate to the task. Routine owner impersonation is not a substitute for scoped support permissions. Access and sessions are revoked or expire when the need ends, and a restore must not silently recreate withdrawn access.
Each Customer assignment must be approved against the actual ordered service, current need and lawful processing route. SG Systems verifies effective permissions and sessions when access is no longer needed. Unknown working countries, device status or effective roles are not treated as approved.
S2 3 Devices and recovery custody
Support devices require active disk protection, protected authentication material, credential-required return after locking and sleep, a defined idle-lock limit and timely security updates. SG maintains a company-controlled recovery arrangement with limited authorised access and independent availability, without exposing recovery secrets in routine evidence. A live boot-recovery test is distinct from a private key-retrieval check.
S2 4 Integrity monitoring and incident handling
Regulated changes, signatures and overrides retain appropriate user, time, reason and before/after attribution. Application audit immutability is maintained, while lawful offboarding uses controlled procedures that preserve unrelated records. Monitoring, alerting and documented incident response address security events, sign-in abuse and unusual exports within the ordered service. Section 8 governs Customer notice; incident coordination does not extend its deadlines.
S2 5 Backup and restored service
Backup intervals and recovery objectives follow the accepted SLA and service profile. Recovery testing records scope and failures. Disposed data is suppressed against an independent current register before restored application access, with preservation and access-denial readback. A database dump, isolated test or suppressed single file is not a full application or HTTP recovery qualification.
S2 6 Organisational controls and assurance
Personnel confidentiality, written Sub-processor duties, change review, supplier/location review and retained evidence support these measures. SG Systems does not hold ISO 27001, SOC 2 or Cyber Essentials certification or attestation. Supplier reports describe those suppliers. Mandatory audit rights remain intact. For On-Premises services, Customer is responsible for its infrastructure; support materials SG Systems receives remain subject to these applicable duties and finite retention.
Schedule 3 Supplier and support processing chain
This Schedule identifies the supplier and support processing chain for the ordered service. It distinguishes SG Systems’ direct contracting parties, downstream infrastructure and independent controllers. Locations include storage and potential remote processing; they are not access assignments. Optional processing occurs only for the service actually enabled or used.
| Party or route | Service and role | Location and qualification |
|---|---|---|
| Supabase Pte. Ltd. | Direct SG database, Auth and Storage supplier under the verified organisation purchase and terms route. AWS is downstream, not a direct SG engagement merely because Supabase uses it. | London for the UK/Europe core profile; Oregon for other-region and existing HiVE support database. Contracting-entity domicile is distinct from selected hosting. |
| Google LLC | Hosted application, independent backups/archives, infrastructure logging and control plane. | London core profile; Oregon HiVE application and other-region application; US multi-region copies for other-region profile. Required global audit and final deletion exceptions are in Schedule 1. |
| Plus Five Five, Inc. trading as Resend | Transactional and sign-in mail under the company-authorised account and supplier DPA. | US content and log handling. A UK sender or callback does not regionalise the supplier’s stored content. Upstream 30-day change rights must be coordinated. |
| OpenAI OpCo, LLC when AI is used | Model processing under the company API account and applicable standard terms/DPA. | United States/global processing and standard supplier retention; optional sharing is disabled for the identified company account. No European-only or zero-retention commitment unless separately agreed. |
| Google Gemini Developer API when used | Optional model processing through the verified SG project/billing correspondence and separately applicable terms. | Applicable model and terms govern processing and retention. Google Cloud CDPA acceptance alone is not Gemini Developer API evidence. |
| Twilio when SG engages or instructs it | Enabled SMS and associated delivery metadata under actual account/terms. Customer-direct contracting is classified separately. | The identified route is us1. Actual per-item deletion and supplier residue follow the applicable terms; shared settings alone do not establish customer-specific purge or Europe-only processing. |
| Existing SG HiVE support route | SG-operated support, messages, chats, attachments, selected workspace/user context and diagnostics; underlying suppliers remain those identified above. | United States, including Oregon database and us-west1 application. It is a separate copy and access route from London hosting. |
| Lovable Labs Inc. where the actual feature routes through it | Gateway or other processing only to the extent Customer Personal Data actually traverses the enabled service. It is not used as a substitute name for Resend or the model supplier. | United States/global. The applicable gateway, legal counterparty and terms must match the enabled feature before processing begins. |
Independent controllers and Customer services
Paddle’s merchant-of-record billing is treated according to its independent controller role and Data Sharing Addendum, not as processing manufacturing records for SG. Customer-directed identity providers, integrations and a genuinely Customer-direct Twilio relationship follow their actual contracts and instructions. A billing webhook, credential owner or commercial reseller label alone does not establish the legal role.
Support Provider authorisation
SG’s twelve executed Provider packs cover the actual individuals or supplying companies and SG countersignatures. Their authenticated originals remain in the restricted register. Before a Provider processes a Customer’s data, the applicable named-recipient schedule must identify the legal party, named operator where relevant, task, workspace, approved working country, period, safeguards and lawful onward route. The restricted named schedule forms part of the accepted service record and is disclosed through a controlled channel where required; listing a signed Provider is not blanket approval for every Customer or reported country.
The wider Provider register reports working locations in the United Kingdom, Uruguay, Australia, Venezuela, Argentina and Spain. These reported locations do not themselves authorise access for a Customer or establish a lawful transfer route. Only the actual approved countries, recipients, tasks and safeguards recorded for the ordered service are permitted.
The applicable Order and service record identify the supplier services and legal counterparties actually used. A route with unresolved eligibility, terms or safeguards must not be enabled for that Customer. Inclusion in this Schedule does not grant a person access or establish that supplier final deletion has occurred.
Schedule 4 Transfer mechanisms and annex information
This Schedule applies only to actual restricted transfers. The exporter is the actual controller or processor, not automatically the invoicing reseller. The importer for Customer-to-SG processing is S.G. Systems, LLC, 6944 Meadowbriar Lane, Dallas, TX 75230, United States; contact Simon Hartley, authorised signatory, through support@sgsystemsglobal.com. The accepted Order and transfer record supply the actual exporter’s legal identity, address, contact, role, authority, signature and effective date.
S4 1 Determine the applicable route
For each transfer, record the actual processing, exporter/importer roles, origin, destination and remote access, applicable data-protection law and lawful mechanism. Adequacy can be relied on only while the applicable decision covers the actual recipient and processing. London hosting does not itself resolve US or other-country access. An Irish Seller’s address or SG’s US incorporation does not alone determine transfer eligibility.
Where eligible for the actual importer processing, the unchanged Standard Contractual Clauses under Commission Implementing Decision (EU) 2021/914 are incorporated into the accepted package: Module Two for controller-to-SG-processor, or Module Three for processor-to-SG-subprocessor. Select one applicable module for the relationship. For Module Three, record the underlying controller and its authorisation. If the importer processing is already directly subject to EU GDPR and the 2021 transfer SCCs are inapplicable, this template is not a substitute for another valid route; affected processing cannot rely on the ineligible selection.
S4 2 Standard SCC elections
| Item | Election or completion |
|---|---|
| Clause 7 | Docking included; actual accession formalities still apply. |
| Clause 9 | Option 2 general written authorisation; 30 calendar days’ notice, with Section 6’s coordinated objection process and mandatory protections. |
| Clause 11 | Optional independent dispute-resolution wording not selected. |
| Clause 13 and Annex I C | Identify the competent supervisory authority under Clause 13(a) for the actual exporter and processing, and record it in the executed annexes. The commercial reseller is not substituted for the actual exporter. |
| Clauses 17 and 18 | Option 1, law of Ireland; courts of Ireland, preserving mandatory beneficiary and forum rights and UK Addendum adaptations where applicable. |
| Annex I A | Actual Order/transfer execution record identifies both parties, contacts, roles, signatures and dates. |
| Annex I B | Schedule 1 plus actual service, processing frequency, duration and transfer details in the accepted Order. |
| Annex II | Schedule 2 and identified actual service measures and accepted evidence; unverified planned controls cannot be asserted as implemented. |
| Annex III information | Applicable Schedule 3 and controlled recipient schedule. Supplying this information does not switch Clause 9 to specific authorisation. |
Mandatory SCC wording is not rewritten by this DPA. Selected instruments and completed annexes are retained as part of the accepted package. Section 9’s finite residual periods do not override mandatory return, deletion, suspension or certification duties; actual exceptions must be lawful under the operative instrument.
S4 3 United Kingdom transfers
For an applicable UK-restricted transfer, incorporate the ICO Approved International Data Transfer Addendum B.1.0, in force 21 March 2022, with the selected linked SCC module and unchanged mandatory Part 2, as revised under its own provisions. A UK route is assessed separately from EU eligibility. The actual transfer and applicable UK data-protection law determine whether the Addendum is needed; UK hosting alone does not select it.
| Part 1 table | Completed standard approach |
|---|---|
| Table 1 | Actual parties, key contacts, signature/capacity, start date and any SG limited-agent signature are those in the executed Order/transfer record. |
| Table 2 | Identify the one linked Module Two or Three form and fixed version/hash. Clause 7 applies; Clause 9 Option 2 and 30 days; Clause 11 option excluded; mandatory UK adaptations govern. |
| Table 3 | Appendix Information comprises the completed parties record, Schedule 1, actual measures in Schedule 2 and applicable supplier/recipient Schedule 3. Module Three includes controller authority. |
| Table 4 | Both exporter and importer may exercise the Addendum Section 19 ending provision in its stated circumstances; no additional ending right is created. |
The parties agree this written Part 1 completion format under the Addendum’s applicable provisions; unchanged mandatory Part 2 accompanies the accepted set. The ICO and mandatory UK law/court adaptations prevail. A UK–US assessment cannot stand in for an assessment of Australia, Venezuela or another destination, and no DPF certification by SG is asserted.
S4 4 Swiss and onward transfers
For Swiss-restricted transfers using an eligible SCC route, make the necessary Swiss-law references, identify the Swiss Federal Data Protection and Information Commissioner and preserve Swiss data subjects’ applicable rights and forum. For onward processing, SG Systems maintains a valid applicable mechanism with each recipient, an assessment where required and effective supplementary safeguards. Another supplier’s DPF status applies only if current and covering that supplier and processing; it is not SG’s certification.
S4 5 Binding execution and standing agency
The actual exporter accepts and signs its own instrument in its own capacity. For its conforming Orders, either authorised Seller may sign SG’s importer block as limited agent under executed D5 Section 10, within an eligible complete package expressly approved by SG. The Seller identifies its own authorised signatory and signs for and on behalf of S.G. Systems, LLC. It cannot sign for the exporter, change approved terms, expand scope or appoint a substitute agent. No separate US-personnel signature is needed where that execution is valid.
The accepted record retains the actual Order, service profile, selected module, options, annex information, assessments, exact DPA/instrument versions and signature evidence. Administrative registration records that agreement; it does not create a fresh approval gate for an otherwise conforming Order. Unexecuted paperwork, a public link or a supplier DPA alone is not the bilateral customer instrument.
S4 6 Standard instrument identification
The selected Module Two or Module Three form must preserve the mandatory wording of the operative Annex to Commission Implementing Decision (EU) 2021/914, except permitted elections, completions and additional safeguards. The actual accepted set identifies the selected form, module, options, annexes, version and execution evidence. The official all-module source is reference material, not a second operative election. The unchanged ICO Addendum accompanies an applicable selected UK set. No signature or actual effective date is supplied merely by this standard text.
Document control
S.G. Systems Data Processing Addendum. Version 1.3. Final consolidated text dated 17 November 2026. Sections 1–13 and Schedules 1–4 form this document. Contractual effect and changes to an existing agreement follow Section 13; preparing the final text does not supply an Order, signature or transfer execution record.
| Version | 1.3, dated 17 November 2026 |
|---|---|
| Permanent address | v5ultimate.com/legal/dpa |
| This version | v5ultimate.com/legal/v/dpa/1.3 |
| Previous versions | Version 1.2 (November 3, 2026); Version 1.1 (November 2, 2026); Version 1.0 (October 12, 2026). Each remains available unchanged for the Orders that accepted it. |
| Related documents | End User Licence Agreement; Commercial Terms; Support & Service Level Agreement; Sub-processors; Privacy Notice |
