Skip to content

Data protection

Data protection begins with knowing which system holds each record.

Netrix stores account, website, audit, location, review, metric, deployment, and usage records in tenant-scoped databases; crawl payloads and attachments use configured object storage; connector history may remain in customer-owned WordPress or Cloudflare systems. Each boundary has a different deletion and persistence behavior.

Request access Explore the platform
FIELD NOTE / TRUSTData protection
NETRIX
Evidence
01
Decision
02
Action
03
Proof
04

An accountable sequence

Observed100% Reviewed78% Applied52% Verified48%
Illustrative states, not benchmark or customer performance data.

What the workflow must answer

Keep the operating question attached to the evidence.

01

Tenant-scoped application data

Account ownership and policy checks constrain records before they reach controllers, jobs, or provider operations.

02

Encrypted credentials

API tokens and connector credentials use Active Record encryption and are never rendered back in full.

03

Documented external state

Applied WordPress values and customer-owned edge resources have persistence rules separate from Netrix database deletion.

Control review

Translate the promise into something an operator can inspect.

Review the trust center
01Tenant-scoped application data
Account ownership and policy checks constrain records before they reach controllers, jobs, or provider operations.
02Encrypted credentials
API tokens and connector credentials use Active Record encryption and are never rendered back in full.
03Documented external state
Applied WordPress values and customer-owned edge resources have persistence rules separate from Netrix database deletion.

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.

Retention

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

Review current retention, report expiry, crawl payload, audit history, logs, connector teardown, and account deletion behavior.

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