Skip to app details
Back to app library
APPNEURAL APP FAMILYIdentity & Security

Compliance

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.

01 / OVERVIEW

See where it fits in your day.

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.

A LOOK INSIDEExample layout · sample content
Data requests
ReferenceIllustrative configuration
01DR-2026-0001Example
02DR-2026-0002Example
03DR-2026-0003Example
02 / CAPABILITIES

Built around the work you do.

What Compliance does for you.

01

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.

02

Holds and discovery

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.

03

Requests and registers

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.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Compliance. What you can do depends on your access in the app.

01

Switch on

Turn archiving on for the domain and wait for the first sync.

02

Set rules

Preview and enable retention rules; place holds for matters.

03

Answer requests

Work the requests list and registers from the home page.

YOUR NEXT MOVE

Make Compliance part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE1 items
P2VERIFIEDPUBLISHED
Overview

Purpose and boundaries

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.

Records governance for a connected domain: an archive of workspace app items, retention rules with a preview, legal holds and matters, audited eDiscovery search with signed exports, data requests with a public form and due dates, and policy, processing and incident registers.

Cookie banners belong to Consents; sign-in belongs to Auth; legal advice stays with the business's own advisers.

Priority
P2
Portfolio
Identity & Security
Capability
Identity & Security
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-18 14:03:15
Semantic inventory

Every number says what it counts

1Catalog itemstrackedEntityCount · catalog-api:live
Production-ready gate

Governance evidence required

5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
MissingGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

compliance schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

compliance.appneurox.com DEPLOYED

compliance.appneurox.com

Worker
compliance-catalog
Health
HEALTHY
Last deployment
2026-11-18 14:03:15
DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

APPNEURAL-Catalogs/compliance-catalogLOCAL · NOT CONFIGURED

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

No health checks have been recorded.
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

No synchronization run has completed yet. The scheduled Worker records missing credentials as Not configured, never as success.

Drift findings

No drift has been recorded.
Evidence & history

Trust record

Verification is verified. Run verification to store check-level evidence, confidence, expiry and remediation.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app