Privacy Policy

Section 01

Information We Collect

We collect data to perform the functions of our Visual Commerce Operating System.

• Data from Commerce Platforms: If you connect a store (e.g., Shopify, WooCommerce), we access your product catalog (Titles, Images, Descriptions) via the platform's API subject to their specific data permissions.
• Direct Uploads: If you use Epox via the web without a connected store, we collect the files you manually upload.
• User Info: We collect Name, email, phone, Store URL (if applicable), and billing information. Please note that full payment details (such as credit card numbers) are collected and processed directly by our authorized third-party payment processors and Merchants of Record (e.g., Tranzila, Lemon Squeezy), and are not stored on Epox's servers.

Marketing Website Analytics & Campaign Attribution

On the production marketing website, we use PostHog to measure page visits, clicks on links to the Epox app, submitted product URL hostnames (not full product URLs), and page-performance metrics. Click events include the page, section, button label and identifier, destination path, and recognized plan, billing cycle, or tool choices. This helps us understand site performance and which entry points visitors use. Page events also include standard browser and request context, such as the marketing page URL and browser or device information.

The website's PostHog configuration uses an anonymous identifier held in memory, without identifying visitors to their Epox accounts. It does not enable session recording or automatic capture of every interaction, and does not store its identifier in cookies, localStorage, or sessionStorage. Full page loads create a new anonymous identifier; client-side page navigation can retain it. We do not automatically share that identifier with the Epox app.

Separately, the website stores incoming campaign parameters, advertising click identifiers (gclid and fbclid), referral codes, and the referring hostname in sessionStorage for the current browser-tab session when storage is available. These values are passed to Epox app links to preserve campaign attribution. This storage is separate from PostHog's in-memory identifier.

Section 02

How We Process Your Data

2.1 The Workflow

• Ingestion: We sync or upload your raw product photos.
• Processing: Assets are processed through our AI engine to generate Lifestyle Images and Videos.
• Storage: We store generated assets in our secure cloud storage to allow you to access your history and library.
• Delivery: Optimized versions are downloaded or pushed back to your store.

2.2 Use of Third-Party AI Sub-Processors

We utilize industry-leading third-party AI APIs (primarily Google Gemini via Google Cloud Vertex AI) to perform generation tasks. We only send the specific data points required for the generation task to these providers.

Epox maintains a current list of all third-party sub-processors utilized for the Service. By using the Service, you grant general authorization for Epox to engage these sub-processors. Epox will provide merchants with commercially reasonable notice (e.g., via email or dashboard notification) of any intended changes concerning the addition or replacement of AI sub-processors, giving you the opportunity to object to such changes by terminating your subscription.

2.3 AI Training & IP Protection (Your "Paid Tier" Guarantee)

Your Data Remains Yours. Epox utilizes the Enterprise/Paid tier of our AI partners.

• No Training on Merchant Data: Consistent with the data privacy commitments of our Enterprise AI partners (including Google Cloud), Epox does not use your proprietary product images or Input Data to train the foundation models of our third-party AI providers.
• Isolation: Your brand assets are processed in isolated instances. Your data is used strictly to generate your requested assets and is not shared with other merchants.

Section 03

Data Retention

• Asset Library: We retain your assets in our Cloud Storage as long as your subscription is active.
• Security: Assets are stored using enterprise-grade encryption (AES-256).

Section 04

Platform Compliance & Data Rights (GDPR/CCPA)

We respect your rights under GDPR and CCPA. The method of data deletion depends on your platform:

4.1 For Shopify Merchants (Mandatory Webhooks)

We strictly adhere to Shopify's API mandates regarding data retention. We process the following mandatory webhooks:

• customers/data_request: If a customer requests their data, we will provide any data we hold regarding that customer to Shopify.
• customers/redact: If a customer requests deletion, we will purge their personal information within 30 days.
• shop/redact (App Uninstall): If you uninstall the Epox App from your Shopify store, we receive this webhook and will permanently delete all your store data and generated assets within 48 hours.

4.2 For Non-Shopify Merchants (WooCommerce/Web)

• Right to be Forgotten: To request the deletion of your account and all associated data, email privacy@epox.ai.
• Grace Period: Unlike Shopify uninstalls, we typically retain your data for 30 days after cancellation to allow for account reactivation, unless you explicitly request immediate deletion.

Section 05

International Data Transfers

Your information may be transferred to computers located outside of your state or country. We ensure appropriate safeguards are in place for cross-border transfers.

Section 06

Sharing Your Information

We do not sell your personal data. We share information only with:

• Website Analytics: PostHog processes the marketing website analytics described above.
• Cloud Infrastructure: Vercel (application hosting), Railway (background processing), Cloudflare R2 (object storage) and Neon (database).
• AI Sub-Processors: Google (Gemini) and Replicate, strictly for content generation.
• E-commerce Platforms: To sync data back to your store (e.g., Shopify, WooCommerce).
• Payment Processors & Merchants of Record: (e.g., Tranzila, Lemon Squeezy) strictly to securely process your subscription payments, handle tax compliance, and manage financial transactions.
• Bot Protection: Cloudflare Turnstile verifies that Try-On requests come from real visitors, without showing a visible challenge. See Cloudflare's Turnstile Privacy Addendum.

Section 07

Virtual Try-On (Store Visitors)

Some merchants add our Try-On widget to their product pages. It lets a shopper upload a photo of their own space and see a product placed in it. This section is about that shopper's data. The merchant whose store you are visiting decides to offer the tool and is the controller of your data; Epox processes it on their behalf.

• What it is for: Placing a product into a photo of a space. Try-On does not detect, measure, or recognise faces or bodies, and does not create a biometric template or identify anyone. Merchants are not permitted to use it as an on-body or facial try-on.
• What we collect: The photo you upload, the description you type, the resulting image, the product and store involved, and a hashed form of your IP address used only to prevent abuse.
• How long we keep it: Your uploaded photo is deleted after 7 days. The generated result and the session record are deleted after 30 days. Neither is ever served from a public CDN.
• Who can see it: The merchant can see the sessions their own widget produced — the generated results, the descriptions typed, and, on request, the original photo while it exists. No other merchant can.
• Deleting it sooner: Ask the merchant to delete the session, which they can do immediately from their dashboard, or email privacy@epox.ai.

Section 08

AI Agent Connections

You can connect an AI agent, such as Claude, ChatGPT or Codex, to your Epox workspace through our MCP server, either by approving the connection on our sign-in screen or with an API key you create.

• What an agent can access: Your workspace's products and their photos, collections, generated images, automation runs, try-on analytics and credit balance. If you allow generation, it can also add photos and start generations that use your credits. It cannot delete data, publish to your store, or change billing or settings.
• Where that data goes: What a connected agent reads is sent to the agent's provider and handled under that provider's terms and privacy policy. We do not share it with anyone else.
• How we protect connections: Only a workspace owner can approve a connection or create a key. We store connection tokens and keys only as one-way hashes, and email every owner of the workspace when a new connection is approved.
• How long we keep it: A connection approved on the sign-in screen lasts at most 90 days before an owner must approve it again; an API key lasts until it is revoked or reaches the expiry you set. Records of expired or revoked connections are deleted 30 days later.
• Ending a connection: Revoke any connection or key at any time in Settings → MCP and Settings → API Keys.

Section 09

Changes to This Privacy Policy

We may update this policy to reflect operational or legal changes. Updates will be posted with a revised "Last Updated" date.

Section 10

Contact Us

For privacy inquiries:

• Email: privacy@epox.ai
• Address: Sapir St 7, 1. Gan Yavne, Israel

FAQ

Common questions about your data

Short answers in plain language — each links to the binding clause above.