1. Definitions

• Customer means the organization that signs an order form, purchases services, receives a deployment, or authorizes users to access SVECTOR.
• Customer Data means data, documents, records, prompts, files, operational data, candidate data, employee data, telemetry, financial data, industrial data, system data, and other materials submitted to or processed through the services by or for Customer.
• Decision Infrastructure means SVECTOR software, workflows, models, integrations, reports, dashboards, APIs, automation, and governance systems that support evidence-based organizational decisions.
• Output means any score, summary, recommendation, alert, report, profile, risk signal, interview prompt, evidence link, analysis, classification, or other result generated by the services.
• Order Form means a written or electronic ordering document, proposal, invoice, subscription record, statement of work, or enterprise agreement accepted by the parties.

2. Product Families

SVECTOR may provide one or more product families depending on the customer need, deployment scope, and written agreement.

• Foundry: Internal and customer-facing software factory, requirements-to-software workflows, architecture generation, delivery acceleration, integration, and deployment support.
• Verdict: Talent decision infrastructure for leadership hiring, mass hiring, candidate marketplace, assessments, interviews, scorecards, career identity, and human capital decision support.
• OIP: Operational decision infrastructure for industrial, energy, infrastructure, telemetry, predictive maintenance, readiness, monitoring, and operational action workflows.
• Financial Intelligence: Financial risk, AML, fraud, sanctions, due diligence, counterparty risk, transaction monitoring, case management, and compliance escalation workflows.
• Enterprise Decision Systems: Cross-system visibility, executive decision support, workflow intelligence, document processing, internal search, and reporting automation.
• Secure Deployment Fabric: Secure cloud, private cloud, customer cloud, on-premise, air-gapped, isolated, sovereign, or restricted deployment infrastructure.

3. Order of Precedence

If multiple documents apply, the following order controls unless a signed agreement states a different order:

1. Signed master agreement or government contract.
2. Signed order form or statement of work.
3. Data processing agreement, security addendum, or product-specific addendum.
4. These Terms and Conditions.
5. Terms of Use and Privacy Policy.
6. Documentation, support policies, and website descriptions.

4. Customer Responsibilities

Customer is responsible for:

• Providing accurate requirements, data, access, systems, and technical contacts.
• Obtaining all consents, notices, permissions, and lawful bases for Customer Data.
• Ensuring that Customer Data may lawfully be submitted to SVECTOR and processed through the services.
• Configuring roles, permissions, access controls, retention settings, and integrations responsibly.
• Reviewing Outputs before taking action.
• Maintaining human oversight for consequential decisions.
• Complying with employment, privacy, sectoral, AI, safety, cybersecurity, export, sanctions, labor, and anti-discrimination laws.
• Training its authorized users on appropriate use of the services.
• Preventing unauthorized use, credential sharing, and excessive access.

5. Enterprise Data Commitments

Customer owns Customer Data. SVECTOR does not acquire ownership of Customer Data. Customer grants SVECTOR the limited rights necessary to provide, secure, maintain, support, improve, and perform the services, subject to these Terms and any written agreement.

Customer data is not used to train general AI models by default. SVECTOR may use Customer Data for model training, shared model improvement, fine-tuning, benchmark development, or cross-customer research only if Customer gives explicit written permission through an order form, data contribution agreement, or signed written instruction.

SVECTOR may use de-identified or aggregated data for security, reliability, analytics, diagnostics, capacity planning, product quality, and benchmarking, provided the data is not reasonably capable of identifying Customer, an individual, or Customer's confidential operations.

6. Verdict-Specific Conditions

Verdict is a high-risk data product because it may process candidate, employee, assessment, psychometric, interview, resume, video, audio, compensation, mobility, marketplace, and hiring data. Customer must use Verdict with a documented human review process and appropriate legal controls.

• Verdict does not make final hiring decisions.
• Verdict outputs must be reviewed by authorized human decision-makers.
• Customer must not use protected characteristics as decision factors.
• Customer must provide required candidate notices, consents, and accommodations.
• Customer must validate assessment workflows where required by law.
• Customer must monitor for adverse impact and bias where required by law.
• Customer must provide alternative selection processes where required.
• Customer must not use optional Vedic, birth, self-reflection, or entertainment data for employment decisions.
• Customer must not use mobility or job-search signals for retaliation or adverse action against current employees.

7. Biometric, Audio, Video, and Proctoring Conditions

