Contact

• Email: [email protected]
• Privacy requests: [email protected]
• Post: 414 Luff Ln, Redwood City, CA 94065, USA

Email beats every other option on speed. The postal address is meant for formal mail such as legal notices, and paper letters take however long the post takes. There is no contact form on the site yet; if one appears later, it will feed into this very inbox.

Every message gets read by me personally. With just one person behind the site, I cannot promise a reply within a fixed number of hours, but fixes always go to the front. A heads-up that a price is off or a rule has moved matters to every reader of that page, so it skips ahead of everything else.

• Corrections. Maybe a price rose, a free tier shrank, a plan got renamed or a policy now says something new. Send me the page link, the current wording on my page, what you are seeing now and the place you saw it. A dated screenshot of the app's pricing screen is ideal. Mention your country as well, since a number of apps price differently from region to region.
• Questions on a page. If something in a review or a list confuses you, just ask. When I think others will wonder too, the answer might get added to the page.
• Broken links. Tell me about any link that goes nowhere, or that goes somewhere its label never mentioned. An offer button leading to the wrong app is a bug, and I fix it.
• Apps you want covered. If an app you like is missing, send me its name. An app earns a record once people are looking it up and it is open to new sign-ups.

Forum threads and videos are good tips, but a record only changes once the app's own site, or a screen seen while signed in, confirms it.

A few changes are tricky to see from outside. A brand-new account may get a smaller free tier than an older one, or the phone app and the website may not match. If you ran into that, let me know how you created your account and on what device, so the page can explain both versions rather than choose one.

Coupons can be similar: a code might work on a fresh account and fail on an existing one, and when that happens the page ought to mention it.

You do not have to follow any format, though a clear subject line lets me find the right page quickly. Something that names the type of message, the app and the detail, for example a fix to one app's free message count or a question about another app's annual plan, tells me nearly everything before I even open it. One copy of each message is enough; I will see it.

If several pages are involved, one email with a short list beats a stack of separate ones, since I can then fix them all and rebuild in one go.

I can, however, point you the right way. Every review sets out the known cancel steps, refund rules and the merchant name on your statement for that app, each with its check date. If you bought it in Google Play or the Apple App Store, both cancelling and requesting a refund happen in that store.

For card payments on the web where the app stops answering, your card provider can walk you through a chargeback. And if your experience differs from what the review says, tell me, so I can fix the record before the next reader relies on it.

I also cannot give legal, money, medical or relationship advice. The site explains apps and their rules; it is not here to tell anybody how to run their life, and my email replies will not start doing that either.

Some requests are simply off limits. No company gets to see a page before it goes live, sign off on its wording, or pay to alter any fact, catch or label. Proposals for affiliate partnerships can come to the same email address.

The affiliate disclosure page covers the way partnerships run and the limits on what they can touch, so please look there first, since it answers most of what partners usually want to know.

If you believe my coverage of your product gets something wrong, quote the exact sentence and send me your source. Fixes happen in public and are dated on the corrections page.

Questions about personal data belong at the privacy address; the requests you are entitled to make are listed in the privacy policy.

Reporters and researchers are warmly welcome as well. If you are covering AI companion apps and need a fact confirmed, go ahead and ask. The site's records keep each app's prices, free allowances and policies with dates and sources, and I would happily send you straight to the original source so you do not have to cite me.

Just please keep my opinions labelled as opinions; my verdicts are one person's read of the evidence, not facts.

A real name is optional, and the facts are all I ever need from you. If you want to show me how a charge appears on a bank statement, trim the screenshot to just the merchant name and the amount, and hide your account details before sending; I never need anything beyond that.

When I make a fix, I update the record first, then every page that uses it gets rebuilt, and the fix goes into the public log. If you like, I will credit you there by first name, or keep you anonymous if you prefer.

A correction always goes through the same steps. I read what you wrote and open the source you included. If that source backs you up, the app's record gets the updated fact, a new date and the link.

Next I rebuild the site, and the updated fact replaces the old one everywhere it appeared, whether in the review, the lists or the comparison tables. Last, the fix goes into the corrections log, and I write back to tell you what changed. If your source does not back up the change, I write back anyway, explaining what it would take to confirm it.

A question gets an email answer. If I expect other readers to ask the same thing, I might also add the answer to the page it concerns, leaving your name off unless you want it included.

A page will not change just because someone wants it to sound nicer or tougher without a fact to back the request.

Everything else, from quick questions and harsh feedback to a simple "this page helped", gets read and gets an answer whenever one is needed.

Lots of questions already have answers on the trust pages. My editorial policy explains my sources and what each review label means. What My Virtual Girlfriend covers, and how it funds itself, is on the about page.

If you are asking about a single app, its review usually has the answer, either in the billing notes or the FAQ near the end. If not, write to me anyway; a question the page cannot answer shows me it needs more work. The site gets better with each message, and a quick note like "I got lost here" often helps more than a long review of the whole page. I am grateful for every one, so thanks for getting in touch.