Skip to content
Trust surface

BYO OAuth credentials.
Your name on the consent screen.

Every social provider Synq supports accepts your own OAuth credentials. Plug them in once per Brand and your end-users see your company name on Google's consent screen, your quota on Apple's token endpoint, your DKIM-signed email on email OTP. Synq stays invisible.

Why it matters

The line between an auth platform and a brand

When a user clicks Continue with Google and a consent screen appears saying "[other company] wants to access your account", it breaks trust on the spot. Every sign-in vendor who skipped BYO credentials lost users at that screen. Synq ships BYO as the default — your OAuth app, your name, your quota. The consent-screen branding is the same brand your user clicked sign-in for.

Supported providers

BYO works on every social method Synq ships

Google
Apple
Microsoft
Discord
Facebook
X
Telegram
Matrica
How it works

Three steps, one screen

1

Register on the provider

Open Google Cloud, Apple Developer, Meta for Developers, whichever provider you want. Create an OAuth client; copy the client ID and secret (or upload Apple’s .p8).

2

Paste into the Synq Brand

In the Dashboard, open Brand → Connections → [Provider]. Paste credentials and toggle Enable. Synq encrypts the secret at rest with AES-256-GCM.

3

Ship — your brand on consent

The next sign-in routes through your credentials. The consent screen shows your company name; the quota counts against your project; the rate limits are yours.

Per-provider walkthroughs

Common questions

Make every consent screen yours.

One per Brand, per provider. Paste the credentials, toggle on, ship. Your company on consent — Synq invisible.