Data protection
To protect data well, you first need to know where it lives.
Netrix stores account, website, audit, location, review, metric, deployment, and usage records in its application database. Crawl files and attachments may use object storage. WordPress and Cloudflare can retain customer-owned changes or history outside Netrix, so deleting an account does not erase every external system.
- Evidence
- 01
- Decision
- 02
- Action
- 03
- Proof
- 04
How the work moves
Observed100% Reviewed78% Applied52% Verified48%What to look for
Get the answer without losing sight of where it came from.
Scope application data to the account
Ownership and policy checks limit records before controllers, background jobs, or provider operations use them.
Encrypt connected-account secrets
API tokens and connection credentials use application encryption and are never shown back in full.
Remember the systems customers own
WordPress values and Cloudflare resources follow their own persistence rules outside Netrix's database.
How Netrix handles it
Look past the promise and see what the product actually does.
- 01Scope application data to the account
- Ownership and policy checks limit records before controllers, background jobs, or provider operations use them.
- 02Encrypt connected-account secrets
- API tokens and connection credentials use application encryption and are never shown back in full.
- 03Remember the systems customers own
- WordPress values and Cloudflare resources follow their own persistence rules outside Netrix's database.
From finding to follow-up
See where the work stands—and what still needs to happen.
- 01Found
Netrix records the page and the issue it found.
- 02Reviewed
Someone checks the finding in context.
- 03Approved
The right person chooses what should change.
- 04Applied
A supported connection accepts the change.
- 05Checked
Netrix reads the public page again.
- 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.
- 01Nothing publishes itself
AI drafts and supported SEO changes wait for an authorized person to act.
- 02A 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.
- 03Limits 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
Security
Security starts with limiting who can reach an account, a credential, or a live site.
Learn how Netrix separates accounts, protects credentials, authenticates connections, gates site changes, and secures production traffic.
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