Product support
Setup, changelogs, widgets, feature requests, subscribers, custom domains, and billing questions.
Support
Reach the team that runs RelayFast.
Send product, billing, privacy, or security questions to one monitored inbox. Include enough project context so we can trace the exact surface quickly.
support inbox
Contact email
Project URL attached
Account email included
Issue area named
Security reports
Include the affected route, account state, reproduction steps, and any evidence needed to understand impact.
Routing
One support path, routed by the issue.
Use the same address for customer questions, operational help, privacy requests, and security reports. Clear context helps us answer with fewer back-and-forth steps.
Privacy requests
Account data, subscriber data, deletion, export, and other privacy-related requests.
Security reports
Responsible disclosure for suspected vulnerabilities or account security concerns.
What to include
Give us the product trail, not just the symptom.
RelayFast usually needs the project URL, account email, and the exact product area to identify the issue. Screenshots are useful when the problem is visual or state-specific.
01
Your RelayFast account email
02
The project URL or custom domain
03
The post, request, widget, or billing area involved
04
What you expected to happen and what happened instead
