# Privacy policy
Last updated: 10 July 2026
This policy explains how CampusNeev handles personal data across the public CampusNeev website and the authenticated CampusNeev web and mobile product. It applies to institution representatives, staff, students, guardians, website visitors, and people who contact CampusNeev.

CampusNeev is built for schools and colleges. The institution using CampusNeev controls most student, guardian, staff, academic, fee, attendance, communication, and campus-operation records. The sections below distinguish those institution records from information CampusNeev handles for its own website, account, security, and support operations.
Canonical page: [Privacy Policy](https://www.campusneev.com/privacy)
## Who decides how data is used
An institution generally decides why and how its records are used in CampusNeev. For those records, the institution is generally the controller or data fiduciary, and CampusNeev acts as its processor or service provider under the institution's instructions and agreement. If applicable law or a written agreement assigns these roles differently, that law or agreement controls.

CampusNeev generally acts as controller or data fiduciary for public website enquiries, its direct customer and account-administration records, service security, and its own legal and business operations. Product data included in a support request remains subject to the institution's authority and should be limited to what is necessary to resolve the issue.

## Data the web and mobile product may handle
The exact fields depend on the modules, roles, and workflows configured by an institution. CampusNeev may handle the following categories when they are needed for that configured service:
- Account and access data, including name, email address, phone number, institution, role, sign-in identifier, session information, permissions, and account status.
- Institution and academic setup, including campuses, academic years, classes, programs, departments, sections, subjects, schedules, and staff responsibility.
- Student and guardian records, including identity and contact details, admission and enrollment identifiers, guardian relationships, emergency context, profile photos, and institution-selected documents or fields.
- Sensitive institution records where configured for a clear purpose, such as limited health, disability, emergency, category, or government-reporting details.
- Operational records, including admissions, enrollment, attendance sessions and corrections, notices, communication and delivery states, schedules, approvals, support activity, reports, and controlled exports.
- Fee and finance workflow records, including fee structures, dues, concessions, adjustments, receipts, payment records, cancellations, reminders, and finance exports.
- Movement and safety records, including transport or movement events, scan events, timestamps, route or vehicle context, and precise location when a configured workflow requires location evidence.
- Technical and security data, including IP address, browser or device type, operating system and app version, sign-in and session events, audit history, diagnostics, crash or performance information, and security logs.

## Precise location, photos, and device permissions
CampusNeev may request precise device location when an institution has enabled a movement, transport, or scan workflow that needs location evidence. The location is associated with that operational action and may be visible to authorized institution roles. CampusNeev does not use precise location for advertising or marketing.

Photos or images may include a profile or student photo, or an image or document that an authorized user or institution chooses to add to a configured record. A configured workflow may request camera or photo-library permission for scanning, capture, or image selection. CampusNeev does not use those images for advertising.

Device permissions can be denied or withdrawn in device settings. A feature that depends on a denied permission may not work. Institutions and authorized users should collect location, photos, and sensitive records only when necessary for a documented campus workflow.

## Data collected on the public website
Demo enquiries collect name, work email, institution, and any optional phone number, student-count range, demo focus, message, or routing source supplied. Support requests collect name, work email, institution, and any supplied role, support area, urgency, and message.

Account-deletion requests collect name, verification email, account email or sign-in identifier, institution or campus, relationship to the account, acknowledgement of the verification and retention notice, and any optional context supplied. These details are sent to the CampusNeev public inbox for review and follow-up.

When a person visits the public website, CampusNeev and its website providers may receive standard request, security, and analytics information such as IP address, timestamp, requested URL, referral source, browser and device details, cookie or similar identifiers, and interaction data. The marketing analytics section below explains the analytics tools and choices.

## Why CampusNeev processes data
- Provide and administer institution accounts, role-aware access, configured web and mobile workflows, reports, exports, communication, and support.
- Maintain student, guardian, staff, academic, attendance, fee, movement, and communication records on the institution's instructions.
- Authenticate users, protect accounts, investigate misuse, preserve audit context, troubleshoot failures, and maintain service reliability.
- Respond to demo, support, privacy, and account-deletion requests and keep the limited records needed to complete and document those requests.
- Meet contractual and legal obligations, resolve disputes, enforce authorized-use terms, and protect the rights and safety of CampusNeev, institutions, and users.

## Student and child safeguards
CampusNeev is provided through schools and colleges and is not a consumer service directed at children. The institution is responsible for deciding which student records are necessary, giving required notices, obtaining any authority or consent required by law, and assigning access to appropriate staff or guardians.

CampusNeev applies institution boundaries, role-aware access, controlled exports, and support limits to student and guardian records. Institutions should avoid collecting sensitive fields, precise location, or photos unless a defined workflow requires them.

CampusNeev does not use authenticated student or child data for targeted advertising, cross-site behavioral tracking, or advertising profiles. Public contact, support, and deletion forms are not intended for student records, identity documents, photos, health details, fee records, or other sensitive campus data.

A parent, guardian, student, or other authorized representative may raise a privacy request. CampusNeev may need to coordinate with the institution and verify the requester's identity and authority before changing an institution-controlled record.

## Authenticated product data and marketing-site analytics
The authenticated CampusNeev product does not load Google Analytics, Microsoft Clarity, advertising pixels, or cross-site behavioral tracking. It does generate the authentication, security, audit, diagnostic, and operational logs needed to provide and protect the service. CampusNeev does not use authenticated product records for targeted advertising.

The public marketing website uses Google Analytics and Microsoft Clarity to understand page visits, referral sources, clicks, resource use, form flow, and technical or usability problems. These services may process IP address, browser and device details, page URLs, approximate location derived from network information, identifiers, cookies or similar storage, and interaction data under their own policies.

CampusNeev analytics events do not include names, email addresses, phone numbers, institution names, contact or support messages, copied checklist notes, or deletion-form field values. Public form fields are marked for masking in Clarity. See the [Google Privacy Policy](https://policies.google.com/privacy), [Google Analytics opt-out add-on](https://tools.google.com/dlpage/gaoptout), and [Microsoft Privacy Statement](https://privacy.microsoft.com/privacystatement). Browser privacy settings, script blockers, and cookie controls may also limit public-site measurement.

## Who may receive data
CampusNeev makes institution records available to the institution's authorized users according to configured roles and responsibilities. It does not share authenticated product records with advertising networks for behavioral advertising.

CampusNeev may use service providers for cloud hosting and storage, backups, email or notification delivery, monitoring, diagnostics, security, customer support, and institution-requested integrations. They process the information needed for their service and are subject to their agreements and applicable law. The provider mix can vary by institution configuration and service scope.

For this public website, Cloudflare provides website delivery, security, and email-routing infrastructure; Google provides Analytics; and Microsoft provides Clarity.

CampusNeev may disclose information when required by law, to respond to valid legal process, to protect a person's safety or legal rights, or to investigate abuse or security incidents. Institution-controlled records remain subject to the institution's authority and applicable agreement.

## Retention, return, and deletion
There is no single retention period for every CampusNeev record. Product retention depends on the institution's instructions and agreement, the type of academic or operational record, account status, support and security needs, and legal requirements. CampusNeev retains personal data only for those purposes and deletes, returns, or de-identifies it when the applicable purpose and required retention end.

Website enquiries, support messages, privacy requests, and deletion requests are retained for the time needed to respond, maintain service and request history, resolve disputes, and meet legal obligations. Analytics information follows the settings and retention practices of Google Analytics and Microsoft Clarity.

Deleting an individual account removes or disables that person's access and initiates review of personal data associated with the account. It does not automatically erase institution-controlled attendance, fee, admission, communication, audit, or student records that the institution must retain or that concern other people. Restricted backup copies may remain until the applicable backup cycle expires, and limited request or security records may be retained where necessary.

## Your choices and rights
Depending on where you live, the processing purpose, and applicable law, you may ask to access information about your personal data, obtain a copy, correct or update it, request deletion, withdraw consent where processing relies on consent, object or ask for a restriction, or raise a grievance. These rights are not absolute and may be limited by institution authority, another person's rights, contract, security, or law.

For student, guardian, staff, attendance, fee, or other institution-controlled records, contact the institution first when practical. CampusNeev will route or coordinate the request with the institution where it acts on the institution's instructions.

To close a CampusNeev account and request deletion of associated personal data, use the direct [account deletion form](https://www.campusneev.com/account-deletion). For another privacy request, email [contact@campusneev.com](mailto:contact@campusneev.com). CampusNeev may verify identity, account ownership, and authority before acting, and will explain if data must be retained or the institution must decide the request.

## Security
CampusNeev uses technical and organizational safeguards appropriate to the service context, including institution boundaries, role-aware authorization, controlled exports, scoped support access, security and audit records, and masked public form fields. Access should be limited to people who need the record for an assigned workflow.

No internet or storage system can be guaranteed completely secure. Users should protect sign-in credentials, use only authorized accounts, keep devices updated, and report suspected unauthorized access through [CampusNeev support](https://www.campusneev.com/support). CampusNeev investigates reported security concerns and provides notices when required by applicable law or agreement.

## Processing locations
CampusNeev and its service providers may process data in locations where they operate. Product hosting and transfer arrangements may depend on the institution's service configuration and agreement. Where applicable law requires transfer safeguards or limits, CampusNeev and the institution address them according to their respective roles.

## Policy updates and contact
CampusNeev may update this policy when the service, providers, or legal requirements change. The date at the top shows the latest published revision. Material changes will be communicated through an appropriate website, product, institution, or direct notice where required.

Questions, privacy requests, and complaints can be sent to [contact@campusneev.com](mailto:contact@campusneev.com). Account closure requests should use the [account deletion form](https://www.campusneev.com/account-deletion) so CampusNeev receives the information needed for verification and routing.
