Archive and retention
Switch archiving on per domain for the apps that expose a workspace feed; rules name the apps, kinds and age, can only be switched on after a preview, and purge only this copy.
Records you can keep, hold, search and answer for
Keep an archive of your apps' records, apply retention rules and legal holds, search them with an audit trail, and answer data requests on time.
The archive reads the workspace feed of Notes, Writer, Sheets, Slides, Tables, Whiteboards, Diagrams, Calendar, Videos, Research, Learning and Brand DNA, and of Events, Webinars, Inventory, Interfaces, Code and Payroll where they expose it, through service bindings and the workspace key; it runs only for domains whose owner switched archiving on, keeps deleted items as tombstones, and uses full-text search. Retention rules name apps, kinds, an owner or keyword and an age, can be switched on only after a preview from the last 24 hours, purge only Compliance's copy, never held items, and log every purge. Legal holds cover apps, custodians, dates and keywords, are re-applied after every sync, are released with a reason, and send hold notices with acknowledgement. eDiscovery is open only to the owner, the admin passcode and the Compliance officer role: search with filters, matters with snapshots hashed with SHA-256, tags, notes, NDJSON export with a signed manifest, and an audit log that refuses UPDATE and DELETE and chains each row to the previous one. Data requests have a public form with email code, honeypot and rate limits, a due date from a setting (default 30 days), assignment, letter templates, reminders, closure with outcome and a status page without names or staff notes. Registers hold policies with versions and attestations, a processing register and an incident log with a reporting window; wording is records and reminders, not legal advice. Optional Claude features write a cited matter summary, a response letter and a request classification. Retention counts from first archived, items saved to a matter are not purged by rules, and a hold cannot stop edits in the source apps. API /api/v1/holds, /api/v1/requests and a policy workspace feed; webhooks request.created, request.closed, hold.created, hold.released and rule.purged.
What Compliance does for you.
Switch archiving on per domain for the apps that expose a workspace feed; rules name the apps, kinds and age, can only be switched on after a preview, and purge only this copy.
Legal holds by app, custodian, dates and keywords; matters with tagged snapshots; owner and Compliance officer search with every action in a tamper-evident log; NDJSON export with a signed manifest.
Public data request form, status link, letter templates and reminders; policies with versions and attestations, a processing register and an incident log with a reporting window.
A suggested path for Compliance. What you can do depends on your access in the app.
Turn archiving on for the domain and wait for the first sync.
Preview and enable retention rules; place holds for matters.
Work the requests list and registers from the home page.
Live host, inventory, governance, health checks, verification, dependencies and history.
The archive reads the workspace feed of Notes, Writer, Sheets, Slides, Tables, Whiteboards, Diagrams, Calendar, Videos, Research, Learning and Brand DNA, and of Events, Webinars, Inventory, Interfaces, Code and Payroll where they expose it, through service bindings and the workspace key; it runs only for domains whose owner switched archiving on, keeps deleted items as tombstones, and uses full-text search. Retention rules name apps, kinds, an owner or keyword and an age, can be switched on only after a preview from the last 24 hours, purge only Compliance's copy, never held items, and log every purge. Legal holds cover apps, custodians, dates and keywords, are re-applied after every sync, are released with a reason, and send hold notices with acknowledgement. eDiscovery is open only to the owner, the admin passcode and the Compliance officer role: search with filters, matters with snapshots hashed with SHA-256, tags, notes, NDJSON export with a signed manifest, and an audit log that refuses UPDATE and DELETE and chains each row to the previous one. Data requests have a public form with email code, honeypot and rate limits, a due date from a setting (default 30 days), assignment, letter templates, reminders, closure with outcome and a status page without names or staff notes. Registers hold policies with versions and attestations, a processing register and an incident log with a reporting window; wording is records and reminders, not legal advice. Optional Claude features write a cited matter summary, a response letter and a request classification. Retention counts from first archived, items saved to a matter are not purged by rules, and a hold cannot stop edits in the source apps. API /api/v1/holds, /api/v1/requests and a policy workspace feed; webhooks request.created, request.closed, hold.created, hold.released and rule.purged.
Cookie banners belong to Consents; sign-in belongs to Auth; legal advice stays with the business's own advisers.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
compliances.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.