Version 1.0 — Last updated 16 Nov 2026
This Data Processing Addendum (“DPA“) forms part of the agreement between coReel, Inc. (“coReel“) and the customer (“Customer“) for the coReel services (the “Services“). That agreement may be the coReel Master Subscription Agreement and its Order Forms, or the coReel Terms of Service (the “Agreement“). This DPA applies whenever coReel processes Customer Personal Data in providing the Services. It needs no separate signature. A Customer that wants a countersigned copy can request one from [email protected].
1. Definitions
Terms not defined here have the meanings given in the Agreement or in Data Protection Laws.
- “Customer Personal Data” means Personal Data in Customer Data that coReel processes on Customer’s behalf under the Agreement.
- “Data Protection Laws” means all laws on privacy and the processing of Personal Data that apply to a party’s processing under the Agreement. These may include:
- the EU General Data Protection Regulation 2016/679 (“GDPR“);
- the UK GDPR and the UK Data Protection Act 2018;
- the Swiss Federal Act on Data Protection;
- the California Consumer Privacy Act, as amended by the CPRA (“CCPA“);
- other U.S. state privacy laws.
- “Personal Data” means information relating to an identified or identifiable natural person. It includes “personal information” as defined in Data Protection Laws.
- “Security Incident” means a breach of security that leads to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Personal Data in coReel’s systems or its Subprocessors’ systems.
- “Standard Contractual Clauses” or “SCCs” means the clauses approved by European Commission Implementing Decision (EU) 2021/914.
- “Subprocessor” means a third party that coReel engages to process Customer Personal Data.
- “controller“, “processor“, “data subject“, “processing“, “business“, “service provider“, “sell” and “share” have the meanings given in Data Protection Laws.
2. Roles and scope
2.1 Roles. For Customer Personal Data, Customer is the controller (or business), and coReel is the processor (or service provider). Customer may itself act as a processor on behalf of its own controllers. In that case, coReel is Customer’s subprocessor, and Customer is responsible for obtaining any authorizations its controllers require.
2.2 coReel’s own data. This DPA does not cover Personal Data for which coReel is itself a controller. Examples are account-holder sign-in details, billing contacts, and data about how the Services are used (Usage Data). coReel’s Privacy Policy covers that data.
2.3 Details of processing. Annex I describes the subject matter, nature, purpose and duration of the processing, and the types of Personal Data and data subjects involved.
3. Customer’s responsibilities
3.1 Lawful basis, notices and consents. Customer is responsible for the lawfulness of its instructions and of the Customer Personal Data it provides. This includes having a lawful basis, and giving the notices and obtaining the consents that Data Protection Laws require, for:
- recording people in videos and calls;
- tracking Recipients’ engagement with watch pages, links and email (for example, opens, views and clicks);
- sending messages to Recipients;
- mailing cards to the addresses Customer supplies.
3.2 Sensitive data. Customer will not use the Services to process special categories of Personal Data, or Personal Data of children under 16, unless coReel agrees in writing. Special categories include health, biometric identification and government ID numbers.
4. coReel’s obligations
4.1 Instructions. coReel will process Customer Personal Data only on Customer’s documented instructions, unless the law requires otherwise. Customer’s instructions are given by:
- the Agreement and this DPA;
- Customer’s and its users’ configuration and use of the Services;
- any other written instructions the parties agree.
If coReel believes an instruction violates Data Protection Laws, coReel will tell Customer. If the law requires coReel to process Customer Personal Data in another way, coReel will tell Customer first, unless the law prohibits it.
4.2 Confidentiality of personnel. coReel will make sure that everyone it authorizes to process Customer Personal Data is bound by a duty of confidentiality.
4.3 Security. coReel will maintain the technical and organizational measures in Annex II. Those measures are designed to protect Customer Personal Data against Security Incidents and to suit the risk of the processing. coReel may update the measures, but it will not materially reduce the overall protection they provide.
4.4 CCPA service-provider terms. coReel will not:
- sell or share Customer Personal Data;
- keep, use or disclose it for any purpose other than the business purposes in the Agreement, including any commercial purpose other than providing the Services;
- keep, use or disclose it outside the direct business relationship between coReel and Customer;
- combine it with Personal Data that coReel receives from or on behalf of others, except as Data Protection Laws allow for a service provider.
coReel will comply with the CCPA’s obligations for service providers. coReel will tell Customer if it can no longer meet them. Customer may take reasonable steps to stop and fix any unauthorized use. coReel certifies that it understands and will comply with these restrictions.
4.5 No model training. coReel will not use Customer Personal Data to train AI or machine-learning models. It will not allow its Subprocessors to do so either.
5. Subprocessors
5.1 General authorization. Customer authorizes coReel to engage Subprocessors. The current list is at coreel.ai/subprocessors/, and Customer approves the Subprocessors listed there.
5.2 Subprocessor terms. coReel will put a written agreement in place with each Subprocessor. That agreement will impose data-protection obligations that are no less protective than this DPA, to the extent they apply to the Subprocessor’s services. coReel remains responsible for each Subprocessor’s performance of those obligations.
5.3 Notice of changes. coReel will update the list at least thirty (30) days before a new Subprocessor begins processing Customer Personal Data. coReel will also email Customers who have asked for updates (as the list page explains).
5.4 Objections.
(a) Notice. Customer may object to a new Subprocessor on reasonable grounds related to data protection. It must give written notice within the notice period.
(b) Resolution. The parties will discuss the objection in good faith. coReel may offer a reasonable alternative.
(c) Termination. If the parties cannot resolve the objection within thirty (30) days, Customer may terminate the affected Services by written notice. coReel will then refund any prepaid fees for the rest of the term of those Services. This is Customer’s sole remedy for an objection.
6. Assistance
6.1 Data subject requests. If coReel receives a request from a data subject about Customer Personal Data, coReel will forward it to Customer and will not answer it itself, unless the law requires otherwise. Taking into account the nature of the processing, coReel will help Customer respond to data subject requests by appropriate technical and organizational measures, as far as possible. Much of this is available directly in the Services, for example deleting videos, contacts and users.
6.2 Impact assessments and consultations. coReel will give Customer reasonable help with data protection impact assessments and prior consultations with supervisory authorities that Data Protection Laws require. This is limited to information available to coReel about its processing.
7. Security Incidents
7.1 Notice. coReel will notify Customer without undue delay after becoming aware of a Security Incident. In any event, the notice will come within seventy-two (72) hours. coReel will notify the Customer’s account owner and the notice contact on file.
7.2 What coReel provides. As information becomes available, coReel will provide:
- the nature of the Security Incident;
- the categories and approximate number of data subjects and records involved;
- the likely consequences;
- the steps taken or proposed to address it.
coReel will take reasonable steps to contain, investigate and reduce the effects of the Security Incident.
7.3 No admission. A notice of a Security Incident is not an admission of fault or liability.
7.4 Exclusions. Unsuccessful attempts that do not compromise security are not Security Incidents. Examples are pings, port scans and failed login attempts.
8. Return and deletion
8.1 Export. During the term, Customer can export or delete its Customer Personal Data using the Services. After the Agreement ends, Customer may export its data for thirty (30) days, as the Agreement describes.
8.2 Deletion. After that period, coReel will delete Customer Personal Data from its active systems within ninety (90) days. Copies in backups are overwritten in the normal backup cycle, within thirty-five (35) days after that.
8.3 Retention required by law. coReel may keep Customer Personal Data where the law requires it. Anything retained stays protected by this DPA and is used only for that purpose.
9. Audits
9.1 Information. On written request, no more than once a year, coReel will give Customer information that is reasonably needed to show compliance with this DPA. That information will be subject to confidentiality. It may include:
- written answers to a reasonable security questionnaire;
- summaries of coReel’s security policies;
- any third-party audit reports coReel has.
9.2 On-site audits. An on-site audit takes place only in these cases:
- a supervisory authority requires it;
- the information under Section 9.1 is not enough to show compliance;
- a Security Incident affecting Customer has occurred.
An on-site audit will be conducted as follows:
- after at least thirty (30) days’ notice;
- during business hours;
- in a way that does not disrupt coReel’s operations or expose other customers’ data;
- by Customer or an independent auditor bound by confidentiality;
- at Customer’s expense.
10. International transfers
10.1 Location. coReel and its Subprocessors process Customer Personal Data in the United States.
10.2 EEA transfers. If the GDPR applies to a transfer of Customer Personal Data to coReel, the SCCs are incorporated into this DPA as follows:
- Module Two (controller to processor) applies where Customer is a controller, and Module Three (processor to processor) applies where Customer is a processor.
- Clause 7 (docking) applies.
- Clause 9(a) uses Option 2 (general authorization) with the notice period in Section 5.3.
- The optional wording in Clause 11 does not apply.
- Clauses 17 and 18 refer to the law and courts of [Ireland].
- Annexes I and II of this DPA complete the SCCs’ Annexes. Annex III is the Subprocessor list.
10.3 UK transfers. For transfers subject to UK data protection law, the UK International Data Transfer Addendum to the SCCs (version B1.0) applies. Its Tables 1 to 3 are completed using this DPA, and either party may end it as described in its Section 19.
10.4 Swiss transfers. For transfers subject to Swiss law, the SCCs apply with these changes:
- references to the GDPR mean the Swiss Federal Act on Data Protection;
- the supervisory authority is the Swiss FDPIC;
- “Member State” includes Switzerland.
10.5 Conflicts with the SCCs. If the SCCs conflict with this DPA, the SCCs prevail.
11. General
11.1 Liability. Each party’s liability under this DPA is subject to the limitations of liability in the Agreement. This does not apply where Data Protection Laws or the SCCs do not allow liability to be limited.
11.2 Order of precedence. On the processing of Personal Data, this DPA prevails over the Agreement. In every other respect, the Agreement governs.
11.3 Term. This DPA lasts as long as coReel processes Customer Personal Data.
11.4 Changes. coReel may update this DPA to reflect changes in Data Protection Laws or in the Services. An update will not materially reduce the protection given to Customer Personal Data. For a Customer with a signed Order Form, an update that materially changes this DPA applies only from the Customer’s next renewal, unless the law requires it sooner.
Annex I — Details of processing
Parties
| Role | Party |
|---|---|
| Data exporter | Customer, as named in the Agreement or Order Form. Role: controller, or processor on behalf of its own controllers. |
| Data importer | coReel, Inc., 2712 Loker Avenue West #1095, Carlsbad, CA 92010, USA. Contact: [email protected]. Role: processor. |
Subject matter and nature. coReel provides a hosted video messaging service that Customer uses to:
- record, store, edit and caption videos;
- send them by email, link or CRM, and through Conversation Rooms;
- host watch pages and embeds;
- track Recipient engagement;
- sync activity to Customer’s CRM;
- generate AI-assisted content;
- print and mail video cards.
Purpose. To provide, support and secure the Services under the Agreement.
Duration. For the term of the Agreement, plus the return and deletion periods in Section 8.
Frequency. Continuous.
Categories of data subjects
- Customer’s users (employees and contractors).
- Recipients and prospective recipients of Customer’s videos, messages and cards.
- Contacts in Customer’s connected CRM or imported lists.
- People who appear in, or are named in, Customer’s videos, transcripts or files.
- Participants in Conversation Rooms and their calls.
Categories of Personal Data
- Identity and contact data: names, email addresses, phone numbers, job titles and company names.
- Mailing data: postal addresses for mailed cards.
- Content: video and audio recordings, including the images and voices of people recorded; screen recordings; thumbnails; captions and transcripts; messages; files; and email and card text.
- Engagement data: opens, views, plays, watch time, clicks, replies and QR scans; timestamps; IP address; user agent and device type; and approximate location derived from the IP address.
- CRM data: contact, deal and activity records read from or written to Customer’s connected CRM.
- AI data: prompts, the context sent with them, and generated output.
- Account data for users: login identifiers, role, team membership, and SSO/SCIM identifiers.
Sensitive data. None intended (Section 3.2). Background blur and virtual backgrounds run on the user’s own device and do not send biometric templates to coReel.
Subprocessors. See Annex III.
Annex II — Technical and organizational security measures
- Encryption. Data is encrypted in transit with TLS. Video storage and databases are encrypted at rest (AWS S3 server-side encryption and database storage encryption). OAuth tokens for connected services are encrypted at the application level with a dedicated key.
- Hosting. Hosted on Amazon Web Services in the United States. Infrastructure runs in a dedicated AWS account inside an AWS Organization, with least-privilege IAM access.
- Authentication. Passwords must be at least 12 characters and are stored as salted bcrypt hashes. Multi-factor authentication is available to users and is required for administrative actions. SSO (SAML/OIDC) and SCIM provisioning are available on eligible plans.
- Sessions. Refresh tokens rotate on each use. Signing out revokes them on the server. If a rotated token is reused, every session for that account is revoked.
- Access control. Roles inside each account (owner, manager, team leader, member). Optional passwords on watch pages and limits on which domains may embed a video. coReel staff access production only where needed for support, security or legal reasons.
- Change management. Every production change goes through a reviewed pull request with automated tests and secret scanning before it is merged. Direct changes to the main branch are blocked.
- Logging and monitoring. Security-relevant actions are recorded in audit logs. Service health is monitored.
- Resilience. Data is backed up regularly. Restoration follows a documented procedure.
- Vendor management. Subprocessors are bound by written data-protection terms (Section 5).
- Personnel. Staff with access are bound by confidentiality and receive security training.
- Incident response. A documented incident process, with notice to Customer under Section 7.