<\/p>\n
\nPRIVACY & SECURITY\n<\/p>\n
\nLangSpector is designed around local auditing, read-only operation and limited communication with external services.\n<\/p>\n<\/div>\n<\/div>\n
<\/p>\n
\nPRIVACY BY DESIGN\n<\/p>\n
\nLangSpector performs its multilingual analysis directly inside your WordPress installation.\n<\/p>\n
\nYour posts, pages, visible text, SEO metadata and image ALT text are not sent to the LangSpector license server for analysis.\n<\/p>\n
\nThe local audit and the Pro licensing system are intentionally kept separate.\n<\/p>\n<\/div>\n<\/div>\n
<\/p>\n
\nLOCAL AUDITING\n<\/p>\n
\nLangSpector does not send the content being audited to an external LangSpector analysis service.\n<\/p>\n<\/div>\n
\nLanguage analysis uses local language profiles included with the plugin rather than sending text to an AI API.\n<\/p>\n<\/div>\n
\nLanguage detection compares content against the relevant languages configured on your WordPress site.\n<\/p>\n<\/div>\n
\nScanning does not automatically rewrite or repair the content being inspected.\n<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n
<\/p>\n
\nREAD-ONLY BY DESIGN\n<\/p>\n
\nLangSpector identifies potential inconsistencies and gives you the information needed to investigate them.\n<\/p>\n
\nIt deliberately leaves the final decision and any correction to the WordPress administrator.\n<\/p>\n<\/div>\n
<\/p>\n
\nDATA STORED BY LANGSPECTOR FREE\n<\/p>\n
\nLangSpector uses dedicated database tables for the information required to display and manage audit results.\n<\/p>\n
\nInformation about the audit itself, including its status and processing information.\n<\/p>\n<\/div>\n
\nThe issues detected during the audit, including their type, severity, language, affected WordPress object and explanatory details.\n<\/p>\n<\/div>\n
\nInformation required to recognise findings that you deliberately chose to ignore.\n<\/p>\n<\/div>\n<\/div>\n
\nOlder completed audit records are removed as newer audits replace them, while ignore preferences can remain available for future scans.\n<\/p>\n<\/div>\n<\/div>\n
<\/p>\n
\nDATA REMOVAL\n<\/p>\n
\nLangSpector includes an option to remove its stored audit data when the Free plugin is fully uninstalled.\n<\/p>\n
\nSimply deactivating the plugin does not trigger this removal, helping prevent accidental loss of audit information during temporary deactivation.\n<\/p>\n<\/div>\n<\/div>\n
<\/p>\n
\nLANGSPECTOR PRO\n<\/p>\n
\nPro needs limited technical communication to activate licenses, verify entitlement, manage installations and provide protected updates.\n<\/p>\n
\nUsed to identify and validate the Pro license.\n<\/p>\n<\/div>\n
\nUsed to associate an activation with the relevant WordPress website.\n<\/p>\n<\/div>\n
\nA generated installation identifier distinguishes one WordPress installation from another.\n<\/p>\n<\/div>\n
\nIdentifies whether the installation is production, staging, development or local.\n<\/p>\n<\/div>\n
\nSent when checking whether an eligible Pro update is available.\n<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n
<\/p>\n
\nWHAT IS NOT SENT FOR LICENSING\n<\/p>\n
\nThe Pro licensing request is separate from the multilingual audit itself.\n<\/p>\n
\nThe license server does not need the text of your posts or pages to determine whether your Pro installation is authorised.\n<\/p>\n<\/div>\n
<\/p>\n
\nINSTALLATION RECORDS\n<\/p>\n
The address associated with the activated installation.<\/p>\n<\/div>\n
The identifier generated for that WordPress installation.<\/p>\n<\/div>\n
Production, staging, development or local classification.<\/p>\n<\/div>\n
Activation and most recent successful license-check timestamps.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n
<\/p>\n
\nLICENSE KEY SECURITY\n<\/p>\n
\nThe complete license key is required for activation and for sensitive installation-management operations.\n<\/p>\n
\nOn the license server, the licensing system maintains a cryptographic hash for key matching and an encrypted representation where the complete key must remain recoverable for administrative purposes.\n<\/p>\n
\nDo not publish or share your LangSpector license key publicly.\n<\/p>\n<\/div>\n
\nAccess to the complete installation list requires the full license key.\n<\/p>\n
\nOnce unlocked from WordPress, access automatically locks again after a limited period.\n<\/p>\n
\nRemote installation management is therefore not exposed merely because someone knows the website URL.\n<\/p>\n<\/div>\n<\/div>\n<\/div>\n
<\/p>\n
\nLICENSE SERVER AVAILABILITY\n<\/p>\n
\nAfter a successful license verification, LangSpector Pro allows a seven-day offline grace period<\/strong>.\n<\/p>\n \nIf the license server temporarily becomes unreachable, a previously verified installation can continue using Pro during this period.\n<\/p>\n \nAfter the grace period, another successful verification is required to keep Pro active.\n<\/p>\n<\/div>\n<\/div>\n <\/p>\n \nAPI PROTECTION\n<\/p>\n \nActivation, verification and installation-management requests are rate limited to reduce automated abuse.\n<\/p>\n \nThe requesting IP address may be processed temporarily for this rate-limiting mechanism, but it is not part of the LangSpector activation record.\n<\/p>\n<\/div>\n<\/div>\n <\/p>\n \nPURCHASES & STRIPE\n<\/p>\n \nWhen purchasing LangSpector Pro, checkout takes place through Stripe’s payment infrastructure.\n<\/p>\n \nLangSpector’s license database does not store your card number or card security code.\n<\/p>\n<\/div>\n \nInformation returned after checkout can include the customer’s name and email address required to create and deliver the license.\n<\/p>\n<\/div>\n \nStripe customer, checkout, subscription and payment identifiers may be stored to manage purchases, renewals, cancellations and refunds.\n<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n <\/p>\n \nLangSpector does not require your site content to process a payment, activate a license or determine whether Pro updates are available.\n<\/p>\n \nDetailed information about personal data collected through this website, purchasing and support will be available in the separate Privacy Policy.\n<\/p>\n<\/div>\n<\/div>\n <\/p>\n \nReview the FAQ or contact us if you need clarification about a specific LangSpector data flow or licensing operation.\n<\/p>\nLicense endpoints are rate limited.<\/h2>\n
\nPayment information is handled through Stripe Checkout.
\n<\/h2>\nCard information<\/h3>\n
Customer information<\/h3>\n
Transaction references<\/h3>\n
Your audit data and your purchase data serve different purposes.<\/h2>\n
\nQuestions about privacy or security?
\n<\/h2>\n