Refund Policy for MemoryClasses.in Learning Support Services

This refund policy explains the payment, refund and reschedule approach before a learner joins a paid support path.

The policy follows a practical support-first approach: clear booking terms, fair review of concerns and a simple refund rule when no paid session has been attended.

Effective date: 2026-04-21

This policy applies to paid support steps booked through MemoryClasses.in or its approved operating flow. The one-time free demo is free and does not create a refund claim by itself.

Where the learner is a child, the parent or guardian who makes the payment is treated as the responsible payer.

The basic public rule is simple: if no paid session has been attended, a full refund the team may consider.

After sessions start, concerns are usually reviewed first through attendance, fit, worksheet or task completion. This helps where relevant, and the practical status of the support term.

Where possible, the platform may try to resolve a concern through clear guidance, support adjustment, rescheduling, or extra no-fee help before a refund decision is considered.

Users are encouraged to review the free demo, pricing direction, terms, and refund policy before making a payment.

The approved quote may depend on learner need, duration, plan structure, timing, and route fit. This helps as users should seek clear guidance before confirming the payment.

Where some paid support activity has started but a review shows that part of the value was not yet used, a partial refund the team may sometimes consider depending on attendance, preparation, materials already used.

and the remaining status of the term.

This is a case-by-case review rather than an automatic promise.

After meaningful paid delivery has already happened, a refund the team may refuse. This helps where the support term has substantially begun, the learner has attended sessions, or relevant materials and guidance have already been used in a practical way.

A non-refundable outcome may also apply where the concern mainly relates to lack of follow-up, non-attendance, repeated no-shows, or refusal to participate in the agreed support flow.

The free demo is a no-cost first-step discussion or sample session. Because it is free, no refund applies to that first step.

The demo exists to help the user understand fit before moving into a paid support decision.

Paid support is usually confirmed as a plan rather than as an instant ecommerce-style checkout item. A learner-based quote the team may share after review or demo, and payment is then made for the approved support term.

Public quick facts may describe common patterns such as 8 sessions per month and sessions of about 45 mins each, but the exact paid plan still follows the approved learner-based quote.

Rescheduling may often be the better solution when the concern is mainly about timing rather than support fit. A user should try to give at least 1 day notice when asking to reschedule.

Reasonable reschedule support the team may offer where timing problems are genuine and the learner is still actively participating.

Repeated missed sessions, last-minute absence without practical notice, or a pattern of no-show behavior may affect whether make-up support or refund review is considered.

The platform may review the overall attendance record before deciding the next step.

If the user wants to stop before the paid support term meaningfully begins, the team reviews the request under the full-refund rule. This applies where no paid session was attended.

If the user cancels after support has already begun, the result may depend on attendance, materials already used. Whether the issue can first be resolved in a practical way.

If the platform is unable to continue a paid support path before meaningful delivery begins, a the team may consider a refund or suitable alternative depending on the situation.

If a user is removed because of serious misuse, abusive conduct, payment abuse, or repeated non-genuine behavior, a refund the team may refuse where reasonable.

Sometimes a route change or structure adjustment resolves the concern without ending the support path entirely.

A route change is not guaranteed, but it the team may consider where it reasonably helps the learner more than an immediate refund review.

If worksheets, guided tasks, notes, recordings, or similar support materials have already been shared and used as part of the paid path, that may affect whether a full refund is appropriate.

This is especially relevant where material access formed part of the delivered value.

Where payment is made through a gateway, bank transfer, or another approved processor, final refund credit time may also depend on that external system’s processing speed.

The site may confirm the refund decision first and then wait for the actual processor timeline to complete the credit.

If the same user accidentally pays twice or pays the wrong amount in a clearly verifiable way, the user should contact the team promptly with the necessary payment reference. This helps as the issue can review.

The team may correct verified duplicates through refund or adjustment as appropriate.

Users should contact the team first before raising a chargeback or dispute through a payment provider. Direct review can resolve many payment concerns faster.

Where a user starts an external dispute after meaningful service delivery, the platform may rely on attendance, records. Policy pages while responding to that dispute.

A refund request may need time for internal review, especially when attendance, timing, materials, or payment verification must be checked first.

Users should allow a reasonable review period before expecting a final decision or processor credit timeline.

The final decision may consider whether paid sessions were attended, what value was already delivered, whether the concern could have been resolved through support adjustment.

and whether the user followed the practical communication process.

This keeps the policy fair to both the learner and the platform.

This policy the team may revise when the payment flow, delivery model, session structure, or public wording needs to be updated or clarified.

The latest published version on the website should be treated as the current public reference unless direct written clear guidance states otherwise.