Data Processing Addendum
This Data Processing Addendum describes how WaverSec Protect processes personal data on behalf of customer organizations when WaverSec acts as a processor or service provider.
This DPA applies only where WaverSec processes personal data on behalf of a customer subject to a customer agreement. If a negotiated DPA or enterprise agreement exists, that negotiated document controls.
Search section titles and document text.
Scope and incorporation
This DPA forms part of the customer agreement for WaverSec Protect where WaverSec processes personal data on behalf of the customer in connection with the service.
For customer-controlled message data and related operational records processed on behalf of the customer, the customer acts as controller or business and WaverSec acts as processor or service provider, unless the parties expressly agree otherwise.
Processing instructions
WaverSec will process personal data only on documented instructions from the customer, including instructions reflected in the service configuration, APIs, support requests, and the customer agreement, unless law requires otherwise.
If WaverSec believes an instruction violates applicable data protection law, WaverSec may suspend the relevant processing and notify the customer.
Subject matter, duration, nature, and purpose
The subject matter of processing is delivery of WaverSec Protect, including email anomaly detection, policy enforcement, DLP checks, optional intelligence analysis, product administration, support, and associated security operations.
The duration of processing is the period during which WaverSec provides the service to the customer and any limited post-termination period reasonably required for secure deletion, backup expiry, dispute handling, or legal compliance.
- Nature of processing: collection, organization, analysis, consultation, storage of limited operational records, transmission, and deletion.
- Purpose of processing: provide, secure, support, and improve the contracted service and comply with lawful obligations.
Categories of data subjects and personal data
Depending on the customer deployment, data subjects may include customer employees, contractors, administrators, correspondents, recipients, and other people whose data appears in messages or account records processed through the service.
- Identifiers and contact data such as names, email addresses, and usernames.
- Message data such as sender, recipients, subject, body, and attachment content when submitted for scanning.
- Configuration and policy data supplied by customer administrators, including domains, allow lists, deny lists, segments, and exemptions.
- Operational data such as request IDs, timestamps, usage metrics, and seat identifiers.
Confidentiality and personnel
WaverSec will ensure that people authorized to process personal data are bound by confidentiality obligations and receive appropriate instructions about data handling.
Access to personal data will be limited to people and subprocessors who need that access to provide or secure the service.
Security measures
WaverSec will implement technical and organizational measures appropriate to the risk, taking into account the nature of the service and the current product architecture.
- Access controls for production systems and customer administration flows.
- Transport encryption for supported API communications.
- Logging, validation, and rate-limiting controls designed to protect exposed service endpoints.
- Product design choices intended to minimize retained message data.
- Change management and incident handling practices reasonably appropriate for the service stage and risk profile.
Subprocessors
The customer gives WaverSec general written authorization to use subprocessors that are reasonably necessary to operate the service, including providers for hosting, edge delivery, managed database infrastructure, identity, analytics, support, and optional AI features enabled by the customer.
WaverSec will impose data protection obligations on subprocessors that are materially protective of personal data and will remain responsible for subprocessors to the extent required by law.
Before a new subprocessor or a material replacement subprocessor begins processing customer personal data, WaverSec will provide notice where reasonably practicable. The customer may object on reasonable data protection grounds by written notice within 15 days after that notice. The parties will work in good faith on a reasonable alternative. If no reasonable solution is available, either party may terminate the affected processing or the affected portion of the service on written notice.
- Clerk for identity and authentication.
- Vercel for application hosting and edge delivery.
- Neon for managed database hosting.
- PostHog for optional website and product analytics.
- OpenAI and Anthropic for optional intelligence features that a customer enables.
Assistance with data subject requests and compliance
Taking into account the nature of processing, WaverSec will provide reasonable assistance to help the customer respond to data subject requests and meet obligations relating to security, breach notification, impact assessments, and prior consultation, to the extent required by law and reasonably possible in light of the service.
The customer remains responsible for evaluating whether its use of WaverSec Protect is lawful and for responding to data subject or regulator requests directed to the customer.
Security incident notification
WaverSec will notify the customer without undue delay after becoming aware of a confirmed security incident affecting customer personal data processed by WaverSec as processor, and will provide information reasonably available to WaverSec to help the customer assess and respond to the incident.
Notification may be delayed only to the extent necessary to determine scope, restore integrity, or comply with law enforcement or legal restrictions.
International transfers
Where personal data subject to GDPR or a similar regime is transferred outside the EEA, UK, or Switzerland, WaverSec will use the transfer mechanism that is appropriate for the specific transfer, such as adequacy decisions, Standard Contractual Clauses, or the UK addendum where applicable.
Deletion or return of data
At the end of the applicable service relationship, WaverSec will delete or return customer personal data in its possession as processor, unless retention is required by law, necessary for security logs, backup expiry cycles, fraud prevention, dispute handling, or another documented legitimate purpose permitted by law.
Because WaverSec Protect is designed not to retain message bodies, recipient lists, or attachment files in its application databases as normal service records, post-termination deletion obligations focus primarily on operational records and customer-configured data that remain in WaverSec systems.
Information and audits
WaverSec will make available information reasonably necessary to demonstrate compliance with this DPA. If further verification is legally required, the parties will work in good faith to agree on a proportionate audit mechanism that protects the confidentiality and security of other customers and WaverSec systems.
Any audit must be limited in scope, conducted during normal business hours, avoid operational disruption, and be subject to reasonable confidentiality and cost-allocation protections.
Conflict and priority
If this DPA conflicts with another part of the customer agreement on data protection matters, this DPA controls for those matters unless a negotiated enterprise addendum expressly states otherwise.