Privacy Policy
Last updated: 2026-10-24
This privacy policy describes how the SecureBite API Proxy app ("SecureBite", "we", "us", "our") handles data when you install and use the app on your Shopify store. We collect the minimum data required to operate the app and do not sell, share, or use it for marketing.
One-line summary: we store your shop's access token, the proxy routes you configure, your selected billing plan, and (optionally) one email address for usage notifications. We never store customer data, order data, or theme code, apart from short-lived request logs (deleted within 7 days) and, only for routes where you turn on response caching, copies of API responses that expire within 24 hours. Theme scans keep only the latest result, with every detected secret redacted.
1. Who we are
SecureBite API Proxy is operated by Webite d.o.o., located in Ljubljana, Slovenia. For any privacy questions, email support@webite.rocks.
2. What data we collect
2.1 Data from your Shopify store
- Shop domain (e.g.
your-store.myshopify.com) - used as the identifier for all stored data.
- Shopify offline access token and refresh token - granted by you during installation so the app can call the Shopify Admin API on your behalf. Used only to scan your published theme for leaked API keys and to read your active subscription. The access token expires after 60 minutes and is rotated automatically; both are deleted the moment you uninstall.
- Store email - optionally fetched from your Shopify account (via the
shop.email field) as a fallback contact address for usage notifications.
2.2 Data you provide
- Proxy route configuration - the target URLs, HTTP methods, secret headers, body templates, and validation rules you set up in the admin UI.
- Notification email (optional) - one email address you can supply to receive usage alerts. Used only for transactional notifications, never for marketing.
- Cleanup request details (Pro / Scale plans only) - if you submit a cleanup service request: your collaborator request code, any note you add, and the findings summary from the most recent theme scan.
- Support messages - if you contact us via the in-app support form or chat, the message contents and the context (shop, plan, route count) that the form attaches.
2.3 Data generated by the app
- Proxy request counts - aggregate count of storefront proxy requests per month, used to enforce your plan limit. We do not store request bodies, and we store response bodies only as described under "Cached responses".
- Cached responses - only if you turn on Cache responses for a route (Pro and Scale plans). The Worker keeps a copy of that route's successful responses for the cache time you choose (at most 24 hours) and answers repeat requests from it. When a route sends the logged-in customer's ID or email to your API, the copy is that customer's response and is tagged with their Shopify customer ID so it is only ever returned to them. Copies are deleted when they expire, when you edit or delete the route, when you uninstall the app, and for one customer when Shopify sends
customers/redact.
- Request logs - Cloudflare keeps a short-lived technical log of each request to the app, used only to troubleshoot and investigate security issues. For storefront proxy requests this includes the request URL, which can contain the logged-in customer's Shopify customer ID and any query parameters the storefront sends, and may include the visitor's IP address. Logs are deleted automatically after at most 7 days and are not used for any other purpose.
- Store overview - your store's name and URL, and install, uninstall and billing history from Shopify's Partner reporting (including any uninstall reason you give Shopify), used only for our internal list of stores using the app.
- Theme scan results cache - the most recent scan summary (file paths, pattern names, line numbers, redacted previews of detected secrets) so you can revisit findings without re-running the scan. Raw secret strings are never stored.
- Selected billing plan - the plan handle Shopify reported on the last subscription callback.
3. What data we do NOT collect
- We do not store any of your customers' personal data, names, emails, addresses, or order details, other than the short-lived request logs described in 2.3 and cached responses for routes where you turn on caching (2.3). The one exception is processing, not storage: if you configure a route with the
{{logged_in_customer_email}} variable, the Worker reads the logged-in customer's email from Shopify to pass it to your target API, holding it only in memory for up to 5 minutes. With the {{klaviyo_profile_id}} variable, the Worker also sends that email to Klaviyo, using the Klaviyo key you entered on the route, to find the customer's Klaviyo profile ID, and holds the ID in memory for up to 5 minutes. Neither is ever written to disk, KV or logs.
- We do not store the actual contents of your theme files - only the redacted summary of any secrets found during a scan.
- We do not store the secret credentials (API keys, tokens) configured in your proxy routes any longer than necessary to handle live requests. They live in Cloudflare KV for the lifetime of the route configuration so the Worker can inject them on each storefront call.
- We do not use cookies, tracking pixels, fingerprinting, or third-party analytics inside the embedded admin UI.
- We do not sell, rent, or share any data with third parties for marketing.
4. Where data is stored
- Cloudflare Workers + Cloudflare KV (US / EU edge), with per-shop isolation.
- Cloudflare Durable Objects for monthly request counters.
- Resend (for delivering transactional emails like usage alerts and cleanup notifications).
- Tawk.to (only for paid-plan merchants who use the live chat widget; loaded client-side).
5. Sub-processors
We use the following third-party services to operate the app:
- Cloudflare - hosting (Workers, KV, Durable Objects). privacy policy
- Resend - transactional email delivery. privacy policy
- Tawk.to - live chat widget (paid plans only, loaded only when the merchant opens the chat). privacy policy
- Shopify - billing and authentication. privacy policy
6. How long we keep data
- When you uninstall the app (Shopify's
app/uninstalled webhook) we immediately delete your access tokens, routes and their credentials, notification email, plan cache, scan results, cleanup requests and notification reminders.
- When Shopify sends the
shop/redact webhook (typically 48 hours after uninstall) we delete everything else tied to your shop: monthly request counts and your store's name and URL. Request counts are kept until then so that reinstalling doesn't reset the month's request limit.
- If we granted your store a free plan, that record (store domain, plan and an internal note) is kept after uninstall so the free plan still applies if you reinstall. Email us to have it removed.
- Short-lived markers expire on their own: the support-form rate limit after 60 seconds, used single-use tokens after 2 minutes, and the usage-limit email reminder schedule after at most 100 days.
- Request logs are deleted automatically after at most 7 days.
- Cached responses expire after the route's cache time (at most 24 hours), and are deleted earlier when you edit or delete the route or uninstall the app.
7. GDPR / data subject rights
The app responds to Shopify's mandatory GDPR webhooks:
customers/data_request - no customer data to return: the only customer data we may hold is cached responses, which expire within 24 hours, long before a data request is due.
customers/redact - deletes every cached response tagged with that customer's ID.
shop/redact - all shop-specific data we hold is deleted.
If you have concerns or want confirmation that your data has been purged, email support@webite.rocks.
8. Security
- All traffic to and from the app is HTTPS only.
- Shopify App Proxy requests are verified by HMAC signature on every call.
- Secret headers and API keys you configure are stored in Cloudflare KV and injected by the Worker server-side - they never appear in storefront page source.
- Cloudflare environment secrets (Shopify API secret, Resend API key) are stored in Cloudflare's encrypted secret store, accessible only to the Worker.
9. Changes to this policy
If we materially change how we handle data, we'll update the date at the top of this page and notify active merchants by email before the change takes effect.
10. Contact
For any privacy questions, data access requests, or concerns, email support@webite.rocks.