Personal by design.

Traffic and performance

We use Vercel Web Analytics and Speed Insights for cookieless, anonymised traffic and performance measurements. Query strings and URL fragments are removed before events are sent.

Optional product analytics

If you choose “Allow analytics”, Faced records a small set of steps such as viewing a product, starting the customiser, whether photo processing succeeded, and reaching checkout. Google Analytics measures consented page visits, acquisition, and this reviewed event subset using first-party analytics cookies. Advertising storage, advertising user data, and ads personalisation remain disabled. PostHog EU uses a random identifier that lasts for one browser tab; its person profiles, location enrichment, automatic capture, and session replay are disabled.

With the same permission, Meta receives product views, customiser starts, cart additions, and checkout starts through its browser pixel and server-side Conversions API. Browser and server copies share a random event identifier to prevent double-counting. Meta may receive its first-party browser identifiers, your IP address, browser user agent, and the page origin and path without query parameters or fragments. Faced does not send Meta a photo, filename, design, email address, postal address, or payment detail. You can withdraw permission at any time with “Privacy choices” in the footer, which stops future optional collection and removes the Google Analytics and Meta cookies accessible to this site.

Creator and campaign links

If you arrive through a registered creator or campaign link, Faced keeps only its short code and capture/expiry timestamps in a signed, short-lived first-party cookie. The cookie has no visitor, account, photo, design, contact, or payment identifier. We use it to count aggregate product views, customiser starts, carts, and Shopify-verified paid orders, with low-volume report rows hidden. This affiliate accounting is separate from optional Google Analytics and PostHog collection; clearing site cookies removes the browser attribution.

Error monitoring

When configured, Sentry receives technical errors and limited performance traces. Faced removes request bodies, cookies, authorization headers, URL queries, user identity, and unsafe breadcrumb categories before sending an error. Retained network and navigation breadcrumbs contain only scrubbed request metadata. Session replay is not enabled.

Email support

When you email support, Faced and its email delivery provider process your email address, display name, subject, message, delivery metadata, and the number of attachments so the store owners can answer you. Message text is copied into Faced’s private support inbox; attachment files are not imported into that inbox. These Faced support threads are automatically deleted after 30 days without activity, while the email provider applies its own configured retention to received and sent mail. Support content is excluded from analytics and error reports. Include an order number only when it is needed for help, and never send card details or passwords.

Marketing email

Faced queues marketing email only after a separate, explicit opt-in. Marketing consent is not bundled with photo processing, checkout, or optional product analytics. Every marketing message includes an unsubscribe link; withdrawing consent suppresses queued and future marketing email unless you explicitly opt in again later.

If you request a saved-design link, the address is kept only in server-restricted marketing-contact storage. The email contains no photo or filename. Its random link can grant access to one saved design until the earlier of the link, design, or guest-session expiry, and can be revoked.