Terms of Service

1. 01

   Plain-language agreements

   We draft contracts in accessible language so founders, legal teams, and operators can align quickly. Legal definitions appear alongside operational examples, reducing ambiguity during rollout. You receive version history for every clause so negotiations remain transparent.

2. 02

   Service availability commitments

   MAR targets 100% monthly uptime across core services, excluding scheduled maintenance windows announced at least seven days in advance. If an outage breaches our service level, customers receive service credits or tailored remediation as described in their order form. We post postmortems within forty-eight hours detailing root cause and long-term fixes.

3. 03

   Backward compatibility discipline

   API and interface changes are introduced with deprecation windows of no less than one hundred eighty days. We provide migration guides, sample code, and office hours to ensure smooth transitions. Breaking changes require explicit customer acknowledgement before rollout.

4. 04

   Mission alignment checkpoints

   Every engagement begins with a mutual success plan capturing deliverables, owners, and measurable impact targets. We revisit the plan each month to confirm assumptions still hold. If goals shift, we renegotiate scope instead of silently changing the workstream.

5. 05

   Transparent billing

   Invoices reflect the pricing schedule attached to your agreement, with line items that map to modules, usage bands, and professional services. We give fourteen days notice before any subscription renewal and highlight opportunities to scale down unused capacity. Late payment policies include grace periods and collaborative remediation plans rather than automatic suspension.

6. 06

   Fair use parameters

   We support ambitious workloads, but automated abuse, scraping, or stress-testing outside agreed scopes is prohibited. If traffic threatens platform stability, we coordinate throttling strategies instead of enforcing silent blocks. Customers receive metrics dashboards to monitor their own consumption.

7. 07

   Collaborative roadmap input

   Customers may submit feature requests through the MAR feedback portal, where they can vote, comment, and track progress. While we cannot guarantee prioritization, we disclose whether a request is on the roadmap, under review, or out of scope. High-impact requests may evolve into co-development projects with shared milestones.

8. 08

   Resilience-first architecture

   We operate redundant infrastructure across multiple availability zones with automated failover. Disaster recovery drills verify that recovery time and recovery point objectives remain within contracted thresholds. Customers receive the drill summaries and are welcome to attend tabletop reviews.

9. 09

   Support expectations

   Standard support includes business-day ticket response within four hours and priority incident paging. Enhanced plans add twenty-four-seven coverage, named solution engineers, and quarterly architecture reviews. We measure support quality through satisfaction surveys and publish aggregated outcomes.

10. 10

    Product integrity

    We do not include third-party code with restrictive licenses or known vulnerabilities in our builds. Supply chain monitoring ensures dependencies are patched promptly. Customers can request a software bill of materials for audit purposes.

11. 11

    Responsible AI use

    Generative and predictive features include guardrails to prevent misuse, bias amplification, or harmful automation. Customers must configure acceptable use policies for their teams, and MAR provides templates to accelerate that work. We encourage ongoing review of model behavior and will collaborate on retraining when needed.

12. 12

    Customer advocacy

    When regulator or stakeholder questions arise, MAR drafts technical narratives explaining architecture, controls, and mitigations. Our leadership team is available for joint briefings to demonstrate accountability. We treat your reputation as an extension of our own.

1. 01

   Authorized user management

   Customers control which team members can access MAR systems and must keep credentials confidential. Audit logs allow administrators to review session activity and revoke access in real time. If you suspect credential compromise, notify us within twelve hours so we can help contain exposure.

2. 02

   Accurate account information

   Shipping addresses, billing contacts, and jurisdictional details must remain current. When changes occur, update them through the admin console or by emailing our support desk. Accurate data keeps tax calculations, compliance notifications, and emergency outreach aligned.

3. 03

   Lawful usage

   You may not use MAR tools to violate applicable laws, infringe intellectual property, or engage in discriminatory practices. If you operate in a regulated industry, you are responsible for configuring MAR to align with sector-specific obligations. We will assist with configuration but cannot assume your statutory responsibilities.

4. 04

   Security collaboration

   Security is a shared responsibility. Customers must maintain endpoint hygiene, enforce multi-factor authentication, and monitor their own integrations. When we publish advisories, apply recommended patches within the documented timeframe to preserve support eligibility.

5. 05

   Feedback partnership

   We welcome candid feedback delivered through structured channels. However, harassment, disrespectful conduct toward MAR staff, or the release of confidential materials is prohibited. Constructive dialogue keeps the partnership healthy.

6. 06

   Resource stewardship

   Avoid automated queries that degrade service for other tenants and respect rate limits we publish. For high-throughput experiments, coordinate in advance so we can scale capacity. Abuse triggers staged responses beginning with warnings and can culminate in temporary suspension.

7. 07

   Integration diligence

   When connecting external systems, ensure that downstream vendors honor privacy and security expectations compatible with MAR commitments. We offer review checklists, but final approval remains with you. Notify us if a downstream vendor experiences a breach touching MAR data.

