Clear Terms for Professional Technology Services

Application of These Service Terms

These Service Terms apply when OrreryHIM provides paid professional or technical services.

Services may include:

• custom desktop or web-based software;
• school-management software and related modules;
• WordPress and Divi website development;
• custom HTML, CSS and JavaScript work;
• payment-gateway integration;
• SQL databases and reporting solutions;
• hosting, domain, SSL and email configuration;
• maintenance, troubleshooting and technical support;
• data migration, compilation or import work;
• technical consultation and system review.

Acceptance of a quotation, payment of an advance, written approval to begin work or use of a delivered service may indicate acceptance of these terms.

Order of Project Documents

A project may be governed by several documents and communications.

Unless otherwise agreed, the following order should normally be used when interpreting the engagement:

1. signed or expressly accepted project agreement;
2. project-specific quotation or proposal;
3. approved written change requests;
4. these general Service Terms;
5. ordinary project correspondence and discussion.

A specific written term for a project takes priority over a general term where both cannot reasonably operate together.

Quotations and Proposals

A quotation is prepared from the information available when the requirement is discussed.

Unless stated otherwise:

• the quotation covers only listed deliverables;
• pricing does not include unidentified future requirements;
• third-party charges may be separate;
• government taxes may apply as legally required;
• quoted timelines depend on timely client cooperation;
• the quotation may have a limited validity period.

OrreryHIM may revise a quotation if the requirement, technical condition, data volume, platform or delivery expectation changes before work begins.

Scope of Work

The project scope consists only of the pages, features, modules, reports, integrations and services specifically identified in the accepted project document.

Items not expressly included are outside scope, even where they may appear related to the project.

Where wording is ambiguous, the parties should clarify the requirement before development continues.

Requirement Accuracy

The client is responsible for clearly explaining its operational needs, users, data, reports, rules and expected output.

OrreryHIM is not responsible for requirements that were:

• not disclosed before development;
• described incorrectly or incompletely;
• changed after approval;
• based on assumptions not confirmed in writing;
• dependent on unavailable third-party access;
• contradictory to another approved requirement.

Complex workflows should be supported by forms, samples, screenshots, report formats or written process descriptions.

Client Responsibilities

The client must provide information and cooperation reasonably required to complete the work.

This may include:

• correct contact and organisation details;
• approved text, photographs and documents;
• domain, hosting and platform access;
• software licences and third-party accounts;
• sample data and existing database information;
• timely feedback and decisions;
• authorised project representatives;
• testing and approval within the agreed period.

Delays caused by missing content, unavailable access or late decisions may extend the project schedule.

Client Content and Permissions

The client confirms that it has the right to use all content, data, photographs, logos, documents, names and trademarks supplied for the project.

The client is responsible for:

• copyright and licensing permissions;
• accuracy of published information;
• privacy notices and consent requirements;
• legal authority to process supplied data;
• approvals required from its management or institution;
• ensuring content is not unlawful or misleading.

OrreryHIM may decline material that appears unlawful, unsafe, fraudulent or technically unsuitable.

Access Credentials and Security

Where access is required, the client should provide only the permissions necessary for the agreed work.

Wherever practical:

• temporary accounts should be created;
• permissions should be restricted;
• credentials should be changed after completion;
• OTP and banking passwords should never be shared;
• live personal data should be masked for testing;
• critical changes should be backed up first.

The client remains responsible for securing its own users, devices, email accounts and internal access.

Project Payments

Payment stages will be defined in the quotation, invoice or agreement.

Depending on the project, payment may include:

• an advance before work begins;
• milestone payments;
• payment before final deployment or handover;
• annual hosting or maintenance renewal;
• separate third-party licence charges;
• fees for additional or urgent work.

Work may be paused where an agreed payment is overdue.

Taxes and Third-Party Charges

Applicable taxes will be charged where legally required.

Third-party costs may include:

• domain registration and renewal;
• hosting and cloud infrastructure;
• SSL certificates;
• premium themes and plugins;
• email, SMS or messaging services;
• payment-gateway charges;
• API or software licences;
• stock images, fonts or media.

These charges may change according to the provider and are not controlled by OrreryHIM.

Project Schedule

Any delivery estimate assumes timely receipt of requirements, content, access, feedback and payment.

The schedule may change because of:

• client delay or unavailable decision-makers;
• changes to scope;
• unexpected condition of existing systems;
• third-party approval or API delay;
• data-quality or migration problems;
• security incidents or infrastructure failure;
• events beyond reasonable control.

A delivery estimate is not an absolute guarantee unless a fixed deadline and its dependencies are expressly agreed in writing.

Revisions and Change Requests

Included revisions apply only to correction or refinement of work already within the approved scope.

A request may be treated as additional work where it:

• adds a new feature, page, module or report;
• changes an approved workflow;
• requires redesign after approval;
• introduces another platform or integration;
• requires substantial data correction;
• results from incorrect client instructions;
• is requested after final acceptance.

