PRIVACY · UPDATED 27 OCTOBER 2026
Your data.
Your business.
Know what stays in your store, what this website needs, and how to make a privacy request.
Who is responsible?
View current operator and privacy details, including without JavaScript.
The company identified below operates OrderWorth and is the controller of personal data collected through this website and its licensing service. Your store operator controls the data processed inside its own WordPress installation.
Legal business name: A.M.E.X. Internet Marketing ltd
Business address: Makariou III, No.9, Larnaca, 7530, Cyprus
Country: Cyprus
Company registration: HE377934
VAT registration: 10377934Z
Privacy contact: Show email
Product support: Show email
For an email enquiry or privacy request, include “OrderWorth” in the subject.
What we use, and why
Data comes from you, your activated installation, the browser request and payment confirmations from Stripe. We do not buy or sell personal data. Newsletter emails require separate, optional consent.
| Purpose and information | Legal basis |
|---|---|
| Deliver a purchase and restore access: plan, amount, currency, payment references and status, dates, accepted terms version, purchase identifier and billing email. Requested access links use a token hash, purchase and customer identifiers, security generation, expiry and use status. | Perform a contract with an individual purchaser, or our legitimate interest in supplying a business purchaser. |
| Provide updates and site slots: license term, purchase-key hash, site URL, installation-token hash, activation date, last authenticated check time and check result. | Provide the purchased service; administer business licenses where relevant. Free reports require no licence. Pro 1.10.18 requires initial site activation; earned local access then continues after subscription expiry or a service outage. |
| Written assistance: your request subject, message text, replies and timestamps. The support privacy notice explains ticket contact fields and AI-assisted staff drafts. | Provide requested contractual support, or our legitimate interest in answering business enquiries. |
| Privacy requests: request type, correspondence, received date, response target, status and any documented retention hold. | Meet our data-protection obligations. |
| Protect the service: request IP address transiently, a keyed IP hash for rate limits, essential browser-recovery identifiers and operational request metadata. | Our legitimate interest in preventing abuse and protecting purchases. Essential cookies support a service you request. |
| Accounting, disputes and refunds: necessary transaction records, dates and payment references. | Applicable legal recordkeeping obligations and our legitimate interest in establishing or defending claims. |
| Optional first-party visitor analytics: public page name, time/day, approximate country and a short-lived, pseudonymous visit identifier. No IP address is stored in analytics. | Your consent, GDPR Article 6(1)(a). Rejecting does not limit browsing or purchases. |
| Staff administration: contact and profile details, role, access status and security activity needed to manage authorised access. | Our legitimate interest in securing and administering business operations. Staff provide these details to use their accounts. |
Contract, legal-obligation and legitimate-interest grounds correspond to GDPR Article 6(1)(b), (c) and (f). Our interests are delivering a secure service, handling business enquiries and resolving disputes; you may object to processing based on legitimate interests.
You can browse and download Free without providing a name or email to this application. A purchase needs payment verification; Pro activation needs a site URL. Without those details we cannot supply the relevant service. Share only what your request needs. Do not send passwords, access keys, card details, special-category data or your customers’ order records.
Purchase confirmations and requested access emails help you retrieve a completed purchase. Links go only to the billing email already associated with that purchase. Entering an email or order reference alone does not grant access: you must open the private link and explicitly continue on our website. The link expires after 30 minutes and can be used once. It does not contain your permanent activation key. We use request limits and existing account and licence checks to prevent abuse; these emails do not subscribe you to marketing.
License checks automatically compare payment status, term and site limits. They do not profile shoppers or determine store profitability, and installed reporting features are not remotely disabled. If access appears wrong, request a human review through written support. This application makes no solely automated decisions intended to have legal or similarly significant effects on individuals.
Payments, providers and international transfers
Pricing follows your URL or manual currency choice. Otherwise our existing Cloudflare network suggests an approximate country, with browser timezone and language as a fallback. You can change the suggestion. The selector does not save the country, your IP address or a currency preference, and does not request GPS access. A VPN or proxy can affect the suggestion. Manual choices travel in the page URL. Separately, optional first-party visitor analytics records an approximate country only after consent. USD, EUR, GBP, CAD and AUD prices are set independently; no exchange-rate service is used.
Stripe handles payment credentials on its own website. We do not receive your card number or payment password. Stripe collects the billing details needed to process the payment, such as a billing address and email. This application stores payment references, amounts, currency, applicable tax and the accepted pricing revision, and the billing email needed to associate a purchase with its customer record. This email is not treated as verified account ownership. It does not copy payer names or billing addresses from those responses. Historic PayPal transactions, if any, retain their original provider records. Older purchases may also retain the exchange-rate details used at the time. Stripe controls its own payment processing; see its privacy statement.
A.M.E.X. Internet Marketing ltd operates OrderWorth from Cyprus. GoDaddy hosts our website and purchase, customer, licence and support records in the United States, and provides our mailbox and outgoing email services. Cloudflare provides website delivery, security and the separate performance measurement described in our privacy notice. OpenAI Sites and Cloudflare also process requests to a legacy service address and may retain historical service records. Stripe handles hosted payments, billing details and automatic tax. Authorised staff and necessary professional advisers access information only for their work. Purchase and subscription confirmations go to the billing email supplied at checkout. Purchases do not subscribe you to marketing.
International transfers: Our GoDaddy VPS is in the United States. OpenAI, Cloudflare, Stripe and Google operate internationally; processing is not restricted to Cyprus or the EEA. Their applicable data-processing terms describe safeguards for covered transfers, including the European Commission’s standard contractual clauses and, where the recipient and processing qualify, an adequacy decision. The EU–US Data Privacy Framework covers participating organisations and covered processing, not every US service. Contact Show email for information about the safeguards applicable to your data or a copy. Provider terms and scope must be reviewed when the service or recipient changes.
Provider information: GoDaddy privacy, Cloudflare processing terms, OpenAI processing terms, Stripe processing terms, and GoDaddy processing terms.
Necessary records may also be shared with authorised professional advisers or competent authorities when required by law or needed for a legal claim. We limit disclosure to the purpose concerned.
How long data is kept
- Checkout recovery: the browser cookie lasts up to 24 hours from issue or refresh. Server recovery for each order expires 24 hours after that order starts. Closing recovery invalidates its browser link sooner.
- Email access links: links expire after 30 minutes and are marked used when redeemed. Their server token records become eligible for deletion seven days after expiry during scheduled cleanup. Delivery or cleanup delays can extend record retention, but an expired or used link cannot grant access. Necessary purchase, email-delivery and abuse-prevention records follow their separate retention purposes.
- Written support: closed requests are eligible for deletion 730 days after their last activity.
- Privacy requests: closed requests are eligible for deletion 1,095 days after their last activity, to document how the request was handled. These are our policy periods, not universal GDPR deadlines.
- Open requests and holds: kept while needed for resolution or a documented legal claim. Holds require a reason and must be reviewed; they are not permission to retain data indefinitely.
- License and payment records: kept while needed to provide access and for the applicable accounting, refund and claims periods. Activated site URLs can be removed in My purchase.
Authorised staff initiate deletion of eligible correspondence, expired browser associations and rate-limit records. This does not automatically erase financial records, provider logs, backups or data inside your WordPress store.
Financial and license retention: Paid purchase and licence records are retained while needed to provide purchased access, reconcile payments, handle refunds or disputes, and meet applicable accounting and legal obligations. We review these purposes at least monthly and delete or anonymise records when they no longer apply. A legal hold is reviewed while it remains necessary. Removing a site slot removes its active registration; it does not erase the purchase or payment provider records. Contact Show email about the period and basis applicable to a particular record.
Closed purchase-support messages are eligible for deletion after 730 days and closed privacy requests after 1,095 days, unless an unresolved request or a documented legal hold requires longer retention. We review retention needs at least monthly; eligibility does not mean immediate deletion. Other correspondence and security records are kept only while needed for support, security, disputes or legal obligations. Deleting a live record does not immediately remove backup copies. Local and provider backups rotate separately, are restricted to recovery, and remain subject to applicable erasure or restriction decisions when restored. We do not promise one fixed maximum age for every provider or backup copy.
Optional first-party visitor analytics
When enabled by the operator, our first-party measurement counts visits and page views on public product and help pages. It excludes checkout, My purchase, staff pages and API URLs. The browser sends only a permitted page name, a random visit identifier and a random event identifier after acceptance. The service adds the date and approximate country supplied by the hosting network. It does not store a full URL, query string, referral URL, IP address, precise location, name or email in analytics.
A visit is a 30-minute session in one browser tab, not a unique person. Another tab or later visit can be counted again. Common bots and staff cookies are filtered where detected; coverage is incomplete and automated traffic can still appear. VPNs and proxies may affect the country. These statistics are not used to change individual prices, profile shoppers or track activity across other websites.
The choice is remembered for 180 days, whether accepted or rejected. A visit identifier expires after 30 minutes or when its tab closes. Server event identifiers become eligible for cleanup after 24 hours; daily country/page totals cover 90 days. Cleanup runs in bounded batches during measurement and report requests; an inactive service does not run a background cleanup job. Expired records are excluded from reports. Authorised staff can delete visitor statistics; deletion requires the service to run or staff to initiate cleanup. Aggregated totals cannot reliably be linked back to a named person.
First-party visitor analytics remains off until controller and privacy-contact details are configured and the operator has reviewed these disclosures. Accepting analytics does not consent to marketing. Change your measurement choice.
Cloudflare performance measurement
Cloudflare measures how pages on this website load and respond, including blog pages. Where its browser beacon runs, it sends page-load timings, a temporary page-load identifier and page/referrer URL information to Cloudflare. Cloudflare states that this beacon uses no cookies or browser storage and does not track visitors across websites. Network requests still pass through Cloudflare’s infrastructure.
This service is separate from our optional first-party visitor analytics. It can run before an analytics choice and is not controlled by our Accept/Reject buttons, Global Privacy Control or Do Not Track handling. Availability can vary by location and browser. Read Cloudflare’s performance data and privacy explanation for its collection, processing and regional limits.
Staff accounts and access
Authorised staff use contact, account and security records to access and administer the service. These records are not made public. Access can be revoked, and only authorised personnel may review account activity.
Expired access records become eligible for cleanup after expiry; expired invitations after 30 days and security activity after 365 days. A revoked account may be deleted after reviewing any continuing legal or security need. Relevant audit history can remain. Staff may use the privacy contact above to request access, correction or erasure. These records are separate from customer purchases and newsletter choices.
Your choices and rights
You may request access, correction, erasure, restriction, portability where applicable, or object to processing based on legitimate interests. If processing relies on consent, you can withdraw that consent without affecting earlier lawful processing. Use Privacy choices to accept, reject or withdraw optional first-party visitor analytics. Withdrawal stops that collection and removes its visit identifier from this browser. Your browser’s Global Privacy Control or Do Not Track signal also disables our first-party visitor analytics. These controls do not govern the separate Cloudflare performance measurement. We do not use marketing trackers.
Open My purchase → Privacy & your data to download a JSON copy of the application records linked to that purchase or send a privacy request. These tools are free and remain available after the paid update term expires or is suspended. The export excludes security credentials and does not include provider logs, email correspondence or local WordPress records. Request a complete access review if you need data beyond the export. A purchase can be linked to several people; we protect others’ information when answering individual requests.
You do not need to buy Pro, renew it, have an access key, make a phone call or use this form to exercise your rights. Email the privacy contact above if you are a visitor, use Free, lost your key, or prefer email. We may ask for proportionate verification where there are reasonable doubts about identity; do not send identity documents unless needed and requested through a secure route.
We respond without undue delay and normally within one month. A permitted extension of up to two further months for complexity or number of requests must be explained within the first month. If we cannot grant a request, we explain why and how to challenge it. Some records may have to be kept for a legal obligation or claim; erasure does not automatically cancel a purchase.
Replies to requests made in My purchase appear there; no email notification is sent. Check the request thread for updates, or use email if you need a different written channel.
You may complain to the supervisory authority where you live, work or believe an infringement occurred. Find your authority in the EDPB directory. You do not have to contact us first.
Temporary live demos
When you request a Free or Pro live demo, we create a separate temporary WordPress store containing fictional orders. A necessary secure, HTTP-only browser cookie, __Host-orderworth_demo, associates your browser with the demo for up to 24 hours. WordPress also uses sign-in and settings cookies scoped to that demo. The store itself expires after 30 minutes and is removed when you end or reset it, or when expiry cleanup runs. Do not enter real customer data, personal information, passwords or payment details.
Changes you make and any locally captured demo emails exist in the temporary store. Demo emails are displayed in its demo inbox and are not delivered to external recipients. We keep short-lived session metadata to operate the service: a random session identifier, keyed browser identifier, edition, creation and expiry times, and status. Cleaned session metadata is eligible for removal after 24 hours; keyed network and browser rate-limit timestamps after one hour. The demo service does not save raw IP addresses in its session database. Hosting and security request logs follow the separate purposes and retention described above.
We use this information to provide the demo you request and protect shared service capacity. Opening a demo does not subscribe you to email or grant optional analytics consent. You can end your temporary store using its toolbar. See demo browser storage.
Optional plugin sharing and emails
In the current Free version, a separate optional screen at the end of Quickstart offers two independent choices after the lessons. Both checkboxes start unchecked and the email field is empty. Skip and finish makes no request to these optional OrderWorth services, opens Profit overview and leaves Free fully usable. Existing saved or skipped choices are preserved when you replay the lessons. You can review the choices later in OrderWorth → Help & preferences → Privacy choices. Installing or activating either edition is not newsletter consent.
- Hostname sharing: if selected, the plugin sends the store’s hostname so we can record which domains have opted in. It does not send the site URL path, email address or Free/Pro edition for this choice alone.
- Newsletter request: if selected, the plugin sends the email you enter and whether Free or Pro is active, to request tips, release news and occasional Pro offers tailored using that reported edition. It does not send the store hostname unless you also select hostname sharing. For a new signup, we send a requested confirmation email; the subscription starts only after you open its link and confirm on the page. Existing subscriptions and preferences are preserved. Article emails, purchase-based personalization and click tracking remain separate choices.
These requests also use a random connection identifier, an authentication credential, a consent-notice version and request time. The service records consent and accepted-report times; the website infrastructure processes the network information needed to receive and protect the request. These are identifiable records, not anonymous statistics. The optional signup does not send order records, customer details, product costs, report totals, WordPress/PHP versions or site-language settings.
After consent, the plugin can refresh the chosen information weekly. Changes between Free and Pro can update the newsletter edition record, no more often than hourly. These tasks depend on WordPress scheduling and may run late. Opening reports does not send financial data to this service. The two choices are separate from Pro licence activation, optional local workflow counts and website visitor analytics.
Retention for this optional connection
Domain and edition details expire after 90 days without an accepted report. Minimal connection and revocation records remain for up to 90 days from the last accepted report or an early cancellation, so delayed requests cannot restore stopped sharing. A new enrollment must arrive within 24 hours of its request time; materially future-dated requests are rejected. A pending newsletter request expires after 48 hours; a confirmed subscription expires 730 days after confirmation. Withdrawal protection and consent-event records for this channel last up to 180 days. Scheduled cleanup attempts run before the newsletter worker, independently of mail delivery; missed jobs or outages can delay physical deletion. Backups follow the separate retention section below, and removals must be reapplied after restoration.
Change or stop a choice
Use the plugin’s Privacy choices to stop its reporting and request authenticated removal of that connection’s shared information. Sharing stops locally immediately; if the service cannot be reached, the plugin retains the removal request for retry and shows its status. A plugin stop cancels an unconfirmed signup made by that connection and removes its edition link. It does not silently unsubscribe an already confirmed newsletter subscription. Use the private preferences or unsubscribe link in an OrderWorth email to stop that subscription, or contact the privacy address above. Deactivation pauses refreshes; it does not unsubscribe you. Stop sharing before uninstalling to request remote removal.
Consent is the basis for these optional choices. Refusing or withdrawing them does not disable Free or change your paid entitlement. Existing purchase, support and licence records follow their separate purposes and retention rules. The newsletter privacy notice explains email confirmation, unsubscribe, provider processing and newsletter retention.
Your WordPress store
Pro previews and a remembered task: genuine example screenshots are bundled with Free and show fictional data. Opening a preview does not save a continuation choice or grant permission for costs, imports, emails or schedules. Only an explicit Continue this task with Pro action remembers the selected workflow locally for seven days, scoped to your WordPress account and store. The workflow choice and store identifiers are not appended to the external pricing link. The destination website still processes the ordinary request information described above. Preview visibility and suggestion dismissals are separate local preferences and can be restored inside OrderWorth; they do not enable optional workflow counting.
Dynamic suggestions after reports, imports and fee reviews use separate site/account/workflow flags in browser sessionStorage, limiting each type to one appearance in that tab session. Only one suggestion card is visible at a time. If this storage is unavailable, dynamic suggestions stay hidden. Completed-report and import counts used for the current suggestion exist only in the page’s memory and are not sent to OrderWorth. The expense-settings preview stays available until dismissed or hidden; Continue with Free removes it for the current page. These controls do not change the separate optional local-count recording choice.
The local _owwc_pro_journey_v1 record, separately keyed per site on multisite, contains the chosen workflow name, creation and expiry times, visibility choice, site-binding hash and revision. The task becomes unusable after seven days; WordPress cron removes the stored choice when the cleanup event runs, which may be later if cron is delayed. Forget this task clears it earlier. WordPress privacy export includes this state. Privacy erasure clears the choice and visibility preference while retaining a minimal revision tombstone to reject stale forms. Uninstall removes this journey record and its current-site cleanup event. Existing financial, guide and optional local-count records retain the preservation rules described below.
WordPress.org review reminders: separately from optional workflow counts, Free keeps a small reminder record in your WordPress user profile for this site: the time of your first completed nonempty report, up to three distinct report dates, your reminder choice and any reminder-until date. It contains no order identifiers, financial results or review rating, and is not sent to OrderWorth. A request can appear inside OrderWorth after 30 days and use on at least three dates, once the official listing is available. You can postpone it or stop reminders. Choosing the review link stops reminders; the plugin does not know whether you post a review. Manage this choice under Help & preferences → Local progress. These records are included in WordPress personal-data export/erasure and removed when Free is uninstalled.
Optional Local progress records daily workflow counts in the signed-in manager’s WordPress user profile, only after that person enables it. Counts cover report completion, saved reviews and selected workflow links; they contain no order IDs, costs or customer contact fields. The view and requested CSV export show up to 90 days. Older stored counters are pruned on the next recorded event or when cleared. Turning recording off clears counts; contextual-suggestion dismissals remain separate. No counts are transmitted to OrderWorth or a tracking provider.
Free works without sharing a hostname or joining a newsletter. Optional contact with OrderWorth starts only after the separate choices described above. Calculations and order reviews run on your WordPress server. Report payloads and CSV exports exclude customer names, emails and addresses. Order IDs and staff user IDs can still identify people when combined with other store records: these reports are not guaranteed anonymous. Your store controls this local data and its retention, including exports, backups and mail providers. Installing OrderWorth does not make a store GDPR compliant.
The plugin stores your expense assumptions, manual review values, and the reviewing WordPress user ID and time. Scan ID lists belong to the requesting user and expire after one hour. Deactivation and uninstall preserve settings and review records.
Pro background reports store the requesting manager’s user ID, selected internal order IDs during processing, financial report rows, dates, progress and aggregates locally. Processing expires after 24 hours. New reports expire after seven days by default; a manager can select 30, 90 or 365 days and a maximum of 12, 24 or 60 retained reports. Existing expiry dates are unchanged. Cleanup runs through WordPress. An owner may grant up to 25 signed-in accounts read-only access to one completed revision; stored grants identify those accounts and are checked on every view/download. Grants expire with the report or can be revoked. Sharing sends no email. Deactivation pauses manual work; local records remain.
Stripe and PayPal fee assistance reads locally stored gateway metadata and makes no provider request. Reviewed CSVs can supply product costs, payment fees and shipping/fulfilment expenses. Files contain internal IDs, costs and non-personal references; avoid uploading customer contact details. Previews and results are private to their owner. Imported source files are read from PHP temporary upload storage and are not retained as public files. Payment-fee and shipping/fulfilment previews and guarded undo expire after one hour; bulk product-cost work and undo expire after 24 hours.
Optional tutorial progress
Inside WordPress, Quickstart stores your reading status and lesson progress for your WordPress user. Separate local records hold the latest completed report date, date ranges, order counts and currency, plus the latest reviewed order ID and change signature. These checks help you resume; reading a lesson does not certify your store data. Replay resets reading progress only. These records stay in WordPress and are preserved on uninstall. See the named data records and removal reference. The public website guide does not save reading progress.
Imports, presets and scheduled summaries
Free cost-import previews are private to the importing WordPress account, contain product identifiers and costs, and expire after 24 hours. Undo checks that an imported cost has not changed. Product stamps and the user’s last-import reference remain; imports do not rewrite existing order costs.
Pro keeps up to 10 personal date presets and the latest 10 original aggregate summaries in WordPress. Its separate Scheduled reports & alerts workflow supports independent daily, weekly and monthly report packs. Schedules and email start off. Action Scheduler or WP-Cron runs work locally; your host scheduler must be operating.
If you enable summary or report-notice email, the schedule owner’s current WordPress profile email address and financial figures or alert details pass through your store’s mail service. Scheduled report notices contain an authenticated link, no report attachment or customer contact fields. These emails are not sent through OrderWorth’s license service. Turn email off to stop notices or pause the relevant schedule to cancel its pending work. Deactivation disables scheduled work; re-enable explicitly after reactivation. Mail acceptance does not prove inbox delivery.
Optional WooPayments fee lookup
With official WooPayments 11.1.0 installed, you may explicitly confirm a lookup in Bulk payment fees. The selected order’s saved payment-intent ID is sent through WooPayments’ authenticated merchant client to its existing payment service to retrieve transaction details for fee verification. No lookup happens just by viewing a page, collecting a report, importing a CSV or running scheduled work. The request does not charge, refund, enrol or change gateway settings. Stop requesting lookups to stop future requests.
OrderWorth retains only the reduced amount, currency, time and provenance needed for the review; it does not retain provider secrets or customer contact details from the response. Applying the fee requires separate confirmation. The payment provider handles its existing transaction records under its own terms. See WooPayments service documentation and Automattic’s privacy policy.
Pro workflow records and retention
Pro’s private Review queue retains up to 100 findings per owner, their report/revision reference, dates, status, reason and latest 10 changes. Period review retains up to 30 frozen-report checklists and notes per owner. These records remain until removed; the source report keeps its original access and expiry rules. Do not enter customer contact information into notes. Scenarios run in your browser and do not save or transmit assumptions or alter store records.
ShipStation preparation handles the supplied shipment file locally on your WordPress server, with no provider request. The raw file is discarded after preparation; the private expense preview retains normalized order IDs, amounts and a hashed source reference for one hour. Applied costs and source references follow order retention. This does not change the existing retention of merchant exports, logs or backups.
Supplier mappings and saved filter definitions belong to their WordPress user, with up to 20 of each. Background imports keep progress, product identities, costs and undo provenance for 24 hours; up to five recent jobs can be reopened. Multiple schedules store owner IDs, cadence, filter choices, alert thresholds and separate email preferences. Up to eight schedules per owner and 32 per site are supported. Pausing stops future work; report expiry still applies. Existing date presets and the original latest-ten summary history remain separate.
Cost history records observed changes with the WordPress actor, time, source, reason and before/after values. Defaults are 730 days / 100,000 records; administrators may choose 30–3,650 days / 1,000–250,000 records, with gradual hourly cleanup. Future-cost records retain owner/product IDs, cost components and confirmation details, expiring after their effective date plus the retention duration selected at confirmation. Historical changes are not reconstructed.
The optional local calculation index retains financial rows and validation signatures, bounded at 100,000 rows / 256 MiB, with 7-, 30- or 90-day expiry. Turning it off stops new reuse; stored rows follow their expiry. Frozen completed reports keep their original expiry. Deactivation and uninstall preserve settings, reviews and retained records. Downloaded reports, backups and mail copies follow your own organisation’s retention and access controls.
Pro historical exchange rates
Pro queues historical-rate requests for foreign orders and requested backfills through your WordPress background scheduler. Frankfurter receives the currency pair and historical date range over HTTPS. The request does not include your order ID, customer details, costs, purchase key or installation token. Like any contacted server, the provider receives the connection from your server; review Frankfurter’s service information for its current handling.
WordPress stores the locked order rate, its source and effective date, shared rate caches, retry records and backfill progress. Where configured by an integration, it also records payment-fee amounts and currencies locally. Opening a report does not fetch new rates. Valid historical snapshots are preserved. These plugin requests are separate from this website’s independently fixed USD, EUR, GBP, CAD and AUD purchase prices.
Pro activation and updates
When you choose to activate Pro and update access, Pro sends your purchase key, site URL and plugin version to the OrderWorth service. It stores an installation token in WordPress instead of the full purchase key. Subsequent update checks send that token, site URL and version. A site slot stores the URL, token hash, activation time, last authenticated check time and the result (active, expired or suspended). The timestamp is not evidence that a store is online. Historical installations have no last-check time until they contact the updated service.
No order data, customer details, product costs or report totals are sent to the license service. Pro 1.10.18 requires a successful initial activation for this site before its tools unlock. Earned local access continues after expiry and service outages. Disconnecting or clearing the local connection, or moving to a different host or home path, locks new Pro work; saved rules keep applying and financial data remains.
Security and changes
Keep your purchase key private: it opens downloads, site slots and correspondence for that purchase. Contact support if you believe someone else has gained access. We use access controls and protected credentials to manage purchased access.
We use HTTPS, role-restricted staff management, server-side authorisation, request limits and output escaping. No system can guarantee zero risk. We update this notice when the service changes and provide information before new uses require it. Policy version: 2026-09-28.4.
Plugin suggestion preferences
Inside your own WordPress administration, Free uses browser session storage to limit contextual suggestions to one per tab session, scoped to the site and signed-in account. Continuing a Free workflow hides its card for that session. Persistent dismissal is saved in your WordPress user preferences. These choices are not sent to OrderWorth.