Privacy Tools · push automatique

🚀 Démarrage en 30 secondes

1. 1. Active une clé API dans /admin/api-keys (rôle ADMIN/RSSI, plan Pro ou Enterprise).
2. 2. Appelle GET /api/v1/dpo-export avec le header Authorization: Bearer hxa_….
3. 3. Parse le JSON et importe-le dans ton outil Privacy (script Python, n8n, Zapier, webhook).

🌐 Exemple curl

# Recupere ton snapshot DPO (JSON)
curl -H "Authorization: Bearer ${HUMANIX_API_KEY}" \
  https://humanix-academie.fr/api/v1/dpo-export

🐍 Exemple Python : pull Humanix + push OneTrust

import os, requests

# 1. Recupere les preuves DPO depuis Humanix
r = requests.get(
    "https://humanix-academie.fr/api/v1/dpo-export",
    headers={"Authorization": f"Bearer {os.environ['HUMANIX_API_KEY']}"},
)
r.raise_for_status()
dpo = r.json()

# 2. Push vers ton outil Privacy
# Exemple OneTrust (adapter selon l'API de ton tenant) :
import requests as onetrust
onetrust.post(
    "https://your-tenant.my.onetrust.com/api/dsr/v1/import",
    headers={"Authorization": f"Bearer {os.environ['ONETRUST_TOKEN']}"},
    json={
        "source": "humanix-academie",
        "schema_version": dpo["schema_version"],
        "erasure_queue": dpo["erasure_queue"],
        "rgpd_counters": dpo["rgpd_counters_90d"],
    },
)

# 3. (Optionnel) Alerte sur les requetes en retard
overdue = [r for r in dpo["erasure_queue"] if r["overdue"]]
if overdue:
    print(f"⚠ {len(overdue)} demandes d'effacement en retard (> 30j)")

Adapter le 2e bloc selon l'outil Privacy cible (Didomi, Privacy.fr, Dastra, Witik utilisent chacun leur propre endpoint d'import).

📦 Réponse JSON (schema v1.0)

{
  "schema_version": "1.0",
  "generated_at": "2026-05-24T16:30:00.000Z",
  "tenant": {
    "id": "tenant_abc123",
    "name": "Acme PME",
    "plan": "pro",
    "data_retention_days": 365
  },
  "rgpd_counters_90d": {
    "DATA_ACCESSED": 142,
    "DATA_EXPORTED": 23,
    "DATA_ERASURE_REQUESTED": 4,
    "DATA_ERASURE_COMPLETED": 3,
    "CONSENT_GIVEN": 87,
    "CONSENT_WITHDRAWN": 12
  },
  "erasure_queue": [
    {
      "request_id": "audit_xyz",
      "user_email": "jean.dupont@example.fr",
      "requested_at": "2026-04-20T10:15:00.000Z",
      "completed_at": null,
      "days_pending": 33,
      "overdue": true
    }
  ],
  "recent_activity_30d": [
    {
      "id": "audit_aaa",
      "action": "DATA_EXPORTED",
      "actor_email": "marie@acme.fr",
      "target_label": "user:user_123",
      "occurred_at": "2026-05-23T14:22:00.000Z",
      "severity": "INFO"
    }
  ],
  "rgpd_awareness": {
    "season_slug": "dpo-quotidien",
    "module_completion_rate": 0.78,
    "users_with_certificate": 12
  },
  "links": {
    "trust_center": "https://humanix-academie.fr/securite",
    "confidentiality_policy": "https://humanix-academie.fr/confidentialite",
    "dpa_template": "https://humanix-academie.fr/securite#dpa",
    "admin_dpo_dashboard": "https://humanix-academie.fr/admin/dpo"
  }
}

Stabilité du schéma : on ne renomme jamais un champ. Les évolutions se font uniquement par ajout de nouveaux champs (rétrocompatible). Le champ schema_version change uniquement si un breaking change est inévitable.

🎯 Outils Privacy compatibles