pages/privacy.html - Issue 29367268: Issue 4474 - short version of Privacy Policy at eyeo.com

Side by Side Diff: pages/privacy.html

Issue 29367268: Issue 4474 - short version of Privacy Policy at eyeo.com (Closed) Base URL: https://hg.adblockplus.org/web.eyeo.com

Patch Set: Fixed unconverted markdown email link. Created Dec. 12, 2016, 7:05 p.m.

Left:
Right:

Use n/p to move between diff chunks; N/P to move between comments.

Jump to:

View unified diff | Download patch

OLD	NEW
1 title=Privacy Policy	1 title=Privacy Policy
	saroyanm 2016/12/13 15:09:54 You converted the file from markdown to HTML I thi You converted the file from markdown to HTML I think it makes sense to change the extension. juliandoucette 2016/12/13 16:41:09 I did change the extension? Show quoted text On 2016/12/13 15:09:54, saroyanm wrote: > You converted the file from markdown to HTML I think it makes sense to change > the extension. I did change the extension? saroyanm 2016/12/13 17:07:17 Yes you did, sorry maybe I mixed some reviews, jus Show quoted text On 2016/12/13 16:41:09, juliandoucette wrote: > On 2016/12/13 15:09:54, saroyanm wrote: > > You converted the file from markdown to HTML I think it makes sense to change > > the extension. > > I did change the extension? Yes you did, sorry maybe I mixed some reviews, just ignore my comment. juliandoucette 2016/12/19 14:36:31 Done. Show quoted text On 2016/12/13 17:07:17, saroyanm wrote: > On 2016/12/13 16:41:09, juliandoucette wrote: > > On 2016/12/13 15:09:54, saroyanm wrote: > > > You converted the file from markdown to HTML I think it makes sense to > change > > > the extension. > > > > I did change the extension? > > Yes you did, sorry maybe I mixed some reviews, just ignore my comment. Done.
2	2

3 <header class="page-title">	3 <header class="page-title">

4 <h1>Privacy Policy (eyeo.com)</h1>	4 <h1>Privacy Policy <small>(eyeo.com)</small></h1>

5 </header>	5 </header>

6	6

7 <div class="content-block" markdown="1">	7 <div class="content-block">

8 Your protection and data confidentiality is of utmost importance to us (“Eyeo” “ we” “our”). We take the protection of your personal data very serious and collec t as less data as possible. Nevertheless, some personal data are necessary to pr ovide our website and/or our application tools for candidates. This privacy poli cy shall inform you about the personal data we collect and how exactly that data is used. We gather and use personal data firmly within the provisions of the da ta protection laws of Germany. In the following text we will inform you about th e specific data, the scope and purpose of the collection and use of personal dat a by us when using Eyeo.	8 <h2 id="short-version">

9	9 Privacy Notice <small>(short version)</small>

10 ## Who is responsible for the Data processing?	10 </h2>

11	11 <p>

12 The legal person responsible for the collection, processing and/or use of person al data in connection with Eyeo (“Controller”) is:	12 The following privacy notice shall provide you with a general overview about the collection, processing and use (hereinafter together referred to as "proces sing") of your personal data. For more information regarding our processing acti vities, please view our complete <a href="#long-version">privacy policy</a>.

13	13 </p>

14 Eyeo GmbH<br>Lichtstraße 25<br>50825 Cologne<br>Germany	14 </p>

15	15 <h3 id="short-process-data">

16 If you have any queries relating your personal data, please do not hesitate to c ontact us: [privacy@eyeo.com](mailto:privacy@eyeo.com)	16 What kind of data do we process?

17	17 </h3>

18 ## What are Personal Data?	18 <ol>

19	19 <li>

