Data Processing Addendum
Last updated: 12 November 2026
This Data Processing Addendum (the "DPA") forms part of the Terms of Service (the "Terms") between Sodasoft LLC ("Sodasoft LLC" or "Processor") and the organization that uses NORDON for business purposes, including an organization that buys a Team Plan (the "Customer"). It applies when Sodasoft LLC processes Customer Personal Data on the Customer's behalf. It is incorporated by reference into the Terms for Team Plan customers and other Business Users and takes effect when the Customer accepts the Terms. A countersigned copy is available on request to support@nordon.ai.
1. Definitions
Capitalized terms not defined here have the meaning given in the Terms. In this DPA:
- "Applicable Data Protection Law" means all laws on data protection and privacy that apply to the processing of Customer Personal Data under the Terms, including the GDPR, the UK GDPR, the Swiss Federal Act on Data Protection ("FADP"), the California Consumer Privacy Act as amended ("CCPA") and other US state comprehensive privacy laws.
- "GDPR" means Regulation (EU) 2016/679, and "UK GDPR" means the GDPR as it forms part of the law of the United Kingdom, with the Data Protection Act 2018.
- "Customer Personal Data" means personal data in Customer Content that Sodasoft LLC processes on behalf of the Customer in providing the Service.
- "Authorized User" means an Owner, Admin or Member of the Customer's Team, or another person the Customer allows to use the Service on its behalf.
- "Personal Data Breach" means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Personal Data.
- "SCCs" means the standard contractual clauses annexed to Commission Implementing Decision (EU) 2021/914 of 4 June 2021, and "UK Addendum" means the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses issued by the UK Information Commissioner under section 119A of the Data Protection Act 2018 (version B1.0).
- "Subprocessor" means a third party engaged by Sodasoft LLC that processes Customer Personal Data.
- "controller", "processor", "data subject", "personal data", "processing", "business", "service provider" and "sell" and "share" have the meanings given in Applicable Data Protection Law.
2. Scope and roles
2.1 Roles. The Customer is the controller of Customer Personal Data (or a processor acting for its own clients), and Sodasoft LLC is its processor (or subprocessor) and, under US state privacy laws, its service provider or processor.
2.2 Excluded data. This DPA does not apply to personal data that Sodasoft LLC processes as a controller for its own purposes, as described in the Privacy Policy: account and sign-in data, billing and payment records, security logs and abuse prevention, service emails, tips emails, website analytics and ad measurement.
2.3 Individual accounts in a Team. Each Authorized User of a Team holds an individual Account. The Service is designed so that Owners and Admins cannot see Members' sessions, transcripts, answers or personal documents. The Customer instructs Sodasoft LLC to operate the Service in this way, including that, when an Authorized User leaves or is removed from the Team, the sessions and personal documents in that user's Account remain with that user, and items they shared with the Team become private to them again. The organization of the Team's Owner is the controller for the use of the Team's accounts, including the sessions of its Authorized Users while they are in the Team, and Sodasoft LLC processes that data as its processor, even though, as the Service works, Members' own sessions are not visible to the Team's Owner and Admins.
2.4 Details. The subject matter, duration, nature and purpose of the processing, and the types of personal data and categories of data subjects, are set out in Annex I.
3. Customer obligations
The Customer:
- is responsible for the lawfulness of the processing of Customer Personal Data, including having a lawful basis and giving every notice and obtaining every consent required by Applicable Data Protection Law and by laws on recording and interception of communications, including for Call Participants and Authorized Users;
- ensures that its instructions comply with Applicable Data Protection Law;
- does not submit special categories of personal data, or personal data relating to criminal convictions, except where necessary for its use of the Service and lawful; and
- is responsible for the use of the Service by its Authorized Users and for the Team rules it sets.
4. Processor obligations
4.1 Instructions. Sodasoft LLC processes Customer Personal Data only on the Customer's documented instructions, including with regard to transfers, unless required to do so by law, in which case Sodasoft LLC will inform the Customer before processing unless the law prohibits it. The Terms, this DPA, and the Customer's and its Authorized Users' use and configuration of the Service (including Team rules, transcript saving and sharing settings) are the Customer's complete instructions. Sodasoft LLC will inform the Customer if, in its opinion, an instruction infringes Applicable Data Protection Law.
4.2 Confidentiality. Sodasoft LLC ensures that persons authorized to process Customer Personal Data are bound by confidentiality obligations and access it only as needed to provide the Service, provide support the Customer requests, investigate abuse or security incidents, or comply with law. Access is limited to a small number of authorized personnel and is reviewed.
4.3 No training. Sodasoft LLC does not use Customer Personal Data to train AI models. It uses AI providers through API terms under which inputs and outputs are not used to train their models; the providers may keep data for a limited period (typically up to 30 days) to monitor for abuse.
4.4 Assistance. Taking into account the nature of the processing and the information available to it, Sodasoft LLC assists the Customer in meeting its obligations under Articles 32 to 36 GDPR (security, breach notification, data protection impact assessments and prior consultation) and their equivalents, as set out in this DPA.
5. US state privacy laws
Where Sodasoft LLC acts as a service provider or processor under the CCPA or another US state privacy law, it:
- processes Customer Personal Data only for the limited and specified business purpose of providing the Service under the Terms;
- does not sell or share Customer Personal Data;
- does not retain, use or disclose Customer Personal Data for any purpose other than the business purposes specified in the Terms, or outside the direct business relationship with the Customer, except as the law permits;
- does not combine Customer Personal Data with personal data it receives from or on behalf of others or collects from its own interactions with consumers, except as the law permits;
- complies with the obligations of, and provides the same level of privacy protection required by, the applicable law;
- notifies the Customer if it determines it can no longer meet its obligations;
- permits the Customer, on notice, to take reasonable and appropriate steps to stop and remediate unauthorized use of Customer Personal Data; and
- engages Subprocessors only under written contracts with obligations no less protective than these.
Sodasoft LLC certifies that it understands and will comply with these restrictions.
6. Security
Sodasoft LLC implements the technical and organizational measures in Annex II. Sodasoft LLC may update them, provided that the update does not materially reduce the overall security of the Service. The Customer is responsible for securing its Authorized Users' email accounts and devices, and for its own configuration choices.
7. Subprocessors
7.1 Authorization. The Customer gives Sodasoft LLC general written authorization to engage Subprocessors. The current Subprocessors are listed on the Subprocessors page (Annex III), which the Customer approves.
7.2 Obligations. Sodasoft LLC imposes on each Subprocessor, by written contract, data protection obligations that provide at least the level of protection of this DPA, and remains liable to the Customer for its Subprocessors' performance of those obligations.
7.3 Changes and objections. Sodasoft LLC will give at least 30 days' notice of a new Subprocessor by updating the Subprocessors page and by email to the Owners of Teams. The Customer may object on reasonable data protection grounds by writing to support@nordon.ai within that period. The parties will discuss the objection in good faith. If they cannot resolve it, the Customer may terminate the affected part of the Service by written notice and receive a refund of prepaid Fees for the remaining period. Where a Subprocessor must be replaced urgently, Sodasoft LLC will give notice as soon as possible, and the objection period runs from that notice.
8. Data subject requests and assistance
The Service lets Authorized Users export their data and delete sessions, documents and Accounts themselves. If Sodasoft LLC receives a request from a data subject that relates to Customer Personal Data and identifies the Customer, it will refer the data subject to the Customer and will not respond itself unless the Customer authorizes it or the law requires it. Taking into account the nature of the processing, Sodasoft LLC will provide reasonable assistance to the Customer in responding to requests to exercise data subject rights.
9. Personal Data Breach
Sodasoft LLC will notify the Customer without undue delay, and in any event within 48 hours, after confirming a Personal Data Breach affecting Customer Personal Data. The notice will describe, as far as then known, the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, the measures taken or proposed, and a contact point; further information will follow as it becomes available. Sodasoft LLC will take reasonable steps to contain and remedy the breach. Notice is sent to the Owner's email address unless the Customer names another contact. A notice is not an admission of fault. Security incidents are handled by Sodasoft LLC's founding team.
10. Return and deletion
During the term, the Customer and its Authorized Users can export Customer Personal Data in JSON format and delete it with the tools in Settings. When a Team Plan ends, nothing is deleted automatically: the Team, its shared documents and playbooks remain until deleted, and each Authorized User keeps their own Account and sessions on their personal Plan. After the Terms end for the Customer, Sodasoft LLC will, at the Customer's written request, delete or return the Customer Personal Data held for the Customer within 30 days, subject to Section 2.3, unless the law requires it to be kept. Deleted data may remain in the database provider's backups and history for up to 30 days and is not restored except to recover the Service.
11. Information and audits
11.1 Information. Sodasoft LLC makes available to the Customer the information reasonably necessary to demonstrate compliance with this DPA, including this DPA and its annexes and written answers to a reasonable security questionnaire once in any 12 months. Sodasoft LLC does not currently hold third-party security certifications or audit reports.
11.2 Audits. Where the information under Section 11.1 is not sufficient to demonstrate compliance, or where a supervisory authority requires it, the Customer may audit Sodasoft LLC's compliance, at the Customer's cost, by an independent auditor bound by confidentiality, on at least 30 days' written notice, during normal business hours, no more than once in any 12 months (unless following a Personal Data Breach or required by a supervisory authority), and without access to other customers' data. The parties will agree the scope in advance. This Section also governs audits under Clause 8.9 of the SCCs.
12. International transfers
12.1 Location. Sodasoft LLC is established in the United States and processes Customer Personal Data in the United States and in the other locations of its Subprocessors.
12.2 EU transfers. To the extent the processing involves a transfer of Customer Personal Data subject to the GDPR to a country without an adequacy decision, the SCCs are incorporated into this DPA by reference and apply as follows: Module Two (controller to processor) applies where the Customer is a controller, and Module Three (processor to processor) applies where the Customer is a processor; the Customer is the data exporter and Sodasoft LLC the data importer; Clause 7 (docking clause) applies; under Clause 9, Option 2 (general written authorization) applies with the notice period in Section 7.3; the optional language in Clause 11 does not apply; under Clause 13, the competent supervisory authority is determined as set out in Annex I.C; under Clause 17, Option 1 applies and the SCCs are governed by the law of Ireland; under Clause 18, disputes are resolved by the courts of Ireland; and Annexes I, II and III of this DPA complete the corresponding annexes of the SCCs.
12.3 UK transfers. For transfers subject to the UK GDPR, the UK Addendum is incorporated by reference: Table 1 is completed with the parties in Annex I.A; Table 2 refers to the SCC modules and options selected in Section 12.2; Table 3 is completed with Annexes I to III; and for Table 4, the importer may end the UK Addendum as provided in its Section 19.
12.4 Swiss transfers. For transfers subject to the FADP, the SCCs apply as set out in Section 12.2 with these changes: references to the GDPR are read as references to the FADP; the Swiss Federal Data Protection and Information Commissioner is the competent supervisory authority for such transfers; and the term "Member State" is read so that data subjects in Switzerland can bring claims in their place of habitual residence.
12.5 Government requests. If Sodasoft LLC receives a legally binding request from a public authority for Customer Personal Data, it will notify the Customer unless the law prohibits it, assess the legality of the request, challenge it where there are reasonable grounds, and disclose only the minimum required, in line with Clause 15 of the SCCs.
12.6 Onward transfers. Sodasoft LLC transfers Customer Personal Data to Subprocessors outside the European Economic Area, the United Kingdom and Switzerland only with appropriate safeguards under Applicable Data Protection Law.
12.7 Precedence. If the SCCs or the UK Addendum conflict with this DPA or the Terms, the SCCs or the UK Addendum prevail.
13. Liability
Each party's liability arising out of or relating to this DPA, including under the SCCs as between the parties, is subject to the exclusions and limitations of liability in Section 21 of the Terms, to the extent permitted by Applicable Data Protection Law. Nothing in this DPA limits either party's liability to data subjects under the SCCs or Applicable Data Protection Law, or liability that cannot be limited by law.
14. Term, precedence and changes
14.1 Term. This DPA lasts as long as Sodasoft LLC processes Customer Personal Data on the Customer's behalf.
14.2 Precedence. Subject to Section 12.7, if this DPA conflicts with the Terms on the processing of Customer Personal Data, this DPA prevails.
14.3 Changes. Sodasoft LLC may update this DPA to reflect changes in law, in guidance of supervisory authorities or in the Service, by posting the new version here and notifying Customers by email at least 30 days in advance, provided that no update materially reduces the protection of Customer Personal Data.
14.4 Governing law. Except as stated in Section 12, this DPA is governed by the law that governs the Terms.
Annex I: Description of processing
A. List of parties
- Data exporter: the Customer, with the name, address and contact person given in its Account, Team or order. Role: controller (or processor). Activities: use of the Service under the Terms. Signature and date: by accepting the Terms.
- Data importer: Sodasoft LLC, 30 N Gould St, Sheridan, WY 82801, USA; contact support@nordon.ai. Role: processor (or subprocessor). Activities: providing the Service under the Terms. Contact for data protection matters and supervisory authorities: support@nordon.ai. Signature and date: by making the Service available under the Terms.
B. Description of the processing and transfer
- Categories of data subjects: Authorized Users; Call Participants whose speech or image is captured in sessions run by Authorized Users; people named or described in documents, playbooks, notes and conversations that Authorized Users provide.
- Categories of personal data: name, email address, team role, last sign-in and usage of Authorized Users; voice audio and short voice samples (processed transiently, not stored); transcripts and the content of conversations; detected questions, AI answers, summaries and coaching notes; text extracted from documents and its embeddings; playbooks; screen pictures (processed transiently, not stored); and any personal data contained in that content.
- Sensitive data: not intended. Conversations and documents may incidentally contain special categories of data. Safeguards: audio and screen pictures are not stored; transcript saving is off by default; encryption in transit; per-account separation; access limited as in Annex II; no training of AI models.
- Frequency of the transfer: continuous, while Authorized Users use the Service.
- Nature of the processing: collection through the Apps, transcription, separation of speakers within a call, AI generation of answers and summaries, text extraction and indexing of documents, storage, retrieval, display, export and deletion.
- Purpose: providing the Service to the Customer under the Terms.
- Retention: audio, voice samples and screen pictures are discarded after each request; other Customer Personal Data is kept until deleted by an Authorized User or under Section 10, as set out in section 11 of the Privacy Policy.
- Transfers to Subprocessors: the subject matter, nature and duration are as described for each Subprocessor in Annex III, for the term of the Terms.
C. Competent supervisory authority
Where the Customer is established in the EEA, its lead supervisory authority, or otherwise the supervisory authority of the Member State where it is established. Where the Customer has no establishment in the EEA, the Irish Data Protection Commission.
Annex II: Technical and organizational measures
These are the measures in place in the Service today.
Encryption and transport
- All traffic to the Service uses HTTPS; HTTP Strict Transport Security is sent with a two-year max-age, including subdomains.
- Secrets held in the database (AI provider keys, the payment webhook signing secret) are encrypted with AES-256-GCM using a key kept outside the database.
- Stored data is encrypted at rest by the database provider, Neon.
Authentication and sessions
- No passwords: sign-in uses single-use links with 256-bit random tokens that expire after 15 minutes (24 hours for links issued by administrators); a link can be used only once, atomically.
- The token travels in the URL fragment, which is not sent to servers or in referrer headers; sign-in pages send no referrer.
- Only SHA-256 hashes of sign-in tokens and session tokens are stored, so a copy of the database yields no usable sign-in.
- Session cookies are HTTP-only, Secure, SameSite=Lax and use the __Host- prefix; sessions expire after 30 days and can be ended on all devices.
- A sign-in link opened on a device other than the one that requested it shows a warning.
- Blocked accounts are refused on every request, and blocking signs the user out everywhere.
Access control and separation
- Every database query for customer data is scoped to the signed-in account, or to its Team for shared items.
- Team roles (owner, admin, member) are enforced on the server for every Team action.
- Platform administrator rights are granted only to accounts listed in the server configuration or by an existing administrator; every grant is written to the security log, and rights are checked on every administrative request.
- Administrators see document counts, not document content, and see transcripts only when they were saved.
Application and network security
- A Content Security Policy, X-Frame-Options DENY, frame-ancestors none, X-Content-Type-Options nosniff, a strict Referrer-Policy and a Permissions-Policy that allows only microphone and screen capture for the site itself.
- Cross-site write requests to the API are refused by an origin check.
- Rate limits on sign-in, link verification, transcription, answers, uploads, exports, billing and administrative actions.
- Payment webhooks are verified by signature and applied only once.
- Scheduled jobs require a secret, compared in constant time.
- Custom AI provider addresses that point to private or internal networks are refused.
- Uploads are limited to 4 MB, and Word files are checked against decompression bombs.
- JSON request bodies are validated against schemas before use.
Data minimization and deletion
- Audio, voice samples and screen pictures are processed in memory and not stored; original uploaded files are not kept.
- Transcript saving is off by default for each session.
- Network addresses in the security log are stored as one-way hashes.
- Deleting a session, document or Account removes the related records permanently from the live database; expired sign-in records, sessions and rate-limit counters are deleted daily; the security log is kept for one year.
- Self-service export of Account data in JSON format.
Logging and monitoring
- A security log records privilege and account changes, Team changes, administrative settings and AI key changes, billing disputes and sign-in problems.
- An automated daily check of production and a weekly check of AI answer quality; results go to the security log, and quality failures are emailed to administrators.
Apps
- The desktop app installs only updates with a valid Ed25519 signature over version, file name and SHA-256 hash, and loads only the NORDON website in its windows.
- The desktop app captures call audio and screen pictures only during a live session and after a one-time consent in a native dialog, which can be withdrawn.
- The Chrome extension requests only storage, activeTab, scripting and tabCapture permissions. tabCapture is used only for the tab on which the user starts a call from the extension's menu; that tab's audio goes only to the user's own NORDON window for live transcription and is not stored. Host access is granted per site by the user, and the extension shows a visible badge while active.
Organizational measures
- Personnel with access to Customer Personal Data are bound by confidentiality obligations.
- Access to production systems and customer data is limited to a small number of authorized people and is reviewed.
- Security incidents are handled by the founding team, who assess, contain and notify as set out in Section 9.
- Providers that process personal data are engaged under written data processing terms (Annex III).
- Sodasoft LLC does not currently hold third-party security certifications.
Annex III: Subprocessors
The Subprocessors authorized under Section 7, with their purpose, location and transfer mechanism, are listed on the Subprocessors page, as updated under Section 7.3.
Sodasoft LLC, 30 N Gould St, Sheridan, WY 82801, USA. support@nordon.ai