How we handle your enquiry.

The enquiry form sends your details over HTTPS to Selectika’s website, which passes them to its configured email service for delivery to [email protected]. An acceptance message confirms that the service accepted the request; it does not confirm inbox delivery. Contact information and message content may be retained in Selectika’s mailbox and configured mail-service logs. The form does not store your message in browser storage.

AskLily chat and email handoff

Lily uses recent chat messages to answer in context. Relevant conversation text and retrieved public material are sent to OpenAI to generate answers under the applicable service policies. Chat messages stay in the current browser conversation. Only after you approve an email handoff, we store an encrypted snapshot so the approved recipients can read it. Access expires after 30 days; expired records are removed by automatic cleanup. This archive is not used as memory for other chats. If you choose email handoff, review the request and your reply address before you approve sending. The email includes the request, a short summary and a protected link to a fixed copy of the current conversation up to draft preparation. Only the approved recipients can read it after signing in with ChatGPT. Lily shows the complete email draft for your approval before sending. You can edit or cancel it. Tali and an authorized Selectika team member may review the request and conversation you choose to share to respond and improve Lily. When email delivery is enabled, the server uses Gmail’s send-only permission to send the approved message from Lily’s dedicated mailbox to Selectika. This connection does not grant access to read email in Lily’s mailbox. The approved request, summary, reply address and protected conversation link are included in the email and may remain in the sender’s and recipient’s mailboxes. Please leave sensitive information out of the chat and any email draft.

A separate email link lets you contact us using your own email application. WhatsApp and social links take you to their respective services, which apply their own terms and privacy practices.

This website uses the existing Selectika Google Analytics and HubSpot services to understand website use and support customer engagement. These services may use cookies and similar technologies. Contact-link clicks can be recorded as events; form contents are not included in those analytics events. Enquiries are handled by the configured server mail service as described above. Hosting access and operational logs are managed by the hosting provider. Fonts are requested from Google Fonts. See Google’s privacy policy and HubSpot’s privacy policy for their practices. The Shop the Look video is served with this website and loads when played. The AI Outfitting demonstration runs locally with curated sample products; selections and the sample bag stay in the page and are cleared when it reloads. Product links open the retailer website. Both search experiences run in your browser. The fashion demo filters a small local sample; website search loads a static index of this website. No query is sent to an AI service. Website search places your query in the page URL, so it can appear in browser history and hosting logs when that URL is loaded. Your theme preference is stored in this browser and can be changed using the Theme control. The website also loads Selectika’s existing analytics script from collect.selectika.com.

For questions about Selectika’s processing of enquiries or platform data, contact [email protected]. Platform retention and contractual data terms should be confirmed with the company.

Connected stores and the Selectika WooCommerce service

This section describes the Selectika WooCommerce integration, including the 1.1 connection model. The store operator chooses which capabilities to enable and is responsible for the notices and consent choices on its store.

Catalogue and product descriptions

When the catalogue connection is enabled, Selectika retrieves product and variation identifiers, SKUs, titles, descriptions, product links, image URLs, categories, attributes, prices, currency and stock availability from the store. These records support catalogue enrichment and the configured shopping features. The catalogue export does not include customer or order records. A separate description-only connection uses authenticated WooCommerce REST API access to read and update the selected product description field. Draft descriptions remain in Selectika until the configured publication workflow approves them.

Widgets and shopping events

After the store operator enables the service and the visitor grants the consent required by the plugin, browser requests can load Selectika scripts and product recommendations from Selectika services. Enabled tracking records page and product views, cart additions and removals, cart views, checkout starts and purchases. Event data can include product identifiers, quantities, prices, currency, order identifiers, timestamps and pseudonymous browser or session identifiers. Browser requests also expose ordinary connection information, such as IP address and user agent, to the services receiving them. The plugin does not intentionally include customer names, email addresses, postal addresses, payment details or order notes in its event payloads.

For the full integration, scripts are served from scripts.selectika.com and statics.selectika.com; retailer configuration and signed order events use retailers.selectika.com; product features use Selectika API services such as ask.selectika.com; and tracking uses data.selectika.com. The plugin stores its consent choice in a first-party cookie and keeps a bounded list of event identifiers in session storage to reduce duplicate browser events. The Selectika pixel may use additional pseudonymous browser and session storage for measurement. Withdrawing consent stops new plugin tracking and reloads the page to unload already-running remote scripts. The visitor can also clear site data in the browser.

Server order events and retention

If the operator enables server order delivery, the plugin sends signed payment, cancellation and refund events for orders with recorded analytics consent. These contain store and order identifiers, product lines, quantities, amounts, currency and event times, rather than customer contact or payment credentials. The plugin can temporarily queue undelivered events in the store database and retry them. Selectika's native WooCommerce event ledger has a 90-day expiry policy. This is not a retention promise for every catalogue record, aggregate report, backup or hosting log; those are governed by the applicable customer agreement and operating requirements. Contact Selectika to confirm the terms for your deployment or request assistance with access or deletion.

Disabling a capability or revoking its credentials stops the corresponding future connection. Deactivating or deleting the plugin does not by itself erase data already delivered to Selectika. Store operators and visitors can contact [email protected] about this processing; visitors should also contact the store where they shopped.

Selectika integration service usage terms

The WordPress plugin connects a store to the separately provided Selectika service. A configured Selectika retailer account and any applicable commercial service agreement are required for connected features. Installing the GPL-licensed plugin does not create a paid subscription, grant access to another retailer's data or replace the terms agreed between the store operator and Selectika.

Only an authorised store administrator should connect a store, grant API permissions or enable catalogue, widget and analytics capabilities. The operator must be entitled to provide the connected catalogue and event data and must configure the notices and consent controls appropriate to its store. Keep connection credentials private and revoke them when access is no longer required. WooCommerce native Read/Write keys grant broader product permissions than descriptions alone, even though Selectika's description update sends only the selected description field.

Review generated product content before publication when your workflow requires approval. Available features depend on the configured service, supported WooCommerce product types and the store environment. Disconnecting the plugin stops its future connections; cancellation of a separate Selectika service agreement and deletion of previously received data should be arranged with Selectika under that agreement. For account access, support, contractual terms or data requests, contact [email protected].