Security & Privacy Notes

LLM Cost Optimizer & Document Anonymizer — Architecture, logging, and privacy practices.

1. Data flow

All processing occurs locally or in your VPC. We do not proxy LLM traffic.

mermaid
flowchart LR
  A[Client App] --> B[LLM Gateway / This API]
  B -->|Anonymize| C[(Text Anonymizer)]
  B -->|Optimize| D[(Model Selector)]
  D --> E{{Provider Price Table}}
  C --> B
  B --> F[(Your LLM Provider)]
  subgraph Your Environment
  B
  C
  D
  E
  end

2. Logging

• No raw PII in logs. Anonymization logs include only counts per PII type.
• Optimization logs include chosen model and cost estimate, not the prompt/body.
• Optional telemetry can be disabled via config/env.

3. Configuration hardening

• Run API behind your gateway; restrict egress to approved LLM providers.
• Keep the provider price table updated; warn if older than 30 days.
• Use deterministic replacement tokens for auditability.

4. Compliance

The tool processes data locally in your environment, giving you full control over compliance requirements. We can provide guidance on GDPR, CCPA, and other privacy regulations upon request.

5. Incident response

Contact us at security@rondanini.net. We will notify affected customers without undue delay if we become aware of a breach affecting account or licensing data.