The form at the bottom of this page writes your message into this site’s own database, where a person reads it. There is no ticketing system, no autoresponder, no support queue and no chat widget. Because this server has no mail server attached to it, the notification email that would normally accompany a submission is best-effort — the stored copy is the part that is reliable. Expect a reply in days rather than minutes, and expect it from a human.
What this form actually is
Most contact pages will not tell you what happens after you press Send, which is how people end up waiting a fortnight for an answer that was never coming. So here is the whole mechanism, in order.
You fill in the form. Your browser posts it to this site. The site checks that the fields are filled in sensibly, that the email address is a real address rather than a typo, and that the submission looks like a person rather than a script. If those checks pass, the message is written to the database as a private record — your name, your email, the topic you chose, your subject line and the full text of what you wrote. That record is the message. It sits there until it is read.
Then, and only as a second step, the site tries to send an email telling us the record exists. That attempt is allowed to fail without affecting anything you see, because on this particular server it is quite likely to.
Why the notification is best-effort, in plain terms
There is no mail server on this box
The machine that serves this site runs a web server and a database and nothing else. It has no mail transfer agent installed, and the domain has no MX records pointing at it, so it can neither reliably send email nor receive any. That is being fixed separately. Until it is, treat the notification as a bonus and the stored record as the delivery.
This is the same reasoning that runs through the rest of the site. The about page argues that a missing server is a stronger guarantee than a policy, because a policy can be changed quietly and a missing component cannot. The flip side of that argument is that when a piece of infrastructure is genuinely absent, we have to say so rather than let you assume it is there. A form that silently drops messages because wp_mail() failed would be exactly the kind of thing this site exists to avoid, so the form was built the other way round: store first, notify second, and never let the notification decide whether your message survived.
The practical consequence for you is that a submission which shows the confirmation message has been kept. If you do not hear back quickly, that is the reply time, not a lost message.
Reporting a wrong number or a bug in a tool
This is the most useful thing anyone can send, and it is worth saying why. Every calculator here shows its workings — the tier benchmark it compared against, the multipliers it applied, the arithmetic that produced the figure — precisely so the numbers can be argued with. If a result looks wrong to someone who knows their own niche better than a published benchmark does, that is information we cannot get any other way.
A report is actionable when it contains five things:
- Which tool. The page name or the URL is enough.
- The exact inputs. The follower count, the likes and comments, the niche, the time zone, the image dimensions — whatever you actually typed or opened. Approximations make a bug impossible to reproduce.
- What you expected. Including, if you have one, the source you were comparing against.
- What you got instead. The literal figure or behaviour on screen.
- Your browser. Name and rough version, and whether you are on a phone or a desktop. Image and canvas tools in particular behave differently across browsers.
If a tool failed to load rather than returning a bad number, open your browser’s developer tools, look at the console, and paste in any red error text. That one line usually shortens the diagnosis from hours to minutes.
A privacy or data question
The privacy policy covers what is and is not collected, key by key, including the browser local storage that a few tools write to on your own device. If something there is unclear, contradicted by what you observe in your own network tab, or simply missing, send it and the page will be corrected.
Formal data requests — access, correction, export, erasure — can be made through this form as well. The honest answer to most of them will be that no personal data is held to hand over, because the tools do not transmit anything and there is no account system. The exception is now this form itself: if you submit a message and later want it deleted, say so and include the email address you used, and the stored record will be removed.
Press and partnership
Questions about how the site is built, why it works the way it does, or how the benchmarks were sourced are welcome, and there is no PR filter in between. Requests for a quote or an interview will get a straight yes or no rather than silence. Please include your outlet and your deadline, because a deadline shorter than a week may simply not be met given the reply times described above.
What will not get a reply
Not as a rudeness, but so nobody wastes their time drafting one:
- Link-building outreach. Link exchanges, link insertions into existing pages, paid placements, “we noticed a broken link” openers.
- Guest post pitches. The guides here are written in-house and that is not changing.
- Requests to add affiliate links of any kind, including to tools and services that are perfectly legitimate.
- Requests to build a private-account viewer, a story viewer, or anything else that promises access to content someone chose not to make public. These do not work; the sites offering them are phishing or survey scams.
- Requests to build a follower-buying, like-buying or automation tool, or to integrate one.
The standing commitment, repeated here so it is on the record in one more place: this site will not carry affiliate links to follower-buying, engagement or automation services. Not now, and not later if the traffic gets big enough to make the offers tempting. If that ever changes, it will be announced on this page and on the about page before any link appears, not discovered by a reader.
Email us directly
If you would rather not use the form, these addresses reach the same place. Use the specific one where it applies — it gets your message read faster, and privacy and security requests are handled ahead of everything else.
| Address | Use it for |
|---|---|
| contact@stealthgram.in.net | Anything general: a question about a tool, a correction, feedback, or you are not sure which of the others fits. |
| bugs@stealthgram.in.net | A wrong number or a bug in a tool. Include the tool, the values you entered, what you expected and what you got, and your browser. |
| privacy@stealthgram.in.net | Privacy and data questions, and anything about what the site stores in your browser. |
| press@stealthgram.in.net | Press enquiries, interviews and partnership proposals. |
| security@stealthgram.in.net | Security reports. If you think you have found a vulnerability, please tell us here before disclosing it publicly. |
| legal@stealthgram.in.net | Legal notices, trademark questions and anything about the terms. |
Send a message
Every field is keyboard operable and labelled, and the form loads no third-party script — no CAPTCHA, no analytics, nothing that would tell another company you were here. Addresses are published above, one per purpose. The form remains the more reliable of the two, because a stored message cannot be lost to a spam filter or a mail misconfiguration — so if what you are sending genuinely matters, use the form and treat email as the convenience option.