Data Processing Agreement
Overview
This Data Processing Agreement (“DPA”) forms part of the Gail Terms of Service published at https://www.meetgail.com/legal/terms or other written services agreement between Nothing Technologies, Inc. dba Gail (“Gail”) and the customer accepting it (“Customer”) (the “Agreement”). It applies when Gail processes personal information on Customer’s behalf in providing the Services. Capitalized terms not defined here have the meanings in the Agreement. The Parties intend their valid acceptance of the Agreement to bind them to this DPA and the incorporated transfer terms without separate signature; a separately executed counterpart (including via electronic signature) is available upon written request to legal@meetgail.com, and the Parties will complete any additional formalities required for a transfer instrument.
01 Definitions
- 1.1 “Applicable Data Protection Law” means laws relating to personal information that apply to a Party’s processing under the Agreement, including, as applicable, the California Consumer Privacy Act as amended by the California Privacy Rights Act and its regulations (“CCPA”), other United States state privacy laws, Regulation (EU) 2016/679 (“GDPR”), the UK GDPR and Data Protection Act 2018, the Swiss Federal Act on Data Protection (“Swiss FADP”), and Brazil’s Lei Geral de Proteção de Dados (“LGPD”). Applicable communications-privacy requirements, including California’s Invasion of Privacy Act, apply to the relevant processing. HIPAA obligations are addressed in Section 13 and the applicable BAA.
- 1.2 “Controller,” “Processor,” “Data Subject,” “Personal Data,” “Processing” and “Supervisory Authority” have their GDPR meanings where GDPR applies. Equivalent terms under another applicable law have the corresponding meanings under that law. “Business,” “Service Provider,” “Consumer,” “Sell” and “Share” have their CCPA meanings.
- 1.3 “Personal Information” means information protected as personal information or personal data under Applicable Data Protection Law, including information relating to an identified or identifiable individual and, where applicable, a household.
- 1.4 “Customer Personal Information” means Personal Information in Customer Data processed by Gail on Customer’s behalf. It includes call and message content and metadata, recordings, transcripts, prompts, outputs, and information about Customer’s personnel, clients, insureds, applicants, borrowers and other Data Subjects. Customer-related service logs remain within this definition to the extent processed on Customer’s behalf.
- 1.5 “Restricted Transfer” means a transfer of Customer Personal Information subject to the international-transfer restrictions of Applicable Data Protection Law that requires a safeguard or other lawful mechanism because no applicable adequacy decision or equivalent instrument covers the recipient, data and activity.
- 1.6 “EU SCCs” means the unmodified standard contractual clauses in the Annex to Commission Implementing Decision (EU) 2021/914, with the applicable module and permitted elections completed in Annex 3. “UK Addendum” means the ICO’s International Data Transfer Addendum to the EU Commission Standard Contractual Clauses, version B1.0 effective 21 March 2022, as lawfully revised under its terms.
- 1.7 “Security Incident” means a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Personal Information. An unsuccessful attempt is excluded only if it does not compromise confidentiality, integrity or availability of Customer Personal Information. A denial-of-service event is not automatically excluded merely because it does not result in unauthorized access.
- 1.8 “Subprocessor” means a third party engaged by Gail to process Customer Personal Information. “BAA” means the executed Business Associate Agreement applicable to the Parties’ processing of Protected Health Information (“PHI”).
02 Roles, Instructions and Restrictions
- 2.1 Customer is the Controller and Gail the Processor for processing on Customer’s behalf, where those roles apply. Where Customer acts as a Processor for another Controller, Gail acts as its Subprocessor. Customer represents that it has authority to appoint Gail, communicate the Controller’s instructions and authorize the processing. Where the CCPA applies, Gail acts as a Service Provider for the covered processing; this DPA does not represent that every Customer meets the statutory definition of a Business.
- 2.2 Gail’s independent processing of business-contact information for account administration, billing and marketing is described in its Privacy Policy. An activity is not excluded from this DPA merely because it involves security, service operation or logs. Gail may not reclassify Customer Personal Information as controller data to avoid these restrictions. Any distinct independent processing must have a lawful basis, appropriate notice and a lawful contractual basis that does not conflict with this DPA.
- 2.3 The Agreement, this DPA, Annex 1, Customer’s authorized configurations and subsequent lawful written instructions constitute documented instructions. Gail will process only on those instructions, including concerning transfers, unless a law applicable to Gail requires otherwise. Where GDPR applies, the statutory exception is subject to Article 28(3)(a). Gail will give prior notice of a legal requirement unless prohibited on the grounds recognized by applicable law, and comply with Section 11 for third-country government requests.
- 2.4 Gail will not use Customer Personal Information to train, fine-tune or improve any AI or machine-learning model, including a third party’s model, and will impose the same restriction on relevant Subprocessors. Providing requested inference, transcription, summaries or Customer-specific analytics does not authorize model training. This restriction is a binding obligation. Any future change permitting training requires a separate, affirmative agreement that lawfully and specifically authorizes the processing and all required notices, permissions and safeguards; posting revised terms, continued use or failure to opt out is insufficient. A BAA or mandatory law may prohibit the processing notwithstanding such an agreement.
- 2.5 Gail will immediately inform Customer if, in its opinion, an instruction infringes Applicable Data Protection Law and may suspend the affected instruction pending resolution. Confirmation by Customer does not require Gail to carry out unlawful processing. Gail is not Customer’s legal adviser.
- 2.6 Customer is responsible for the lawfulness of its instructions, data accuracy and minimization, applicable legal bases and special-category conditions, required notices, and obtaining and documenting required consents before the relevant processing begins. This includes call recording, interception, transcription and monitoring, AI disclosures and automated communications. Customer must provide a lawful process for refusal or withdrawal where required and configure the Services accordingly. Acceptance of the Agreement is not a substitute for a Data Subject’s legally required consent. Each Party remains responsible for obligations directly applicable to it.
03 CCPA Service Provider Obligations
- 3.1 The limited business purposes for disclosure to Gail are specified in Annex 1. Gail will process Customer Personal Information only for those purposes and other processing expressly permitted by the CCPA and consistent with Customer’s instructions and this DPA. A general reference to improving services does not authorize an independent commercial use of Customer Personal Information.
- 3.2 Gail will not Sell or Share Customer Personal Information; retain, use or disclose it for a purpose outside the specified business purposes or direct business relationship, except as expressly permitted by the CCPA; or combine it with information from another person or Gail’s own Consumer interactions except where expressly permitted and consistent with this DPA. Gail certifies that it understands and will comply with these restrictions.
- 3.3 Gail will comply with applicable Service Provider obligations and provide the level of protection the CCPA requires. It will notify Customer promptly and no later than five business days after determining it can no longer comply, and cooperate in reasonable steps to stop and remediate unauthorized processing.
- 3.4 Customer may take reasonable and appropriate steps to monitor compliance, including the audit rights in Section 12, and to stop and remediate unauthorized use. Gail will bind downstream recipients to the applicable restrictions and cooperate with Customer’s rights obligations.
- 3.5 Gail will forward Consumer requests without undue delay and no later than five business days, and will not respond substantively on Customer’s behalf unless authorized or legally required. On lawful instruction, Gail will delete information or cease the covered processing and instruct relevant Subprocessors, subject to applicable lawful exceptions. Section 8 governs assistance.
- 3.6 Gail will provide information and cooperation reasonably needed for applicable risk assessments, cybersecurity audits and automated-decision obligations concerning the Services. Assistance will address applicable notice, access, explanation, opt-out and human-review duties when those duties apply. This clause does not represent that all AI uses are regulated significant-decision processing or that a feature not identified in the Order Form is available. The Parties must identify any required implementation before initiating the affected use.
04 Personnel and Confidentiality
- 4.1 Gail will ensure authorized personnel are subject to confidentiality duties that survive their engagement, receive security and privacy training at least annually, and have access only as necessary for their role.
- 4.2 Gail will carry out legally permitted, role-appropriate background screening for personnel with production access and revoke or adjust access promptly on departure or role change, as detailed in Annex 2.
05 Security Measures
- 5.1 Gail will implement and maintain Annex 2’s measures, taking account of the state of the art, implementation costs, processing characteristics and risks to Data Subjects. Those measures are contractual commitments; an available audit report describes only its stated scope and period.
- 5.2 During an Order Form’s term, Gail will not materially reduce the agreed protection and may replace a measure only with equivalent or stronger protection. A change must not contradict mandatory law, an incorporated transfer instrument or an applicable BAA.
- 5.3 The Trust Center at https://trust.meetgail.com provides available security evidence. Gail will accurately identify certification coverage, validity and report periods. Gail’s current certification status is stated in Section 8.2 of the Agreement. Neither a marketing label nor this DPA establishes that a particular deployment is within a certification’s scope or that an audit covers future operation.
06 Security Incidents
- 6.1 Gail will notify Customer without undue delay and no later than 24 hours after becoming aware of a Security Incident affecting Customer Personal Information. Gail will not delay initial notice while completing an investigation, determining fault or assessing whether Customer must notify another person. Where another applicable obligation requires earlier notice, that obligation applies. This obligation runs continuously and is not postponed by Base Support Business Hours.
- 6.2 Initial notice will state the information then known, including the incident’s nature, affected data and approximate numbers of Data Subjects and records, likely consequences, remedial measures and a contact point. Gail will provide further information in phases without undue delay as it becomes available.
- 6.3 Gail will take reasonable steps to contain, investigate and remediate the incident, preserve relevant evidence, mitigate adverse effects and assist Customer’s investigation, risk assessment and notification decisions.
- 6.4 Gail will not notify an authority or Data Subject on Customer’s behalf unless instructed or legally required. This does not prevent Gail from meeting its own obligations or engaging advisers and authorized incident responders under appropriate confidentiality restrictions. Notice is not an admission of fault or liability.
07 Subprocessors
- 7.1 Customer generally authorizes the Subprocessors identified in the subprocessor register published at https://www.meetgail.com/legal/subprocessors, subject to this Section. The register identifies each entity, relevant contact information, processing activity and country or countries of processing, including relevant remote access. Gail will provide additional information reasonably needed for Customer’s assessment.
- 7.2 Gail will provide at least 30 days’ advance written notice of a new or replacement Subprocessor before it processes Customer Personal Information, using Customer’s designated administrative or privacy contact, and update the register. Mere publication without an effective notice to Customer is insufficient.
- 7.3 Customer may object within those 30 days on reasonable data-protection grounds. The Parties will seek a resolution in good faith before the affected processing begins. If Gail cannot provide a commercially reasonable alternative, Customer may terminate the affected Order Forms without penalty and receive a refund of prepaid Platform Fees for the unused term. A pending objection does not authorize processing prohibited by law or the applicable transfer clauses.
- 7.4 Gail will impose by written contract equivalent applicable data-protection obligations, including Section 2.4, confidentiality, security, rights assistance and lawful transfer safeguards. Gail remains fully responsible to Customer for the Subprocessor’s performance of those obligations. It will provide the information and copies required by applicable transfer clauses, with only lawful confidentiality redactions.
- 7.5 Where an urgent change is needed to protect security or availability, Gail will seek Customer’s specific written authorization before a shorter notice period is used for a new Subprocessor. This clause does not waive the EU SCCs’ prior authorization or notice requirements. Gail may use an already authorized provider within its authorized scope, or suspend affected processing if necessary, while obtaining required authorization.
08 Data Subject Rights
- 8.1 Customer may use available documented functionality to access, correct, export, restrict or delete information. Where that functionality is absent or insufficient, Gail will provide the appropriate technical and organizational assistance, taking account of the processing, to enable Customer to meet its legal deadlines.
8.2 Customer bears reasonable costs of material assistance not attributable to Gail’s breach, as agreed in advance where practicable.
Section 11.9 of the Agreement governs Gail’s rights on non-payment, including its right to suspend or disable access to the Services, the administrative console, the APIs, support and Customer’s access to Customer Data held in the Services, and to do so in respect of a disputed amount. Those rights apply in full notwithstanding this DPA. The sole exception is that charges, account suspension or unpaid invoices will not prevent the rights assistance that Applicable Data Protection Law makes mandatory, or a PHI export required under the BAA or by law. Where that exception applies, Gail will provide only the minimum the law requires, Customer will pay Gail’s reasonable cost of providing it, and Gail may require payment of all undisputed amounts first. Nothing in this Section requires Gail to restore access to the Services, the administrative console, the APIs, support, Managed Services or any export, retrieval or reporting functionality.
- 8.3 Gail will acknowledge a directly received request, direct it to Customer where identifiable, and forward it without undue delay and within five business days. Gail will not respond substantively without authority unless required by law. Requests concerning Gail’s own controller processing are handled under its Privacy Policy.
- 8.4 Gail will notify Customer without undue delay of a relevant regulatory complaint, inquiry or notice unless prohibited by law and provide reasonable assistance. Customer retains responsibility for determining the substantive response concerning its processing.
09 Assessments, Records and Cooperation
- 9.1 Gail will assist Customer with security obligations, personal-data breach response, DPIAs, transfer assessments and prior regulatory consultation concerning the Services, taking account of the nature of processing and information available to Gail. It will provide the relevant annex information and security documentation. It will also provide information reasonably needed for Customer’s legitimate-interest assessment where relevant.
- 9.2 Gail will maintain the processing records required of it by Applicable Data Protection Law and provide Customer with information reasonably necessary to demonstrate compliance, without exposing other customers’ information.
- 9.3 Gail has designated Roly Vicaría as its Data Protection Officer, reachable at privacy@meetgail.com. Gail is established in the United States and has not appointed a separate GDPR Article 27 representative in the European Economic Area or the United Kingdom; EEA, UK, and Swiss supervisory authorities, Customers, and Data Subjects may contact Gail’s Data Protection Officer directly at privacy@meetgail.com.
10 Retention, Return and Deletion
- 10.1 Gail will process Customer Personal Information only for the term of the Services and the limited return, deletion and lawful retention described here. Retention must remain necessary and proportionate; an active account does not authorize retention of every record indefinitely.
- 10.2 Customer’s lawful shorter retention or deletion instruction takes priority over the default lifecycle. Gail will carry out a documented deletion instruction within 30 days or a shorter period needed to meet a binding legal deadline communicated by Customer, unless a valid legal exception prevents it. Gail will explain the scope and reason for any legally permitted retention and limit the remaining processing.
- 10.3 On expiry, termination or closure, Customer may elect return or deletion. The default lifecycle provides 30 days for retrieval followed by a further 60 days in an inactive state solely to complete return or deletion, with deletion from active systems no later than 90 days after expiry, termination or closure, consistent with Section 9 of the Agreement. Gail will not extend that period because of suspension, unpaid charges or an internal account-status change. An earlier lawful deletion election controls. If Customer elects return, Gail will return the information and delete remaining copies as required by law and applicable transfer clauses.
- 10.4 A suspension may provide a restoration grace period of up to 90 days while the Agreement remains in force. It does not restart or extend a termination, deletion, legal-rights or PHI deadline. If the account closes after suspension, the closure lifecycle applies only to data that is still lawfully retained and only to the extent it does not extend an earlier applicable deadline.
- 10.5 Residual backup copies will be isolated from ordinary use, remain protected, expire within the maximum backup period stated in Annex 1, and not be restored to ordinary processing without reapplying relevant deletion instructions. A backup exception does not permit indefinite retention. Mandatory legal retention is limited to the data and time the applicable law requires; for data subject to GDPR Article 28 or EU SCC deletion provisions, only the legal-retention exception allowed by that provision applies. Other laws or government demands must be assessed under the applicable transfer clauses. PHI is subject to the BAA’s return, destruction and infeasibility requirements.
- 10.6 Properly anonymized or de-identified information may be retained only where the process and resulting information satisfy applicable law and this DPA; pseudonymized information remains protected. Gail will not use this provision to train a model or avoid a Customer instruction. On request, Gail will certify required deletion and identify any lawful residual retention and its expiry.
11 International Processing and Transfers
- 11.1 Gail may process Customer Personal Information in the United States and the authorized locations identified in the subprocessor register and any agreed regional restrictions. Hosting location alone does not authorize access from another country. Gail will maintain the required transfer safeguards for onward transfers and provide relevant location information.
- 11.2 For a Restricted Transfer subject to GDPR, the EU SCCs apply with Module Two where Customer is Controller and Gail Processor, and Module Three where Customer is Processor and Gail Subprocessor, subject to the SCCs’ scope. They are incorporated with Annex 3’s elections and completed details. The Parties will not assume the 2021 SCCs are available as the approved mechanism where the importer’s relevant processing falls outside that instrument’s scope, including its Article 3 applicability condition. They will establish another valid mechanism before the affected transfer if necessary.
- 11.3 For UK Restricted Transfers, the UK Addendum is incorporated and completed in Annex 3. For Swiss Restricted Transfers, the recognized EU SCCs apply with Annex 3’s Swiss adaptations. The Parties will meet the applicable transfer assessment and supplementary-safeguard requirements, maintain the necessary assessment record, cooperate in reassessment, and provide relevant information on request subject to appropriate confidentiality.
- 11.4 Where an applicable adequacy instrument covers a transfer, the Parties may rely on it only for its actual scope. Reliance on the EU–U.S. Data Privacy Framework, UK Extension or Swiss–U.S. framework requires verification that the actual recipient has active certification covering the entity, activity and data, and that the relevant adequacy instrument remains available. Nothing here represents that Gail is certified. If that basis ceases to apply, an alternative valid mechanism must be effective before transfers continue. The Parties’ Article 28 and other obligations remain applicable regardless of adequacy.
- 11.5 Transfers subject to the LGPD require a mechanism valid under Article 33 and applicable ANPD rules. Where relying on standard contractual clauses, the Parties will enter the applicable ANPD clauses with their required particulars, without impermissible modification, before the transfer. The EU SCCs are not deemed equivalent merely by this DPA. The Parties must document any applicable adequacy decision, approved equivalent clauses or other valid mechanism; absent one, the transfer must not begin or continue.
- 11.6 Gail will comply with the applicable transfer clauses regarding public-authority requests, including reviewing lawfulness, notifying Customer and Data Subjects where required and legally permitted, seeking waiver of prohibited notice where required, challenging requests where there are reasonable grounds under the relevant clauses, seeking interim measures where appropriate, documenting its assessment and limiting disclosure to legally required data.
- 11.7 Gail will promptly inform Customer if it cannot comply with a transfer safeguard. The Parties will apply the required suspension, termination, return or deletion procedures, including EU SCC Clause 16, and will not continue an unlawful transfer on the basis of a general contractual permission.
12 Information and Audits
- 12.1 Gail will make available information necessary to demonstrate compliance. Available audit reports, certificates, their scope statements, penetration-test summaries, security questionnaires and the subprocessor register may be supplied through the Trust Center under reasonable confidentiality controls. Customer should review appropriate existing evidence first where that can meet its need, but evidence access is not a substitute for required audit rights.
- 12.2 Customer or an independent auditor it appoints may audit compliance, including inspections. For routine audits, the default is once per 12 months, on 30 days’ written notice, during business hours, for a reasonable duration and subject to confidentiality and protection of other customers’ information. These procedural limits do not apply where a Security Incident, reasonable indication of noncompliance, required follow-up, regulator request or mandatory law or transfer clause reasonably requires an additional or earlier audit. Gail will contribute to the audit and provide required information. Customer bears reasonable costs unless the audit reveals Gail’s material breach; costs must not prevent exercise of mandatory rights.
- 12.3 Nothing restricts a competent authority’s statutory powers or the rights required by EU SCCs or other mandatory transfer terms.
13 Protected Health Information
- 13.1 Customer must not submit PHI unless the Parties have executed the Business Associate Agreement published at https://www.meetgail.com/legal/business-associate-agreement and the affected Services and configuration are within its permitted scope. This DPA alone does not authorize PHI processing.
- 13.2 Gail will not knowingly accept PHI outside an authorized arrangement. If it becomes aware of such a submission, it will notify Customer and cooperate on lawful containment, return or deletion. The absence of a signed BAA does not eliminate statutory business-associate obligations that arise from actual processing. Neither ordinary cookie consent nor acceptance of the Agreement substitutes for a required HIPAA authorization.
- 13.3 For authorized PHI processing, the BAA governs permitted uses, safeguards, subcontractors, incidents, assistance and return or destruction. No general analytics, de-identification or data-license provision overrides a BAA restriction or mandatory law.
14 Liability, Term and Precedence
- 14.1 Liability between the Parties is subject to the Agreement’s allocation and limitations to the extent lawful, as Section 14.4 of the Agreement provides. Those limits do not curtail Data Subject rights, regulatory powers or liability that cannot lawfully be limited under the EU SCCs, UK Addendum, other mandatory transfer terms or applicable law.
- 14.2 This DPA remains effective for as long as Gail or its Subprocessors retain Customer Personal Information. The relevant confidentiality, security, incident, assistance, retention, transfer and audit obligations survive accordingly.
- 14.3 Mandatory law and mandatory transfer terms prevail over conflicting contractual terms. The EU SCCs and applicable UK Addendum retain their own hierarchy rules. Subject to those rules and mandatory law, the BAA prevails for PHI, and this DPA prevails over the Agreement and an Order Form for processing Customer Personal Information. An Order Form cannot waive mandatory privacy duties or the protections required by an incorporated transfer instrument.
- 14.4 Gail may amend this DPA when required by law, a binding regulatory or court decision, or a change in an applicable transfer instrument, and otherwise only under the Agreement’s amendment procedure. It will provide at least 30 days’ notice of a material amendment unless a shorter period is legally required. Changes may not retrospectively authorize prohibited processing; Section 2.4 governs any proposed model-training permission.
Annex 1 — Processing and Transfer Details
Nature and Purposes
Providing the Customer-selected hosted business-process and conversational-AI Services: operating inbound and outbound voice agents; placing and receiving communications; recording and transcribing when lawfully enabled; sending and receiving messages; operating chat assistants; generating summaries, Customer analytics and quality records; and integrating with Customer’s management, CRM, telephony and calendar systems. Processing operations include collection, transmission, recording, organization, storage, retrieval, analysis to provide those features, authorized disclosure, return and deletion.
CCPA business purposes are providing the specified Services to Customer; maintaining security and integrity; debugging and repair; permissible short-term transient processing; maintaining and verifying service quality and safety; and Customer-directed analytics. They do not authorize independent advertising, sale, sharing or model training. Any internal quality activity using personal information must remain within instructions and legally permitted Service Provider purposes.
Data Subjects and Categories
Data Subjects are Customer’s personnel and authorized users; customers, clients, insureds, policyholders, applicants, borrowers and prospects; and others communicating through the Services.
Information includes names, phone numbers, email and postal addresses, account and online identifiers, professional and employment information, demographic information, commercial and policy information, quotes, coverage and claims details, payment status, call audio, recordings, transcripts, voicemail, chats and message content, prompts and outputs, communication time, duration, routing, outcome and disposition, and related inferences and summaries. The actual scope is limited to the configured service and lawful instructions; a general category does not authorize collecting unnecessary information.
Sensitive Information and Safeguards
Communications may include health, financial or other sensitive information, and may include GDPR special-category or criminal-offence information in an authorized use case. Customer will identify such intended processing and establish the additional lawful condition and safeguards before it begins. PHI requires the authorized BAA arrangement. Unique biometric identification and other sensitive use cases are not authorized merely because audio is processed.
Specific safeguards include purpose and access restrictions, confidentiality, Annex 2 security, Section 2.4’s training prohibition, authorized Subprocessors and transfers, applicable BAA controls, and deletion rules.
Customer may submit GDPR special-category or criminal-offence Personal Data only where expressly permitted by an applicable Order Form (and, for PHI, an executed Business Associate Agreement) and subject to role-based workspace access restricted to authorized personnel under multi-factor authentication, TLS 1.2+ and AES-256 encryption, approved zero-training AI Subprocessors, Customer-configured data-minimization or retention limits appropriate to the deployment, and a strict prohibition on biometric voiceprint identification.
Frequency, Duration and Retention
Transfers and processing occur continuously or as Customer uses the Services during the Agreement, followed only by the limited return, deletion and lawful retention in Section 10. Subprocessor processing follows the function and duration identified in the subprocessor register and the same instructions and retention obligations.
The default account lifecycle is 30 days for retrieval plus 60 further inactive days after closure, expiry or termination, subject to earlier lawful instructions and Section 10. Suspension has a restoration grace period of up to 90 days only while the Agreement remains in force and cannot extend an earlier deadline.
The maximum routine log periods are 12 months for application logs, 13 months for infrastructure and platform logs, and six months for network-flow logs. Where those logs contain Customer Personal Information, Section 10 and any shorter necessary retention, deletion instruction or mandatory duty take priority. These periods do not grant independent use rights.
Encrypted system and database backups overwrite and expire automatically on a rolling cycle of up to thirty (30) days (with up to seven (7) days of point-in-time recovery transaction logs for managed relational databases), after which deleted Customer Personal Information is permanently purged from backup media. Backup schedules do not override mandatory deletion obligations or PHI protections.
Countries and Recipients
Processing may occur in the United States and other expressly authorized locations identified in the subprocessor register and applicable regional agreement. Each transfer must satisfy Section 11. The register must distinguish vendor headquarters from actual processing and relevant access locations.
Annex 2 — Technical and Organizational Measures
Gail will implement the following agreed measures for the applicable Services. The Parties must complete any identified implementation particulars before relying on this annex for an affected transfer. This annex does not expand a certification’s actual scope.
Encryption and Key Management
Encrypt stored Customer Personal Information with AES-256 or an appropriate equivalent, using managed cloud key protection and restricted key access. Protect service interfaces using TLS 1.2 or higher and secure supported cipher suites; prohibit SSL and TLS 1.0 and 1.1 for those interfaces. Use current secure cryptographic algorithms and SHA-256 or stronger where appropriate for hashing or message authentication; do not use MD5 or SHA-1 for security purposes. Password storage must use an appropriate password-hashing scheme rather than a bare general-purpose hash.
All web interfaces, APIs, webhooks, customer integrations, and cloud-to-AI-provider connections are encrypted in transit using TLS 1.2 or higher, and stored call recordings, transcripts, and customer records are encrypted at rest using AES-256. Standard telephone calls traversing the public switched telephone network (PSTN) and unencrypted carrier SIP/RTP trunks operate over standard telecommunications protocols that are not TLS- or SRTP-encrypted on the carrier leg unless encrypted SIP/SRTP trunking is expressly configured for Customer’s deployment.
Access and Separation
Apply least privilege, role-based access and unique personnel credentials; require multifactor authentication for administrative and production access; review access on a documented schedule and revoke it promptly on departure or role change. Log privileged access and segregate Customer data logically. Use confidentiality duties and authorization controls to prevent access for unrelated purposes.
Network, Application and Development Controls
Restrict network ingress and administrative access, segment environments as appropriate, and operate vulnerability management with documented severity-based remediation. Use secure development, code review and controlled changes. Perform periodic penetration testing and track remediation.
Logging and Monitoring
Maintain appropriate application, infrastructure and network security logs, monitoring and alerting. Protect log access and integrity and avoid unnecessary communication content or sensitive data in logs. Apply Annex 1’s agreed retention and Section 10’s limits.
Resilience and Testing
Maintain documented backup, recovery, business-continuity and disaster-recovery procedures and test relevant plans at least annually. Protect backups and apply the agreed expiry and deletion process. Evaluate and test the effectiveness of security measures regularly and after material changes as appropriate to risk.
Personnel and Physical Safeguards
Require confidentiality, role-appropriate legally permitted background screening, annual security and privacy training, and documented onboarding and offboarding. Use the physical and environmental controls of the relevant authorized cloud providers and appropriate controls for Gail offices, endpoints and removable media. Securely erase or destroy media before disposal or reuse and obtain appropriate cloud-provider assurances.
Governance and Vendors
Maintain documented incident response, risk management, vendor management, classification, retention and encryption procedures, reviewed at least annually. Conduct pre-engagement Subprocessor due diligence, required contractual flow-down and periodic reviews at least annually. Maintain security governance appropriate to the processing and appoint legally required privacy roles. Gail maintains an information security management system certified under ISO/IEC 27001:2022, including a Statement of Applicability, and obtains an annual SOC 2 Type II examination for the agreed service scope. The actual certification scope, validity, examination period and covered system are identified in the Trust Center; these commitments do not expand an auditor’s conclusions. Gail’s current certification status is stated in Section 8.2 of the Terms of Service.
Assistance and Service Specifics
Provide the rights, incident, assessment, audit, return and deletion assistance described in this DPA through available product controls or a documented support process.
Service-specific security schedules and recovery objectives (applicable to this Annex 2 and SCC Annex II): (a) Access reviews: conducted quarterly for production and administrative systems; (b) Vulnerability remediation targets: Critical within 3 calendar days, High within 14 calendar days, Medium within 60 calendar days, and Low within 90 calendar days; (c) Penetration and resilience testing: independent third-party penetration testing and disaster-recovery and incident-response plan testing conducted at least annually; (d) Backups and recovery objectives: automated AES-256 encrypted daily cross-region backups with quarterly restoration testing, a Recovery Time Objective (RTO) of 4 hours, and a Recovery Point Objective (RPO) of 1 hour; and (e) Sensitive-data safeguards: workspace role-based access control, TLS 1.2+ and AES-256 encryption, contractual zero-training AI Subprocessor restrictions, HIPAA BAA controls where applicable, and strict prohibition of biometric voiceprint identification.
Annex 3 — International Transfer Instruments
A. EU SCC Elections
The full EU SCC text identified in Section 1.6 is incorporated without alteration other than its permitted selections and appendix completion. A summary here does not replace the incorporated text.
Module Two applies to Customer as Controller exporting to Gail as Processor. Module Three applies to Customer as Processor exporting to Gail as Subprocessor. If both roles occur, the relevant module applies separately to each transfer. Neither Module One nor Four is selected by this DPA.
Clause 7 docking is included; accession requires the agreement and completion required by that clause.
Clause 9(a) uses Option 2, general written authorization, with 30 days’ advance notice and the information and objection process in Section 7.
The optional independent dispute-resolution provision in Clause 11 is not selected.
Clause 17 uses Option 1 and the law of Ireland, provided that law permits third-party beneficiary rights as required by the SCCs.
Clause 18(b) selects the courts of Ireland, without limiting Data Subjects’ forum rights under Clause 18(c).
B. Annex I.A — Parties
Data exporter. Customer’s full legal name, notice address, state or country of incorporation, authorized signatory or accepting representative, and privacy and legal notices contacts are those recorded in the executed Order Form, which requires each of them, or in the completed account acceptance record. Its relevant activity is obtaining the Services for the purposes in Annex 1. Its role is Controller or Processor as specified above. Date and evidence of acceptance are recorded with the Agreement.
Data importer. Nothing Technologies, Inc., trading as Gail, a Delaware corporation (Delaware Division of Corporations File No. 5238310), registered office c/o The Corporation Trust Company, Corporation Trust Center, 1209 Orange St, Wilmington, DE 19801, United States. Data Protection Officer and privacy contact: Roly Vicaría, privacy@meetgail.com. Legal notices: legal@meetgail.com.
C. Annex I.B — Transfer Description
Annex 1 supplies the Data Subjects, information, sensitive-data restrictions, frequency, purposes, operations and duration. Section 10 supplies retention and deletion criteria. The subprocessor register identifies each Subprocessor’s subject matter, nature, duration and processing locations. Required sensitive-data and retention particulars must be completed for the relevant transfer; a blank field is not a valid instruction to proceed without safeguards.
D. Annex I.C — Supervisory Authority
The competent authority is determined under Clause 13: the authority responsible for an EEA-established exporter; where an exporter subject to GDPR Article 3(2) has an Article 27 representative, the authority of the member state where that representative is established; or, where no representative is required, an authority of a member state in which relevant Data Subjects are located in the circumstances specified by Clause 13. The Parties will identify the resulting authority in the Order Form or transfer record before reliance on the clauses. Ireland is not an automatic default for every non-EEA exporter.
E. Annex II and Subprocessor Information
Annex 2, completed with applicable service particulars and additional sensitive-data safeguards, is SCC Annex II. The subprocessor register supplies current information about authorized Subprocessors and is preserved or made available in a dated form for the applicable transfer. With Clause 9 Option 2 selected, SCC Annex III is not mandatory merely by that election; the register and Section 7 still satisfy applicable authorization and information duties. If the Parties later select specific authorization, they must complete Annex III with the required particulars.
F. UK Addendum Completion
The ICO UK Addendum, including its mandatory Part 2, is incorporated for covered UK transfers. For its Table 1, the Parties, contacts and details are those in Annex 3.B, with the start date being the DPA’s binding acceptance date for the relevant transfer. Table 2 selects the 2021 EU SCCs, Modules Two and Three as applicable, and the elections in Annex 3.A. Table 3 uses Annex 3.B and Annexes 1 and 2, plus the subprocessor register where applicable, for the appendix information. In Table 4, both importer and exporter may end the Addendum under its Section 19. The Addendum’s mandatory hierarchy, governing-law, court and interpretation provisions apply, including England and Wales as its default law and courts; the Irish selections do not replace them for UK transfers.
G. Swiss Adaptations
For processing subject exclusively to the Swiss FADP, references to GDPR in the SCCs are read as references to the Swiss FADP as necessary to protect the covered transfer; references to an EU member state extend as necessary to Switzerland; the competent authority is the Swiss Federal Data Protection and Information Commissioner; and the clauses must permit Data Subjects in Switzerland to exercise their rights there. Clause 17 uses Swiss law and Clause 18 permits the competent Swiss courts for that Swiss-only application. Where both GDPR and the Swiss FADP apply, the EU selections remain for GDPR and the Swiss authority and protections apply additionally to the Swiss processing. No adaptation narrows mandatory Data Subject rights.
H. Brazil Transfer Record
The Parties will identify and complete the applicable LGPD and ANPD mechanism under Section 11.5, including the unmodified ANPD standard clauses and required particulars where used. This DPA does not attach or purport to complete that separate instrument. No Restricted Transfer from Brazil may rely solely on this paragraph or an assertion that EU SCCs are equivalent.
Version history
Select a past version of this document to review it as it appeared on that date.
You're viewing the current version.
