Delete request

What is the delete request?

If you are named in a protocol as a data subject or have a legitimate interest in having data removed, you can submit a delete request through the protocol viewer (Art. 17 GDPR — right to erasure).

The request is forwarded to the protocol creator — the owner or controller who created the protocol. deep.rent stores protocol data as a processor; the creator decides how to handle the request.

Opening the page

At the bottom of every protocol page in the viewer, the footer includes a “Delete Request” link (alongside terms, privacy, and website). Clicking it opens the form for the currently loaded protocol.

The form

At the top — when available — you see protocol information:

You then enter:

• First name and last name
• Email (for follow-up by the creator)
• Reason for the deletion request

Before submitting, read the legal notice on the page. Tap “Send Delete Request” to submit.

After a successful submission you receive a confirmation — not an automatic deletion decision.

What happens for the owner?

The protocol creator (owner / controller) is notified of your delete request. They may, for example:

• delete the protocol entirely,
• correct, restrict, or anonymise personal data, or
• decline the request where legal retention obligations or other legal grounds apply.

There is no obligation to comply with the request. Whether and to what extent data is deleted or adjusted is entirely up to the protocol creator. They may contact you directly if needed.

Role of deep.rent

• deep.rent forwards the request but does not review, evaluate, or decide on delete requests.
• deep.rent cannot perform deletion on behalf of the requester — the creator remains responsible.
• deep.rent intervenes only when content violates the terms and conditions; in that case content may be taken down independently of a delete request.

In short: the delete request is a channel to the protocol owner, not an automatic deletion order to deep.rent.