Matt Steady

Share a link once, then change where it points — without resending anything.
Swirv is a personal link manager for WordPress. Every link lives on your own domain (such as <code>yoursite.com/swirv/download</code>), and its destination is yours to change at any time. Send a link to 200 people today, swap its target tomorrow, and all 200 land in the new place — no third-party shortener, no resending, and never that “sorry, use this link instead” message.
<h4>Passes: a private link for every recipient</h4>
A Pass is a personalised version of a link — its own unguessable URL and a reference label (a supporter, a customer, a newsletter). Issue everyone their own Pass and they all inherit the parent link’s target. Change the link once and every Pass follows. Emailed a track download to your supporters, then need to make a tweak? Edit the target once, and every one of them now gets the fix.
<h4>What you can do</h4>
<ul>
<li>Redirect links on your own domain, e.g. <code>yoursite.com/swirv/download</code></li>
<li>Re-point any link after it has been shared — no dead links, no resending</li>
<li>Issue personalised Passes under any link, each with its own private URL</li>
<li>Group links into Campaigns, with optional public campaign pages</li>
<li>Track clicks with daily analytics charts — privacy-first, no visitor IPs stored</li>
<li>Generate QR codes for any link or campaign</li>
<li>Run Health Scans to catch dead, redirecting, or slow target URLs</li>
<li>Import and export everything as JSON/ZIP for backups and migrations</li>
<li>Optional prefixless links (<code>yoursite.com/download</code>), with clash-checking against existing pages</li>
</ul>
A companion plugin, Swirv Pro, adds advanced Pass controls — access limits, expiry, self-destruct — and more, for larger libraries and tighter workflows.
<h4>Privacy-first by design</h4>
Swirv keeps your link and click data on your own site. It never stores visitor IP addresses — a click records only a 2-letter country code — and Swirv URLs are served <code>noindex, nofollow</code> with a <code>no-referrer</code> policy. Detailed click tracking is optional and can be switched off entirely under Swirv → Settings → Data. Full disclosure of the minimal, opt-in external services Swirv can use is in the External services section below.
<h3>External services</h3>
Swirv stores a 2-letter ISO country code per click, for visitor-country analytics. It derives that code from Cloudflare’s <code>CF-IPCountry</code> request header when present, or otherwise by looking the visitor’s IP up against a local MaxMind GeoLite2-Country database if one has been installed. The raw IP is read only to derive the country code and is never written to the database in any form, hashed or otherwise. With neither source available, the country code is stored empty.
<h4>Requests to your target URLs</h4>
Swirv makes server-side HTTP requests to the target URLs you have added, in three situations: (1) when you save a Link, Swirv sends a HEAD request to learn the target’s MIME type, used to drive per-link image-target download behaviour; (2) Health scans send HEAD requests when you run them; (3) when a visitor clicks an image-typed Link that has the force-download behaviour active, Swirv fetches the image body server-side and streams it back to the visitor. In all three cases the destination server receives a request from your WordPress site. The save-time HEAD probe sends a User-Agent of <code>Swirv Target Probe/{version} (+{your_site_url}; content-type sniffer)</code>; the Health-scan and inline-download paths use the default WordPress HTTP API User-Agent. No visitor data, click data, or WordPress account information is sent in the body of these requests.
<h4>Cloudflare</h4>
Swirv reads Cloudflare’s HTTP_CF_IPCOUNTRY request header when your site is fronted by Cloudflare. Swirv does not send any data to Cloudflare; the header is set by Cloudflare’s edge on incoming requests as part of your site’s existing Cloudflare relationship. The only data Swirv extracts is the 2-letter ISO country code, used for visitor-country analytics on this install. If your site is not on Cloudflare, this code path is inert.
Service: Cloudflare (https://www.cloudflare.com) 
Terms of service: https://www.cloudflare.com/terms/ 
Privacy policy: https://www.cloudflare.com/privacypolicy/
<h4>MaxMind GeoLite2</h4>
Swirv can connect to MaxMind, Inc. to download the GeoLite2-Country database, used to map visitor IP addresses to a 2-letter country code for analytics. The database is stored locally on your server under <code>wp-content/uploads/swirv/geoip/</code> and every country lookup happens on your server against that local copy; Swirv never sends visitor IP addresses to MaxMind.
Swirv contacts MaxMind only after a site administrator has added their own MaxMind licence key under Swirv → Settings → Analytics → Geography and either (a) clicked the Download / update database now button, or (b) the monthly refresh cron has fired since the key was saved. Without a saved licence key, the cron fires but takes no action and Swirv makes no outbound request to MaxMind.
The licence key you enter is stored on your own server in the WordPress options table (as the <code>swirv_maxmind_license_key</code> option), in the same plain-text form WordPress core uses for other site credentials and API keys; Swirv applies no separate encryption to it. It is never transmitted anywhere except to MaxMind as the <code>license_key</code> parameter of the download request described below. Anyone with read access to your WordPress database (including other plugins running on the site) can read it, so treat your MaxMind key like any other site secret. You can clear it at any time by emptying the field and saving.
When downloading the database, Swirv issues a single HTTPS GET request to <code>https://download.maxmind.com/app/geoip_download</code> with three query-string parameters: <code>edition_id=GeoLite2-Country</code>, <code>license_key={your key}</code>, and <code>suffix=tar.gz</code>. The request uses the default WordPress HTTP API User-Agent (which includes your site URL, per WordPress core). No visitor data, click data, or WordPress account information is sent by Swirv as part of this download request.
Service: MaxMind GeoLite country database (https://www.maxmind.com) 
Terms of use: https://www.maxmind.com/en/terms-of-use 
Privacy policy: https://www.maxmind.com/en/privacy-policy 
GeoLite end-user licence agreement: https://www.maxmind.com/en/geolite/eula
<h4>swirv.org</h4>
Swirv links the admin to swirv.org (the Swirv project’s marketing and documentation site, operated by Matt Steady) in three places:
<ul>
<li>The About ↗ submenu item under Swirv in the WordPress admin sidebar opens https://swirv.org in a new tab. This is the Swirv project’s home page — project information, contact details, and links to documentation.</li>
<li>The Swirv Pro ↗ submenu item — visible only when the Swirv Pro companion plugin is not active — opens https://swirv.org/swirvfree/upgrade.html in a new tab. This is the page describing the Swirv Pro companion plugin.</li>
<li>The ★ Swirv Pro badges next to Pro-only features in the admin (the Settings → Analytics tab, the Passes and Analytics admin pages, and the Health Scan page) also open https://swirv.org/swirvfree/upgrade.html in a new tab.</li>
</ul>
These are user-initiated browser links, not server-side calls. Swirv does not send any visitor data, click data, site URL, or WordPress account information to swirv.org as part of these links — the connection happens in the user’s browser when they click the link. Standard web-server access logs on swirv.org (the visitor’s IP address, user-agent, referer) apply the same as any browser navigation to any site.
Service: swirv.org (the Swirv project’s marketing and documentation site) 
Terms of use: https://swirv.org/terms.html 
Privacy policy: https://swirv.org/privacy
<h4>A note on uptime-monitor names</h4>
Swirv ships a default “exclude monitor traffic” list (Settings → Analytics) containing names such as Pulsetic, UptimeRobot, Better Stack, Hyperping, StatusCake, and Pingdom. These are not external services Swirv connects to. They are text substrings Swirv matches against the User-Agent header of incoming requests to your own site, so that clicks from those uptime monitors are not counted in your analytics. No data is sent to any of these services, and no network connection is made.
<h3>Source Code and Bundled Libraries</h3>
Swirv ships two minified third-party JavaScript libraries and keeps all custom Swirv JavaScript readable and unminified.
<ul>
<li><code>admin/js/chart.umd.min.js</code> is Chart.js 4.5.1. Readable source is available at <code>https://www.npmjs.com/package/chart.js/v/4.5.1</code> and <code>https://github.com/chartjs/Chart.js/tree/v4.5.1</code>.</li>
<li><code>admin/js/qrcode.min.js</code> is node-qrcode 1.5.4, bundled from the browser entry point as an IIFE that exposes <code>window.QRCode</code>. Readable source is available at <code>https://www.npmjs.com/package/qrcode/v/1.5.4</code> and <code>https://github.com/soldair/node-qrcode/tree/v1.5.4</code>.</li>
</ul>

Swirv

Share a link once, change where it points later — no resending. Personalised Passes give each recipient their own private URL.

Fred Klopper

The Miix Laposta Campaigns Lite plugin allows you to display your Laposta email campaigns on your WordPress website. This lite version provides basic functionality to showcase your campaigns with simple display options.
Features:
<ul>
<li>Display Campaigns: Show your Laposta campaigns on your site</li>
<li>Display Options: Control campaign count and screenshot visibility</li>
<li>Simple Grid Layout: Clean, responsive grid display</li>
<li>Campaign Screenshots: Toggle campaign preview images on/off</li>
<li>Multi-language Support: Available in English and Dutch</li>
<li>Responsive Design: Works on all device sizes</li>
</ul>
Available Shortcode Parameters:
<ul>
<li><code>number</code> – Maximum number of campaigns to display (default: 0 = all)</li>
<li><code>per_page</code> – Campaigns per page for pagination (default: 6)</li>
<li><code>show_screenshot</code> – Display campaign screenshots (yes/no, default: yes)</li>
<li><code>show_date</code> – Display campaign dates (yes/no, default: yes)</li>
<li><code>keyword</code> – Only show campaigns whose subject contains this keyword</li>
</ul>
Example Usage:
<pre><code>[miix_laposta_campaigns_lite] - Shows all campaigns with pagination (6 per page)
[miix_laposta_campaigns_lite per_page="9"] - Shows 9 campaigns per page
[miix_laposta_campaigns_lite number="12"] - Shows maximum 12 campaigns (paginated)
[miix_laposta_campaigns_lite show_screenshot="no"] - Shows campaigns without screenshots
[miix_laposta_campaigns_lite keyword="newsletter"] - Shows only campaigns with "newsletter" in the subject
</code></pre>
<h3>External services</h3>
This plugin connects to the Laposta API to retrieve and display your email campaigns on your WordPress website.
What is Laposta? 
Laposta is a Dutch email marketing service that allows you to create and send newsletters. This plugin retrieves your campaign data from Laposta to display it on your website.
What data is sent and when: 
* Your Laposta API key is sent to authenticate requests 
* Requests are made to retrieve campaign lists, campaign details, and campaign statistics 
* Data is fetched when you view the plugin admin pages or when the shortcode is displayed on your website 
* Campaign data is cached locally to reduce API calls
No personal visitor data is sent to Laposta through this plugin.
Laposta service links: 
* <a href="https://www.laposta.nl/" rel="nofollow ugc">Laposta website</a> 
* <a href="https://www.laposta.nl/algemene-voorwaarden" rel="nofollow ugc">Laposta Terms of Service</a> 
* <a href="https://www.laposta.nl/privacyverklaring" rel="nofollow ugc">Laposta Privacy Policy</a>

Miix Laposta Campaigns Lite

Display your Laposta email campaigns within WordPress with shortcode functionality.

Swirv vs Miix Laposta Campaigns Lite