Terms of use

The service and these terms

These terms describe access to the Dikaya browser chat and API at https://dikaya.cloud. “Dikaya” refers to the service and its administrator. The contact page identifies the available support channel and the service information currently published.

Use these terms together with the privacy notice, current prices and the conditions shown in your account. They do not remove rights that cannot be waived under applicable law. Version dates let you identify the document you are reading.

Accounts and API keys

Registration uses a username and password; an email address is not required. Keep your password and personal API key private. Requests made using a key consume the associated account credit. If a key is exposed, rotate it in the account; the old key stops working.

Do not interfere with other accounts, probe private customer records or deliberately disrupt the service. Administrators may manually restrict access to address misuse, incidents or a breach of these rules. Restriction can block login, API access, sessions and key rotation. Financial questions remain subject to a separate review; a restriction is not a promise of a refund or an automatic forfeiture rule.

Automatic password recovery is not currently implemented. Do not assume that a lost password can be reset by email. The contact page states the limitations of the available account-only support channel.

Demo and published limits

Eligible new accounts may receive a one-time $0.5 demo balance and up to 25 requests on Pro 2. Eligibility depends on browser, network and overall allocation limits; a new account can be created without a demo grant. Earlier account-specific demo conditions remain in effect.

The current new-account demo is text-only: up to 512 output tokens, 6000 bytes of context, 10 requests per minute and one concurrent request. Client tools and longer work require a topped-up account. A demo is not an unlimited free plan.

Payments, credit and prices

Dikaya uses a prepaid balance shared by chat and API. There is no recurring subscription or balance expiry. The minimum top-up is $5. The pricing page lists the current retail model rates and package amounts; the authenticated model catalogue shows rates and model permissions for your own key.

Credit and any qualifying package bonus are added after a confirmed payment with a unique reference. Creating an invoice is not a payment confirmation. Follow the network, recipient, amount and expiry instructions in your own invoice; do not reuse someone else’s invoice. Digital-asset transfers recorded on public networks cannot be cancelled by changing a Dikaya page.

A package bonus is additional service credit, not a cash payout or an investment return. Separate payments do not combine to unlock a higher bonus tier. Wholesale partners may have an explicitly assigned tariff; there is no automatic conversion of ordinary accounts. Completed historical charges are not repriced when a new tariff is published.

Usage, reservations and interruptions

Usage is charged by ordinary input, cached input and output tokens at the applicable model rate. Reasoning tokens, when used, are part of output usage, not an additional duplicate charge. Paid Pro image handling uses a separately billed Flash-to-text step; both steps require funds before processing.

Before inference the service reserves a conservative cost estimate. When final usage is known, it settles the actual amount and releases the unused part. An explicit HTTP rejection refunds unused work, but any completed image-processing step can still be charged.

If the processing outcome or final usage is unknown, the reservation may remain for reconciliation. Closing a browser tab or losing a network connection does not prove that no processing occurred. Repeating a request may start a separate billed operation. Report a disputed request with its time and identifier rather than assuming every interruption is free.

Generated output and availability

AI output can be incomplete or inaccurate. Check code in its actual environment and verify facts before relying on them. Model names, context windows and protocol compatibility do not guarantee an answer to every request, successful tool execution or support for every third-party client feature.

Features and model availability can change, and maintenance or network incidents can temporarily interrupt access. No uptime, response-time or support-reply SLA is published. Keep copies of material you need; do not treat chat history as your only archive.

You must have the necessary rights to material you submit. Generated output is not a guarantee of uniqueness or clearance of third-party rights. These terms do not purport to grant rights owned by someone else or exclude obligations that cannot lawfully be excluded.

Payment questions and refunds

Questions about a payment, remaining credit or a disputed charge are reviewed manually through the Support section in your account. Provide the invoice or payment reference, amount, network and transaction identifier where relevant; for an API request provide its approximate time, model and request identifier if available. Never send a password, complete API key, private wallet key or recovery phrase.

There is no automatic cash-refund feature and no published fixed review deadline. A request is not a guarantee of approval or rejection. The administrator checks payment and usage records and discusses the available resolution, any required payment details and applicable requirements. Do not send an additional transfer merely to have an earlier transfer reviewed.

If an account or key is inaccessible, see the contact page before taking further action. Currently no separate public email or messaging channel is published. This is a real limitation of the support setup, not a promise that recovery is available.

Deletion and document updates

Account deletion requires confirmation of the username and acknowledgement of a positive balance. It closes access and sessions, removes browser chat and support history from the active application, invalidates the key and cancels unpaid invoices. It is not a refund request. Raise unresolved payment or remaining-credit questions before deletion.

Payment, usage and moderation audit records, deletion tombstones and backups can remain; see the privacy notice for the distinction between account history and service records. Deletion does not automatically erase previously delivered private notifications.

This page carries a version date. Revisions do not rewrite confirmed payment history, completed usage or demo conditions already stored for an account. Material changes should be read before starting further paid work. Questions about a clause can be raised through the contact route.