SSF Media Manager Pro Terms

1. Supplier and contact

Murshid Farm Industries, Pakistan, supplies SSF Media Manager Pro under its Smart Solutions Framework (SSF) software brand. Owner/proprietor: Muhammad Sajid Minhas. Business address: Murshid Farm Industries, 9 Km Sheikhupura Road, Opposite Millat Tractor, Lahore 54600, Pakistan. Product, account and support email: sales@mfipk.com. SSF is not a separately incorporated LLC.

2. Price, site entitlement and payment

Choose a single-payment plan: USD 39 for 1 active WordPress installation, USD 99 for 5, or USD 199 for 20. Every plan includes the same Pro features and one year of update/support eligibility. There is no subscription, automatic renewal or recurring debit authorisation. Checkout shows applicable tax and the final total before payment. A further purchase requires a separate deliberate checkout agreement.

The one-year update/support term starts when the order and licence are created, before first site activation. Delaying activation does not extend the term. The exact recorded end date appears in the plugin licence settings. A renewal is optional and extends update/support eligibility under the separately agreed renewal purchase.

3. Included Pro tools

SSF Media Manager Pro 0.2.0 requires the separate free SSF Media Manager 0.1.2 or later. Pro tools are for administrators and remain subject to the licence checks below. These are bounded tools, not a claim about the total capacity or performance of your media library.

• Saved media views: create, open and delete up to 20 saved search, collection and supported media-type filter combinations per administrator and site.
• Classic CSV memberships: the existing tool exports up to 500 matching files and 500 membership rows and imports up to 500 data rows / 256 KiB of UTF-8 CSV. It previews explicit add/remove operations for exact current-site attachment IDs, current original attachment URLs and existing collection slugs. Preview access expires after ten minutes; apply rechecks and consumes the preview. This tool does not create collections, migrate sites or change media files or attachment metadata.
• Bulk attachment metadata: preview up to 50 attachments and deliberately select titles, captions, descriptions and image alt text to change. Common values require explicit selection; alt text applies only to images. Selected values are plain text with HTML stripped, up to 10,000 UTF-8 bytes per field, within the 2 MiB history budget. A blank-information report displays up to 50 matching attachments per page while scanning at most 100 IDs per request. Empty fields may be intentional. Editing attachment metadata does not rewrite text or alt/caption values already stored separately in page blocks.
• Virtual collection nesting: review and apply parent relationships for existing collections through drag-and-drop or an accessible selection form. The nesting screen supports up to 1,000 collections. This changes virtual collection relationships, not physical folders or media memberships. Opening a collection still shows its direct members; child collections are not automatically included.
• Guarded change history: bulk metadata, collection-parent changes and each larger CSV import batch record before/after states for guarded undo. Each entry supports at most 100 entity states and 2 MiB of history data. Later conflicting edits are not overwritten. The classic CSV tool is outside this new change history, and filename copies have their own separate history. Recovery is a guarded attempt, not a substitute for a backup.
• Exact duplicate review: compare local original uploads by complete SHA-256 hash and byte size, not by visual similarity. Each scan supports up to 5,000 matching attachments, 20 MiB per original file and at most 20 items / 32 MiB of eligible original files per explicit step, with processing time limits. Missing, linked, remote, out-of-uploads or oversized files are skipped and reported; generated sizes are not compared. No duplicates are automatically deleted, merged or moved. Reports are time-stamped observations and may be incomplete when items are skipped or files change.
• Larger CSV jobs: validate the whole import before the first write, up to 5,000 data rows / 2 MiB of UTF-8 CSV, then explicitly continue steps of at most 100 data rows. Rechecked current-site IDs, current original URLs and existing collection slugs are required. Progress/error reports identify confirmed, unprocessed and unconfirmed batches. Cancellation retains earlier completed batches; guarded history undo is separate. The whole job is not an atomic transaction. Larger exports use administrator-selected ceilings of up to 5,000 matching files and 5,000 membership rows, process at most 100 files per step and offer the membership CSV only when complete without truncation. Export values are read as each step runs, rather than one atomic library snapshot. No background worker is included.
• Local filename copies: preview a filename-stem pattern using {name}, {id} and {n}, for up to 20 attachments, 200 related files and 256 MiB of additional copies per operation. Only ordinary local uploads are supported, without offloaded/filtered paths or URLs, symlinks or junctions. The tool checks paths, hashes and case-insensitive collisions, exclusively creates verified renamed copies of the main file, referenced generated sizes, original image and backup sizes, then repoints attachment file metadata. It never overwrites or deletes an existing file. Every old file remains so old URLs retain copies; GUIDs and page/post content are not rewritten. This permanently increases disk usage. Filename Undo restores file metadata only and retains new copies too, so new links keep their copies. Later record/file changes can block undo or recovery.