Biometric, audio, video, proctoring, facial analysis, voice analysis, attention analysis, emotion analysis, and similar features may be used only if enabled in an authorized product configuration and only with required notices, consents, retention schedules, deletion processes, and alternative workflows.

Customer must not enable or use biometric features unless Customer has confirmed that the workflow complies with all applicable biometric, privacy, labor, accessibility, employment, and AI governance laws. SVECTOR does not sell, lease, or trade biometric data.

8. OIP and Industrial Use Conditions

OIP may support industrial visibility, predictive maintenance, sensor correlation, readiness monitoring, operational alerts, and decision workflows. Unless a signed agreement expressly says otherwise, OIP is not a certified safety system, emergency shutdown system, medical device, aviation control system, nuclear control system, or substitute for trained operators, engineers, safety personnel, or regulated control systems.

Customer is responsible for validating all alerts, models, thresholds, integrations, and operational actions before relying on them in production environments.

9. Financial Intelligence Conditions

Financial Intelligence may support fraud, AML, sanctions, due diligence, counterparty risk, transaction monitoring, compliance investigation, case prioritization, and audit workflows. Outputs are decision support and do not replace regulated compliance officers, legal counsel, auditors, or mandatory reporting obligations.

Customer is responsible for validating models, reviewing false positives and false negatives, documenting investigations, making regulatory filings, and complying with applicable financial services laws.

10. Secure Deployments

Customer may request private cloud, customer cloud, on-premise, air-gapped, isolated, sovereign, regulated, or restricted deployment. Such deployments require a written agreement that identifies architecture, responsibilities, access controls, update procedures, support boundaries, logging, data residency, security review, incident response, and customer-side infrastructure obligations.

If Customer hosts or controls infrastructure, Customer is responsible for physical security, network security, endpoint security, environment availability, backups, administrator access, change control, and local compliance unless the written agreement states otherwise.

11. Implementation and Professional Services

SVECTOR may provide implementation, integration, configuration, migration, advisory, training, custom software, forward-deployed engineering, security support, and professional services. Deliverables, milestones, acceptance criteria, dependencies, fees, ownership, and timelines must be stated in an order form or statement of work.

Customer delays, unavailable data, incomplete access, changed requirements, third-party dependency failures, or security review delays may affect timelines. SVECTOR is not responsible for delays caused by Customer or third parties outside SVECTOR's reasonable control.

12. Security and Compliance

SVECTOR will implement reasonable technical and organizational safeguards designed to protect Customer Data. Safeguards may include encryption, access controls, audit logs, network controls, customer isolation, identity management, vulnerability review, incident response, personnel confidentiality, secure development practices, and deployment-specific controls.

Customer is responsible for its own user management, endpoint security, credential security, integration configuration, data classification, input review, retention settings, and internal access governance.

13. Data Processing Agreement

Where SVECTOR processes personal data on behalf of Customer, SVECTOR acts as a processor or service provider and Customer acts as controller or business. The parties may enter into a data processing agreement that covers processing instructions, confidentiality, security measures, subprocessors, data subject requests, incident notice, audits, international transfers, return, and deletion.

If no separate data processing agreement is signed and data protection law requires one, Customer must contact legal@svector.co.in before submitting regulated personal data to the services.

14. Subprocessors and Third-Party Providers

SVECTOR may use subprocessors and service providers for hosting, authentication, database infrastructure, observability, security, email, support, payments, analytics, AI processing, OCR, geocoding, and other service functions. SVECTOR will require subprocessors that process personal data on SVECTOR's behalf to protect that data and use it only for authorized purposes.

Customer-selected third-party integrations are Customer's responsibility. Customer authorizes SVECTOR to transmit Customer Data to those integrations as necessary to provide the configured service.

15. Audit Rights

Enterprise customers with a signed agreement may receive reasonable audit rights limited to SVECTOR's security and data protection controls relevant to the services. Unless an agreement says otherwise, audits require at least 30 days written notice, may occur no more than once per year, must be conducted during normal business hours, must not disrupt SVECTOR operations, and must protect SVECTOR confidential information.

16. Detailed Data Processing Terms

Where SVECTOR processes personal data for Customer, Customer instructs SVECTOR to process the data only to provide, secure, maintain, support, improve, and administer the contracted services, and only according to the applicable order form, data processing agreement, product configuration, documentation, and written instructions.

