Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add tutanota.toml corrections #138

Merged
merged 4 commits into from
Sep 9, 2024
Merged

Conversation

ganthern
Copy link
Contributor

Type of pull request: product edit

Related issues: N/A


There's a few inaccuracies and/or misleading statements in the Tutanota survey.

@privacyspy-bot
Copy link

Thanks for submitting this pull request. @milesmcc has been assigned to review these changes, provide feedback, and determine next steps.

If you haven't already, please ensure your changes pass all the automated tests. Look in the "Checks" box below and "Files changed" tab to see test results.

To learn about the PrivacySpy contribution process, check out the contribution guide.

Note to maintainers: if this pull request passes all tests and code reviews, it should be squashed and merged.

@privacyspy-bot privacyspy-bot bot added size/S new contributor product Related to a product on PrivacySpy labels May 30, 2022
@milesmcc
Copy link
Collaborator

So this brings up an interesting case: What do we do when a company is legally required to follow certain rules based on their jurisdiction, but do not explicitly say so in their privacy policy? We've dealt with this question before, but it's worth reconsidering. @doamatto and @ibarakaiev — what do you all think?

notes = [
"Although their imprint describes them being based in Germany, Tutanota does not comply with Article 33 of the GDPR."
"Tutanota is based in Germany so it is legally obliged to notify users of data breaches, even if not listed in the privacy policy."
Copy link
Collaborator

@milesmcc milesmcc May 30, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this is quite right — our interpretation of GDPR article 33 is that the company must notify the supervisory authority, not users themselves:

In the case of a personal data breach, the controller shall without undue delay and, where feasible, not later than 72 hours after having become aware of it, notify the personal data breach to the supervisory authority competent in accordance with Article 55, unless the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons.

Copy link
Collaborator

@doamatto doamatto May 30, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Supervisory authority is defined in Art. 4, §22 and Art. 51

’supervisory authority’ means an independent public authority which is established by a Member State pursuant to Article 51

@doamatto
Copy link
Collaborator

There are really two ways to think of it: we can assume they’d play by the rules that they will notify of breaches, even if they don’t explicitly say they will, or we can have their word, per se, that they will.

I can’t say that I’m in favour of the optimistic or pessimistic view, but I do think it should be explicitly mentioned that they follow the policy.

@doamatto doamatto merged commit d23276d into Politiwatch:master Sep 9, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new contributor product Related to a product on PrivacySpy size/S
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants