Practically Referral Code

The amount is clear and the condition is not. In referral offers the condition is almost always the part that matters.

The offer is "₹50 for every certified student signup", and the word carrying all the weight is "certified".

Nothing on the record defines it. That single word could reasonably mean any of:

a verified email or phone number — a low bar, met within minutes;
a completed student profile, including school and class details;
account activation plus some minimum usage — opening a lesson, completing one;
a verified student identity, which is a meaningfully higher bar;
or a paid subscription, which is a different proposition altogether.

Those possibilities span the entire range from "trivially easy" to "unlikely to happen". So the honest position is that this offer cannot be valued from the outside, and anyone sharing a code should establish the definition first. This project's repeated finding is that the trigger, not the amount, is what decides whether a referral pays — and here the trigger is a single undefined adjective.

Ask three questions before sharing anything: what exactly must the referred person do; how long do they have to do it; and is the reward reversible if they stop using the app.

Now the more important part of this page, because this product is for children and that changes the analysis.

Practically is a learning app for school students. Referring someone therefore usually means referring a child, through their parent — and this project has taken a consistent position on minor-facing products since it first encountered one: a referral fee should not be the reason a child's account is created.

That is not a criticism of the product, which teaches curriculum subjects and may be entirely good. It is a statement about the referrer's position. ₹50 is a small sum, and the decision it might influence — what educational tools a child uses, and what data is collected about them — is not one that should turn on a small sum at all.

The specific things a parent should establish, which a referrer is well placed to mention:

What data is collected about the child, and whether it is used for anything beyond delivering the lessons. India's data protection framework requires verifiable parental consent for processing a child's personal data and restricts behavioural advertising to children — this project noted that in its earlier work on minor-facing apps, and it applies squarely here.
Whether the app is free, freemium or subscription, and what the actual cost is once the free portion is exhausted. Learning apps for children commonly open free and gate the useful material, which is a legitimate model but should be understood before a child is invested in it.
Whether the content matches the child's actual curriculum and board, since Indian syllabi vary and a mismatch makes even good material unhelpful.
How much screen time it implies, which is a real consideration for school-age children and one the marketing will not raise.

And the honest educational point, which applies to every app in this category. Interactive and immersive formats are genuinely engaging, and engagement is not the same as learning. A child enjoying an app is a good sign; it is not evidence that anything was retained. The test is whether they can do something afterwards they could not do before — which, for school subjects, is measurable in ordinary schoolwork rather than in the app's own progress metrics.

Note on this page's limits: we could not verify Practically's pricing, curriculum coverage, ownership or data practices while writing this, so none is asserted. The questions above are the right ones regardless of what the answers turn out to be, and a later revision should establish them.