Privacy Policy

Last updated: 23 July 2026

CodingClap is a school-linked coding question-and-answer community for school students. Because our users are children, we treat their data with more care than the law's minimum, and we explain here — in plain language — exactly what we collect, why, and what we will never do.

1. Who we are

CodingClap is built and run by Anuj in Bangalore, under Amriculum Education. You can reach me at anuj@codingclap.com.

2. Parental consent comes first

India's Digital Personal Data Protection Act, 2023 treats everyone under 18 as a child, and requires a parent or guardian's consent before a child's personal data is processed. CodingClap is built around that requirement.

When a student registers, their account is created in a pending state. It cannot be used to post questions, post answers, or give claps. We send a consent email to the parent or guardian address given at registration, and the account is activated only after the parent confirms through that email. The confirmation link is valid for 48 hours. If a parent does not confirm, the account stays pending and unusable, and we delete it and its registration data after 7 days.

3. What we collect

About the student: first and last name, display name, class and section, the school they registered under, and a securely hashed password. We do not ask students for an email address or phone number.

About the parent or guardian: name, email address, and mobile number. These are used to obtain and record consent, and to contact you about your child's account.

What the student writes: the questions they post, the answers they write, any code they paste, and any screenshots they upload to a question.

Activity records: claps given and received, questions viewed, logins, and a log of significant actions. These records include the time of the action and the IP address it came from. We keep them so that teachers and moderators can maintain a safe community, and so that consent actions can be shown to have happened.

Cookies and technical data: When a student logs in, we set a session cookie so the site knows they are signed in. It is not used for tracking or advertising, and it expires when the session ends. We also record the IP address of the parent or guardian at the moment consent is given or withdrawn, as part of the consent record.

4. Why we collect it

We collect this data for one purpose: to run a safe, school-verified place where students can ask coding questions and help each other. That means verifying that a student belongs to a participating school, obtaining and recording parental consent, showing questions and answers to the community, letting teachers see and moderate what happens, and keeping an audit trail of consent and moderation actions.

We do not collect data for any purpose beyond running the platform.

5. What we will never do

6. Who can see a student's activity

Questions and answers posted on CodingClap are visible to other students and teachers on the platform, alongside the student's display name, class, and school. This is how the community works — students learn from each other's questions and answers. Students should not post personal information such as addresses, phone numbers, or photographs of themselves in questions or answers.

Teachers and administrators at a student's school can see that student's activity. Parents may ask us at any time for a summary of what their child has posted.

7. Where data is stored

CodingClap's data is held with our hosting provider. Uploaded images are stored on the same hosting account.

Our hosting and email providers process data on our behalf in order to run the platform.

8. How long we keep it

If a parent does not confirm consent within 7 days, we delete the pending account and its registration data. Where consent is given, we keep the account and its content while the account is active.

Questions and answers are not erased when they are removed from view, because they may form part of a moderation record. If you ask us to delete your child's data, we will remove their personal details and delete their account within 30 days. Anything they posted may remain on the platform without their name attached, so that other students don't lose answers they are learning from.

9. Withdrawing consent

A parent or guardian can withdraw consent at any time by writing to info@codingclap.com. When consent is withdrawn, the student's account is immediately suspended from posting, and their data is deleted as described above. Withdrawing consent does not affect anything that lawfully happened before the withdrawal.

10. Your rights

As the parent or guardian of a student on CodingClap, you may ask us to tell you what data we hold about your child, correct anything that is wrong, delete your child's data, or withdraw your consent. Write to us at info@codingclap.com and we will respond.

11. Keeping data secure

Passwords are stored as bcrypt hashes and are never logged or transmitted in readable form. The site is served over HTTPS. Database access uses prepared statements. Access to student data is restricted by role, and every significant action is logged.

No system is perfectly secure. If a breach occurs that affects personal data, we will notify affected parents and the relevant authority.

12. Changes to this policy

If we change how we handle data, we will update this page and change the date at the top. If the change is significant, we will contact parents directly rather than rely on this page alone.

13. Contact and complaints

For any question, request, or complaint about how CodingClap handles personal data, write to info@codingclap.com. We will acknowledge your message and tell you what we are doing about it.