Privacy Policy
Last updated:
Draft — test deployment. The operator details on this page are not set yet, and this document is not in force until they are.
This document is published in English only. The English version is the one that applies.
1. Who this policy is about
This policy explains what OnlyHot does with information about the people who use it. References to “we”, “us” and “our” below mean OnlyHot. References to “you” mean anyone who visits the site or holds an account on it.
The site is strictly for adults. Nobody under 18 may use it or hold an account, and we do not want their information at all. See the section on people under 18 below.
The service runs on one shared account system that also serves a sibling site of ours. If you have used both, the same account, credit balance, plan and history stand behind each of them, and this policy covers that shared record.
2. What we collect, and why we hold it
We keep the smallest set of information that lets an account work, be paid for, and be defended against abuse. Each category below says what it is and what it is for.
Account details. Your email address, a display name, and a photo URL if your sign-in method supplied one. If you sign in through Telegram, or pay through it, we also store the numeric account id it gives us. We hold these because they are what an account is: without them we cannot let you back in, address you, or show you your own history. If you signed up with a password, what we store is a bcrypt hash of it, never the password.
Sign-in material. One-time codes sent to your email address, which are short-lived and are cleared once used or replaced, and the session token issued when you sign in. These exist so that we can tell you apart from someone claiming to be you.
Credits and the ledger. Your credit balance, and one record for every movement of it: the amount, a machine-readable type, a short description and the time. If a member of our staff adjusts a balance, the record also names which staff account did it. The ledger is append-only — entries are added, never edited — because a balance nobody can reconcile is a balance we cannot honestly show you.
Your plan and your payments. Which tier and term you bought, when it expires, and one record per payment: the rail it came in on, what it was for, the amount, its status and the provider’s reference for it. We do not receive or store card numbers — no card is ever entered into this service. On the crypto rail we hold the order reference and the confirmation the processor reports; on the Telegram rail, the charge id it gives us, which is also what a reversal is matched against.
Referral records. A referral code of your own, a record of who introduced whom, the commission entries produced by a referred account’s payments, and the payout address you give us when you ask to withdraw. These exist to run the partner programme described in the terms.
Technical records. The IP address the account signed up from and the one most recently seen, a language code, a country code derived from the connection, and the times an account was created and last active. These are how we spot duplicate accounts, referral self-dealing and credential stuffing, and how we honour any restriction on where the service may be offered.
Uploads and what is made from them. When you upload a photo to a template, that photo is sent to the rendering provider that performs the generation and is processed in order to produce the video you asked for. That is the whole purpose it is used for: it is not used to train anything, it is not published, and it is not shown to other users.
Generation records. For each generation, which template you ran, the settings you chose, the prompt if you typed one, what it cost, whether it succeeded, and the link to the result. These are what your collection is made of, and they are what lets us return credits when a generation fails and answer you when you say one did.
Messages you send us. If you write to support, by email or through Telegram, we keep the correspondence so the next person who reads it has the history.
3. The purpose and the basis for each of those
Where the law requires a stated basis for processing, these are ours, category by category.
- Performing our agreement with you — account details, sign-in material, credits and the ledger, your plan and payment records, referral records, and processing an upload into the output you asked for. Without these the service cannot be delivered at all.
- Our legitimate interest in a service that is not abused — technical records, rate limits, fraud, payment-reversal and duplicate-account checks, and enforcing the prohibitions in the terms. We think this is a fair use of the data because the alternative is a platform that cannot keep out the conduct it forbids.
- Your consent — anything optional you choose to add, such as signing in through a third-party account or supplying a display photo. You can withdraw that consent by removing the item or closing the account.
- Legal obligation — records we are required to keep, including accounting records for payments taken, and anything we must retain in response to a lawful request.
Where the basis is our legitimate interest, you can object; see your rights below.
4. What we do not do
We do not sell your information, and we do not trade it for anything of value. We do not build advertising profiles, and we do not share your activity with advertising networks.
We do not use your uploads or your generated videos to train models. We do not put them in the public catalogue, and no other user can reach them through the service.
We do not read your generations to profile you, and there is no automated decision with a legal or similarly significant effect on you. Content checks happen — an upload can be refused, and an account can be suspended under the terms — and where one of those decisions goes against you, a person can look at it if you ask.
5. Uploads and generated videos
An uploaded photograph is held on our side for about 2 hours — the window the generation needs it for — and is then dropped. The rendering provider takes its own copy in order to run the job, and keeps it under its own schedule.
A finished video is kept for as long as your plan pays for. While a plan is running that is between 3 and 12 months from the moment the video completed, depending on the tier, and the exact date is shown against the video in your collection. Without a running plan there is no storage period: the video stays reachable only for the short window the rendering provider keeps its own copy, which is measured in hours.
Deletion at the end of that period is automatic and permanent. A deleted video cannot be restored, by you or by us. Downloading one gives you a copy that is yours to keep — these periods apply only to the copy on our systems.
You can delete a generation from your collection yourself at any time before its period ends, and doing so removes it from the service.
6. Who else handles your information
We use a small number of outside providers to run the service. They are described here by the job they do rather than by name, because the supplier for a given job is a configuration decision that can change without the substance of this policy changing. We can tell you the current supplier for any of these roles if you ask.
- A hosting and database provider runs the servers and stores the database. It holds everything the service holds, and processes it only on our instructions.
- A generation provider runs the models. It receives the photograph you uploaded, the template and settings for the job, and returns the video, which it also hosts. It is the one outside party that sees your uploads, and it sees them in order to do the thing you asked for.
- Payment providers