| 1.1 Portfolio
51 Subscription Portfolio | |
|---|
| 1.1.51 Subscription Portfolio | | * ZEMA is upgraded to UEM so history can be managed in the normal way. UEM shares symbolic keys with its parent person, so navigation by drill down is feasible. |
| Business Rules: | | * Before a UEM is inserted, its existence is verified against UAP and other UEM data. If the UAP says no communications or UEM has opted-out for the given web page, then UEM is not inserted and the message rejected. |
| Right to be Forgotten: | | * Right to be Forgotten is a simple flag at the UAP person record level that is selected to say no communications whatsoever. All subscriptions can be changed to opted-out as secondary evidence. |
| 1. Overview: | | 1. All electronic communication must be subject to subscription control; people must be able to subscribe (opt-in) and unsubscribe (opt-out). Control data is needed to manage when and how people subscribe and unsubscribe to specific types of message. | | 2. Regulations are concerned with people as staff and customers (and suppliers). Phase 1 is to manage staff communications and phase 2 is to manage customer relationships. Phase 1 is to manage subscriptions at the web page number level. |
| 2. Envelope and Letter: | | 1. Every electronic communication must share the proven envelope and letter method where the letter is any web page or document. The primary purpose of the envelope is track and trace - every envelope has a unique subscription record to track if the person opts-in or opts-out. | | 2. Subscription control is simply the build up of envelope evidence as a person subscribes or unsubscribes to any emailed web page. Subscription operates at the web page level. A person does not subscribe or unsubscribe to ALL electronic communications. | | 3. Every envelope has a WHO and WHAT record - subscription is about controlling the WHAT for each specific WHO. Each WHO person has the right to see their list of WHAT subscriptions with opt-in date, and their list of WHAT unsubscribed opt-out dates. Shared read-only data is a right and a privilege, and evidence that subscriptions are being managed in an professional way. |
| 3. Life Cycle: | | 4. Every letter has a fixed life cycle that is managed by the subscription record. A message can be changed at any time, even after the envelope has been sent. The letter can be revoked at any time by expiring its life cycle. |
| 4. Subscription Data: | | Each subscription record holds WHO, WHAT, WHEN and WHY - each record is the data representation of an envelope. | | 1. WHO is held as a person key that represents a persons name and mail address. People tend to have unique mail addresses. IP and browser instances are retained as evidence. | | 2. WHAT is held as a web page number that represents a page key and page subject. Messages must have a page number and subject. A record key may also be stored to identify in instance of the web page. A unique message number is also used that is the key to the subscription record. | | 3. WHEN is the date and time when a subscription or unsubscribe took place. | | 4. WHY is simply an Opt-In or Opt-Out flag. |
| 5. Extra Data: | | 5. Details of the person who sent the electronic communications is stored with the sent date and time. Subscription control is independent of who sent a message. A message cannot be sent to a person who has unsubscribed from the web page that is about to be sent. | | 6. Expiry date and time are controlled in the subscription record. | | 7. URL and subject are carried for lookup identification purposes. |
| 6. Subscription History: | | 1. Subscription History for a named person is a spreadsheet of opt-in and opt-out records in date order with the applicable web page number and subject. Every personal dashboard may include a link so the person may view their subscription evidence in date order. |
|
|