Terms of Service

Practical terms for using MarGioM.com, submitting inquiries, reviewing proposals, paying invoices, and starting professional software projects.

Effective date: June 20, 2026

Clear operating terms for a software studio workflow.

These terms explain how MarGioM.com, inquiry forms, proposal review, payment requests, support tickets, client portal access, demos, case studies, and project delivery workflows should be used. They are practical operating terms for MarGioM and should be reviewed by a qualified legal professional before publication as final legal terms.

Website, Demos, and Inquiry Use
This website explains MarGioM services, pricing direction, demos, case-study concepts, support options, and project request paths.
  • Website content is informational and may change as MarGioM updates services, pricing direction, processes, and platform features.
  • Submitting a quote, message, support ticket, discovery call request, similar-website reference, proposal request, conversation message, or open application does not create a binding service agreement.
  • Demo previews, internal workflows, and concept case studies are examples of what MarGioM can build. They are not fake client claims or guaranteed results.
  • Visitors agree not to misuse forms, submit malicious files, attempt unauthorized access, or interfere with website, admin, or portal systems.
Quotes, Proposals, and Project Start Rules
A real project should move through scope review, proposal approval, written agreement, and deposit verification before work starts.
  • Published ETB ranges are planning anchors, not automatic final quotes. Final pricing depends on scope, timeline, content readiness, integrations, support level, and risk.
  • A proposal may include scope, deliverables, assumptions, exclusions, milestones, payment schedule, change-request rules, and maintenance options.
  • Project execution should not begin until the proposal is approved, the contract or agreement is signed, and the initial deposit is verified.
  • If there is a conflict between this page and a signed project agreement, the signed agreement should control for that project.
Client Responsibilities
Successful software work depends on accurate information, timely decisions, and clear ownership of provided materials.
  • Clients are responsible for providing accurate requirements, legal content, brand assets, product data, access credentials through secure channels, and timely review feedback.
  • Clients must have the rights to any logos, images, copy, data, third-party assets, or business materials they ask MarGioM to use.
  • Delays in feedback, content, approvals, payment, or third-party access may affect timeline, scope, and delivery dates.
  • Acceptance criteria, testing windows, launch responsibilities, handover documents, and maintenance commitments should be defined in the project agreement or project workspace.
Payments and Deposit Verification
Payments should be handled through clear invoices, provider verification, manual proof review, and activity records.
  • Deposit, milestone, maintenance, and support payments may be handled through manual proof review or configured payment providers such as Chapa or future supported gateways.
  • Manual payment proof is not final until MarGioM verifies it. Gateway payment callbacks are verified server-side before a payment is marked paid.
  • Payment statuses may include requested, checkout created, pending, proof uploaded, under review, manually verified, gateway verified, paid, failed, cancelled, expired, rejected, or refunded.
  • Client access, project activation, and delivery stages may remain blocked until proposal approval, signed agreement, and verified deposit are complete.
Scope, Changes, and Acceptance
Software projects need clear scope control so timelines, cost, and responsibilities stay realistic.
  • Features, integrations, pages, dashboards, data models, roles, support expectations, and launch responsibilities should be listed in the proposal, agreement, or project workspace.
  • Requests outside the agreed scope may be classified as included adjustment, minor change, paid change request, or future phase.
  • Out-of-scope changes, late content, new integrations, urgent timeline changes, or third-party delays may affect price, timeline, and delivery order.
  • Client review, UAT, bug reports, final delivery approval, handover, and maintenance start should be recorded through the agreed workflow whenever possible.
Client Portal and Account Access
MarGioM uses request tracking before a person becomes a verified client and client portal access after approval.
  • Request ID and Access Code tracking is intended for pre-client request, discovery, proposal, contract, and deposit stages.
  • Verified client portal accounts are invite-only and should be used only by the approved client or authorized representatives.
  • Clients are responsible for keeping project IDs, access codes, portal invitations, passwords, and shared credentials secure.
  • MarGioM may suspend, revoke, or limit portal access for misuse, unauthorized access attempts, non-payment, project closure, or security concerns.
Ownership, Confidentiality, and Third Parties
Ownership, confidentiality, source access, licenses, and third-party services should be clearly handled in the signed project agreement.
  • Final ownership, license rights, source-code access, portfolio usage, and handover obligations should be defined in the project proposal or agreement.
  • Clients must have permission to provide logos, copy, images, data, reference files, credentials, business materials, and third-party assets.
  • Project work may depend on third-party services such as hosting, database, authentication, email, analytics, payment gateways, maps, APIs, AI tools, storage, domains, or app stores.
  • Third-party tools may have their own pricing, terms, outages, restrictions, region limits, account requirements, and data practices.
Support, Maintenance, and Careers
Support, maintenance, and hiring communications are handled separately from a standard project request.
  • Support, warranty periods, bug-fix windows, emergency response, maintenance retainers, monitoring, training, and future enhancements should be agreed separately where needed.
  • Submitting a support ticket does not guarantee a specific response time unless an active support or maintenance agreement says so.
  • Open job applications, career messages, or collaboration requests do not guarantee an interview, contract, employment offer, or reply.
  • MarGioM may update services, support paths, payment methods, client portal features, and hiring processes as the company grows.
Disclaimers and Limits
These terms describe practical operating expectations, but paid work should be governed by a written agreement.
  • MarGioM works to provide reliable software services, but website content, demos, estimates, and public materials are provided for general information and planning.
  • MarGioM is not responsible for delays caused by missing client input, third-party service outages, payment provider issues, domain problems, app store reviews, hosting incidents, or unauthorized changes outside MarGioM control.
  • To the extent permitted by applicable law, MarGioM's liability should be limited by the signed agreement for the relevant project.
  • These terms may be updated. Continued use of MarGioM.com after updates means the updated terms apply to website use, while signed agreements continue to control their related projects.

Before paid work begins

Use the proposal and agreement as the source of truth.

These terms help explain the website and normal working process. For real projects, MarGioM should confirm the specific scope, deliverables, payment schedule, ownership, support expectations, and change-request policy in a written proposal and agreement.

Request a proposalRead privacy policyAsk a terms question

Last updated June 20, 2026. These terms are practical operating notes and should be reviewed by a qualified legal professional before publication as final legal terms.