Refund Policy

Last updated: May 9, 2026

ComputerScienceHomeworkHelp.com publishes the following refund policy for every order placed on this website. The policy covers computer science homework, programming assignments, debugging tasks, code optimization work, theoretical CS exercises, exam preparation, and live tutoring sessions across Java, Python, C++, C, JavaScript, Assembly, and 50+ additional languages. The conditions on this page apply to every order without exception. Read the full page before placing any order. A few minutes here prevents most disputes later.

1. Refund Eligibility Summary

A full refund applies in 5 specific situations: cancellation within 2 hours of payment, missed deadlines, plagiarism in written deliverables, tutor no-show on a booked live session, and duplicate or accidental double payments. Partial refunds apply in 5 additional categories detailed below. Outside these conditions, refunds do not apply.

2. Cancellation Within 2 Hours of Payment

Cancellations submitted within 2 hours of payment receive a full 100% refund. No explanation is required at this stage.

The 2-hour window starts from the timestamp on the payment confirmation email, not from the brief upload, the quote stage, or any earlier interaction. Cancellation requests sent through email, the website contact form, or the secure chat system all count as valid notification. The team confirms receipt and processes the cancellation within minutes. At this stage no expert has been assigned, no work has begun, and the project closes cleanly.

3. Cancellation After Expert Assignment

Cancellations after the 2-hour window carry a partial refund between 0% and 70%, calculated against the work completed at the cancellation point. Once the assignment passes to a verified CS tutor, time and effort apply to the project, and partial compensation reflects that committed work.

Three factors determine the exact percentage. The first is the volume of work completed. The second is the proximity to the deadline. The third is whether any partial deliverables, code samples, or progress drafts have been shared with the student. A cancellation 4 hours into a 5-day distributed systems project carries a higher refund percentage than a cancellation 4 days into the same project.

3a. Cancellation Near the Deadline

Cancellations submitted close to the deadline carry no refund. At this point the tutor has completed the assignment or substantially completed it, and the work product retains value to the student regardless of the formal cancellation. The phrase "close to the deadline" covers the final 25% of the project timeline.

3b. Rush Orders Under 6-Hour Deadline

Rush orders operate under a stricter cancellation window. A 100% refund applies only when the cancellation arrives within 30 minutes of payment. After the 30-minute mark, partial refunds apply, calculated against the percentage of work completed.

Rush orders move fast. The expert begins the assignment immediately on payment confirmation, and by the 60-minute mark on a 4-hour rush deadline, a substantial portion of the Java program, the C++ binary, the SQL schema, or the algorithm proof already exists.

4. Live Tutoring Session Refunds

Live tutoring sessions follow a separate refund track because the service runs on an hourly booking model rather than a project model. Four rules govern live session refunds.

• Rescheduling more than 24 hours before the session: free of charge. The booking moves to the new slot at no cost.
• Cancellation more than 24 hours before the session: full 100% refund. The hour returns to the booking pool and the payment refunds to the original method.
• Cancellation within 24 hours of the session: no refund. The tutor reserves the slot and prepares for the topic in advance, and the time slot rarely fills at short notice.
• Tutor no-show: full 100% refund on the session, automatically. A no-show covers any case where the tutor fails to join the session within 10 minutes of the scheduled start time. The session also reschedules at the student's discretion at no additional cost. Recording failures, technical issues on the platform side, or session interruptions caused by the tutor qualify under the same clause.

Recording delivery for completed sessions runs within 24 hours of session end. Recording failures on the platform side trigger the no-show clause.

5. Acceptance and Use Clause

No refund applies after the student accepts the delivered work and uses it. Acceptance and use confirms the transaction as final, and the order closes for refund purposes.

These actions count as acceptance and use:

• Submitting the deliverable to an academic portal such as Canvas, Blackboard, Moodle, Gradescope, AutoGrader, HackerRank, or any institutional grading system
• Sharing the deliverable with a third party, such as a study group, a tutor, a forum, or any external recipient
• Sending the deliverable to a professor, a teaching assistant, or a grading platform
• Adapting the deliverable into a final submission file under the student's own name and putting it forward for academic credit
• Pushing the deliverable to a personal or course GitHub repository linked to the institution

Inspection of the deliverable does not count as acceptance. Downloading the file to a local machine for review does not count as acceptance. Review the source code, the algorithm proof, the design document, the database schema, the technical report, or the live session recording in full before any action that triggers acceptance. Concerns raised during inspection, before submission, sharing, or further use, qualify for the standard refund pathway.

6. Missed Deadlines

