Subprocessors

Last Updated: February 1, 2026

Harmonity is built for teams handling sensitive contract work. To operate the Service, we may use carefully selected third-party service providers (“Subprocessors”) that process Customer Personal Data on our behalf (as a Processor), under written agreements and security requirements consistent with our Data Processing Addendum (DPA).

  • Product / Service subprocessors (used to deliver Harmonity to customers)
  • Website / marketing third parties (used on harmonity.ai and related pages), where applicable

For questions, contact

1. Definitions (quick)

Customer Personal Data: Personal data contained in Customer Data (e.g., contract documents, signatory details, user account data).
Subprocessor: A vendor that processes Customer Personal Data on Harmonity’s instructions to provide the Service.
Processing region: High-level region where data may be processed or stored (e.g., Türkiye, EU/EEA, US), depending on configuration and vendor.

2. Product / Service Subprocessors

The table below lists subprocessors involved in providing the Harmonity Service (e.g., hosting, support tooling, security monitoring). Some vendors may process only limited metadata rather than full contract documents.

SubprocessorPurposeTypical data processedProcessing region
Cloud Infrastructure / Hosting ProviderCore hosting and compute for the ServiceCustomer Data stored/processed in the Service (including documents and metadata)TR / EU / US
Object Storage / Backup ProviderSecure storage and backupsEncrypted backups; stored Customer DataTR / EU / US
Email Delivery ProviderService emails (invites, notifications, security alerts)User email addresses, notification metadataTR / EU / US
Customer Support / Ticketing ToolCustomer support operationsSupport requests, contact info, attachments submitted to supportTR / EU / US
Error Monitoring / Logging ToolReliability and incident diagnosisTechnical logs/telemetry; may include user IDs and limited metadataTR / EU / US
Analytics (Product) VendorProduct usage analytics (in-app)Usage events, device/browser data; typically pseudonymous identifiersTR / EU / US
AI Model / AI Infrastructure ProviderAI-enabled features initiated by Customer (Harmony AI)Inputs/outputs to generate requested AI results (as configured)TR / EU / US

Important boundaries (as committed in the DPA):

  • Subprocessors may only process Customer Personal Data to provide the Service under our instructions.
  • No training on Customer Data for general-purpose models unless Customer explicitly opts in in writing.

3. Website / Marketing Third Parties

This section is for transparency about third parties used on our website (e.g., embedded video, chat widgets, analytics, ad pixels). These providers may set cookies or collect data as described in our Cookie Statement and Cookie Preferences controls.

Provider categoryExample useData involvedNotes
Embedded videoYouTube / Vimeo embedsIP address, device/browser data, page interactionsControlled via cookie categories where applicable
Chat widgetIntercom / HubSpot / similarChat content, contact details you submit, device/browser dataYou can choose what you share
Website analyticsAnalytics vendor(s)Page views, events, device/browser dataConsent-based (Analytics category)
Advertising pixelsMeta / LinkedIn / GoogleAd attribution and measurement dataConsent-based (Marketing category)

If a vendor acts as an independent controller for its own purposes (common for some ad platforms), that will be described in our Cookie/Privacy documentation.

4. How we add or change subprocessors

We update this page as subprocessors change.

Notice approach

  • We will post updates to this page promptly.
  • Where commercially reasonable, we aim to provide advance notice for material subprocessor changes via reasonable channels (e.g., email or in-product notice).

Customer objections

  • If you have a reasonable data protection objection to a new subprocessor, contact support@harmonity.ai with details.
  • We will work in good faith to address objections (e.g., provide information, suggest a workaround, or consider alternatives where feasible).
  • If we cannot resolve the objection, applicable remedies (including termination of the affected Service component) follow the Agreement and DPA.

5. How we evaluate subprocessors

Before engaging a subprocessor, we apply risk-based due diligence and contractual safeguards, including:

  • Written data processing obligations (confidentiality, security, breach notification)
  • Scope-limitation (least-privilege access and purpose limitation)
  • Security review appropriate to the risk (architecture controls, access controls, incident practices)
  • Ongoing vendor management aligned with operational needs

6. International transfers

Depending on vendor location and Customer configuration, data may be processed outside Türkiye and/or outside the EU/EEA/UK.

Where GDPR/UK GDPR applies, we support appropriate transfer mechanisms where required (e.g., Standard Contractual Clauses / UK addendum). Where KVKK applies and specific safeguards are required for cross-border transfers, we will cooperate in good faith to implement the required mechanism as applicable.

See the Data Processing Addendum (DPA) for full details on international transfer mechanisms.

7. Change log

DateChange
February 1, 2026Initial publication