20 The purpose of data protection is to protect personal data. Personal data means any information relating to an identified or identifiable natural person (“data subject”); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an i dentification number, location data, an online identifier or to one or more fact ors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person. This information includes, for examp le, details such as name, postal address, email address or telephone number but also nicknames, certificates and information about your interests.	20 While using the Eyeo.com website:
	saroyanm 2016/12/13 15:09:54 This list is almost same as the one below, maybe w This list is almost same as the one below, maybe we can include them, otherwise we have duplication here. j.nink 2016/12/13 15:18:21 Please do not change any content. I know that this Show quoted text On 2016/12/13 15:09:54, saroyanm wrote: > This list is almost same as the one below, maybe we can include them, otherwise > we have duplication here. Please do not change any content. I know that this is double, but this is required according to the short form template. saroyanm 2016/12/13 15:27:35 Acknowledged. Show quoted text On 2016/12/13 15:18:21, j.nink wrote: > On 2016/12/13 15:09:54, saroyanm wrote: > > This list is almost same as the one below, maybe we can include them, > otherwise > > we have duplication here. > > Please do not change any content. I know that this is double, but this is > required according to the short form template. Acknowledged. saroyanm 2016/12/13 15:57:43 Aligned with Judith and apparently there was misun Show quoted text On 2016/12/13 15:18:21, j.nink wrote: > On 2016/12/13 15:09:54, saroyanm wrote: > > This list is almost same as the one below, maybe we can include them, > otherwise > > we have duplication here. > > Please do not change any content. I know that this is double, but this is > required according to the short form template. Aligned with Judith and apparently there was misunderstanding and she agreed not to have duplication in the code. j.nink 2016/12/13 15:59:21 agreed Show quoted text On 2016/12/13 15:57:43, saroyanm wrote: > On 2016/12/13 15:18:21, j.nink wrote: > > On 2016/12/13 15:09:54, saroyanm wrote: > > > This list is almost same as the one below, maybe we can include them, > > otherwise > > > we have duplication here. > > > > Please do not change any content. I know that this is double, but this is > > required according to the short form template. > > Aligned with Judith and apparently there was misunderstanding and she agreed not > to have duplication in the code. agreed juliandoucette 2016/12/13 16:41:09 Will-do. Show quoted text On 2016/12/13 15:59:21, j.nink wrote: > On 2016/12/13 15:57:43, saroyanm wrote: > > On 2016/12/13 15:18:21, j.nink wrote: > > > On 2016/12/13 15:09:54, saroyanm wrote: > > > > This list is almost same as the one below, maybe we can include them, > > > otherwise > > > > we have duplication here. > > > > > > Please do not change any content. I know that this is double, but this is > > > required according to the short form template. > > > > Aligned with Judith and apparently there was misunderstanding and she agreed > not > > to have duplication in the code. > > agreed Will-do. juliandoucette 2016/12/19 14:36:32 Done. Show quoted text On 2016/12/13 16:41:09, juliandoucette wrote: > On 2016/12/13 15:59:21, j.nink wrote: > > On 2016/12/13 15:57:43, saroyanm wrote: > > > On 2016/12/13 15:18:21, j.nink wrote: > > > > On 2016/12/13 15:09:54, saroyanm wrote: > > > > > This list is almost same as the one below, maybe we can include them, > > > > otherwise > > > > > we have duplication here. > > > > > > > > Please do not change any content. I know that this is double, but this is > > > > required according to the short form template. > > > > > > Aligned with Judith and apparently there was misunderstanding and she agreed > > not > > > to have duplication in the code. > > > > agreed > > Will-do. Done.
21	21 <ul>

22 ## What kind of Data do we collect and process and how?	22 <li>

23	23 IP address (stored separately)

24 ### Website logs	24 </li>

25	25 <li>

26 While using Eyeo.com website, we are automatically recording website logs and th ereby collecting the following data for technical and for security reasons:	26 Date and time of access

27	27 </li>

28 * IP address	28 <li>

29 * Date and time of access	29 Browser type / version

30 * Browser type / version	30 </li>

31 * URL of previously visited Web page	31 <li>

32 * Amount of data sent	32 URL of previously visited webpage

33	33 </li>

34 This data is stored purely for technical reasons and cannot be linked to any ind ividual person. We are not combining the website log data with any other informa tion about you. Such website logs are retained for a period of 30 days after whi ch only the aggregated usage statistics, which cannot be connected to a single u ser remain. Everything else will be deleted.	34 <li>

35	35 Amount of data sent

36 ### Application data	36 </li>

37	37 </ul>

38 If you are applying online for a job at Eyeo you need to fulfil our online appli cation form. In order to evaluate your application properly we need at least your name, email address and a CV. On a voluntary basis you may further add a t elephone number, a cover letter, additional documents, as but not limited to cer tificates, a website and additional information about you.	38 </li>

39	39 <li>

