Skip to content

Redact secrets and enforce telemetry retention (#35) - #58

Draft
4nass wants to merge 2 commits into
mainfrom
feature/security-redaction-retention
Draft

4nass wants to merge 2 commits into
mainfrom
feature/security-redaction-retention

Conversation

@4nass

@4nass 4nass commented Aug 12, 2026

Copy link
Copy Markdown
Owner

Summary

  • add deterministic built-in and project-configured secret redaction
  • redact requests, provider results, diagnostics, job events, approvals and outbound-ready summaries before persistence
  • add configurable retention policy and auditable tombstone deletion by run/session/project
  • enforce owner-only permissions on SQLite stores and provide secure artifact-directory helper
  • document backup handling and remaining artifact-store scope (Securely ingest mobile attachments, logs, screenshots and voice transcripts #38)

Closes #35.

Validation

  • /home/anass/.local/bin/uv run pytest -q
  • 797 passed, 2 pre-existing collection warnings

@4nass

4nass commented Aug 15, 2026

Copy link
Copy Markdown
Owner Author

Status

Delivered: deterministic redaction, configurable retention, auditable tombstone deletion, owner-only SQLite permissions, artifact helpers, tests and documentation.

Residual: storage/encryption and external-backup scope remains in #38; remote readiness evidence remains in #49.

Closes #35 is present in the PR description.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Redact secrets and define telemetry retention and deletion

1 participant