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:
- Customer: the customer named in the account or Order Form ("Customer"); and
- CERTAVI TECHNOLOGIES - FZCO (trading as SyRev), a free zone company licensed in the International Free Zone Authority (IFZA) free zone, Dubai (IFZA licence no. 87593), of DSO-IFZA, IFZA Properties, Dubai Silicon Oasis, Dubai, United Arab Emirates ("SyRev").
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:
- (a) Regulation (EU) 2016/679 (the "EU GDPR");
- (b) the EU GDPR as it forms part of UK law (the "UK GDPR") and the UK Data Protection Act 2018;
- (c) UAE Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data (the "UAE PDPL") and its implementing regulations; and
- (d) any other law that applies to Customer and is notified to SyRev in writing.
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:
- reference records (titles, abstracts, author lists, identifiers);
- eligibility criteria, screening decisions and notes;
- full-text PDFs, data extraction and risk-of-bias entries;
- account and workspace information.
"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:
- (a) account and billing administration;
- (b) security and fraud prevention; and
- (c) de-identified screening metrics, where clause 2.3 allows them.
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.
- It is off by default, and the admin can turn it off at any time.
- While it is off, no metrics are used from any review in the workspace, whatever an individual member's own setting.
- Only screening runs recorded after the admin turns it on are used, and never records made before 28 September 2026.
What the metrics are:
- Counts and rates about a completed screening run, for example: the number of records imported, screened and auto-excluded; how often reviewers agreed with or overrode the AI suggestion; recall against labelled records where the reviewer supplied labels; score summaries per criterion (with the criteria replaced by neutral labels); thresholds used; run time; software and model version; and the month of completion.
- They contain no record content (titles, abstracts, authors, PDFs), no criteria text and no review names.
How they are stored and used:
- The stored metrics are linked to the review they came from, not to a person, and are deleted when the review is deleted.
- The export SyRev uses for validation carries no account, user, email, review or workspace identifier.
- SyRev uses the metrics only for its own product validation and improvement.
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.
- The notice will name the Subprocessor, its purpose, the data it will receive and where it will process that data.
- Customer may object on reasonable data protection grounds within the 15-day period, by email to privacy@syrev.ai.
- Customer may object on reasonable data protection grounds.
- If the parties cannot resolve the objection, Customer may terminate the affected service and receive a pro-rata refund of prepaid fees for the unused period.
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:
- First transfer, to SyRev in the UAE. Module Two (controller to processor) applies. Customer, and any EU/EEA or Swiss controller that uses Customer's Workspace, is the data exporter. CERTAVI TECHNOLOGIES - FZCO, established in the UAE (which has no EU adequacy decision), is the data importer. This covers all Customer Personal Data that SyRev receives, wherever it is then hosted.
- Onward transfers. SyRev's onward transfers to Subprocessors in countries without an adequacy decision, including the main AI scoring provider and the hosting provider in the United States (Annex III), are made under Module Three (processor to processor) SCCs between SyRev, as exporter, and each Subprocessor, as importer. Alternatively, where the Subprocessor offers it, an equivalent safeguard (for example certification under the EU-US Data Privacy Framework) is used. Clause 8.8 of Module Two applies to these onward transfers;
- Clause 7 (docking clause) applies;
- Clause 9(a): Option 2 (general authorisation), with the notice period in section 4.2;
- Clause 11: the optional redress language does not apply;
- Clauses 17 and 18: the law and courts of Ireland;
- Annexes I to III of the SCCs are completed by Annexes I to III of this DPA.
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:
- the nature of the breach;
- the categories and approximate numbers of Data Subjects and records;
- the likely consequences; and
- the measures taken or proposed; and
- a contact point for more information.
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:
- at its own cost, no more than once a year;
- on at least 30 days' notice, during business hours; and
- subject to confidentiality.
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.
- Copies in backups are deleted as the backups expire. Daily backups are kept as 7 daily and 4 weekly sets, so data leaves them within about 5 weeks. One-off database copies taken before software updates are deleted automatically once they are more than 30 days old.
- Backups are not restored except for disaster recovery.
- Deletion in SyRev does not reach copies held by an AI provider under its own terms (Annex III).
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
| Item | Description |
|---|---|
| Data subjects | Customer's authorised users (staff, students, reviewers). Authors named in the bibliographic records and full-text PDFs Customer imports. |
| Categories of personal data | Users: 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 data | None intended. The service processes published research literature. Customer should not upload patient-level or other special category data. |
| Nature and purpose | Hosting 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. |
| Frequency | Continuous, for the term of the Agreement. |
| Retention | For 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.
- The application, database and uploaded files run on Railway, in Railway's US West region.
- Traffic to app.syrev.ai uses HTTPS, with HSTS (max-age one year, including subdomains).
2. Authentication.
- Passwords are hashed with bcrypt.
- Server-side sessions use a 256-bit random identifier in a Secure, HttpOnly cookie and expire after 14 days. Signing out deletes the session.
- Password-reset tokens are stored hashed (SHA-256) and expire after 1 hour. Completing a reset revokes all of the user's sessions.
- Sign-in and reset attempts are rate limited. Attempt counters are stored only in hashed form and deleted after 24 hours.
- Two-step sign-in is available.
3. Single sign-on (where SyRev sets it up for Customer).
- OpenID Connect (authorization code with PKCE, state and nonce; ID-token signatures verified against the provider's keys) or SAML 2.0.
- Only verified domains can use single sign-on.
- Identity-provider secrets are encrypted with AES-256-GCM using a server-held key.
4. Access control.
- Review access is limited to the owner and authorised workspace members, with owner, admin and member roles.
- Requests that change data are rejected when they come from other websites (Origin check).
- SyRev's internal admin dashboard is limited to an allowlist of SyRev operator accounts.
5. Integrity and auditability.
- A per-review decision log records AI and human decisions.
- Dual review is blinded.
- A security audit log records sign-ins and failed sign-ins, sign-outs, two-step sign-in changes, workspace membership and role changes, review transfers, exports and deletions. It is kept for 400 days, and workspace owners and admins can see their workspace's events.
6. Data minimisation for AI.
- Main AI model provider (primary), United States; name available on request from privacy@syrev.ai. Requests contain:
- the review's criteria and each record's title and abstract;
- on plans with full-text screening, text passages from the full-text PDF (reference list removed; split into parts of up to 64,000 characters; capped at five parts, about 100 pages, with the cap shown to the user);
- for AI data extraction, passages from the PDF and the extraction field instructions.
- Requests contain no user account data.
- Backup AI model provider, United States; name available on request from privacy@syrev.ai. Currently disabled (since 2 October 2026). It receives no data. If the main provider is unavailable, screening stops with a "temporarily unavailable" message and nothing is charged. When enabled, the backup was used only for title/abstract screening, full-text screening and criteria checks during an outage, never for data extraction. Its scores always went to human review and were re-scored by the main provider.
- No other AI provider is used.
- SyRev does not train models on Customer Data.
7. Backups.
- Automatic daily backup of the database (SQLite online backup, integrity-checked) and uploaded PDFs, kept as 7 daily and 4 weekly sets, with a scripted restore.
- One-off database copies taken before software updates are deleted automatically once they are more than 30 days old.
- Backups are on the same Railway volume as the app.
8. Deletion.
- Users can delete their own reviews (records, decisions, PDFs and results) and their account in the app. Workspace admins can delete a member's data.
- A replaced PDF is removed from storage.
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.
| Subprocessor | Purpose | Data received | Location | Provider terms |
|---|---|---|---|---|
| Railway Corporation | Application hosting, database, file storage and backups | All Customer Data stored in the service | United States (US West) | https://railway.com/legal/dpa |
| AI model provider (primary), United States. Name available on request from privacy@syrev.ai | Main AI provider: screening, full-text screening and AI data extraction | Review 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 States | Provider 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.ai | Backup 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 States | Provider terms: supplied with the name on request from privacy@syrev.ai (no DPA in place) |
| Stripe | Payments (hosted Checkout) | Billing email, plan and transaction data. Card data is collected by Stripe directly. | Available on request | https://stripe.com/legal/dpa |
| Resend | Transactional email | Recipient email address and email content (reset links, invitations, notices) | Available on request | https://resend.com/legal/dpa |
| Google LLC (Google Workspace) | Company email, including support emails from customers | Content of emails sent to SyRev | Available on request | https://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 from | Available on request | https://www.notion.so/notion/Data-Processing-Addendum-361b540101274b1fa7e16b90402b0d99 |
| Vercel Inc. | Hosting of the marketing website syrev.ai | Standard web request data for visitors to syrev.ai. No review data. | Available on request | https://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:
- Clause 7 (docking clause): applies.
- Clause 9(a): Option 2, general written authorisation, with 15 days' notice (section 4.2).
- Clause 11(a): optional language does not apply.
- Clause 13: the supervisory authority is the authority of the Customer's EU Member State (or Irish DPC where none).
- Clauses 17 and 18: the law and courts of Ireland.
- Annex I.A (parties): as set out at the start of this DPA.
- Annex I.B (description of transfer): Annex I of this DPA.
- Annex I.C (competent supervisory authority): as in Clause 13 above.
- Annex II (technical and organisational measures): Annex II of this DPA.
- Annex III (subprocessors): Annex III of this DPA.
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:
- Table 1 (parties): Customer, as exporter, and CERTAVI TECHNOLOGIES - FZCO (UAE), as importer, with the details at the start of this DPA.
- Table 2 (selected SCCs): the Approved EU SCCs, Modules Two and Three, with the selections in Annex IV.
- Table 3 (appendix information): Annexes I to III of this DPA.
- Table 4 (ending the Addendum when it changes): neither party may end the Addendum.
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.