Konsil Data Processing Agreement

Version 2026-10-24

Version: 2026-10-24 Last updated: 2026-10-24

This Data Processing Agreement (the "DPA") is part of the Konsil Terms of Service (the "Terms") between Berry Holdings LLC ("Konsil") and the customer that accepted the Terms ("Customer"). It applies when Konsil processes Customer Personal Data on Customer's behalf. Words defined in the Terms have the same meaning here.


1. Definitions

  • Customer Personal Data means personal data within Customer Data that Konsil processes on Customer's behalf in providing the Service.
  • Data Protection Laws means the privacy and data protection laws that apply to the processing, which may include U.S. state privacy laws (such as the California Consumer Privacy Act), the EU General Data Protection Regulation ("GDPR"), the UK GDPR and Data Protection Act 2018, and the Swiss Federal Act on Data Protection.
  • 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 while it is held by Konsil or its Subprocessors.
  • Subprocessor means a third party Konsil engages to process Customer Personal Data.
  • Controller, processor, data subject, personal data, processing, business, service provider and similar terms have the meanings given in Data Protection Laws.

2. Roles and scope

2.1 Roles. Customer is the controller (or, under U.S. state laws, the business) of Customer Personal Data. Konsil is a processor (or service provider) acting on Customer's behalf. If Customer is itself a processor for another controller, Customer confirms that its controller has authorized these instructions and the appointment of Konsil, and Konsil is a sub-processor.

2.2 Konsil as controller. This DPA does not cover personal data Konsil handles as a controller, such as account, billing and website data about Customer's Users. The Konsil Privacy Policy covers that.

2.3 Connected Tools are not Subprocessors. Tools Customer chooses to connect (such as its CRM, mailbox, chat workspace, outreach tools, call recorders, analytics, or its own AI model account) are Customer's own providers. Konsil sends data to and receives data from them on Customer's instructions. They are not Konsil's Subprocessors, and Customer's agreements with them govern their processing.

2.4 Details. Annex I describes the processing.

3. Customer's instructions

3.1 Konsil follows instructions. Konsil processes Customer Personal Data only on Customer's documented instructions, unless the law requires otherwise, in which case Konsil will tell Customer first unless the law forbids it.

3.2 What counts as an instruction. Customer's instructions are:

  • the Terms, this DPA and any Order Form;
  • Customer's configuration of the Service, including which tools it connects, which Agents it runs, and its approval and auto-approve settings; and
  • other written instructions that are consistent with the Terms and that Konsil agrees to.

3.3 Unlawful instructions. Konsil will tell Customer if, in its opinion, an instruction breaks Data Protection Laws. Konsil may pause the affected processing until the instruction is changed.

3.4 Customer's responsibilities. Customer is responsible for having a lawful basis for the processing and for giving data subjects any notices, and obtaining any consents, that Data Protection Laws require, including for recording or transcribing calls and for outreach.

3.5 U.S. state law terms. Konsil will not:

  • sell or share Customer Personal Data (as "sell" and "share" are defined in the California Consumer Privacy Act);
  • keep, use or disclose it for any purpose other than providing the Service under the Terms, or outside the direct business relationship with Customer; or
  • combine it with personal data from other sources, except as Data Protection Laws allow for service providers.

Konsil will tell Customer if it can no longer meet its obligations under those laws. Customer may take reasonable steps to stop and fix unauthorized use.

3.6 No model training. Konsil does not use Customer Personal Data to train AI models, and engages its AI model Subprocessors on terms that do not allow them to do so.

4. Confidentiality

Konsil makes sure that everyone it authorizes to process Customer Personal Data is bound by a duty of confidentiality and has access only as needed for their role.

5. Security

5.1 Konsil implements and maintains the technical and organizational measures in Annex II.

5.2 Konsil may update these measures over time, as long as the update does not materially lower the overall protection of Customer Personal Data.

5.3 Customer is responsible for its own security choices in the Service, including who it gives access to, its Users' roles, and the Agent approval rules it enables.

6. Subprocessors

6.1 General authorization. Customer authorizes Konsil to use the Subprocessors listed in Annex III.

6.2 Konsil's obligations. Konsil will:

  • put a written agreement in place with each Subprocessor with data protection obligations that are at least as protective as this DPA, to the extent relevant to its service; and
  • remain responsible to Customer for its Subprocessors' performance of those obligations.

6.3 Changes, with 30 days' notice. Konsil will tell Customer at least 30 days before it adds or replaces a Subprocessor. Konsil will give notice by email to Customer's admins and by updating the list at to be confirmed. Customers may also ask to be told at legal@konsil.ai.

