Clear data practices for faster search.

1. Scope

This policy applies to the Fast Search application, its merchant dashboard, and the Fast Search storefront service. The merchant remains responsible for its own storefront privacy notice and its use of shopper data.

Fast Search does not process orders, payment details, shipping addresses, customer accounts, or customer lists.

2. Data we process

Store connection and administration

• Store ID, preferred language, and app installation or subscription status.
• A commerce-platform API access token, encrypted before database storage, and a public token when the platform supplies one.
• Search display settings and merchant-created synonym or spelling rules.
• Webhook event identifiers, types, and processing timestamps used to safely synchronize catalog changes.
• A searchable copy of public storefront catalog fields, including product and category IDs, names, descriptions, SKU, formatted price, stock status, visible options and attributes, image URLs, and storefront URLs. This copy is built automatically when the merchant first opens the app and is maintained through catalog-change notifications and periodic refreshes.

Search Intelligence

When enabled, Fast Search stores normalized search phrases in hourly aggregate rows with search counts, no-result counts, result totals, and the most recent search time. It does not create an individual database record for every search.

Email-like search phrases are rejected from Search Intelligence. Merchants should still avoid asking shoppers to enter personal or confidential information in a product-search field.

Internal diagnostics

The current service does not record new server or browser performance aggregates. Earlier versions stored hourly timing and request totals, which are removed after 31 days. During internal catalog checks, Fast Search may also store hourly totals that compare indexed search results with platform API results. These comparison totals are removed after 31 days and do not contain search phrases, visitor identifiers, IP addresses, or access tokens.

Rate limiting and operational records

A random anonymous identifier is generated in the shopper's browser session for abuse prevention. Fast Search does not place this identifier, shopper IP addresses, or shopper identities in its application database or custom application logs.

Custom operational logs may contain a store ID, event type, response counts, timing information, and error details. They intentionally omit full search phrases, access tokens, and anonymous visitor identifiers. Cloudflare may process connection and request metadata while delivering and protecting the service.

Support communications

If you contact support, we receive your email address and the information you include in your message. Support email is not added to the Fast Search application database.

3. How data is used

• Provide live product and category search for the correct store.
• Apply each merchant's display settings, synonyms, and spelling corrections.
• Show merchants aggregated demand and no-result Search Intelligence.
• Build, synchronize, and validate the searchable copy of public storefront catalog data.
• Secure the service, limit abuse, diagnose errors, and maintain reliability.
• Respond to support, privacy, and deletion requests.

4. Service providers

Fast Search uses a limited set of providers to operate:

• Lightspeed eCom supplies the app installation, storefront integration, and catalog API. Search phrases may be sent to Lightspeed eCom to retrieve or compare matching public catalog results.
• Cloudflare hosts the Worker, database, Queues, short-lived cache, rate limiting, and operational logs.
• Google Gmail processes communications sent to the support address.

These providers process data under their own terms and privacy practices. Data may be processed where they operate. We may also disclose information when required by applicable law or a valid legal process.

5. Retention and deletion

• Search Intelligence aggregate rows are automatically removed after 31 days.
• Existing search performance aggregate rows are automatically removed after 31 days.
• Catalog-index comparison aggregate rows are automatically removed after 31 days.
• Store tokens, settings, rules, public catalog-index rows, and active webhook history are retained while Fast Search remains installed.
• Public catalog search responses may remain in Cloudflare's cache for up to five minutes. Public storefront configuration may be cached for up to 60 seconds.
• Custom Workers logs follow Cloudflare's plan retention, currently up to three days on the Workers Free plan and up to seven days on the Workers Paid plan.
• Cloudflare D1 Time Travel disaster-recovery history may remain available for up to seven days on the Workers Free plan or 30 days on the Workers Paid plan.
• Support communications are retained only as reasonably needed to answer the request, maintain support records, and meet legal obligations.

6. Security

Fast Search uses HTTPS, AES-GCM encryption for access tokens at rest, short-lived signed dashboard sessions, HMAC verification for platform webhooks, bounded inputs, tenant-scoped database queries, and per-store and per-visitor rate limits.

Access tokens are decrypted only in Worker memory when needed for a commerce-platform API request and are never returned to the merchant dashboard or storefront browser. No internet service can guarantee absolute security, but Fast Search is designed to minimize both the amount and lifetime of retained data.

7. Your choices

Merchants can disable Fast Search live results from the app settings without uninstalling. Native product search remains available. Uninstalling Fast Search from the store control panel automatically initiates deletion of the store's active application data.

To request access, correction, or deletion, email support and include your store ID and the nature of your request. We may ask you to verify that you control the store before acting. Rights vary by location and applicable law.

8. Contact and policy changes

Fast Search is developed and operated by Rakesh Shishodia. Questions about this policy, support, or data deletion can be sent to:

This policy may be updated as Fast Search changes or legal requirements evolve. The effective date at the top of this page will be revised when the policy changes materially.