1. Private submission and evaluation
Submitting a query or feature request is free and does not create a client relationship, duty to accept, reservation, confidentiality beyond section 6, or obligation to provide advice. Do not submit passwords, live credentials, regulated records, unlawfully obtained material, or information you are not entitled to disclose.
If a request is accepted for further discussion, the customer may request one free 30-minute assurance call before payment. That call is for fit, conflicts, privacy, non-use and scope; it is not the paid solution or guided build.
2. Prepared conversations
A prepared conversation covers one pre-submitted query. Payment amount determines duration: ₹10–₹99 for 10 minutes, ₹100–₹499 for 30 minutes, and ₹500 or more for 60 minutes. Payment does not increase the promised expertise, correctness or outcome.
kuja.dev promises personal advance review, attendance, and dedicated discussion for the purchased duration. The service does not promise resolution, commercial success, safety, completeness or suitability for an unstated use.
3. Guided app builds
A guided app build is hands-on coaching for a customer developing their own app. It is not a done-for-you development contract. The customer operates their development environment, makes product decisions, writes or approves the code, and remains responsible for testing and release. kuja.dev prepares, teaches, explains, reviews, troubleshoots, and works alongside the customer.
The minimum block is ten working days at two focused coaching hours per day. Dates shown during submission are preferences until a written plan is accepted and payment reserves them. The plan identifies the app goal, starting point, learning objectives, working days, dependencies, exclusions, rescheduling terms and fixed price.
BenchK, DropK and EQK are apps created by kuja.dev. A customer is not limited to modifying those products. Unless the written plan expressly promises a defined deliverable, the service promises guidance and dedicated time—not a completed app, launch, approval, revenue result, or specific feature set.
4. Solution Records
A formal recommendation may be delivered as a dated and versioned Solution Record identifying the submitted question, assumptions, recommendation, alternatives, known limitations, sources and express guarantee. Only the written record and signed engagement scope are authoritative. A call explains them but does not silently expand the guarantee.
5. Guarantees, cancellation and refunds
If kuja.dev does not personally prepare for or attend a prepared conversation for substantially the purchased duration, the customer may choose a replacement session or full refund.
If kuja.dev does not provide the preparation or focused coaching time stated in a guided-build plan, the customer may choose replacement time or a refund for the undelivered portion. Customer absence, missing access or materials, changed goals, force majeure, platform review and third-party outages pause or exclude the affected schedule.
Nothing in these terms removes a remedy or right that applicable law does not permit the parties to exclude.
6. Confidentiality and non-use
kuja.dev will not disclose, reuse, build from, or monetise confidential information in an accepted private submission outside evaluating and performing the proposed engagement. This does not cover information already lawfully known, independently developed without use of the submission, public through no breach, received lawfully from another source, or required to be disclosed by law.
Submission content and delivered solutions will not be pasted into or processed through a generative-AI system. Ordinary email, hosting, spam filtering, payment and scheduling providers may process the minimum information needed to operate those services.
7. Ownership and permitted use
The customer retains ownership of their pre-existing materials and confidential input. They grant kuja.dev the limited permission necessary to evaluate the request and, after acceptance, perform the engagement.
kuja.dev retains its pre-existing materials, methods, templates, written recommendations, code, designs, tests, tools and general know-how. A prepared-conversation customer receives a non-exclusive, non-transferable licence to use the delivered recommendation for the agreed personal or internal purpose. Republishing, reselling, sublicensing or claiming authorship requires written permission.
The customer's app, pre-existing materials, product decisions, and code written by the customer remain theirs. kuja.dev retains ownership of its pre-existing teaching material, methods, templates, tools, examples, written recommendations and general know-how. Any reusable example or snippet supplied by kuja.dev may be used and modified inside the customer's app under a non-exclusive, perpetual licence, unless the written plan states a different licence.
8. Customer responsibilities
The customer remains responsible for deciding whether and how to act, testing before production use, obtaining qualified advice where needed, and warning kuja.dev about material constraints. No unrelated third party may rely on a formal recommendation without written consent.
The customer warrants that submitted material is lawful and that they have the authority to provide it. The service does not accept medical, legal, investment, structural-engineering, emergency, weapons, or other regulated or safety-critical decisions.
9. Reviews and Transparent Mode
Private Mode is the default. Payment alone does not authorise publication of identity. After a completed paid engagement, a customer may separately consent to Transparent Mode and preview the public name, service, completion month and review status to be published.
A Transparent Mode entry may neutrally state “review submitted” or “no review submitted.” The query, email, payment data and call content remain private. Consent may be withdrawn; the named entry will then be removed or anonymised while non-identifying aggregate counts may remain.
Reviews may be positive or critical. kuja.dev may respond but will not rewrite them. Content may be withheld or removed for impersonation, abuse, illegality, spam, conflicts with a court order, or exposure of confidential or personal information.
10. Responsibility and limitation of liability
To the extent permitted by law, kuja.dev is not liable for indirect, incidental, special or consequential loss. Ordinary contractual liability for one engagement is limited to the amount paid for that engagement. This limitation does not apply where applicable law does not permit exclusion or limitation, including fraud, wilful misconduct, or mandatory consumer remedies.
11. Changes, governing terms and conflicts
The version accepted at payment governs that engagement. Later website changes do not retroactively alter it. If an engagement-specific signed scope conflicts with these general terms, the signed scope controls for that engagement.
12. Contact and complaints
Questions, privacy requests, complaints and refund requests may be sent to support@kuja.dev. Include the engagement or payment reference if one exists.