Refresh HiveGrid Cloud reference snapshot
This commit is contained in:
1 parent
5e99e14772
commit
7f88026f79
5955 files changed
+1177325
-188362
No files matched your search
@@ -2,7 +2,10 @@
|
||||
|
||||
## Scope
|
||||
|
||||
This inventory documents the current data-protection-relevant surfaces in the boilerplate for follow-up work in Compliance Retention. It is a repository evidence map, not legal advice and not an implemented retention schedule. Entries are grounded in the current security and production evidence boundaries from `docs/security.md` and `docs/production-checklist.md`, the Compliance Retention baseline inventory report, and Prisma schema surfaces under `prisma/schema`.
|
||||
This inventory documents the current data-protection-relevant surfaces in HiveGrid for follow-up work
|
||||
in Compliance Retention. It is a repository evidence map, not legal advice and not an implemented
|
||||
retention schedule. Entries are grounded in `docs/security.md`, `docs/staging-live-uat.md` and the
|
||||
Prisma schema surfaces under `prisma/schema`.
|
||||
|
||||
The inventory covers user, tenant, authentication, API, file, entity-row, import/export, notification, billing, audit, email, analytics, worker, and optional plugin-candidate surfaces that can contain personal data or personal-data-adjacent operational evidence. Unknown retention periods are listed as implementation gaps for later Compliance Retention slices rather than invented durations.
|
||||
|
||||
@@ -81,7 +84,9 @@ Repository-level retention defaults now live in [`docs/data-retention.md`](../da
|
||||
|
||||
## Operational redaction rules
|
||||
|
||||
- Follow `docs/security.md` and `docs/production-checklist.md`: automatic evidence is local/static unless a human explicitly approves a runtime check; browser, provider-console, Docker, registry, Coolify, production traffic, Playwright, and Cypress activities remain manual records.
|
||||
- Follow `docs/security.md` and `docs/staging-live-uat.md`: automatic evidence is local/static unless
|
||||
a human explicitly approves a runtime check; browser, provider-console and production activities
|
||||
remain manual records outside the configured deploy workflow.
|
||||
- Safe evidence includes model or surface labels, route or endpoint labels, status, stable error code, request ID, job ID, queue name, counts, command name, exit code, redacted diagnostic code, and pass/fail labels.
|
||||
- Unsafe evidence includes secrets, bearer tokens, cookies, API keys, key hashes/prefixes/last-four, raw authorization headers, tenant identifiers, customer domains, customer names, email addresses, phone numbers, IP addresses, object keys, signed URLs, webhook signatures, provider payloads, queue payloads, raw logs, screenshots with personal data, import/export contents, and email/message bodies.
|
||||
- Examples in compliance docs must stay placeholder-shaped and must not include realistic personal data, tenant slugs, domains, UUID-like deploy endpoints, provider IDs, or secret-shaped strings.
|
||||
|
||||
Reference in new issue
Block a user