Privacy and request process

Information you provide

We store your name, email, selected service, project details, optional contact number and budget, plus the request reference, status, and submission time.

How your information is used

It is used to review, contact you about, and manage your request. Requests are not public and are available only in the protected owner dashboard. A brief notification may be sent to the project owner inside Manus.

Chat assistant and artificial intelligence

The assistant is automated, not a person. Before a chat begins, we ask for your explicit consent to store the chat text and time in the site database and to process the text with an artificial-intelligence service to draft replies and collect project needs. The site owner can review conversations in a protected dashboard for follow-up. Your browser keeps a private chat token, and customer conversations are not public. Starting a chat or a new conversation does not send a service request or delete earlier conversations from the database.

Do not enter passwords, card details, or sensitive information in chat. The assistant does not make payments, grant discounts or refunds, or confirm a binding date or final delivery. Replies are preliminary information; every final agreement needs the owner’s approval.

Retention and deletion

Requests and conversations are kept in the site database and are not deleted automatically. You may ask the service owner directly, through the contact method used with them, to correct or delete information. Do not send passwords, card details, or sensitive information.

Agreement, payment, and approval

Prices are starting estimates and durations are approximate. Deliverables, final price, timing, revisions, file-use rights, cancellation, and refund terms are agreed directly. Submitting a request is free. Only the owner issues an approved private invoice. The invoice identifies its hosted payment provider. The system supports Ziina and earlier Stripe invoices; old invoices are not automatically moved to another provider. The site never stores card numbers or security codes. Private invoices and history require Manus sign-in with the request email. Invoice details, buyer identity, payment purpose, provider, transaction identifiers, and verified confirmation are retained for tracking. Ziina requires a valid HMAC notification and matching API verification; live activation needs a successfully verified integration test. Test invoices collect no real money. Returning to the site does not prove payment, and a deposit is not full-project payment. Any spending, discount, refund, binding date, or final delivery needs owner approval, and email drafts are not sent unless their send is approved.

Access and external links

Administration and private payment pages use a secure Manus session. WhatsApp and email links open external services governed by their own policies. Essential session data for administration and basic visit measurement may be provided by the hosting platform.