A New HTTP Status Code for Consent-Based Access Control

Privacy regulations worldwide increasingly emphasize the need for explicit user consent before processing data. 460 Consent Required bridges this gap, offering a standardized response for consent-dependent requests.

Sign a Petition

What is 460

Card Image

A New HTTP Status Code for Consent-Based Access Control

460 Consent Required is a new HTTP status code designed for consent-based access control. It helps users and organizations ensure compliance with privacy laws.

Read more

How?

Using 460 Consent Required: What You Need to Know

Implementing the 460 Consent Required status code follows a simple process:

  • 1 User requests access to content
  • 2 Server checks for valid user consent
  • 3 If consent is missing, server returns 460
Card Image

Why 460

Privacy Matters

Your data should remain yours. The 460 Consent Required status ensures transparency and user control.

Stronger Regulation

We advocate for better compliance with privacy laws through standardized HTTP responses.

Global Awareness

By raising awareness, we empower users and companies to prioritize privacy and consent.

Supporters

We are grateful for the organizations and individuals who support our mission. Their contributions help drive meaningful change.

Consentual support