A File Format to Aid in Consumer Privacy Enforcement, Research, and Tools
draft-colwell-privacy-txt-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Nick Sullivan , Louise Van der Peet , Georgios Smaragdakis , Brien Colwell | ||
| Last updated | 2024-12-29 (Latest revision 2024-06-27) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This proposal outlines a new file format called privacy.txt. It follows similar placement on a web server as robots.txt [RFC9309], security.txt [RFC9116], or ads.txt [ADS-TXT], in the / directory or /.well-known directory. The file format adds structured data for three areas: 1. A machine parsable and complete privacy policy 2. Consumer actions under their privacy rights 3. Cookie disclosures
Authors
Nick Sullivan
Louise Van der Peet
Georgios Smaragdakis
Brien Colwell
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)