LogoLogo
  • Introduction
  • Background
    • The GDPR
    • Data Request Practice
  • Why a Data Request API
    • Security
    • Modularisation
    • Best practices
    • A great user experience
  • Proposal
    • Goals
    • API Formatting
    • Authentication
    • Describing Data
  • Future Considerations
    • Governance
    • API Extensions
    • Certification
    • Security
    • Reference Implementations
    • Data Rights Registry
    • Iconography
Powered by GitBook
On this page
Export as PDF
  1. Why a Data Request API

A great user experience

PreviousBest practicesNextProposal

Last updated 4 years ago

While many organisations have processes for data rights (some electronic even), they differ between organisations. Particularly smaller organisations suffer from a lack of attention to make this process feasible and accessible for citizens. We consider this a pity, because dealing with these processes in a thorough manner showcases the attention that should be expected from an organisation processing personal information. A great user experience reinforces the idea that organisations are accountable and diligent with the data they are provided. Doing the process right, increases consumer trust, which is beneficial for revenue (e.g. ; ; ).

We strongly encourage the development of a standard range of tools that can act as a front-end to the Open Data Rights API. Work is already being done here in the form of , a desktop application that automates and archives data requests. Companies can either adopt such tools, or build their own. Yet, the choice for a suitable front-end lies with the user. This promotes developing strong user experiences in the realm of data rights.

Tsai et al., 2011
Tang et al., 2008
Udo, 2001
Aeon