Aller au contenu principal

Agency Data Processing Agreement

Last updated: 2026-11-01 v1.0

About this Agreement

This Data Processing Agreement (“DPA”) is between Far Horizons OÜ, registry code 14863934, Sepapaja 6, 15551 Tallinn, Estonia, operator of Heimo (“Meridian”, “we”, “us”), and the agent or agency that uses the services listed below (“the Agency”, “you”).

It forms part of the Agent & Agency Terms of Service and meets the requirements of Article 28 of the General Data Protection Regulation (EU) 2016/679 (“GDPR”). Where this DPA and the Agent Terms differ on the processing of personal data, this DPA prevails. It applies from the day you first use a covered service and lasts as long as we process Agency Data.

1. Roles and scope

For the services below, you are the controller and we are your processor. You decide why visitors’ data is collected on your website; we store it, show it to you and deliver it to you on your behalf.

Covered serviceWhat we process for you
Agency websiteEnquiries about your listings, contact messages and valuation (appraisal) requests submitted through forms on your website
Website assistantConversations visitors have with the assistant on your website, and any enquiry it records for you
Lead inboxStoring, displaying and emailing you the leads from the two services above, and the notes you add to them

”Agency Data” means the personal data we process for you through these services.

This DPA does not cover:

  • Enquiries submitted on the Heimo portal itself. For those, we and you are joint controllers under the Joint Controller Agreement.
  • Your own account, user and billing data, which we process as an independent controller under our Privacy Policy.
  • Analytics or other tags you add to your website, such as a Google Analytics measurement ID. Those send data from visitors’ browsers straight to that provider under your own agreement with it; that provider is not our sub-processor.

2. Details of the processing

ItemDescription
Subject matterHosting your website’s forms and assistant, and receiving, storing and delivering the leads they produce
DurationFor as long as you use a covered service, and until deletion under section 11
Nature and purposeCollection, storage, retrieval, display and transmission of leads to you; generating assistant replies; keeping the service secure and working. We process Agency Data for no other purpose
Types of personal dataName, email address, phone number, message content, the listing or page the lead came from, property details and address given in a valuation request, assistant conversation text, and request metadata such as IP address and time
Categories of data subjectsVisitors to your website: prospective buyers, tenants, sellers and landlords, and anyone else who contacts you through it
Special categoriesNone are requested. Visitors may still type them into a free-text message; we treat any such content as Agency Data

3. Your instructions

We process Agency Data only on your documented instructions. Your instructions are this DPA, the Agent Terms, the way you configure the covered services, and any other written instruction you send to privacy@farhorizons.io that is consistent with them.

The only exception is where EU or Member State law requires us to process Agency Data; we will tell you before we do, unless that law forbids it. If we think an instruction breaks the GDPR or other data protection law, we will tell you straight away and may pause that instruction until you confirm or change it.

4. Your responsibilities

As controller, you are responsible for:

  • Having a lawful basis for collecting Agency Data through your website.
  • Giving your website’s visitors a privacy notice that names you as controller and explains how you use their data, including that Meridian processes it for you.
  • Obtaining any consent your website needs, including for cookies and analytics tags you add.
  • Making sure your instructions to us comply with data protection law.

5. Confidentiality

Everyone we authorise to process Agency Data is bound by a duty of confidentiality, by contract or by law, and has access only to the extent their work needs it.

6. Security

We apply the technical and organisational measures in Annex A to protect Agency Data, as required by Article 32 GDPR. We may change them over time, but never in a way that lowers the overall level of protection.

7. Sub-processors

You give us general authorisation to engage sub-processors. The sub-processors we use for Agency Data today are listed in Annex B.

  • Notice of changes. We will tell you by email at least 30 days before we add or replace a sub-processor for Agency Data.
  • Right to object. You may object on reasonable data protection grounds within that 30 days. We will then try to resolve your concern; if we cannot, you may stop using the affected service and we will refund any fees prepaid for it for the period after the change.
  • Same obligations. Each sub-processor is bound by a written contract with data protection obligations no less protective than those in this DPA.
  • Our liability. We remain fully liable to you for the performance of each sub-processor’s obligations.

8. Assistance

Taking into account the nature of the processing, we will help you:

  • Answer data subject requests. If a visitor asks us directly to exercise their rights over Agency Data, we will pass the request to you without undue delay and will not answer it ourselves unless you ask us to. On your request we will export, correct or delete the Agency Data concerned within 30 days.
  • Meet your obligations under Articles 32 to 36 GDPR, including security, breach notification, data protection impact assessments and prior consultation with a supervisory authority, by giving you the information we hold about our processing.

9. Personal data breaches