Additional work may require a revised price and schedule.

Design Approval

For website and interface work, the client should review design, layout, wording, colours, navigation and mobile presentation.

Once a design stage is approved:

• development may proceed on that basis;
• major redesign may be chargeable;
• later personal-preference changes may affect delivery;
• approval should be provided by an authorised representative.

Different screens, browsers and devices may render minor visual differences.

Software and Database Testing

The client must test the system using realistic scenarios before full operational reliance.

Testing should include:

• normal data entry and processing;
• incorrect and incomplete input;
• permissions and user roles;
• reports, totals and calculations;
• printing and exported documents;
• backup and restoration procedures;
• payment and transaction workflows where applicable.

Business rules and calculations must be verified by the client, because OrreryHIM may not independently know every institutional policy or operational exception.

Errors and Correction Period

OrreryHIM will make reasonable efforts to correct reproducible defects in agreed features reported within the applicable testing or warranty period.

A defect does not include:

• a new requirement;
• a change of preference;
• incorrect client data;
• failure of a third-party service;
• unauthorised modification;
• use outside the agreed environment;
• problems caused by expired or unsupported software.

The applicable correction period should be stated in the quotation or delivery communication.

Delivery and Acceptance

Delivery may occur through deployment, file transfer, website publication, software installation, access credentials or another agreed method.

The client should review delivered work promptly and report any scope-related issue within the stated review period.

The work may be treated as accepted where:

• written approval is provided;
• the system is placed into live operational use;
• the final payment is made;
• no material issue is reported during the review period;
• the client requests further work after delivery.

Training and Documentation

Training, user manuals, video instructions or written documentation are included only where specified.

Unless otherwise agreed:

• training is limited to the agreed number of sessions;
• the client should nominate suitable participants;
• repeat training may be chargeable;
• staff turnover does not create unlimited retraining rights;
• custom documentation may require additional fees.

Ownership of Client Material

The client retains ownership of original material supplied by it, including its:

• business data;
• institutional records;
• logos and branding;
• approved photographs;
• documents and written content;
• lawfully owned databases.

OrreryHIM receives permission to use that material only as reasonably required to deliver the project.

Source Code and Development Components

Source-code ownership depends on the project-specific agreement.

Unless expressly transferred in writing:

• OrreryHIM retains ownership of reusable development methods;
• general libraries and utilities remain with their owner;
• third-party components remain subject to their licences;
• existing OrreryHIM frameworks are not automatically assigned;
• the client receives the usage rights necessary for the delivered solution.

Third-Party Software and Licences

Projects may include WordPress, Divi, plugins, libraries, operating systems, database engines, payment SDKs or other third-party components.

Those components remain subject to their own:

• licence conditions;
• renewal fees;
• feature limitations;
• support policies;
• security updates;
• compatibility decisions.

OrreryHIM cannot grant ownership or rights that belong to a third-party provider.

Portfolio and Project References

Unless confidentiality or another written restriction applies, OrreryHIM may identify completed work in a professional portfolio.

A portfolio reference may include:

• the organisation or project name;
• a general description of completed work;
• a public screenshot or public website link;
• non-confidential technical categories.

Confidential records, private credentials, protected data and unpublished client information will not be intentionally disclosed as portfolio material.

Domains, Hosting and SSL

Domains, hosting and SSL services may be purchased directly by the client or arranged through OrreryHIM.

The client is responsible for:

• providing correct registration details;
• renewing services before expiry;
• maintaining valid billing and contact information;
• following provider usage policies;
• avoiding unlawful, abusive or resource-intensive activity.

Expired domains, hosting, licences or certificates may cause website, software or email interruption.

Hosting Availability

Hosting depends on external infrastructure and cannot be guaranteed to remain continuously available.

Service may be affected by:

• provider maintenance;
• hardware or network failure;
• resource limits;
• cyberattack or malware;
• DNS and domain problems;
• account suspension;
• events outside reasonable control.

Any uptime commitment must be obtained from the relevant hosting provider or expressly agreed in writing.

Backups

Backup responsibility should be defined for each service.

Unless a managed-backup service is expressly included:

• the client should maintain independent backups;
• hosting backups should not be the only recovery method;
• backup restoration is not guaranteed without verification;
• large or special backups may require additional storage;
• restoration work may be chargeable.

The client should periodically confirm that important data can be restored.

Payment-Gateway Integration

OrreryHIM may integrate a website or software system with a payment gateway, but the gateway and banking network remain independent third-party services.

The client is responsible for:

• merchant-account approval;
• accurate KYC and business information;
• merchant charges and settlement rules;
• refund and chargeback procedures;
• compliance with gateway and banking requirements;
• reconciliation of transactions and settlements.

OrreryHIM does not control bank approval, payment success, settlement timing, chargebacks or gateway downtime.

Data Migration and Import

Data migration depends on the completeness, consistency and structure of the source data.

