Commerce search with clear data boundaries.
FlatSearch.Pro is designed to improve WooCommerce product discovery while keeping core storefront search inside the merchant’s WordPress commerce environment.
This policy explains how FlatSearch.Pro, WHISKY SDN BHD, Freemius, optional cache providers and support workflows may process data.
The short version.
The details below control if there is any difference between this summary and the full policy.
Search belongs to the store
Core FlatSearch.Pro storefront search is designed to operate within the merchant’s WordPress and WooCommerce environment.
Freemius handles purchases
Freemius processes checkout, subscriptions, licensing and related customer account information.
Caching is configurable
Browser storage, persistent object cache and Cloudflare may process search data when those features are enabled.
Support data is supplied deliberately
Debug Reports, HAR captures and screenshots are normally received only when a customer chooses to send them for troubleshooting.
FlatSearch.Pro business information.
This policy covers information processed by WHISKY SDN BHD in connection with FlatSearch.Pro, flatsearchpro.com, licensing and support.
It does not replace the privacy policy that a merchant must provide to shoppers using its own WooCommerce store.
Your store and FlatSearch.Pro have different privacy responsibilities.
This distinction is particularly important for search analytics, browser storage and shared caching.
WooCommerce shopper data
A merchant operating FlatSearch.Pro controls how the plugin is configured on its store and is generally responsible for informing shoppers about data processed through that store.
- Search analytics settings
- Recent-search features
- Browser/local storage disclosures
- Cookie consent where required
- Cloudflare/CDN configuration
- Store-specific retention policies
Customer, license & support data
WHISKY SDN BHD is responsible for data it directly receives through FlatSearch.Pro sales, support, business communications and related services.
- Support correspondence
- Files deliberately supplied to support
- Sales enquiries
- Business/contact records
- Information received through licensing integrations
What information may be involved.
Not every category applies to every user or store configuration.
| Category | Examples | Purpose | Typical location / processor |
|---|---|---|---|
| Purchase & billing data | Name, email, billing information, order, subscription, payment status, tax and invoice information. | Checkout, subscription, invoice, refund and account administration. | Freemius / payment providers |
| License & activation data | License information, site URL, activation status, plugin version and relevant environment information. | License activation, validation, updates, compatibility and support. | Freemius / licensing services |
| WooCommerce catalogue data | Product titles, IDs, prices, product URLs, stock context, images, categories and other searchable product information. | Build and operate FlatSearch.Pro search. | Merchant WordPress / WooCommerce site |
| Shopper search data | Search query, result set, result count, clicked result or related analytics where enabled. | Return search results and optionally help the merchant understand search demand. | Merchant environment |
| Browser search data | Cached result data, recent queries or related local search state where enabled. | Improve repeat-query performance and user experience. | Visitor browser |
| Shared / edge cache data | Public query URL, request metadata, cache headers and public search response. | Reduce repeated origin work. | Optional cache / CDN provider |
| Support data | Email, support message, screenshot, Debug Report, HAR capture, exact query, URLs and technical environment details. | Diagnose bugs, performance, compatibility, image and licensing problems. | FlatSearch.Pro support systems |
| Website enquiry data | Name, email, website/company information and submitted message. | Respond to sales, support and business enquiries. | FlatSearch.Pro website / communication services |
Core commerce search stays close to the WooCommerce store.
Optional infrastructure can accelerate the same public search flow without changing who operates the underlying store.
Visitor Browser
Sends the shopper’s product query and may reuse appropriate local search data.
Shared / Edge Cache
Optional infrastructure may reuse valid public search responses.
FlatSearch Fast Index
Searches prepared WooCommerce catalogue information on the merchant’s infrastructure.
WooCommerce
Remains the merchant’s source for product, image, price and commerce data.
What major FlatSearch.Pro features use.
| Feature | Data involved | Primary purpose | Privacy consideration |
|---|---|---|---|
| Fast Index Engine | Searchable WooCommerce catalogue information. | Provide efficient origin search. | Primarily merchant product/catalogue data. |
| Universal Search Form / Icon | Shopper query and public result data. | Provide FlatSearch.Pro’s theme-independent WooCommerce search interface. | Same privacy principles apply regardless of theme. |
| Browser Quick Search / repeat reuse | Appropriate recent search/result state in the browser. | Reduce repeat search work. | Merchant should disclose local storage where legally required. |
| Cloudflare Fast Search | Public query requests, response data and network/cache metadata. | Reuse public search results at the edge. | Shared caching should not be used for private or customer-specific content. |
| Redis / Object Cache | Search cache objects and related server-side data. | Reduce repeated server processing. | Stored within infrastructure selected by the merchant/host. |
| Popular / Recent Searches | Search terms. | Provide useful discovery suggestions. | Do not expose private or identifying queries as public suggestions. |
| Search Analytics | Search terms, result counts and related search interactions where configured. | Help merchant understand search demand and discovery gaps. | Merchant should disclose analytics use where required. |
| Guided Answer Search | Merchant-created answers, aliases and associated WooCommerce products. | Provide controlled commerce guidance. | Content is configured by the merchant. |
| Quick Add | Product/cart interaction generated by shopper action. | Add eligible products to WooCommerce cart. | WooCommerce cart/privacy behavior remains governed by the merchant’s store. |
| Debug Report | Plugin version, modules, cache state and technical environment information. | Diagnose FlatSearch.Pro problems. | Review before sending and remove unrelated sensitive information. |
Faster search can involve several temporary storage layers.
Each layer is controlled by the merchant’s configuration and infrastructure.
Browser storage
FlatSearch.Pro may use browser-side search state or cached query results where the relevant feature is enabled.
Persistent object cache
Redis, Object Cache Pro or another persistent cache may temporarily hold appropriate search cache data when configured by the merchant.
Cloudflare / CDN
Valid public search responses may be cached or processed by Cloudflare or another CDN where the merchant enables that infrastructure.
Checkout and licensing are provided through Freemius.
FlatSearch.Pro uses Freemius for commercial checkout, licensing, subscriptions and related customer-account functions.
- Trial and purchase processing
- Billing and payment status
- Subscription administration
- License activation and validation
- Invoices and refunds
- Related customer-account functions
Information processed by Freemius
Depending on the transaction and license workflow, Freemius may process customer identity, email, billing, transaction, subscription, license, site and relevant technical information.
Support files can contain more information than expected.
When troubleshooting search performance or compatibility, customers may choose to provide diagnostic material.
- FlatSearch.Pro Debug Report
- HAR / browser network capture
- Screenshots
- Product or page URLs
- Exact search queries
- Relevant WordPress environment information
Do not send unnecessary secrets.
- WordPress passwords
- Database credentials
- API secret keys
- Payment-card information
- Private customer records
- Identity documents
Why information is processed.
Sell & license
Process trials, purchases, subscriptions, invoices, refunds and license activation.
Operate search
Build Fast Index data, return product results and support configured browser/server/cache functionality.
Provide support
Investigate search, caching, image, compatibility, licensing and performance issues.
Improve the product
Understand defects, compatibility patterns and support issues using appropriate diagnostic information.
Protect the service
Validate licensing, prevent abuse, investigate security problems and protect company rights.
Communicate
Respond to support and business enquiries and send service or marketing communications where permitted.
Service messages and marketing are different.
Some communications are necessary to provide the purchased service, while promotional communications are subject to applicable marketing and consent rules.
Operational emails
Examples include billing, license, subscription, security and support messages needed to provide the service.
Promotional emails
Newsletters, offers and promotional messages are sent only where permitted under applicable law and available consent/preferences.
Different information requires different retention.
Purchases & licenses
Commercial records may be retained as necessary for account administration, tax, accounting, fraud prevention, contractual and legal requirements.
Diagnostic records
Support correspondence and submitted files may be retained while an issue is investigated and for a reasonable period afterward.
Search analytics
Search-history and analytics retention primarily depends on the merchant’s FlatSearch.Pro, WordPress and infrastructure settings.
You may have rights over your personal data.
The rights available depend on your jurisdiction and the type of information involved.
- Request access to relevant personal data.
- Request correction of inaccurate information.
- Request deletion where applicable.
- Object to or restrict certain processing where applicable.
- Withdraw consent where processing depends on consent.
- Opt out of marketing communications.
Contact us
Email: help@flatsearchpro.com
Subject: Privacy Request
Freemius-controlled billing, checkout or license-account information may also require use of Freemius customer tools or Freemius support.
Other important privacy considerations.
Children’s privacy
FlatSearch.Pro is a business software product intended for merchants, agencies and website operators. It is not directed to children.
International processing
Service providers such as Freemius, hosting, email or infrastructure providers may process information in jurisdictions different from your own.
Legal basis
Depending on applicable law, processing may rely on contract, legitimate interests, consent, legal obligation, fraud prevention or security requirements.
Common questions about FlatSearch.Pro data.
Does FlatSearch.Pro centrally collect every shopper search?
Core storefront search is designed to operate within the merchant’s WordPress/WooCommerce environment and configured infrastructure.
A merchant may separately enable analytics, browser storage or third-party cache/CDN services that process search information.
Does FlatSearch.Pro collect WooCommerce shopper payment-card data?
FlatSearch.Pro is a search product and does not need shopper payment-card information to perform product search.
WooCommerce checkout and payment information is handled by the merchant’s own WooCommerce/payment stack.
Does Freemius process FlatSearch.Pro purchases?
Yes. Freemius provides commercial checkout, subscription and licensing services for FlatSearch.Pro and therefore processes information necessary for those functions.
Can search terms be stored?
Yes, depending on merchant configuration.
Search analytics, recent-search functionality, browser reuse, server cache or CDN cache can involve processing or temporary storage of search-query information.
Are search queries personal data?
A normal product query such as a brand name is not necessarily personal information.
A query can become personal data if a shopper types names, email addresses, account details or other identifying information into the search field.
Does Cloudflare Fast Search cache customer-specific data?
FlatSearch.Pro’s shared search-cache architecture is intended for suitable public search responses.
Merchants should not intentionally configure shared public caching for private, sensitive or customer-specific search data without independently validating the privacy and cache behavior.
What is stored in the Fast Index?
Fast Index primarily uses searchable information derived from the merchant’s own WooCommerce catalogue so products can be retrieved efficiently.
Does using the universal search form change the privacy model?
No. The universal search form changes how FlatSearch.Pro is presented by the theme; it does not turn the search engine into a separate hosted shopper-data service.
What should I remove before sending a HAR file?
Review the capture and remove or redact unnecessary passwords, authentication headers, cookies, private customer data, API secrets, payment information and unrelated sensitive information before sending it whenever possible.
Who is responsible for my store’s shopper privacy policy?
The merchant operating the WooCommerce store is responsible for its own shopper-facing privacy disclosures and compliance obligations.
FlatSearch.Pro provides search technology but does not replace the merchant’s legal/privacy responsibilities.
Who do I contact about FlatSearch.Pro privacy?
Email help@flatsearchpro.com with the subject Privacy Request .
This policy may change as FlatSearch.Pro evolves.
We may update this policy when the plugin architecture, integrations, Freemius configuration, analytics functionality, support workflow, service providers, law or business information changes.
Material updates will be reflected by changing the “Last updated” date shown on this page.
Search infrastructure should have understandable data boundaries.
FlatSearch.Pro keeps the core commerce-search workload close to the WooCommerce store while clearly separating optional caching, commercial licensing and support-data workflows.