A 100% refund applies to every order delivered after the agreed deadline. No conditions apply. No negotiation occurs. No processing fee is deducted from the refund amount.

The agreed deadline appears on the order confirmation email and on the project dashboard at all times. The expert and the project manager work to a buffer of 2 to 4 hours ahead of the visible deadline as standard practice. In the rare case where this buffer fails, the project manager contacts the student in advance and presents two options: a deadline extension at the student's discretion, or a full refund. The student selects.

Missed deadlines are rare. The full-refund clause exists as a guarantee against unusual cases, not as a routine outcome.

7. Quality Concerns

Quality complaints qualify for a full refund when supported by specific evidence. Evidence in this context refers to four items: the original assignment brief, the rubric or grading criteria, the delivered solution, and a documented list of where the deliverable diverges from the brief.

Generic complaints, like "the code is bad" or "I expected more," do not establish grounds for a refund without a specific reference to where the deliverable failed the brief. Specific complaints establish clear grounds, and the refund proceeds within 1 business day of confirmation.

Examples of evidenced, specific complaints:

• The rubric required dynamic programming and the delivery uses a brute-force solution
• The brief asked for unit tests on five functions and only two functions were tested
• The assignment specified Java 17 and the code uses syntax from Java 8
• The brief required pointer-based linked list operations in C and the delivery uses a Python-style list abstraction
• The rubric required a balanced binary search tree and the code submits an unbalanced one
• The assignment specified Big-O analysis for every function and the delivery omits complexity comments
• The brief required Valgrind-clean memory output and the code shows leaks

8. Plagiarism Claims

Plagiarism in written deliverables triggers a full refund. The student submits proof, typically a Turnitin, SafeAssign, PlagScan, or Copyscape report, within 24 hours of delivery. The team confirms the finding and processes the refund within 1 business day.

Source Code and the 20% Similarity Rule

A specific exception applies to source code in any language. Code similarity scanners, including MOSS, JPlag, Codequiry, and the built-in tools on Gradescope, AutoGrader, and HackerRank, flag standard syntax as similar to public code by default. Common library imports such as java.util, std::vector, numpy, pandas, and React produce false-positive matches in these tools, along with standard loop structures, common function names like main(), constructor patterns, and variable names like i, j, x, y, ptr, and node.

A 20% similarity score on source code is common across legitimate, original solutions and falls within accepted tolerance for this niche. Reports above 20% receive full investigation, and a refund applies on confirmation. The 20% threshold applies uniformly across Java, Python, C, C++, JavaScript, Assembly, and every other language listed on the site.

The 24-hour reporting window is non-negotiable. Plagiarism claims raised after 24 hours of delivery do not qualify for refund consideration.

9. Duplicate Order

Accidental duplicate orders receive a 100% refund on the duplicate within 3 working days of notification. The original order proceeds as planned.

Duplicate orders happen. A slow payment confirmation prompts a second submission, a browser tab refreshes during checkout, two devices submit the same brief. Notification through email, the contact form, or the secure chat initiates the duplicate cancellation immediately. No questions are asked, and no documentation is required beyond the order IDs.

10. Overpayment

Surplus payments receive a 100% refund on the excess amount. Surplus payment covers paying twice for one order, paying double the quoted figure, or duplicate transactions on the payment processor. Reporting through any communication channel within 3 working days starts the process.

Bank settlement varies by processor and country. Stripe, PayPal, Apple Pay, and Google Pay typically settle in 3 to 7 business days. International wire reversals run 5 to 10 business days. Cryptocurrency refunds in Bitcoin and Ethereum settle within 24 hours. The refund instruction goes out the same day as approval, and actual settlement timing depends on the receiving institution.

11. Partial Refunds for Grades Below 75%

A partial refund applies when the student receives below 75% on a graded assignment delivered through ComputerScienceHomeworkHelp.com, with one supporting condition: documented proof of the grade. Acceptable proof refers to a screenshot, a PDF, or a direct email from the academic portal showing the score, the assignment title, and the grading date.

The partial refund percentage scales against the gap from 75%. A grade of 65% on a $30 order generates a 25% partial refund. The calculation uses the 10 percentage point gap multiplied by an established compensation factor. Grades from autograder platforms (Gradescope, AutoGrader, HackerRank, CodePost) and grades from human-evaluated submissions both qualify equally under this clause.

This clause covers assignments graded by the academic institution. Self-assessed scores, peer-evaluated drafts, and unofficial estimates do not qualify.

12. Free Post-Delivery Support

Free post-delivery support runs for 7 days from the delivery date. The assigned expert fixes the deliverable at no extra charge inside this window when the work does not match the rubric or the original assignment brief.

