Fast answer
Cookie and tracker notice gives the visitor a direct answer, the exact product behavior, the limits that affect the decision and a practical path to verification.
This is a structured counsel-ready draft, not legal advice and not permission to publish invented entity, retention, sanctions, tax, consumer or governing-law terms. Replace every bracketed field with an approved operating fact.
Technical details
strictly necessary storagepreferences and locale choiceauthentication and security storageanalytics and measurementmarketing trackers only after valid consentregional consent behaviorretention and vendor listwithdrawal and preference center
Approved facts required
| Field | Required approved value |
|---|---|
| Cookie and vendor inventory | [APPROVED VALUE REQUIRED] |
| Consent categories | [APPROVED VALUE REQUIRED] |
| Retention | [APPROVED VALUE REQUIRED] |
| Preference-center URL | [APPROVED VALUE REQUIRED] |
How traffic and Inspector data are handled
Oxaa's public edge terminates public HTTPS so it can resolve the exact hostname, identify the current authenticated route and forward the request. The session between the enrolled device and Oxaa is encrypted; the selected local service receives the request through that session.
Oxaa retains bounded account, route, usage, security, billing, support and diagnostic metadata required to operate and protect the service. Inspector body capture is a separate, explicit debugging action: the bounded request or response body copy shown by the local Inspector remains on the developer device and can be redacted, deleted or allowed to expire. Public traffic still has to be processed by the edge, so the accurate claim is local Inspector copies—not “Oxaa cannot see traffic.”
Complete the next real step
Continue with Manage preferences when the current product, plan and country support that action. Use Contact support to review the exact technical, trust or support path before committing.
oxaa login
oxaa http 3000