• Customer is responsible for determining the lawful basis, purpose, scope, and categories of data submitted to the services.
• Customer must not submit personal data that is unlawful, excessive, unrelated to the service scope, or prohibited by the applicable order form.
• SVECTOR will not disclose Customer Data except as needed to provide the services, comply with law, protect security, enforce agreements, or as Customer instructs.
• SVECTOR personnel and contractors with access to Customer Data must be bound by confidentiality obligations.
• SVECTOR may process service telemetry, diagnostic logs, security logs, billing records, account metadata, and aggregated or de-identified data as described in these Terms and the Privacy Policy.
• Customer must maintain copies and backups of Customer Data unless a written agreement expressly assigns backup obligations to SVECTOR.

If applicable law requires a written data processing agreement and no executed data processing agreement exists, Customer must not submit regulated personal data until the parties have completed the required agreement.

17. Data Subject Requests and Regulator Cooperation

Customer is primarily responsible for responding to data subject, candidate, employee, consumer, regulator, and authority requests when Customer is the controller, business, employer, or data fiduciary. SVECTOR will provide reasonable assistance where required by law, written agreement, and the nature of the services.

• SVECTOR may redirect a request to Customer where Customer controls the data.
• Customer must provide SVECTOR with timely instructions when assistance is required.
• SVECTOR may decline requests that cannot be verified, are unlawful, expose another person's data, conflict with Customer instructions, or exceed legal obligations.
• Customer is responsible for regulatory filings, employee notices, candidate explanations, adverse action notices, accommodation responses, and appeal processes unless a written agreement assigns a specific task to SVECTOR.
• Each party will reasonably cooperate in inquiries from data protection authorities, labor authorities, consumer authorities, or courts related to the services.

18. Security Schedule

SVECTOR will maintain a security program appropriate to the nature of the services, the deployment model, the sensitivity of Customer Data, and the written agreement. Security controls may vary across hosted, customer-cloud, on-premise, air-gapped, prototype, pilot, and restricted deployments.

No security program can eliminate every risk. Customer must maintain its own security controls and must not rely on SVECTOR as a substitute for Customer's internal governance, endpoint protection, identity management, backup, or compliance program.

19. Incident Response and Breach Cooperation

SVECTOR will maintain procedures for identifying, investigating, containing, remediating, and documenting security incidents affecting the services. If SVECTOR determines that a security incident affects Customer Data and notice is required by law or contract, SVECTOR will notify Customer without undue delay and in accordance with the applicable agreement.

• Notice may include a description of the incident, affected systems, affected data categories, mitigation steps, and recommended customer actions, to the extent known and legally permitted.
• SVECTOR may provide updates as investigation facts develop.
• Customer is responsible for notices to its own users, employees, candidates, regulators, customers, and authorities unless law or the written agreement assigns notice to SVECTOR.
• Customer must promptly report suspected unauthorized access, leaked credentials, data exposure, misconfiguration, malicious files, or vulnerability evidence.
• Customer must not make public statements about an incident involving SVECTOR without coordinating where coordination is legally and practically possible.

20. AI Governance Schedule

SVECTOR may use AI models, language models, retrieval systems, OCR systems, ranking systems, rules engines, embeddings, classifiers, workflow automations, and scoring logic. Customer must evaluate whether its use of these systems is high risk, regulated, sector-specific, or subject to AI governance duties.

• Outputs are decision support and require human review before consequential action.
• Customer must review output accuracy, fairness, explainability, relevance, and suitability for its use case.
• Customer must not remove, hide, or ignore confidence signals, evidence links, warnings, limitations, or review prompts designed to reduce risk.
• Customer must maintain records of configuration, role criteria, assessment criteria, model settings, review decisions, and overrides where required by law.
• SVECTOR may update models, prompts, ranking logic, extraction logic, or workflows to improve security, quality, performance, compliance, or product function.
• Customer data is not used to train general AI models without explicit written permission.
• Where Customer authorizes fine-tuning or model improvement with Customer Data, the order form must identify permitted data categories, purpose, retention, revocation, and restrictions.

Customer is responsible for determining whether impact assessments, conformity assessments, bias audits, procurement reviews, notices, human oversight measures, technical documentation, or post-market monitoring obligations apply to Customer's deployment.

21. Verdict Employment Compliance Schedule

Verdict may be used in sensitive employment contexts. Customer is responsible for ensuring every Verdict workflow is lawful, job-related, consistent with business necessity where required, accessible, validated where required, and supervised by trained human decision-makers.

Customer must not represent that SVECTOR certifies a candidate, guarantees hiring success, guarantees retention, verifies every resume claim, or eliminates the need for background checks, reference checks, legal review, or human judgment.

