Your audience stays yours.
EngageNudge is designed around data minimization, customer ownership, tenant isolation, secure key handling, export and clear retention controls.
Request security overviewBuilt for publisher trust
Customer-specific VAPID keys
Your push credentials stay tied to your origin, not shared across tenants.
Tenant isolation
Subscriber data, campaigns and analytics are scoped per publisher account.
Export and deletion
Audience export and deletion paths are documented, not hidden behind support tickets.
Encrypted endpoints
Push subscription endpoints are stored encrypted. We do not sell personal data.
GDPR-ready by design
EngageNudge is designed to support GDPR-compliant publisher implementations. The appropriate legal basis, permission flow, and transparency setup depend on your use and market. We document what we process and why.
What we disclose
- Customer content and event data categories
- Model providers and regions where language features apply
- Whether inputs are used for model training
- Retention, export and deletion controls
- Optional vs required intelligent features
- Human approval before send
- No sensitive-category inference by default
- Policy versioning and audit trail
- Subprocessors list on request
Useful intelligence requires visible control. Editors stay in charge of what goes out.
Your next loyal reader may already be on your website.
Give them a direct way back. Then know when that relationship is worth using.