Your data.
Protected.

1Who We Are

JMeC Connect is an automotive service coordination, dispatch, connection, communication, payment, and marketplace platform. JMeC helps customers connect with independent mobile mechanics, repair shops, tow providers, roadside providers, skilled repair helpers, specialty providers, and other automotive service partners.

Unless expressly stated in writing, service providers who perform automotive work through JMeC are independent businesses or contractors and are not employees of JMeC Connect.

2Scope of This Policy

This Privacy Policy applies to information processed through:

• JMeC Connect websites and WordPress/Elementor pages
• JMeC customer, provider, affiliate, and administrative portals
• JMeC mobile applications and future PWA/web-app experiences
• Service request, ZIP coverage, intake, quote, scheduling, dispatch, and job-status workflows
• Payment, payout, refund, direct-pay, fee-balance, subscription, and accounting workflows
• Provider onboarding, eligibility, compliance, insurance, license, tax, and background-check workflows
• Refer & Earn and Affiliate Partner programs
• Email, SMS, push notification, in-app messaging, support, and other communication channels
• Photo, video, document, receipt, vehicle, VIN, barcode, and other upload or scan features
• Location, mapping, routing, ETA, arrival, and active-job tracking features
• Analytics, performance monitoring, fraud prevention, error logging, and security systems

3Information We Collect

Depending on how you use JMeC Connect, we may collect:

Contact and account information

• Name, email address, phone number, mailing or service address, ZIP code, city, and service area
• Customer, provider, affiliate, referral, payout, job, and other internal identifiers
• Account, portal, session, authentication, magic-link, and verification information

Vehicle and service information

• Vehicle year, make, model, trim, VIN, license plate, mileage, and decoded vehicle information
• Service category, issue descriptions, urgency, preferred schedule, appointment details, and job status
• Diagnostic information, quote requests, estimates, approvals, more-details submissions, and repair history
• Photos, videos, notes, damage documentation, arrival evidence, completion evidence, and related records

Provider and business information

• Business name, role, service categories, experience, skills, tools, availability, travel/service areas, and pricing information
• Insurance, licenses, registrations, tax forms, W-9 information, contractor agreements, background/compliance information, and eligibility status
• Provider job offers, responses, assignments, scheduling, arrivals, completions, payouts, assistance requests, ratings, and performance information

Payment, payout, and transaction information

• Payment amount, status, payment method metadata, Stripe identifiers, refunds, chargebacks, reversals, receipts, and transaction references
• Provider gross, JMeC fees, processing-fee allocations, provider net payout, payout status, balances, and payout references
• Affiliate/referral reward amounts, commission rates, payout identities, settlement status, and related audit records
• Optional membership/subscription plan, billing status, renewal status, cancellation status, entitlements, and billing history when such plans are offered and elected

Communications and support

• Messages between customers, providers, and JMeC administration
• Email, SMS, push, in-app message, support, dispute, no-show, cancellation, and rescheduling history
• Customer-service interactions and communication preference or opt-out records

Technical, analytics, and security information

• Browser/device type, operating system, viewport, page path, session identifiers, timestamps, and error information
• Referral or affiliate code, UTM campaign values, referring host, click and conversion timestamps, and attribution status
• Security, fraud, abuse, duplicate-account, rate-limit, and diagnostic information

JMeC Connect does not ordinarily store full payment card numbers. Approved payment processors such as Stripe collect and process card details under their own privacy and security practices.

4Canonical Identity and Account Continuity

JMeC may assign persistent internal identifiers to customers, providers, affiliates, referrals, jobs, payments, payouts, and accounts. These identifiers help keep history, jobs, payments, memberships, referrals, and account records connected when a person legitimately changes an email address, phone number, address, vehicle, or other profile information.

JMeC may use normalized email addresses, normalized phone numbers, prior identifiers, account history, and other records to resolve duplicate or legacy records. Where reasonably necessary for audit, fraud prevention, accounting, support, or record integrity, prior identifiers or contact values may be retained as aliases or historical records rather than silently overwritten.