Previews and imports are administrator/site-bound and rechecked before changes. Unmentioned memberships remain intact. Failed operations attempt guarded metadata or membership recovery and expose unresolved states for review. No universal atomicity, complete backup or guaranteed recovery is supplied.

4. After the year and online licensing

The update/support end date alone does not switch off the Pro tools on each previously trusted activated installation. Its saved views, existing memberships and media remain stored. Renewal is optional for continued use on each recognised installation.

Pro still requires the same recognised licence, site binding and service instance. A successful check is cached for up to one hour. When a check is due or explicitly requested, a network or licence-validation failure blocks Pro tools until a successful manual Check licence retry. No offline grace period is implemented. Invalid, disabled, revoked, refunded or wrong-product activation proof does not qualify. These conditions are separate from reaching the date alone. The free plugin remains separate and available.

5. Site replacement and activation after expiry

Activate no more than the chosen plan’s 1, 5 or 20 separate WordPress installations at a time. Each installation uses one activation. During the eligible term, deactivate an installation before replacing it when its slot is needed. After the update/support term ends, a new-site activation or site transfer requires a current key from a deliberately purchased renewal. Continued use on each already recognised installation does not require renewal.

If the old installation cannot be reached, contact support for review of its activation slot. Staging/development installations consume a slot when activated. Network-wide multisite activation is not supported.

6. Updates and delivery

No in-plugin automatic updater, automatic update portal, release schedule or future-feature roadmap is included. The original purchased ZIP remains available through its purchase record. The plugin does not automatically expire that hosted download after a year.

During the eligible term, request any released maintenance package through sales@mfipk.com with the purchase reference. We check the order/entitlement and supply a versioned package manually. We retain the original purchase version rather than replacing its variant files with future restricted updates for all previous buyers.

7. Refunds

Request a full refund of the first purchase within 14 calendar days of purchase by emailing sales@mfipk.com with the order number and purchase email; no explanation is required. Approved refunds are processed through Lemon Squeezy. Requests after 14 days and renewal purchases are reviewed for a material defect, duplicate charge or applicable mandatory rights.

This policy does not promise immediate payment-provider posting, reduce mandatory consumer rights or remove Lemon Squeezy refund discretion.

8. Support

During the eligible one-year term, email support at sales@mfipk.com covers installation, activation and reproducible defects in the supplied add-on. Our initial response target: within two business days, Monday–Friday. This is a target, not an SLA or a guaranteed resolution time.

Support excludes custom development, site administration, hosting/server maintenance, migration and unsupported third-party integrations. Include the product/version, WordPress/PHP details, a clear issue description and purchase reference. Do not send passwords, OTPs, private keys, recovery codes or full payment-card details.

9. Licensing data and local storage

After an administrator explicitly consents, licence activation sends the customer key and a hashed site label to https://api.lemonsqueezy.com/v1/licenses/. Validation/deactivation send the key and saved instance identifier. The label derives from the site URL and WordPress site identifier; hashing does not promise anonymity. The receiving service also sees ordinary network request information.

The plugin stores the key, instance, consent, site/configuration binding, licence/order/variant identifiers, status, check timestamps and entitlement end date in the site database without WordPress option autoloading. The key is not displayed back in settings. No application-level encryption is claimed; site administrators and database backups must protect it. These licence requests do not send media contents, attachment metadata or membership CSV files to Lemon Squeezy.

Before requesting a new activation, the plugin stores a pending activation record in the site database without autoloading. It includes the key, consent, hashed site/configuration binding used for the site label, variant/order/licence identifiers, entitlement end and creation time; a returned instance identifier is retained when available. An uncertain service outcome blocks another activation request to avoid consuming another plan slot. Pending records remain until safely resolved. Guarded recovery validates the known instance, or the matching instance identified through merchant/support review, against the key, product, site label and instance before requesting release. It never allocates a new slot. The service API does not list activation attempts. If no matching instance can be identified, merchant-side confirmation and controlled local repair through support are needed before retrying; there is no blind reset. For support, provide the purchase reference and displayed site label, never licence keys, passwords, OTPs or private recovery codes.

