> For the complete documentation index, see [llms.txt](https://veloshield.gitbook.io/veloshield/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://veloshield.gitbook.io/veloshield/policy/privacy-policy.md). # PRIVACY POLICY ## Privacy Policy for VeloShield: Protect Store **Effective Date:** May 27, 2026\ **Last Updated:** May 27, 2026 VeloShield ("we", "us", or "our") operates the VeloShield: Protect Store application (the "App") for Shopify merchants. This Privacy Policy describes how we collect, use, share, and protect personal information when you install or use our App in connection with your Shopify-supported store (your "Store"). By installing and using the App, you agree to the collection and use of information in accordance with this Privacy Policy. *** ### 1. Information We Collect from Your Store When you install the App, we are automatically authorized to access certain types of information from your Shopify account via Shopify’s API. This information includes: #### a. Merchant and Store Owner Data * **Contact Information:** Name, email address, physical address, and phone number associated with your Shopify account. * **Store Parameters:** Store name, domain URL, geographic location, primary currency, and installed theme metadata (needed to deploy theme app extensions). #### b. Storefront Visitor and Activity Data (For Security Screening) To protect your store from content theft, scrapers, geo-threats, and malicious bots, our scripts monitor traffic interactions on your public theme layout. We process: * **Network & Device Technical Data:** IP addresses, approximate geographic location (country/region), browser type, user-agent details, operating system, and hardware metrics. * **Visitor Identifiers:** Unique anonymous Visitor IDs generated by browser configurations to map persistent behavior patterns. * **Storefront Interaction Event Metrics:** Triggers such as right-click context menu attempts, text selection occurrences, text copying, developer tool hotkey combinations, and competitor spy extension background signals. #### c. Store Metrics & Catalog Structure Data * **Sales Analytics Signals:** Public data parameters exposed by the storefront theme layout (such as collection best-selling sort query paths `?sort_by=best-selling`). * **Order History Logs:** Access to order structures for the trailing 60 days (processed strictly if you utilize advanced bot-checkout protection filters to detect malicious automated fraud behaviors). *** ### 2. How We Use the Information We Collect We utilize the collected metrics exclusively to render, maintain, and boost the capabilities of our protection system layers: * **To Compute Your Security Score:** Analyzing your active toggles to deliver a live threat dashboard overview rating from 0 to 100. * **To Enforce Security Rules:** Processing inbound IP structures against your active Blocklists, Whitelists, and Country Geo-blocking configurations. * **To Disrupt Malicious Actions:** Deploying frontend blocker scripts that actively shield your product descriptions, text, and images from scrapers. * **To Handle Redirect Workflows:** Instantly routing geo-restricted or blocked visitor targets to alternative landing page URLs provided by you. * **To Deliver Support:** Communicating via your review or support channel email (`claydrusilla2733@gmail.com`) regarding configurations, performance stats, or technical issues. *** ### 3. Data Retention and Deletion * **Operational Logs:** Technical diagnostic data logs containing storefront interaction patterns or blocked IP captures are automatically purged or anonymized on a regular cycle to safeguard consumer privacy. * **App Uninstallation:** When you uninstall the App from your Shopify store dashboard, Shopify immediately sends a mandatory web-hook event triggering the automated deletion of your store profile configurations within 48 hours, in accordance with Shopify data protection regulations. *** ### 4. Third-Party Data Sharing We do not sell, rent, or trade your store data or your customers’ tracking metrics to third parties. We share information only with trusted infrastructure providers strictly necessary to deliver the service: * **Hosting and Computing Infrastructure:** Encrypted cloud servers secure our databases and backend rulesets. * **Legal Compliance:** We may disclose collected metrics if required by applicable law, court orders, or state regulatory bodies to prevent fraud or security breaches. *** ### 5. Security Measures VeloShield takes the protection of your business data seriously. We apply industry-standard Secure Sockets Layer (SSL) encryption protocols, secure token-based API authentication gates, and restricted internal server accesses to protect assets against unauthorized modifications, disclosure, or theft. *** ### 6. Your Rights and Contact Information Depending on your regional legal jurisdiction (such as GDPR in the European Union or CCPA in California), you or your storefront visitors may possess rights to access, amend, or remove personal details tracked by our servers. For privacy inquiries, technical data requests, or compliance complaints, please reach out to our dedicated privacy contact team at: **Email:** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://veloshield.gitbook.io/veloshield/policy/privacy-policy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.