Compliance

Built around the rules admissions must follow.

Privacy law, messaging rules, fee regulators and admission norms each ask for proof. Vector Admissions records that proof while the intake runs, so the compliance report is a by-product of the work, not a separate project.

1 · Work happensLeads consented, offers issued, fees taken, refunds approved.
2 · Signed and chainedEach action is signed by its user and added to the audit trail.
3 · Tagged to clausesEvery entry is tagged to the rules it provides evidence for.
4 · Report on demandOne sealed report per intake, filtered by rule or body.
What we map to

Requirements, and what the platform does about each.

Each row names a requirement, says how Vector Admissions supports it, and marks who carries the rest.

Built in works from day one Configurable set per institution Your institution a decision or registration only you can make Planned not yet complete
DPDP Act 2023 and DPDP RulesConsent on every leadEach enquiry stores what the person agreed to, when, and for which purpose, whether it came from a form, WhatsApp, a fair or a counsellor. Messages go only where consent allows.Built in
DPDP Act 2023Applicants under 18Most applicants are minors or just adults. Applicants flagged as under 18 get a guardian-consent step before documents or payment details are collected.Configurable
DPDP Act 2023Access, correction and erasureApplicants and parents can ask to see, correct or erase their data. Requests are queued with owners and due dates. Records the law requires you to keep are retained, and the reason is shown.Built in
DPDP Act 2023Retention of lost leadsLeads that never apply are deleted or anonymised after a window you set. Enrolled students move to your student records under your policy.Configurable
DPDP Act 2023 and CERT-In Directions 2022Breach handling and logsIncidents are logged with times and affected counts, with notice templates. Logs are kept for at least 180 days. Deciding whether and when to notify stays with your institution.Your institution
IT Act 2000, s.43A and SPDI Rules 2011Reasonable securityEncryption, role-based access and signed logging support the "reasonable security" expectation while these rules remain in force alongside DPDP.Built in
Aadhaar Act and Supreme Court privacy judgmentIdentity dataAadhaar numbers are not collected by default. Applicants are identified by application number and the documents your rules require.Built in
TRAI rules on commercial SMS (DLT)Sender IDs and templatesBulk SMS goes only through sender IDs and templates registered on your DLT account, which only your institution can register. Unregistered templates are blocked from sending.Your institution
TRAI rules on unsolicited commercial communicationDo-not-disturb preferencesPromotional calls and SMS are checked against the applicant's preference and the national do-not-call register before a task is created.Configurable
WhatsApp Business policyOpt-in and approved templatesWhatsApp messages need recorded opt-in. Outside the 24-hour service window, only approved templates are sent.Built in
Email consent and unsubscribeOpt-outEvery promotional email carries an unsubscribe link, and an opt-out stops all follow-up sequences immediately.Built in
Fee structure approved by your regulatorOnly approved fee headsFee heads and amounts are loaded from your approved fee structure. A charge outside it cannot be raised without a logged approval, and the applicant sees every head before paying.Configurable
State capitation-fee lawsNo hidden chargesAll amounts collected are tied to a published fee head with a receipt. Cash or off-system collection is flagged in the daily reconciliation.Built in
UGC fee refund policy and your regulator's rulesRefunds on withdrawalThe refund schedule is set by you to follow the applicable policy, shown to the applicant before payment, and each refund goes through an approval trail with a receipt.Configurable
Receipts and reconciliationMoney in, money accounted forGateway and bank entries are reconciled daily, offline challans are matched, and mismatches are listed for the accounts officer.Built in
Central, state and institutional reservation rulesCategories and quotasCategory, EWS, state and management quotas are configured per programme. Each merit decision records the rule that applied. Which rules apply is for your admissions committee to confirm.Configurable
Seat matrix and published intakeOffers within sanctioned seatsOffers cannot exceed the sanctioned intake for a programme and quota. Over-allocation needs a logged approval.Built in
Mandatory public disclosureSeats, fees and rules on the portalSeat matrix, fee structure, eligibility and dates can be published on the applicant portal and kept in step with what the system enforces.Configurable
UGC anti-ragging regulationsUndertakings at admissionThe anti-ragging undertaking is collected from the student and a parent at enrolment, and its status is tracked per student. Submission on the national portal is done by your institution.Configurable
Government and accreditation dataAISHE, NIRF, NAAC and NBA intake figuresIntake, category-wise admissions, gender and state-of-origin figures are exported in clean tables for the returns your institution files.Built in
Electronic records as evidence (Bharatiya Sakshya Adhiniyam 2023, s.63)DisputesOffer, payment and refund records export with hash values and a certificate template. The certificate is signed by the responsible person, not by us.Built in
NAACStudent enrolment and profileSeat fill, category-wise admissions, and students from other states and countries are reported per intake, ready to cite in a self-study report.Built in
NBAQuality of admitted studentsEntry qualifications and the profile of each admitted cohort are exported by programme.Built in
NIRFStudent strength and inclusivityCounts of women, students from other states and economically or socially disadvantaged students are produced from the profile data.Built in
AISHEAnnual enrolment returnEnrolment by programme, category and gender is exported in a clean table for the return.Built in
UGC and AICTE approvalsAdmitted against approved intakeOffers cannot exceed the sanctioned intake, and any approved exception is on the record.Built in
Evidence for a visitAudit-chain extractsInspectors can be given a verified extract of any decision, fee or document trail, with the chain check attached.Built in
Which framework version appliesMapping to your cycleAccreditation formats are revised. We map the report to the version your institution is assessed under, and your accreditation coordinator confirms it.Your institution
ISO/IEC 27001 and SOC 2Security managementControls are designed to align with these standards. Vector Admissions is not certified against either today, and every report and proposal will say so until that changes.Planned
Access controlRoles and sign-inRole-based access with least privilege. Partner agents see only the leads they referred. Counsellors see only their own leads unless shared.Built in
IntegritySigned trailOffers, waivers, refunds and merit changes are signed by the person who made them, and the trail is chained so a later edit shows up.Built in
HostingWhere data livesDeployment in an Indian cloud region is the default recommendation. Government bodies that must use an empanelled provider can deploy there, and the choice is yours.Your institution

