slug: clerk-io
provider: Clerk.io
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 1
edges:
- tag: Privacy
  spec_file: clerk-io-privacy-api-openapi.yml
  capability_id: BC-130.50
  capability_id_l1: BC-130
  capability_name: Privacy & Data Protection Management
  confidence: 0.8
  evidence: GET /privacy/forget  privacy-forget ... GET /privacy/info  privacy-info
  reason: Endpoints implement data-subject rights — erasure ('forget') and access to stored personal data
    ('info') — which is squarely privacy and data-protection compliance. Some ambiguity only over whether
    to frame it as the SaaS vendor's service-privacy commitment surface.