If we become aware of a personal data breach affecting Agency Data, we will notify you without undue delay and within 24 hours. Our notice will describe, as far as we know at the time, the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, and the measures taken or proposed. We will follow up as we learn more.

Because you are the controller, you decide whether to notify the supervisory authority and the data subjects. We will not notify them on your behalf unless you ask us to or the law requires it.

10. International transfers

Agency Data is stored in our managed database in Frankfurt, Germany. Some sub-processors in Annex B process it outside the European Economic Area. Each such transfer is covered by an adequacy decision, including the EU–U.S. Data Privacy Framework where the recipient is certified, or by the European Commission’s Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914) together with any supplementary measures needed.

11. Deletion and return

During the term, we keep Agency Data while your account is active. You may ask us at any time to export or delete specific records.

When you stop using the covered services, you may ask us within 30 days for an export of your Agency Data in a structured, machine-readable format. After that period we delete Agency Data from our live systems within a further 30 days, unless EU or Member State law requires us to keep it. Copies in backups expire on our hosting provider’s rolling backup cycle, currently seven days. Until then they are used only to recover the service, or to check in a separate copy that recovery works; we delete that copy once the check is done. On request we will confirm the deletion in writing.

12. Audits

We will make available to you the information needed to show that we meet Article 28 GDPR. This includes this DPA and its annexes and written answers to your reasonable security and data protection questionnaires.

You, or an independent auditor you appoint who is bound by confidentiality, may audit our compliance with this DPA once a year, and additionally after a personal data breach affecting Agency Data or where a supervisory authority requires it. Give us at least 30 days’ written notice and a scope; audits take place during business hours and must not unreasonably disrupt the service or expose other customers’ data. Each party bears its own costs.

13. Liability and law

Each party’s liability under this DPA is subject to the limitations in the Agent Terms, except where Article 82 GDPR or other mandatory law does not allow them. This DPA is governed by the laws of the Republic of Estonia, and disputes go to the courts of Tallinn, as set out in the Agent Terms.

We may update this DPA to reflect changes in law or in the services, with at least 30 days’ notice, as the Agent Terms provide. A change to Annex B follows section 7.


Annex A — Technical and organisational measures

Data location and storage

  • Agency Data is stored in a managed PostgreSQL 16 database in DigitalOcean’s Frankfurt region. Connections require TLS, and the provider encrypts the database and its backups at rest.
  • The data is split across separate logical databases. Each service connects with its own login, limited to reading and writing rows in its own database: it cannot change the schema or read another database’s tables.
  • The database connection layer does not cache query results, because the data includes personal data.

Encryption in transit

  • Every website, portal and API is served over HTTPS with TLS 1.2 or higher, terminated at Cloudflare’s edge.
  • Agency websites and the portals send HTTP Strict Transport Security headers. The portals also send a Content Security Policy and other browser security headers (X-Frame-Options, X-Content-Type-Options, Referrer-Policy and Permissions-Policy).

Application and credentials

  • Services run as isolated Cloudflare Workers and reach one another through service bindings, not through public addresses.
  • API keys and other secrets are held as encrypted Worker secrets, never in source code.
  • Passwords are stored only as salted scrypt hashes. Sign-in signing keys are encrypted with AES-256-GCM before they are stored.
  • Payment card data is handled only by Stripe and never reaches our systems.

Access and change control

  • Access to production systems is limited to Far Horizons OÜ personnel who need it.
  • Every change to the service is made through a pull request that must pass automated tests before it is merged, and production is deployed only from the main branch by an automated pipeline.
  • We monitor our software dependencies for published vulnerabilities and apply security updates.

Data subject rights

  • Export and erasure of a person’s data run across every database. If any part fails, the request is reported as failed rather than as complete.

Use of AI

  • Assistant conversations are sent to the AI provider only to generate the assistant’s reply. We do not use Agency Data to train AI models.

Annex B — Sub-processors for Agency Data

Sub-processorLocationWhat it does with Agency Data
Cloudflare, Inc. (United States)Global networkHosts your website, its forms and the assistant; runs our application services; delivers lead notification emails to you
DigitalOcean, LLC (United States)Frankfurt, GermanyHosts the managed database where leads, valuation requests and assistant conversations are stored
OpenRouter, Inc. (United States)United States, routing to the model providerAI gateway for the website assistant: passes conversation text only to the two hosts below and returns the reply
OpenAI, L.L.C. (United States), via OpenRouterUnited States and other regionsGenerates the website assistant’s replies with its GPT-4.1 mini model, from the conversation text
Microsoft Corporation (Azure, United States), via OpenRouterUnited States and other regionsServes the same OpenAI model when OpenRouter routes a request to Azure instead of OpenAI

Last updated: 1 November 2026