Fulfill every data subject request, across every system you own.

DaedalusDSAR ships with 22 connectors out of the box, with more added regularly. Databases include PostgreSQL, MySQL, MariaDB, MSSQL Server, Snowflake, and Google BigQuery. SaaS connectors cover Salesforce, HubSpot, Stripe, Shopify, Zendesk, Klaviyo, Mailchimp, ActiveCampaign, Braze, Segment, Amplitude, Mixpanel, Okta, Auth0, and Airtable, plus Amazon S3 and DynamoDB. A generic API connector reaches any other REST endpoint using variables drawn from the subject, such as email and name, so anything with an API is in scope. SQL sources discover their own tables automatically, and AWS auto-discovery can scan an entire AWS account, importing each S3 bucket, DynamoDB table, and database as its own connector.

Both. Collect gathers the subject’s data from every connected source; delete then removes it — a permanent GDPR erasure in HubSpot, a customer delete in Stripe, and so on. A review gate sits between the two stages, so your team inspects exactly what was found before anything is removed. For access requests, the subject verifies their identity and downloads their own data report, so fulfillment covers access as well as deletion.

After the delete stage, the Validate stage re-runs collect against the same sources and confirms the records are gone, recording that result as proof the deletion succeeded. Every staff action and stage transition is also written to an audit timeline with the actor and a message, so each request carries its own evidence trail. When legal or an auditor asks how a request was handled, the answer is one screen away rather than a reconstruction after the fact.

Each stage has two independent switches — run automatically and advance automatically — both off by default, so the pipeline is fully manual until you decide otherwise. Turn them on stage by stage for a hands-off pipeline, or leave the collect-to-delete advance off to keep a mandatory human review gate before any data is destroyed. The dashboard tracks active requests, how many are out of regulation, which are due within five days, and your on-time completion rate against the statutory deadline derived from each subject’s location.

The public form is deliberately isolated. The internet-facing container serves only the submission form — the admin console and management APIs return 404 on that runtime and are reachable only from inside your network. The scanners that connect to your data sources run on a separate fleet that holds no database connection and no encryption key and only dials outbound, so the internet-facing surface has nothing sensitive to reach. Submissions are encrypted at rest with AES-256-GCM, and connector credentials can resolve from your own vault at scan time rather than living in the database.

Self-hosted first. DaedalusDSAR ships as containers you run in your own environment with Docker Compose or our AWS CloudFormation template, where it makes no outbound calls and can run fully airgapped, so your most sensitive data never leaves your infrastructure. A managed cloud option is also available when you would rather we operate it, with a scanner that can still sit inside your VPC. Either way, access is gated by local or SSO authentication with passkeys and TOTP multi-factor.

The demo stands the platform up in your own environment, connected to a few of your real data sources, for 30 days. You deploy with Docker Compose or our AWS CloudFormation template, then run live requests through the pipeline so your team sees fulfillment and the audit trail firsthand, all on your own data, before any commitment.