From environment isolation to role-based access, IP restrictions, and data residency controls — encatch is built for teams where security is not optional.
Security layers
Access Control
Domain locking
IP whitelisting
Role-based permissions
Environments
Sandbox isolation
Production promotion
No dev access to prod
API Keys
Domain-scoped
Env-scoped + expiry
Data Governance
Configurable retention
Audit log
Data residency
4
Access layers
2
Environments
Live
SSO
Sandbox environment
In most tools, configuring feedback requires developers and PMs to work in production — which means either giving developers production access, or constant back-and-forth coordination. encatch Sandbox breaks that model entirely. PMs configure forms, triggers, and screen paths in a fully isolated environment. Developers implement SDK events there. Once everything is validated together, the PM promotes the configuration to production — no developer ever touches it.
Sandbox
Safe to iterate
Production
PM-controlled
How teams work together
Configures feedback forms, triggers, and screen paths in Sandbox
Implements SDK events and URL paths in Sandbox — no production access needed
Reviews end-to-end in Sandbox. Approves and promotes config to Production
Production config goes live — developers never touched it
Sandbox usage does not count against production quotas
Access control
encatch's role system gives you surgical control over who can do what. Roles are defined at the organization level or scoped to individual projects — so your integration manager can manage webhooks without seeing feedback responses, and your feedback manager can analyze responses without touching API keys or billing.
Custom roles
Org Admin
Organization level
Feedback Manager
Project level
Integration Manager
Project level
Admin portal controls
Domain locking
Prevent unauthorized signups on your domain
IP whitelisting
Restrict admin access to trusted networks only
SSO (OIDC / SAML)
Enterprise identity provider integration
API keys
Every encatch API key is scoped at creation — to a specific domain or mobile bundle ID, and to an environment (sandbox or production). A frontend SDK key on your marketing site is sandboxed from your production environment. Keys expire automatically, reducing stale credential risk.
MYAPP_WEB · Production
Expires Jan 2026
Scope dimensions
Domain scope
app.myproduct.com
Environment
Production
Expiry
Configurable
Keys are shown once at generation — never stored. Separate keys for web domains and mobile bundle IDs.
Sandbox key
Production key
User identity signing
encatch API keys are public by design — they're embedded in your SDK. Without additional protection, anyone who extracts your key could forge user identity calls, create fake users, and inflate your MAU count. HMAC signatures close that gap entirely. Your server signs every identity payload using a secret key that never leaves your infrastructure. encatch verifies the signature before accepting any user creation — unsigned or tampered calls are rejected outright.
Identity verification
Trusted — server-signed
HMAC‑SHA256(userId + timestamp, secret_key)
Signed on your server — never in client code
Valid window: 5 minutes — replay attack prevented
encatch accepts · user created · MAU counted
Rejected — unsigned / forged
SDK call without valid signature
encatch rejects · no user created · no MAU charged
Algorithm
HMAC-SHA256
Stored where
Your server only
Time window
Configurable
MAU protection
Enforced
Data governance
encatch gives compliance teams the controls they need: configurable retention windows, automated data purging, immutable audit logs for every admin action, and data residency options as they roll out across regions. Every deletion, key revocation, and role change is logged — so your security team always knows what happened and when.
Data residency
India
LiveEuropean Union
Coming soonUnited States
Coming soonData retention
Retention window
Up to 2 yearsAudit log
admin@acme.com · retention_updated · 90 → 30 days
2h agodev@acme.com · api_key_revoked · MYAPP_WEB_OLD
5h agoadmin@acme.com · role_created · Integration Manager
1d agoCapabilities
From sandbox isolation to enterprise SSO — encatch gives IT admins and security teams the controls they need, without slowing down the product team.
Sandbox environment
Isolated project type for safe integration, testing, and PM review — no production usage charged.
Production promotion
PMs promote sandbox configs to production. Developers never need production access.
Custom roles
Define roles at org and project level — feedback manager, integration manager, system admin, and more.
Domain locking
Prevent unauthorized users on your domain from signing up to the admin portal.
IP whitelisting
Restrict admin portal access to trusted IP addresses and corporate networks.
SSO (OIDC / SAML)
Enterprise single sign-on integration with your identity provider — OIDC and SAML supported.
API key scoping
Keys scoped to specific domains, environments (sandbox/production), and permission types.
Data residency
Currently hosted in India. EU and US regions available on request — coming soon.
Audit log
Immutable log of every admin action — retention changes, key revocations, role updates.
Configurable retention
Set your data retention window from 3 months up to 2 years. Records purged automatically.
Sandbox rate limits
Lower rate limits in sandbox protect the platform while giving enough capacity for testing.
API key scoping
Keys scoped to specific domains, environments (sandbox/production), and expiry dates — no stale credentials.
HMAC identity signing
Server-side HMAC-SHA256 signatures verify every user identity call. Time-bound validity windows prevent replay attacks and protect MAU billing integrity.
Enterprise ready
Sandbox environments, granular roles, and API key scoping mean your team ships faster without compromising control. Talk to us about enterprise deployment options.