Design Considerations [to be removed]

In this lesson, we will handle the following concerns:

• Can a user activate and deactivate client-side reports?
• How do client-side agents reach collectors under faulty conditions?
• How will we protect user privacy?

Activate/deactivate reports

We will use a custom HTML header to send appropriate information to the collectors. Though a client accesses the service via a browser, a specific browser should know about this feature to appropriately fill in the header information in the HTTP requests. For organizations that make browsers and provide services (for example, chromium-based browsers), such features can be incorporated and standardized over time.

Another solution can be to use a client-side application that the service controls, and then we can easily include such headers over HTTP.

The client can fill in the request header (if the client has already consented to that, but more on that in the privacy section). The service can then reply with appropriate values for the policy and collection end-points.