5How We Use Information

We may use information to:

• Check ZIP/service-area coverage and route customer requests
• Create, maintain, and secure customer, provider, affiliate, and administrative accounts
• Match customers with eligible providers based on location, service, availability, status, and other dispatch factors
• Provide quotes, approvals, scheduling, arrival, in-progress, completion, cancellation, no-show, and rescheduling workflows
• Release customer/provider contact and location data only when required platform conditions are met
• Process payments, fees, refunds, provider payouts, referral rewards, affiliate commissions, balances, and future subscription charges
• Maintain service history, payout ledgers, commission ledgers, audit trails, and accounting records
• Operate Refer & Earn and Affiliate Partner programs
• Operate optional future memberships, benefits, entitlements, and recurring billing when a user elects a plan
• Send service, dispatch, quote, appointment, payment, security, support, and other authorized communications
• Verify provider eligibility, insurance, tax, licensing, agreements, and other compliance requirements
• Detect duplicate records, prevent fraud, investigate abuse, secure the platform, and resolve disputes
• Analyze platform performance, conversion, page engagement, dispatch performance, and operational reliability
• Comply with legal, tax, accounting, insurance, regulatory, and business-record obligations

6Location, Mapping, Dispatch, and Active-Job Tracking

JMeC may process ZIP code, service address, approximate or precise device location, provider service area, route, ETA, arrival, and other location data when a user permits or uses a location-enabled feature.

Location data may be used for coverage checks, provider matching, routing, arrival verification, active-job status, safety, customer visibility, and service documentation. Precise location and direct contact information may remain locked until assignment, payment, job status, or other release conditions are satisfied.

JMeC does not intend active-job location tracking to operate as unrelated, continuous surveillance. Location features should stop, reduce, or change after the applicable service workflow ends, subject to reasonable retention of job, route, timestamp, or audit records.

7Payments, Direct Pay, Payouts, and Financial Records

JMeC Connect may use Stripe and other approved processors to handle service payments, dispatch and connection fees, partner-assistance fees, provider payouts, referral rewards, affiliate payouts, refunds, chargebacks, and future subscription billing.

Payment processors may receive contact information, transaction amounts, customer/provider identifiers, payout identity information, and other data needed to process payments or payouts.

If JMeC provides an option to pay a provider directly, JMeC may record the user's acknowledgement of the direct-pay disclosure, including the applicable notice version and acknowledgement timestamp. Direct payment to a provider may result in JMeC having less direct payment evidence than when payment is processed through JMeC, and applicable JMeC fees or balances may remain due.

JMeC may retain payment, refund, chargeback, fee, payout, settlement, commission, and ledger records as reasonably necessary for accounting, tax, fraud prevention, dispute resolution, and legal compliance.

8Optional Memberships and Subscriptions

JMeC may offer optional customer or provider memberships, subscriptions, or paid plans in the future. This Privacy Policy is designed to support those services without implying that a membership currently exists for every user.

If a user elects a paid plan, JMeC may process plan selection, subscription ID, billing interval, price, payment status, renewal date, cancellation status, benefit entitlement, credits or discounts, failed-payment status, and related support history.

Subscription payment information may be processed by Stripe or another approved payment processor. JMeC may use subscription status to apply plan benefits, discounts, priority features, provider tools, or other entitlements described when the membership is offered.

9Independent Providers, Eligibility, and Compliance Data

JMeC may collect and process provider information to determine whether a provider is eligible to receive jobs, accept assignments, receive payouts, use particular features, or remain active on the platform.

Provider compliance information may include:

• Identity and contact information
• Business name and organization information
• W-9/tax information and payout identity
• Insurance coverage and expiration dates
• Licenses, certifications, background/compliance documents, and eligibility status
• Required agreements, acknowledgements, training, or policy acceptance
• Uploaded documentation and verification/review status

