At a glance
- Record the request the day it arrives: the deadline is counted from that date, not from the day you start work on it.
- Moirova sets the deadline from the person's country: 30 days for the EU, the EEA, the UK, Switzerland or no country on file, and 45 days elsewhere.
- Check who is asking before you send anything, and record how you checked. Never keep a copy of an identity document.
- Find gathers every record linked to the person; Download the copy gives a file they can read and a machine-readable file.
Before you start
- Who can do it
- Admins, and anyone an admin gives the permission "Handle privacy requests" in Admin, Roles.
- Where it is
- Admin, Privacy, Requests.
- What you need
- The request itself (an email, a letter, a form or a note of a call) and the contact it is about.
What counts as an access request
An access request is a person asking to see the personal data a business holds about them, or for a copy of it. Under the GDPR it is called a subject access request; US state privacy laws such as the California CCPA and the Texas TDPSA give a similar right to know. People rarely use the legal term: "what do you have on me?" in an email is enough.
Your workspace is the controller of its contacts' data, so the request is yours to answer. Moirova gives you the tools and keeps the record.
Record the request
- Open the register. Go to Admin, Privacy, Requests and choose New request.
- Say what they asked for. Choose "See their data / get a copy". The other types are correct, delete, restrict and opt out of marketing.
- Choose the person. Pick the contact the request is about. If the request came from an authorized agent, record the agent and that they asked for the person.
- Record how and when it arrived. Choose email, phone call, web form, letter, in person or other, and enter the date it arrived. The deadline starts from that date.
- Record the request. The request gets a reference, its deadline and a log. Every later step is added to the log with who did it and when.
Tip
Record a request even when you plan to refuse it. Refusing is also an answer, and the register is your proof that you answered on time.
How the deadline is set
| Where the person lives | Time to answer | One extension, with a reason |
|---|---|---|
| EU, EEA, UK or Switzerland | 30 days | Two more months |
| Anywhere else (US state laws) | 45 days | 45 more days |
| No country on file | 30 days (the stricter clock) | The shorter of the two |
The country comes from the contact record. When it is missing, Moirova uses the 30-day clock so you are never late under the stricter rule. The list and the dashboard warn you seven days before a request is due, and show it as late once the date passes.
Choose Extend the deadline only when you have a reason, such as a request that is unusually complex, and tell the person. The reason is kept in the log.
Check who is asking
Sending someone else's data to the wrong person is a data breach, so check identity before you send anything. Choose Record the identity check and pick how you checked:
- They wrote from the email address you hold for them.
- Someone on the team who knows them confirmed it on a call or in a meeting.
- They answered a check sent to the address or number you hold.
- An identity document was shown to you. Do not keep a copy; Moirova records only that it was seen.
- An authorized agent sent signed permission from the person.
A request cannot be closed as answered until the identity check is recorded.
Find everything and send the copy
- Search. Open the request and run the search. Moirova follows every link to the contact across your records - deals, quotations, invoices, payments, activities, emails, files, notes and more - and shows how many it found in each place.
- Check the results. If a place holds more than the search reads at once, the screen says so rather than hiding it. Confirm records that may belong to someone else with the same name before you include them.
- Download the copy. Choose Download the copy. You get a page the person can read and a machine-readable file (JSON) with the same records. Passwords, sign-in secrets and one-time links are never included.
- Send it securely. Send the files the way you agreed with the person, for example as an attachment to the address you checked.
Close the request
Choose Close the request and pick how it ended: answered, refused or withdrawn by the person. A refusal needs the reason you gave the person and how they can complain. The closed request stays in the register as proof - by default for three years, and never less than two.

