Service Delivery Policy

The CoreSphere Technologies is a sole proprietorship business based in Mumbai, Maharashtra, India. Our services are primarily digital and do not involve physical shipping unless specifically stated in a written quotation, proposal or invoice.

This Policy should be read together with our Terms & Conditions, Privacy Policy, Refund & Cancellation Policy, and the applicable quotation, proposal, invoice, subscription plan or product-specific terms.

1. Scope of Delivery

Depending on the service purchased, delivery may include:

• Website design, development, deployment and configuration.
• Custom software, SaaS, WaaS or AI-enabled platform access.
• Customer, tenant, workspace, administrator or user-account activation.
• Software installation, migration, configuration and integration.
• Source files, build files, credentials, documentation or reports.
• Training, onboarding, demonstrations and implementation assistance.
• Maintenance, support, updates, issue resolution and agreed enhancements.
• Other digital deliverables described in the accepted proposal or invoice.

2. Delivery Method

Digital services may be delivered through one or more of the following methods:

• Deployment to a customer-owned or customer-authorised hosting account.
• Activation on infrastructure operated or managed by us.
• Secure email containing links, credentials, reports or documentation.
• Customer portal, product dashboard, cloud storage or repository access.
• Remote implementation, screen-sharing, video call or guided onboarding.
• Another method agreed in writing with the customer.

Access credentials and activation information will ordinarily be sent only to the customer’s registered or authorised contact details.

3. When Delivery Timelines Begin

Unless otherwise stated in writing, delivery timelines begin only after all required commencement conditions have been satisfied, including:

• Receipt and verification of the required advance, subscription or milestone payment.
• Acceptance of the applicable quotation, proposal or scope.
• Receipt of required content, branding, data, credentials, technical details and approvals.
• Provision of server, domain, API, payment, messaging or third-party access where required.
• Completion of KYC, business verification or compliance checks where applicable.

Time spent waiting for customer inputs, approvals or access is not counted as active delivery time unless agreed otherwise.

4. Estimated Delivery Timelines

Delivery dates communicated in a quotation, proposal, invoice, email or project plan are estimates unless expressly stated as fixed commitments.

Timelines may vary depending on:

• Scope, complexity and level of customisation.
• Number and availability of integrations or third-party services.
• Customer response, approval and content-submission speed.
• Testing, security, compliance or data-migration requirements.
• Infrastructure, hosting, API, bank, payment-gateway or app-store review timelines.
• Changes requested after work begins.
• Events outside our reasonable control.

Where a material delay becomes apparent, we will make reasonable efforts to inform the customer and provide a revised estimate.

5. SaaS and WaaS Account Activation

SaaS and WaaS products may be activated automatically or manually after successful payment, registration and verification.

• Trial accounts may be activated immediately or within the period displayed during registration.
• Paid accounts may be activated after successful payment confirmation and any required verification.
• Custom onboarding, migration or configuration may require additional implementation time.
• Access may be subject to plan limits, product-specific terms and authorised-user controls.

If payment is successful but activation does not occur within the communicated period, the customer should contact us with the transaction reference and registered account details.

6. Custom Project Delivery

Custom projects may be delivered in phases or milestones. A milestone may include one or more of the following:

• Planning, wireframes, architecture or design approval.
• Development of agreed modules or features.
• Staging or test deployment.
• User acceptance testing.
• Production deployment or handover.
• Post-launch support or maintenance.

A milestone is treated as delivered when the agreed deliverable, access, demonstration or deployment is made available to the authorised customer contact.

7. Customer Responsibilities

The customer is responsible for:

• Providing accurate, lawful and complete information, content and instructions.
• Providing required access, credentials, approvals and decision-makers on time.
• Ensuring ownership or permission for all supplied text, images, logos, data and intellectual property.
• Reviewing deliverables and providing clear, consolidated feedback within agreed timelines.
• Maintaining secure passwords, devices, email accounts and administrator access.
• Maintaining lawful backups unless backup services are expressly included.
• Complying with applicable laws, licences, industry rules and product-specific obligations.

Delays or errors caused by incomplete, inaccurate or late customer inputs may extend delivery timelines and may require additional charges.

8. Review and Acceptance

Customers should review each deliverable promptly and report material issues in writing within the review period stated in the proposal or, where no review period is stated, within seven calendar days of delivery.

A deliverable may be treated as accepted where:

