Last updated 10 October 2026
Data Processing Agreement
When an organisation uses Oras Work accounts, it decides about its members' data and we process that data on its behalf. This agreement sets out how, as Article 28 of the GDPR requires.
1. Parties and roles
This agreement is between the organisation that owns an Oras Work account ("Customer") and You're Going Places Limited, Navarinou 18, Navarino Business Centre, Agios Andreas, 1100 Nicosia, Cyprus, HE 465790 ("Oras"). The Customer is the controller and Oras is the processor of the personal data described in Annex 1. Words such as "personal data", "processing", "controller", "processor" and "personal data breach" have the meaning given in the GDPR (Regulation (EU) 2016/679).
Oras is a controller, not a processor, only for its own account administration, billing, security of the service and legal obligations, as described in our Privacy Policy.
2. Instructions
- Oras processes personal data only on the Customer's documented instructions. The Terms of Service, this agreement and the Customer's use and settings of Oras (including the actions of its admins) are the Customer's complete instructions.
- Oras may also process personal data where EU or member state law requires it. In that case Oras informs the Customer before processing, unless that law forbids it.
- Oras tells the Customer immediately if it believes an instruction breaks the GDPR or other data protection law.
3. Confidentiality
Everyone at Oras who may access personal data is bound by confidentiality, by contract or by law, and only gets the access needed for their task.
4. Security
Oras takes the technical and organisational measures required by Article 32 GDPR, described in Annex 2. Oras may improve these measures over time, but will not lower the overall level of protection.
Much of the Customer's content is end-to-end encrypted with keys that only its members hold. Oras cannot read that content and the Customer accepts that Oras therefore cannot recover it if members lose their passwords and recovery phrases.
5. Sub-processors
- The Customer gives general permission for Oras to use sub-processors. The current list is at oras.si/subprocessors.
- Oras informs the Customer's owners by email at least 30 days before adding or replacing a sub-processor. The Customer can object on reasonable data protection grounds within that period. If we can't resolve the objection together, the Customer may end the affected service and receive a refund of prepaid fees for the remaining period.
- Oras imposes the same data protection obligations on each sub-processor as in this agreement, and remains responsible to the Customer for its sub-processors.
6. Helping the Customer
- Requests from people: Oras gives the Customer's admins tools to manage members' accounts, and helps the Customer answer requests from people exercising their GDPR rights. If Oras receives such a request directly, it forwards it to the Customer and does not answer it itself, unless the Customer asks it to.
- Other obligations: Oras helps the Customer with its obligations under Articles 32 to 36 GDPR (security, breach notification, data protection impact assessments and prior consultation), taking into account the information Oras has.
7. Personal data breaches
Oras informs the Customer without undue delay, and at the latest within 48 hours, after becoming aware of a personal data breach affecting the Customer's data. The notice describes, as far as known, what happened, the data and people concerned, the likely consequences and the measures taken or proposed. Oras adds information as it becomes available and takes reasonable steps to limit the damage.
8. Location and transfers
Oras stores and processes the Customer's personal data in the European Economic Area, currently in the Netherlands. Oras does not transfer it outside the EEA without the Customer's prior written approval, and only with the safeguards required by Chapter V GDPR.
9. End of the service
When the service ends, the Customer's admins can save their data first. Oras then deletes the Customer's personal data within one month, and encrypted backups are overwritten within 14 days after that deletion, unless EU or member state law requires Oras to keep it.
10. Information and audits
Oras makes available the information needed to show compliance with Article 28 GDPR, such as this agreement, its security measures and summaries of independent security tests when available. If that is not enough, the Customer may have an audit carried out, at its own cost, by an independent auditor bound by confidentiality, with at least 30 days' notice, during normal working hours and not more than once a year, unless a breach or a supervisory authority requires otherwise. Audits must not put the security of other customers at risk.
11. General
- This agreement lasts as long as Oras processes personal data for the Customer.
- If this agreement and the Terms of Service conflict, this agreement wins on data protection.
- Liability is governed by the Terms of Service, without limiting either party's liability to people under Article 82 GDPR.
- This agreement is governed by the law of the Republic of Cyprus, and the courts of Nicosia have jurisdiction.
- Oras may update this agreement to meet legal requirements or to improve protection, and informs the Customer at least 30 days before changes that affect it.
Annex 1: the processing
| Subject and purpose | Providing Oras to the Customer: encrypted email, team inboxes, chats, contacts, calendars and related features, including storage, delivery, backup, security and support. |
|---|---|
| Duration | For the duration of the Customer's use of Oras, plus the deletion periods in section 9. |
| Nature | Storage, transmission, encryption, backup, deletion and, for mail arriving from outside Oras, automatic spam checks before encryption. |
| People concerned | The Customer's members and admins, and the people they communicate with. |
| Types of personal data | Account data (names, addresses, roles, status), sign-in and session data, public keys, encrypted private keys, mail (encrypted content; readable sender, recipients, date, size and subject), contacts, calendars, chat metadata (members of conversations, times, device names) and end-to-end encrypted chat content and files. |
| Special categories | Oras does not ask for special categories of data. The Customer's members may include them in content, which is end-to-end encrypted where described in our Privacy Policy. |
Annex 2: technical and organisational measures
Encryption
- End-to-end encryption of stored mail with OpenPGP. Mail arriving from outside Oras is encrypted with the recipient's public key before it is stored; team inbox mail is encrypted with the team key within seconds of arrival.
- End-to-end encryption of chats and chat files with the Matrix encryption protocol. The chat server refuses unencrypted messages.
- Private keys are created on members' devices and stored only in encrypted form. Passwords are not sent to Oras (OPAQUE in the Oras app, a derived sign-in key in Oras Mail).
- TLS for all connections. Encrypted backups (AES-256).
Access control
- Invitation-only accounts. Two-factor sign-in with authenticator apps, passkeys or security keys; required for admins in the Oras app, who must also confirm sensitive actions again.
- Short-lived access tokens (10 minutes) and rotating sign-in tokens; members can sign out other devices.
- Server access only with personal SSH keys, by as few people as possible. Firewall and automatic blocking of repeated failed logins.
- Admins of one organisation cannot see other organisations.
- Oras staff manage accounts only through a separate admin site that requires a passkey, remembers nothing on the device, ends after 30 minutes without activity and asks for the password again before any change. Every staff action is logged.
Minimal data and logging
- No web access logs. Rate limits are kept in memory only. Chat connection IP addresses are kept for at most one day.
- No analytics, advertising or tracking. Remote images in mail are loaded through a privacy proxy.
- Chats are not shared with other servers (no federation).
Availability and resilience
- Daily encrypted backups, kept for 14 days, and a documented restore procedure.
- Automatic security updates of the operating system, and a staged release process (test, beta, live) with automatic backups before each update.
Organisational measures
- Confidentiality obligations for everyone with access.
- A documented response plan for incidents and personal data breaches.
- Hosting with a sub-processor in the EU that is bound by a data processing agreement.
- Regular review of security measures, including independent security testing.