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

No easily accessible Privacy Policy #18481

Open
SorryAward04 opened this issue Feb 26, 2025 · 2 comments
Open

No easily accessible Privacy Policy #18481

SorryAward04 opened this issue Feb 26, 2025 · 2 comments

Comments

@SorryAward04
Copy link

We were looking into darktable for our student organization, but while looking for a privacy policy, we could not find one - neither on the website at darktable.org nor in this repo.
We would like to hope this is just an error on our part, considering it's a requirement under GDPR to have one.
Until this is clear, we unfortunately cannot use darktable (yes, we are German).

I know that this has been at least partially addressed here - however, other software in tangential fields offer at least a short statement that their services do not collect personal data (e.g. paint.net, Krita, GIMP).
I hope that this topic is not a major issue (and also that the repo is the correct place for this).

@parafin
Copy link
Member

parafin commented Feb 26, 2025

Where does it say in GDPR that every peace of software must have a privacy policy? Does ls command have one?

If you're talking about website, then it's the wrong repo indeed - the right one is here: https://github.com/darktable-org/dtorg/issues

@MStraeten
Copy link
Collaborator

MStraeten commented Feb 26, 2025

We would like to hope this is just an error on our part, considering it's a requirement under GDPR to have one.

please be more precise on that by citing the relevant legal text.
There’s much bullshit around arguing spurious GDPR requirements especially in Germany ;)

To help: first identify who is providing services to you - the darktable team isn‘t.
Then identify, who is handling privacy relevant data in your local darktable installation - the darktable team isn‘t.

You can take the source and compile it yourself or use a precompiled software to provide a kind of service yourself (that’s importing images, tagging them)
If you use personal data to tag images, then that’s not a GDPR relevant service of the darktable team, but your own responsibility you need to care of following GDPR (if you’re in a country where GDPR is relevant)
So you need to write your own data privacy policy if you feel you need one when using darktable ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants