dojap
I know about the cookies frontend part, but what about the server side part compliance with GDPR and especially the websocket protocol and things it stores.
Is there anything I should be aware of?
Does Phoenix store some information that is GDPR important in the Database or somewhere else?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Practical resources that improve the lives of professional developers.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 6- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
kip
Phoenix itself does not store any information in a data store.So the platform itself does not have a material impact as a result of GDPR. What your application does matter though of course.
egze
In case you want to disable cookies and not worry about GDPR: https://byteflip.de/blog/cookieless-setup
wanton7
WebSocket protocol doesn’t have anything to do with GDPR. Check Cookies, the GDPR, and the ePrivacy Directive - GDPR.eu not all cookies need GDRP consent and browser local storage & session storage likely also fall in this same rules because law is not just about cookies. Anyway from there
Cookies can’t contain information that identify the person. So you can’t store users email or name in them for example. No login name in the cookie either but user id is probably ok.
You could even store just client id or authorization id in JWT token in the cookie instead user id for example that is then tied server side authorization that contains user id. That way user id is also kept out of browser cookies.
If you use some 3rd party browser analytics like azure application insights you likely need to show that GDRP consent popup. If you use azure application insights specifically then you might need extra steps to make it GDRP compliant so it won’t store cookie until user has given consent by setting
disableCookiesUsageto true until user has given consent. But I’m pretty sure lot of sites don’t do this and just let analytics create cookie before consent is given..josevalim
This is a misconception. You don’t need to disable cookies for GDPR compliance. All you have to do is not use cookies for tracking. Cookies for login and other functional cookies are totally fine.
dojap
So, the Phoenix.LiveDashboard.Router is fully GDPR compliant?
josevalim
Yes, it is.