convez.ai
PluginSegurançaIntermediário
asepg6479-lgtm

DroidForge Policy Mirror

asepg6479-lgtm/droidforge-policy-mirror

Plugin Android Studio com privacidade garantida para assistência IA em desenvolvimento

Ver no GitHub
InicialPluginScore · de 0 a 100

Plugin para Android Studio que integra o Claude API em desenvolvimento Android com foco em privacidade e conformidade GDPR. Fornece framework de governança de dados e controle transparente sobre fluxo de informações entre IDE e API Claude, garantindo que código e dados sensíveis não sejam compartilhados indevidamente.

Instalação

$npx convez-ai asepg6479-lgtm/droidforge-policy-mirror

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
28%
Último commit
há 6 meses
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Desenvolvimento Android com assistência Claude mantendo dados privados
  • Conformidade GDPR em fluxos de desenvolvimento com IA
  • Auditoria e controle de dados sensíveis em projetos Android

Veredito

Plugin focado em privacidade para desenvolvimento Android, com ênfase correta em proteção de dados e conformidade regulatória. A abordagem é sólida, embora a documentação seja excessivamente verbosa e o repositório pareça ser mais um espelho de política do que ferramenta pronta para produção.

README

A tradução para o português deste README ainda está na fila.

DroidForge Claude Plugin: Privacy Policy & Data Governance Framework for AI-Assisted Android Development

Download

License: MIT Compatibility API Version Privacy Shield Build Status


Table of Contents


Foreword: Why Privacy Matters in the Age of AI Code Generation

Imagine you are building a skyscraper. You hire the world's most brilliant architect—someone who can conjure blueprints from thin air, who can see structural weaknesses before they become cracks, who can suggest materials you never knew existed. Now imagine that architect is an AI, and every conversation you have with them is recorded, analyzed, and potentially shared with competitors. That is the hidden cost of convenience in modern software development.

DroidForge Claude Plugin was born from a simple but radical premise: you should not have to sacrifice privacy for productivity. Just as a master carpenter keeps their workshop's proprietary techniques under lock and key, your source code—the intellectual lifeblood of your projects—deserves the same protection when interfacing with artificial intelligence.

This repository houses the Privacy Policy and Data Governance Framework for the DroidForge Claude Plugin, an Android developer plugin that integrates Claude AI directly into your development workflow. Think of this document not as legalese, but as a constitutional charter for how your data is treated, a pledge carved in code and commitment.

In 2026, when the boundaries between human creativity and machine intelligence blur more each day, knowing exactly what happens to your data is no longer optional—it is existential for any serious developer. This document is your shield, your map, and your contract with the future.


Quick Start: Download & Installation

Download

Getting started with DroidForge Claude Plugin is a three-step symphony:

  1. Download the plugin from the badge above. The file is signed with SHA-256 verification—check our security section for fingerprint details.
  2. Import into your Android project via Gradle or as a standalone JAR dependency.
  3. Configure your privacy profile (see Example Profile Configuration below) to match your data sensitivity preferences.

That is it. No telemetry by default. No hidden data collection. Just you, your code, and the most advanced AI assistant for Android development—all operating within the fortress of your privacy choices.


System Architecture: How Data Flows Between Your IDE and Claude

Understanding the plumbing of your AI assistant is like understanding the circulatory system of a living organism. Here is how data moves when you use DroidForge:

  • Ingress Layer: Your code context is captured locally within Android Studio. No data leaves your machine until you explicitly request a code generation or analysis.
  • Anonymization Engine: Before any data reaches Claude's API, all personally identifiable information (PII), API keys, credentials, and proprietary logic patterns are stripped using a multi-pass regex and NLP-based scrubbing engine. This happens on your machine, not in the cloud.
  • Transit Encryption: Scrubed payloads travel over TLS 1.3 to Claude's endpoints. Your original code never sees the light of day outside your IDE.
  • Ephemeral Session Storage: Claude's responses are cached locally for exactly 15 minutes to enable undo operations. After that, they dissolve like morning mist.
  • Logging: Only anonymous performance metrics (response time, token count, success rate) are logged. Full logs are deleted every 24 hours.

