← back to swap

Security

Technical controls for the CryptoConvert swap interface.

Non-custodial design

We never ask for private keys. Swaps are routed to ff.io; settlement happens on-chain through that provider.

Server-side API

All exchange API calls and HMAC signing run on the server. API secrets are not exposed to the browser.

Abuse prevention

Rate limiting (Upstash Redis in production), CAPTCHA on swap creation, and input validation on addresses and amounts.

Browser protections

Content Security Policy, X-Frame-Options, HSTS, and strict referrer policy reduce XSS, clickjacking, and mixed-content risk.

Logging

Logs are minimized and redact sensitive fields (addresses, tokens, secrets).

Report an issue

If you discover a security concern, contact us through the support page with details so we can investigate.