Retention
Some records expire automatically. Others remain until the account or an operator removes them.
Expiring report links and short-lived tokens have defined lifetimes. Many audit, deployment, metric, review, and usage records remain until their owning account data is deleted. Crawl files, infrastructure logs, and customer-owned connection history may follow separate operational schedules.
| State | Evidence | Owner |
|---|---|---|
| Found | RetentionOriginal page and available evidence recorded | Audit |
| Reviewed | Decision recordedA person checked the target and proposed value | Human |
| Checked | Public page readLive result recorded separately | Netrix |
What to look for
Get the answer without losing sight of where it came from.
Access links and tokens expire
Report links have a finite expiry, and invitation or pairing tokens have their own short lifetimes.
Work history is generally long-lived
Audits, tasks, deployments, metrics, reviews, and usage records remain until their owning records are deleted.
Customer systems have their own history
WordPress changes and connection records may survive a Netrix disconnect, depending on site ownership and uninstall choices.
How Netrix handles it
Look past the promise and see what the product actually does.
- 01Access links and tokens expire
- Report links have a finite expiry, and invitation or pairing tokens have their own short lifetimes.
- 02Work history is generally long-lived
- Audits, tasks, deployments, metrics, reviews, and usage records remain until their owning records are deleted.
- 03Customer systems have their own history
- WordPress changes and connection records may survive a Netrix disconnect, depending on site ownership and uninstall choices.
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.
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.
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