ConsentKeep
Leightweight GDPR Consent Logging API for Startup
9 followers
Leightweight GDPR Consent Logging API for Startup
9 followers
Automate GDPR consent logging with screenshot proof, IP hashing, and CSV export. Audit-ready compliance in 10 minutes. Starts at $29/mo. Leightweight GDPR Consent Logging API for Solo Devs. Simple Integration - Works with vanilla JS, React, Next.js, or static sites. Google Consent Mode v2 - Seamless integration with Google Analytics, Google Ads, and Tag Manager.
A webhook trigger for consent revocations would be a really useful addition, since right now you have to poll for changes. Could you add support for sending a POST to a user-defined endpoint whenever a user withdraws consent, so downstream systems like mailing lists can react in real time?
@hamidekileci Great suggestion – polling is definitely not the cleanest approach 😅
We're actually working on webhooks right now. Should be live in the next couple of weeks. Would a simple POST with user ID, consent type, and timestamp cover your use case? Or do you need more fields?
Let us know – happy to tailor it before we ship.
Would love to see a built-in consent banner widget that auto-syncs with the API, right now I still need to build the UI separately and wire it up myself which kind of defeats the 10 minute promise.
@zgrhyz3 Fair point – and honestly, you're right 😅
The 10-minute promise should include the UI, not just the API. We're actually building a drop-in widget right now – just a few lines of code and you get a fully branded banner that auto-syncs with the API.
Hoping to ship it in the next 2-3 weeks. Would that solve the friction for you?
Love how quick this looks to set up, especially for solo projects. One thing that would really help: a webhook that fires whenever a user withdraws consent, so I can sync it with my own database in real time instead of waiting for the next CSV pull.
@bar191801 Thanks! 🙌 Quick setup is exactly what we were going for.
Webhook for consent revocation? That's actually brilliant – been hearing this from a few users too. Added to our roadmap.
Quick q: would you prefer a simple POST with the full payload, or per-event type (opt-in/out/withdrawal)?
Appreciate the feedback! 🙏
The screenshot proof feature is a smart move. It gives auditors something concrete to look at instead of just timestamps, which is exactly the kind of detail that makes compliance reviews feel less painful.
@turkbayyig96068 The screenshot proof feature is a smart move. It gives auditors something concrete to look at instead of just timestamps, which is exactly the kind of detail that makes compliance reviews feel less painful.
Honestly love how it just slots into vanilla JS without any weird wrappers, that's basically the kind of no-fuss integration solo devs actually need. The screenshot proof feature is a nice touch too.
@erdi0xqk Appreciate that! 🙌 Vanilla JS was definitely a deliberate choice – no React wrappers, no build tools, just drop it in and go. Exactly what I wanted as a solo dev myself.
And yeah, the screenshot proof came from a real audit panic moment 😅 Figured it'd save someone else the same headache.
Thanks for the kind words!
Love how lean the API is, especially the vanilla JS support. Most consent tools overengineer the integration but this drops in cleanly.
@mete1776580 Appreciate that! 🙌 "Lean" and "drops in cleanly" – exactly what we were aiming for.
Most CMPs feel like they're built for enterprise teams with dedicated compliance leads, not solo devs who just want to get it working and move on. Vanilla JS + minimal config was a deliberate choice.
Thanks for the feedback – means a lot! 🙏