Peering Data Processing Agreement

This Peering Data Processing Agreement ("DPA") is between agentcensus ("agentcensus," "we," "us," or "our"), as processor, and the organisation on whose behalf it is accepted ("you," "your," or the "Organisation"), as controller. It applies to personal data in Descriptors, as the Peering Agreement defines them, and to nothing else.

Version peering-dpa/2026-10-14 · Legal enquiries to legal@agentcensus.io · See also the Peering Agreement and the privacy policy

1. Scope and roles

An administrator of the Organisation accepts this DPA in the console, with the Peering Agreement, before the Organisation is granted the peering capability.

For personal data in Descriptors, you are the controller and we are your processor. For the records of disclosure the Service keeps, and for the identity of the person behind each act on a peering, we are the controller, this DPA does not apply, and the privacy policy does.

2. The processing

• Subject matter and purpose: storing Descriptors, checking their signatures, and serving each one to the Partners you share it with.
• Nature: storage, signature verification, retrieval, transmission to the Partners you name, backup, and deletion.
• Personal data: a Descriptor accepts only the fields its format lists, and none of them is meant for personal data. Personal data reaches us only where you put it in a Descriptor, for example a person's name in a free-text field, or an identifier that relates to an individual.
• Data subjects: whoever that personal data relates to, typically your own staff.
• Duration: while the Descriptor is stored with us, and then until its backups expire.

3. Your instructions

We process this personal data only on your documented instructions. The Peering Agreement, this DPA, and the Shares, peerings and deletions your administrators make in the console are those instructions. If we believe an instruction breaks data protection law, we will tell you. If the law requires us to process the data otherwise, we will tell you first, unless the law forbids it.

4. Our obligations

1. Confidentiality. Only people who need access to run the Service have it, and they are bound by confidentiality.
2. Security. We keep Descriptors in records owned by your organisation, and serve them to Partners only through a database role that owns no table, holds no table privilege, and returns a Descriptor only to a Partner with a live Share. The security measures in section VIII of the privacy policy also apply.
3. Sub-processors. You authorise Amazon Web Services, which hosts the Service in the United States, and members of our group of companies, including Infoblox and its affiliates. We will tell you before adding or replacing a sub-processor, you may object, and if we cannot meet your objection you may end the Peering Agreement. We impose on each sub-processor obligations no less protective than these, and we remain responsible for it.
4. Location and transfers. The data is stored and processed in the United States. Where the law that applies to you requires a transfer mechanism for that, we will put one in place with you.
5. Assistance. We help you respond to requests from data subjects, and with security, breach notification, impact assessments and consultations with authorities, as the processing and the information available to us allow. You can delete a Descriptor in the console at any time.
6. Breaches. We tell you without undue delay after becoming aware of a personal data breach affecting this data, with the information we have and as more becomes available.
7. Deletion. When you delete a Descriptor, or when your organisation is deleted, we delete the personal data in it. Copies in backups expire on the backup schedule and are not restored except to recover the Service.
8. Information and audits. We make available the information needed to show that we meet these obligations, and we allow for and contribute to reasonable audits, on reasonable notice and at your cost.

5. What we do not do

We do not sell this personal data, use it for our own purposes, or combine it with other data, except as the Peering Agreement allows for running the Service. Partners that receive a Descriptor are recipients you choose. They are not our sub-processors, and what they do with it is between you and them.

6. Everything else

This DPA ends when the Peering Agreement ends, except section 4's deletion obligation, which continues until it is met. The Terms' limitations of liability, governing law and dispute provisions apply. Where this DPA and the Peering Agreement or the Terms conflict on personal data in Descriptors, this DPA governs.