Effective date: October 24, 2026
1. What SmartFix does
SmartFix is a browser extension that checks and corrects writing in supported editable fields on websites. To work, its content scripts can access text in those fields while you type or paste. That access is used to provide writing corrections.
2. Text processed for corrections
SmartFix's packaged correction engine analyzes text in your browser to identify potential spelling, typing, grammar, punctuation, and capitalization errors. SmartFix is designed to perform writing corrections locally. Website text does not need to be sent to the SmartFix licensing service for correction.
Important: SmartFix can encounter sensitive text if you type it into a supported field. Avoid using any writing extension with sensitive content unless you are comfortable with its access. A local correction operation is distinct from transmitting text to a server.
3. Extension settings and usage
SmartFix uses browser storage to retain settings, feature preferences, correction-use counters, and licensing-related state so the extension can work across browser sessions. Depending on browser settings, some stored values may persist until reset or removal.
4. Licensing and device activation
SmartFix communicates with a Cloudflare-hosted licensing service over HTTPS to verify eligibility for the free allowance and paid activation. Licensing may involve an extension-generated device identifier or public key, license or activation identifiers, usage/entitlement status, and related security information. These records are used to prevent duplicate or unauthorized activation, restore purchases where supported, and administer the one-device licensing policy.
5. Purchases and payment provider
If paid checkout becomes available, the checkout flow may direct you to Stripe, an independent payment processor. Stripe processes the payment details you submit to it under its own privacy practices. SmartFix's licensing service may receive transaction references and payment status needed to activate a license. SmartFix does not need your complete payment-card number to issue a license.
6. Service providers and technical records
Cloudflare provides hosting and infrastructure for SmartFix's license verification service. Stripe is the intended checkout provider for purchases when payments are enabled. Infrastructure services may process technical request metadata such as IP addresses and timestamps as part of normal delivery and security operations. The precise retention of such records depends on enabled service settings and provider policies.
7. How information is used and shared
Information used by SmartFix is intended to support text correction, user preferences, free-usage enforcement, paid activation, purchase restoration, support, and service security. SmartFix does not require selling writing content to advertisers to operate. Information may be processed by the service providers identified above for those purposes or disclosed if legally required.
8. Data retention and deletion
You can remove locally stored extension data using your browser's extension and site-data controls. Removing the extension may not automatically delete server-side license records or payment records. Some records may need to be retained for purchase validation, fraud prevention, legal obligations, or support. To ask about server-side data or deletion, use the developer contact mechanism on SmartFix's Chrome Web Store listing.
9. Security
SmartFix's licensing communications are intended to use HTTPS, and its packaged browser-side correction logic runs within the browser extension environment. No internet-connected system can promise absolute security.
10. Changes and contact
SmartFix may update this policy when its functionality, service providers, or data practices change. Changes requiring additional notice or consent will be handled as applicable. For questions or privacy requests, contact the developer using the contact information provided in the official SmartFix Chrome Web Store listing.
Publisher review required: This policy describes the known product architecture; before public release, the developer must verify the deployed extension and backend against these statements, including text transmission, logging, activation fields, Stripe mode, retention, and a working privacy contact channel.