Answer a data-subject request
A person has the right to be told what you hold about them (an access request, GDPR Article 15) and to have it removed (an erasure request, Article 17). Privacy requests, under Account settings, answers both for one email address in one workspace. It shows every place MarqIQ holds something for that address, in plain words, lets you copy the records into your reply, and erases the lot in one confirmed step. It also tells you what it keeps and why, and what it cannot do — because a request answered with a half-truth is not answered.
Before you start
- You need the Workspace Admin role. The screen opens for anyone, but the buttons are refused for other roles.
- Have the email address exactly as the person gave it. Capitalisation does not matter — MarqIQ matches an address however your tools stored it.
- An erasure cannot be undone. Read what is held first; the screen makes you do this before it offers to erase.
See what MarqIQ holds
Open Account settings and choose the Privacy requests tab.
Enter the email address and click Show what is held.
MarqIQ reads every place it could hold something for that address. On a large workspace this can take more than one pass; the button says which pass it is on, and the screen never shows a partial answer as if it were complete.
Read the tiles.
Each tile is one place data is held, in the words you would use to the person: form submissions, contact records, email opens and clicks, raw copies of tool records, records that failed to sync, links to deals, leads, proposed changes, rows in uploaded spreadsheets, and mentions inside other people’s rows. A grey tile means nothing is held there.
Open The records themselves to copy the export.
The block holds the contact records and form submissions as MarqIQ stores them. Paste it into your reply — it is their Article 15 answer. If the person has more than 500 submissions, the most recent 500 are shown and the total is stated.
Open What stays, and why.
This is the honest half. It lists what an erasure would not remove — a company record, a deal the person was attached to, the audit entry of the request itself — and the reason for each. Include it in your reply; a reviewer will ask.
Known to your tools as
Under the tiles the screen names the record ids your tools use for this person, for example a HubSpot contact number. Those are what MarqIQ used to find the payload copies, and they are what you need if you go on to delete the person in the tool itself.
Erase everything held
Below the tiles, type the address again into the red box.
The address is the confirmation. There is no second click to mis-hit; you type what you are erasing.
Click Erase permanently.
Every place counted above is cleared, in an order that is safe to interrupt: if the request is cut off part-way, running it again for the same address finishes the job. The screen shows which pass it is on.
Read the result.
The tiles now show what was removed from each place. Below them: that the workspace’s cached analyses were cleared (one can hold this person’s values as an example), how many copies were found by reading the tool’s payload rather than by id, whether the activity-log entry was written, and — again — what stays and why.
Delete the person in your connected tool as well.
This is the step people miss, and the screen says it in red. An erasure in MarqIQ is not an erasure in HubSpot, Salesforce or your spreadsheet. While the person still exists there, the next sync brings them back. A linked Google Sheet is re-fetched from Google on refresh, which also restores the rows this erasure cleared.
Take care
If the result says Partly erased — run it again to finish, do that before you reply to the person. It means the workspace held more than one pass could read, and the screen carries on exactly where it stopped when you click Continue erasing.
What the erasure deliberately keeps
Each is listed on the screen with its reason, in the route’s own words. The short version:
| Kept | Why |
|---|---|
| A company record | It belongs to every contact at that company. Deleting it on one person’s request would erase other people’s records. A sole trader identifiable by a company record should have it removed as a company record. |
| A deal the person was attached to | The link between the person and the deal goes. The deal is the company’s commercial record and stays. On Zoho CRM and Dynamics 365 a deal can still carry the person’s display name in a lookup field, because those tools write the name rather than an id. |
| The names of your own users | Every synced record carries its owner’s name — your salesperson, not a data subject of this workspace’s records. A request from one of your own staff is a request about your staff data and is not answered here. |
| A second email address held inside a contact’s properties | The contact record keeps one address in its email field. An alternate address stored only inside the tool’s properties is not matched by an erasure asked about that other address. |
| Meeting attendees beyond the first | A synced meeting or call keeps one address in its email field and the rest inside the event’s properties. |
| The audit entry of this erasure | It is written with the address as its key, on purpose, as the record that the request was received and acted on. |
| A mark on a change set that sent a write to the person’s record | The proposed changes about the person are deleted. Where MarqIQ had sent one of them to your tool, the change set keeps a mark that one of its changes was to a record since erased, so it does not claim to have been put back. The mark holds no id, address or value. It keeps one thing: whether that change read Changed or was never confirmed. A value MarqIQ wrote is still in your tool; one it sent and could not confirm may be. |
What the screen does not do
- It does not reach into your tools. Nothing in HubSpot, Salesforce, Marketo, Pipedrive, Zoho, Dynamics or a spreadsheet changes. Delete the person there yourself.
- It does not stop the person coming back. There is no suppression list yet: a synced tool that still holds the person re-creates them here on its next run.
- It does not remove the person from other workspaces. Each workspace answers its own requests.
If it did not work
The buttons do nothing, or the screen says only an admin can act
Why: Your role is not Workspace Admin. The screen is visible to everyone so a person with a request knows where it is answered; acting on it is restricted.
Fix: Under Team & roles, find someone with the Workspace Admin role and pass the request to them, or ask to be given that role.
“This workspace’s database is not ready yet”
Why: The workspace’s own database is still being created, or its creation failed and is being retried. Nothing was changed.
Fix: Wait a minute and try again. If it keeps happening, Setup & diagnostics shows the database’s state, and Support can see what is standing in the way.
The tiles all read 0 but the person says they filled in a form
Why: Either the address they gave is not the one they used, or the form was on a site this workspace’s tracking script does not run on.
Fix: Ask for every address they might have used and run each. Check under Tracking that the script is installed on the site they mean.
I erased them and they are back
Why: They still exist in the connected tool, and the sync re-created them — or a linked Google Sheet was refreshed and re-fetched their row from Google.
Fix: Delete the person in the tool, and remove their row from the source spreadsheet, then erase here once more.
The result says the activity-log entry could not be written
Why: The erasure ran, but the control database refused the audit write at that moment.
Fix: Record the request and the date yourself. The data is gone; only the log line is missing.
Next steps
Related articles
Was this article helpful?