Skip to content

Retention

State what expires, what persists, and what still requires an operator.

Netrix documents implemented retention rather than presenting a policy as if code already enforces it. Report links expire, some transient platform records age out, and account deletion cascades through tenant data, while several audit, results-bucket, log, and connector cleanup paths remain long-lived or operationally managed.

Request access Explore the platform
Operating ledgerEXAMPLE / TRACE
Example evidence, review, and verification states
StateEvidenceOwner
ObservedRetentionPage-level source retainedAudit
ReviewedDecision recordedScope and value inspectedHuman
VerifiedPublic response readOutcome has separate proofSystem
Synthetic product illustration. It demonstrates state meaning and does not represent a customer result.

What the workflow must answer

Keep the operating question attached to the evidence.

01

Time-bounded access

Report links default to a finite expiry and invitation or pairing tokens have explicit lifetimes.

02

Long-lived operating evidence

Audit, task, deployment, metric, review, and usage records currently remain until their owning records are deleted.

03

Customer-side persistence

WordPress content changes and connector history may survive Netrix disconnect according to the site’s own ownership and uninstall behavior.

Control review

Translate the promise into something an operator can inspect.

Review the trust center
01Time-bounded access
Report links default to a finite expiry and invitation or pairing tokens have explicit lifetimes.
02Long-lived operating evidence
Audit, task, deployment, metric, review, and usage records currently remain until their owning records are deleted.
03Customer-side persistence
WordPress content changes and connector history may survive Netrix disconnect according to the site’s own ownership and uninstall behavior.

An accountable trail

A useful state says exactly what happened.

  1. 01Observed

    The source evidence is recorded.

  2. 02Interpreted

    The condition is reviewed in context.

  3. 03Decided

    An authorized person chooses the next state.

  4. 04Applied

    A supported destination accepts the action.

  5. 05Verified

    The public result is read independently.

  6. 06Reported

    The claim matches the available evidence.

Product truth

Automation prepares work. Authority stays visible.

  1. 01
    No hidden autopilot

    Netrix does not publish AI drafts or apply SEO changes without an explicit authorized action.

  2. 02
    No optimistic verification

    An accepted write and a confirmed public value remain different states, and an unreadable page stays unknown.

  3. 03
    No invented scope

    Pages describe the product’s current boundary and name external providers or unfinished paths where they matter.

Continue the work

Related Netrix resources

Browse all resources

Security

Put a concrete control at every place authority enters.

Review Netrix tenant isolation, credential handling, network protections, connector authentication, deployment gates, and operational controls.

Data protection

Data protection begins with knowing which system holds each record.

Understand what Netrix stores, how tenant data and credentials are separated, transport protections, logs, and deletion boundaries.

AI governance

AI output remains a proposal until an authorized person decides otherwise.

See how Netrix scopes AI drafting, attributes account usage, protects prompts and credentials, and keeps publishing under human control.

See it in your workflow

Bring the evidence, decisions, and outcomes into one trail.

Request access