The client should:

• retain an original backup;
• verify sample migrated records;
• identify duplicate or incomplete data;
• confirm field mapping and business rules;
• approve totals and reports after migration.

Extensive cleaning, correction or manual reconstruction of data may be treated as additional work.

Support and Maintenance

Project delivery does not automatically include unlimited lifetime support.

Support may be provided through:

• a defined correction period;
• annual maintenance contract;
• hosting and maintenance plan;
• paid support request;
• separate upgrade or enhancement quotation.

The applicable support channel, response expectation and covered work should be stated in the relevant arrangement.

Support Exclusions

Support may be chargeable or excluded where an issue results from:

• client or third-party modification;
• unsupported hardware or software;
• expired licences or hosting;
• malware, hacking or credential compromise;
• incorrect data entry;
• internet, electricity or network failure;
• new requirements or changed business rules;
• third-party platform updates.

Remote and On-Site Services

Services may be delivered remotely unless an on-site visit is included or separately agreed.

On-site work may involve additional:

• travel expenses;
• accommodation;
• local transport;
• daily professional charges;
• scheduling requirements.

The client should provide suitable access, workspace, electricity, network connectivity and authorised staff.

Confidentiality

Each party should protect confidential information received for the project and use it only for the relevant engagement.

Confidential information does not normally include information that:

• is already public without breach;
• was independently known lawfully;
• is received lawfully from another source;
• must be disclosed under legal authority;
• is independently developed without using protected material.

Highly sensitive projects may require a separate confidentiality agreement.

Security Limitations

OrreryHIM will use reasonable care appropriate to the agreed service, but no website, server, application, device or network can be guaranteed completely secure.

The client remains responsible for:

• strong passwords and user controls;
• secure staff behaviour;
• device and network protection;
• timely updates and renewals;
• appropriate backup and incident response;
• reporting suspected compromise promptly.

No Guaranteed Commercial Result

Unless specifically agreed, OrreryHIM does not guarantee:

• search-engine ranking;
• website traffic or enquiries;
• revenue, admissions or sales;
• social-media reach;
• approval by external platforms;
• continuous compatibility with future technology;
• a specific business or institutional outcome.

Technology can support a process, but results also depend on content, operations, market conditions, users and third-party platforms.

Limitation of Liability

To the extent permitted by applicable law, OrreryHIM will not be responsible for indirect or consequential loss arising from a service.

This may include:

• loss of anticipated profit;
• business interruption;
• loss of opportunity;
• third-party claims;
• failure of external providers;
• loss caused by unauthorised modification;
• loss caused by missing backups or client negligence.

Where liability cannot legally be excluded, any contractual limitation remains subject to mandatory statutory rights.

Force Majeure and Events Beyond Control

Neither party should be treated as responsible for delay caused by events reasonably beyond its control.

Such events may include:

• natural disaster or severe weather;
• internet or electricity failure;
• government restriction;
• war, civil disorder or epidemic;
• data-centre or provider failure;
• cyberattack affecting external infrastructure;
• serious illness or unavoidable emergency.

Suspension and Termination

OrreryHIM may pause or terminate work where:

• payment remains overdue;
• required access or information is repeatedly unavailable;
• the client requests unlawful or harmful work;
• communication becomes abusive or threatening;
• continued work creates serious security or legal risk;
• the client materially breaches the agreed terms.

The client may end a project by written notice, but remains responsible for completed work, reserved time, purchased services and non-cancellable commitments.

Project Inactivity

A project may be treated as inactive if required content, feedback, access or approval is not provided for an extended period.

When an inactive project is restarted:

• the schedule may need to be revised;
• development resources may no longer be immediately available;
• technology or pricing may have changed;
• a restart or review charge may apply;
• old third-party licences may require renewal.

Dispute Resolution

If a disagreement arises, both parties should first attempt to resolve it through written discussion.

The discussion should identify:

• the relevant scope or agreement term;
• the specific disputed work or payment;
• supporting communication and evidence;
• a practical proposed resolution;
• a reasonable period for response.

Informal resolution does not remove any legal remedy available to either party.

Governing Law and Jurisdiction

These Service Terms are governed by the laws of India.

Subject to mandatory consumer rights and any jurisdiction that cannot lawfully be excluded, disputes relating to OrreryHIM services should fall within the jurisdiction of competent courts at Solan, Himachal Pradesh, India.

A project-specific agreement may define an alternative lawful dispute-resolution process.

Severability and No Waiver

If a provision is found invalid or unenforceable, the remaining provisions should continue to operate to the extent legally possible.

Failure to enforce a term immediately does not automatically waive the right to enforce it later.

Changes to These Service Terms

OrreryHIM may update these general terms for future engagements.

The terms applicable to an existing project are normally those accepted when that engagement began, together with any later written amendment agreed by both parties.

Contact OrreryHIM

Questions regarding these Service Terms may be directed to: