Current provider categories
OmniLux uses service providers to operate hosting, edge security, authentication, account data, billing, email, monitoring, analytics, support, managed-media workflows, and product infrastructure.
Provider availability, regions, and product roles may change as OmniLux moves from private beta toward public launch.
- Supabase - authentication, database-backed application features, and account sessions.
- WorkOS - organization-aware authentication, SSO, and provider or studio access flows.
- Stripe - checkout, billing, customer billing portal, payment processing, tax support, and fraud-prevention signals.
- Cloudflare - DNS, edge routing, TLS, traffic protection, bot or abuse prevention, and public ingress support.
- Sentry - optional error monitoring, crash reporting, and reliability diagnostics.
- Plausible or Umami - optional privacy-respecting marketing site analytics when configured and allowed.
- Email and sign-in providers - account verification, password reset, transactional email, OAuth, and sign-in flows you initiate.
- Content and metadata providers - catalog metadata, artwork, imagery, or third-party materials used in discovery or marketplace previews.
Provider review
Before broad launch, OmniLux should maintain an internal subprocessor inventory with purpose, data categories, transfer posture, retention, security review, and contract status.
Material subprocessor changes that affect active customers or providers should be reflected in this page or a product-specific notice where required.
Provider contracts should cover confidentiality, security controls, breach notice, subprocessor flow-downs, deletion or return of data, cross-border transfer terms where needed, and limits on using OmniLux data for unrelated provider purposes.
Regional requests
Privacy requests about subprocessors can be sent to [email protected] from the email address associated with your OmniLux account.
OmniLux may need to verify your identity and may route some requests through the account, billing, provider, or support workflow that owns the relevant data.