40 We are collecting and processing those data for the sole purpose of managing Eye o’s recruitment related activities as well as for organizational planning purpos es. Consequently, Eyeo may use your personal data in relation to the evaluation and selection of applicants including for example setting up and conducting inte rviews and tests, evaluating and assessing the results thereto and as is otherwi se needed in the recruitment processes including the final recruitment.	40 When applying for a job:
	saroyanm 2016/12/13 15:09:54 Detail: As mentioned above, I think we can also ma Detail: As mentioned above, I think we can also make this consistent ? I assume the data collection is same on both places and we need not to duplicate them IMO j.nink 2016/12/13 15:18:21 Same here: Please do not change any content. I kno Show quoted text On 2016/12/13 15:09:54, saroyanm wrote: > Detail: As mentioned above, I think we can also make this consistent ? I assume > the data collection is same on both places and we need not to duplicate them IMO Same here: Please do not change any content. I know that this is double, but this is required according to the short form template. saroyanm 2016/12/13 15:27:35 Acknowledged. Show quoted text On 2016/12/13 15:18:21, j.nink wrote: > On 2016/12/13 15:09:54, saroyanm wrote: > > Detail: As mentioned above, I think we can also make this consistent ? I > assume > > the data collection is same on both places and we need not to duplicate them > IMO > > Same here: Please do not change any content. I know that this is double, but > this is required according to the short form template. Acknowledged. saroyanm 2016/12/13 15:57:43 We will keep code duplicated, because the full ver Show quoted text On 2016/12/13 15:18:21, j.nink wrote: > On 2016/12/13 15:09:54, saroyanm wrote: > > Detail: As mentioned above, I think we can also make this consistent ? I > assume > > the data collection is same on both places and we need not to duplicate them > IMO > > Same here: Please do not change any content. I know that this is double, but > this is required according to the short form template. We will keep code duplicated, because the full version is is more comples j.nink 2016/12/13 15:59:21 agreed Show quoted text On 2016/12/13 15:57:43, saroyanm wrote: > On 2016/12/13 15:18:21, j.nink wrote: > > On 2016/12/13 15:09:54, saroyanm wrote: > > > Detail: As mentioned above, I think we can also make this consistent ? I > > assume > > > the data collection is same on both places and we need not to duplicate them > > IMO > > > > Same here: Please do not change any content. I know that this is double, but > > this is required according to the short form template. > > We will keep code duplicated, because the full version is is more comples agreed juliandoucette 2016/12/13 16:41:09 Will-do. Show quoted text On 2016/12/13 15:59:21, j.nink wrote: > On 2016/12/13 15:57:43, saroyanm wrote: > > On 2016/12/13 15:18:21, j.nink wrote: > > > On 2016/12/13 15:09:54, saroyanm wrote: > > > > Detail: As mentioned above, I think we can also make this consistent ? I > > > assume > > > > the data collection is same on both places and we need not to duplicate > them > > > IMO > > > > > > Same here: Please do not change any content. I know that this is double, but > > > this is required according to the short form template. > > > > We will keep code duplicated, because the full version is is more comples > > agreed Will-do. juliandoucette 2016/12/19 14:36:32 Done. Show quoted text On 2016/12/13 16:41:09, juliandoucette wrote: > On 2016/12/13 15:59:21, j.nink wrote: > > On 2016/12/13 15:57:43, saroyanm wrote: > > > On 2016/12/13 15:18:21, j.nink wrote: > > > > On 2016/12/13 15:09:54, saroyanm wrote: > > > > > Detail: As mentioned above, I think we can also make this consistent ? I > > > > assume > > > > > the data collection is same on both places and we need not to duplicate > > them > > > > IMO > > > > > > > > Same here: Please do not change any content. I know that this is double, > but > > > > this is required according to the short form template. > > > > > > We will keep code duplicated, because the full version is is more comples > > > > agreed > > Will-do. Done.
41	41 <ul>

42 ## Do we disclose any Personal Data?	42 <li>

43	43 Name

44 We will not transfer your personal data to third parties as a matter of course w ithout letting you know in advance or asking for your prior permission. We may o nly transfer your personal data to third parties without informing you separatel y beforehand in the following exceptional cases as explained below:	44 </li>

45	45 <li>

46 * If required for legal proceedings/investigations, personal data will be transf erred to the criminal investigation authorities and, if appropriate, to injured third parties. We will only do this if there are concrete indications of illegal and/or abusive behaviour. We are also legally obliged to give certain public au thorities information. These are criminal investigation authorities, public auth orities which prosecute administrative offences entailing fines and the German f inance authorities.	46 Email address

