Privacy

An account holds an email, a name, a password stored as a hash, a role, the date it was created, and whether the account is blocked.

So you do not type the password on every page, we keep a sign-in session. A cookie holds the session marker. On the server we store its hash, when it expires, and the browser and IP address you signed in from.

A client profile holds a name and a wallet balance in USDT.

A host profile holds gender, age, prices for 15, 30, and 60 minutes, languages, interests, a schedule, the name and description in the site’s languages, photos and video, presence, rating, number of meetings, and whether the profile is hidden from the catalog.

A host application holds a name, email, age, gender, a phone number or Telegram, and optionally Instagram, a text about yourself, and photos. If the application is declined, we keep the reason and who reviewed it.

For meetings we store who met whom, the time, duration, price, status, whether it was an instant call, charges, refunds, extensions, and how the meeting ended. This is what the payment, the refund, and the fine are calculated from.

We also store ratings and comments after a meeting, reports, host fines, favorites, and the pairs where a client has hidden a host.

We do not record the video or audio of a meeting. Picture and sound go between the two participants while the meeting is on. If a direct connection cannot be made, the stream may pass through a relay server for the duration of the call and is not saved.

Chat messages are delivered to the other person during the meeting and are not kept on the server as a transcript. A copy may stay on your device while this is the current conversation, and for a short time after the meeting.

We do not accept card or bank details, and we do not store them.

A top-up is a USDT transfer. The transfer itself is visible on the public network of the blockchain you chose. We do not control that network and cannot erase the transaction.

The site stores the wallet balance and its movements: top-ups, charges for meetings, donations, and refunds. A top-up is credited automatically when the payment provider confirms the transfer.

The administrator of the platform sets the addresses used for transfers. Those are the platform’s addresses, not your personal wallet.

A host’s public profile — name, photos, video, description, languages, interests, schedule, prices, rating, and number of meetings — is visible in the catalog.

The host a client books can see that client’s name. The client can see the host’s name.

During a meeting, the other person sees the video and receives the chat messages.

An administrator sees accounts, applications, meetings, reports, balances, and fines, in order to run the platform and review reports.

The administrator sees an application and its photos. Photos the administrator later publishes on the profile become visible in the catalog.

To create an account and keep you signed in.

To book meetings, run them, and calculate payment, refunds, and fines.

To show the catalog, favorites, and people you have hidden.

To review reports and apply the rules.

To review a host application and contact the person at the contact they left.

Account data stays while the account exists.

You can delete the account from the profile. The account, meeting history, balance, favorites, ratings, and reports you sent are removed and cannot be restored. You cannot delete the account during a live meeting.

A host application is stored separately. After the account is deleted, the application can remain with the administrator until the administrator deletes it.

The sign-in session ends when you sign out, change the password, or delete the account.

We do not sell data, and we do not use advertising trackers.

Your device may keep the language you chose, the camera and microphone you chose, booking notifications and their sound setting, the chat of the current meeting, and a top-up request in the open tab.

This information is not sent to the server on its own. You can remove it by clearing the site data on the device.

A new version is published on this page. The date is at the top.