6.4 Objections. Customer may object on reasonable data protection grounds within that 30-day period by writing to legal@konsil.ai. The parties will discuss it in good faith. If Konsil cannot offer a reasonable alternative, Customer may end the affected part of the Service, and Konsil will refund prepaid fees for the rest of the term for that part.

6.5 Emergency replacement. If Konsil must replace a Subprocessor urgently (for example, to fix a security problem or because a provider stops its service), Konsil will tell Customer as soon as it can, and Section 6.4 still applies.

7. Personal Data Breaches

7.1 Notice. Konsil will notify Customer without undue delay, and in any case within 72 hours, after becoming aware of a Personal Data Breach.

7.2 What the notice includes. As far as Konsil knows at the time, the notice will describe:

  • the nature of the breach, including the categories and approximate number of data subjects and records involved;
  • the likely consequences; and
  • what Konsil has done, or proposes to do, to address it and reduce harm.

Where Konsil does not yet have all of this, it will provide it in stages as it learns more.

7.3 Konsil's actions. Konsil will take reasonable steps to contain, investigate and fix the breach, and will give Customer reasonable help with any notices Customer must give to regulators or data subjects.

7.4 Not an admission. Notifying Customer of a breach is not an admission of fault.

7.5 Where notices go. Konsil sends breach notices to Customer's admins by email. to be confirmed

8. Assistance

8.1 Data subject requests. If Konsil receives a request from a data subject about Customer Personal Data, it will pass it to Customer and will not answer it directly, except to confirm it has been passed on. Taking into account the nature of the processing, Konsil will give reasonable help so that Customer can respond, mostly through the Service's own features (such as editing, deleting and exporting data).

8.2 Assessments and regulators. Konsil will give reasonable help with data protection impact assessments and prior consultations with regulators, where Customer cannot do them with the information it already has.

8.3 Cost. Help beyond what the Service provides through its normal features may be charged at reasonable rates agreed in advance, unless the request arises from Konsil's breach of this DPA.

9. Deletion and return

9.1 During the term. Customer can delete Customer Personal Data in the Service. Customer can ask Konsil for an export of Customer Personal Data at any time, and Konsil provides it within 5 business days of the request.

9.2 After the term. When the Terms end, Konsil will:

  • let Customer export Customer Personal Data for 90 days, as described in the Terms; and
  • delete it from Konsil's live systems when that 90-day export window closes, or once an export Customer requested during the window has been delivered, whichever is later, and no later than 120 days after the end date.

Backup copies are overwritten on their normal schedule to be confirmed and stay protected until then. Konsil may keep data longer only where the law requires it, and this DPA continues to protect it while Konsil does.

9.3 Connected Tools. Deletion in Konsil does not delete data held in Customer's Connected Tools.

9.4 Confirmation. On written request, Konsil will confirm in writing that deletion is complete.

10. Audits

10.1 Questionnaire first. Konsil will make available the information reasonably needed to show that it meets this DPA. On Customer's written request, no more than once in any 12-month period, Konsil will answer a reasonable written security and privacy questionnaire, and will provide relevant summaries of its security documentation and of its Subprocessors' audit reports or certifications, where Konsil has them and may share them.

10.2 Further audit. If the questionnaire and documents do not reasonably show compliance, or a regulator requires it, or after a Personal Data Breach, Customer may audit Konsil's compliance with this DPA, by itself or through an independent auditor bound by confidentiality who is not a Konsil competitor. Customer must give at least 30 days' written notice, agree the scope with Konsil in advance, carry out the audit during business hours without disrupting Konsil's operations, and pay its own costs. Audits of Subprocessors happen through their own audit reports.

10.3 What is not available. Konsil does not currently hold a SOC 2 report or similar certification. Audits do not give access to other customers' data or to information that would compromise Konsil's security.

11. International transfers

11.1 Where data is processed. Konsil and its main Subprocessors process Customer Personal Data in the United States.

11.2 EU transfers. To the extent the processing involves a transfer of personal data protected by the GDPR to a country without an adequacy decision, the parties agree to the Standard Contractual Clauses approved by the European Commission in Decision (EU) 2021/914 (the "SCCs"), which are incorporated by reference, 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 clause) applies;
  • in Clause 9, Option 2 (general written authorization) applies, with the notice period in Section 6.3 of this DPA;
  • the optional wording in Clause 11 does not apply;
  • in Clause 13, the competent supervisory authority is the one that the SCCs point to based on Customer's establishment or representative;
  • in Clause 17, the SCCs are governed by the law of Ireland to be confirmed;
  • in Clause 18, disputes are resolved by the courts of Ireland;
  • Annex I of the SCCs is completed by Annex I of this DPA; Annex II by Annex II of this DPA; and Annex III by Annex III of this DPA.

