Skip to content
Moirova

Trust center

How we look after the data in your workspace.

Where your data is kept, who processes it for us, how it is backed up, how a deletion lasts, and what we do not claim. In plain words, and only what is in place today.

In short

Moirova keeps each workspace's data separate, lists every provider that processes it, backs it up on a schedule with copies kept up to 98 days, and gives you tools to answer privacy requests - including an erasure that a restore from a backup applies again. Your business decides what happens to your contacts' data; we process it for you.

Who decides

Your data, your decisions.

  • You are in charge of your contacts' data

    Your business decides what it collects about its clients and why. In privacy law, that makes your business the controller of that data.

  • We process it for you

    We store and process your workspace's data to run Moirova for you, and for no other purpose. We do not sell it, and we do not use it for advertising.

  • We are in charge of our own data

    Your team's accounts, sign-in records and billing are ours to look after, as our privacy policy explains.

Where data is kept

Where your data lives.

The main places your workspace's data is stored and processed today. The full list of providers is on our sub-processors page.

WhatWhere
The database (your records)Google Cloud, Mumbai region (India)
The application serversGoogle Cloud, United States
Accounts and sign-inGoogle's global infrastructure
Files you uploadCloudflare R2, or your workspace's own storage if you connect it
SearchA search server we run on a cloud server

Data travels between these places over encrypted connections. We are adding data locations in the United States and the United Kingdom. When they open, each new workspace will choose where its records are kept when it signs up; existing workspaces stay in Mumbai until they are moved. If your business needs its data in a particular country, tell us at hello@moirova.com before you sign up, so we can tell you what is possible today.

Safeguards

What is in place.

  • Each workspace kept separate

    Every record carries its workspace, and both the database's rules and our servers check it on every read and write.

  • Two-step sign-in for everyone

    Every account signs in with a password and a code from an authenticator app, admins included.

  • Access by role

    Each person sees and does only what their role allows, down to their own clients.

  • Credentials kept apart

    Mailbox passwords, email service keys, sign-in tokens and other keys are kept in Google Secret Manager, never in the database.

  • A signed domain (DNSSEC)

    Our domain is DNSSEC-signed: resolvers that check signatures can detect forged answers for our website address and our email records. It protects the address lookup, not the app itself.

  • On record

    Changes to records, settings, access and privacy requests are written to an audit trail people in the workspace cannot edit.

  • Every place personal data is kept, listed

    One register lists where personal data is kept, why and for how long, and our tests fail when code stores it anywhere else.

How each of these works: our security page

Backups and restores

Backed up, and deletions that last.

  • Backups on a schedule

    The database is backed up on a schedule, and the copies are kept for up to 98 days, then deleted. Sign-in accounts are exported daily and kept for the same period.

  • Files can be brought back

    A file deleted or replaced in our main file storage is kept for 30 days and can be restored.

  • One workspace at a time

    A workspace can be restored on its own, without touching any other workspace.

  • Erased people stay erased

    Backups are not edited. Instead, every erasure is written to an erasure ledger, and every restore applies it again, so a person you erased never comes back.

Privacy tools

Answer what people ask about their data.

Requests to see, correct, restrict or delete data are recorded with their legal deadline, answered with tools built for each one, and kept on record as proof. Retention rules delete logs and history on a schedule you choose.

What we do not claim

Honest about where we are.

  • We have not completed an independent security audit or attestation yet. When we do, it will be listed here with its date and scope.
  • Moirova gives you tools that help you meet privacy laws such as the GDPR and US state privacy laws. How you use them, and whether your business meets those laws, is your decision and your responsibility as the controller.
  • The information on this site is not legal advice.

Questions about privacy or security?

Write to us at hello@moirova.com. If your business needs a data processing agreement, ask us there too.

Bring Moirova to your team.

Tell us a little about your business. A person on our team reviews every request and replies by email.