Privacy controls
CyberFurl can load analytics only after you opt in. Core product features work without analytics consent.
This page now points to the real contact paths already referenced across the product: general support, security disclosures, and privacy or legal requests. Use the lane that matches the problem so the message lands with the right team faster.
Quick routing
Support and sales: contact@cyberfurl.com
Security: security@cyberfurl.com
Privacy: privacy@cyberfurl.com
Legal: legal@cyberfurl.com
General support and sales inquiries should include enough context to avoid a back-and-forth loop.
General, security, privacy, and legal issues now have explicit paths.
Current public pages identify CyberFurl as operating from New Delhi, India.
Use the public status route before filing an outage report when the issue may already be known.
Choose the right lane
Quick guidance on which inbox to use so your request reaches the correct team faster.
What to include
Domain, affected route, plan tier, and exact symptom or reproduction notes help the team triage faster.
Contact lanes
Replacing the old placeholder form with explicit routing makes the page clearer for users and more honest operationally.
Use the main inbox for product questions, onboarding help, plan comparisons, billing issues, and domain-specific support requests.
Report vulnerabilities, abuse, or sensitive security issues through the security inbox so they can be triaged separately from general support.
Use the dedicated legal inboxes for privacy requests, terms questions, procurement review, or policy-related follow-up.
Before you send
CyberFurl requests are easiest to triage when the first message already includes the affected domain, the route involved, and the exact symptom instead of a generic “it broke.”
Share the domain, the route you were using, the plan tier if relevant, and the exact issue you saw. A screenshot or copied error text speeds up triage.
Tell us how many domains you need to monitor, whether you need reporting or white-label output, and which alerting channels matter to your team.
Send the impacted route, reproduction steps, and any safe evidence required to validate the issue. Do not include destructive payloads or sensitive third-party data.
Availability
These links handle the most common pre-contact checks: operational status, product scope, and policy review.
Check the public status route first when you suspect an outage or degradation is broader than a single account.
Current public pages identify CyberFurl as operating from New Delhi, India, with email-first support across product, privacy, and legal questions.
If you are unsure which lane applies, use contact@cyberfurl.com and mention whether the issue is product support, procurement, or policy-related.
Next step
Start with live monitoring if you want to see current posture first, or email the team directly if you already know you need posture snapshots, white-label output, or recurring monitoring.