Screen and Protect:
Data Processing and Handling Agreement (Hostaway Hosts)
DATA PROCESSING AND HANDLING AGREEMENT
BETWEEN:
- Truvi Technologies Ltd, a company incorporated in the United Kingdom under registration number 11871938, whose registered office is at 3rd Floor, 1 Ashley Road, Altrincham, Cheshire, United Kingdom, WA14 2DT (“Truvi”); and
- the person or business that accepts this Agreement in accordance with clause 2.1 (the “Host”).
BACKGROUND
A. Truvi is a Trust and Safety SaaS platform for short-term vacation rentals. Its Screen and Protect services enable Hosts to screen guests before a stay and to request protection against property damage caused during a stay.
B. The Host offers Screen and Protect on its Bookings through the platform of a Distribution Partner, and has accepted Truvi’s Host Protection terms.
C. To provide the Truvi Services, Truvi processes Personal Data about the Host’s Guests, mainly as the Host’s Processor and in limited cases as an independent Controller.
D. The Parties enter this Agreement to record and formalise their data processing and handling arrangements in relation to the Truvi Services.
IT IS NOW AGREED BY THE PARTIES AS FOLLOWS:
1. INTERPRETATION AND DEFINITIONS
1.1 The following terms shall have the following meanings for the purposes of this Agreement:
“Agreement” means these terms and conditions, including all Appendices;
“Appendix” means an appendix to this Agreement;
“Approved” means a status allocated to a Booking with no significant risks identified following Validation;
“Booking” means a confirmed stay submitted to Truvi for the Truvi Services;
“Business Day” means Monday to Friday (excluding bank or public holidays in England and Wales);
“Data Protection Legislation” means all laws relating to privacy and the processing of Personal Data that apply to a Party in connection with this Agreement, including, where applicable: (a) the UK GDPR, the Data Protection Act 2018 and the Privacy and Electronic Communications (EC Directive) Regulations 2003, each as amended by the Data (Use and Access) Act 2025; (b) the EU GDPR and national laws implementing or supplementing it; and (c) the US State Privacy Laws; in each case as amended or replaced from time to time;
“Data Protection Particulars” means, in relation to any Processing under this Agreement: (a) the subject matter and duration of the Processing; (b) the nature and purpose of the Processing; (c) the type of Personal Data being Processed; and (d) the categories of Data Subjects;
“Data Subject Request” means an actual or purported request, notice or complaint from (or on behalf of) a Data Subject exercising their rights under the Data Protection Legislation;
“Distribution Partner” means the software provider through whose platform the Host offers the Truvi Services and accepts this Agreement;
“EU GDPR” means Regulation (EU) 2016/679;
“Flagged” means a status allocated to a Booking after risks have been identified following Validation;
“Guest” means the lead guest named on a Booking. Truvi does not request, and the Host shall not provide, Personal Data about other occupants or about anyone under 18;
“Host Protection terms” means Truvi’s terms for property damage protection accepted by the Host;
“Personnel” means all persons engaged or employed from time to time by the relevant Party, including employees, consultants, contractors and permitted agents;
“Rejected” means a status allocated to a Booking when significant risks have been identified following Validation;
“Restricted Transfer” means a transfer of Shared Personal Data (including remote access to it) that is subject to the UK GDPR to a recipient outside the United Kingdom, or that is subject to the EU GDPR to a recipient outside the European Economic Area;
“Security Requirements” means the requirements on the security of Personal Data in Article 5(1)(f) and Article 32 of the UK GDPR or EU GDPR (as applicable) and any equivalent requirement of the US State Privacy Laws;
“Shared Personal Data” means the Personal Data processed by Truvi under this Agreement, as described in Appendix 1;
“Status” means the Approved, Flagged or Rejected status allocated to a Booking;
“Sub-processor” means a third party, including an affiliate of Truvi, that Processes Shared Personal Data on behalf of Truvi where Truvi acts as the Host’s Processor;
“Truvi Services” means the Screen and Protect services provided by Truvi in respect of the Host’s Bookings, as described in the Host Protection terms;
“UK GDPR” has the meaning given in section 3(10) (as supplemented by section 205(4)) of the Data Protection Act 2018;
“US State Privacy Laws” means the California Consumer Privacy Act of 2018 as amended by the California Privacy Rights Act (“CCPA”) and each other US federal or state law regulating the Processing of personal information of individuals that applies to a Party in connection with this Agreement, in each case as amended;
“Validation” means the checks performed by Truvi to allocate a Status to a Booking, namely name verification, phone and/or email verification and a Watchlist check;
“Watchlist” means Truvi’s internal database of individuals in respect of whose Bookings Truvi may decline to provide protection, maintained in accordance with clause 3.17.
The terms “Controller”, “Data Subject”, “Personal Data”, “Personal Data Breach”, “Processor” and “Processing” have the meanings given in the UK GDPR or EU GDPR (as applicable), and “Process” and “Processed” shall be construed accordingly. Under the US State Privacy Laws, “Controller” includes a “business” and “Processor” includes a “service provider” or “contractor”. Truvi does not request, and the Host shall not provide, special category data, criminal offence data or sensitive personal information.
1.2 In this Agreement:
1.2.1 the headings are for ease of reference only and shall not affect its interpretation;
1.2.2 references to a clause or Appendix are to a clause of, or Appendix to, this Agreement. The Appendices form part of this Agreement;
1.2.3 unless the context otherwise requires, the singular includes the plural and vice versa, and words denoting any gender include all other genders;
1.2.4 references to any statute, regulation or guidance include it as amended, re-enacted or replaced from time to time;
1.2.5 a reference to a person includes natural persons, partnerships, companies and any other entity capable of legal personality;
1.2.6 the words “other”, “including” and “in particular” do not limit the generality of any preceding words; and
1.2.7 where expressions are not defined and have a special meaning in the short-stay vacation rental sector, they are to be interpreted accordingly.
2. COMMENCEMENT AND TERM
2.1 The Host accepts this Agreement by ticking the acceptance box presented through the Distribution Partner’s platform when activating the Truvi Services. By doing so, the Host confirms it has authority to accept this Agreement for itself or for the business it represents. Neither the Host nor the Distribution Partner may amend this Agreement. The Host further confirms that it enters this Agreement in the course of business and not as a consumer.
2.2 This Agreement commences on acceptance and continues until Truvi no longer holds any Shared Personal Data received in respect of the Host’s Bookings (the “Term”). This includes data held after the Host stops using the Truvi Services, for example for an open protection payment request or a Watchlist entry.
2.3 Truvi may update this Agreement to reflect changes in the law, regulatory guidance or the Truvi Services, on at least 30 days’ notice of any material change. If a change materially reduces the protection given to Shared Personal Data, the Host may stop using the Truvi Services before it takes effect. Continued use after that date means the Host accepts the change.
3. DATA PROTECTION
3.1 Each Party shall comply with its respective obligations under the Data Protection Legislation. For the purposes of this Agreement, the Host is the Controller and Truvi is the Host’s Processor for Validation and for providing the Status. Truvi acts as an independent Controller only for the activities identified as such in the roles table in Appendix 2, being the Watchlist, claims handling and recovery under the Host Protection terms. The Distribution Partner acts as the Host’s Processor when it transmits Shared Personal Data to Truvi; Truvi is not the Distribution Partner’s Processor or Sub-processor.
3.2 Each Party gives the following commitments:
3.2.1 Truvi will ensure that it is not subject to prohibitions or restrictions which would prevent it from complying with the Data Protection Legislation or this Agreement;
3.2.2 the Host warrants that it has a lawful basis under the Data Protection Legislation to collect the Shared Personal Data and to provide it to Truvi for the purposes in Appendix 2;
3.2.3 before Validation is performed, or where the booking channel does not allow this, at the first opportunity and in any event before check-in the Host shall give Guests clear information that their booking details will be shared with Truvi for screening and protection, including Truvi’s identity and the guest privacy information Truvi supplies, and that those Guest details and damage evidence may be shared with Truvi if damage is claimed, in which case Truvi may pursue recovery and may add the Guest to the Watchlist under clause 3.17. Truvi has no direct contact with Guests and relies on the Host to do this; and
3.2.4 the Host shall provide only the Shared Personal Data listed in Appendix 1, and its instructions to Truvi shall comply with the Data Protection Legislation.
3.3 Truvi shall maintain up-to-date records of its processing activities, both as the Host’s Processor and as an independent Controller, as required by the Data Protection Legislation.
3.4 The Parties acknowledge and agree that Appendix 2 (Data Protection Particulars) is an accurate description of the Data Protection Particulars.
3.5 Truvi shall not retain Shared Personal Data for longer than the retention periods set out in Appendix 2.
3.6 Truvi may retain Shared Personal Data for longer than those periods only where a longer period is required by law.
3.7 Truvi shall implement and maintain appropriate technical and organisational measures to meet the Security Requirements and to protect the Shared Personal Data against unauthorised or unlawful Processing and against accidental loss, destruction, damage, alteration or disclosure. These include, at a minimum, the measures in Appendix 4, and:
3.7.1 the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services;
3.7.2 the ability to restore the availability of and access to Shared Personal Data in a timely manner in the event of a physical or technical incident;
3.7.3 pseudonymisation and encryption of Shared Personal Data where appropriate; and
3.7.4 a process for regularly testing, assessing and evaluating the effectiveness of those measures.
Truvi may update Appendix 4, provided the overall level of protection is not materially reduced.
3.8 Within 30 days of the Host ceasing to use the Truvi Services, or of the Host’s reasonable request, Truvi shall, at the Host’s choice, return or delete the Shared Personal Data it holds as the Host’s Processor. Truvi may keep Shared Personal Data after that only where required by law, for an open protection payment request or recovery action, or as a Watchlist entry under clause 3.17. In those cases Truvi holds the data as an independent Controller, keeps only what it needs for that purpose, and deletes it at the end of the relevant period in Appendix 2.
3.9 Following deletion under clause 3.8, Truvi shall on request confirm in writing that the Shared Personal Data has been deleted, including any copies held by Sub-processors.
3.10 Truvi shall notify the Host without undue delay, and in any event within 48 hours after becoming aware of a Personal Data Breach affecting Shared Personal Data processed for the Host. The notice shall include, as far as known: what happened; the categories and approximate number of Data Subjects and records affected; the likely consequences; the measures taken or proposed; and a contact for further information. Truvi may provide information in stages. Truvi shall also:
3.10.1 take reasonable steps to contain the breach and reduce its effects; and
3.10.2 assist the Host to make any notifications to supervisory authorities and affected Data Subjects, including any information needed under US state breach notification laws.
For a Personal Data Breach affecting data Truvi holds as an independent Controller, Truvi is responsible for notifying supervisory authorities and Data Subjects, and will tell the Host where its Guests are affected.
3.11 Truvi shall ensure that only those Personnel who need access to the Shared Personal Data are granted it, only for the purposes of this Agreement, and that they have been informed of its confidential nature and have committed themselves to protecting its confidentiality.
3.12 Truvi shall take reasonable steps to ensure the reliability of its Personnel with access to Shared Personal Data, and that each of them has:
3.12.1 undergone, and continues to receive annually, training in the Data Protection Legislation and the handling of Personal Data; and
3.12.2 entered into binding confidentiality undertakings.
Truvi shall require each Sub-processor to impose materially similar obligations on its own personnel.
3.13 Each Party shall notify the other within five (5) Business Days of receiving any Data Subject Request, or correspondence with a supervisory authority, that relates to the other Party’s Processing of Shared Personal Data, including requests for access or deletion and objections to a Watchlist entry. Each Party shall maintain a process for Data Subjects to complain about its Processing and shall assist the other with complaints. Requests and complaints about the activities for which Truvi is an independent Controller are handled by Truvi directly and may be sent to [email protected]
3.14 Where Truvi Processes Shared Personal Data as the Host’s Processor, Truvi shall, in addition to its obligations in clauses 3.3 to 3.13:
3.14.1 Process it only on the Host’s documented instructions, including with regard to Restricted Transfers, unless required to do otherwise by law (in which case Truvi shall inform the Host first, unless the law prohibits this). This Agreement, the Host Protection terms and the Host’s use of the Truvi Services constitute the Host’s complete instructions at acceptance;
3.14.2 unless prohibited by law, notify the Host without undue delay if it considers that an instruction infringes the Data Protection Legislation;
3.14.3 engage Sub-processors only in accordance with clause 3.15.1;
3.14.4 where Truvi acts as the Host’s Processor, provide reasonable assistance to the Host, within the time limits set by law, to respond to Data Subject Requests, and not respond to a Data Subject Request directly unless the Host authorises it or the law requires it;
3.14.5 assist the Host to meet its obligations on security, Personal Data Breach notification, data protection impact assessments and prior consultation with supervisory authorities (Articles 32 to 36 of the UK GDPR and EU GDPR), including by providing a summary of Truvi’s own assessment of the Truvi Services;
3.14.6 make available to the Host the information reasonably necessary to demonstrate Truvi’s compliance with this clause 3.14 and Article 28 of the UK GDPR and EU GDPR.
3.14.7 not use Shared Personal Data for advertising, product development, analytics, general service improvement, model training or to build or enrich any database other than the Watchlist under clause 3.17, save that Truvi may: (a) use data that has been irreversibly anonymised or aggregated so that no Data Subject is identifiable, including for pricing and loss analysis; (b) Process Shared Personal Data as reasonably necessary to provide, secure, maintain or fix the Truvi Services; (c) Process it as reasonably necessary to prevent, detect or investigate suspected fraud connected with the Truvi Services or a claim; and (d) Process it as required by law or to establish, exercise or defend legal claims.
3.15 The Parties acknowledge that for the purposes of this clause, “onward disclosure” means any sharing of Shared Personal Data by Truvi with a third party, whether a Sub-processor or a third-party Controller or Processor of the Host.
3.15.1 The Host gives Truvi general authorisation to engage Sub-processors. The sub-processors currently engaged by Truvi are listed in Appendix 3. Truvi shall give at least 30 days’ notice before adding or replacing a Sub-processor, by updating the list and notifying Hosts through the Distribution Partner. The Host may object on reasonable data protection grounds within that period; if the objection cannot be resolved, the Host may stop using the Truvi Services for future Bookings. Truvi shall impose on each Sub-processor, by written contract, the same data protection obligations as those in this Agreement, and remains fully liable to the Host for each Sub-processor’s performance.
3.15.2 Truvi may correct, minimise and pseudonymise Shared Personal Data, add Validation results to it, and delete it in accordance with this Agreement. Truvi shall not sell Shared Personal Data or disclose it to any third party except to Sub-processors under clause 3.15.1, to the third-party Controllers listed in Appendix 3 (such as payment providers), to supervisory authorities, courts and law enforcement where required by law, to professional advisers bound by confidentiality, and to recovery agents in connection with a claim.
3.15.3 Truvi shall make a Restricted Transfer only where permitted by the Data Protection Legislation (including where an applicable adequacy decision or regulations, appropriate safeguards or another lawful basis is in place), and the Host authorises Restricted Transfers made on that basis. If the Data Protection Legislation requires the Parties to put a transfer mechanism in place for Shared Personal Data to be transferred to Truvi, they shall promptly enter into it, and Truvi will provide the standard form.
3.16 Where Truvi acts as an independent Controller under clause 3.1:
3.16.1 Truvi decides the purposes and means of that Processing and is responsible for its own compliance with the Data Protection Legislation;
3.16.2 Truvi relies on its legitimate interests in protecting Hosts and their properties, preventing fraud and managing the financial risk of providing protection, and has carried out a legitimate interests assessment;
3.16.3 Truvi shall publish a privacy notice covering that Processing and shall supply short guest privacy information for the Host to provide to Guests under clause 3.2.3; and
3.16.4 clauses 3.14 and 3.15.1 do not apply to that Processing.
3.17 Watchlist:
3.17.1 During Validation, Truvi checks the Guest’s identifiers against the Watchlist. A match means Truvi will not provide protection for that Booking and the Status will be Rejected.
3.17.2 Truvi shall not add a Guest to the Watchlist as a result of routine Validation or an ordinary claim.
3.17.3 Truvi may add a Guest to the Watchlist only following a substantiated incident of significant property damage during a Booking, supported by evidence, and only where Truvi and the affected Host agree in writing that the addition is appropriate. The Host’s agreement confirms the facts of the incident; the decision to add the Guest is Truvi’s.
3.17.4 The Watchlist is internal to Truvi and is not shared with Hosts, the Distribution Partner or anyone else. Hosts receive only the Status.
3.17.5 A Guest may ask Truvi to review a Watchlist entry and may challenge it with appropriate evidence. A person at Truvi shall review each challenge and respond within one month. Entries are reviewed at least every 12 months and removed at the end of the period in Appendix 2 unless a further substantiated incident occurs.
3.17.6 Within one month of adding a Guest to the Watchlist, Truvi shall notify the Guest, using the contact details it holds, of the entry, the reason for it, how long it will be kept and how to ask for a review or object.
3.18 Status and decisions about Guests:
3.18.1 The Status is information to help the Host decide whether to accept a Booking. The Host makes that decision, not Truvi.
3.18.2 The Status is final only for deciding whether Truvi will offer its protection service and permit the Host to request a protection payment in respect of the Booking under the Host Protection terms. A Rejected Status means no protection service is offered by Truvi; it does not require the Host to refuse or cancel the Booking.
3.18.3 When telling a Guest about a decision on their Booking, the Host shall describe it accurately as the Host’s own decision, informed by Validation.
3.18.4 If the Host declines or cancels a Booking because of a Flagged or Rejected Status, the Host shall give the Guest a way to ask for that decision to be reconsidered by a person. Truvi shall help by explaining the Status to the Host on request and by reviewing any Guest challenge under clause 3.17.5.
4. INDEMNIFICATION AND LIABILITY
4.1 Each Party is liable for damage caused by its own breach of this Agreement or of the Data Protection Legislation.
4.2 If a Party is required by a court or supervisory authority (or agrees, with the other Party’s prior written consent) to pay compensation to a Data Subject for damage caused partly by Processing for which the other Party is responsible, the other Party shall reimburse the share of that compensation that reflects its responsibility.
4.3 Each Party’s aggregate liability under or in connection with this Agreement is subject to the limits and exclusions on liability in the Host Protection terms, which apply to this Agreement as if set out in it.
4.4 Nothing in this Agreement limits or excludes liability that cannot be limited or excluded by law.
5. GOVERNING LAW AND JURISDICTION
5.1 This Agreement and any dispute or claim arising out of or in connection with it or its subject matter or formation (including non-contractual disputes or claims) is governed by English law, and the Parties irrevocably submit to the exclusive jurisdiction of the English courts.
5.2 Nothing in this clause affects a Data Subject’s right to bring a complaint or claim under the Data Protection Legislation.
5.3 If this Agreement conflicts with the Host Protection terms or any other agreement between the Parties on the Processing of Shared Personal Data, this Agreement prevails. If Appendix 5 or Appendix 6 conflicts with the main body of this Agreement, that Appendix prevails for the Processing it covers.
5.4 The Host may not transfer this Agreement without Truvi’s consent. If any provision is unenforceable, the rest of this Agreement continues. No third party may enforce this Agreement. Data protection notices to Truvi go to [email protected]
APPENDIX 1: DATA PROCESSED
What types of Personal Data does Truvi process?
The Host, through the Distribution Partner, provides Truvi with the Personal Data below so that Truvi can provide the Truvi Services. Truvi also generates Validation results, and receives claims data from the Host when a claim is made.
| Category of Personal Data | Types of Personal Data | Source |
|---|---|---|
| Guest details | Lead Guest’s first name, last name, email address and phone number | Host, via the Distribution Partner |
| Guest booking details | Booking reference, check-in and check-out dates, booking channel | Host, via the Distribution Partner |
| Property booking details | Property location and any conditions of use | Host, via the Distribution Partner |
| Host details (where the Host is an individual) | Name, business name, contact details, payment details for protection payments | Host, via the Distribution Partner |
| Validation results | Verification results, risk indicators and the Status | Generated by Truvi and its Sub-processors |
| Claims data | Claim details, damage evidence (photos, invoices), amounts claimed and paid correspondence, where this data contains Guest personal details | Host |
Truvi does not process special category data, criminal offence data, sensitive personal information or data about children.
APPENDIX 2: DATA PROTECTION PARTICULARS
What does Truvi do with the Personal Data and in what role?
| Activity | Personal Data | Host’s role | Truvi’s role |
|---|---|---|---|
| Validation and providing the Status | Guest, Guest booking and Property booking details; Validation results | Controller | Processor |
| Activity | Personal Data | Host’s role | Truvi’s role |
| Watchlist check during Validation | Guest details | Controller | Independent Controller for deciding whether to provide the protection service (the Host receives only the resulting Status) |
| Adding a Guest to the Watchlist (clause 3.17) | Guest details; Claims data | Controller | Independent Controller |
| Handling claims and deciding protection payments | Claims data; Host details | Controller of its own claim | Independent Controller |
| Particular | Description |
|---|---|
| Subject matter | Screening of short-term rental Bookings and assessing eligibility for property damage protection and considering protection payment requests from the Host |
| Nature and purpose | Verifying the lead Guest’s name, phone and email; checking the Watchlist; providing the Status; handling protection payment requests and recovery under the Host Protection terms |
| Duration | From each Booking’s submission until the end of the retention periods below |
| Type of Personal Data | As set out in Appendix 1 |
| Categories of Data Subjects | Lead Guests on Bookings; Hosts who are individuals; Host staff contacts |
How long does Truvi keep it?
| Data | Retention period |
|---|---|
| Validation data, Approved or Flagged Booking with no claim | 7 years after check-out |
| Validation data, Rejected or cancelled Booking | 7 years after the Status is given |
| Claims and recovery files | 6 years after the claim closes |
| Watchlist entries | 5 years from addition, reviewed every 12months |
| Data | Retention period |
| Financial and accounting records for protection payments | As required by law 6 years plus the current tax year under UK law |
APPENDIX 3: SUB-PROCESSORS AND THIRD-PARTY CONTROLLERS
| Name | Role | Service | Data | Location of processing and access |
|---|---|---|---|---|
| SEON | Sub-processor | Email, phone and fraud signal checks | Guest details | EU |
| Microsoft Azure | Sub-processor | Cloud hosting | All Shared Personal Data | Ireland (EEA) |
| Airwallex | Third-party Controller | Protection payments | Host details | EU, USA, Singapore, Hong Kong |
APPENDIX 4: SECURITY MEASURES
- Encryption of Shared Personal Data in transit (TLS 1.2 or higher) and at rest (AES-256 or equivalent).
- Role-based access on a need-to-know basis, with multi-factor authentication for all staff and administrative access.
- Logging and monitoring of access to Shared Personal Data.
- Pseudonymisation or minimisation where it does not affect the Truvi Services.
- Regular backups, tested restoration, and documented incident response and business continuity plans.
- Annual penetration testing and regular vulnerability scanning, with findings fixed according to risk.
- Secure deletion at the end of each retention period.
- Security and data protection checks on Sub-processors before appointment and periodically after.
- Staff confidentiality agreements and annual data protection training.
APPENDIX 5: UK AND EU/EEA TERMS
This Appendix applies where the Host, or its Processing of Shared Personal Data, is subject to the UK GDPR or the EU GDPR.
- Article 28. This Agreement, with Appendices 1 and 2, is intended to meet Article 28(3) of the UK GDPR and EU GDPR.
- Automated decisions. Truvi does not make decisions about Guests based solely on automated processing that have legal or similarly significant effects; the Host decides whether to accept a Booking (clause 3.18). Truvi will support the Host in providing the safeguards in Articles 22A to 22D UK GDPR or Article 22 EU GDPR if they apply to the Host’s decision, including human review of a Status on request.
- Criminal offence data. The Watchlist records evidence of property damage and unpaid liability. It does not record allegations or findings of criminal offences.
- Complaints. Under clause 3.13, each Party will acknowledge complaints within 30 days and respond without undue delay, as required by the Data (Use and Access) Act 2025.
- Supervisory authority. For the UK, the Information Commissioner’s Office. For the EU/EEA, the authority competent for the Host.
APPENDIX 6: US TERMS
This Appendix applies to the extent the CCPA or any other US State Privacy Law applies to the Host’s Processing of Shared Personal Data. To the extent a US State Privacy Law requires the contract to include terms not set out in this Agreement, those terms are incorporated by reference and the Parties shall agree in good faith any further amendment required.
- Roles. Where Truvi Processes Shared Personal Data as the Host’s Processor, Truvi is the Host’s “service provider” under the CCPA and “processor” under other US State Privacy Laws.
- CCPA service provider terms. For Shared Personal Data that is personal information under the CCPA, Truvi shall: (a) Process it only for the limited and specified business purposes of guest screening and property damage protection described in Appendix 2; (b) not sell or share it (as defined in the CCPA); (c) not retain, use or disclose it for any other purpose, or outside the direct business relationship with the Host, except as permitted by the CCPA and its regulations (including for security, fraud prevention and legal compliance); (d) not combine it with personal information from other sources, except as permitted by the CCPA regulations; (e) comply with the CCPA and provide the same level of privacy protection as the CCPA requires of the Host; (f) notify the Host if it can no longer meet its CCPA obligations; and (g) allow the Host, on notice, to take reasonable steps to stop and remediate any unauthorised use and to check that Truvi’s use is consistent with the Host’s CCPA obligations. Truvi certifies that it understands and will comply with these restrictions.
- Other states. Clauses 3, 3.14.6 and 3.15.1 provide the processor contract terms required by other US State Privacy Laws, including instructions, confidentiality, deletion or return, making information available, assessments, and flow-down to Sub-processors with notice and a right to object.
- Deidentified data. Where Truvi uses deidentified data under clause 3.14.7(a), it will take reasonable measures to ensure the data cannot be linked to an individual, publicly commit to keeping it deidentified, and not attempt to re-identify it.
- Health data. Truvi does not request, and the Host shall not provide, consumer health data, including data covered by Washington’s My Health My Data Act.
- Consumer requests. Clauses 3.13 and 3.14.4 apply to requests under the US State Privacy Laws, including requests to know, delete, correct and opt out.