The 7-day window covers fixes for rubric mismatch and missing requirements from the original brief. Requests for additional features, expanded scope, or changes outside the original brief follow a separate quote and sit outside this clause.

After 7 days, free post-delivery support falls outside this policy. When a fix inside the 7-day window does not bring the deliverable into rubric compliance, the refund pathway in this policy remains open as a substitute.

Free unlimited revisions during the active project, before delivery, operate under the standard process and do not consume any post-delivery support window.

13. The 15-Day Claim Window

Refund claims submitted more than 15 days after the delivery date are not eligible. The 15-day window covers every refund category, including quality dissatisfaction, plagiarism, grade-based partial refunds, and any other claim type.

Inside the 15-day window every claim receives individual assessment in the order received. Outside the window the order closes for refund purposes, regardless of the underlying issue.

The 15-day claim window operates independently from the 30-day file retention window. Files auto-delete from the platform 30 days after delivery, and the deliverable remains under the student's control during that period as a local copy.

14. Refund Processing Timeline

Approved refunds enter processing within 7 business days of the approval date. Settlement at the student's bank or payment processor adds further time depending on the institution and the payment method.

Typical settlement times by payment method:

• Credit and debit cards (Visa, MasterCard, American Express): 5 to 10 business days
• PayPal: 3 to 5 business days
• Apple Pay and Google Pay: 3 to 7 business days
• Cryptocurrency, including Bitcoin and Ethereum: 1 to 24 hours
• International wire transfer: 5 to 10 business days

ComputerScienceHomeworkHelp.com is not responsible for bank fees, currency conversion charges, intermediary bank deductions, or processing delays at the receiving institution. The refund equals the original transaction amount in the original currency.

15. When Refunds Do Not Apply

Refunds do not apply in 6 specific scenarios:

• The student has accepted and used the delivered work, including submitting it, sharing it with a third party, or putting it forward for academic credit.
• The cancellation request arrives after the deadline has passed and the deliverable is complete.
• The claim arrives more than 15 days after the delivery date.
• The complaint lacks supporting evidence, such as a rubric reference, a specific failure point, or grade documentation.
• The student requested features outside the original brief mid-project and the expert declined the additional scope.
• The student blocked or refused communication during the project, preventing clarification.

These categories are non-negotiable. Each refund decision is documented in writing, and the reasoning is shared with the student in plain language.

16. How to Submit a Refund Request

Refund requests follow a 3-step procedure:

• Send the request to [email protected] or through the contact form on the website. Include the order ID, the date of delivery, the specific reason, and any supporting evidence such as the rubric, the grade screenshot, or the plagiarism report.
• The support team confirms receipt within 1 business day and routes the request to a project manager for review.
• The project manager reviews the order history, the delivered work, and the supporting evidence. A written decision arrives within 3 business days.

Approved refunds enter processing within 7 business days of the approval. Disputed decisions move to a senior review at the student's request. A second project manager re-examines the file independently and produces a final decision within 5 business days.

17. Discretionary Authority

ComputerScienceHomeworkHelp.com retains discretion on every refund decision. Discretion applies to edge cases such as unusual project scope, mid-project changes initiated by the student, unforeseen platform failures, or third-party service outages, where the standard rules do not produce a fair outcome on their own.

The use of discretion never produces a result worse than the standard rule for the student. Discretion exists to allow flexibility in unusual cases, not to override the published policy in the company's favour.

18. Policy Amendments

This refund policy is subject to amendment at any time. Amendments take effect from the date posted on this page. Orders placed before an amendment date remain governed by the policy active at the time of payment.

The "Last Updated" date at the top of this page reflects the most recent amendment. Material changes (new categories, modified percentages, or changed timelines) appear in a brief change log appended to this page for 90 days following the amendment.

19. Contact

For questions on this policy, refund requests, or clarification on any condition, three contact channels are open:

• Email: [email protected]
• Secure chat: through the chat button on the website
• Contact form: computersciencehomeworkhelp.com/submit/

Response times run 4 to 12 hours during business days, and 12 to 24 hours over weekends.

Disclaimer

The services on ComputerScienceHomeworkHelp.com are provided for educational, learning, and tutoring purposes. The deliverables (source code in any supported language, algorithm proofs, design documents, database schemas, technical reports, study guides, and live tutoring session recordings) exist as learning aids, study references, and practice material. Use of the work remains at the student's discretion and responsibility. This refund policy governs the commercial transaction between the student and ComputerScienceHomeworkHelp.com only, and does not constitute a guarantee of academic outcome.