11.3 UK transfers. To the extent the processing involves a transfer of personal data protected by UK data protection law, the parties agree to the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses issued by the UK Information Commissioner (version B1.0 or its current successor, the "UK Addendum"), which is incorporated by reference. Tables 1 to 3 of the UK Addendum are completed by the details in this DPA and its annexes. For Table 4, either party may end the UK Addendum as allowed by its Section 19.

11.4 Swiss transfers. For personal data protected by Swiss law, the SCCs apply with these changes: references to the GDPR include the Swiss Federal Act on Data Protection, the Swiss Federal Data Protection and Information Commissioner is the competent supervisory authority, and "member state" includes Switzerland so that data subjects there can bring claims in their place of habitual residence.

11.5 Precedence. If the SCCs or UK Addendum conflict with this DPA or the Terms, the SCCs or UK Addendum control.

12. Liability

Each party's liability under this DPA is subject to the limits and exclusions in the Terms, except where Data Protection Laws or the SCCs do not allow that.

13. Term

This DPA lasts as long as Konsil processes Customer Personal Data on Customer's behalf, including after the Terms end, until deletion is complete.


Annex I — Details of processing

A. Parties

Data exporterData importer
NameCustomer, as named in its account or Order FormBerry Holdings LLC
AddressAs in its account or Order Form30 N Gould St, Ste R, Sheridan, WY 82801, USA
ContactCustomer's account adminslegal@konsil.ai
ActivitiesUses the Service for its businessProvides the Service
RoleController (or processor)Processor (or sub-processor)
Signature and dateBy accepting the TermsBy making the Service available

B. Description of the transfer and processing

ItemDetails
Categories of data subjectsCustomer's staff and Users; Customer's customers, prospects, leads, partners and suppliers and their staff; people who appear in Customer's emails, messages, calls and documents; recipients of Customer's outreach and social posts; website visitors whose data appears in Customer's analytics
Categories of personal dataNames; business contact details (email, phone, company, job title, LinkedIn profile URL); CRM records (contacts, companies, deals, notes, tasks, activity history); email and chat message content and metadata; call recordings, transcripts and summaries from connected call recorders; documents and files Customer uploads or connects; outreach and engagement data (sends, opens, replies, unsubscribes); website and campaign analytics; Agent outputs (drafts, summaries, proposed actions)
Sensitive dataNone intended. The Terms prohibit special categories of data, health information, government ID numbers, payment card data and children's data unless agreed in writing. If such data appears incidentally in content Customer connects (for example in an email body), it is handled under the same Annex II measures.
FrequencyContinuous, for as long as Customer uses the Service
Nature of processingCollecting from Connected Tools; storing; organizing; analysing and summarizing with AI models; drafting content; writing, sending or posting to Connected Tools as Customer's settings allow; exporting; deleting
PurposeProviding the Service to Customer: running AI agents that help Customer with its sales, marketing, customer success and operations work, under Customer's instructions
RetentionFor the term, then as set out in Section 9 (export for 90 days; deletion from live systems when that window closes or once an export requested during it has been delivered, whichever is later, no later than 120 days after the end date; backups expire on their schedule)
Subprocessor transfersAs listed in Annex III, for the purposes stated there, for the duration of the Service

C. Competent supervisory authority

As set out in Section 11.2.


Annex II — Technical and organizational security measures

These are the measures Konsil uses today. They describe the controls in place as of this document's version.

1. Tenant isolation

  • Each customer is a separate organization. Every customer data record carries its organization's identifier.
  • The database enforces row-level security (RLS), so a signed-in user can read only the records of organizations they are a member of.
  • Server-side routes check the user's organization membership before acting, including on cached data.
  • File storage is split by organization path, and storage policies check that path. Working files are kept in private storage and shared through short-lived signed links.
  • Automated tests check that one test organization cannot read or change another's data.

2. Access control

  • Sign-in uses Supabase Authentication.
  • Users have roles within their organization (for example admin and viewer). The database refuses writes from read-only roles on covered data.
  • Multi-factor authentication is required for admin roles. Any exception is recorded.
  • Signup and invitation endpoints are rate-limited.
  • Konsil staff access to production systems is limited to the people who operate the Service. to be confirmed

