Chatwith
Every change, in order — the continuous timeline of everything we ship.
Updates to our Privacy Policy & DPA
We've updated our privacy policy and Data Processing Agreement to clearly cover how session context is handled when your chatbot is installed on your site.
This gives you and your compliance team complete transparency about the data flowing through Chatwith, making it easier to confidently roll out chatbots in regulated environments.
Smoother Zapier Integration with v2 Support
Your Zapier integrations just got more flexible. We've added support for Zapier v2 alongside v1, so existing Zaps keep working while new ones can take advantage of improved authentication and richer responses.
What's new under the hood:
- Per-user API key authentication scoped to your own webhooks for tighter security
- Action endpoints now return useful status and trigger details instead of empty responses
- Optional Zap-specific IDs when subscribing or unsubscribing webhooks, making cleanup more precise
- Full backwards compatibility — no action required for existing Zaps
Why it matters: you get better visibility into what your automations are doing and stronger per-user security, without breaking a single existing workflow.
Stay in the Loop with In-App Release Notes
We've added a release pad directly inside your dashboard, so you can discover the latest updates, improvements, and fixes without ever leaving chatwith.
No more hunting through changelogs or missing important announcements — every new feature and improvement is now just a click away from where you work.
Auto-Reset Embed Conversations on a Schedule
Embedded chatbots can now automatically start a fresh conversation after a set number of hours, so visitors on your site always get a clean slate without needing to click reset.
Why it matters: anonymous embed visitors had their conversations persisted in localStorage indefinitely, and the manual reset button isn't reachable from cross-origin host pages. Now you can keep conversations relevant, protect privacy on shared devices, and avoid stale context — all with zero custom JavaScript.
- Configure the reset window directly in the General settings tab with the new "Auto-reset conversations" field.
- Override the default per-embed using the ?resetAfterHours= URL parameter (decimals like 0.5 for 30 minutes are supported).
- Manual resets via the header button also restart the clock, keeping behavior consistent.
- Leave the setting empty to keep the existing indefinite-persistence behavior.