Trust

Privacy.

An authority record explains a decision. It should not quietly become a record of someone's working day.

What an authority record holds

Needed to govern the delegation

In the record

  • Who may act, and on whose behalf
  • The resource, action and limits
  • Who authorised it, and when
  • The purpose it was granted for
  • Start, expiry, review and revocation events
Not required for the purpose

Out of the record

  • Activity unrelated to the delegated authority
  • Personal information the decision does not depend on
  • Content of the work carried out under the authority
  • Monitoring of the person beyond the delegation itself

A governance record and a surveillance record are different things, and the difference is whether the data is needed to explain and control the delegation. That boundary is a design principle, not an afterthought.

People in the model

Understanding your own authority
A person acting under delegated authority should be able to see what they may do, on whose behalf, within what limits and until when.
Understanding authority you gave
Someone who delegates should be able to see what is currently active in their name, and end it.
Decisions that affect you
Where a decision materially affects a person's authority, they should be able to understand the basis for it.
Your organisation's obligations
Recording delegated authority means handling personal information, so your privacy obligations continue as they do today. We work through what that means for a given design.

This website

What this site collects.

This is a static website. It sets no cookies, includes no third-party analytics or advertising, and does not track you between visits.

If you send an enquiry, we receive what you typed and use it to answer you. Privacy questions: privacy@maits.co.nz.

Working on a privacy impact assessment?

Tell us the deployment you have in mind and we will work through what information the model would hold, and what it would not.