Legal

Data Processing Agreement

SyRev: CERTAVI TECHNOLOGIES - FZCO

Published: 27 October 2026

This Data Processing Agreement ("DPA") forms part of the agreement for SyRev services (the "Agreement"). The Agreement consists of the SyRev Terms of Service (https://syrev.ai/legal/terms) and any Order Form. Where Customer uses SyRev for an organisation, the Terms of Service incorporate this DPA without a separate signature (Terms s.13), whatever the plan. The parties are:

SyRev privacy contact: privacy@syrev.ai. Security and breach contact: security@syrev.ai.

1. Definitions

1.1 "Data Protection Laws" means all laws that apply to the processing of Personal Data under the Agreement, including, where applicable:

1.2 "Personal Data", "Processing", "Controller", "Processor", "Data Subject" and "Personal Data Breach" have the meanings given in the applicable Data Protection Laws.

1.3 "Customer Data" means the data Customer or its users submit to the SyRev service, including:

"Customer Personal Data" means the Personal Data in Customer Data.

1.4 "Subprocessor" means a third party engaged by SyRev to process Customer Personal Data.

1.5 "SCCs" means the standard contractual clauses approved by European Commission Implementing Decision (EU) 2021/914 of 4 June 2021. "UK Addendum" means the International Data Transfer Addendum to the EU SCCs issued by the UK Information Commissioner under s.119A of the Data Protection Act 2018.

2. Roles and scope

2.1 Customer is the Controller, and SyRev is the Processor, of the Customer Personal Data processed to provide the service. Annex I describes the processing.

2.2 SyRev acts as an independent controller only for:

2.3 De-identified screening metrics. SyRev collects de-identified screening metrics from Customer's organisation workspace only if Customer's workspace admin turns this on in the workspace admin settings.

What the metrics are:

How they are stored and used:

3. Processor obligations

SyRev will:

3.1 process Customer Personal Data only on Customer's documented instructions, including those in the Agreement and given through Customer's use of the service, and tell Customer if it believes an instruction breaks Data Protection Laws;

3.2 make sure everyone authorised to process Customer Personal Data is bound by confidentiality;

3.3 implement the technical and organisational measures in Annex II;

3.4 taking into account the nature of the processing, help Customer respond to Data Subject requests (access, rectification, erasure, restriction, portability, objection). Users can delete reviews and accounts themselves in the service (Annex II, item 8). SyRev fulfils other requests within 30 days;

3.5 help Customer, as reasonably required, with security, breach notification, data protection impact assessments and prior consultations;

3.6 not use Customer Data to train machine-learning models; and

3.7 not sell Customer Personal Data.

4. Subprocessors

4.1 Customer gives general authorisation for SyRev to engage the Subprocessors listed in Annex III.

4.2 SyRev will give Customer at least 15 days' notice before adding or replacing a Subprocessor that processes Customer Personal Data, or before re-enabling the backup AI provider listed in Annex III as disabled. The notice will be given by updating https://syrev.ai/legal/subprocessors and by emailing the owner of Customer's Workspace.

4.3 SyRev will impose data protection terms on each Subprocessor that are no less protective than this DPA, to the extent they apply to the services that Subprocessor provides. SyRev remains responsible to Customer for its Subprocessors' performance.

5. International transfers

5.1 Customer Personal Data is processed in the locations listed in Annex III.

5.2 Where Personal Data is transferred under this DPA from the EEA, Switzerland or the UK to a country without an adequacy decision, the parties agree that the SCCs apply. They are set out in Annex IV and incorporated by reference, as follows:

For UK transfers, the UK Addendum in Annex V applies to the same first transfer (Customer as exporter, CERTAVI TECHNOLOGIES - FZCO in the UAE as importer) and to onward transfers on the same basis.

For Swiss transfers, the SCCs apply with the adaptations required by the Swiss FADP.

5.3 For transfers out of the UAE, SyRev will comply with the cross-border transfer provisions of the UAE PDPL and its implementing regulations, relying on adequacy, contractual safeguards or another legal basis they permit.

6. Security and Personal Data Breaches

6.1 SyRev will maintain the measures in Annex II. It may update them, provided the overall level of protection does not decrease.

6.2 SyRev will notify Customer without undue delay, and in any event within 72 hours, after becoming aware of a Personal Data Breach affecting Customer Personal Data. The notice will be sent by email to the owner and admins of Customer's Workspace. It will give the information reasonably available about:

6.3 Where not all of the information is available at once, SyRev will provide it in stages without further undue delay. SyRev's notice is not an admission of fault or liability.

7. Audits

SyRev will make available the information reasonably necessary to show compliance with this DPA. This includes completed security questionnaires and, where relevant, its Subprocessors' third-party reports, subject to their terms. SyRev does not currently hold its own SOC 2 or ISO 27001 certification.

Customer may carry out an audit:

Customer may also audit where required by a supervisory authority or after a Personal Data Breach.

8. Return and deletion

8.1 During the term, Customer can export its review data from the service (decision logs, RIS, CSV, PRISMA, methods and validation exports).

8.2 After the Agreement ends, Customer has at least 60 days to export its data, as set out in the Terms of Service. SyRev will email the owner of Customer's Workspace at least 30 days before deleting, so no deletion happens until at least 90 days after the Agreement ends. SyRev will then delete Customer Personal Data from the live database and uploaded-file storage no later than 120 days after the Agreement ends, or sooner on Customer's written request, unless law requires SyRev to keep it. SyRev will confirm the deletion in writing on request.

9. Liability and precedence

9.1 Each party's liability under this DPA is subject to the limitations in the Agreement, except where Data Protection Laws or the SCCs require otherwise.

9.2 If this DPA conflicts with the Agreement, this DPA prevails for the processing of Personal Data. If this DPA conflicts with the SCCs, the SCCs prevail.

This DPA applies through the Terms of Service without a separate signature. A countersigned copy is available on request from privacy@syrev.ai.


Annex I: Description of processing

ItemDescription
Data subjectsCustomer's authorised users (staff, students, reviewers). Authors named in the bibliographic records and full-text PDFs Customer imports.
Categories of personal dataUsers: name or display name; email address; organisation; role; password hash; session identifiers; two-step sign-in data if used; single sign-on identity links; workspace membership; security audit log entries (including IP address); activity needed to run the service (screening votes, decisions, timestamps). Bibliographic records: titles, abstracts, author names, journal and identifiers (DOI, PMID, PMCID), and full-text PDFs Customer uploads or asks SyRev to fetch from open-access sources. Billing: email and Stripe transaction identifiers. Card data is held only by Stripe.
Special category dataNone intended. The service processes published research literature. Customer should not upload patient-level or other special category data.
Nature and purposeHosting and storing Customer's reviews; deduplication; AI-assisted screening of titles and abstracts against Customer's criteria and, on plans that include it, of full text; AI-assisted data extraction on plans that include it (values are saved only when a person accepts them); risk-of-bias recording; dual human review; exports; single sign-on; transactional email; support.
FrequencyContinuous, for the term of the Agreement.
RetentionFor the term of the Agreement, then deleted under section 8. Published schedule: https://app.syrev.ai/legal/retention

Annex II: Technical and organisational measures

Verified in the SyRev application code (main 6fcf9b3 plus PR #121) and production settings on 2 October 2026.

1. Hosting.

2. Authentication.

3. Single sign-on (where SyRev sets it up for Customer).

4. Access control.

5. Integrity and auditability.

6. Data minimisation for AI.

7. Backups.

8. Deletion.

9. Incident response. Breaches are handled under section 6. Contact: security@syrev.ai.

Annex III: Subprocessors

"Data received" is what the SyRev code sends to each provider.

SubprocessorPurposeData receivedLocationProvider terms
Railway CorporationApplication hosting, database, file storage and backupsAll Customer Data stored in the serviceUnited States (US West)https://railway.com/legal/dpa
AI model provider (primary), United States. Name available on request from privacy@syrev.aiMain AI provider: screening, full-text screening and AI data extractionReview criteria; record titles and abstracts; on plans with full-text screening or AI data extraction, text passages from full-text PDFs (reference list removed, capped as in Annex II) and extraction field instructions. No account data.United StatesProvider terms and DPA: supplied with the name on request from privacy@syrev.ai
AI model provider (backup), United States. Name available on request from privacy@syrev.aiBackup AI provider. Currently disabled; receives no data. SyRev will give notice under section 4.2 before re-enabling it.None while disabled. When enabled: the same fields as the main provider, only for records scored during an outage (never extraction), and criteria text for a criteria check during an outage. No account data.United StatesProvider terms: supplied with the name on request from privacy@syrev.ai (no DPA in place)
StripePayments (hosted Checkout)Billing email, plan and transaction data. Card data is collected by Stripe directly.Available on requesthttps://stripe.com/legal/dpa
ResendTransactional emailRecipient email address and email content (reset links, invitations, notices)Available on requesthttps://resend.com/legal/dpa
Google LLC (Google Workspace)Company email, including support emails from customersContent of emails sent to SyRevAvailable on requesthttps://cloud.google.com/terms/data-processing-addendum
Notion Labs, Inc.Inbox for the feedback form on syrev.ai (only if used)Name, email, message and the page it was sent fromAvailable on requesthttps://www.notion.so/notion/Data-Processing-Addendum-361b540101274b1fa7e16b90402b0d99
Vercel Inc.Hosting of the marketing website syrev.aiStandard web request data for visitors to syrev.ai. No review data.Available on requesthttps://vercel.com/legal/dpa

Public research services (not Subprocessors). When users choose search, open-access lookup or retraction checks, SyRev sends search terms or public article identifiers to NCBI (PubMed E-utilities, PubMed Central), Europe PMC (EMBL-EBI), OpenAlex, Crossref, Unpaywall (with SyRev's contact email) and doi.org. PDFs are then downloaded from the publisher or repository links these services return. No criteria, decisions or user data are sent.


Annex IV: Standard Contractual Clauses (EU)

The SCCs adopted by Commission Implementing Decision (EU) 2021/914 of 4 June 2021 apply to transfers described in section 5.2. Module Two (controller to processor) applies between Customer (and any EU/EEA or Swiss controller using Customer's Workspace), as data exporter, and CERTAVI TECHNOLOGIES - FZCO, in the UAE, as data importer. Module Three (processor to processor) applies to SyRev's onward transfers to Subprocessors (section 5.2).

The full official English text of the Annex to Commission Implementing Decision (EU) 2021/914 (the standard contractual clauses) is set out at https://syrev.ai/legal/scc. It is unchanged. Modules Two and Three are the modules that apply. The selections are below, and are not written into that text.

Selections:

Annex V: UK International Data Transfer Addendum

The UK Addendum (version B1.0, issued by the UK Information Commissioner and in force from 21 March 2022) applies to transfers from the UK. It is completed as follows:

The full official text, version B1.0, is set out at https://syrev.ai/legal/uk-addendum. The official PDF is https://syrev.ai/legal/uk-idta-addendum-b1.0.pdf. It is unchanged.