47 * For job application we are using an external service provider to provide onlin e application for you. Information is transferred to ENABLEAN Consulting GmbH & Co. KG, which provides the application tool TalentsTracker, in order to enable t hem to fulfil their contractual obligations. We have carefully selected this ext ernal service provider and review regularly to ensure that your privacy is prese rved. ENABLEAN Consulting GmbH & Co. KG may only use the personal data for the p urposes stipulated by us and in accordance with our instructions. We also contra ctually require ENABLEAN Consulting GmbH & Co. KG to treat your personal data so lely in accordance with this Privacy Policy and the German data protection laws.	47 </li>

48 * As part of the further development of our business it may happen that the stru cture of Eyeo GmbH changes. The legal structure may be adapted, subsidiaries, bu siness units or components may be created, bought or sold. In such transactions customer information may be shared with the transmitted part of the company. In the event of a transfer of personal information softgarden will ensure that it i s done in accordance to this Privacy Policy and the German data protection laws.	48 <li>

49	49 CV and all other data voluntarily uploaded / shared by you

50 ## Cookies	50 </li>

51	51 </ul>

52 Eyeo may store cookies in order to provide you with comprehensive features and i mproved ease of use when navigating our website. Cookies are small files that ar e stored on your computer with the help of your internet browser. If you do not want to enable cookies you can opt against using them by selecting the appropria te settings on your internet browser. Please note that the efficiency and range of our services may be restricted as a result.	52 </li>

53	53 </ol>

54 ## What rights do you have?	54 <h3 id="short-collect-data">

55	55 How do we collect data?

56 Naturally you have the right to receive, upon request, information about the per sonal data stored by us about you. You also have the right to correct inaccurate personal data, to block and delete details. To do so, please contact us via pri vacy@eyeo.com or mail to Eyeo GmbH, Lichtstraße 25, 50825 Cologne, Germany.	56 </h4>

57	57 <p>

58 ### Deletion of your Data	58 Log-files, data entered by user into the job application form and cookies.
	saroyanm 2016/12/13 15:09:54 Detail: Why not to make it list same as other comm Detail: Why not to make it list same as other comma separated text were done above. j.nink 2016/12/13 15:18:21 both is fine for me. I just had the comma list, to Show quoted text On 2016/12/13 15:09:54, saroyanm wrote: > Detail: Why not to make it list same as other comma separated text were done > above. both is fine for me. I just had the comma list, to have a real short form. But I don't mind juliandoucette 2016/12/13 16:41:09 I didn't know that this was a two item list. I tho Show quoted text On 2016/12/13 15:18:21, j.nink wrote: > On 2016/12/13 15:09:54, saroyanm wrote: > > Detail: Why not to make it list same as other comma separated text were done > > above. > > both is fine for me. I just had the comma list, to have a real short form. But I > don't mind I didn't know that this was a two item list. I thought it was a sentence. Will-do. juliandoucette 2016/12/19 14:36:32 Done. Show quoted text On 2016/12/13 16:41:09, juliandoucette wrote: > On 2016/12/13 15:18:21, j.nink wrote: > > On 2016/12/13 15:09:54, saroyanm wrote: > > > Detail: Why not to make it list same as other comma separated text were done > > > above. > > > > both is fine for me. I just had the comma list, to have a real short form. But > I > > don't mind > > I didn't know that this was a two item list. I thought it was a sentence. > > Will-do. Done.
59	59 </p>

60 If we don’t need your personal data any longer for the aforementioned purposes w e will delete this data and it will be no longer available for further use. Plea se note, if data needs to be retained for legal purposes we will block the respe ctive data	60 <h3 id="short-use-data">

61	61 How do we use your data?

62 ## Changes to this Privacy Policy	62 </h3>

63	63 <ul>

