Skip to content

Commit 82fe7e4

Browse files
daguaggitbook-bot
authored andcommitted
GitBook: [master] one page modified
1 parent 0bc49c3 commit 82fe7e4

File tree

1 file changed

+14
-31
lines changed

1 file changed

+14
-31
lines changed

applicationdevelopmentlifecycle/analysisphase.md

Lines changed: 14 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -23,13 +23,8 @@ Access to device-specific information \(e.g. UDID, IMEI, MAC addresses, etc.\) M
2323

2424
The processing of personal data makes it necessary to define a **Privacy Policy**. Since the minimum requirements of the local data protection laws have to be fullfilled anyway we suggest to take data protection serious and go a step further to build attractive and competitive apps.
2525

26-
* [ ] [comment](https://github.com/AppPETs/developer-guidelines/tree/5d6d22d22b2f697aeba374552a121460ae793d2a/"/README.md):"no minimal compliance, but real data protection
27-
2826
_If we talk about personal data, keep in mind that **a lot of data can be linked to individuals**, especially in the field of mobile apps. That's why it is advised to avoid the storage and processing of data where possible_
2927

30-
* [ ] _notice that all data on a device might be linkable to a person._ -> data minimisation is key
31-
* [ ] Textbox: Legal Hint: Privacy Policy requirements
32-
3328
The definition of a privacy policy implies, but is not limited to:
3429

3530
### Which types of personal data are accessed and why?
@@ -43,7 +38,6 @@ The definition of a privacy policy implies, but is not limited to:
4338
* Statement on how to access personal saved data as a user
4439
* Statement on how to initiate personal data deletion as a user
4540
* extended information about privacy policies etc. can be found here: \[[https://www.enisa.europa.eu/](https://www.enisa.europa.eu/)\]
46-
* [ ] \(hier einfach die basalen Punkte, \(die zeitlos sind\) übernehmen\*
4741
* [ ] make clearer reference to concrete pages
4842

4943
### Is data leaving the main ecosystem?
@@ -54,13 +48,14 @@ Think about on which level your data is processed and transmitted.
5448
* is data leaving the "local boundary"
5549
* is data leaving the "eco system boundary"
5650
* is data leaving the "3rd party boundary"
57-
* [ ] explain what that exactly means!
5851

59-
For the processing of data, you need a proper contract, that you are entitled to do so. This is bound to a number of duties
52+
{% hint style="info" %}
53+
For the processing of data, you need a proper contract, that you are entitled to do so. This is bound to a number of duties. \(cf. [Article 28, GDPR](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32016R0679&from=EN#d1e3033-1-1)\)_._
54+
{% endhint %}
6055

61-
* [ ] _\(german ADV\)_ \(translation of the term?\)
62-
* [ ] which duties exactly?
63-
* [ ] _\(processors need to be obliged to data protection principles_
56+
{% hint style="success" %}
57+
_You can find an_ [_template_](https://www.gdd.de/downloads/praxishilfen/Mustervertrag_zur_Auftragsverarbeitung_DS-GVO_english.docx) _at the Society for data protection and data securitys \(GDD\) website._
58+
{% endhint %}
6459

6560
### Which data needs which level of protection?
6661

@@ -73,23 +68,25 @@ Special categories of data are placed under particular protection of the law.
7368
| sensitive data | harmful consequences possible, special risk assessment necessary |
7469
| | |
7570

76-
* [ ] add legal hint to "Data Protection Level"
77-
7871
| Legal Hint: "Data Economy" |
7972
| :--- |
8073
| Access to data \(e.g. PIM, media, etc.\) MUST take place in line with data economy1 according to §3a BDSG. Data MUST NOT be passed on to third parties without an Opt-In from the user. Utilization of the data SHOULD be explained to the user \(why does the application need this access, and what will not function if I do not provide this access?\). |
8174

82-
#### Sensitive Data
75+
#### Special categories of personal data with stronger limitations
76+
77+
{% hint style="warning" %}
78+
Special categotires of data include data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, and the processing of genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health or data concerning a natural person's sex life or sexual orientation. \([Art 9, GDPR](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32016R0679&from=EN#d1e3033-1-1)\)
79+
80+
These data generally may only be used where the data subject has given explicit consent regarding these very categories of information.
81+
{% endhint %}
8382

84-
Amongst these are personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, and the processing of genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health or data concerning a natural person's sex life or sexual orientation. These data generally may only be used where the data subject has given explicit consent regarding these very categories of information.
8583

86-
* [ ] convert to box?
8784

8885
#### Extent of data used
8986

9087
Where the information on individuals used by the app is particularly comprehensive, exposing their conduct or characteristics, particular attention needs to be paid to the protection of those data.
9188

92-
* Is data used that must be deletable on user demand? \(@ULD: which data is affected\) _\(grundsätzlich immer\)_
89+
* In general data used must be deletable on user demand
9390
* a routine must be implemented to ensure full deletion of user data on demand
9491
* all saved data from the user must be deletable
9592
* this applies also to data stored in the cloud
@@ -101,17 +98,3 @@ Where the information on individuals used by the app is particularly comprehensi
10198
If children or other persons who require particular legal protection are involved, the processing of data might be more restricted than otherwise.
10299
{% endhint %}
103100

104-
## Risk Assessment
105-
106-
* [comment](https://github.com/AppPETs/developer-guidelines/tree/5d6d22d22b2f697aeba374552a121460ae793d2a/"/README.md):"to be discussed"
107-
* cf. risk management in section "Design Phase"
108-
* [ ] which generic parts of RA can be put in Introduction.md / Foundations.md and which special part might be relevant for the specific phases
109-
* [ ] the criteria mentioned above are a good basis for the risk assessment, which shoule be revisited after every step in the development lifecycle
110-
* [ ] what means risk here for the developer? [comment](https://github.com/AppPETs/developer-guidelines/tree/5d6d22d22b2f697aeba374552a121460ae793d2a/"/README.md):"risk to endanger privacy of clients"
111-
* all processed data needs to be analysed to specify a risk level of potential malicious use of the data
112-
* based on these risk levels special protection routines need to be applied \(refer to standardized risk-levels\)
113-
114-
**Examples:**
115-
116-
* [ ] TODO...
117-

0 commit comments

Comments
 (0)