Privacy

What we do with
your students’ data.

Every claim this site makes about privacy is written out here in full, including the parts that constrain us. Where a detail depends on your agreement, it is marked rather than fudged.

Last updated 3 August 2026 Applies to intellicamp.school and the Intellicamp platform

Needs your lawyer before launch. This is written to match what the rest of the site actually claims, with every placeholder marked. It is not legal advice, and the bracketed fields must be completed by whoever holds the entity.

1Who we are

[REGISTERED ENTITY NAME] (“Intellicamp”, “we”) operates intellicamp.school and the Intellicamp examination platform. Registered office: [REGISTERED ADDRESS]. CIN [CIN]. For privacy questions, write to [email protected].

Where a school or coaching institute uses Intellicamp, the school is the data controller and we are the processor. We handle student data on their written instructions and for no other purpose. Where an individual learner signs up directly, we are the controller for their account.

2What we collect

Only what the platform needs to work:

  • Account data — name, email, role, and the school, standard and division you belong to.
  • Academic data — papers set, answers submitted, marks awarded, teacher overrides, and the chapter-level analysis derived from them.
  • Exam integrity data — where proctoring is enabled by your institution: submission timestamps, connection interruptions, and flags raised during an exam.
  • Technical data — IP address, browser and device type, kept for security and diagnostics.

We do not collect location, contacts, camera or microphone access outside an actively proctored exam, browsing history outside the platform, or any behavioural profile of a student.

3What we use it for

To deliver the service your school or you asked for: generating papers, running exams, marking them, producing analytics, and supporting you when something breaks.

Student work, answers and results are not used to train models — ours or anybody else’s. Questions your department writes stay in your bank and are not shared with other institutions. This is a contractual commitment, not a setting.

We do not sell personal data, and we do not use student data for advertising or share it with advertisers under any circumstances.

4Who can see what

Access is role-based and enforced server-side, not merely hidden in an interface:

  • Students see their own papers, marks and analysis, plus a class average for context.
  • Teachers see the students in the divisions they teach.
  • Heads of department see their subject across divisions.
  • Administrators see their own institution.
  • Parents see one child, and nothing else.

Our staff do not browse student records. Access to production data is limited to a named on-call group, requires a documented support reason, and is logged.

5How it is protected

Data is encrypted in transit (TLS 1.2 or above) and at rest. Passwords are hashed and never stored in a recoverable form. Backups are encrypted and access to infrastructure requires multi-factor authentication.

Data is hosted in [HOSTING REGION — e.g. India (ap-south-1)] on [CLOUD PROVIDER]. If we ever need to move a school’s data to another region we will tell that school before it happens, not after.

6How long we keep it

While your school’s agreement is active, and for [RETENTION PERIOD — e.g. 90 days] after it ends, so a school that leaves in March can still export a full academic year. After that, personal data is deleted from live systems, and from backups within [BACKUP CYCLE — e.g. 35 days].

A school can ask for earlier deletion at any point and we will act on it within [N] days. Individual learners can delete their account from settings, which removes their work on the same schedule.

7Your rights

Under India’s Digital Personal Data Protection Act, 2023 — and under the GDPR where it applies — you can ask for access to your data, correction of anything wrong, deletion, a portable export, or an explanation of an automated decision.

Marking is not an unappealable automated decision. Every AI-proposed score is reviewed and can be overruled by a named teacher before a result is released, and every override is logged. If you disagree with a mark, raise it with the teacher first — they can change it and the change is recorded.

If your child is at a school using Intellicamp, address requests to the school as controller; they will reach us and we will act on them. Otherwise write to [email protected]. We respond within [N] days.

8Children’s data

Most people whose data we hold are children. Accounts are created by the school or institute under their own consent and safeguarding arrangements, not by the child. We do not market to students, and there is nothing in the student interface that asks a child to share data beyond their exam work.

No rank or position in the class is computed for any user, at any level. It is not a permission we withhold — the number does not exist in the system.

9Who else is involved

We use a small number of sub-processors to run the service — hosting, email delivery, error monitoring and payments. Each is bound by a data-processing agreement and none may use your data for their own purposes.

The current list is at [LINK TO SUB-PROCESSOR LIST]. Schools on an institutional agreement are notified before we add one.

10Changes, and how you find out

If we change anything material — what we collect, who can see it, how long we keep it — we will email institutional customers at least [N] days before it takes effect, and note the change here with its date. Cosmetic edits are made without notice and do not change the date above.

Any of this unclear?

Ask before you sign.

If a clause here matters to your school’s decision, raise it on the demo call and we will answer it in writing.