Tool data is processed and stored on the customer site. Saved views remain per administrator/site. Collection-parent relationships remain in the site database. Previews contain the selected records, proposed values and current-state checks. Classic CSV, bulk metadata, collection-parent and filename preview access expires after ten minutes. Larger CSV job previews/progress reports and exact-duplicate scan access expire after one hour. Expired data may remain in the database or backups until cleanup; expiry is not a promise of physical deletion at that instant.

Change history retains the last 50 finished metadata/collection entries site-wide, while filename-copy history retains the last 20 finished receipts site-wide. Unresolved/pending recovery records are not automatically pruned. Stored records may include attachment IDs, original/proposed URLs and local paths, titles, captions, descriptions, image alt text, collection states, hashes, byte sizes, account/site bindings and before/after recovery states. File contents are not sent to Lemon Squeezy by these tools. Filename operations also retain old and newly copied files on local disk; neither ordinary deactivation nor filename Undo deletes those copies.

Only the owning administrator can undo a receipt. If an unfinished record’s owner no longer has administrator access, another administrator may attempt guarded recovery, with the recovering account recorded. Site administrators and database/file backups must protect this stored data. Licence deactivation releases its remote instance and removes local licence state after verified release; ordinary plugin deactivation does not erase saved views, collection relationships, retained history/recovery records, stored media or licence state.

Lemon Squeezy provides checkout, payment, order and download services under its Buyer Terms and privacy policy. We receive necessary order/entitlement information for fulfilment, updates, refunds and support. Support correspondence contains information you choose to send and purchase references. Contact sales@mfipk.com for applicable information requests. Necessary records follow the published Privacy Policy; no fixed deletion deadline or local-only processing guarantee is promised.

10. GPL code rights and commercial services

The supplied code is GPLv2-or-later. The included GPL governs copying, modification and redistribution. For these WordPress packages, those rights prevail over inconsistent generic website restrictions on copying, resale, sublicensing, modification, reverse engineering or transfer. Copyright stays with the relevant rights holders; GPL permission does not transfer ownership.

The chosen plan’s site-count/year commercial offer concerns supplied activation and update/support services. It does not replace the GPL, make GPL rights expire after a year or require deletion of received code. Protect private account credentials and purchased service keys; receiving GPL code does not grant access to another customer account or private merchant systems.

11. Compatibility and operating limits

Plugin headers declare WordPress 6.4 or later and PHP 8.1 or later. Before the site-count plan change, the local functional suite passed 189 assertions in each of three environments: WordPress 7.1.2 / PHP 8.3.35, WordPress 6.4 / PHP 8.3.35, and WordPress 6.4 / PHP 8.1.34, all using MariaDB 11.8.9 through native mysqli. For the final changed build, 135 metadata/tier assertions and 136 remaining feature/integration assertions passed across two fresh local WordPress 7.1.2 / PHP 8.3.35 runs (271 total). The affected metadata, integration and tier suite also passed 166 assertions on WordPress 6.4 / PHP 8.1.34. All final runs used MariaDB 11.8.9 through native mysqli and synthetic licence-service responses, with no external service calls. The earlier 189-pass matrices remain historical pre-tier evidence. Oracle MySQL, other runtime combinations, network-wide multisite and large-library performance remain outside the established release-verification scope.

Automatic update delivery, cloud/offloaded-storage integration, physical-folder management, compression and media-file deletion are not supplied. The filename tool creates local renamed copies and repoints attachment file metadata while retaining both old and new URL copies; it does not rewrite GUIDs or existing page/post content. Old and new copies are not automatically cleaned up and require additional disk space. Other metadata/collection tools do not move or rename media files. Keep appropriate database and file backups and use a staging copy before bulk changes or filename operations. No universal host/theme/plugin compatibility, uptime or recovery guarantee is included.

12. Checkout, policy precedence and mandatory rights

Lemon Squeezy provides merchant-of-record/reseller checkout and related transaction services under its Buyer Terms. Murshid Farm Industries supplies the software and these product services. These product-specific terms apply to SSF Media Manager Pro and take precedence over inconsistent generic software restrictions for these GPL WordPress packages.

Nothing here excludes rights that applicable law does not allow to be excluded. The product-specific GPL section prevails over conflicting generic restrictions for these plugin packages. VisaFile and other SSF products retain their own separate scope and disclaimers.