This page describes how Vector Admissions is designed, in plain language. It is not legal advice, and it is not a certificate of compliance. Regulations change, and some of the rules above are being brought into force in phases, so your counsel should confirm what applies to your institution.

The report

Nobody assembles it. It is already written.

Because every action is tagged as it happens, the report is a view of the audit trail. Pick a rule or a body, and the evidence is already grouped.

  • One report per intake, filtered by rule or body
  • Counts, dates and named roles, with every figure traced to log entries
  • Sealed with a hash, so the report itself cannot be quietly changed
  • Open items and gaps are listed, never hidden
  • Exports to PDF and CSV, with an electronic-records certificate template

Everything in the preview is example data.

Compliance evidence report · 2027 intakeExample data
Ready
DPDP · consent recorded on leads4,820 of 4,820Complete
SMS sent on registered templates100%Complete
Offers within sanctioned seats610 of 610Complete
Refunds paid inside policy time18 of 191 open
Waivers approved by a named approver42 of 42Complete
Anti-ragging undertakings received396 of 396Complete
Sealedsha256 · pending
How evidence is kept

Every action is a block. Every block holds the one before it.

Logins, document views and downloads, chat messages, decisions, payments and settings changes are recorded as signed, hash-chained entries, in the manner of a blockchain. Change any past entry and every hash after it stops matching, so tampering is visible straight away.

Tamper-evidentEdits and deletions break the chain and show up in verification.
Signed by the personEach entry is signed by the user who acted.
Layered protectionEncryption, role-based access, step-up sign-in and masked fields reduce the chance of a breach. No system can promise zero breaches, so the chain makes sure one cannot be hidden.

Example values are illustrative.

Tell us which rules you work under.

We will walk through the exact report your admissions office would receive.