_update-privacy-policy

Add or remove third-party subprocessors in a JSON-based RGPD registry.

34|6|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/flavien-ia/hypervibe-harness --skill update-privacy-policy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: _update-privacy-policy
Source: https://github.com/flavien-ia/hypervibe-harness/tree/main/skills/_update-privacy-policy
Command: npx skills add https://github.com/flavien-ia/hypervibe-harness --skill update-privacy-policy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill eliminates the manual, error-prone process of updating legal privacy policy registries when adding new third-party services to a project.

Core Features & Use Cases

  • Idempotent Registry Updates: Automatically adds or removes subprocessors from the project's RGPD registry without duplicating entries.
  • Centralized Compliance: Ensures that the subprocessor list remains consistent with the actual infrastructure services used in the application.
  • Use Case: When you add a new database or analytics service to your project, this skill automatically updates your privacy policy registry to reflect the new data processor, ensuring your legal documentation stays current.

Quick Start

Use the update privacy policy skill to add the neon database service to the project registry.

Frequently Asked Questions about _update-privacy-policy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate RGPD subprocessor registry updates when adding new infrastructure services?

You can automate RGPD subprocessor registry updates by running scripts that add or remove third-party services from your JSON-based privacy policy registry. This ensures your legal documentation stays current without manual data entry.

What is a subprocessor registry and when do I need to update it for RGPD compliance?

A subprocessor registry is a legal record of third-party services processing user data within your project. You need to update it for RGPD compliance whenever you integrate new databases, auth providers, or analytics services into your application infrastructure.

Do I need Node.js to manage a privacy policy registry for third-party services?

Yes, you need Node.js installed to execute the internal scripts that maintain the subprocessor registry. The scripts operate on JSON data files and maintain the integrity of the registry alongside its TypeScript wrapper.

How do I add a new database service to my project's privacy policy registry?

To add a new database service, you execute the registry update skill with the service name. The script performs idempotent updates, automatically adding the new subprocessor to your RGPD registry without duplicating existing entries.

What is the best way to keep legal privacy policy documentation consistent with actual infrastructure services?

The best way to keep privacy policy documentation consistent is to automate subprocessor registration using JSON-based data files. This centralized compliance approach ensures your legal records accurately reflect the infrastructure services used.

Can I remove a subprocessor from the RGPD registry without breaking existing legal compliance entries?

Yes, you can remove a subprocessor from the RGPD registry using automated scripts that safely delete entries while maintaining the integrity of the remaining privacy policy data. The process ensures legal compliance across your infrastructure integrations.