Privacy policy, in plain terms.

migrationHIPPO is operated by ITPS (NZ) Limited, New Zealand (“we”, “us”). This policy covers the migrationHIPPO website and application at migrationhippo.app and the services that run migrations for it.

When you migrate an organisation’s data, that organisation decides what is migrated and why; we process it on its instructions. If you are a user whose mailbox or files are being migrated by your organisation, your organisation is the right first contact for questions about that migration.

• Account information. Your name, email address, company name, and either a password (stored only as a one-way hash) or the identity of the Microsoft or Google account you sign in with.
• Billing information. What you bought and when. Card details are entered with Stripe and never reach our servers.
• Connection credentials. The access tokens, keys or certificates that let us reach the accounts you connect. They are encrypted before they are stored.
• Migration records. To track and verify each item we move, we record details about it: identifiers, folder and label names, file names and paths, sizes, checksums, email subject lines, timestamps, and whether it succeeded. This is how we can resume a migration, avoid duplicates and show you what moved.
• Content in transit. The messages, events and files themselves pass through our migration servers on their way from the source to the destination. We do not keep a copy once an item has been delivered.
• Operational logs. Technical records of requests and errors, used to run and secure the service.

We use this information only to provide the service you asked for: to connect your accounts, plan and run migrations, verify the results, report on them, bill for them, support you, and keep the service secure. We do not sell personal information, use it for advertising, or build profiles of the people whose data we migrate.

When you connect a Google account, you grant migrationHIPPO the following access. Each one is used only to migrate that account’s data, as you direct.

We never change or delete anything in a source account. In a destination account we only create items, and, when you run a follow-up sync, remove or trash items we previously migrated there so that the destination mirrors deletions made at the source.

migrationHIPPO’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:

• We use Google user data only to provide and improve the migration features you can see and use in migrationHIPPO.
• We transfer it only to the destination you choose for the migration, to the service providers listed under Who we share it with who process it on our behalf to provide the service, where required by law, or as part of a merger or acquisition with notice to you.
• We do not use it for advertising, and we do not sell it.
• We do not use it to develop, improve or train generalised artificial intelligence or machine learning models.
• Nobody at migrationHIPPO reads your Google user data. We don’t keep message, event or file content, and we have no tool for viewing it. The item details we do keep, such as subject lines and file names, are used only to run and report on your migration, and are shown only to your organisation.

You can remove migrationHIPPO’s access at any time from your Google Account’s third-party access page, or by deleting the connection in migrationHIPPO, which erases the stored credentials.

Microsoft 365 accounts are connected through an app registration in your own tenant, with permissions you grant there. For a Microsoft 365 source, those permissions are read and export only. Microsoft 365 data is handled exactly as described above for Google: used only to perform the migration you asked for, never sold, never used for advertising or to train AI models, and not read by anyone at migrationHIPPO.

We use these service providers to run migrationHIPPO. Each processes data only on our instructions and only to provide its part of the service.

As the table shows, information is stored and processed outside New Zealand, in Australia and the United States. We use providers that protect it to a standard comparable to New Zealand law.

Migration content goes to the destination account you choose, and nowhere else. We disclose information to authorities only when the law requires it.

• All traffic to and from migrationHIPPO, and to Google and Microsoft, is encrypted in transit.
• Connection credentials are encrypted at rest with a key specific to your company, so one customer’s credentials cannot be decrypted with another’s key.
• When a migration is between two organisations that each connect their own accounts, neither ever sees the other’s credentials.

• Content is not kept after it has been delivered to the destination.
• Credentials are erased when you delete the connection.
• Migration records are kept while your licence lets you re-run the migration (90 days from first use) and then for 14 more days, after which they are permanently deleted. You can permanently delete a migration sooner from the application.
• Account information is kept while your account is open.
• Billing records are kept as long as tax and accounting law requires.

You can ask us for a copy of the personal information we hold about you, ask us to correct it, or ask us to delete it, by writing to privacy@migrationhippo.app. We will respond within the time the law allows, and we will not charge you for a reasonable request. We are subject to New Zealand’s Privacy Act 2020; if you are not satisfied with our response you can complain to the Office of the Privacy Commissioner. Depending on where you live you may have further rights under local law.

We may update this policy from time to time. The date at the top of this page shows when it last changed.

Privacy questions and requests: privacy@migrationhippo.app
Everything else: help@migrationhippo.app

ITPS (NZ) Limited, New Zealand