Explore without student data.
Public examples use prepared content. Keep real answer sheets and student records out of previews and general support messages.
A clear account of what this website handles, how institutional assessment differs, and where your choices and responsibilities begin.
Public examples use prepared content. Keep real answer sheets and student records out of previews and general support messages.
A live service needs agreed instructions, access, providers, retention and release rules before student processing begins.
A correction is not automatic permission to train a model. The proposed learning process requires rights checks and verified evidence.
This notice covers suhimark.com, its SIH walkthrough, invitation-only sample preview, demo-booking links and contact channels. “SuhiMark”, “we” and “our” refer to the SuhiMark service. Our contact for privacy questions and complaints is support@suhimark.com.
The public website explains a product in development. Prepared examples are not a live examination record system. A live institutional pilot or service requires a separate agreement and service-specific notice identifying the responsible parties, permitted processing and applicable safeguards. The V7 architecture describes intended controls; a diagram does not establish that every control is deployed.
We do not embed advertising pixels or behavioural analytics in the current site. Hosting security and operational records are separate from advertising tracking. We do not sell personal information collected through these website interactions.
The preview-access form receives an email address, institution code and invitation token. It validates the form and token and uses a keyed, time-bucketed value derived from the email to limit repeated attempts. The handler does not save the raw email or institution code as an account profile. Hosting and security records may still exist.
A successful check sets a signed, one-hour preview cookie. It unlocks a sample workspace; it does not verify institutional identity or create a staff role. An institution code is not authorization to access real student records.
Files selected in the current sample workbench use a browser-local preview rather than a production upload service. Use synthetic material only. The preview is not an approved channel for real student records, confidential exams or identity documents.
suhimark-theme remembers light or dark mode on your device until you clear site storage or change the preference. If storage is unavailable, the theme still works for that visit.suhimark-preview is set after successful preview access. It expires after one hour and is HttpOnly, SameSite Strict, and Secure on HTTPS. Clearing site cookies removes the local session.The WhatsApp control is a link, not an embedded chat tracker. Opening its contact panel does not load a WhatsApp script. Choosing a WhatsApp link opens the external service; you decide whether to send the prefilled message.
For a separately agreed live service, the institution usually determines the educational purpose and authorized recipients. SuhiMark processes assessment information under agreed instructions; any independent purpose needs its own lawful basis and notice. Roles must be documented for the actual arrangement.
The agreed dataset may include student IDs and rosters; scanned answers and handwriting; questions, answer keys and rubrics; literal transcriptions and evidence regions; proposed marks and feedback; reviewer discussions and corrections; approval history; checked reports; parent contacts and delivery permissions. Collect only what the agreed assessment needs.
These are V7 service boundaries, not a claim that live integrations are available in the preview. Actual processing, providers and retention must be settled before a live pilot.
Website and enquiry information supports requested pages, replies, demonstrations, security and applicable obligations. Asking about a demo does not authorize student-data processing, unrelated marketing or model training.
Where processing relies on consent, it must be specific to the described purpose and can be withdrawn through support@suhimark.com. Withdrawal affects future consent-based processing; it does not undo earlier lawful processing or records required under another applicable obligation. If the service cannot continue without necessary information, we will explain the consequence.
A live institutional arrangement must identify a valid legal basis for each purpose. A teacher’s upload, invitation token or parent email is not a substitute for required authority, notice or consent.
Public booking and enquiries are intended for adults arranging institutional services. Children should not submit personal data or create a preview identity. If a child’s information was submitted inappropriately, contact support@suhimark.com so we can investigate and arrange appropriate removal or restriction.
Before processing children’s records, the institution and SuhiMark must establish applicable age rules, required parental or guardian authorization, verification and permitted educational use. India’s DPDP framework defines a child as a person under 18; obligations and exemptions depend on the provisions in force and processing context. An educational purpose is not an automatic exemption. See the official DPDP Act.
Parent delivery is separate. The intended service requires the institution to verify the recipient relationship and enable delivery of the approved report. Correct outdated or wrong addresses before dispatch. Revocation can stop future access; it cannot recall an already-downloaded report.
AI proposals can be wrong. In AI, clear copies complete after automated evaluation and checks; uncertain copies require SuhiMark expert resolution before handover. AI+ includes expert review of every question in every copy. Institutional publication remains separate in both modes. Unclear writing must remain unresolved until evidence is available; it must not be invented or converted into a zero.
The public walkthrough does not train models or call a live grading model. For a live service, the approved provider, permitted payload, location, retention and provider-training conditions must be documented before use. We do not promise zero provider retention or India-only processing without verifying the specific service and account.
Correction and training are different purposes. The proposed learning process admits only permissioned, source-linked, quality-checked examples. It separates reader and grader training, freezes independent test groups, and tests candidates before promotion. A software, rubric or prompt fix may be more appropriate. A reviewer correction does not automatically enter a training dataset.
Future learning agreements must specify lawful authority, permitted uses, dataset and model lineage, retention and withdrawal effects. Removing an example is not guaranteed erasure of its influence from already-trained weights. Existing exam decisions remain tied to their approved versions.
The website is internationally accessible. Hosting, scheduling, email and messaging providers can process information outside your country. The public site is not an India-only data-residency service.
A live deployment needs a documented location and transfer assessment before student information reaches a provider. Where regional restrictions apply, ineligible external routes must stay unavailable. Contracts, onward transfers and safeguards must be checked for the actual deployment.
Law depends on the people, purpose, service and jurisdiction. India’s DPDP Act and 2025 Rules have phased commencement; this notice does not imply every provision was operative on its update date. See the notified Rules and commencement provisions.
Where EU or UK data-protection law applies, relevant lawful-basis, rights, processor and transfer requirements must be addressed. US children’s and education-record rules, including COPPA or FERPA where applicable, need their own assessment. Worldwide access is not worldwide compliance certification. See the EDPB transfer guide and FTC education-service guidance.
Retention depends on purpose and binding obligations. Theme preferences stay until cleared; preview cookies expire after one hour; prepared review state lasts for the page session. Security counters use short attempt windows, but a counter’s expiry is not proof that its database row or hosting logs have been erased.
Enquiry and booking correspondence may remain while the request, follow-up or a legitimate recordkeeping need continues. There is no single verified deletion period covering all external-provider records. Ask what we hold or request deletion through support@suhimark.com; we will explain information that must be retained and why.
Before live processing, the institutional agreement must set retention and deletion rules for originals, derivatives, transcriptions, discussions, decisions, reports, delivery records, backups and separately permitted learning artifacts. Deletion must account for derived copies and provider systems. Backups and legal holds may require a different timetable, not a promise of instant erasure.
The current website uses HTTPS, signed preview sessions, server-side token validation, request-size and origin checks, and database-backed preview-attempt limits. These reduce particular risks; they do not make the system immune to misuse.
The institutional design adds tenant-scoped permissions, private storage, controlled document workers, versioned decisions, bounded retries and audit records. Complete production integration, access review and security verification are prerequisites for live use, not certifications conferred by this page.
Report suspected exposure, a wrong-recipient report, unauthorized access or a security issue to support@suhimark.com, with the affected page, time and a minimal description. Do not send passwords, tokens or unredacted student records. We will investigate and handle applicable notification and remediation duties under relevant law and the service agreement.
Contact support@suhimark.com to ask about information associated with you, request correction or deletion, withdraw consent where relevant, raise a concern or request this notice in a more accessible form. Applicable law may also provide access, portability, restriction, objection, nomination or regulatory-complaint rights, depending on jurisdiction and processing.
A privacy request differs from an academic appeal. For a mark or feedback dispute, start with the institution so the published version, evidence and authorized reviewer can be identified.
Updates will show a revised date and version. Material changes requiring a new notice or consent must be addressed before the new purpose begins. Continued browsing does not authorize training or a new student-data use.
Questions: support@suhimark.com. Related document: Website & preview terms.
For privacy requests, complaints, or questions about these terms, contact SuhiMark. Please describe the issue without attaching student papers, passwords or identity documents.
support@suhimark.com ↗Choose what you’d like help with. Review your message in WhatsApp before sending.
General enquiries only. Please don’t send student papers, marks, passwords or identity documents. Privacy details