Teable is now GDPR compliant 🇪🇺

Hi everyone,

Earlier this month we committed to GDPR compliance with a target of March 2027. Today we’re happy to share that Teable is now GDPR compliant, months ahead of that target.

Thank you again to @steph47dh7 , @t.s.123.teable , @ChrisHK , @Javier_Pastora , and @Francesco_Li_Petri , and to everyone who raised this with us. Here’s what’s in place.

A DPA for every Teable Cloud workspace Our Data Processing Addendum covers GDPR, UK GDPR, and the Swiss FADP. It includes the EU Standard Contractual Clauses and the UK Addendum for international transfers, and it applies automatically, with no separate signature needed.

A representative in Europe We’ve appointed DataRep as our representative in the EU, the UK, and Switzerland, so you have a direct contact for data protection questions. Contact details are in our Privacy Policy.

Your data is not used to train AI models On Teable Cloud, our AI providers process your content only to complete your requests, and they are contractually prohibited from using it for training.

Transparency on subprocessors Our subprocessor list is public in the Trust Center. We give 30 days’ notice before adding a new one.

Self-hosting is still an option Run Teable on your own servers and keep your data on your own infrastructure.

What’s next SOC 2 Type 2 and ISO 27001 are underway. You can follow our progress, and find our policies, security controls, and subprocessors, at the Teable Trust Center.

Questions about compliance, or need help with a security review? Reply below.

6 Likes

Congrats and thank you !! :clap:t2::clap:t2::clap:t2:

I ahas to go to the self-hosted solution, but this is an awesome achievement for whom is using the cloud version from EU/UK/Swiss ! Congrats ! :heart:

2 Likes

Top

1 Like

Very good news! You guys are awesome!

1 Like

Thank you very much! So Glad!!!

1 Like

Thank you very much for the DPA and the transparent presentation! :handshake:
An important note for EU companies: The EU SCCs must be fully integrated into the DPA and attached as annexes.

Simply naming them or referring to them without providing the complete text accessible at all times and fully completed annexes is not sufficient for effectiveness, as otherwise the DPA remains invalid for the EU. Specifically, Module 2 (Controller→Processor) and, if applicable, Module 3 (Processor→Processor) should be included in full text, along with Annex I (Parties/Transfer Description), Annex II (Technical and Organizational Measures), and Annex III (Sub-processors) completely enclosed.

This would be the decisive step for us EU customers toward legally secure use. Thank you for your efforts. We have already made significant progress. The SCCs are public and free templates that you can easily download, integrate, and complete from the official EU website. Thank you!:folded_hands: