Requests arrive everywhere
Web forms, the privacy inbox, and authorized-agent services all send requests in different shapes. Each one has to be found, read, and logged before work can start.
Data subject requests
Superset takes in verified requests from your web form, your privacy inbox, and authorized agents. Then it runs the action in your own systems and tells the requester when it's done.
Your team only touches the requests that actually need a person.

Most of the work in a data subject request happens before and after the part that matters.
Web forms, the privacy inbox, and authorized-agent services all send requests in different shapes. Each one has to be found, read, and logged before work can start.
Chasing missing details and confirming the requester is real takes days your statutory deadline doesn't give you.
The actual deletion or opt-out happens in your own databases, so every request turns into a ticket for engineering.
Three things to set up. The first two take one sitting, and the third gets easier once requests are flowing.
Pick the fields you need to find someone in your records, then share the portal link on your privacy page and in your email footers.
Sign in with your privacy mailbox or set up forwarding, so requests that arrive by email get classified and routed too.
Turn on the rights Superset should handle end to end. Everything else waits in your queue for a person to review.

From your form, your inbox, or an authorized agent, checked against the fields you require.
An API call to your own endpoint carries out the deletion, opt-out, or other action, with the request's details filled in.
A confirmation email goes out once your endpoint reports success. If you hold no records, a no-match email goes out instead.
You choose who gets auto-executed: requests from authorized agents, from data subjects directly, or both.
Three layers of protection on every form submission, so you can act on a request with confidence.
Cloudflare Turnstile keeps automated junk off your form.
The form turns away email addresses whose domain doesn't exist or can't receive mail.
Every submission sends a verification link. Nothing is processed until the data subject clicks it.
Request types map to the rights in CCPA/CPRA, GDPR, and the other U.S. state privacy laws. Turn on automation for each one when you're ready.
Prefer to process requests in your own systems? The Superset API lets you pull request data, create requests from other channels, and report status back in bulk. The requester still gets the right email either way.
Read the API docsSet up your form, connect your inbox, and let Superset handle the requests that don't need a person.