gRc402 • Personalization
& Mass-Customization

Week 9 • Winter 2021 • Ahmed Sagarwala

Lab Submission (Next Sunday)

  • Bring it all together!
  • Front:
    • Variable image with dynamic text
    • Branded*
  • Back:
    • Mailing information
    • QR code (covered in lab)*
    • Correct margins
    • Incorporates an indicia
  • Two sample records (You + me)

Checklist Submission (this Sunday)

  • Details posted to Canvas
  • Consider form fields, data cleansing, layout/design, print output, delivery, and tracking
  • Should contain over FOUR checks per stage
  • Ideally, team member should come up with 8+ ideas

What examples can we think of?

Objectives

  • Explore the Privacy By Design approach.
  • Understand issues around data capture and transparency.
  • Determine how businesses can improve their track-records.
  • Review upcoming technologies that will change legislation and how we use the internet.

But why?

  • Follow up with HR or the person that interviewed you.
  • Email is ideal, but don't expect an answer.
  • If they can't tell you, you probably shouldn't be there.
  • What should you ask?

The job application process is often a black box. We often have no idea what happens behind the scenes. How are decisions actually made?

What bothers you?

You're making an online purchase. There are several steps in completing the purchase:

  1. Finding the product
  2. Adding it to your cart
  3. Sign in / sign up
  4. Shipping details
  5. Payment details

When did the data collection start?

  1. Finding the product
  2. Adding it to your cart
  3. Sign in / sign up
  4. Shipping details
  5. Payment details

I want to know what you know.

"Coveillance"

Privacy by Design

  • Privacy design framework
  • Created in the 90's by Dr. Ann Cavoukian
  • Canadian and Dutch report released in '95
  • Incorporated by E.U. to create G.D.P.R.
  • Seven principles

1. Proactive not reactive; preventative not remedial

2. Privacy as the default setting

3. Privacy embedded into design

  • Standard notifications for ToS changes
  • Simplified language around data use
  • Checkboxes default to not sharing
  • Compel users to opt-in
  • Strong encryption for personal data
  • Third-party sharing controls
  • End-user auditing tools

4. Full functionality
— positive sum, not zero sum

5. End-to-end security
— full lifecycle protection

Image: Daniel Goldman

6. Visibility and transparency
— keep it open

7. Respect for user privacy
— keep it user-centric

Pasco’s sheriff uses grades and abuse histories to label schoolchildren potential criminals.

The kids and their parents don’t know.

Consent

A friend drops by and asks to come in.
You allow them in.
They sleep on the couch and eat your food. They leave.

 

A few days later, they return.

They walk right in, grab a snack, and takeover the couch.

Solid

What is solid?

  • Sir Tim Berners-Lee
  • Use of pods to allow users to make decisions
  • Users store and manage their own pods
  • Users control app access to pod(s)

GrC402 Week 9

By Am Sagarwala

GrC402 Week 9

Data capture privacy and ethics

  • 243