# Privacy Goals for the Data Lifecycle
## 6 Step 3-Aligning the Privacy Goals to GDPR and the Data Lifecycle
### Ideal-Cities-Worked Example  
To illustrate how these can be used to support decision making throughout 7-DL, the privacy goals are evaluated with the use of a worked example. This example will look at each of the privacy goals and explain how these might be applied in practice to help readers understand how they can put the framework into context and apply this to their business. This worked example will consider one of the Ideal-Cities circularity use cases, created as part of the project data management plan. The use case scenario that will be used is the _life logging \"Fire Incident\"_ use case from the Ideal-Cities project [53]. This use case was one of the pilot use cases trialled as part of the project's evaluation. Its aim is _increasing citizen safety through life logging and location information_. In this use case, the idea is that a user reports a fire in real-time (using the fire evacuation app). Users can report an incident either manually or through a GPS locator embedded within the app. To support the ability to use the GPS locator, a series of QR codes for each location are pre-installed in strategic locations throughout the building. Once a user has reported an incident, users within the affected building or within close vicinity of that building, will be notified and advised to evacuate the area. In the pilot trial case, the project used pre-existing QR stickers on doors within the buildings to facilitate location GPS and to record pre-determined evaluation point locations for each building so that users can be directed accordingly. To demonstrate how to align this use case with 7-DL, we will describe each stage in 7-DL in turn in relation to the use case, 7-DL, GDPR and the privacy goals. The data flow diagram presented in Figure 4 provides a full overview of the worked example. The figure is designed to depict the flow of the data among the elements of the scenario and the framework connections as the data flow. Steps _7-DL1: Governance_ and _7-DL7: Disposal_ are not tagged into any flow or the process since the governance step covers all the decisions that have been made in this diagram and the disposal step is a post consideration, also being one of the crucial steps of the framework. The use case data flow starts with the user initiating the fire event by reporting the fire using the application. Immediately after this action, the location information from the GPS access of the mobile device and a picture from the event have been collected following the _7-DL2: Collection_ step. After the collection, the flow proceeds with the transformation of the collected data into an event object. This step follows the _7-DL3: Transformation_ considerations of the framework. Then, the created event for the incident is stored, filtered, and traced in the Ideal-Cities Hub which fulfils the _7-DL4: Retention_ steps. The event information is then pushed to the users in the same building, related services and the fire department utilising the _-DL5: Access and Release_. Further post access of this event by the fire departments and the services and consideration of the post access is given with the _7-DL6: Post Access_ step of the framework. In the next sections, one can find the'step-by-step' explanation of the data flow and the framework. The dashed boxes on Figure 4 depict the trust boundaries of the worked example. Main distinctions between trust boundaries can be seen between independent computation units where the data flows. The initial trust boundary alternation (Green Box) is when the data is being captured on the mobile device from the user, as several considerations come into play regarding trust, such as the security posture of the mobile device or installed applications on the mobile device. As the data moves towards the Ideal Cities Hub identities towards the data flow diagram, the trust boundary changes in accordance. As can be seen in the boundary defining Ideal Cities Hub (Red Box), information processing and event dispatching is considered within the same boundary.