22. Biometric and Media Addendum

If Customer enables or requests biometric, video, audio, proctoring, liveness, identity verification, voice, facial, gaze, emotion, behavior, or similar features, Customer must confirm that the workflow is lawful in each applicable jurisdiction and that required notices, consents, retention schedules, deletion procedures, and alternative workflows are in place.

• Customer must not enable biometric workflows by default where opt-in, written consent, or separate notice is required.
• Customer must not use emotion, attention, voice, facial, or proctoring signals as final employment determinations.
• Customer must restrict access to recordings, transcripts, screenshots, biometric templates, and integrity signals.
• Customer must honor deletion and destruction obligations for biometric identifiers and biometric information where applicable.
• SVECTOR may refuse or disable biometric configurations that appear unlawful, excessive, discriminatory, deceptive, or unsafe.

23. Candidate Marketplace Addendum

Candidate marketplace functionality may include profile visibility, employer search, recruiter access, contact requests, opportunity matching, candidate blocking, role preferences, compensation preferences, relocation preferences, and activity signals. Customer must use marketplace features only for lawful talent workflows.

• Customer must respect candidate privacy settings and product access controls.
• Customer must not use marketplace data for spam, unrelated marketing, wage suppression, retaliation, discrimination, blacklisting, or unauthorized enrichment.
• Customer must not export or combine marketplace data with external datasets unless authorized and lawful.
• Customer must ensure recruiter messages are accurate, professional, lawful, and related to legitimate opportunities.
• SVECTOR may restrict searches, exports, contact volume, visibility, or account access to prevent misuse.

24. Data Retention, Return, and Deletion Schedule

Retention, return, export, deletion, and destruction of Customer Data are governed by the applicable order form, data processing agreement, product configuration, law, and the Privacy Policy. If no specific retention period is stated, SVECTOR may retain data for the period reasonably necessary to provide services, comply with law, resolve disputes, enforce agreements, preserve security, and maintain business records.

• Customer must configure retention settings and deletion workflows where available.
• Customer must export required records before termination if Customer needs a copy.
• SVECTOR may retain backup copies until overwritten under ordinary backup cycles.
• SVECTOR may retain logs, audit records, billing records, security records, legal hold materials, and dispute files as needed.
• Deleted data may remain in de-identified, aggregated, or statistical form if it no longer reasonably identifies Customer or a person.
• Customer must not demand deletion that would violate law, court order, regulator instruction, employment recordkeeping, tax, audit, or legal hold obligations.

25. Customer Configuration and Admin Controls

Customer controls many operational choices in the services, including user roles, permissions, connected systems, assessment settings, candidate visibility, retention, export permissions, integrations, model settings, workflow stages, scoring criteria, notifications, and access review processes where available.

• Customer is responsible for administrator actions and omissions.
• Customer must promptly remove users who no longer need access.
• Customer must not give shared credentials to recruiters, vendors, interviewers, or contractors.
• Customer must review product configuration before production use and after material changes.
• Customer must ensure role criteria, scoring rubrics, and workflow labels are lawful, accurate, and not misleading.
• Customer must not disable safeguards, warnings, audit trails, human review controls, or candidate notices where legally required.

26. Integration and Third-Party Dependency Schedule

SVECTOR services may connect with customer-selected systems, identity providers, applicant tracking systems, HR systems, finance systems, databases, industrial systems, analytics tools, cloud services, AI providers, OCR services, email systems, and other third parties. Customer authorizes SVECTOR to exchange data with configured integrations as needed to provide the services.

• Customer is responsible for third-party accounts, permissions, data flows, contracts, privacy notices, and security settings for customer-selected integrations.
• SVECTOR is not liable for downtime, data loss, errors, pricing changes, API changes, policy changes, or security incidents caused by third parties outside SVECTOR's control.
• Customer must not connect systems that Customer is not authorized to connect.
• Customer must review field mappings, synchronization rules, export settings, and automated actions before enabling integrations.
• SVECTOR may disable an integration if it creates security, availability, legal, cost, or product risk.

27. Change Management and Product Evolution

SVECTOR may modify the services to improve security, performance, reliability, usability, compliance, architecture, model quality, workflow fit, or commercial viability. Changes may include interface updates, model updates, feature changes, infrastructure changes, provider changes, workflow changes, deprecations, and documentation updates.

