I want to take a moment to share how we’re committed to protecting your users’ privacy and staying GDPR compliant.

1. What We Collect (and What We Don’t!)

We collect and process limited personal data from your users:

• Emails and conversations shared through the Tiny Chat widget.

• IP addresses (to prevent spam and ensure your chat is safe from bots).

👉 Rest assured, we do not fingerprint browsers or track users unnecessarily.

2. Local Storage: Keeping Conversations Seamless

We store a small amount of data in their browser’s local storage:

• Current Chat ID: This ensures that users can continue their conversations even if they close their browser and return later.

• Chat Widget States: For example, whether a conversation has started or if there’s a “new message notification.”

3. Hosting and Data Handling

• We’ve stopped using external services like Google Fonts API and AWS CloudFront for our widget.

• All HTTP calls from the widget are made directly to our servers in France. 🇫🇷

• Your customers messages and emails are sent to Slack, you can read Slack statement about GDPR here.

4. Transparency in Email Collection

By default, your widget will explain to users why you’re collecting their email:

“This will allow us to respond to you by email if we are not present.”

If you plan to use emails for newsletters or updates, it’s simple to modify the text via your dashboard:

“This allows us to respond to you by email and send you updates about our product.”

This way, your users know exactly how their data will be used!

5. Limited Data Retention

We believe in keeping only what’s necessary:

• Emails and conversations stored in Tiny Chat are deleted after 1 year.

• However, Slack retains your chat data, so you’ll need to manage retention settings on your Slack workspace.

6. In Case of a Data Breach

If a data breach ever occurs, we’ll notify you promptly via a message in your Slack #tiny-chat channel.

7. Enhanced Privacy with Encryption

Soon, you’ll have the option to enable a privacy-first feature that prevents Slack from reading customer messages or emails.

• Instead of sending raw messages to Slack, we’ll send a secure link like https://tiny-chat.com/decrypt?content=324Efds.

• To access the content, you’ll enter a password—keeping sensitive data out of Slack’s reach.

If you have any questions, ideas, or feedback, I’d love to hear from you.