Website, demos, and project enquiries
Terms of Service
Last updated: 7 August 2026
These terms govern use of syedsystems.dev and its enquiry process. They do not, by themselves, license a product or create a software-development contract. Paid work begins only under a separate written agreement accepted by the relevant parties.
1. About Syed Systems
Syed Systems is the software and IT division of SMCTi (Syed Monsur Construction Technology & ideas Ltd.), based at 395 Purba Goran, Adarsha School Road, Khilgaon, Dhaka 1219, Bangladesh. The website presents software products, engineering services, implementation briefs, and technical articles and provides a route for product and project enquiries.
2. When these terms apply
By accessing or using this website, you agree to these Terms of Service and acknowledge the Privacy Policy. If you use the site for an organisation, you confirm that you are authorised to make the enquiry and provide the submitted information on its behalf.
If you do not agree, do not submit the form or continue using restricted parts of the site. Basic viewing of publicly available pages remains subject to applicable law and the acceptable-use rules below.
3. Website information is not a binding offer
Product pages describe intended capabilities, audiences, deployment approaches, and configurable workflow boundaries. Service pages describe typical scope, client inputs, deliverables, methods, and technologies. This information helps frame a discussion but is not a guaranteed specification, quotation, service level, implementation commitment, legal opinion, security certification, or regulatory approval.
A feature, integration, technology, deployment model, delivery date, or support arrangement applies to a purchase only when it appears in the accepted product order, proposal, statement of work, licence, or other written agreement.
4. Product demonstrations
A demonstration is an evaluation conversation, not production access or acceptance of an order. Demonstration data, workflows, interfaces, and integrations may be simplified, configured for a sample scenario, or different from a future production release.
Before a demo, we may ask about users, permissions, expected volumes, data sensitivity, integrations, hosting, retention, and approval rules so the session is relevant. Do not provide live credentials, production customer data, payment information, national identity documents, or confidential source data for an initial demonstration.
5. Quotes, proposals, and project enquiries
A website submission confirms only that an enquiry was sent. It does not require Syed Systems to accept the work, reserve staff, hold a price, meet a deadline, or begin discovery. We may decline a request, ask for additional information, or propose a smaller discovery phase when scope or risk is uncertain.
Unless a written proposal states otherwise:
- prices, schedules, staffing, assumptions, and availability remain estimates;
- a proposal may have an expiry date and can be withdrawn before acceptance;
- taxes, provider charges, licences, cloud consumption, messaging fees, store fees, and third-party subscriptions are not automatically included;
- work outside the stated scope requires a documented change or separate proposal; and
- no binding engagement exists until the required parties accept the written commercial terms.
6. The separate service or licence agreement controls paid work
Each accepted engagement should define the parties, scope, exclusions, deliverables, client inputs, milestones, review process, acceptance criteria, fees, payment schedule, taxes, intellectual-property position, third-party components, security duties, confidentiality, data handling, support, warranties, liability, suspension, termination, and dispute process.
If these website terms conflict with a signed contract or accepted written order for the same subject, that agreement controls to the extent of the conflict. These website terms continue to govern unrelated use of the public site.
7. Client information, access, and decisions
Software delivery depends on timely and accurate client inputs. A project agreement may require the client to provide:
- a product owner or decision maker with authority to approve priorities and resolve questions;
- process owners and representative users for discovery and review;
- accurate policies, business rules, content, brand assets, sample records, and acceptance examples;
- lawful access to systems, APIs, environments, accounts, data, devices, domains, and third-party documentation;
- timely reviews, approvals, testing participation, and consolidated feedback; and
- appropriate licences, consents, notices, and authority for any material supplied to the project.
Missing, late, inaccurate, unlawful, or changing inputs can affect scope, cost, design, test coverage, and schedule. The project agreement should state how those effects are assessed and approved.
8. Scope changes and assumptions
A change can include a new workflow, user role, report, data source, device requirement, integration, migration volume, language, regulatory control, environment, acceptance condition, or support obligation. A request described as a “small change” may still affect architecture, security, testing, or previously accepted work.
Syed Systems may document the impact on price, schedule, dependencies, and risk before starting changed work. Silence, an informal message, a meeting discussion, or a demonstration comment does not automatically amend an accepted scope.
9. Delivery dates and dependencies
Any public statement about process or duration is illustrative. A binding schedule must appear in the project agreement and remains subject to its dependencies, review periods, third-party availability, change control, and force-majeure provisions.
Where a client approval, account, integration environment, source dataset, legal decision, content package, or third-party response is required, the related delivery activity may pause until the dependency is available and usable.
10. Acceptance, release, and handover
The applicable agreement should define how deliverables are reviewed, the time allowed for review, what constitutes a valid defect, what evidence is required, and when a deliverable is accepted. A preference change or new requirement is not automatically a defect when the delivered behaviour matches the accepted scope.
Production release should occur only after the agreed responsibilities are complete, such as content approval, user access, environment readiness, security review, backup or recovery preparation, migration reconciliation, store approval, or operational handover. Support after release is limited to the support scope and period stated in writing.
11. Product licences and permitted use
Viewing a product page or attending a demo does not grant a software licence. A product order or licence agreement should define authorised organisations, users, environments, modules, term, usage boundaries, support, updates, data export, suspension, termination, and any restrictions on copying, resale, reverse engineering, or unauthorised access.
Configuration and integration work may be separate from the product licence. Third-party messaging, identity, AI, cloud, payment, or platform services may require the client to maintain its own approved account and comply with the provider's rules.
12. Intellectual property
Website material
Unless stated otherwise, Syed Systems or its licensors own the website design, text, graphics, code, product descriptions, and original material. You may view and share a normal page link for legitimate business evaluation. You may not republish substantial website content, remove ownership notices, present it as your work, scrape it at a disruptive rate, or use it to create a misleading competing representation.
Enquiry material
You retain rights in material you submit. You give Syed Systems permission to read, copy internally, and use it only as reasonably needed to assess and respond to the enquiry, maintain business records, protect the service, and comply with law.
Project and product rights
Ownership of custom source code, pre-existing tools, reusable components, configuration, documentation, data, designs, product software, and project inventions is not decided by this website. Those rights, licences, restrictions, and handover conditions must be stated in the separate agreement.
13. Open-source and third-party components
Software may use open-source packages, cloud services, APIs, app stores, content systems, model providers, messaging platforms, or other third-party technology. Those components can have their own licences, acceptable-use rules, availability limits, fees, data practices, update schedules, and geographic restrictions.
Syed Systems does not control every third-party change or outage. The project agreement should identify material dependencies and assign responsibility for accounts, approvals, fees, replacements, and service-level risk.
14. Confidential information and initial enquiries
The public enquiry form is not a secure data room and does not create a confidentiality agreement by itself. Send only the minimum information needed to begin the conversation. Marking a message “confidential” does not automatically impose a new legal duty beyond applicable law and existing written agreements.
If technical, commercial, personal, or regulated information is required for evaluation, the parties can first agree a confidentiality arrangement and an appropriate transfer method.
15. Acceptable use
You must not use the website or enquiry endpoint to:
- break a law, violate another person's rights, or submit information without authority;
- probe, scan, exploit, bypass, or interfere with authentication, validation, rate limits, availability, or security;
- introduce malware, destructive code, automated spam, fraudulent requests, or misleading identity information;
- access non-public systems, data, accounts, source code, or administrative functions without written authorisation;
- overload the site or use automated collection in a way that degrades service or ignores published controls; or
- misrepresent an affiliation, endorsement, certification, employment relationship, product right, or commercial commitment.
Good-faith security testing still requires explicit written authorisation that defines targets, techniques, timing, data handling, and emergency contacts.
16. External links and third-party names
Links to SMCTi, social platforms, technology providers, or other external sites are provided for context. A link does not guarantee the destination's availability, accuracy, security, or privacy practice. Product names and marks owned by others remain the property of their respective owners.
17. Website availability and changes
We may correct content, change routes, add or remove product descriptions, suspend forms, perform maintenance, or restrict abusive traffic. We do not promise uninterrupted website availability, permanent publication of a page, or preservation of a public article in its original form.
18. No professional or regulatory advice
Website content about security, banking, fintech, identity verification, public-sector work, data handling, or software delivery is general technical information. It is not legal, tax, accounting, investment, compliance, or regulatory advice. Clients remain responsible for obtaining qualified advice and approving the policies, controls, and lawful basis that apply to their organisation.
19. Website disclaimers
We work to keep the site accurate and useful, but public information can become incomplete, outdated, or unsuitable for a particular environment. To the extent permitted by applicable law, the public website is provided on an “as available” basis without a promise that every page will be uninterrupted, error-free, secure against every threat, or fit for a specific project.
Nothing in this section removes a warranty or duty that cannot lawfully be excluded, or changes a warranty expressly accepted in a separate written agreement.
20. Limitation relating to public website use
To the extent permitted by applicable law, Syed Systems is not responsible under these website terms for indirect or consequential loss caused only by reliance on general public content, inability to access the public site, or use of an external link. Commercial-project and product liabilities are governed by the applicable signed or accepted agreement, not this paragraph.
Nothing in these terms limits liability that applicable law does not allow a party to limit.
21. Suspension and reporting misuse
We may block or restrict requests that appear automated, abusive, unlawful, unsafe, or inconsistent with these terms. If you believe a block is mistaken or want to report a vulnerability or misuse, email info@syedsystems.dev with enough non-sensitive detail for review.
22. Changes to these terms
We may revise these terms when the website, enquiry process, products, services, providers, or applicable requirements change. The current version is the one published on this page with its “Last updated” date. A separate commercial agreement cannot be changed merely by editing this public page.
23. Governing law and disputes
These website terms are governed by the laws applicable in Bangladesh, without overriding any mandatory protection that applies to you. The courts with jurisdiction in Dhaka, Bangladesh will have jurisdiction over a dispute concerning these website terms, unless applicable law requires another forum or the parties agree otherwise in writing.
24. General provisions
If a provision cannot be enforced, it should be limited or removed only to the extent necessary, and the remaining provisions continue. A delay in enforcing a provision is not a waiver. These website terms do not create a partnership, employment relationship, agency, fiduciary relationship, or exclusive supplier arrangement.
25. Contact
Questions about these terms may be sent to info@syedsystems.dev or to Syed Systems at 395 Purba Goran, Adarsha School Road, Khilgaon, Dhaka 1219, Bangladesh.