Terms for merchant workspaces.

1. Service and agreement

By creating or using a merchant workspace, the organization identified during signup or in an order form (the Merchant) agrees to these Terms. The person accepting them represents that they are authorized to bind the Merchant. MyCover.me is a software platform; it is not the manufacturer, seller, coverage issuer, insurer, repair provider, or legal decision-maker unless a separate signed agreement expressly says otherwise.

The service may include product and order imports, Product Instances, Coverage Entitlements, ownership claiming, support cases, warranty claims, messaging, evidence, eligibility explanations, repair or replacement tracking, audit history, analytics, and merchant-authorized integrations. Preview, beta, planned, or authorization-dependent capabilities are not production commitments.

2. Accounts, workspaces, and access

• Merchant must provide accurate account and organization information, protect credentials, configure appropriate roles, and promptly remove access for people who no longer need it.
• Each workspace is tenant-scoped. Merchant may access only its own customer relationships, products, coverage, support, and service records.
• Merchant is responsible for actions taken by its authorized users and for reviewing audit history, integration health, and security notices.
• MyCover.me may suspend credentials, sessions, integrations, or high-risk actions to protect the service, consumers, or other tenants.

3. Product, coverage, and ownership records

Coverage Entitlement, product registration, ownership, Support Case, and Warranty Claim are separate records. Merchant must not configure a workflow that restarts or removes a buyer’s legitimate coverage merely because the buyer scans late, does not create a MyCover.me account, or uses a recovery path, unless the Merchant’s actual policy lawfully requires registration.

Merchant is solely responsible for the accuracy, legality, publication, versioning, and fulfillment of its warranty or support promises. Merchant must identify the real coverage issuer and may not instruct MyCover.me to label unverified information as issuer verified. Manual corrections, assisted linking, eligibility decisions, refunds, replacements, and other material actions must be truthful and auditable.

3A. QR credentials and disputed ownership

An order-bound QR or code is a private bearer credential associated with a specific sold unit, order item, or permitted serial reference. Merchant may review an issued credential and its tenant-scoped activity without consuming the buyer’s one successful ownership claim. Merchant must not publish credentials on public packaging, listings, product photography, or other channels where an unrelated person could claim them.

When a credential was used, copied, expired, or claimed by the wrong person, Merchant must offer a reasonable verification path. Verification may use the order number, account email, buyer name, shipping-address match, serial, receipt, or other proportionate evidence. Merchant may use these details only to verify ownership, administer coverage, prevent fraud, and provide product support; it must not use claim-recovery evidence for unrelated marketing, profiling, or resale.

4. Commerce and third-party integrations

Merchant authorizes MyCover.me to access connected services only within the scopes approved by the Merchant. Shopify requires verified setup; Amazon functionality depends on SP-API approval and seller authorization; CSV or JSON imports use only the files Merchant provides. Availability may change when a provider changes its API, permissions, policies, or service.

Merchant must have all rights, notices, and lawful bases needed to provide customer, order, product, serial, receipt, and support data. Merchant will not upload data it is prohibited from using or ask MyCover.me to circumvent provider restrictions.

5. Merchant responsibilities

• Honor applicable consumer, warranty, returns, accessibility, privacy, marketing, product-safety, and recordkeeping laws.
• Give buyers accurate policy terms, support identity, required notices, and a meaningful path to request help, including after coverage expires where support options exist.
• Review evidence and high-impact decisions. Do not use the service to discriminate, retaliate, deceive, or automatically reject lawful rights.
• Use attachments, serials, IMEIs, contact details, and fraud signals only for legitimate, authorized support and security purposes.
• Limit QR scan activity, claimant identity, order matches, address checks, and receipt evidence to authorized staff who need them for ownership verification and post-purchase service.
• Keep public replies separate from internal notes and ensure buyer-visible content is appropriate.

6. AI and deterministic decisions

AI features may summarize, classify, extract, troubleshoot, draft, or recommend. Outputs can be incomplete or wrong and must be reviewed. AI does not set warranty dates or policy rules and may not autonomously deny warranty rights, issue refunds, approve high-value replacements, change coverage terms, or make another legally significant decision. Deterministic policy evaluations remain explainable and authorized people remain responsible for final decisions.

7. Plans, usage, and payment

Current plan entitlements, case allowances, seats, stores, integrations, and optional features are shown on the Pricing page or an order form. Paid subscriptions renew for the selected period until canceled. Taxes, payment timing, overages, credits, refunds, and price protection will be stated at checkout or in the order form. Reaching a case allowance will not silently discard a buyer request; MyCover.me may preserve it while placing the workspace in a grace, over-limit, or upgrade state.

8. Data protection and confidentiality

For merchant-directed buyer warranty and support workflows, Merchant generally acts as controller or business and MyCover.me as processor or service provider. The parties will enter a Data Processing Addendum where required. MyCover.me may separately act as controller for merchant account administration, security, abuse prevention, billing, service operations, and its direct consumer product wallet. Each party will protect confidential information and use it only to perform the agreement, exercise rights, or meet legal obligations.

9. Acceptable use

Merchant may not probe or bypass security, access another tenant, scrape the service, upload malicious code, send unlawful or deceptive communications, expose secrets, submit content without rights, reverse engineer except where law prevents restriction, resell access without permission, or use MyCover.me to facilitate unsafe products, fraud, harassment, or unlawful surveillance.

10. Intellectual property and feedback

MyCover.me and its licensors retain rights in the platform, software, design, documentation, and brand. Merchant retains rights in its data, policies, content, and trademarks and grants MyCover.me the limited rights needed to host, process, secure, display, and transmit them for the service. Feedback may be used without restriction or attribution, but MyCover.me will not identify Merchant publicly without permission.

11. Availability, warranties, and liability

The service is provided using commercially reasonable care, but uninterrupted or error-free operation is not guaranteed. Third-party services and beta features may fail or change. To the maximum extent permitted by law, implied warranties are disclaimed. Neither party is liable for indirect, incidental, special, punitive, or consequential damages, or lost profits, revenues, goodwill, or data, except where such exclusion is unlawful. The final production agreement must state a negotiated liability cap and legally required carve-outs.

12. Suspension, termination, and export

Merchant may stop using the service and cancel as provided in its plan or order form. MyCover.me may suspend or terminate for material breach, security risk, unlawful use, nonpayment, or provider restrictions, using notice and a cure opportunity when appropriate. Subject to law, security, other people’s rights, and payment status, Merchant may request an export of its tenant-scoped data. Audit, security, billing, legal-hold, and consumer-rights records may be retained where required.

13. Changes and general terms

Material changes will be announced through the service or account email and will identify a new effective date. An order form controls over conflicting online terms, followed by any DPA and these Terms. Neither party may assign the agreement except with consent or in connection with a merger, reorganization, or sale of substantially all relevant assets, subject to applicable law. The final governing law, forum, notices address, and contracting legal entity must be inserted before general availability.