• The customer confirms approval in writing.
• The customer deploys, publishes, uses or commercially operates the deliverable.
• No material issue is reported within the applicable review period.
• The next milestone or final payment is approved or made.

Minor defects that do not materially prevent intended use do not automatically prevent acceptance, provided they can reasonably be corrected.

9. Change Requests

Requirements outside the accepted scope are treated as change requests. Changes may affect price, timelines, testing and delivery.

We will make reasonable efforts to communicate the impact before proceeding. Urgent work requested without a formal revised quotation may be charged based on time, complexity or the agreed commercial rate.

10. Third-Party Dependencies

Delivery may depend on third-party services such as hosting providers, domain registrars, cloud platforms, payment gateways, banks, UPI services, messaging providers, APIs, app stores, software vendors or internet-service providers.

We are not responsible for delays, outages, policy changes, rejection, account restrictions, review queues or technical failures caused by third parties outside our reasonable control. We will, where possible, assist the customer in identifying a practical resolution or alternative.

11. Payment Gateway and Merchant Service Dependencies

Website payments, payment links, merchant QR, UPI, SmartHub Vyapar, SmartGATEWAY or similar services may require separate bank or payment-provider onboarding, KYC, website review, risk approval, pricing acceptance and technical integration.

Approval and activation of such services are controlled by the relevant bank or payment provider. The CoreSphere Technologies cannot guarantee approval or a specific onboarding timeline.

12. Delivery of Credentials and Sensitive Information

Credentials may be shared through secure or limited-access channels. Customers should change temporary passwords promptly and restrict access to authorised users.

Customers must never send or request UPI PINs, card PINs, CVVs, OTPs, NetBanking passwords or complete card details through email, WhatsApp, telephone or support channels.

13. Data Migration

Data migration is performed only where included in the accepted scope. The customer is responsible for the accuracy, legality, completeness and backup of source data.

Migration outcomes may be affected by source-data quality, format limitations, missing fields, duplicates, corruption or third-party export restrictions. Any cleansing, reconstruction or manual correction outside the agreed scope may be separately chargeable.

14. Training and Onboarding

Training or onboarding may be delivered remotely or through written guidance unless otherwise agreed. Sessions may be limited by duration, number of attendees or number of sessions as stated in the proposal or plan.

Additional training, repeated onboarding or role-specific sessions may be separately chargeable.

15. Support After Delivery

Post-delivery support, warranty, maintenance and update terms depend on the relevant proposal, product plan or support agreement.

• Verified defects within the agreed scope may be corrected during the applicable support or warranty period.
• New features, redesigns, scope changes, third-party changes and customer-caused issues are not treated as defects.
• Ongoing hosting, maintenance, security, backups, monitoring or support are included only where expressly stated.
• Response and resolution times may vary by severity, plan and support availability.

16. No Physical Shipping

Unless a written proposal or invoice expressly states otherwise, all products and services supplied by The CoreSphere Technologies are digital. No physical goods are shipped and no courier or delivery charge applies.

17. Delivery Failure or Non-Activation

If a customer has made a successful payment but has not received the agreed digital delivery or activation, the customer should contact us with:

• Customer and business name.
• Registered email address and phone number.
• Invoice, quotation, subscription or order reference.
• Transaction reference, payment date and amount.
• Description of the missing delivery or activation.

After verification, we will make reasonable efforts to complete delivery, correct the issue, provide an agreed alternative or process an eligible refund under our Refund & Cancellation Policy.

18. Suspension of Delivery

We may pause or suspend delivery where:

• Required payments are overdue.
• Customer inputs, approvals or access remain unavailable.
• Security, legal, compliance or fraud concerns arise.
• The customer materially breaches the applicable terms.
• A third-party provider, bank, hosting provider or authority requires suspension.

Delivery may resume after the issue is resolved, subject to resource availability and any revised timeline.

19. Force Majeure

We are not responsible for delivery delays caused by events beyond reasonable control, including natural disasters, internet or power failures, cyberattacks, epidemics, war, civil disturbance, government action, labour disruption, banking outages, payment-network failures or failure of essential third-party infrastructure.

20. Contact and Delivery Support

We aim to acknowledge genuine delivery or activation issues within two working days.

21. Changes to This Policy

We may update this Service Delivery Policy to reflect changes in services, products, payment methods, technology, legal obligations or business practices. The revised Policy will be published on this page with an updated effective date.