The Age-Restricted Internet

A vision of privacy & protection for a legally compliant validation of our confidential things like age, education, medical, or employment status.

Core Principles

A Service is private when the Owner decides it should not be displayed. Data is private when a Publishing Service decides it shall be governed as such. Consuming Services can onboard new members immediately, granting privileged access in response to changes in real-time. Owner updates to privacy and Service updates to access take effect immediately.

“This is not just a technical solution — it’s a logical framework that reflects the natural truths of validation, privacy, and safety; programmatically enforced in code.”

Respecting this shared vision: Publishers define access, Owners define privacy, and trusted Consuming Services handle only what is authorized.

Services define what are appropriate trusted sources like the "My Health Record" in the National Provider Portal (NPP), Department of Motor Vehicles, Employment or Alumni associations, even GitHub. Rather than relying on static ID cards, Owners confirm the accounts behind the data used to print cards made for when data is not available. Consuming Services set the legal or policy standards, while Owners have choice.

DevHäuz Merit Badges & Privileged Feature Access

Owners control privacy, granting or revoking as they wish, while Consuming Services like this one, are ensured of adherence to legal and regulatory requirements. Meanwhile, Publishing Services continue to govern access — all parties enjoy freedom from risk.

• The DevHäuz Consuming Service responds to the existence of a validated and qualified Publishing Service.
  
• DevHäuz does not reveal account details but relies on validation of this specific trusted Publishing Service for veracity.
  
• DevHäuz responds by displaying trust-building details, such as an account holder's privatized birthday, repo count, or full name, as evidence of transparency.
  
• Owners grant requested credentials to access immediate onboarding and privileged features and revoke them if they wish.

When a validating property is provided, a special achievement badge appears. If not, the badge disappears until the Owner specifically grants visibility of a validating property to this Consuming Service, DevHäuz.