• SVECTOR may make emergency changes without advance notice where needed for security, legal compliance, availability, or urgent risk mitigation.
• SVECTOR may deprecate features that are insecure, low-use, legacy, commercially unreasonable, legally risky, or replaced by newer functionality.
• Customer is responsible for testing changes in customer-specific workflows, integrations, and downstream processes.
• Material change notice, migration windows, or backward compatibility commitments apply only if stated in a written agreement.

28. Acceptance, Testing, and Validation

For implementation services, custom work, private deployments, integrations, or customer-specific workflows, Customer must test and validate deliverables before using them in production or regulated workflows. Unless the order form states a different process, deliverables are accepted when Customer uses them in production, confirms acceptance, or does not reject them with specific written defects within 10 business days after delivery.

• Customer must provide realistic test data, acceptance criteria, technical access, and subject matter review.
• Customer must verify that outputs meet Customer's business, legal, sectoral, accessibility, and operational requirements.
• Customer must not use pilot, demo, sandbox, or prototype outputs for production decisions unless expressly authorized.
• SVECTOR is not responsible for defects caused by incomplete requirements, inaccurate data, customer changes, unsupported integrations, or unauthorized modifications.

29. Compliance Documentation and Audit Artifacts

SVECTOR may provide documentation, security summaries, technical descriptions, product limitations, model cards, assessment descriptions, data flow summaries, subprocessor information, or compliance artifacts where commercially reasonable and where disclosure does not compromise security, confidential information, trade secrets, other customers, or third-party obligations.

• Documentation is informational unless expressly incorporated into an order form.
• Customer must not publish confidential security or technical documentation without written permission.
• Customer remains responsible for mapping SVECTOR documentation to Customer's own legal, procurement, and compliance requirements.
• SVECTOR may update documentation as products, models, providers, controls, and laws change.

30. Business Continuity and Disaster Recovery

SVECTOR will use commercially reasonable measures designed to support continuity of hosted services. Business continuity and disaster recovery commitments vary by product and deployment model and apply only to the extent stated in a written agreement.

• Hosted products may rely on cloud providers, infrastructure providers, database providers, and other third-party continuity controls.
• Customer-controlled or on-premise deployments may require Customer to operate backups, restore procedures, failover systems, monitoring, and local incident response.
• SVECTOR is not responsible for Customer's lack of backup, network outage, identity provider outage, endpoint compromise, local infrastructure failure, or customer-side disaster recovery gap.
• Customer must define recovery time and recovery point requirements in the order form if such commitments are required.

31. Regulated Data and Sector-Specific Restrictions

Customer must not submit regulated, restricted, classified, government, healthcare, payment card, criminal justice, export-controlled, defence, children's, biometric, special category, or other high-risk data unless the order form authorizes that data category and the parties have agreed to required controls.

• Healthcare, medical, clinical, or patient data may require a separate written agreement and specialized safeguards.
• Payment card data must not be submitted except through approved payment processors or authorized payment workflows.
• Classified, defence, intelligence, government restricted, or national security data requires separate written authorization and deployment controls.
• Children's data may be processed only where Customer has lawful authority and required consent, notice, and age-appropriate safeguards.
• Export-controlled data may require region, personnel, access, support, and transfer restrictions.
• Customer is responsible for identifying regulated data before submission and for selecting an appropriate deployment model.

32. Fees, Taxes, and Payment

Customer must pay all fees stated in the applicable order form or invoice. Fees may include subscription fees, platform fees, usage fees, deployment fees, implementation fees, support fees, data processing fees, professional service fees, and pass-through third-party costs. Customer is responsible for taxes, levies, duties, withholding, GST, or similar charges unless prohibited by law.

If Customer fails to pay undisputed amounts when due, SVECTOR may suspend services, restrict access, pause professional services, charge late fees where permitted, or terminate the applicable order after notice and a reasonable cure period.

33. Service Levels and Support

Support scope, response times, service levels, uptime commitments, maintenance windows, support contacts, escalation paths, and remedies apply only if stated in a written agreement or support policy. Otherwise, services are provided on an commercially reasonable basis without a guaranteed uptime commitment.

34. Confidentiality

Each party must protect the other party's confidential information using at least reasonable care and may use confidential information only for the purpose of performing under the applicable agreement. Confidential information includes non-public technical, business, financial, security, product, operational, customer, candidate, employee, pricing, architecture, deployment, and roadmap information.

Confidentiality obligations do not apply to information that is public without breach, independently developed without use of confidential information, lawfully received from a third party, or approved for release in writing.

35. Intellectual Property and Deliverables

