Updated: 1 November 2026.
1. Parties, incorporation and subject matter
The controller is the organization identified in the order. The processor is schukai, postal address Eichenstraße 26, 82290 Landsberied, Germany, contact: hey@schukai.com. The full legal identity is in the imprint.
This agreement is incorporated electronically or in writing with the specific order. The order identifies the organization, authorized instruction contacts, service and duration and the binding operational schedule under section 8. Publication of this agreement does not conclude a contract. Processing on instructions starts only after incorporation of the agreement and confirmation of the operational schedule for that order.
The subject matter is processing on instructions for encrypted Hosted exchange, organization inbox, templates, device management and configured notifications. It continues for the agreed service and subsequent return/erasure. This does not make local Community transfers processing by schukai. schukai's own contract, accounting and service-security purposes are described separately in the privacy notice.
2. Data and data subjects
Processing includes receipt, storage, provision, transmission, association and erasure of encrypted contents and related metadata. Data subjects are employees, external senders and recipients and other persons determined by the organization. Data comprise contents, organization and device identifiers, public keys, roles, domain proofs, times, sizes, delivery status and any notification addresses. The service processes no private content keys. The controller determines allowed contents, legal bases and any special categories before use and assesses the suitability of the safeguards.
3. Instructions and confidentiality
schukai processes only on documented instructions, including third-country transfers, unless required by law. The controller is informed beforehand unless prohibited. If schukai doubts an instruction's lawfulness, it informs the controller without delay and resolves the issue before execution. Authorized persons are bound to confidentiality and receive only necessary access. Instructions, identity checks and incident contacts are documented through the channels specified in the order.
4. Security, assistance and incidents
schukai implements the agreed measures and regularly tests their effectiveness. Changes must not lower the agreed protection. Taking account of processing and available information, schukai assists with data-subject rights, security, notifications, impact assessments and prior consultations. Requests received directly about data processed on instructions are forwarded to the controller without delay, unless a legal duty requires otherwise.
schukai notifies the controller of personal data breaches without undue delay after becoming aware, with available information about their nature, affected data and persons, consequences, contact and mitigation. Missing information is supplied without undue delay; notification does not wait for completed root-cause analysis. Report security incidents to hey@schukai.com.
5. Subprocessors and transfers
Subprocessors require the controller's prior specific written or electronic authorization in the operational schedule. Changes are submitted for approval before use. schukai imposes equivalent data-protection obligations and remains responsible for performance. Third-country processing additionally requires an evidenced lawful Chapter V GDPR mechanism; an EU server region is insufficient.
Hosting is planned with DigitalOcean, LLC, Frankfurt (fra1) server region. Mail transport uses the Hosted adapter and schukai's gateway in Landsberied. The complete specific chain, including access, maintenance and backup providers, is identified and approved in the schedule before processing. This description is no blanket authorization of unknown subprocessors. Google Play's own store purposes are assessed separately; recipient mail services and webhook targets designated by the organization are classified according to their actual roles.
6. Evidence and audits
schukai makes available all information necessary to demonstrate compliance and allows and contributes to audits, including inspections, by the controller or its mandated auditor. The parties coordinate logistics and protection of others' data without preventing necessary audits. External certification is not promised.
7. Return, erasure and backups
After service ends, data processed on instructions are returned or erased at the controller's choice and existing copies erased, unless law requires retention. Retained data are restricted to that statutory purpose. The order makes return format, deadlines, permissible residual data, backup expiry and reconciliation after restoration binding. schukai cannot return private content keys or lost Relay payloads.
Version 1.0 has no automatic organization-wide server erasure. Cancellation, entitlement expiry, review revocation or test-window closure alone does not erase durable organization data. An executable access/erasure procedure and its owner must therefore be agreed and evidenced before processing begins. A technical gap does not remove statutory obligations.
8. Operational schedule: measures and lifecycles
The schedule specifies the following requirements for the particular order:
- TLS and device/browser-side content encryption; no private content keys in the service; separate content and entitlement authority. Delivery of browser code is part of the trust boundary.
- Separate Relay/Control data. Relay contents end on terminal state or expiry, without backup or WAL archiving. Content-free Relay records and completed notification deliveries have a seven-day lifecycle.
- Transient recipients and Play retry secrets are excluded from Control backups. Their conditions and other technical periods are described in the privacy notice and reconciled for the particular order.
- Purchase provenance, review and test-window records are separate from the 30-day pruning of terminated purchase records. The order expressly allocates durable metadata, purposes and permitted retention; absence of automatic cleanup does not justify indefinite retention.
- Access controls, secure administration, confidentiality, patching, incident handling and regular effectiveness reviews and evidence are specified with responsibilities and review scope.
- Production Control backups are not promised as available or recoverable in this version. The temporary operational exception ends on 10 November 2026 at 22:14:10 UTC; expiry does not establish an implemented backup. Permanent data loss is possible. Suitability of this state must be assessed before processing. Later backups need an updated schedule stating location, scope, retention and erasure/revocation reconciliation before traffic resumes.
- Mail gateway: maximum queue lifetime five days including bounce messages; weekly log rotation with four archives alongside the current file. Gateway backups may contain delivery metadata. Their retention and erasure are agreed separately from application periods.
The binding schedule specifically identifies approved providers, countries, transfer safeguards, periods and contacts. This agreement replaces neither verification of their actual implementation nor incorporation of that schedule.