Privacy Policy for the use of Lope

1. Gene­ral
Per­so­nal infor­ma­ti­on is infor­ma­ti­on that may dis­c­lo­se or dis­c­lo­se the iden­ti­ty of the user. We adhe­re to the princip­le of data avo­id­ance. As far as pos­si­ble, the collec­tion of per­so­nal data is wai­ved.
1.2 Hand­ling of per­so­nal data
Per­so­nal data are used exclu­si­ve­ly for estab­li­shing the con­tract, con­tent, exe­cu­ti­on or exe­cu­ti­on of the con­trac­tu­al rela­ti­ons­hip (Art. 6 I b DSGVO). They are not pas­sed on to third par­ties.
Sin­ce the pro­ces­sing of purcha­ses and pay­ments with the necessa­ry pay­ment data takes place exclu­si­ve­ly through the App Stores, over which Lope is avail­ab­le, we recei­ve con­cre­te buy­er data only if the purcha­sers con­tact us sepa­r­ate­ly with their con­cerns.
1.3 Data Access
Instal­ling and using the app gives Lope access to the fol­lo­wing types of data:
‚ÄĘ In-app purcha¬≠ses (for later purcha¬≠se of the full ver¬≠si¬≠on)
‚ÄĘ Pro¬≠fi¬≠le data (for ‚Äď vol¬≠un¬≠ta¬≠ry ‚Äď back¬≠up of the cur¬≠rent data on Goog¬≠le dri¬≠ve)
‚ÄĘ Calen¬≠dar (to read and dis¬≠play mee¬≠ting data and com¬≠pu¬≠te occup¬≠an¬≠cy and coverage)
‚ÄĘ micro¬≠pho¬≠ne (for voice input of tasks)
If you do not want any of the­se, plea­se renoun­ce the use of Lope.
1.4 Par­ties invol­ved
The data of Lope are basi­cal­ly only acces­si­ble to the two par­ties invol­ved: The App Lope was con­cei­ved by denk­bar ein­fach GmbH. It has inst­ruc­ted the
2OrgU GmbH
August Wil¬≠helm K√ľhn¬≠holz-Str. 5
26135 Olden­burg
with the tech­ni­cal rea­li­za­ti­on as well as the tech­ni­cal eva­lua­ti­on, as for examp­le from crash reports, for the pur­po­se of the impro­ve­ment and advan­ce­ment of the app.
1.5 Regis­tra­ti­on Data
No regis­tra­ti­on is requi­red for the full use of Lope.
1.6 Dura­ti­on of sto­rage
We store your per­so­nal data after the end of the pur­po­se for which the data was collec­ted, only as long as requi­red by law (in par­ti­cu­lar tax law).
2. Your rights
2.1 Infor­ma­ti­on

