SAVEDANK.
LIVE · NOW
NORTH OAK CO.·20% OFF FLOWER·—·ONGOING······
HIGHLAND HEMP·BOGO PRE-ROLLS·—·ONGOING······
GREENBELT DISPENSARY·$25 OFF $100·—·ONGOING······
CASCADE BUDS·FREE GRINDER W/ $80·—·ONGOING······
NORTH OAK CO.·20% OFF FLOWER·—·ONGOING······
HIGHLAND HEMP·BOGO PRE-ROLLS·—·ONGOING······
GREENBELT DISPENSARY·$25 OFF $100·—·ONGOING······
CASCADE BUDS·FREE GRINDER W/ $80·—·ONGOING······
Plugin privacy · v0.2.0

What the Save Dank Tracker plugin does — and doesn't — do with your data

Save Dank charges vendors a commission on orders that come from our directory. The plugin's whole job is to give us the data we need to invoice you accurately for those orders — nothing more. This page spells out exactly which fields leave your site, which ones never get touched, and how you stay in control.

Which orders get sent

The plugin does not send us every completed order in your store. It sends only the orders that are directly attributable to Save Dank — everything else stays on your server, invisible to us.

An order is attributable to Save Dank only if at least one of these is true at checkout:

  1. The shopper arrived from Save Dank and the plugin captured our click-attribution cookie, or
  2. The shopper used a coupon code that's in the cached list of Save Dank codes the plugin syncs from our API.

If neither applies — for example, a walk-up customer using your own in-house promo code — the order is silently skipped. It's never transmitted, never logged on our side, and never stored.

Our server enforces this rule too: if a misbehaving plugin version ever POSTed an un-attributable order, we reject it before writing to the database. The privacy promise is enforced by code on both sides, not just by trust.

What the plugin sends us

For each qualifying order (see above), the plugin makes one HTTPS POST to our /plugin/conversionsendpoint with the following fields. That's the entire payload:

  • Order ID
    Your internal WooCommerce order number (e.g. 12847). Three reasons we keep it: (1) idempotency — if the plugin retries on a flaky network we need to not double-count, (2) refund matching — when an order is later refunded the plugin phones home a second time and we use this ID to find the original row, and (3) vendor audit — you can cross-reference our Connection Log against your own WooCommerce orders panel in one glance.
  • Order total + currency
    Sent as integer cents (e.g. 8900 / "USD") so we can calculate commission accurately and aggregate revenue.
  • Coupon code used
    Only if the shopper used a Save Dank coupon code at checkout. Coupons from your other promotions (e.g. a "SUMMER20" code you run outside Save Dank) are never transmitted — the plugin checks the code against the cached list of Save Dank codes first and skips the order entirely if it doesn't match.
  • Click-cookie token
    If the shopper clicked through from Save Dank, the attribution token our directory set on their browser. No cookie, no token.
  • Timestamp
    When the order completed in your store. Used for reporting and the return-window check.

Sample payload (what an actual request body looks like):

POST /plugin/conversions
Authorization: Bearer sd_live_•••••
Content-Type: application/json

{
  "vendorOrderId": "12847",
  "orderTotalCents": 8900,
  "currency": "USD",
  "couponCode": "BUDLIST20",
  "sdRef": "abc123def",
  "occurredAt": 1776936570504
}

What the plugin never touches

Every field below stays on your server. The plugin is not authorized to read, transmit, or cache any of it — it literally doesn't call the WordPress APIs that would expose these values.

  • Customer names, emails, or phone numbers
  • Shipping, billing, or IP addresses
  • Payment details of any kind (card numbers, PayPal, crypto, etc.)
  • Product names, SKUs, descriptions, or inventory
  • Line-item breakdowns unless you explicitly opt in
  • Visitor analytics, page views, or browsing history
  • Your customer database or mailing list
  • Anything from plugins other than Save Dank Tracker
  • WordPress admin users, roles, or credentials

Where the data goes

Conversion records are stored on Save Dank infrastructure and are visible only to you (on your vendor dashboard) and our admin team for support and invoicing. We do not share, sell, or resell any of this data to third parties. We do not enrich or cross-reference it with data from other sources.

How long we keep it

Conversion records are retained while the vendor relationship is active so we can invoice correctly and honour the return window on past orders. If you end your relationship with Save Dank, we will delete all conversion records older than 30 days within 30 days of termination on request.

Your kill switch

You can disconnect the plugin in under a minute, any time, for any reason:

  1. Revoke your API key from the vendor dashboard — it stops working immediately, worldwide.
  2. Deactivate + delete the plugin in WordPress (Plugins → Installed Plugins).

No call-us-to-cancel. No waiting period. No hidden processes still running.

Questions, concerns, incident reports

Email [email protected] and we'll respond within two business days.

This page describes the data practices of the Save Dank Tracker plugin only. For the broader Save Dank directory privacy policy, see the main site privacy page.