Legal
Privacy Policy
How Epox collects, uses, and protects your data.
Version 2026-11-14 · Last updated November 14, 2026
Epox is a commercial product operated by Matan Markes, a registered Sole Proprietor (Osek Murshe) in Israel ("we," "us," or "our"). We are committed to protecting the privacy and intellectual property of the professionals and merchants ('you' or 'User') who use our application, and the shoppers who use Try-On on merchants' storefronts. This Policy describes how we collect, use, and secure your data.
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 your name, email address, 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 (Polar, Tranzila, and, for Shopify App Store subscribers, Shopify Billing), and are not stored on Epox's servers.
- Usage & Technical Data: Product-analytics events, device and browser information, IP address, and error diagnostics generated as you use the application. See Product Analytics & Error Monitoring.
- People who report content: If you use our Report content form, we collect your name and email address, your phone number and postal address if you choose to give them, and the report itself (what you report, why, and any statement you make). We use it to handle the report and, where the law requires, to share the notice with the account holder concerned. It is kept for up to 3 years after the report is closed (see Section 3).
- Virtual Try-On Shoppers: If you are a shopper using the Try-On widget on a merchant's storefront, see Virtual Try-On (Store Visitors), which describes what we collect from you.
Optional Generation Notifications
If you choose Notify me or enable notifications in Settings and allow your browser's permission request, we notify you when your generations finish. Closed-tab notifications require a separate opt-in in Settings or the Notify me prompt that explains they work even when Epox is closed. We store your browser's push endpoint and encryption keys linked to your account and workspace to deliver these notifications through your browser provider's push service. Notifications can contain a product or flow name and completion counts, which may appear on your device's lock screen. We do not use this permission for marketing. You can withdraw permission at any time in Settings > Preferences > Notifications or in your browser's site settings. Turning push off removes the browser subscription; signing out also attempts to remove it. We remove server subscriptions when you turn them off successfully or the push service reports that they have expired.
Marketing Website Analytics & Campaign Attribution
Only if you accept. When you first visit the production marketing website, a banner asks whether we may use analytics cookies and session recordings. Until you choose, and if you choose Reject, the website loads no analytics, sets no analytics cookie or browser storage, and sends nothing to PostHog. If your browser sends a Global Privacy Control or Do Not Track signal, we treat it as Reject and do not show the banner. The legal basis for this analytics is your consent.
If you accept, we use PostHog to measure page visits, how far you scroll, clicks on links to the Epox app, submitted product URL hostnames (not full product URLs), and page-performance metrics. We also build heatmaps of where on a page visitors click, move the pointer and scroll; a heatmap records positions on the page, not the text of the page or anything you type. Click events include the page, section, button label and identifier, destination path, and recognized plan, billing cycle, or tool choices. Page events also include standard browser and request context, such as the page URL, campaign parameters and referring site, and browser or device information. PostHog may also record the session (a share of visits, not all of them): the page layout, your clicks, scrolling and navigation. Anything you type into a field is masked and never recorded. This helps us understand which pages and entry points work and fix what is hard to use; we never use it for advertising or to track you on other sites.
PostHog then sets a cookie and local-storage entries (their names begin with ph_) holding a random identifier and your session. The cookie is set for the whole epox.ai domain, so the Epox app recognizes the same identifier: if you then create an account, your earlier website visits are linked to it and handled as described in Section 9.1. How long PostHog keeps each entry is set by PostHog; see PostHog's documentation.
Changing your mind. Use Cookie settings at the foot of any website page to see your choice and change it. Choosing Reject deletes the PostHog cookie and browser storage the website can reach and stops collection from then on; data already collected stays subject to Sections 3 and 4. Your choice is kept in a cookie named epox-consent (Section 9.1) for six months, after which we ask again.
Separately, the website reads incoming campaign parameters, advertising click identifiers (gclid and fbclid), referral codes, and the referring hostname from the address you arrive at, and keeps them in the page's memory while you browse. It does not write them to cookies, localStorage or sessionStorage, and they are gone when you reload or close the page. When you follow a link to the Epox app, they are added to that link so the app can tell which campaign brought you; the app then uses them only for the analytics described in Section 9.1.
Contact form. If you write to us through the contact form on the website, we receive the website, email address, and, if you give them, the name and message you enter, and the page the form was on. Our email provider (Resend) delivers them to hello@epox.ai. We use them only to answer you and keep the email for as long as we need it to handle your request.
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 use third-party AI services to perform generation, editing, upscaling, and analysis tasks. Google is our primary provider, used through both Google Cloud Vertex AI and the Gemini API. Depending on the feature and the model used, we also send data to other providers, including Replicate and fal.ai (which host third-party models), OpenAI, xAI, Volcengine (ByteDance), Ideogram, and Black Forest Labs. We may also use TypeSafe to run automated quality checks on generated images, which would send it the prompt, product details, the generated image and the product photo it was made from; it is not switched on yet, and we will give notice as described below before it is. We only send the specific data points required for the requested operation to these providers.
Epox maintains a current list of all third-party sub-processors utilized for the Service, which merchants can request at hello@epox.ai. By using the Service, you grant general authorization for Epox to engage these sub-processors. When we add or replace any sub-processor, we give merchants notice in the app (the next time you sign in you are asked to review and accept the updated terms) and, where practical, by email, giving you the opportunity to object to the change by closing your account.
2.3 Safety Screening of Uploads
To keep Epox safe and lawful, we automatically screen the images you upload or import, and the photos shoppers submit to Try-On, for sexually explicit content, sexual content involving minors, and graphic violence. Some content is not screened, such as images that sync from your connected store, and a video file itself (for an uploaded video we check its cover image). A downscaled copy is sent to our AI provider for this check. The check itself is automated: no person reviews your image as part of it unless the check flags it. We also aim to check the results Try-On generates before they are shown to a shopper; this is automated and cannot catch everything, and if a result is blocked the store's credits for it are refunded.
If the check cannot run, for example during a brief outage of our AI provider, a Try-On photo is not used or stored and the shopper is asked to try again; a photo that cannot be read is rejected. An image you upload is accepted during such an outage and checked automatically once the check is available again; if it then breaks the rules it is blocked and removed. When we block an image you uploaded we tell you that the decision was made automatically, give the broad reason, and tell you how to ask a person to review it: use Report issue in the app or email hello@epox.ai, quoting the reference we show you.
For each decision we record an event — what was detected, when, the workspace, and where it happened — and not the image. The one exception is apparent child sexual abuse material. The law does not allow us to simply delete it, so if the check detects it, whether in an upload or a Try-On photo or result, we keep a copy separately, with access limited to the people handling the report, for the period the law requires, may report it to the competent authorities, and delete it afterwards (see Section 3). Any other Try-On photo that cannot be used is not stored.
2.4 AI-Generated Content
Images and videos created or edited with Epox's AI tools are marked as AI-generated. Where technically possible we embed a machine-readable label in the file's metadata (the IPTC "digital source type" field), and our Try-On previews display an "AI-generated preview" label. Not every kind of output carries a metadata label: videos made before we added video marking do not; a trimmed or cropped copy of a video that was not made with Epox's AI is not marked; WebM videos are not marked; removing the background from your own photo is treated as ordinary editing and is not marked; a copy of an AI-generated image that you edit with some of the tools that run in your browser (for example, cropping or adjusting it) can be saved without the marking; and a temporary preview from a quick edit is not marked until you save it. The markers can also be lost when a file is re-compressed or re-uploaded by another service, so please do not rely on them alone: if you publish AI-generated content, tell your audience that it is AI-generated.
2.5 AI Training & IP Protection
- Google: We use Google's AI services under its paid, enterprise-grade terms (Google Cloud Vertex AI and the paid Gemini API). Under those terms Google states that it does not use customer data submitted through these services to train its foundation models.
- Other AI providers: The other providers named in Section 2.2 receive only the data needed to perform the requested operation and handle it under their own terms and privacy policies. Those terms differ from Google's, and we do not make a no-training commitment on their behalf.
- Epox: Epox does not use your Input Data or your Generated Assets to train, fine-tune, or distill generative AI models. We use them only to generate your requested assets and to operate, secure, support, and improve the Service, including automated quality checks on generated images and reviewing AI request traces to fix and evaluate generation quality, and we do not share them with other merchants.
- Provider changes: If we add or replace an AI provider, we will update our sub-processor list and give notice as described in Section 2.2.
Section 03
Data Retention
- Asset Library: We keep your assets in our cloud storage for as long as your account exists. Cancelling a paid subscription moves the workspace to the free plan and does not delete them. When you delete your account, we keep it restorable for 30 days and then permanently delete it and its assets (see Section 4.2).
- Virtual Try-On: A shopper's uploaded photo is deleted automatically, normally within 8 days of the Try-On session starting; the generated result, description, and session record are deleted 30 days after the session is created. See Virtual Try-On (Store Visitors).
- Records of what you accepted: When you accept our Terms or confirm an upload attestation we record the wording version, the time, your IP address, your browser user agent and the workspace. If your account is deleted we keep these records as evidence, on the basis of our legitimate interest in establishing and defending legal claims, for 7 years after the deletion. They are detached from the account, and your email address is kept only as a keyed, non-reversible value, so they can be found again only from that address. At the deletion we also shorten the IP address to its network part (the last part is removed) and delete the browser user agent; what we keep is the wording version, the time, the shortened IP address and, while that workspace exists, the workspace it was accepted for. During the 30-day restore period they stay with the account.
- Safety and legal records: We keep records of automated content-moderation decisions for 6 months (180 days) after the decision, or, where the decision sent the content for review by a person, until that review is finished if that is later; records and evidence of apparent sexual content involving minors for at least one year after the matter is closed, and never while it is open; and notices of illegal or infringing content, with our response, for up to 3 years after the report is closed; we may keep a record longer where a legal obligation or a legal claim requires it. Apparent child sexual abuse material detected by our screening, including in Try-On photos and results, is not deleted on the schedules above: where the law requires us to preserve it (including material reported to the National Center for Missing & Exploited Children) we keep it securely and separately, with access limited to the people handling the report, for at least the period U.S. law requires for material reported to NCMEC (one year), or longer if law enforcement asks us to preserve it, then delete it.
- Operational data: Server logs held by Better Stack are kept for up to 90 days. Error reports held by Sentry are kept only for the standard retention period of our Sentry plan, after which Sentry deletes them. The detailed log of credit changes is kept for 365 days, generation analytics events and store-sync history for 90 days, and generation job records (including prompts and settings) for as long as the workspace exists; invoices and payment records are kept for as long as tax law requires. Bug reports you send through Report issue, including any voice recording and its transcript, are kept in our database while your workspace exists so that we can follow them up, and are deleted with it; copies sent to our internal tools (team alerts in Telegram and Google Chat, and the text of a proposed fix on GitHub) are not deleted automatically and can remain there. Conversations with Epoxy, the in-app assistant, are deleted after 30 days without activity.
- Security: Assets are stored using enterprise-grade encryption (AES-256).
3.1 Backups
Our database is protected by backups: a point-in-time recovery window of 7 days and scheduled snapshots kept for up to 35 days, both provided by our database provider, and weekly off-site copies that we keep for up to 90 days. Data you or we delete from the live service can therefore remain in those encrypted database backups for up to 90 days, after which it is overwritten or removed. Backups are used for disaster recovery. They contain database records, not the image and video files themselves, which are held in object storage and are deleted from it when you or the retention schedule delete them.
Section 04
Platform Compliance & Data Rights
We respect your rights under the privacy laws that apply to you. 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: We respond to this webhook, but Epox does not store records identified by a Shopify customer, so there is nothing to return (see below).
- customers/redact: We respond to this webhook, and because we hold no record identified by a Shopify customer there is nothing to erase. Anonymous Try-On shopper data is deleted automatically (photos normally within 8 days, everything else after 30).
- shop/redact (App Uninstall): Shopify sends this webhook about 48 hours after you uninstall the Epox App. On receipt we permanently delete the data tied to that Shopify store — its imported products, the Generated Assets created from them, and related synchronization records — and the entire workspace only if it was created solely for that store. If it also holds anything else (another store or member, a paid plan billed outside Shopify, purchased or granted credits, or content not derived from the shop), we delete only the shop-derived data. If you reinstall before the signal is processed, nothing is deleted.
Epox does not receive Shopify customer identities, including for Storefront Try-On shoppers, so there is normally no customer record for these two webhooks to return or erase. See Shopify Stores in the Try-On section.
Warning: Due to Shopify's requirements, we cannot offer a 30-day "grace period" for uninstalled Shopify stores. Ensure you download your assets before uninstalling.
4.2 For Non-Shopify Merchants (WooCommerce/Web)
- Right to be Forgotten: Delete your account in the app under Settings, or email hello@epox.ai to ask us to delete it and all associated data.
- Grace Period: Unlike Shopify uninstalls, a deleted account that owns a workspace can be restored by signing in again within 30 days (an account that owns no workspace is deleted straight away). After that it is permanently deleted (see the Terms, Section 6.2), unless you ask for immediate deletion. Cancelling a paid subscription does not start this period; it only moves you to the free plan.
4.3 Your Rights by Region
To report content that uses your image, voice, or personal data without permission, or that shows you in an intimate image without your consent, use Report content. For access, correction, or deletion requests, follow the steps below.
Depending on where you live, you may have the following rights. To exercise any of them, email hello@epox.ai. We verify that a request comes from you, normally by replying to the email address on your account, and where Epox is acting as a processor for a merchant we may direct your request to that merchant. We answer within one month (this can be extended by up to two further months for complex requests, in which case we tell you why), and within 45 days for requests under California law.
What you must give us. Your name, email address and, for paid plans, billing details are needed to create and run your account; if you do not provide them we cannot provide the service. Everything else, such as a store connection, a phone number on a report, or a message in the contact form, is optional. You are not legally obliged to give us any personal data.
Why we may use it (legal bases). To provide the service you signed up for (contract): your account, workspace, uploads, generations, store sync and billing. For our legitimate interests: securing the service and preventing abuse, safety screening, fixing errors, logs, and understanding how the product is used (product analytics and session replay, Section 9.1). With your consent: Try-On photos where the widget asks for it. To meet a legal obligation: keeping tax records, handling notices of illegal content, and preserving and reporting child sexual abuse material.
- Israel: Under the Protection of Privacy Law, 5741-1981 (as amended), you may ask to review the personal information we hold about you and to have it corrected or deleted. You may also complain to the Privacy Protection Authority at the Ministry of Justice.
- European Union and United Kingdom (GDPR / UK GDPR): You may ask for access to, correction of, erasure of, or restriction of your personal data, object to processing based on our legitimate interests, ask for a portable copy of data you provided, and withdraw consent at any time (without affecting earlier processing). You may also complain to the data protection authority in the country where you live or work (in the United Kingdom, the Information Commissioner's Office). We process merchant account data to perform our contract with you and for our legitimate interests in running and securing the service, and Try-On shopper data on the basis of your consent (or, where the merchant has confirmed that its storefront already collects it, on the merchant's own legal basis).
- California (CCPA/CPRA): You may ask us to disclose the categories and specific pieces of personal information we collected, to delete it, and to correct it, and you will not be discriminated against for doing so. We do not sell personal information and do not share it for cross-context behavioral advertising.
Section 05
International Data Transfers
Epox is based in Israel, and our service providers (see Section 6) may process data in other countries. Your information may therefore be transferred to computers located outside of your state or country. The European Commission recognizes Israel as providing an adequate level of data protection (as do the United Kingdom and Switzerland), so transfers from those places to Epox rely on that recognition. When we pass data on to a provider in a country without such a recognition, we rely on the EU-U.S. Data Privacy Framework (and its UK and Swiss counterparts) where the provider is certified, and otherwise on the European Commission's standard contractual clauses, with the UK addendum for UK data.
Section 06
Sharing Your Information
We do not sell your personal data. We share information with our service providers, grouped as follows, and, at your direction, with the e-commerce platforms and AI agents you connect:
- Cloud Infrastructure: Vercel (application hosting), Railway (background workers, queue and cache), Neon (database), and Cloudflare (object storage and CDN) for hosting and storage. When you open the text-layer tool in the image editor, your browser loads its typefaces from Google Fonts, which receives your IP address and browser information.
- AI Sub-Processors: Google (Vertex AI and the Gemini API) and, depending on the feature and model used, Replicate and fal.ai (which host third-party models), OpenAI, xAI, Volcengine (ByteDance), Ideogram, and Black Forest Labs, strictly for content generation, editing, upscaling, and analysis; and TypeSafe, for automated quality checks on generated images. Apify is used to read public web pages when you ask us to import a store or product page.
- E-commerce Platforms You Connect: To sync data back to your store (e.g., Shopify, WooCommerce). These are not Epox sub-processors.
- Payment Processors & Merchants of Record: Polar, Tranzila, and Shopify Billing, strictly to securely process your subscription payments, handle tax compliance, and manage financial transactions.
- Analytics & Monitoring: PostHog, Sentry, Better Stack, Langfuse (AI request tracing), and Telegram (internal alerts, including the contents of bug reports); see Section 9 (and Section 1 for the marketing website's analytics).
- Bug Reports: A report you send through Report issue (which is also how you ask a person to review a moderation decision) goes to our team. Google transcribes any voice recording you attach. If a team member hands the report to our automated engineering agent, its title and description, the page it was sent from, the recorded steps taken before it was sent, and a link to any voice recording are processed by Anthropic (the agent's AI model) on a server hosted by Google Cloud, and the proposed fix, which can summarise the report, is published to our GitHub code repository.
- AI Agents You Connect: If you connect an AI agent to your workspace, what it reads is sent to that agent's provider at your direction; see Section 8. Those providers are not Epox sub-processors.
- Communications: Resend, to send transactional email such as receipts and account messages, and to deliver messages sent through the website's contact form to us.
- Inspiration Search: Unsplash and Pexels receive the search terms you enter when you browse inspiration images.
- Bot Protection: Cloudflare Turnstile verifies that Try-On requests come from real visitors, without showing a visible challenge. See Cloudflare's Turnstile Privacy Addendum.
We may also disclose information where required by law or to protect rights, safety, and the security of the service.
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 ("shoppers"). You do not need an Epox account to use it, and we do not ask for your name or email address.
7.1 Who Is Responsible
The widget runs on the storefront of the merchant that chose to offer it. That merchant decides why and how your photo is used and is responsible for its own notices to you; Epox operates the widget for the merchant as its processor. Epox is responsible on its own account only for securing the service, preventing abuse, and complying with law. The widget always shows you a privacy notice. Unless the merchant has confirmed that its storefront already collects your consent, the widget also asks for your consent before you can upload a photo.
7.2 What We Collect and Why
- Your photo and the result generated from it, to produce the try-on preview you asked for. A photo of a space can incidentally show people, so please upload only photos you are entitled to share.
- The description you type (an optional prompt), to guide the result.
- Your IP address is used briefly, for rate limiting and for a bot check provided by Cloudflare Turnstile (see Section 6). It is held only for the short rate-limit window and can appear in our short-lived security and server logs (see Section 3); we do not store it, or any value derived from it, with your session.
- The storefront address and product you were viewing, and, where the widget asked for it, a record of your consent (the wording version and the time you accepted), or, where the merchant switched the consent step off, a record that it did, so that we can route the session to the right merchant and show how consent was handled.
- Technical information such as browser type and any errors the widget raises, through the error-monitoring tool described in Section 9. We do not run product analytics or session recording inside the Try-On widget, so your photo is never captured by them.
Legal basis: where the widget asks for it, your consent, which you give before uploading and can withdraw at any time by asking us to delete your data (see 7.6). A merchant may switch the consent step off only by confirming that its storefront already obtains your consent; in that case the merchant is responsible for that consent and for its own legal basis, and the permanent privacy notice in the widget still shows. For security and abuse prevention we rely on our legitimate interest in keeping the service secure.
7.3 Who Receives It
Your photo and prompt are processed by our AI provider to generate the result (the Try-On feature currently uses a Google Gemini model; see Section 2.2), and are stored with our infrastructure providers. Where AI request tracing is enabled, our tracing provider (Langfuse) receives only technical details of a Try-On request (the model, settings such as the aspect ratio and resolution, timing, usage, cost and whether it failed), never your photo, the description you typed, or the result. The merchant whose storefront you used can see the sessions its own widget produced: the generated results and the descriptions typed. It cannot see or download your original photo, and no other merchant can see your session. Authorised Epox staff can view a session's photo and result to investigate a fault or answer a support request, only while they are kept (see 7.4). We do not sell your data and do not share it with advertisers. Epox does not use your photo or prompt to train AI models.
7.4 No Facial Recognition & Biometric Data Retention Policy
Try-On is for placing a product into a photograph of a space. It does not detect, measure, or recognise faces or bodies, and Epox does not create or store face templates, face geometry, or any other biometric identifier from your photo. Merchants are not permitted to use it as an on-body or facial try-on. The photo is processed only to generate the image you requested. To the extent a photo that happens to show a face could be treated as biometric information under the law that applies to you, this section is our retention and destruction policy for it:
- We use the photo only to produce your result for the merchant's product, to screen it for safety (see Section 2.3), and, while it is kept, for our staff to investigate a fault or answer a support request about that session, and for no other purpose.
- Your uploaded photo is permanently deleted, normally within 8 days of the Try-On session starting (it is kept for 7 days and the deletion job runs daily). The generated result, the description, and the session record are permanently deleted 30 days after the session is created. A scheduled job performs these deletions daily. These files are not published or listed anywhere: the result is shown to you through a hard-to-guess link, which stops working once the file is deleted.
- The one exception is apparent child sexual abuse material. If our automated screening detects it in a photo or a result, the law does not allow us to simply delete it: we preserve it separately, with access limited to the people handling the report, for the period the law requires, may report it to the competent authorities, and delete it afterwards. It is not available to the merchant.
- You can ask for earlier deletion (see 7.6), except for the material described above. Our database backups do not include the image files (see Section 3.1).
7.5 You Must Be 18 or Older
Try-On is for people aged 18 or over. If you are under 18, please do not use it or upload a photo. If you believe a photo of a person under 18 has been uploaded, email hello@epox.ai and we will remove it from the service (subject to the exception in 7.4).
7.6 Deleting Your Data & Your Rights
Your data is deleted automatically on the schedule in 7.4. To have it deleted sooner, ask the merchant, who can delete a session immediately from its dashboard, or email hello@epox.ai with the storefront you used and the approximate date and time. Because there are no accounts, we may need those details to find your session. To exercise any of the rights described in Section 4, use the same address.
7.7 Shopify Stores
Epox does not receive Shopify customer identities for Try-On shoppers. The Epox app does not request access to Shopify customer or order data, and a Try-On session is not linked to a Shopify customer record. Shopify's customers/data_request and customers/redact requests therefore have nothing to return or erase beyond the automatic deletion described in 7.4.
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 summary and credit balance, products and their photos, collections, generated images and videos, generation flows and jobs, automations and their runs, your store connection status, and try-on analytics and session summaries (without shoppers' photos, prompts or IP addresses). If you allow generation, it can also add source photos, create products and flows, and start image and video generations and edits 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.
- What we log when an agent adds an image: We record which connection or API key did it, which workspace owner's confirmation it rode on, the website the image came from (host only), and its size and type, for security and abuse prevention. We remove location and camera metadata from stored copies of fetched images.
- 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 approved on the sign-in screen are deleted 30 days later. A revoked or expired API key stops working immediately, and its record is kept.
- Ending a connection: Revoke any connection or key at any time in Settings → MCP and Settings → API Keys. Questions: hello@epox.ai.
Section 09
Product Analytics & Error Monitoring
- Product analytics (PostHog): In production, while you are signed in to the app (Section 9.1), we use PostHog to understand how the product is used, through specific events we define (automatic click capture is turned off). We also use session replay: recordings show layout, clicks, and navigation; form inputs are masked, and images, videos and canvases are blocked from recordings. Other text shown on screen, such as product names or a prompt displayed outside a form field, can be recorded.
- Error monitoring (Sentry): Sentry receives error reports and performance traces, which can include technical details such as the page address and browser and device information, and, where we attach one, a user or workspace identifier.
- AI request tracing (Langfuse): Where tracing is configured, Langfuse receives the prompt and settings of AI requests and references to the source and generated images, which we use to debug and evaluate generation quality. For Storefront Try-On requests it receives no prompt, image or result, only technical details (model, settings, timing, usage and errors).
- Logs (Better Stack): Our servers ship structured logs to Better Stack to keep the service healthy. These logs record operational events and can include identifiers and request metadata.
9.1 Cookies and Similar Technologies
"Cookies and similar technologies" means small files and browser storage (such as cookies and local storage) that a site keeps on your device. We use three kinds.
Essential: always on. These make the service work and cannot be switched off in the product:
- Sign-in session: cookies that keep you signed in and secure your account (a session token and a cached copy of your session, plus a flag if you chose not to be remembered). They last up to 7 days, are renewed while you use Epox, and are removed when you sign out.
- Guest mode: a cookie named
epox-guest-mode, kept for up to 30 days, and a local-storage entry with the same name, that remember you are browsing as a guest. - Security: cookies and tokens that protect forms and requests against forgery and abuse.
- Your cookie choice: on the marketing website, a cookie named
epox-consent, kept for six months, that records whether you accepted or rejected analytics, so we do not ask on every page.
Functional: always on, kept only in your browser. Local-storage and session-storage entries that remember your preferences and keep work from being lost: your light or dark theme, selections and pickers you were in the middle of, pending uploads and generations you started, and a copy of your recent conversation with Epoxy, the in-app assistant. They hold no advertising or tracking identifier, are not sent to anyone else, and stay until the task completes, you clear them, or you clear your browser data.
Analytics: on while you use the Epox app, as described here. We do not ask you to opt in. This section is the notice. On the marketing website, analytics runs only if you accept it; see Marketing Website Analytics & Campaign Attribution.
- Product analytics and session replay (PostHog): in production, while you are signed in to the Epox app, PostHog sets a cookie and local-storage entries (their names begin with
ph_) that hold a random identifier, your session, your account identifier and your workspace's identifier and name. We do not send PostHog your email address or your name; older records that still held them are being removed. A session replay records the layout, your clicks and navigation as you use the app: text you type into fields is masked, and every image, video and canvas is blocked from the recording, but other text shown on screen, such as product names or a prompt displayed outside a form field, can be recorded. How long PostHog keeps each entry is set by PostHog; see PostHog's documentation. We use this to understand how the product is used and to fix what is hard to use, and never for advertising or to track you across other sites. It does not run in our own staff sessions, and it never runs inside the Try-On widget shown to store visitors. - Error monitoring (Sentry): in our configuration Sentry sets no cookies and writes nothing to your browser storage. It sends error reports under our legitimate interest in keeping the service working.
Opting out. To stop analytics and session replay for your account, email hello@epox.ai from the address you signed up with and we will exclude you and delete the PostHog data tied to your account. You can also block or delete cookies and local storage in your browser settings, though that may sign you out. Data already collected stays subject to the retention and rights described in Sections 3 and 4. Epox works the same either way.
Section 10
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 (currently November 14, 2026). Where a change adds or replaces any sub-processor, we will give merchants notice as described in Section 2.2.
Section 11
Contact Us
For privacy inquiries:
- Email: hello@epox.ai
- Address: Sapir St 7, 1, Gan Yavne 7688000, Israel
FAQ
Common questions about your data
Short answers in plain language — each links to the binding clause above.
See also our Terms of Service. Questions about your data? Contact us.