Get in Touch
I'm Akshat Thakur, the developer behind MailMyCertificate. Questions, ideas, bug reports, or just want to say hi — I'd love to hear from you.
Content freshness: Last updated · First published
Prefer email?
Sometimes email just feels right.
akshatthakur22@gmail.com
I usually reply within a day or two.
Sometimes faster if I'm between commits.
Sometimes faster if I'm between commits.
Open Source
MailMyCertificate is open source. If you'd like to contribute, improve performance, or help shape the project — contributions are always welcome.
View GitHubWhat should you expect when you get in touch?
Honest answers about response times, where to report bugs, and what not to send.
- Who answers messages sent to MailMyCertificate?
- Akshat Thakur, the developer who wrote and maintains the project. There is no support team or ticketing layer in between, so replies come directly from the person who can change the code.
- How quickly will I get a reply?
- MailMyCertificate is a free open-source project maintained alongside other work, so replies usually arrive within a few days rather than within hours. Bug reports that block a live event are prioritised, so mention your event date if you have one.
- Where should I report a bug or request a feature?
- Open an issue on the GitHub repository at github.com/akshatthakur22/MailMyCertficate. Issues are public, searchable and get tracked properly, so they are far more effective than email for anything code-related.
- Can I contribute code to MailMyCertificate?
- Yes. The project is MIT licensed and accepts pull requests. Read CONTRIBUTING.md in the repository first, and look for issues tagged as good first issues if you want a smaller starting point.
- Should I email you my participant list if something goes wrong?
- No, and please do not. Participant names and email addresses never need to leave your device to diagnose a problem. Describe the symptom, the browser you used, and the column headers in your file instead.
- Do you offer paid support or custom development?
- There is no commercial support tier. For custom needs, the code is open source and MIT licensed, so you or your team are free to fork it and adapt it without asking permission.
Keep reading
Related workflows and answers from the rest of the site.
- Full step-by-step guideThe complete walkthrough: template setup, field mapping, generation and Gmail delivery.
- About the projectWho builds MailMyCertificate, why it exists, and how the local-first architecture works.
- Privacy policyExactly what stays on your device, what Google receives, and what is never collected.
- MailMyCertificate vs CertifierAn honest side-by-side, including the cases where Certifier is the better choice.
- Blog & guidesArticles on certificate creation, bulk delivery, best practices, and tool comparisons.
- Contact the maintainerQuestions, bug reports and feature requests, answered by the person who wrote the code.