Security and privacy
Product safeguards, explained plainly.
A practical overview of how Nodify limits data collection and protects the workflows behind your buttons.
Controls in the product
Workspace routes require authentication. Channel credentials are encrypted at rest, outbound webhook destinations are checked, and rate limits protect public and authentication routes.
- Public click identifiers are opaque and input is validated.
- Notification credentials are not returned to the browser after storage.
- Security headers and request limits are applied by the application server.
Privacy choices
Nodify does not monitor email opens. The optional contact form is the explicit path for a visitor to provide identifying details.
- Core services are hosted in the European Union.
- IP data used for abuse controls is hashed and not exposed as visitor analytics.
- Account holders can export or delete their account data from the workspace.
Practical notes
This page is a product overview, not a certification or audit report.
The privacy policy remains the detailed source for processing purposes and service providers.
Report security concerns to tech@matikus.com.
Turn the next email into a clear next step.
Create a button, choose where alerts should arrive, and test the complete confirmation flow.