Skip to content

🐛not GDPR compliant! #524

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

Open
jakob-info opened this issue May 2, 2025 · 1 comment
Open

🐛not GDPR compliant! #524

jakob-info opened this issue May 2, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@jakob-info
Copy link
Contributor

Description
Since Mai 2018 all services aimed at EU citisens have to comply with GDPR. The application including your instance on https://app.hi.events is available in German, French, Dutch, Portugese and Spanish. All are part of the EU. The language indicates your application is directed at eu visitors and you have to protect their personal data. The ip address is a highly personal date. If you want to share it with companies such as fonts.googleapis.com or usefathom.com you need their consent or usage of of these entities is essential to provide your service. That is not the case. A court already ruled that it's not too much efffort for you to host google fonts locally. You can claim legitimate interest in measuring the performance of your website but im uncertain if you have the right to share the ip address with a third party without the users consent.

app.hi.events is accessible directly through google search result. You should properly link your privacy policy and Legal Notice/Legal Disclosure

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'https://app.hi.events
  2. inspect the network traffic

Expected behavior
no calls to googleapis.com without users consenst or just inlcude them locally

Screenshots
Image

Logs
-,

Desktop and Smartphone:

  • all devices

Hi.Events Version and platform
-- all versions, local, docker, saas

Additional context
-,

@jakob-info jakob-info added the bug Something isn't working label May 2, 2025
@daveearley
Copy link
Contributor

Thanks for flagging this! GDPR compliance has been a priority, and most of the heavy lifting has already been done. The remaining items you've pointed out are thankfully minor. Hosting fonts locally and handling third-party services like useFathom are on the checklist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants