Contact Us
One developer reads this inbox, from India, so replies come on IST working days rather than instantly. Email is the way in, and every address below reaches a person rather than a ticket queue.
Get in touch
| What you need | Where to write | Response |
|---|---|---|
| Support, bugs, account issues | [email protected] | within 2 business days |
| Billing and refunds | [email protected] | within 2 business days |
| Privacy, data access or deletion | [email protected] | within 30 days |
| Law enforcement requests | [email protected] | as promptly as we can |
| Complaints under the IT Rules, 2021 | [email protected] | acknowledged within 24 hours |
Reporting someone is faster in the app
If someone breaks the House Rules during a call, use the ⚑ report button on the call screen rather than email. It attaches the evidence automatically and lands directly in our moderation queue, which is how we act in minutes rather than days. Urgent safety concerns involving a minor or a credible threat: email us as well, with “URGENT” in the subject.
Complaints and grievances
Complaints about content, conduct, or your rights on Fyreflock go to a dedicated address that is read by a person, not a queue. This is our grievance channel under the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021.
| Stage | What happens | When |
|---|---|---|
| Acknowledgment | We confirm in writing that your complaint has been received, with a ticket reference. | within 24 hours |
| Resolution | We investigate, act, and write back telling you what we did. | within 15 days |
| Unlawful content or non-consensual imagery | Removed on receipt of a valid complaint, ahead of the full investigation. | within 24 hours |
Include your username, what happened, and roughly when. If it involves a specific conversation, an in-app ⚑ report attaches the evidence automatically and reaches us faster.
Who builds this
Fyreflock is built by a small independent team rather than a company, with security treated as a design constraint from the start rather than a review at the end. The things that follow from that are checkable rather than promised:
- Conversations are unreadable to us. Video, audio and live chat travel directly between the two devices where the networks allow, and through an encrypted relay where they do not. Either way the keys stay on the two devices, so there is nothing on our side to leak, subpoena or sell.
- Private group messages are sealed with a key we are never sent. It travels only in the fragment of an invite link, which browsers do not transmit to servers. Public community Roosts are the deliberate exception: their invite is meant to be posted publicly, so a fragment would keep the key secret from nobody, and we store it. Treat a Roost as readable by us, and a private group as not.
- Messages delete themselves within 24 hours at the outside, and anything left for an offline friend is the only thing that touches a server at all.
- Two-factor authentication via any authenticator app, with recovery codes, available to every account and mandatory for administrators.
- A live camera check before the queue, which runs entirely on your own device. No frame of it is uploaded, stored or seen by us.
Found something we got wrong? Write to [email protected] with “SECURITY” in the subject. Reports are read by a person, acted on, and never met with a lawyer.
Policies
Terms of Service · Privacy Policy · Refund & Cancellation Policy