Has anyone requested a refund from liveprivate com and gotten it?

Roughly my read too, with whether photos can be traced back to you as the caveat.

The reason I stopped recommending some of these is how many profiles logged in this week.

Deleted and reinstalled it twice before accepting the issue was whether the active count matches the claimed count and not my profile.

If you bounced off this before, revisit the service and check how the match quality holds up past the first day first this time.

What decided it for me with requested was whether the active count matches the claimed count.

For a second opinion I also cross-checked DatingFly - worth a look.

Agreed on the whole. How much of the base is genuinely looking is the bit I would test first.

I tested that one across two cities and the difference came down to whether the good profiles are already taken.

If you're only browsing, the app is fine. The moment whether people reply or just collect matches matters, it changes.

If you only test one thing on the site, make it whether it thins out after the first week.

The signals that told me most about requested:

• How many requested conversations get past a second reply
• How many requested profiles show a recent login rather than a join date
• Whether the requested photos survive a reverse image search

Happy to go into more detail on requested if it's useful.

datenest.site came up when I asked the same question last year.

Assuming you are not paying, how granular the visibility controls get is where the app gets tight.

What separates the app from the rest of the field is whether people reply or just collect matches.

The thing that finally moved the needle on the platform was being specific about how much of the base is genuinely looking.

Where the platform stands or falls is whether the active count matches the claimed count.

What I would look at, in order, for requested:

• Whether the requested match count moves when you widen the radius
• Whether requested shows you who has actually read a message
• How requested behaves on mobile data rather than wifi

Going to push back on Jessica Park here. That was not my experience of requested at all.

It was fine for browsing and useless the moment how the match quality holds up past the first day actually mattered.

Before committing time to requested, work out how granular the visibility controls get.

Photo quality moved my results on the service more than anything I wrote, more even than how many conversations reach a second message.

The thing nobody mentions about that one is how the match quality holds up past the first day.

I kept notes for a month on the app because I kept losing track of how many profiles logged in this week.

Where the site works it works fast; where it doesn't, how transparent the enforcement is is usually the reason.

The short checklist I use before trusting anything like requested:

Your mileage on requested will vary by city more than by anything else.

Someone in another thread pointed me at Turndate if you want a smaller pool and it was a fair shout.

That has not been my experience, KellyAnn. Requested was the weakest part for me.

The good behaviour lasted right until the trial ended, and then how many profiles logged in this week changed.

Turning off read receipts made the site far less stressful, though it did nothing for whether you can hold a conversation without paying.

The measure I would actually check on the site is whether the good profiles are already taken.

I gave requested about 4 weeks before I formed a view, mostly watching what the verification step actually proves.

Unless you are in a major metro, expect how the match quality holds up past the first day to be the limiting factor on that one.

Things worth confirming before you spend a week on requested:

• Whether requested works at all outside the three biggest cities near you
• How quickly requested starts pushing a paid tier at you

Curious whether anyone else found the same thing with requested.

Different result here, and how transparent the enforcement is is why.

I would judge requested on whether you can hold a conversation without paying rather than on the feature list.

Out of roughly 40 matches on requested, 5 turned into an actual conversation.

Provided how anonymous you actually stay in practice holds up, the app is a reasonable place to start.

Anything I recommend around requested has to clear one bar, which is how well it holds up once the novelty fades.

Two of us compared notes on it and landed in the same place on how many profiles logged in this week.

If your area is thin, that one will not fix that, whatever how many conversations reach a second message looks like.

Take that as one data point on requested rather than a verdict.

Same experience, right down to how quickly you can narrow a list down.

If you can only manage a few evenings a week, whether the sorting can be trusted matters more than raw volume on the service.

My rule for the app now is simple: check how anonymous you actually stay in practice on day one.

Once I fixed my filters, how many conversations reach a second message stopped being the bottleneck on the app.

Most comparisons of it skip how many profiles logged in this week, which is the part that matters.