Help centre · Privacy requests

Answer privacy requests on time

Add a request form to your privacy page, send requests to the Velo queue and answer each one before its reply by date.

5 min readReviewed 18 November 2026

How requests reach Velo

Velo keeps one queue of privacy requests for each account: access, deletion, consent withdrawal and other requests. A request gets into the queue when a form sends it to Velo: the form Velo hosts for each of your sites, or one you add to your own website.

Each request arrives with a reply by date 30 days after it was received. Velo shows it as due soon a week before that date, and as overdue after it.

Velo also emails the person a link to confirm that the address they gave is theirs. The queue shows whether they did.

Before you start

  • Find your site ID in Configuration, in the Site card. A form you build has to send it, or the request reaches no queue.
  • Decide where the form goes. A privacy page or the privacy section of your contact page works well.
  • Decide who checks the queue. Velo notifies you in the console, not by email.

Use the hosted form

Every site has a request form at https://app-staging.veloconsent.com/privacy-request/your-site-id. Find its link in Requests, in the Your request form card, and link to it from your privacy notice. There is nothing to install.

The form opens in the visitor’s browser language when that is English, Spanish, French, Portuguese or German, and in English otherwise. Add ?lang=es to the link to choose the language yourself.

Or build your own form

Paste this form and script where the form should appear, and replace your-site-id with your own site ID. Change the labels and the wording to match your site. The script reads the visitor’s consent receipt from the velo_receipt cookie, when there is one, so the request arrives linked to their consent history.

Example only · use your own site ID
<form id="privacy-request">
<label>Name <input name="name" required></label>
<label>Email <input name="email" type="email" required></label>
<label>Request
<select name="type">
<option value="access">See my data</option>
<option value="delete">Delete my data</option>
<option value="withdraw">Withdraw my consent</option>
<option value="other">Something else</option>
</select>
</label>
<label>Message <textarea name="message" maxlength="2000"></textarea></label>
<button type="submit">Send request</button>
<p id="privacy-request-status" role="status"></p>
</form>
<script>
document.getElementById('privacy-request').addEventListener('submit', async (e) => {
e.preventDefault();
const f = e.target, status = document.getElementById('privacy-request-status');
const receipt = (document.cookie.match(/(?:^|;\s*)velo_receipt=([^;]+)/) || [])[1];
const res = await fetch('https://app-staging.veloconsent.com/v1/requests', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({
site_id: 'your-site-id',
name: f.name.value, email: f.email.value, type: f.type.value,
message: f.message.value || undefined,
receipt_id: receipt ? decodeURIComponent(receipt) : undefined,
source_url: location.origin + location.pathname,
}),
});
status.textContent = res.ok ? 'Thank you. Your request has been received.' : 'That did not go through. Please check the form and try again.';
if (res.ok) f.reset();
});
</script>

The form can live on any page of your site, on any platform where you can add HTML and a script.

What the form sends

FieldRequiredWhat it is
site_idYes, in practiceYour site ID. Without it the request is stored but appears in no account’s queue.
nameYesUp to 200 characters.
emailYesA valid address, up to 320 characters.
typeYesaccess, delete, withdraw or other.
messageNoUp to 2,000 characters.
receipt_idNoThe visitor’s consent receipt ID, which links the request to their consent history.
source_urlNoThe page the form was sent from. Velo keeps the address without its query string.

A request that is accepted gets the answer 201 with a request ID and confirmation_sent, which says whether Velo emailed the person a confirmation link. A request with a missing or wrong field gets 422 and the list of what to fix.

Work through the queue

  1. Open Requests and select the website, or All sites.
  2. Use the Open, Due soon, Overdue and Closed views, and filter by request type.
  3. Open a request to see the person’s details, whether they confirmed their email, their message and, when the form sent a receipt ID, that receipt and their earlier consent decisions. Export the history as CSV if your reply needs it.
  4. Move the request to In progress while you work on it, and to Resolved or Rejected when you have replied.

A notification appears in the console when a request arrives and again when it is due soon.

What stays with you

  • Check who the person is before you send or delete any data. A confirmed email is a start, not proof of identity.
  • Find and handle their data in each of your own systems.
  • Check the deadline your law sets. Velo’s 30 days is a working date: the GDPR gives one month, which can be extended in some cases, and other laws differ.

Test the form

  • Send a test request from the hosted form, or from your own form, with an email address you own.
  • Open the confirmation email, follow its link, and check that the request shows Email confirmed.
  • Check that it appears in Requests with a reply by date 30 days out.
  • Accept the banner, send a second test and check that its receipt and consent history appear in the request.
  • Move both tests to Rejected, so they do not count as open work.

Still stuck?

Tell us where you got to and we will pick it up from there.