MyMEXCards
MyMEX CardsMore than a card. A connected business.
Try 7 days free
POPIA & privacy

Your information has a purpose—not a blank cheque.

This notice explains how Motoring Excellence processes information through MyMEX Cards, including self-service signup, subscriptions, tenant workspaces, public cards, CRM conversations, analytics and support.

01

Who is responsible

Motoring Excellence operates MyMEX Cards. For platform account, billing, security and support administration, Motoring Excellence acts as the responsible party. Each tenant is responsible for the staff, customer, lead and content information it chooses to process in its own workspace, while MyMEX provides the secured service and authorised support layer.

02

Information we process

Depending on the feature used, information may include account and identity details, company and industry information, card-holder profiles, credentials in protected form, brand media, public card content, customer enquiries, CRM notes and messages, consent preferences, subscription quantities and provider references, email delivery records, push subscriptions, analytics events, support requests and technical security records.

03

How information reaches us

Information may be supplied directly during signup, onboarding, card creation, support or customer interaction; added by an authorised tenant user; generated when a card or platform feature is used; or returned by a configured service such as PayPal, an email provider or a browser push service. Tenants must have a lawful basis to upload or import personal information.

04

Why we process it

We process information to create and secure accounts, verify email addresses, provision tenants, administer subscriptions, publish digital cards, route enquiries, support customer conversations, measure engagement, deliver requested notifications, prevent misuse, maintain audit records, diagnose problems and provide platform support. We do not sell personal information.

05

Lawful processing and minimisation

Processing is limited to an applicable contract, legitimate service or security purpose, legal obligation, consent or another lawful basis. MyMEX is designed to separate tenant data, restrict roles and collect only what the active workflow needs. A tenant must not use the platform to collect excessive, irrelevant or unlawfully obtained information.

06

Subscriptions and PayPal

PayPal processes payment credentials and recurring payments under its own privacy terms. MyMEX does not store a customer’s full card or PayPal login details. We retain provider references, billing cycle, purchased quantity, subscription status, payment-event status and audit information needed to activate capacity, reconcile webhooks, assist support and meet legal obligations.

07

Public cards and sharing

Information deliberately published on a digital card is publicly accessible through its share link, QR code, installed app or search metadata where enabled. Card holders and tenant administrators must review public fields before publishing. Removing a field or archiving a card limits future access but cannot retract copies that another person lawfully saved or shared earlier. Where lawful and appropriately authorised, MyMEX may use approved public card and campaign examples to showcase its work as explained in Showcasing tenant work in the Platform Terms. Private workspace and customer records are excluded. Unnecessary personal details should be omitted or obscured, and a tenant or affected cardholder may contact MyMEX to request exclusion or removal. This does not limit applicable privacy rights.

08

Artificial intelligence

Jarvis may assist with explanations, drafting, classification and recommendations. Only information necessary for the requested, authorised task should be sent to an AI service. AI output remains reviewable and does not bypass permissions, consent or business rules. Platform credentials stay server-side, and important customer-facing actions require a separate confirmed workflow.

09

Email, WhatsApp and push

Messages and notifications are subject to tenant permissions, available consent or service purpose, suppression and delivery controls. WhatsApp hand-offs may be recorded before the external app opens. Push notifications require an opt-in browser subscription and can be disabled in the browser. Delivery records may be retained for audit, retry and support.

10

Cookies, local storage and analytics

MyMEX uses essential session cookies and limited browser storage for security, authentication, interface preferences, install behaviour and reliable app operation. Workspace and card analytics may record page, action, device and campaign context without requiring unnecessary message content. We do not use the public platform to sell third-party behavioural advertising profiles.

11

Service providers and cross-border processing

MyMEX’s hosting provider is HostAfrica. Contact us through the support form for hosting-region, service-provider and data-processing information relevant to your proposed use.

Authorised hosting, payment, email, AI, mapping, browser and support providers may process limited information needed to perform their service. Where information is processed outside South Africa, Motoring Excellence and the tenant must use appropriate contractual, legal and security safeguards for the circumstances.

12

Retention

Information is kept only for the active service, recovery, security, audit, dispute and legal periods that apply. Retention differs by record type. Account, payment and security logs may outlast a public card; temporary verification tokens expire sooner. When deletion is appropriate, information is removed or de-identified through a controlled process and backups age out according to the backup cycle.

13

Security and tenant isolation

Safeguards include hashed passwords and one-time tokens, CSRF protection, server-side role checks, workspace scoping, protected secrets, prepared database operations, signed webhook verification, audit records and restricted administration. No system can guarantee absolute security, so users must protect credentials and report suspicious access promptly.

14

Your rights

Subject to POPIA and any applicable exceptions, a data subject may ask whether information is held, request access or correction, object to certain processing, withdraw consent where consent is the basis, or request deletion. We may verify identity and coordinate with the responsible tenant before acting. A concern may also be raised with South Africa’s Information Regulator.

15

Security incidents

Suspected unauthorised access is investigated and contained. Where notification is legally required, the responsible party, Information Regulator and affected data subjects will be notified in the manner and timeframe applicable to the incident. Tenants must promptly tell Motoring Excellence about an incident affecting their workspace or credentials.

16

Contact and updates

Privacy and support enquiries may be submitted through the secure support form or emailed to admin@motoringexcellence.com. We may update this notice when the platform, providers or legal requirements change and will publish the new effective date.

Security & Trust

Security & Trust

Protection you can understand.

Layered safeguards help protect your account, payments and information while keeping responsibilities and limitations clear.

Controls reviewed 26 October 2026 · Reviews are ongoing
01

Account access

Login throttling limits repeated password guesses. Session expiry, revocation and active-user checks help stop stale access. Keep credentials private and remove staff access when responsibilities change.

02

Payment safeguards

Payment verification and duplicate-processing safeguards help prevent false payment activation and repeated billing. They do not guarantee protection against every payment dispute or fraud scenario.

03

Encrypted connections

HTTPS protects information travelling between your browser and MyMEX. Check the website address before signing in. HTTPS does not make a fraudulent website trustworthy.

04

Restricted system files

Private configuration and restricted file permissions help reduce unauthorized reading or changes to sensitive application files.

05

Recovery safeguards

Selected production database and application backups were restored and checked in isolation. Deployment rollback was rehearsed. Full restored-service business testing remains outstanding.

06

Ongoing review

Security reviews continue. Provider-level MFA enforcement, server patching, SSH and firewall policies, and immutable/off-site backup assurances have not yet been independently verified in this review.

07

Security is a shared responsibility

No online service eliminates every risk. Protect your credentials, review workspace access and report unexpected account or payment activity promptly. This page describes reviewed controls; it is not an independent certification or a guarantee that every platform route has been audited.

08

Report a security concern

Use our support form to request a private security follow-up. Describe the affected page and what happened. Do not send passwords, API keys, payment details or customer records. For sensitive evidence, ask support for an appropriate private channel first.

Platform terms · Privacy notice

MyMEX Security & Trust · Reviewed controls, clear limitations and ongoing improvement.