Skip to content

Data Processing Agreement

The EvenTier DPA: a Common Paper DPA Cover Page for the cloud service. It covers Article 28 processor terms, Standard Contractual Clauses for EEA and UK transfers, and the named subprocessor list.

Effective October 10, 2026 · Version 2026-10-10

01

How this DPA works

This Data Processing Agreement (DPA) has two parts: the Key Terms on this Cover Page, and the Common Paper DPA Standard Terms Version 1.1 (the DPA Standard Terms), which are incorporated by reference. If the two parts conflict, this Cover Page controls. Capitalized words have the meanings given on this Cover Page, in the DPA Standard Terms, or in the Agreement.
Customer accepts this DPA electronically, together with the Customer Agreement, when its workspace or self-hosted account is created, or before it first pays for Standard if Provider set the workspace up. Each acceptance is recorded with the DPA version, the time, and the accepting user. There is nothing further to sign or request: the DPA applies to all Customer Personal Data processed in the Cloud Service.
The DPA Standard Terms are published by Common Paper, Inc. and licensed under CC BY 4.0. This Cover Page follows the Common Paper DPA Cover Page, completed for EvenTier.
02

Key Terms

Agreement

This DPA supplements the EvenTier Customer Agreement between Provider and Customer. Provider is EvenTier (legal entity name pending confirmation), and Customer is the organization that accepted it.

Approved Subprocessors

The list at /legal/subprocessors, with each subprocessor’s country of location and processing task. Provider gives written notice of a change at least 10 business days in advance by email to Customer’s workspace administrators, or to the owner of its self-hosted account.

Provider Security Contact

security@eventier.io

Postal address: Pending confirmation

Security Policy

As defined in the Agreement.

Changes to the Agreement

None. Claims under this DPA use the liability caps, Governing Law and Chosen Courts of the Agreement.

Service Provider Relationship

To the extent the California Consumer Privacy Act, Cal. Civ. Code § 1798.100 et seq. (CCPA) applies, the parties acknowledge and agree that Provider is a service provider and is receiving Personal Data from Customer to provide the Service as agreed in the Agreement and detailed below (see Nature and Purpose of Processing), which constitutes a limited and specified business purpose. Provider will not sell or share any Personal Data provided by Customer under the Agreement. In addition, Provider will not retain, use, or disclose any Personal Data provided by Customer under the Agreement except as necessary for providing the Service for Customer, as stated in the Agreement, or as permitted by Applicable Data Protection Laws. Provider certifies that it understands the restrictions of this paragraph and will comply with all Applicable Data Protection Laws. Provider will notify Customer if it can no longer meet its obligations under the CCPA.

03

Restricted Transfers

Governing Member State

EEA Transfers: Ireland.

UK Transfers: the laws of England and Wales.

Where a Restricted Transfer takes place, the parties are deemed to have entered into the EEA SCCs (Module Two, or Module Three where Customer is itself a processor) or the UK Addendum as the DPA Standard Terms describe, and this Cover Page supplies their Annexes.

04

Annex I(A): List of Parties

Data Exporter

Name: Customer, the organization that accepted the Agreement.

Address: the address in Customer’s billing details.

Contact person: the workspace administrator who accepted this DPA, at the email address of their EvenTier account.

Activities relevant to transfer: see Annex I(B).

Role: Controller, or Processor where Customer processes the data on behalf of another controller.

Data Importer

Name: Pending confirmation

Address: Pending confirmation

Contact person: Privacy contact, hello@eventier.io

Activities relevant to transfer: see Annex I(B).

Role: Processor.

05

Annex I(B): Processing Activities

Service

The EvenTier Cloud Service described in the Agreement.

Categories of Data Subjects

Customer’s employees, contractors and other Users (agents, approvers and requesters), and individuals named or described in requests, comments, attachments and knowledge articles.

Categories of Personal Data

Names; contact information such as email address and phone number; employment information such as job title, department, manager and location; account data such as hashed passwords, MFA enrollment and single sign-on identifiers; user activity such as sign-in times, IP addresses, browser details and audit records; and any personal data Users include in requests, comments, form responses, attachments and knowledge articles.

Special Category Data

No. The Standard Terms of the Agreement treat special category data as Prohibited Data, which Customer does not submit to the Cloud Service.

Frequency of Transfer

Continuous, for as long as Customer uses the Cloud Service.

Nature and Purpose of Processing

Provider will Process Customer Personal Data as instructed in the Processing Instructions of the DPA Standard Terms. The nature of processing includes:

  • Receiving data through the portal, forms, the API, integrations and imports
  • Holding data, including storage, organization and structuring
  • Using data for search, routing, reporting and, when AI features are used, AI-generated summaries and suggestions
  • Updating data as Users edit it
  • Protecting data, including restricting access, encrypting and security testing
  • Sharing data with Customer’s Users, with integrations Customer enables, and with Approved Subprocessors
  • Returning data through exports
  • Erasing data on instruction and at the end of the Agreement
Duration of Processing

Provider will process Customer Personal Data as long as required (i) to conduct the Processing activities instructed in the DPA Standard Terms; or (ii) by Applicable Laws.

06

Annex I(C): Supervisory Authority

The supervisory authority will be the supervisory authority of the data exporter, as determined in accordance with Clause 13 of the EEA SCCs or the relevant provision of the UK Addendum.

07

Annex II: Security Measures

See Security Policy. The controls in place are described at /trust and include:
Identification and authorization

Password sign-in under an organization password policy, SAML and OIDC single sign-on, multi-factor authentication, re-authentication for sensitive actions, sign-in network restrictions, roles built from individual permissions, team scoping for agents, and confidential requests limited to the team handling them and the people named on them.

In transit

TLS on every connection to the Cloud Service.

At rest

Single sign-on credentials, integration tokens, license keys and MFA secrets are encrypted by the application; passwords and recovery codes are stored only as hashes. Uploaded files are scanned for malware before they are stored.

Isolation

Application queries are scoped to Customer’s organization.

Events logging

Separate logs for changes, sign-ins and security events, exportable or streamable to Customer’s SIEM. The change log is kept 7 days on Free and 30 days on Standard, longer with an audit-retention add-on; sign-in and security logs are kept 400 days.

Availability and restore

A managed PostgreSQL database with point-in-time recovery, keeping backups for 7 days.

Testing

Automated type checks, lint and test suites on every pull request, and a vulnerability scan of each release image before it is published.

Data minimization

Product usage analytics never include request content, comments or attachments, and a workspace administrator can turn them off.

Portability and erasure

A workspace export of records and stored files, a per-person access export, and a per-person erasure that keeps a proof record instead of the identity.

Certification

Provider holds no third-party security certification or audit report yet.

08

Changes to the DPA Standard Terms

Security Reports

Provider is not yet audited against a third-party standard, so the Security Reports provision of the DPA Standard Terms applies only once Provider has a Report. Until then, Customer exercises its audit rights through written Security Due Diligence requests to the Provider Security Contact.

Security Incident notices

Provider sends the notice the DPA Standard Terms require (no later than 72 hours after becoming aware of a Security Incident) by email to Customer’s workspace administrators, or to the owner of its self-hosted account.

Deletion and return

A workspace administrator can download an export of the workspace before scheduling its deletion. When a workspace administrator schedules deletion, Provider permanently deletes the workspace’s Customer Personal Data and stored files 30 days later; until then Provider can restore the workspace on request. Database backups age out within 7 days after deletion.

Provider and Customer have not changed the DPA Standard Terms except for the details on this Cover Page.

Questions about this document?

Legal notices, contract questions and privacy requests go to hello@eventier.io, and vulnerability reports to security@eventier.io.