You can ask us for infor­ma­ti­on about whe­ther we pro­cess per­so­nal data of you and if so you have a right to infor­ma­ti­on about the­se per­so­nal data and on the other infor­ma­ti­on men­tio­ned in Art. 15 DSGVO (Ger­man law for data pro­tec­tion).
2.2 Right to rec­tifi­ca­ti­on
You have the right to cor­rect incor­rect per­so­nal data rela­ting to you and may request the com­ple­ti­on of incom­ple­te per­so­nal data in accordance with Art. 16 DSGVO.
2.3 Right to can­cel­la­ti­on
You have the right to demand that the per­so­nal data con­cer­ning you be dele­ted imme­dia­te­ly. We are obli­ged to dele­te them imme­dia­te­ly, espe­ci­al­ly if one of the fol­lo­wing rea­sons app­lies:
‚ÄĘ Your per¬≠so¬≠nal infor¬≠ma¬≠ti¬≠on is no lon¬≠ger necessa¬≠ry for the pur¬≠po¬≠ses for which it was collec¬≠ted or other¬≠wi¬≠se pro¬≠ces¬≠sed.
‚ÄĘ You revo¬≠ke your con¬≠sent to the pro¬≠ces¬≠sing of your data and the¬≠re is no other legal basis for pro¬≠ces¬≠sing.
‚ÄĘ Your data was pro¬≠ces¬≠sed unlaw¬≠ful¬≠ly.
The right to dele­te does not exist if your per­so­nal data are necessa­ry for the asser­ti­on, exer­ci­se or defen­se of our legal rights.
2.4 Right to restric­tion of pro­ces­sing
You have the right to demand that we restrict the pro­ces­sing of your per­so­nal data if
‚ÄĘ you deny the accu¬≠ra¬≠cy of the data and we the¬≠re¬≠fo¬≠re check the accu¬≠ra¬≠cy,
‚ÄĘ the pro¬≠ces¬≠sing is unlaw¬≠ful and you refu¬≠se the dele¬≠ti¬≠on and ins¬≠tead demand the restric¬≠tion of use
‚ÄĘ we no lon¬≠ger need the data, but you need it to assert, exer¬≠ci¬≠se or defend legal claims,
‚ÄĘ You have objec¬≠ted to the pro¬≠ces¬≠sing of your data, and it is not yet clear whe¬≠ther our legi¬≠ti¬≠ma¬≠te rea¬≠sons out¬≠weigh your rea¬≠sons.
2.5 Right to Data Por­ta­bi­li­ty
You have the right to recei­ve the per­so­nal infor­ma­ti­on you pro­vi­de to us in a struc­tu­red, com­mon and machi­ne-read­a­ble for­mat and you have the right to trans­fer this data to ano­t­her per­son wit­hout hin­dran­ce from us, pro­vi­ded the pro­ces­sing is based on your con­sent or a con­tract and pro­ces­sing is done by us using auto­ma­ted pro­ce­du­res.
2.6 Right of with­dra­wal
As far as the pro­ces­sing of your per­so­nal data is based on a con­sent, you have the right to revo­ke this con­sent at any time.
2.7 Gene­ral and the right to com­p­lain
The exer­ci­se of your above rights is basi­cal­ly free of char­ge. You have the right to con­tact the respon­si­ble super­vi­so­ry aut­ho­ri­ty, the sta­te data pro­tec­tion offi­cer, direc­t­ly in case of com­p­laints.
3. Use of Goog­le Fire­ba­se
Lope uses Goog¬≠le Fire¬≠ba¬≠se tech¬≠no¬≠lo¬≠gy (Goog¬≠le Inc., 1600 Amphi¬≠thea¬≠ter Park¬≠way, Moun¬≠tain View, CA 94043, USA, ‚ÄúGoog¬≠le‚ÄĚ). Fire¬≠ba¬≠se is part of Goog¬≠le Cloud Plat¬≠form and offers many ser¬≠vices to deve¬≠lo¬≠pers. A list can be found here: https://firebase.google.com/terms/. Some Fire¬≠ba¬≠se ser¬≠vices pro¬≠cess per¬≠so¬≠nal infor¬≠ma¬≠ti¬≠on. In most cases, the per¬≠so¬≠nal data is limi¬≠ted to so-cal¬≠led ‚Äúinstan¬≠ce IDs‚ÄĚ, which are pro¬≠vi¬≠ded with a time stamp. Firebase‚Äôs Instan¬≠ce IDs are uni¬≠que, allo¬≠wing you to link dif¬≠fe¬≠rent events or pro¬≠ces¬≠ses. The¬≠se data are neit¬≠her per¬≠so¬≠nal¬≠ly iden¬≠ti¬≠fia¬≠ble infor¬≠ma¬≠ti¬≠on nor do we make any effort to per¬≠so¬≠na¬≠li¬≠ze it after¬≠wards. We pro¬≠cess this sum¬≠ma¬≠ri¬≠zed data for the ana¬≠ly¬≠sis and opti¬≠mi¬≠za¬≠ti¬≠on of the usa¬≠ge beha¬≠vi¬≠or, as for examp¬≠le by the eva¬≠lua¬≠ti¬≠on of crash reports.
In addi¬≠ti¬≠on to the ‚ÄúInstan¬≠ce ID‚ÄĚ descri¬≠bed above, Goog¬≠le also uses the adver¬≠ti¬≠sing ID of the device for Fire¬≠ba¬≠se Ana¬≠ly¬≠tics. In the device set¬≠tings of your mobi¬≠le device you can restrict the use of the adver¬≠ti¬≠sing ID.
For Andro­id: Set­tings> Goog­le> Ads> Reset Adver­ti­sing ID
For iOS: Set­tings> Pri­va­cy> Adver­ti­sing> No Ad Tracking
4. Use of Goog­le Dri­ve
To maxi­mi­ze device chan­ge or loss con­ve­ni­en­ce, Lope pro­vi­des the abi­li­ty to back up the fol­lo­wing data in Goog­le Dri­ve:
‚ÄĘ Tasks
‚ÄĘ Memos
‚ÄĘ Set¬≠tings
Calen­dar data is not saved by Lope. For com­for­ta­ble sto­rage, Goog­le requi­res iden­ti­fi­ca­ti­on via the respec­tive user account. You can find more here https://support.google.com/drive/ as well as you when using the fea­ture for the first time.
5. Push messa­ges
Lope does not use push messa­ges.
6. Third par­ty ser­vices
The Lope app does not use any third-par­ty or con­tact ser­vices.
7. Con­tact
To con­tact us regar­ding pri­va­cy, plea­se feel free to con­tact us using the con­tact infor­ma­ti­on below. Respon­si­ble wit­hin the mea­ning of the DSGVO:
denk­bar ein­fach GmbH
August Wil¬≠helm K√ľhn¬≠holz-Str. 5
26135 Olden­burgre­p­re­sen­ted by its CEO Mr. Ingo Kör­ne­rE-Mail: info@lope.app