Update to Praxikon

{
  "canonical_app_id": "asdk_app_6ad23f35e2ec81918cdb84407ab61063",
  "connector_id": "asdk_app_6ad23f35e2ec81918cdb84407ab61063",
  "created_at": "2026-10-16T16:09:04.832525Z",
  "discoverability": "LISTED",
  "id": "plugin_asdk_app_6ad23f35e2ec81918cdb84407ab61063",
  "is_template": false,
  "is_template_instance": false,
  "is_v2_template": false,
  "name": "praxikon",
  "release": {
    "app_ids": [
      "asdk_app_6ad23f35e2ec81918cdb84407ab61063"
    ],
    "app_manifest": {
      "apps": {
        "praxikon": {
          "id": "asdk_app_6ad23f35e2ec81918cdb84407ab61063",
          "required": true
        }
      }
    },
    "app_templates": [],
    "description": "EU AI Act and GDPR checks with sources, through the online Praxikon connector.",
    "display_name": "Praxikon",
    "id": "pluginrel_ade3334c4340819183ad68061ec312c5",
    "interface": {
      "brand_color": "#1B3354",
      "capabilities": [],
      "category": "Business & Operations",
      "composer_icon_dark_url": null,
      "composer_icon_url": "https://files.openai.com/content?id=file_0000000087f081f49e07d824195716fb",
      "default_prompt": "Is our AI hiring tool high risk under the EU AI Act?",
      "default_prompts": [
        "Is our AI hiring tool high risk under the EU AI Act?",
        "Do we need a DPIA for this AI use case?",
        "Who supervises the AI Act in the Netherlands?"
      ],
      "developer_name": "Praxikon",
      "logo_url": "https://files.openai.com/content?id=file_00000000f48c81f4b75d47f4a5538251",
      "logo_url_dark": null,
      "long_description": "Praxikon checks a concrete use of AI or personal data against the EU AI Act and the GDPR, and shows where every answer comes from.\n\nWhat you can ask:\n- How the EU AI Act classifies a specific AI system: prohibited practice screening, Annex III high risk, transparency under Article 50, the fundamental rights impact assessment (FRIA) and the general purpose model route.\n- Which obligations apply to your role, provider or deployer, and from when.\n- The legal path behind one obligation: the condition, the exception, the source and the exact locator.\n- Whether a data protection impact assessment (DPIA) is required under Article 35 GDPR and the list of the Dutch Data Protection Authority, and whether a FRIA comes into play.\n- The DPIA intake as a Word file to work on: the four parts of Article 35(7) GDPR with the seventeen points of the Dutch government model DPIA, and the FRIA draft where it applies.\n- A short general question about the EU AI Act or the GDPR, such as whether a customer service chatbot has to say that it is AI, answered from the published Praxikon answers with the articles and sources.\n- Who supervises the AI Act in a member state, how far the national implementing law has come, and dated enforcement signals.\n\nHow it works: the plugin calls a deterministic rules engine over the published Praxikon implementation graph of the EU AI Act and the published Praxikon answers. Nothing is generated by a language model on our side. The same answers always give the same outcome, every result carries the source and the locator it was read from, and a question it does not recognise gets no answer rather than a constructed one.\n\nWho it is for: data protection officers, privacy and AI governance professionals, lawyers and compliance teams, and anyone preparing an AI procurement, a DPIA or a FRIA in the European Union.\n\nPrivacy: no login and no account. Praxikon never sees the conversation. To improve its answers it keeps, for at most 12 months and without IP address, account, cookie or time of day, what a tool needs to work: the tool used and whether it worked, the kind of assistant and the language, the fixed-list choices (such as the case check answers), the outcome and, for the general question tool, the question itself when it passes a filter that drops anything that looks like a name, e-mail address, phone number or other number. Answers are not kept. Ask the assistant not to keep your question and nothing of that call is kept, apart from an anonymous daily count. The case check and the DPIA intake accept fixed answer codes only and refuse free text, so a case description, a name or an organisation name cannot reach them. The DPIA intake comes back as a link to the case check on the Praxikon site with the answers after the # sign, a part the browser does not send to the server, and the Word file is built in the user's own browser. The general question tool takes one question of at most 200 characters in general terms and refuses a question that looks like it contains personal data. Details: privacy statement, section 2.7.\n\nLimitations: Praxikon prepares, it does not advise. The output is not legal advice, and Praxikon is not a supervisory authority. The engine assesses what its questions cover; anything it did not assess is reported as not assessed, with the reason, and an unknown answer is never treated as no. The legal content covers the EU AI Act and the GDPR, with national supervision data per member state and the most detail for the Netherlands.",
      "plugin_category_id": "business & operations",
      "privacy_policy_url": "https://www.praxikon.com/en/legal/privacy",
      "screenshot_urls": [],
      "short_description": "EU AI Act and GDPR checks",
      "terms_of_service_url": "https://www.praxikon.com/en/legal/terms",
      "website_url": "https://www.praxikon.com/en/ai-assistant"
    },
    "keywords": [
      "eu-ai-act",
      "ai-act",
      "gdpr",
      "privacy",
      "data-protection",
      "dpia",
      "fria",
      "ai-governance",
      "compliance",
      "avg"
    ],
    "mcp_servers": [
      {
        "key": "praxikon",
        "metadata": {
          "headers": {},
          "type": "streamable-http",
          "url": "https://www.praxikon.com/api/mcp"
        }
      }
    ],
    "onboarding_skill_name": null,
    "requires_local_executor": false,
    "skills": [],
    "version": "1.0.2"
  },
  "scope": "GLOBAL",
  "share_url": "https://chatgpt.com/plugins/plugin_asdk_app_6ad23f35e2ec81918cdb84407ab61063?open_in_app",
  "status": "ENABLED"
}