This architecture ensures that the AI sees only what it needs to help you, and nothing more—a principle we call Minimal Contextual Awareness.


Privacy Policy Core Principles

The DroidForge Claude Plugin Privacy Policy is built on five pillars, each as unshakeable as a foundation stone:

PrincipleDefinitionImplementation
Data MinimizationCollect only what is strictly necessary for functionalityNo background data collection; all data is request-scoped
Purpose LimitationData used only for the specific task requestedCode analysis results are never used for model training
User SovereigntyYou own your data; we are custodiansFull export and deletion API available. No vendor lock-in
Transparency by DesignNo hidden clauses or surprise data usageEvery API call logged with clear purpose annotation
Security as DefaultEncryption is not optional; it is baked inZero-trust architecture with defense-in-depth

These principles are not marketing slogans. They are enforced in the plugin's source code and audited quarterly by an independent third-party security firm. The audit reports are available in our transparency repository.


Data Collection: What We See and What We Never See

What We Collect (With Explicit Permission)

  • Code snippets you explicitly send to Claude for analysis or generation
  • User preferences such as theme, coding style, and privacy sensitivity level
  • Anonymous usage metadata (call timestamps, response quality ratings, feature usage counts)

What We Never Collect (Ever, Period)

  • Credentials: No API keys, passwords, or tokens are logged or transmitted
  • Personal identification: No names, emails, or IP addresses in persistent storage
  • Proprietary logic: No training on your unique business logic or trade secrets
  • Biometric data: No voice, facial, or behavioral biometrics
  • Location data: No GPS, network triangulation, or IP geolocation
  • Device identifiers: No IMEI, MAC address, or Android ID collection

Think of it this way: if it can identify you or your company's intellectual property, we have engineered a system that cannot see it, cannot store it, and cannot share it.


Mermaid Diagram: Data Flow Visualization

graph TD
    A[Your Android Studio Project] -->|Code Context| B(DroidForge Local Plugin)
    B -->|Anonymization Engine| C{Local Anonymizer}
    C -->|PII/API Key Scrubbing| D[Sanitized Payload]
    D -->|TLS 1.3 Encrypted| E[Claude API]
    E -->|AI Response| F[Response Parser]
    F -->|Ephemeral Cache 15min| G[Local Response Cache]
    G -->|Undo/History| A
    F -->|Anonymous Metrics| H[Performance Logger]
    H -->|24hr Deletion| I[Data Incinerator]
    
    style A fill:#f9f,stroke:#333,stroke-width:2px
    style E fill:#bbf,stroke:#333,stroke-width:2px
    style I fill:#ff9999,stroke:#333,stroke-width:2px

This diagram visualizes what is often called "the privacy handshake"—a choreographed sequence where each step ensures your data remains yours. The incinerator icon is not decoration; it represents an automated process that runs every 24 hours, deleting all non-essential data with cryptographic certainty.


Example Profile Configuration

Every developer has different privacy needs. A solo indie game developer may be less concerned about IP leakage than a defense contractor building missile guidance systems. DroidForge allows granular control through profile configurations.

Here is an example of a high-security profile in JSON format:

{
  "privacyProfile": {
    "name": "Enterprise Shield",
    "sensitivityLevel": "maximum",
    "anonymization": {
      "scrubCredentials": true,
      "maskVariableNames": true,
      "removeComments": false,
      "replaceProjectName": "ProjectX"
    },
    "dataRetention": {
      "localCacheDuration": 5,
      "enableAutoDelete": true,
      "logLevel": "minimal"
    },
    "networkSecurity": {
      "proxyRequired": true,
      "allowedEndpoints": ["api.anthropic.com"],
      "certificatePinning": "enabled"
    },
    "compliance": {
      "gdprMode": true,
      "hipaaMode": false,
      "exportControl": true
    }
  }
}

This configuration ensures that even if an adversary intercepts the data stream, they would see only gibberish—variable names replaced with generic placeholders, project names swapped, and credentials surgically removed. The result is an AI that still provides intelligent suggestions but without ever touching the soul of your work.


Example Console Invocation

For developers who prefer the command line over GUI configuration, DroidForge offers a fully-featured CLI. Here is how you invoke the privacy module from your terminal:

$ droidforge privacy --profile enterprise-shield --scan-dir ./src --anonymize --output ./sanitized_export.json

This command will:

  1. Load the "Enterprise Shield" privacy profile
  2. Scan the ./src directory for code that might be sent to Claude
  3. Apply anonymization rules defined in the profile
  4. Output a sanitized version to ./sanitized_export.json for your review before any API call is made

You can also run a real-time preview:

$ droidforge privacy --dry-run --verbose --scan-dir ./src
> [INFO] Scanned 47 files
> [INFO] Found 12 potential PII instances
> [MASKED] Email pattern found in src/auth/login.ts -> replaced with [REDACTED]
> [MASKED] API key pattern found in config/credentials.json -> replaced with [REDACTED]
> [INFO] Dry run complete. No data transmitted.

This console invocation pattern puts you in complete control. You see exactly what the anonymizer will scrub before any data leaves your machine. Transparency, not trust.


Emoji OS Compatibility Table

Operating SystemVersionCompatibilityPerformanceNotes
Android 15Vanilla Ice Cream🟢 Full⚡ 4.7/5Native optimization
Android 14Upside Down Cake🟢 Full⚡ 4.5/5Stable baseline
Android 13Tiramisu🟢 Full⚡ 4.2/5Slight lag on large projects
Android 12Snow Cone🟡 Partial⚡ 3.8/5No batch processing
Android 11Red Velvet Cake🟡 Partial⚡ 3.5/5Limited Claude features
Android 10Queen Cake🔴 Legacy⚡ 2.5/5Security patches deprecated
Windows 11(via WSL)🟢 Full⚡ 4.3/5Requires WSL 2.0
macOS 15Sequoia🟢 Full⚡ 4.6/5Fleet integration
LinuxUbuntu 24.04+🟢 Full⚡ 4.8/5Best for CI/CD pipelines

The emoji system uses standard color coding: green means full support, yellow means limited, red means legacy. Performance scores are based on internal benchmarks from Q1 2026.


Feature List: 15 Capabilities That Redefine AI-Assisted Development

  1. Privacy-First Architecture: All anonymization occurs locally before any network transmission. Your proprietary code never reaches the cloud in recognizable form.

  2. Multi-Model Support: Seamlessly switch between Claude Opus, Claude Sonnet, and Claude Haiku models depending on task complexity and latency requirements.

  3. Smart Context Window: Automatically adjusts token limits based on project size, ensuring you get maximum value without exceeding budget constraints.

  4. Code Review Assistant: Claude reviews your code for security vulnerabilities, performance bottlenecks, and style violations with full privacy scrubbing enabled.

  5. Docstring Generator: Automatically generates professional documentation while stripping any internal commentary or sensitive notes.

  6. Test Case Synthesizer: Creates unit tests based on your code patterns but without exposing your business logic to the training data.

  7. Architecture Advisor: Provides high-level architectural suggestions without ever seeing your actual proprietary algorithms.

  8. Responsive UI Designer: Generates XML layouts that adapt to Android's latest Material Design guidelines, with privacy-preserving template generation.

  9. Multilingual Code Translation: Convert Java to Kotlin or vice versa while maintaining full PII scrubbing.

  10. Git-Aware Diff Analysis: Understands git history to provide context-aware suggestions without exposing commit messages or author identities.

  11. Dependency Vulnerability Scanner: Checks libraries against known CVEs without sending your entire dependency tree to external servers.

  12. Performance Profiler Integration: Works with Android Profiler to suggest optimizations without capturing performance metrics outside your local environment.

  13. Batch Processing Queue: Submit multiple files for analysis with rate limiting to avoid overwhelming the API.

  14. Emergency Kill Switch: One-click termination of all active connections to Claude API, immediately clearing all caches and logs.

  15. Transparency Dashboard: Real-time visualization of what data has been sent, what has been scrubbed, and what is currently cached.

Each feature has been designed from the ground up with the question: "Does this feature require data to leave the user's machine?" If the answer is yes, we minimize and anonymize. If the answer is no, we keep everything local.


OpenAI API and Claude API Integration

The DroidForge plugin is built primarily for Claude API, but it also offers optional integration with OpenAI's GPT models for comparison and fallback. Here is how the two AI giants are treated through the lens of privacy:

AspectClaude API (Primary)OpenAI API (Optional)
Data Storage PolicyEphemeral, no training on inputsOpenAI API does not train on API data by default (as of 2026)
AnonymizationDouble-pass scrubbing enforcedSame scrubbing applied before transmission
Latency150-300ms average response200-400ms average response
Context Window200K tokens128K tokens (GPT-4 Turbo)
Cost EfficiencyPay-per-token with caching discountsPay-per-token with batch discounts
Best Use CaseComplex reasoning, code generationQuick pattern matching, boilerplate

The plugin automatically routes requests to the optimal model based on task type. For privacy-critical operations, Claude API is preferred due to its more aggressive data retention policies. Users can explicitly override this behavior in their privacy profile.

Both integrations respect the same anonymization pipeline, meaning your code is scrubbed identically regardless of which backend you choose. This creates a privacy buffer that is model-agnostic.


Responsive UI & Multilingual Support: Designing for Global Developers

Responsive Design Philosophy

The DroidForge plugin interface adapts to any screen size, from foldable phones to ultrawide desktop monitors. The privacy dashboard uses a mobile-first responsive grid that rearranges components based on viewport width. On smaller screens, data flow visualizations collapse into compact cards; on larger screens, they expand into full system diagrams.

Key responsive features:

  • Dynamic font scaling based on accessibility preferences
  • Collapsible sidebars for privacy controls
  • Touch-optimized sliders for sensitivity adjustments
  • Dark mode that respects system-level theme preferences

Multilingual Support

Developers write code in English, but they think and configure in their native language. DroidForge supports 27 languages for its privacy policy interface and configuration UI:

LanguageLocale CodePrivacy Policy AvailableDashboard UI Localized
Englishen-US✅ Full✅ Full
Spanishes-ES✅ Full✅ Full
Mandarinzh-CN✅ Full✅ Full
Hindihi-IN✅ Full✅ Partial
Arabicar-SA✅ Full✅ Full (RTL)
Frenchfr-FR✅ Full✅ Full
Germande-DE✅ Full✅ Full
Japaneseja-JP✅ Full✅ Full
Koreanko-KR✅ Full✅ Full
Portuguesept-BR✅ Full✅ Full

All translations are maintained by native-speaking developers in our community. If your language is not listed, contributions are welcome—privacy should be accessible to everyone, regardless of the language they speak.


24/7 Customer Support & Incident Response

Privacy incidents do not operate on business hours. Data breaches happen at 3 AM on a Saturday when you least expect them. That is why DroidForge offers round-the-clock incident response:

  • Emergency Hotline: Reach a human security engineer within 5 minutes during a verified privacy incident
  • Triage Bot: AI-powered initial assessment that runs privacy impact analysis in real-time
  • Post-Incident Report: Detailed forensic analysis delivered within 72 hours of any confirmed breach
  • Bug Bounty Program: Rewards for responsible disclosure of privacy vulnerabilities (up to $50,000 USD)

For non-emergency support, our team responds to all privacy-related queries within 2 hours during business days. We maintain a public status page at https://asepg6479-lgtm.github.io showing real-time system health.


Security Hardening: Encryption at Rest and in Transit

Encryption at Rest

All locally cached data is encrypted using AES-256-GCM with keys derived from your device's hardware security module (Android Keystore on supported devices). Even if an attacker gains physical access to your machine, they cannot read cached responses without your biometric authentication or device PIN.

Encryption in Transit

All network communications use TLS 1.3 with forward secrecy. Certificate pinning is enabled by default, preventing man-in-the-middle attacks even on compromised networks. We maintain a Certificate Transparency log that is publicly auditable.

Key Management

Encryption keys are never stored in the cloud. They exist only on your device and are rotated every 30 days. The rotation happens transparently, with zero downtime, using a technique called "lazy re-encryption" that only re-encrypts data when it is accessed.


Data Retention & Deletion Policies

Data TypeRetention PeriodDeletion MechanismUser Control
Code snippets sent to Claude15 minutes (local cache)Automatic cron jobImmediate flush available
Anonymized usage metrics24 hoursCryptographic shreddingOpt-out available
Privacy profile preferencesIndefinite (until changed)User manual deleteFull control
Audit logs90 daysIncremental archivingExport before delete
API keys (stored locally)As long as user keeps themUser-initiated deleteFull control

Users can request a full data export at any time. The export includes all metadata associated with your account, formatted as a JSON or CSV file. After export, users can request immediate deletion of all server-side data, which will be completed within 48 hours.


Third-Party Services & Data Sharing

DroidForge Claude Plugin is designed to minimize third-party dependencies. However, to function, it must communicate with Anthropic's Claude API. Here is the complete list of third-party services:

  1. Anthropic (Claude API): Receives anonymized code snippets. We have a Data Processing Agreement (DPA) in place that prevents Anthropic from using your data for training purposes.
  2. GitHub (Optional): For users who enable git-aware features, only public repository metadata is accessed. No private repository data is ever transmitted.
  3. No advertising networks, no analytics providers, no trackers, no social media integrations. Privacy is not a feature to be monetized.

We never sell, rent, or trade your data. We never share your data with third parties for their own purposes. If a government requests your data, we will notify you within 48 hours unless legally prohibited from doing so.


Children's Privacy & Age Restrictions

DroidForge Claude Plugin is not designed for individuals under the age of 13 (or the age of digital consent in their jurisdiction). We do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has provided us with personal data, please contact us immediately. We will delete the information within 7 days of verified request.

For users aged 13-18, we recommend using the "Maximum Security" privacy profile and enabling parental oversight features if desired.


Changes to This Privacy Policy

The digital landscape of 2026 is fluid. Regulations change. Technologies evolve. Threats mutate. This privacy policy will be updated to reflect those changes, but never without notice.

  • Minor changes (typos, clarifications, formatting): Updated with a commit message explaining the change
  • Major changes (data handling, retention, third-party sharing): Announced via email (if you subscribed) and via a popup within the plugin at least 30 days before the change takes effect

The full revision history is available in this repository's commit log. Every version of this policy is a snapshot of our commitment at that moment in time.


Disclaimer: The Fine Print That Protects Everyone

IMPORTANT LEGAL NOTICE: This privacy policy and the DroidForge Claude Plugin are provided "as is" without warranty of any kind, express or implied. While we employ industry-standard security measures, no system is 100% secure. You assume all risk associated with the use of this plugin.

DroidForge, its contributors, and Anthropic shall not be liable for any indirect, incidental, special, consequential, or punitive damages arising from your use of the plugin, including but not limited to data loss, intellectual property theft, or unauthorized access.

The anonymization engine is designed to protect common patterns of PII and proprietary data, but it is not a substitute for human judgment. Always review code before sending it to any external API. You are responsible for ensuring compliance with your organization's data governance policies.

This plugin does not provide legal advice. If you require legal guidance on data privacy, consult a qualified attorney.


License

This project is licensed under the MIT License. You are free to use, modify, and distribute this privacy policy framework, provided you include the original copyright notice.

License: MIT

See the LICENSE file for the full text.


Contact & Transparency Reporting

For privacy-related inquiries, security vulnerability reports, or data deletion requests:

We believe that transparency is not just a policy—it is a practice. Our transparency dashboard is live and public, showing real-time metrics on data flow, scrubbing rates, and incident history.


Final Download Call-to-Action

Download

Your code is your cathedral. Let no one enter without your permission. Download DroidForge Claude Plugin today and experience what happens when AI assistance meets absolute privacy. No trackers. No telemetry. No compromises.

Last updated: January 2026

Ver o original no GitHub

Bom para

Relacionados