
Minae Kurashiki
Lead Editor, Companion Chat & Roleplay
Handles
- Corrections
- Submit a Tool
Hentai AI Girlfriend
Pick the route that fits your message and include the details it asks for. That helps us verify issues, review submissions, and handle privacy requests cleanly.

Lead Editor, Companion Chat & Roleplay
Handles

Senior Reviewer, Image, Video & Voice
Areas of expertise

Security & Privacy Researcher
Handles
Every message goes to the same address. Start the subject with the tag below so it lands in the right queue.
[Correction]Corrections
Use this if you found a factual error in a review, guide, ranking note, or product detail on this site.
Read by Minae Kurashiki
[Tool Submission]Submit a Tool
Use this if you want our editors to consider a live adult AI tool for hands-on testing and possible coverage.
Read by Minae Kurashiki
If you are writing from a vendor side, keep it factual. Our scores, drawbacks, and verdicts are the editors' own, and a message to the inbox does not buy softer copy or a different ranking.
How this directory makes money[Privacy]Privacy Requests
Use this for data, deletion, takedown, or other privacy matters related to this site and its published content.
Read by Luz Marina Quispe
[Press]Press
Use this for journalist requests, quotes, background on our testing process, or questions about our editorial coverage.
[Commercial]Commercial Enquiries
Use this for advertising or other business-side enquiries about working with this publication.
[General]General Questions
Use this for anything that does not fit the other routes, including reader questions about how we test and update pages.
We read every message and aim to reply when a note needs an answer or follow-up.
No. We may review a submitted tool, ignore it, or revisit it later, but coverage and scoring stay with the editorial team. A commercial message does not change a ranking, remove a drawback, or secure inclusion.
No. Sending a tool for consideration is free. What matters is whether the product is live, testable, clearly adult-gated, and documented well enough for our editors to verify what it does.
We compare the claim on the page against sources we can check, such as the product itself, public documentation, policy pages, or a fresh re-test when needed. If the page is wrong, we update it; if the point is still disputed, we may ask for stronger evidence.
We review what content is affected, what action is being requested, and whether the requester has given enough information to verify the issue. We may ask for limited proof tied to the request, then update, remove, or decline based on what we can confirm.