Privacy Policy

Who is responsible

The Marketgrid operator (legal entity awaiting confirmation) is responsible for the Marketgrid service described here. Contact the privacy contact form or use the contact form for privacy enquiries. The operating entity, address and dedicated privacy contact are awaiting confirmation in this draft.

Information you give us

Trial and contact requests can include your name, email address, business name, store website, platform, selected contact region and message. We also record the request status, consent time and plan details offered when the enquiry was made. These requests are stored in our database for manual handling; submitting the form does not itself send an email or enroll you in marketing.

A connected retailer account includes its store identity, website, owner-account reference, connection information, selected public catalogue details, guide draft and published snapshot, trial dates, subscription status and monthly generation count. Keep customer personal data out of catalogue and design fields.

Shopper answers and browser storage

In the current embedded Buying Guide widget, answers are processed in the open browser session. That widget does not send a shopper answer history or order record to Marketgrid. It loads the published guide and requests current product information from the retailer as needed.

On Marketgrid’s public shopping pages, the current guide uses browser-held answers and requests product options using the selected category, store, language, country and currency. Saved products, comparisons, theme and language settings may be kept in your browser’s local storage. Clearing site storage removes those local preferences; it does not delete merchant records on our servers.

Account and enquiry workflows use ordinary session and security cookies where needed. Hosting infrastructure may log request information such as IP address, browser information, requested URL and time. Third-party fonts and product images can cause your browser to contact their providers. The retailer’s own website may separately use its own cookies, analytics and customer-account systems.

Why we use information

We use the information to respond to enquiries, connect the correct store, create and host guides, verify subscription access, administer trials and generation allowances, handle cancellations or refunds, prevent abuse and maintain the service.

Depending on the applicable law, processing may be needed to take steps you request before a contract, perform a subscription contract, meet legal obligations, or pursue legitimate interests in running and securing the service. Where a use requires consent, it must be requested separately and can be withdrawn for future processing. We do not treat a trial enquiry as consent to unrelated marketing.

Automatic drafting with OpenAI

When a retailer requests automatic drafting, product names, descriptions, attributes, catalogue-derived options, the brand, design brief, graphic labels and requested language are sent to OpenAI. Wording-only updates send question and answer text. The current drafting request excludes shopper answers and payment-card data.

The integration requests store=false for model responses. This is not a promise of zero retention by the provider: OpenAI’s separate service, abuse-monitoring and legal-retention rules still apply. Review OpenAI’s data controls at https://developers.openai.com/api/docs/guides/your-data.

Payments and other service providers

Where Stripe checkout is enabled, you provide payment details to Stripe. Marketgrid receives the identifiers and payment or subscription status needed to administer your plan; the integration should not store your full card number or security code. Stripe’s own privacy policy explains its payment, fraud-prevention and regulatory processing: https://stripe.com/privacy.

Shopify and WooCommerce provide connection or subscription information for their integrations. Hosting and other infrastructure providers process data needed to serve the website. Retailers and affiliate destinations receive information when you visit their sites and apply their own notices. We may disclose information where required by law or necessary to address security abuse.

Storage, retention and deletion

Merchant records are kept while needed to operate the connected service and administer support, billing and legal obligations. Enquiries and operational records are kept according to their purpose and the applicable legal requirements. A fixed automated deletion schedule is not implemented in the reviewed version; deletion requests are handled manually.

Uninstalling the Shopify app disables its guides. A verified Shopify shop-erasure event removes that shop record and associated guide records. Removing the WooCommerce plugin removes its local settings; it does not by itself delete server-side Marketgrid merchant records. Contact us to request deletion or disconnection of retained records. Copies in provider systems and backups may follow separate retention processes.

International processing

Your information may be processed by the operator and its service providers in countries other than your own. The final policy must identify the operator’s hosting locations and applicable transfer arrangements before commercial launch. Selecting India, the USA, Hong Kong, the UAE or Malaysia in a contact form does not promise local data storage.

Your choices and requests

Depending on your location and applicable law, you may be able to ask for access, correction, deletion, restriction or transfer of personal information, object to certain processing, or withdraw consent. Use the contact form or the confirmed privacy address, tell us what you need and provide enough information for us to locate the relevant account. We may need to verify your identity without asking for more information than necessary.

You may also complain to the relevant privacy regulator where that right applies. The final policy should name the appropriate regulator after the operating entity and target jurisdictions are confirmed. The service is intended for adult business users and general shopping guidance; do not submit children’s personal information.

Anonymous guide journeys and credit accounting

For credit-based retailer guides, a random journey token is saved in the shopper’s session storage so reopening or retrying the same journey does not charge twice. Marketgrid stores anonymous selected option indices, recommendation counts and product clicks for up to 30 days, then scheduled cleanup removes the journey records. We do not request a shopper name, email or checkout details for this purpose. Subscription, consent, payment and credit ledgers are retained separately for billing, fraud prevention and applicable record-keeping obligations.