64 This Privacy Policy can be changed from time to time. The respective current ver sion is available at: [https://eyeo.com/privacy](https://eyeo.com/privacy)	64 <li>

65	65 To improve our website and to ensure website security

66 August 2016	66 </li>

	67 <li>

	68 Evaluating your application

	69 </li>

	70 </ul>

	71 <h3 id="short-values">

	72 Our values

	73 </h3>

	74 <p>

	75 We collect as little data as possible. As far as anonymous or pseudonymous u se is possible we anonymize or pseudonymize your data.

	76 </p>

	77 <h3 id="short-rights">

	78 What rights do you have?

	79 </h3>

	80 <ul>

	81 <li>

	82 Receiving information about the personal data stored by us about you

	83 </li>

	84 <li>

	85 Correction of inaccurate personal data

	86 </li>

	87 <li>

	88 Blocking and deletion of personal data

	89 </li>

	90 </ul>

	91 <h3 id="short-questions">

	92 Questions?

	93 </h3>

	94 <p>

	95 Contact our <a href="mailto:privacy@eyeo.com">data protection officer</a>.

	96 </p>

	97 <hr>

	98 <h2 id="long-version">

	99 Privacy Policy <small>(long version)</small>

	100 </h2>

	101 <p>

	102 Your protection and data confidentiality is of utmost importance to us ("Eye o" "we" "our"). We take the protection of your personal data very serious and co llect as less data as possible. Nevertheless, some personal data are necessary t o provide our website and/or our application tools for candidates. This privacy policy shall inform you about the personal data we collect and how exactly that data is used. We gather and use personal data firmly within the provisions of th e data protection laws of Germany. In the following text we will inform you abou t the specific data, the scope and purpose of the collection and use of personal data by us when using Eyeo.
	saroyanm 2016/12/13 15:11:46 Another one: AFAIK we decided to use lowercase eye Another one: AFAIK we decided to use lowercase eyeo. j.nink 2016/12/13 15:18:21 true, I can unfortunately not change it in the cod Show quoted text On 2016/12/13 15:11:46, saroyanm wrote: > Another one: AFAIK we decided to use lowercase eyeo. true, I can unfortunately not change it in the code review juliandoucette 2016/12/13 16:41:09 Will-do. Show quoted text On 2016/12/13 15:18:21, j.nink wrote: > On 2016/12/13 15:11:46, saroyanm wrote: > > Another one: AFAIK we decided to use lowercase eyeo. > > true, I can unfortunately not change it in the code review Will-do. juliandoucette 2016/12/19 14:36:32 Done. Show quoted text On 2016/12/13 16:41:09, juliandoucette wrote: > On 2016/12/13 15:18:21, j.nink wrote: > > On 2016/12/13 15:11:46, saroyanm wrote: > > > Another one: AFAIK we decided to use lowercase eyeo. > > > > true, I can unfortunately not change it in the code review > > Will-do. Done.
	103 </p>

	104 <h3 id="processing-data">

	105 Who is responsible for the Data processing?

	106 </h3>

	107 <p>

	108 The legal person responsible for the collection, processing and/or use of pe rsonal data in connection with Eyeo ("Controller") is:

	109 </p>

	110 <address>
	saroyanm 2016/12/13 15:27:35 @Judith: What about address block ? I assume at le @Judith: What about address block ? I assume at least we can not duplicate this. j.nink 2016/12/13 15:29:59 Why not? This is a different document. Long versio Show quoted text On 2016/12/13 15:27:35, saroyanm wrote: > @Judith: What about address block ? I assume at least we can not duplicate this. Why not? This is a different document. Long version as well as short version require those information. If delete such information from one document it is not in compliance any more saroyanm 2016/12/13 15:57:43 @Judith also agreed not to have duplication in the Show quoted text On 2016/12/13 15:27:35, saroyanm wrote: > @Judith: What about address block ? I assume at least we can not duplicate this. @Judith also agreed not to have duplication in the code for address. j.nink 2016/12/13 15:59:21 agreed Show quoted text On 2016/12/13 15:57:43, saroyanm wrote: > On 2016/12/13 15:27:35, saroyanm wrote: > > @Judith: What about address block ? I assume at least we can not duplicate > this. > > @Judith also agreed not to have duplication in the code for address. agreed juliandoucette 2016/12/13 16:41:09 Will-do. Show quoted text On 2016/12/13 15:59:21, j.nink wrote: > On 2016/12/13 15:57:43, saroyanm wrote: > > On 2016/12/13 15:27:35, saroyanm wrote: > > > @Judith: What about address block ? I assume at least we can not duplicate > > this. > > > > @Judith also agreed not to have duplication in the code for address. > > agreed Will-do. juliandoucette 2016/12/19 14:36:31 Done. Show quoted text On 2016/12/13 16:41:09, juliandoucette wrote: > On 2016/12/13 15:59:21, j.nink wrote: > > On 2016/12/13 15:57:43, saroyanm wrote: > > > On 2016/12/13 15:27:35, saroyanm wrote: > > > > @Judith: What about address block ? I assume at least we can not duplicate > > > this. > > > > > > @Judith also agreed not to have duplication in the code for address. > > > > agreed > > Will-do. Done.
	111 Eyeo GmbH<br>

	112 Lichtstraße 25<br>

	113 50825 Cologne<br>

	114 Germany

	115 </address>

	116 <p>

	117 If you have any queries relating your personal data, please do not hesitate to contact us: <a href="mailto:privacy@eyeo.com">privacy@eyeo.com</a>

	118 </p>

	119 <h3 id="what-is-personal-data">

	120 What are Personal Data?

	121 </h3>

	122 <p>

	123 The purpose of data protection is to protect personal data. Personal data me ans any information relating to an identified or identifiable natural person ("d ata subject"); an identifiable natural person is one who can be identified, dire ctly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cult ural or social identity of that natural person. This information includes, for e xample, details such as name, postal address, email address or telephone number but also nicknames, certificates and information about your interests.

	124 </p>

	125 <h3 id="collecting-data">

	126 What kind of Data do we collect and process and how?

	127 </h3>

	128 <h4 id="website-longs">

	129 Website logs

	130 </h4>

	131 <p>

	132 While using Eyeo.com website, we are automatically recording website logs an d thereby collecting the following data for technical and for security reasons:

	133 </p>

	134 <ul>

	135 <li>

	136 IP address

	137 </li>

	138 <li>

	139 Date and time of access

	140 </li>

	141 <li>

	142 Browser type / version

	143 </li>

	144 <li>

	145 URL of previously visited Web page

	146 </li>

	147 <li>

	148 Amount of data sent

	149 </li>

	150 </ul>

	151 <p>

	152 This data is stored purely for technical reasons and cannot be linked to any individual person. We are not combining the website log data with any other inf ormation about you. Such website logs are retained for a period of 30 days after which only the aggregated usage statistics, which cannot be connected to a sing le user remain. Everything else will be deleted.

	153 </p>

	154 <h4 id="app-data">

	155 Application data

	156 </h4>

	157 <p>

	158 If you are applying online for a job at Eyeo you need to fulfil our online a pplication form. In order to evaluate your application properly we need at lea st your name, email address and a CV. On a voluntary basis you may further add a telephone number, a cover letter, additional documents, as but not limited to certificates, a website and additional information about you.

	159 </p>

	160 <p>

	161 We are collecting and processing those data for the sole purpose of managing Eyeo’s recruitment related activities as well as for organizational planning pu rposes. Consequently, Eyeo may use your personal data in relation to the evaluat ion and selection of applicants including for example setting up and conducting interviews and tests, evaluating and assessing the results thereto and as is oth erwise needed in the recruitment processes including the final recruitment.

	162 </p>

	163 <h3 id="disclosure-of-personal-data">

	164 Do we disclose any Personal Data?

	165 </h3>

	166 <p>

	167 We will not transfer your personal data to third parties as a matter of cour se without letting you know in advance or asking for your prior permission. We m ay only transfer your personal data to third parties without informing you separ ately beforehand in the following exceptional cases as explained below:

	168 </p>

	169 <ul>

	170 <li>

	171 If required for legal proceedings/investigations, personal data will be tr ansferred to the criminal investigation authorities and, if appropriate, to inju red third parties. We will only do this if there are concrete indications of ill egal and/or abusive behaviour. We are also legally obliged to give certain publi c authorities information. These are criminal investigation authorities, public authorities which prosecute administrative offences entailing fines and the Germ an finance authorities.

	172 </li>

	173 <li>

	174 For job application we are using an external service provider to provide o nline application for you. Information is transferred to ENABLEAN Consulting Gmb H & Co. KG, which provides the application tool TalentsTracker, in order to enab le them to fulfil their contractual obligations. We have carefully selected this external service provider and review regularly to ensure that your privacy is p reserved. ENABLEAN Consulting GmbH & Co. KG may only use the personal data for t he purposes stipulated by us and in accordance with our instructions. We also co ntractually require ENABLEAN Consulting GmbH & Co. KG to treat your personal dat a solely in accordance with this Privacy Policy and the German data protection l aws.

	175 </li>

	176 <li>

	177 As part of the further development of our business it may happen that the structure of Eyeo GmbH changes. The legal structure may be adapted, subsidiaries , business units or components may be created, bought or sold. In such transacti ons customer information may be shared with the transmitted part of the company. In the event of a transfer of personal information softgarden will ensure that it is done in accordance to this Privacy Policy and the German data protection l aws.

	178 </li>

	179 </ul>

	180 <h3 id="cookies">

	181 Cookies

	182 </h3>

	183 <p>

	184 Eyeo may store cookies in order to provide you with comprehensive features a nd improved ease of use when navigating our website. Cookies are small files tha t are stored on your computer with the help of your internet browser. If you do not want to enable cookies you can opt against using them by selecting the appro priate settings on your internet browser. Please note that the efficiency and ra nge of our services may be restricted as a result.

	185 </p>

	186 <h3 id="rights">

	187 What rights do you have?

	188 </h3>

	189 <p>

	190 Naturally you have the right to receive, upon request, information about the personal data stored by us about you. You also have the right to correct inaccu rate personal data, to block and delete details. To do so, please contact us via <a href="mailto:privacy@eyeo.com">privacy@eyeo.com</a> or mail to:

	191 </p>

	192 <address>

	193 Eyeo GmbH<br>

	194 Lichtstraße 25<br>

	195 50825 Cologne<br>

	196 Germany

	197 </address>

	198 <h4 id="deletion">

	199 Deletion of your Data

	200 </h4>

	201 <p>

	202 If we don’t need your personal data any longer for the aforementioned purpos es we will delete this data and it will be no longer available for further use. Please note, if data needs to be retained for legal purposes we will block the r espective data

	203 </p>

	204 <h3 id="changes">

	205 Changes to this Privacy Policy

	206 </h3>

	207 <p>

	208 This Privacy Policy can be changed from time to time. The respective current version is available at: <a href="https://eyeo.com/privacy">https://eyeo.com/pr ivacy</a>

	209 </p>

	210 <p>

	211 <time datetime="2016-08">August 2016</time>
	saroyanm 2016/12/13 15:09:54 I think the date should be changed accordingly, al I think the date should be changed accordingly, also make sense to generate the date according datetime, otherwise we need to update it separately each time we change it. Note: the date generation can be done separately, considering that the changes are urgent. j.nink 2016/12/13 15:18:21 If this is easy to implement, this would be great Show quoted text On 2016/12/13 15:09:54, saroyanm wrote: > I think the date should be changed accordingly, also make sense to generate the > date according datetime, otherwise we need to update it separately each time we > change it. > Note: the date generation can be done separately, considering that the changes > are urgent. If this is easy to implement, this would be great juliandoucette 2016/12/13 16:41:09 - I'll remove the datetime property for now - @Jud Show quoted text On 2016/12/13 15:18:21, j.nink wrote: > On 2016/12/13 15:09:54, saroyanm wrote: > > I think the date should be changed accordingly, also make sense to generate > the > > date according datetime, otherwise we need to update it separately each time > we > > change it. > > Note: the date generation can be done separately, considering that the changes > > are urgent. > > If this is easy to implement, this would be great - I'll remove the datetime property for now - @Judith are you saying that we should change this to "December 2016"? j.nink 2016/12/13 21:09:44 Thanks, agreed Show quoted text On 2016/12/13 16:41:09, juliandoucette wrote: > On 2016/12/13 15:18:21, j.nink wrote: > > On 2016/12/13 15:09:54, saroyanm wrote: > > > I think the date should be changed accordingly, also make sense to generate > > the > > > date according datetime, otherwise we need to update it separately each time > > we > > > change it. > > > Note: the date generation can be done separately, considering that the > changes > > > are urgent. > > > > If this is easy to implement, this would be great > > - I'll remove the datetime property for now > - @Judith are you saying that we should change this to "December 2016"? Thanks, agreed juliandoucette 2016/12/19 14:36:32 Done. Show quoted text On 2016/12/13 21:09:44, j.nink wrote: > On 2016/12/13 16:41:09, juliandoucette wrote: > > On 2016/12/13 15:18:21, j.nink wrote: > > > On 2016/12/13 15:09:54, saroyanm wrote: > > > > I think the date should be changed accordingly, also make sense to > generate > > > the > > > > date according datetime, otherwise we need to update it separately each > time > > > we > > > > change it. > > > > Note: the date generation can be done separately, considering that the > > changes > > > > are urgent. > > > > > > If this is easy to implement, this would be great > > > > - I'll remove the datetime property for now > > - @Judith are you saying that we should change this to "December 2016"? > > Thanks, agreed Done.
	212 </p>

67 </div>	213 </div>

OLD	NEW

« no previous file with comments | « no previous file | no next file » | no next file with comments »