API keys
Scoped and stored safely
Secret keys are shown once, stored hashed, tied to an app, and limited by scopes. Rotation and revocation let teams respond without changing unrelated integrations.
Security and privacy
Protect every key, tenant, and recipient.
HoneyNotify applies separate controls at the account, API, device, provider, webhook, and data-lifecycle layers.
Access control
Use the minimum authority each integration needs.
Public client keys
Safe client-side boundaries
Keys with the ps_public_ prefix are forced to device registration, event submission, and device removal. They cannot send notifications or administer an app.
Team accounts
Individual access and MFA
Organisation membership, role controls, MFA support, authentication throttling, and audit records reduce shared-secret and account-takeover risk.
Sensitive integrations
Credentials and callbacks stay verifiable.
Provider credentials
Encrypted outside application code
APNs, FCM, and Web Push credentials are encrypted at rest and managed separately from public SDK configuration. Validation catches malformed credentials before they reach delivery workers.
Signed webhooks
Authenticate every callback
Webhook deliveries include an HMAC-SHA256 signature and timestamp. Consumers can reject altered content and stale replay attempts before processing an event.
Destination safeguards
Safer outbound requests
Webhook URL validation protects against private-network destinations and other server-side request forgery patterns, while retry limits prevent uncontrolled delivery loops.
Verified identity
Prevent user impersonation
Apps can require a short-lived ES256 token from their backend before a client attaches an external user identity to a device.
Data lifecycle
Tenant-aware processing with deliberate retention.
Security also means limiting what remains available and for how long.
Isolation
App-scoped API queries
Devices, users, messages, segments, journeys, webhooks, events, and exports are resolved within the authenticated app and organisation context.
Retention
Configurable cleanup
Retention jobs remove aged event detail and disabled device data according to app settings while preserving records that remain operationally or legally required.
Privacy workflows
Export and account deletion
Company exports expire after 24 hours, and account deletion uses a scheduled workflow so the action can be controlled, audited, and processed consistently.
No internet service can guarantee absolute security. Keep server keys out of clients, rotate suspected credentials, restrict team access, validate webhook signatures, and avoid placing unnecessary sensitive data in notification content or metadata.
Integrate with least privilege from day one.
Use a public key in the SDK, a scoped secret key on your server, and verified identity where user association is sensitive.