A website enquiry does not guarantee a demo, pilot place, account, delivery date, implementation, migration, hardware, training, support level, or product availability.
1. Current website
The public website is informational. It does not automatically create or deliver a SchoolSync account after a visitor submits the email handoff.
2. Future digital service delivery
If a pilot or subscription is agreed, access is expected to be delivered electronically to authorized school users after the documented prerequisites are complete. The signed order or pilot plan must identify the target environment, modules, authorized contacts, start date, onboarding stages, acceptance checks, and support channel.
3. School prerequisites
Depending on scope, the school may need to provide verified organization details, authorized administrators, approved data, configured academic and fee structure, devices, connectivity, printer access, messaging or payment-provider accounts, policy decisions, and staff availability for testing and training.
4. Data migration
Migration is not assumed to be included. The order must state the source formats, records, history period, validation responsibilities, correction process, acceptance criteria, excluded data, schedule, and charges. No school should send production data through the public enquiry form.
5. Hardware, printers, cards, and consumables
SchoolSync is planned primarily as a digital service. Thermal printers, attendance devices, QR cards, cameras, mounts, paper, network equipment, installation, travel, and replacements are not included unless the order expressly lists them. If physical goods are sold, the seller, delivery area, dispatch estimate, shipping charge, risk, warranty, return, replacement, and support terms must be supplied before payment.
6. Training and support
Training format, attendees, sessions, language, documentation, support hours, response targets, channels, escalation, and any on-site work must be recorded in the order or support schedule. The marketing website does not create a service-level agreement.
7. Acceptance and changes
The pilot or implementation plan should define who may accept delivery, the test period, material defects, correction window, change requests, dependencies, and the effect of customer delay. New modules, customization, integrations, or volume changes require written agreement.
8. Suspension, termination, and data return
The school agreement must define suspension grounds, notice, export availability, termination assistance, data return, retention, deletion, backup expiry, and legal holds. The website itself makes no fixed application-data commitment.
9. Contact
Questions about a proposed delivery plan may be sent to vyapartechstudio@gmail.com.