SVECTOR owns SVECTOR technology, software, products, systems, source code, models, methods, designs, templates, frameworks, documentation, product names, trademarks, and know-how. Customer owns Customer Data. Unless a statement of work expressly assigns ownership of a custom deliverable to Customer, SVECTOR retains ownership of reusable tools, libraries, components, templates, models, processes, and knowledge developed or used in providing the services.

Customer grants SVECTOR a limited license to use Customer Data and Customer materials solely to provide, secure, support, and improve the contracted services, subject to the data use restrictions in these Terms and applicable written agreements.

36. Restricted and Government Deployments

Government, defence, sovereign, national security, critical infrastructure, classified, law enforcement, or restricted deployments require separate written terms. Public website pages do not describe or authorize access to non-public deployments. Such deployments may include special data isolation, personnel requirements, clearance requirements, export restrictions, audit controls, access controls, customer-owned infrastructure, and dedicated security obligations.

37. Legacy Products and Migration

Legacy AI products, chatbot products, inference APIs, model releases, synthetic data tools, automation tools, or historical platforms may be deprecated, discontinued, restricted, migrated, or supported only on limited terms. SVECTOR may provide migration paths to current decision infrastructure products where commercially reasonable. Legacy product data is handled under the applicable agreement and Privacy Policy.

38. Warranties and Disclaimers

Except as expressly stated in a signed agreement, SVECTOR provides the services "as is" and "as available". SVECTOR disclaims warranties of merchantability, fitness for a particular purpose, title, non-infringement, uninterrupted service, error-free operation, and specific results.

SVECTOR does not guarantee that any Output will be accurate, complete, unbiased, lawful for Customer's use case, compliant with Customer's sectoral obligations, or sufficient for a consequential decision without human review and customer-side validation.

39. Limitation of Liability

To the maximum extent permitted by law, neither party will be liable for indirect, incidental, special, consequential, exemplary, punitive, or enhanced damages, or for lost profits, lost revenue, lost goodwill, lost data, business interruption, substitute services, failed hires, employment outcomes, regulatory penalties caused by Customer decisions, or operational losses caused by Customer reliance without validation.

To the maximum extent permitted by law, SVECTOR's total liability arising out of or relating to the services will not exceed the fees paid by Customer for the affected service during the 12 months before the event giving rise to liability, unless a signed agreement states a different cap.

40. Indemnification

Customer will defend, indemnify, and hold harmless SVECTOR from claims, damages, losses, liabilities, penalties, costs, and expenses arising from Customer Data, Customer systems, Customer instructions, Customer misuse, unlawful employment decisions, failure to obtain notices or consents, discriminatory use, regulatory violations, third-party integrations selected by Customer, or Customer breach of these Terms.

41. Term and Termination

The term of each service begins on the date stated in the applicable order form or when access is first provided. Either party may terminate as stated in the applicable agreement. SVECTOR may suspend or terminate services for non-payment, security risk, legal risk, misuse, breach, unauthorized access, or unlawful use.

After termination, Customer must stop using the services. SVECTOR will return, export, delete, or retain Customer Data as required by the applicable agreement, Privacy Policy, data processing agreement, and law.

42. Force Majeure

SVECTOR is not liable for delay or failure caused by events beyond reasonable control, including natural disasters, war, terrorism, civil unrest, epidemic, labor disputes, power failures, internet failures, cloud provider failures, government action, sanctions, export restrictions, cyberattacks, or third-party service failures.

43. Assignment

Customer may not assign these Terms or an order without SVECTOR's prior written consent. SVECTOR may assign these Terms to an affiliate, successor, acquirer, restructuring entity, or purchaser of relevant assets, provided the assignment does not materially reduce Customer's contractual data protection rights.

44. Governing Law and Disputes

These Terms are governed by the laws of India. Courts in Ahmedabad, Gujarat, India have exclusive jurisdiction for disputes not subject to arbitration. The parties will first attempt informal resolution for 60 days after written notice. Where permitted and unless a signed agreement states otherwise, disputes may be resolved through binding arbitration seated in Ahmedabad, Gujarat, India.

45. Notices

Legal notices to SVECTOR must be sent to legal@svector.co.in. Privacy requests should be sent to privacy@svector.co.in. Support requests should be sent to support@svector.co.in.

46. Entity Information

SVECTOR TECHNOLOGIES PRIVATE LIMITED
CIN: U62011GJ2026PTC179633
Ahmedabad, Gujarat, India
Website: www.svector.co.in