Privacy
What is collected for operating the service, how long it is kept and what is deliberately never collected.
Legal
The rules, written to be read.
What data we hold, why we hold it, what we are allowed to do to your website, and what you can ask us to do — summarized here, with the full privacy notice, terms and data processing agreement linked from every section.
What the current evidence supports
AegiFlow acts on a website only within the limits you accept in writing, and each version of those terms is recorded with the moment you accepted it.
What you can see and control
Every capability has a narrow responsibility, an operational state and evidence that explains the result.
Available
Authorization to test
Security work on a website requires permission from someone entitled to give it. That permission is explicit and recorded.
Data processing
The terms that apply when we process data on behalf of your organization or your clients.
02
How you use it in an operating workflow
The visitor path remains short. Configuration, verification and rollback stay visible to the operator at every stage.
Fast request pathParallel analysisEvidence before promotion
- 01
Read the summary
Each section starts with what it means in one sentence.
- 02
Accept explicitly
The current version must be accepted before a service can be provisioned.
- 03
Ask anything
If a clause is unclear, that is our problem to fix, not yours to decode.
The interface explains what is known, unknown and required
AegiFlow does not turn missing evidence into a reassuring zero. Every state links to its source, freshness and next action.
- State
- Available, observation, configuration required, degraded, unavailable or planned.
- Evidence
- Source, timestamp, scope and last successful verification.
- Action
- The responsible party, exact change and expected impact.
- Way back
- Rollback instructions are defined before an active change.
In depth
How this capability behaves in production — grounded in the platform's documented, current operation.
Permission is explicit, and recorded
Security work on someone else's website is only legitimate with permission from a person entitled to give it. Before a service can be set up, the current terms must be accepted, and the platform records which version was accepted and when. Nothing is implied by usage.
What we deliberately never collect
The content of your visitors' requests, their addresses and their personal data are not gathered for analysis. What is kept is deliberately coarse: a normalized page name, a status, a timing and a country — enough to operate, not enough to profile anyone.
Start in observation. Activate only measured controls.
Ownership, certificate, origin health and rollback must pass before traffic protection changes.