Data Processing Agreement

If you are subject to the GDPR, the UK GDPR or similar legislation and need a signed data processing agreement with Linkeddit, we will provide one. This page sets out the position that agreement reflects, so you know what you are signing before you ask for it.

Last updated 31 August 2026.

How to request one

Email team@om.linkeddit.com from the address on your account, with your legal entity name and the address for notices. We will send a DPA for signature. There is no charge and it is not limited to a particular plan.

We do not offer a click-through DPA on this page on purpose. An unsigned template presented as executed is not an agreement, and a real one needs your entity details.

The position it reflects

Our role
For the data you put into Linkeddit, you are the controller and we are the processor. We process it to provide the product and for no other purpose.
What we process
Account details (name, email, billing identifiers), the projects and questions you configure, the domains and competitors you track, and the measurement evidence we collect on your behalf from answer engines and public web pages.
What we do not process
We do not collect special category data, and the product has no reason to. Do not put it into free-text fields.
Where
Primarily the United States. Two sub-processors also process in the European Union. The full list, with locations, is on the sub-processors page.
Retention
Account data is retained while your account is active. Measurement evidence is retained so that trends remain meaningful over time, since a visibility trend with deleted history is not a trend. On account deletion we remove your data within 30 days, except where we are required to keep billing records.
Sub-processor changes
We publish the current list and update it when it changes. Customers with a signed agreement that requires advance notice can ask to be notified.
Security
Described on our security page, which states what we do and is explicit about what we do not yet claim.

See also our security practices, sub-processors and privacy policy.