Product
API Integrations
Every third-party service the LaceLuxx product touches, what it does, and what (if any) of your data we send it. Updated June 20, 2026.
We’re a small team and we believe in being explicit about what tools we use to keep the lights on. If you have questions about any of the below, email [email protected]. Data we handle is governed by our Privacy Policy.
Publishing
Meta Graph API (Facebook + Instagram)
Live- What it does
- Publishes posts to the LaceLuxx Facebook Page and Instagram Business account via Meta's Content Publishing API.
- Why we use it
- Keeps our feed alive between live shows so followers see new authenticated pieces, show countdowns, and post-show recaps even when we're off-camera.
- What we send
- Our own post text and images. No follower data is read. We never message anyone on Meta's behalf.
Threads API
Live- What it does
- Publishes text posts to @lace__luxx on Threads via Meta's Threads Graph endpoint (graph.threads.net).
- Why we use it
- Threads is becoming a real luxury-resale conversation hub; we want LaceLuxx in it without the manual paste.
- What we send
- Our own post text only. Threads is text-only in our flow.
Live Commerce
WhatNot
Live- What it does
- Hosts our weekly live luxury-bag auctions and the WhatNot Shop drop-buys.
- Why we use it
- WhatNot is the platform our community already trusts for live luxury auctions with $1 starting bids.
- What we send
- We don't pull WhatNot data programmatically (no public API). Order info comes through WhatNot's seller dashboard.
Resale Marketplace
Poshmark
Live- What it does
- Mirror of select inventory for buyers who prefer Poshmark over WhatNot's live format.
- Why we use it
- Some buyers like the slower, browse-and-bid pace.
- What we send
- Order info is handled by Poshmark's own platform.
Content Generation
OpenAI (gpt-image-1 / DALL·3)
Live- What it does
- Generates on-brand still-life images for each scheduled post when no photo is provided. Prompts are built from a brand visual guide so output stays editorial and restrained.
- Why we use it
- Lets us keep a posting cadence without spending a half-day on photo shoots for filler posts.
- What we send
- Only the post's intent (channel, beat, body) is sent. No personal information.
Data Infrastructure
Supabase
Live- What it does
- Postgres database + Storage bucket that mirrors our content calendar and archives every generated image to a permanent URL.
- Why we use it
- Single source of truth across the cron publisher, the admin dashboard, and the kit JSON in source control.
- What we send
- Server-only access via a service-role key. Not exposed to the public web.
Hosting
Vercel
Live- What it does
- Hosts www.lace-luxx.com, the admin dashboard at /admin/calendar, and the API routes the dashboard calls.
- Why we use it
- Edge-first Next.js hosting with zero-config preview environments per PR.
- What we send
- Standard HTTP request logs only.
Cloudflare Pages
Live- What it does
- Secondary static deploy of the marketing site as a CDN-fronted backup.
- Why we use it
- Geographic resilience.
- What we send
- Standard request logs only.
Automation
GitHub Actions
Live- What it does
- Cron that runs every 5 minutes, checks the scheduled-post kit, and fires posts whose send time has passed.
- Why we use it
- Hands-off posting so the feed runs even when Lacey is sourcing inventory.
- What we send
- Only our own kit data. Posts back the published-post id and timestamp.
Analytics
Google Analytics 4
Live- What it does
- Aggregated traffic and conversion analytics.
- Why we use it
- Helps us see which announcements drive WhatNot follows and Poshmark visits.
- What we send
- Anonymous, aggregated. We honor Do Not Track.
Vercel Analytics + Speed Insights
Live- What it does
- Core Web Vitals and page-view metrics for the marketing site.
- Why we use it
- Catches regressions in load time after deploys.
- What we send
- Anonymous, sampled.
PostHog
Live- What it does
- Product analytics with event-level granularity — which CTA, which channel, which live show was the entry point.
- Why we use it
- Goes deeper than GA4 so we can A/B test post copy and CTA placement.
- What we send
- Anonymous device id by default. No PII.