openrouter-data-privacy

Implement data privacy controls for OpenRouter requests. Use when handling PII or meeting compliance requirements. Trigger with phrases like 'openrouter privacy', 'openrouter pii', 'openrouter gdpr', 'openrouter data protection'.

⭐878stars🔀101forks📁View on GitHub🕐Updated Jan 4, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill provides robust data privacy controls and PII (Personally Identifiable Information) detection for OpenRouter API requests. It acts as a security layer to ensure LLM interactions comply with global regulations like GDPR and CCPA by redacting sensitive information and enforcing data protection standards before data leaves your environment.

Use Cases

  • PII Redaction: Automatically identify and mask sensitive data such as names, emails, and financial details in prompts before they are sent to OpenRouter models.
  • Compliance Automation: Streamline the implementation of GDPR and data protection requirements for developers building AI-powered applications that handle user data.
  • Enterprise Data Guardrails: Establish secure patterns for corporate AI integrations, ensuring that internal sensitive information is filtered and handled according to organizational privacy policies.
  • Secure API Connectivity: Verify and monitor OpenRouter integrations to ensure that connectivity remains compliant with privacy-first architecture designs.
nameopenrouter-data-privacy
description|
allowed-toolsRead, Write, Edit, Grep
version1.0.0
licenseMIT
authorJeremy Longshore <jeremy@intentsolutions.io>

Openrouter Data Privacy

Overview

This skill covers PII detection, data redaction, and compliance considerations for OpenRouter integrations handling sensitive data.

Prerequisites

  • Understanding of applicable privacy regulations
  • Data classification requirements

Instructions

Follow these steps to implement this skill:

  1. Verify Prerequisites: Ensure all prerequisites listed above are met
  2. Review the Implementation: Study the code examples and patterns below
  3. Adapt to Your Environment: Modify configuration values for your setup
  4. Test the Integration: Run the verification steps to confirm functionality
  5. Monitor in Production: Set up appropriate logging and monitoring

Output

Successful execution produces:

  • Working OpenRouter integration
  • Verified API connectivity
  • Example responses demonstrating functionality

Error Handling

See {baseDir}/references/errors.md for comprehensive error handling.

Examples

See {baseDir}/references/examples.md for detailed examples.

Resources