QueRank is installed by a merchant and operates on their store's content. Two things follow:
• We do not collect, store or process your customers' personal data. The app reads products, collections, blogs, articles and pages. It does not request, and is not granted, access to orders, customers or checkout. There is no customer record anywhere in the application database.
• The personal data we do hold belongs to the merchant and their staff — the people who install and use the app.
For data we hold about merchants we act as a controller. For store content we process on the merchant's behalf we act as a processor, with Shopify's merchant as the controller.
Audit results, issue lists, scores, generated meta titles and descriptions, image alt text, structured data, FAQ and HowTo content, tracked search queries, AI-visibility results, Search Console metrics, click-through predictions, A/B test results, and generated PDF and CSV reports.
This is store content and its derivatives. It contains whatever the merchant has published on their storefront.
Free-text fields the merchant chooses to provide — brand description, unique selling points, target audience, tone, keywords to use or avoid — used to condition AI generation. Supplied voluntarily; the app works without them.
The app requests ten permissions, and every one of them has a use. It asks for nothing covering customers, orders, checkout or themes.
Customer names, emails, addresses, phone numbers, order contents, payment details or card data. None of these exist in the application's data model, and the app does not request the Shopify scopes that would grant access to them. This holds for the privacy request webhooks too: when Shopify forwards one, we record that it arrived and what we did about it, and no customer contact details are written down.
Store content is sent to these services only as needed to perform the function the merchant asked for.
Not used. The app sends no email and has no email provider. It uses no outside file storage — generated reports and image backups stay on the server described under International transfers. There is no advertising network, no data broker, and no sale or sharing of any data for advertising purposes.
AI providers are used through their standard APIs. We do not knowingly send personal data to them; what is sent is store content — product titles, descriptions and page copy — for rewriting.
The app can send notifications to a Slack channel, a Discord channel or a webhook address of the merchant's choosing. Nothing is sent to any of them unless the merchant sets the destination up, and it stops when they remove it.
These destinations are chosen and controlled by the merchant, so they are not our subprocessors. What happens to the data after it arrives is governed by the merchant's agreement with Slack, Discord, or whoever operates the address they entered. Destination addresses are encrypted at rest.
If the merchant connects Search Console, they grant read-only access (webmasters.readonly) to the property they select.
• OAuth tokens are encrypted at rest with AES-256-GCM and are never logged, never returned to the browser, and never sent anywhere but Google.
• We read aggregate performance data — pages, queries, clicks, impressions, position. Search Console does not expose individual users, and we could not identify one if we wanted to.
• The merchant can disconnect at any time from Intelligence → Search Console, which revokes the token with Google and deletes the stored credentials.
Some data is cleared on a fixed schedule while the app is still installed:
One exception survives deletion: a compliance record noting that a privacy request arrived and what was done about it. It is kept for record-keeping, it excludes all credentials, and it holds no customer contact details.
• The Shopify Admin API token and Google OAuth tokens are encrypted at rest with AES-256-GCM using per-purpose derived keys. Tampered or wrongly-keyed ciphertext fails to decrypt rather than yielding a usable value.
• All traffic is over TLS.
• Webhooks are verified by HMAC-SHA256 signature before any handler runs; an unsigned or wrongly-signed request is rejected with a 401 and does nothing.
• Redis, which holds the background job queue, is bound to localhost and is not reachable from the internet.
• The application does not run as a privileged user.
• Secrets are never written to logs or error reports.
No system is perfectly secure. If you believe you have found a vulnerability, contact support@querank.com and we will respond.
Under GDPR, UK GDPR and similar laws, merchants may request access to, correction of, export of, or deletion of their data, may object to or restrict processing, and may withdraw consent for optional integrations by disconnecting them in the app.
Under the CCPA/CPRA, California merchants have equivalent rights. We do not sell or share personal information, so there is nothing to opt out of.
Two routes to exercise these rights:
• Uninstall the app. Shopify sends us a mandatory deletion request 48 hours later and all data is permanently deleted, automatically.
• Email support@querank.com. We respond within 30 days.
If a merchant's own customer contacts Shopify to ask what data this app holds about them, Shopify forwards the request and we respond that no customer data is stored — because none is. The same is true when Shopify asks us to erase a customer: we acknowledge the request, and there is nothing to erase, because the app keeps no record of any individual shopper.
Merchant data is stored and processed in Nuremberg, Germany, on a server rented from Hetzner Online GmbH. The database, the job queue and the application all run on that one machine, inside the EU. No merchant data is stored anywhere else.
We are an Indian company, so our staff administer that server from India.
Beyond that, data leaves the EU only when it is sent to a subprocessor listed above to do the job the merchant asked for:
• Google (Gemini, Search Console, PageSpeed Insights), OpenAI, Anthropic and PostHog are United States companies, and data sent to them is processed in the United States.
• Sentry error reports go to Sentry's European (Germany) region, so they do not leave the EU.
• DataForSEO receives a keyword and a location code, and nothing that identifies a store or a person.
Transfers out of the EEA and the UK rely on the Standard Contractual Clauses in each subprocessor's terms.
The app is a business tool sold to merchants and is not directed at anyone under 16.
Material changes will be announced in the app and by updating the date at the top. Continued use after a change constitutes acceptance.
Viharnika Enterprise LLP 11, Jagatpur Road, Ishwar Krupa Society, Chandlodia, Ahmedabad 382481, Gujarat, India support@querank.com