OXAA

Secure public endpoints for local development

Privacy notice

Privacy notice: practical workflow, product behavior, limits, evidence and the exact next step with Oxaa.

Manage preferences

Contact support

Fast answer

Privacy 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

  • operating entity and roles
  • data categories and purposes
  • legal bases where applicable
  • cookies, local storage and consent
  • public traffic, local Inspector and operational data distinctions
  • billing, support and abuse records
  • subprocessors, transfers and locations
  • retention and deletion
  • rights and request process
  • security contact and complaints
  • effective date and changes

Approved facts required

FieldRequired approved value
Operating entity[APPROVED VALUE REQUIRED]
Privacy contact[APPROVED VALUE REQUIRED]
Data inventory[APPROVED VALUE REQUIRED]
Retention schedule[APPROVED VALUE REQUIRED]
Rights-request process[APPROVED VALUE REQUIRED]
Regulator or complaint path[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

Secure public endpoints for local development

Privacy notice

Manage preferences