Contents
On this page

Privacy and uninstall - Plugixa POS for WooCommerce

Plugixa POS keeps its data in your own WordPress database. It sends no sale, order or customer data to Plugixa or to anyone else. This page lists what it stores, the two outside services it can involve, and what happens when you delete it.

What the plugin stores

Sales are WooCommerce orders, stored by WooCommerce like any other order. On those orders the plugin adds the register, store, cash session, cashier, payments, ticket number and fiscal hash of the sale.

Its own tables, all named wp_plugixapos_... (with your table prefix):

Table What it holds
outlets and registers Your store details and registers.
sessions and cash_movements Cash sessions with their float, expected and counted amounts, and each cash in or out with its reason and user.
held_carts Sales put on hold at the register, until they are resumed.
order_refs The link between each register sale and its WooCommerce order and ticket number.
invoices and invoice_sequences PRO Issued invoices and credit notes, with the customer details typed for them, and the number counters.
fiscal_journal Every sale, refund, session event and reprint, with its lines, totals, payments, the customer’s user id and the user who made it.
fiscal_closings Session, day, month and year closings.
audit_log Refused changes to register orders, journal checks and Pro events such as issued invoices, with the user, the IP address (REMOTE_ADDR) and the time.
sync_log Recent product and stock changes the registers pick up. Rows older than two days are deleted.

Settings are stored in the plugixa_pos_settings option. Pro modules add tables of their own with the same prefix.

The fiscal journal, the closings and the audit log are append-only: the plugin has no code that edits or deletes their rows. Keep that in mind when you answer a request to erase a customer’s personal data. See Fiscal journal.

What stays in the browser

The register keeps, in the browser’s local storage of each device:

  • the current sale (plugixa-pos-cart), so a reload or a crashed tab does not lose it;
  • which register the device is;
  • small display preferences, such as the width of the cart panel.

None of this is sent anywhere except to your own site.

Outside services

The register’s font and icons are served from your own site.

Freemius

The plugin includes the Freemius SDK, which shows an optional opt-in screen on activation and the plugin’s account page. It is the only outbound connection your server makes for the plugin.

  • If you skip the opt-in, no identifiable data is sent.
  • If you opt in, the data that screen lists is sent to https://api.freemius.com: your WordPress user’s first and last name and email address; your site’s homepage URL and title, WordPress and PHP versions and site language; the plugin’s version and whether it is active or uninstalled; and, unless you switch that item off on the opt-in screen, the names, slugs and versions of your installed plugins and themes and whether each is active.

No sale, order or customer data is ever sent to Freemius or to Plugixa. The Upgrade links are plain links to the plans page on plugixa.com; the plugin shows no pricing or checkout page inside WordPress and loads no analytics.

Provided by Freemius, Inc.: Terms, Privacy.

WhatsApp

Only when a cashier chooses to send a receipt by WhatsApp on the sale complete screen, the cashier’s browser opens https://wa.me with the customer’s phone number (as typed or taken from the customer’s account) and a plain-text copy of the receipt: shop name, ticket and order number, date, items with their prices, discounts, total, payments and change. Your server sends nothing, and the message is only sent if the cashier presses Send in WhatsApp. Nothing is opened if the button is not used. See Receipts.

Provided by WhatsApp LLC (Meta): Terms, Privacy.

Pro integrations such as card terminals and pay links connect to their own providers; each is described on its page.

Deactivating

Deactivating the plugin stops its scheduled tasks (the automatic closings among them) and changes no data. Reactivating it picks up where it stopped; missing day, month and year closings are written on the next run.

Deleting the plugin

By default, deleting the plugin from Plugins removes its files and keeps everything else: tables, settings and the capabilities on roles and users. Reinstalling brings it all back, with staff access intact.

Erasing the data

Erasing is off by default. The setting is Delete Plugixa POS data when the plugin is deleted (delete_data_on_uninstall). The Settings screen has no switch for it, so it can only be turned on through the REST API, by a site administrator:

PUT /wp-json/plugixa-pos/v1/settings
{ "delete_data_on_uninstall": true }

With it on, deleting the plugin:

  1. runs the plugixa_pos_uninstall action, so add-ons can clean up;
  2. drops every wp_plugixapos_ table except the fiscal ones: fiscal_journal, fiscal_closings, the audit log and any other fiscal_ table are always kept;
  3. deletes the plugixa_pos_settings option and the plugin’s database version markers;
  4. removes every plugixa_pos_ capability from all roles and users.

WooCommerce orders made at the register are WooCommerce’s data and are never deleted by the plugin.

Erasing is skipped, and everything is kept, when:

  • the user deleting the plugin cannot activate plugins;
  • another copy of Plugixa POS (for example the free and the Pro build side by side) is still installed, active or not, because that copy uses the same tables.

The fiscal records are kept so that deleting a plugin never deletes records a tax audit may ask for. How long you must keep them depends on your country. To remove them, drop the tables yourself once you are sure you no longer need them.

Quick Links

Share