1
Create your role
After signup, choose whether you want to be contacted as a provider or browse profiles as a client. Each role has its own onboarding form.
Product flow
Simple structure, deliberate contact.
Eve Chat separates discovery, requests, and end-to-end encrypted chat so people know exactly what stage they are in and how private messages are handled.
2
Complete the profile
Providers add photos, interests, and a visible profile. Clients define who they want to find and set their own details for matching context.
3
Start with a request
Clients do not drop directly into a random inbox. They send a contact request first, and providers can accept or reject it.
4
Pay with credits
Clients top up credits before or during chat. Provider replies consume credits in clear daily steps, and the app warns both sides before the balance blocks more client messages.
Discovery
Search stays relevant
Client search can use age and orientation filters, and the app avoids showing the same providers once contact already exists.
Chat
Realtime when it matters
Accepted requests move into direct one-to-one chat with end-to-end encryption, delivery states, media support, and history stored on user devices.
Safety
Tools around the edges
Moderation hooks, reporting, and rate limits help keep the main experience focused without turning the product into an open public feed.
Payments
Visible billing, not hidden metering
Billing information stays visible inside chat and profile views, so clients can see available credits and providers can see whether the client has enough balance to continue.
Pricing
Credits, pricing, and payouts
The current pricing model is designed for straightforward support and transparent testing.
Client bundles
Base bundle: 70 credits for EUR 4
Larger bundles scale from the same base price. Default currency follows the user country: CZK for Czech Republic, EUR for Slovakia and all other countries.
Conversation charging
Charge in message batches
A charge posts only after 10 qualifying provider messages and at least 1 qualifying client reply in that bucket. Qualifying text needs 5+ characters, each image or audio counts as 1, the first bucket costs 35 credits, and later buckets cost 15 credits.
Provider payouts
Tracked end to end
Providers can save payout accounts and send mocked withdrawal requests. Admins can audit balances, top ups, charges, and payout requests from the web dashboard.
Billing flow
How credits move through a conversation
The app charges only for qualifying provider replies, requires one qualifying client reply per 10-message bucket, shows the current batch progress in chat, and stops advancing the next batch once the client balance is empty.
Top up
Client adds credits
A client starts with a credit bundle. The current balance stays visible in chat before any provider reply is counted.
Reply
Provider messages advance the batch
Only qualifying provider messages advance billing. A bucket charges at 10 messages only after the client has sent at least 1 qualifying reply; the first bucket costs 35 credits and later buckets cost 15.
Warning
Both sides see the balance state
Clients see how many credits remain. Providers also see when a bucket is waiting on the client's qualifying reply, so repeated provider messages alone do not keep building billable buckets.
Resume
Billing resumes after the next top up
If the client balance reaches zero, client sending is blocked until the next top up. Provider messages can continue, but billing only resumes after credits are added again.
This keeps the meter visible and predictable: no hidden countdown, no surprise catch-up charge while the balance is empty.