Revient Partner Data Processing Addendum
This addendum is between the company that operates Revient, whose registered name, number and office are shown on this page once registration is complete ("Revient") and the organisation named in the signature record ("the Partner", "you"). Every partner signs it. It forms part of, and is read with, the Revient Partner Platform Terms ("the Platform Terms"), and it prevails over them on personal data. Words defined in the Platform Terms have the same meaning here.
Key terms in brief
This box is a reading aid. The numbered clauses are what count.
- Roles. The Merchant controls its Customers' data. Revient processes it for the Merchant. You receive it as a controller in your own right for your collection or purchase, under this addendum (clause 2).
- What you get. Only what the Case needs: name, email, postcode, the order and the evidence. The delivery address only through the address release. Never a phone number, card details or a billing address (clause 3).
- Security. At least the measures in the Annex, including two-step sign-in and encryption (clause 5).
- Breaches. Tell Revient as soon as you can, aiming for 12 hours and never later than 24 hours after you become aware (clause 7).
- Deletion. Within 30 days of a Case closing, keeping only what the Law requires or a legal claim needs, locked away (clause 9).
1Words used
1.1Data Protection Law means every law on personal data that applies to the processing, including the UK GDPR and the Data Protection Act 2018, the EU GDPR, the California Consumer Privacy Act, Canada's PIPEDA and Australia's Privacy Act 1988.
1.2Case Data means personal data about a Customer, or about a Merchant's staff, that you receive through the Platform or create while working a Case.
1.3Controller, processor, personal data, personal data breach, data subject and processing have the meanings in the UK GDPR.
2Roles
2.1The Merchant is the controller of its Customers' personal data. Revient processes it for the Merchant to build and run the Case, and is a controller only for its own platform purposes: running accounts, vetting partners, security, audit records, billing and defending legal claims. Revient does not build profiles of Customers across Merchants or use Case Data to train models for anyone else.
2.2Collection. When you accept a Case to collect, you receive the Case Data as an independent controller for your collection activity, because you decide, within this agreement and the Law, how and when to contact the Customer. This addendum is the data sharing agreement between you, Revient and the Merchant for that Case. Where the Law of the Customer's country, or a regulator there, treats a collection agency as the creditor's processor (as in Ireland), you act as the Merchant's processor for that Case, and the processor terms in clause 11 apply as well.
2.3Purchase. Before a sale, you receive the Case Data shown for review as an independent controller, only to decide whether to offer. From the Transfer Date you are the controller of the Case Data for the purchased debt.
2.4The parties are not joint controllers.
3What is shared and why
3.1This is what is shared, and why.
| People | Customers of Merchants; the Merchant's named contacts |
| At referral | Name, email address, postcode and country; the order (what, when, where to, for how much); the chargeback and its reason; the evidence file, reduced to what the Case needs |
| Only by address release | The delivery address, released as clause 3 of the Collection Agency Agreement describes (and with the Case for Customers in the United States) |
| Created by you | Contact log, messages and replies, payments, plans, disputes, complaints, and any vulnerability note you need to treat the Customer fairly |
| Never shared | Telephone number, card details, billing address, account passwords, and any special category data |
| Purpose | Recovering, or deciding to buy and then owning and recovering, the amount on that Case, and meeting your legal duties about it |
| Lawful basis | The Merchant's and your legitimate interests in recovering a lawful debt, and establishing, exercising or defending legal claims |
| How long | Until clause 9 applies |
3.2You must use Case Data only for the purpose in clause 3.1, only for the Case it belongs to, and only as far as that purpose needs. You must not combine it with other data to build a profile of the Customer, use it for marketing, sell it, or use it to train a model.
3.3The delivery address may not be where the Customer lives. You must check it before relying on it, as the Collection Agency Agreement says.
4Your duties as a controller
4.1You must comply with Data Protection Law in your processing of Case Data.
4.2You must tell the Customer, in or with your first message, who you are, that you act for the named Merchant (or, after a purchase, that you own the debt), where you got their information, and where they can read your privacy notice, and you must keep that notice accurate.
4.3You must not pass Case Data to anyone else, including a subcontractor, tracing agent or later buyer, unless:
(a)Revient has agreed in writing (for a later buyer, clause 5 of the Debt Purchase Agreement applies instead);
(b)you have a written contract with them that imposes duties at least as strict as this addendum; and
(c)you remain responsible for what they do with it.
4.4You must not disclose Case Data to a public authority unless the Law requires it, and you must tell Revient first where the Law allows.
5Security
5.1You must protect Case Data with appropriate technical and organisational measures, and at least those in the Annex.
5.2Only your staff who need Case Data to work the Case may access it. Each must be bound to confidentiality and trained in data protection and in fair treatment of Customers.
6Transfers outside the UK and EEA
6.1You must not transfer Case Data, or allow access to it, from outside the United Kingdom and the European Economic Area unless a lawful transfer mechanism applies.
6.2Where Case Data is transferred to you outside the United Kingdom or the European Economic Area, and no adequacy decision or data bridge covers you, the following are incorporated into this addendum and apply, with Revient (or the Merchant) as exporter and you as importer:
(a)for data from the United Kingdom, the International Data Transfer Addendum to the EU Standard Contractual Clauses issued by the Information Commissioner, with the tables completed from this addendum; and
(b)for data from the European Economic Area, the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914), module one (controller to controller), or module two where clause 11 applies, with clause 7 (docking) included, option 2 of clause 9 where it applies, the optional wording in clause 11 omitted, Irish law in clause 17 and the courts of Ireland in clause 18.
6.3If a mechanism stops being valid, the parties must agree a replacement promptly, and you must suspend transfers until it is in place where the Law requires.
7Personal data breaches
7.1You must tell Revient of any actual or reasonably suspected personal data breach affecting Case Data without undue delay, aiming for 12 hours and never later than 24 hours after you become aware of it, at privacy@revient.io and through the Platform.
7.2You must give what you know at the time (what happened, which Cases and Customers, what data, the likely consequences and what you are doing) and keep Revient updated. You must take reasonable steps at once to contain it.
7.3You must not tell a Merchant, Customer or the press about a breach affecting Revient's Platform or another partner without talking to Revient first, unless the Law requires you to. This does not stop you notifying a regulator or a Customer where the Law requires it.
7.4Revient tells you without undue delay of a personal data breach on its side affecting Case Data you hold or receive.
8Requests from Customers
8.1You answer requests and objections from Customers about your own processing yourself, within the time the Law allows. Where a request also concerns Revient's or the Merchant's processing, you must pass it to Revient through the Platform within 2 Business Days.
8.2You must record in the Platform when a Customer objects, withdraws consent to a channel, or asks not to be contacted in a certain way, and honour it. Where you continue processing because it is needed for a legal claim, you must record why.
8.3Where Revient receives a request to delete a Customer's data from a Merchant's store platform or from the Customer, you must delete the Case Data concerned within 10 days, keeping only what the Law requires you to keep or what a legal claim already started needs, and confirm it.
9Keeping and deleting
9.1When a Case is closed, withdrawn or handed back, you must delete Case Data within 30 days, or return it through the Platform if Revient asks.
9.2You may keep only what the Law requires you to keep (for example, records a regulator requires) or what is needed to establish, exercise or defend a legal claim about the Case, for no longer than that requires and in any event no longer than 6 years after the Case closes unless proceedings are under way. Anything you keep must be locked away from everyday use.
9.3After a purchase, clause 9.1 applies when the debt is paid, settled, written off, bought back or sold on.
10Checks
10.1You must give Revient the information it reasonably needs to show you comply with this addendum, and allow the checks in clause 10 of the Platform Terms. Revient may ask for completion of a security questionnaire once in any 12 months.
10.2Where the California Consumer Privacy Act applies, you certify that you understand and will comply with the restrictions in this addendum, and Revient may take reasonable steps to stop and remedy any unauthorised use of Case Data.
11Processor terms
Where clause 2.2 makes you the Merchant's processor for a Case, you must also, for that Case:
(a)process Case Data only on the Merchant's documented instructions given through the Platform, including on transfers, unless the Law requires otherwise, in which case you tell the Merchant first where the Law allows;
(b)ensure the people processing it are bound to confidentiality;
(c)take the measures in clause 5 and the Annex;
(d)engage another processor only with the Merchant's prior written authorisation given through the Platform, on terms imposing the same duties, remaining liable for it;
(e)help the Merchant, by appropriate measures, to answer requests from Customers;
(f)help the Merchant meet its duties on security, breach notification, impact assessments and prior consultation, taking into account the information available to you;
(g)at the Merchant's choice, delete or return all Case Data at the end of the work, and delete copies unless the Law requires you to keep them;
(h)make available all information needed to show compliance with this clause, and allow and contribute to audits by the Merchant or an auditor it appoints, through Revient; and
(i)tell the Merchant at once if, in your opinion, an instruction breaks Data Protection Law.
12Liability
12.1Clause 13.5 and clause 14 of the Platform Terms apply to this addendum. Nothing in this addendum limits a Customer's rights under Data Protection Law against any party.
12.2A Merchant may enforce this addendum as it concerns its Cases, as clause 21.4 of the Platform Terms describes.
Annex: minimum security measures
-
Access. Named accounts for every person, two-step sign-in for every account that can see Case Data, access limited to staff who need it, and removed within one Business Day when they no longer do.
-
Encryption. Case Data encrypted in transit (TLS 1.2 or later) and at rest, including on laptops, phones and backups.
-
Systems. Supported, patched software; malware protection; firewalls; secure configuration. Holding Cyber Essentials (UK), ISO 27001, SOC 2 or an equivalent recognised certification, or meeting its requirements.
-
Logging. A record of who accessed and changed Case Data, kept for at least 12 months.
-
Staff. Confidentiality undertakings, background checks where the Law allows, and data protection training at the start and at least every year.
-
Separation. Case Data kept apart from other clients' data and not copied into personal accounts, personal email or unapproved tools, including artificial intelligence tools that keep or learn from what they are given.
-
Incidents. A written incident response plan, tested at least once a year.
-
Continuity. Backups tested at least once a year, and a plan to keep paying Merchants and answering Customers through an outage.
-
Disposal. Secure deletion of Case Data and secure destruction of paper and media.
-
Review. These measures reviewed at least once a year and after any incident.