AegiFlow
FR
EnglishRomânăEspañolFrançaisDeutsch
AideCréer un compte
Legal and data handling

Clear authority, clear data boundaries, clear exclusions.

Commercial terms, privacy notice, DPA, acceptable-use policy, subprocessors and incident procedures are release gates for paid service.

Request legal documentsSee the complete operating flow
Operational viewIllustrative flow. No customer data.
What the current evidence supports

This page documents intended controls and operational boundaries; it is not a substitute for reviewed legal documents.

GoTe now

GoTe nowGoTePrivate beta · operator-assisted
Traffic
Checking current route
Protection
Unknown
Runtime
Unknown
Scope
Not verifiable
Traffic proof until
Not verifiable

Current state is shown only after a fresh, schema-validated snapshot is loaded.

Open status evidence
01

Platform capabilities

These cards describe product scope. Current delivery stage, runtime health, scope and freshness are reported separately from the validated public snapshot above.

01

Confidentialité

Minimize telemetry, avoid bodies by default and publish retention and deletion behavior.

Platform · implemented
02

Authorized scope

Scanning, proxying and response require verified ownership and explicit technique limits.

Platform · implemented
03

Commercial documents

Terms, DPA, AUP, SLA and subprocessors require Romanian and EU legal review.

Platform · planned
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 pathAnalyse en parallèleEvidence before promotion
  1. 01

    Document

    Describe data, authority, responsibilities and exclusions.

  2. 02

    Review

    Obtain written legal and privacy assessment.

  3. 03

    Accept

    Store versioned customer acceptance before activation.

03

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.

Delivery stage
Planned, implemented, verified, activatable or active.
Runtime health
Healthy, degraded, stale, unknown or unavailable — independently of delivery stage.
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.

Start without changing traffic. Activate only measured controls.

Ownership, certificate, origin health and rollback must pass before traffic protection changes.

Request legal documents