Meta BYOK / branded OAuth consent for white-label API customers

We're a white-label SaaS platform using Zernio for social connect, analytics, posting, and inbox. Headless OAuth works well for returning users to our domain after connect.

Problem On Meta's OAuth consent screen, users still see Zernio's shared app branding (app name, privacy/terms links), not our product brand. Headless mode doesn't change that screen — support confirmed this can't be customized per API key today, and Meta BYOK isn't available yet (unlike X/Twitter BYOK for some accounts).

Impact

• Customer trust: Users expect to authorize our product name, not a third-party connector they don't recognize

• Meta app review / access verification on our side doesn't match what end users see at connect time

• Breaks our white-label positioning at the highest-friction step in onboarding

Request Please prioritize one of:

1. Meta BYOK — let API customers attach their own Meta Developer app (name, logo, legal URLs, redirect URIs) while Zernio continues to handle tokens, refresh, and API operations

2. Dedicated branded Meta app per customer — Zernio-managed, but shown as our brand on consent

3. Public roadmap + ETA if neither is near-term, plus guidance for customers going through Meta verification on a shared app

Context Multi-tenant SaaS; each end user connects their own Instagram/Facebook/Threads accounts. We've already built on your API (headless connect, analytics, inbox, posting). Building a parallel Meta Graph stack outside Zernio would duplicate your value prop.

Happy to discuss requirements privately with your product team — this post is to add customer weight to the feature, not to share implementation details publicly.