JMeC may use third-party providers, including payment, identity, background, compliance, or document-processing vendors, where reasonably necessary to support onboarding or eligibility.

10Refer & Earn Information

JMeC may collect referral information from public referral forms, provider dashboards, claim links, or other approved referral tools. Referral information may include the referrer's contact information, the referred person's contact information, referral type, source, attribution, qualification, reward status, claim status, payout identity, and payout reference.

Permission to submit another person's information

A person submitting a referral should provide another person's information only when they have permission to share that information with JMeC for the referral. Referral submission does not authorize the referrer to provide SMS or marketing consent on behalf of the referred person.

JMeC may use referral information to determine whether the referred party is new, prevent duplicate or fraudulent referrals, connect the referral to customer or provider records, determine whether qualification conditions were met, administer rewards, create payout claims, and maintain audit/accounting records.

11Affiliate Partner Program and Attribution

JMeC's Affiliate Partner Program may process affiliate applications, approval status, Affiliate ID, public affiliate code, tracking links, click events, conversion events, commission events, payout identity, payout records, suspension or reinstatement status, and administrative audit history.

Affiliate tracking information

Affiliate tracking may include:

• Affiliate code or Affiliate ID
• Opaque session or click identifiers
• Landing-page path and timestamp
• UTM source, medium, campaign, term, and content values
• Referring host only, not the full referring URL for affiliate analytics
• Device category and viewport information
• Conversion, qualification, commission, and payout events

Affiliate codes are used for attribution and are not authentication credentials. A click does not by itself create commission ownership. JMeC may apply first-valid attribution, new-user, anti-self-referral, duplicate, fraud, and qualification rules when determining affiliate commissions.

JMeC may use a limited-duration first-party cookie or similar local storage to remember an affiliate code or click timestamp so attribution can operate across the applicable tracking window. We do not need to derive affiliate identifiers from a user's email address, phone number, IP address, or browser fingerprint.

The Affiliate Partner Program is also governed by the JMeC Affiliate Partner Agreement .

12SMS, Email, Push, and Other Communications

JMeC may send service-related email, push, in-app, and account communications necessary to operate requested services, accounts, payments, payouts, security, provider workflows, referrals, affiliate applications, and support.

Customer transactional SMS

JMeC Connect sends recurring transactional text messages under the customer service-request SMS program only to individuals who voluntarily provide a mobile phone number and expressly opt in through the applicable JMeC Connect SMS consent process, including the public service request page at https://www.jmecconnect.com/request-service/ .

SMS consent is separate from acceptance of this Privacy Policy, Terms of Service, account registration, affiliate application, referral submission, or purchase. A checkbox used for SMS consent is not preselected.

Marketing or promotional SMS, if offered, requires separate consent where required. JMeC does not treat referral submission, affiliate application, or general account registration as permission to send marketing texts.

13Cookies, Analytics, Performance, and Tracking

JMeC may use cookies, local storage, session storage, analytics, tracking links, performance monitoring, error logging, and similar technologies to operate the platform, maintain sessions, remember referral/affiliate attribution, understand traffic, measure conversions, improve user experience, diagnose errors, and secure JMeC services.

Affiliate and application analytics

Affiliate landing and application analytics may record page views, section views, scroll depth, CTA clicks, active engagement, form start, field completion status, validation errors, submit events, application result status, and form abandonment. Application analytics should record the field name or validation state only, not the applicant's typed name, email, phone number, or free-text response.

Referrer information used for affiliate analytics should be reduced to the referring host rather than storing a full referrer URL that could contain personal information or session parameters.

Consent and regional controls

Where applicable law requires consent for non-essential analytics or advertising technologies, JMeC may provide a consent choice and limit those technologies until consent is obtained. Strictly necessary technologies used for authentication, security, fraud prevention, payment, or requested referral/affiliate attribution may be treated differently where permitted by law.

