Skip to content

Security

Security starts with limiting who can reach an account, a credential, or a live site.

Netrix scopes data to the active account, encrypts provider credentials, validates public fetch targets, signs WordPress requests, verifies site ownership, and checks several gates before a supported change can run. This page describes controls present in the product today, not a certification.

Request access Explore the platform
ControlSystemHumanClient
Collect evidence✓——
Review meaning—✓✓
Approve action—✓✓
Verify output✓✓—
Permissions depend on the person's account role, ownership of the site, the connected provider, and the change being requested.

What to look for

Get the answer without losing sight of where it came from.

01

Keep client accounts separate

Records resolve through the active account and membership role; client users are limited to businesses assigned to them.

02

Protect credentials and outbound requests

Netrix encrypts provider secrets, filters them from logs, and restricts URL fetching to allowed public destinations.

03

Put gates in front of production

Account access, ownership, system switches, connection capability, and crawl quality can stop a supported deployment.

How Netrix handles it

Look past the promise and see what the product actually does.

Review the trust center
01Keep client accounts separate
Records resolve through the active account and membership role; client users are limited to businesses assigned to them.
02Protect credentials and outbound requests
Netrix encrypts provider secrets, filters them from logs, and restricts URL fetching to allowed public destinations.
03Put gates in front of production
Account access, ownership, system switches, connection capability, and crawl quality can stop a supported deployment.

From finding to follow-up

See where the work stands—and what still needs to happen.

  1. 01Found

    Netrix records the page and the issue it found.

  2. 02Reviewed

    Someone checks the finding in context.

  3. 03Approved

    The right person chooses what should change.

  4. 04Applied

    A supported connection accepts the change.

  5. 05Checked

    Netrix reads the public page again.

  6. 06Shared

    The report summarizes the audit and fixes currently marked applied.

A few things worth knowing

Netrix can prepare the work. Your team still makes the call.

  1. 01
    Nothing publishes itself

    AI drafts and supported SEO changes wait for an authorized person to act.

  2. 02
    A write is not proof

    Netrix records when a provider accepts a change, then checks the public page separately. If it cannot read the page, the result stays unknown.

  3. 03
    Limits belong in the open

    When a feature depends on another provider or stops short of a complete workflow, the page should say so.

Keep exploring

More on this part of the work

Browse all resources

Data protection

To protect data well, you first need to know where it lives.

See what Netrix stores, how account data and credentials are separated, how traffic is protected, and what deletion does not reach.

Retention

Some records expire automatically. Others remain until the account or an operator removes them.

Review how long reports, audit history, crawl files, logs, and connection records remain, and what account deletion removes.

AI governance

AI writes drafts. Authorized people decide what happens to them.

See which tasks use AI, how account usage is recorded, how prompts and keys are handled, and where human approval remains required.

See how it fits your team

Bring the crawl, the review, and the follow-up together.

Request access