8. 08

   Compliance cooperation

   If regulators request information about your use of MAR, inform us promptly so we can coordinate responses. Provide reasonable assistance during investigations into misuse or policy breaches. Our goal is to resolve issues collaboratively without disrupting your operations.

9. 09

   Intellectual property respect

   You retain ownership of content you upload, while MAR retains ownership of platform software, models, and branding. Do not reverse engineer, decompile, or create derivative works from MAR code unless expressly permitted. We respect your IP and expect the same in return.

10. 10

    Payment duties

    Pay invoices on time using the methods specified, including wire, ACH, or supported digital payments. If you anticipate delays, engage our finance team early—payment plans are possible when transparency exists. Persistent non-payment may result in service interruption and debt collection.

11. 11

    Incident notification

    Should you discover security incidents or data exposures involving MAR systems, notify us immediately with relevant logs. Shared intelligence allows us to react decisively. Delayed notification can limit remediation options and increase risk for other tenants.

12. 12

    Termination procedures

    When contracts end, download your data before the termination effective date. We will retain backups for thirty days to accommodate late export requests, after which data is securely destroyed. Users must uninstall connectors and confirm deletion on their side as well.

1. 01

   Change management

   MAR uses staged deployment pipelines with automated testing, peer review, and canary releases. We publish changelog entries to keep customers aware of functionality updates. High-risk changes require explicit go/no-go meetings with representation from engineering, security, and product leadership.

2. 02

   Incident transparency

   If an incident affects your service, we will deliver timeline updates through the MAR status page, email alerts, and in-app notifications. Communications include impact, mitigation progress, and next checkpoints. After resolution we distribute a detailed post-incident report.

3. 03

   Data portability tooling

   Exports are available at any time, and we provide schema documentation plus sample scripts. Our support team assists with validation to ensure exported data flows into your destination systems cleanly. If you need an engineer on call during migration, we can arrange it via a professional services statement of work.

4. 04

   Business continuity planning

   Annual business continuity exercises validate that critical operations continue during widespread outages. Exercises cover power loss, cloud provider disruption, natural disasters, and vendor failures. Lessons learned feed into updated playbooks shared with customers under NDA.

5. 05

   Third-party assessments

   Independent auditors evaluate our controls, and we share summary reports along with remediation status. Customers may request bridge letters and control mappings for frameworks like NIST CSF or HITRUST. We welcome customer auditors onsite with reasonable notice.

6. 06

   Confidential information

   Each party agrees to protect confidential information with reasonable care and to use it solely for fulfilling contractual obligations. Confidential materials include technical documentation, roadmaps, security procedures, and non-public product concepts. Disclosure is allowed only when required by law and after providing notice when legally permitted.

7. 07

   Mutual indemnification

   MAR indemnifies customers against third-party claims alleging our technology infringes intellectual property, while customers indemnify MAR against claims arising from their misuse of the platform. Indemnification obligations include defense, settlement, and reimbursement for damages awarded by a court.

8. 08

   Limitation of liability

   Neither party is liable for indirect, special, incidental, or consequential damages, nor for lost profits or revenue. Our aggregate liability is capped at the greater of fees paid in the preceding twelve months or the amount specified in your master agreement. These limitations do not apply to gross negligence, willful misconduct, or breach of confidentiality.

9. 09

   Dispute resolution

   The governing law and venue appear in your order form. Parties will first attempt to resolve disputes through executive escalation meetings before turning to arbitration or litigation. Mediation is available if both parties agree a neutral facilitator could accelerate resolution.

10. 10

    Assignment controls

    You may not assign the agreement without MAR's written consent, except to an affiliate or successor that assumes all obligations. MAR may assign the agreement in connection with a merger, acquisition, or corporate restructuring. We will notify you of any assignment that alters the legal entity responsible for the services.

11. 11

    Government use

    If you are a public sector customer, additional clauses addressing procurement rules, audit rights, and security baselines attach to your agreement. We comply with export control laws and restrict access to sanctioned jurisdictions. Government users receive briefings on how MAR aligns with mission assurance requirements.

12. 12

    Survival of obligations

    Sections relating to confidentiality, payment, intellectual property, warranty disclaimers, indemnification, and limitations of liability survive termination. These clauses ensure obligations continue where necessary to protect both parties. Survival periods align with statutory requirements and practical risk windows.

Making amendments

MAR may update these terms to reflect product enhancements or regulatory change. When updates are material, we send notice at least thirty days in advance, provide a redline, and host Q&A sessions for your legal and operational teams. Continuing to use the services after the effective date signals acceptance of the revised terms.

Questions about these terms can be directed to support@gomarai.com. If you require modifications, our legal team is available to draft tailored amendments that preserve the intent of our partnership.