14Photos, Videos, Documents, VIN, Scans, and Uploads

JMeC may allow users to upload or capture photos, videos, repair evidence, inspection images, arrival/completion documentation, receipts, provider compliance documents, licenses, insurance documents, VIN images, barcodes, or other materials.

Uploaded content may be stored in JMeC-connected storage systems and made available to authorized customers, providers, administrators, payment/compliance processors, or support personnel as reasonably necessary for the related service, eligibility review, dispute, payment, or audit purpose.

Users should not upload unrelated highly sensitive information. JMeC may retain service evidence, compliance records, and audit documentation where reasonably necessary for safety, disputes, fraud prevention, insurance, tax, legal, or business-record purposes.

15How We Share Information

JMeC may share information only as reasonably necessary with:

• Independent providers evaluating, accepting, scheduling, or performing a service request
• Payment and payout processors such as Stripe
• Telecommunications carriers, messaging aggregators, email, push, or notification providers
• Cloud hosting, database, storage, mapping, routing, analytics, security, and automation providers
• Background, identity, compliance, insurance, licensing, or document-review vendors where applicable
• Accounting, tax, legal, insurance, and professional advisers
• Government authorities or other parties where disclosure is legally required or reasonably necessary to protect rights, safety, security, or prevent fraud
• Business service providers operating under appropriate contractual or confidentiality obligations

Customer/provider contact and precise service-location information may be withheld from other marketplace participants until applicable platform release conditions are satisfied.

16Data Security

JMeC uses reasonable administrative, technical, and organizational safeguards designed to protect information. These may include access controls, tokenized or limited-access portal links, restricted data release, logging, fraud detection, provider/admin authorization checks, payment-processor controls, and other security measures appropriate to the system.

No website, mobile application, email system, API, cloud platform, payment system, or transmission method can guarantee absolute security. Users should protect account links, verification codes, devices, and credentials and should not forward private portal or payout links to unauthorized persons.

17Data Retention

JMeC retains information for periods reasonably necessary for service delivery, account and job history, settlement, accounting, tax reporting, compliance, provider eligibility, insurance, fraud prevention, safety, dispute resolution, legal obligations, analytics, and audit integrity.

Retention periods may differ by data category. For example, active-job location may require shorter operational use than payment, tax, compliance, payout, referral, affiliate, service-history, or dispute records. JMeC may retain a limited historical record after account closure where reasonably necessary for legal, accounting, fraud, or audit purposes.

18Data Accuracy

Users are responsible for providing accurate information. Incorrect phone numbers, email addresses, ZIP codes, addresses, vehicle information, service details, payment information, provider documents, or payout information may delay or prevent service, payment, communication, qualification, activation, or support.

19Children's Privacy

JMeC Connect is not directed to children under 13, and we do not knowingly collect personal information from children under 13. A parent or legal guardian who believes a child submitted information without authorization should contact JMeC.

20Your Choices and Privacy Requests

Depending on applicable law and your relationship with JMeC, you may request access to, correction of, or deletion of certain personal information, subject to legal, accounting, fraud-prevention, security, dispute, tax, compliance, and record-integrity exceptions.

Users may update available account information, manage certain communication preferences, unsubscribe from email where provided, or reply STOP to SMS messages.

Some information cannot be immediately deleted if JMeC must retain it for payment, payout, tax, fraud, dispute, safety, provider compliance, legal, or audit purposes.

21Policy Updates and Versioning

JMeC may update this Privacy Policy from time to time. The current version and effective date will be posted on this page.

Where a workflow records a Privacy Policy version—such as an affiliate application, membership enrollment, provider agreement, or other affirmative acceptance—JMeC may retain the version identifier and acceptance timestamp associated with that action.

A later materially changed policy will not be represented as though a user accepted it on an earlier date. Where required, JMeC may request acknowledgement or consent to a new version.

22Contact Us

For privacy, communication, account, or data-related questions, contact JMeC Connect: