Data processing agreement
In plain English
- When a business uses MigrateMyMail to move its mailboxes, the mail belongs to the business. We only handle it to copy it, on your instructions.
- We do not store the content of the email, we protect the passwords, and we delete them when the job is done (or 30 days later, if you ask us to keep them for re-syncs).
- We tell you without delay if anything goes wrong with your data.
- This agreement applies automatically to business customers. Nothing needs signing.
1. What this is
This agreement is part of the terms of service between you (a business customer, "you") and Daniel C Brummitt trading as MigrateMyMail ("we"). It applies where we handle personal data for you that is subject to UK data protection law (the UK GDPR and the Data Protection Act 2018) or, where it applies to you, the EU GDPR.
For that data you are the controller, or a processor acting for your own customer, and we are your processor (or sub-processor). Our own use of your account and payment details is covered by the privacy policy, not by this agreement.
2. What we handle for you
| Purpose | Copying email from the source mailboxes to the destination mailboxes you choose, testing sign-in, measuring sizes, and reporting the result |
|---|---|
| How long | For each migration: from when you add its mailboxes until its records are deleted (section 3.7) |
| Kinds of data | Email messages and attachments (which can contain any kind of personal data, including sensitive data); folder names; mailbox addresses and usernames; mailbox passwords; mailbox sizes and message counts; technical records of the copy |
| Whose data | Your staff and other mailbox users, and the people they have exchanged email with |
3. What we promise
- Your instructions only. We handle the data, including sending it to the destination you choose wherever that is, only on your documented instructions: the way you set up the migration, these terms and anything else you tell us in writing. The only exception is where the law requires otherwise, in which case we tell you first unless the law forbids it. We tell you if we think an instruction breaks data protection law.
- Confidentiality. Anyone working for us who can reach the data is bound to keep it confidential.
- Security. We take the measures the law requires (Article 32 of the UK GDPR), including those in section 7, and may improve them.
- Sub-processors. You agree that we may use the companies listed as handling mailbox data on our Sub-processors page. We hold each to the same data protection obligations as these and remain fully responsible to you for what they do. We post changes on that page and email you at least 14 days before a new sub-processor starts handling mailbox data. If you object on reasonable data protection grounds and we cannot resolve it, you may stop using the service and we will refund any migration not yet carried out.
- Helping you. Taking into account what we handle, we help you, by appropriate technical and organisational measures, to answer requests from people exercising their data protection rights, and with your duties on security, breach notification, impact assessments and consulting the regulator. If someone sends us such a request about your mailboxes, we pass it to you and do not answer it ourselves.
- Breaches. If we become aware of a breach of security affecting your data, we tell you without undue delay, give you what we know at once (what happened, what data and whose, what we have done and what we suggest you do), and add to it as we learn more.
- Returning and deleting. When the service for a migration ends, you choose whether we return or delete the personal data we hold for you, and we delete remaining copies unless the law requires us to keep them. In practice: the content of the email is never stored by us (it remains in your source and destination mailboxes); mailbox passwords are deleted when the migration finishes, or 30 days after it first finished if you ask us to keep them for re-syncs; unpaid drafts and their passwords are deleted after 7 days (up to 2 days longer if payment had been started). The other records of a migration (addresses, sizes, results and technical output) stay until you ask us to delete them or delete your account; on request we send you a copy first. They leave our backups within 35 days after deletion. Payment records are kept as the law requires.
- Showing you. We make available all information needed to show we keep to this agreement, and we allow and contribute to audits, including inspections, by you or an auditor you appoint. For routine audits we ask for reasonable notice, working hours, no more than one a year, a duty of confidentiality, and care that other customers' data is not put at risk; you bear your own costs. These limits do not apply to an audit required by a regulator, needed after a breach, or reasonably necessary to look into a suspected failure to keep to this agreement.
4. What you promise
You have the right to give us this data and these instructions: you have a lawful basis for the migration, and the authority to access every mailbox you ask us to copy.
5. Where the data goes
Our server and database are in Ireland; that is the only place we store mailbox passwords and the content-free records of a copy. Emails we send about a migration (which can name mailbox addresses) pass through our email delivery provider, listed on the Sub-processors page with its location. The source and destination email providers you choose may be anywhere in the world: we send the mail there on your instructions, and each of us meets the transfer obligations that apply to it. If we ourselves ever needed to move mailbox data outside the UK and the European Economic Area for any other reason, we would first put in place safeguards the law recognises and tell you as in section 3.4.
6. Liability and precedence
The limits of liability in the terms of service apply to this agreement. If this agreement and the terms say different things about personal data, this agreement wins.
7. Our security measures
- Email content is not stored. Messages and attachments pass through the server's memory from one mailbox to the other. Records of the copy (addresses, sizes, folder names, results and technical output with anything password-like removed) are kept as described above.
- Passwords: when saved they are encrypted to a key that only the migration worker holds, so the website and the database cannot decrypt them; they are never written to logs; deletion is real deletion, on the schedule above.
- Isolation: each migration job runs as its own temporary user, with restricted access to files, memory-only temporary storage, its own memory limit and network controls that block internal addresses.
- Encryption in transit: connections to mail servers must use TLS, with the certificate checked; this site is HTTPS only.
- Access: the production system is administered by its owner only; the back office requires two-factor sign-in; the code that runs is owned by the system administrator and changed only by a deliberate release.
- Records: security-relevant actions are logged; sign-in attempts are rate-limited.
- Backups and recovery: backups are encrypted and kept with Amazon Web Services; each is kept for no more than 35 days.
- Notice to mailbox owners: we try to email each source mailbox when a copy of it starts.
Last updated