3. Encryption

  • Data travels over encrypted connections (HTTPS/TLS).
  • The database and file storage are hosted by Supabase, which encrypts data at rest.
  • Credentials for Connected Tools are stored encrypted with AES-256-GCM using an application key kept outside the database. If that key is missing, the Service refuses to save a new credential rather than store it unencrypted. to be confirmed
  • Secrets are kept in the hosting provider's encrypted variable store, never in source code.

4. AI agent controls

  • Each Agent belongs to one organization. Data is separated by organization through row-level security on all tables in the database, together with application-level access checks in the Service. Scheduled Agents currently run with a database credential that is not limited to a single organization, so separation for scheduled runs relies on these application-level checks rather than on a per-Agent credential.
  • Where approval policies exist (writes to Function and Workspace records), Agent Actions follow the approval policy Customer sets: proposed for human review, or automatically applied under rules Customer enables. Other Agent Actions run as Customer has configured them. Action limits cap how much an Agent can change in one run.
  • Outbound requests the Service makes to web addresses are checked to block access to private or internal networks.
  • Outreach audiences are checked against Customer's suppression lists when a campaign is built and again before it is launched.
  • AI model providers used by Konsil are engaged on terms that do not permit training on Customer Data.

5. Monitoring and logging

  • Agent runs and their results are recorded and visible to Customer in the Service.
  • Every background worker reports a regular heartbeat. A watchdog alerts Konsil when a worker goes silent.
  • Logs from the hosting platforms are retained, and Konsil reviews them when investigating an issue. Konsil does not currently run systematic error monitoring across the application.

6. Secure development

  • All code changes go through version control on a separate branch and a pull request, with automated checks (tests, type checks, isolation checks) and automated code review before merge.
  • Dependencies are reviewed during development and updated when issues are found.
  • A separate staging environment with its own database is used for testing.

7. Availability and recovery

  • The Service runs on managed cloud infrastructure (Railway and Supabase).
  • The database is backed up by Supabase. to be confirmed
  • Customer can ask Konsil for an export of its data at any time. Konsil staff provide it within 5 business days of the request.

8. Incident response

  • Konsil investigates suspected security incidents promptly and notifies customers as set out in Section 7 of this DPA.

9. Subprocessor management

  • Konsil reviews a provider's security and data protection terms before engaging it, and lists each Subprocessor in Annex III.

Annex III — Subprocessors

Last updated: 2026-10-15. Konsil gives 30 days' notice before adding or replacing a Subprocessor (Section 6.3).

A. Core Subprocessors (used for every customer)

SubprocessorPurposeDataLocation
Supabase, Inc.Database, authentication and file storageAll Customer Data stored in the ServiceUnited States (AWS us-west-2, Oregon)
Railway CorporationApplication and background worker hostingAll Customer Data processed by the Service, in memory and logsUnited States to be confirmed
Cloudflare, Inc.DNS and network delivery for Konsil domains, website analytics (cookieless, aggregate) and Turnstile bot checks on Konsil formsRequest metadata (IP address, headers), bot-check signals and data in transitUnited States and global edge network
Anthropic, PBCAI models that power Agents (unless Customer connects its own model account)Content Agents read or draft: CRM records, messages, transcripts, documentsUnited States
Resend, Inc.Sending service emails (invitations, sign-in, notifications)User names and email addresses; email contentUnited States
Stripe, Inc.Billing for paid plansBilling contact details and payment informationUnited States
ZernioPublishing social media posts (including LinkedIn) for Konsil-hosted social publishingPost content and the connected social profile detailsto be confirmed

B. Feature Subprocessors (used only when Customer turns on the feature)

to be confirmed

SubprocessorFeatureDataLocation
ClayContact and company enrichmentNames, companies, work emails, LinkedIn URLs of contacts to enrichUnited States
DeeplineContact and company enrichmentNames, companies, work emails, LinkedIn URLs of contacts to enrichto be confirmed
DataForSEOSearch and website performance dataWebsite domains and search keywords (generally no personal data)to be confirmed
GitHub, Inc.Hosting and publishing Customer website content managed in the Service, where the site's code lives in a Konsil-managed repositoryWebsite content and postsUnited States

C. Connected Tools (Customer's own providers, not Subprocessors)

Customer chooses to connect these with its own accounts, and its agreements with these providers govern their processing (Section 2.3). Examples: HubSpot; Google (Gmail, Google Analytics 4, Google Drive); Microsoft (Outlook, Teams, OneDrive and SharePoint); Slack; HeyReach and LinkedIn; Instantly; call recorders such as Granola, Gong, Fathom or Fireflies; and AI model accounts Customer connects itself (Anthropic, OpenAI, xAI, Google Gemini or a compatible server).

to be confirmed