RN
There is a version of this write-up that lists features, and it would be short work, because the operator lists them itself. The more useful thing to look at is which of Secret Desires' own documents a prospective customer can actually read before paying.
One of them is unusually good. The site publishes a security page with real engineering detail on it: full-volume AES-256 encryption at rest with a separate key per project, TLS terminated at Cloudflare, hosting at OVH under a stack of ISO 27000-series certifications, Firebase handling authentication so that passwords are never held locally, and named penetration-testing firms. It also states that a SOC 2 Type I and II audit is underway, dated to a specific month and naming the auditor. That is a page written by somebody who expected to be checked, and in a category where the usual disclosure is a padlock icon and the word "encrypted", it stands out.
Two other documents are not readable at all. The subscription page returns navigation and no plan content; `/premium` and `/pricing` are dead. The privacy policy and terms of service return their titles and nothing else, because the body renders client-side and never arrives for a plain fetch. So the two things that determine whether a subscription is a good idea — what it costs, and what the company is permitted to do with what you type — are, in practice, unreadable until you are already inside the product.
Affiliate pages will happily fill that gap. Search results for the pricing return a tier of review sites quoting monthly figures and a credit currency, and they do not agree with each other. None of that is restated here, because none of it is first-party and the category has an obvious incentive to publish a favourable number.
What the platform is claimed to do
Taken from the operator's own description: a companion you configure — appearance, voice, personality, interests, a backstory — which then holds text conversations with memory carried across sessions, generates images on request, produces voice notes and short video, and can place real-time calls. It also initiates contact rather than only responding, sending messages and images unprompted if permitted. The self-description is unambiguous about the content: an adult fantasy platform, with an FAQ stating an 18+ requirement.
Whether the experience lives up to that is not a question a fetch can answer, and this write-up does not pretend otherwise. What can be said is that the feature list is coherent — none of it depends on capability that does not exist in 2026 — and that "phone calls" and "video" are the two items where the gap between a demo and daily use tends to be widest across this whole category.
The claim worth reading carefully
The privacy statement on the security page is more specific than most, and it is also the one worth reading slowly.
The assertion is that upstream AI providers contractually guarantee zero retention, and that messages are processed and immediately discarded. Note what that covers and what it does not. It is a statement about the model providers' handling of inference traffic. It is not, on its face, a statement that the operator itself keeps no conversation history — and the product's advertised memory across sessions has to be built on something persisted somewhere. Those two things may well be reconcilable; the point is that the security page does not reconcile them, and the document that would, the privacy policy, is the one that will not load.
The gaps
Alongside the technical detail, the security page is silent on the questions that actually govern an adult generative platform: how age is verified beyond an assertion, what content is prohibited, how generation is moderated, and whether the likeness of a real person may be used to build a companion. That last one is not a hypothetical concern in this product category, and its absence from the published material is a real gap rather than an oversight worth assuming away.
The reasonable position
Secret Desires documents its infrastructure better than most of its competitors and its policy surface worse than it documents its infrastructure. If you are evaluating it, the two things to establish before paying are the current price on the account page and the actual text of the privacy policy and terms in a browser that will render them — specifically what is retained, for how long, and under what circumstances a human reads it. Those answers exist; they are simply not where a cautious reader would look for them first.