---
title: "App branding & logo"
description: "Add a logo, homepage, privacy policy, terms, and support email to your OAuth app so it looks trustworthy on the BankSync consent screen."
section: "API"
canonical: "https://banksync.io/docs/api/app-branding"
---

Your app's branding is what users see when they authorize it on the BankSync consent screen: the logo, the display name, and links to your homepage, privacy policy, and terms. Complete branding makes your app look trustworthy — and it's required before you can request verification.

> **Before you start:** You need the Admin or Owner role in the workspace that owns the app. Branding is optional
> while an app is internal (draft), and required when you request verification.

[![An OAuth app's branding and verification: adding a logo and details, requesting verification, the verified badge on the app, and how a verified app shows your brand on the consent screen.](https://cdn.banksync.io/videos/app-branding.poster.b6ac7a7bb0260ceb.png)](https://cdn.banksync.io/videos/app-branding.a97f24f44bf1e82f.mp4)

[Watch: An OAuth app's branding and verification: adding a logo and details, requesting verification, the verified badge on the app, and how a verified app shows your brand on the consent screen.](https://cdn.banksync.io/videos/app-branding.a97f24f44bf1e82f.mp4)

## Upload a logo

**Upload a logo**

1. **Open the Branding tab** — On the app detail page (Developers → Apps → your app), open the Branding tab.
2. **Choose an image** — Click Upload (or drag an image onto the logo box). Use a PNG, JPEG, or WebP up to 1
   MB. Square images look best.
3. **Done** — The logo uploads and appears immediately. Click Replace to change it or Remove to clear
   it.

> **Supported formats:** Logos must be static raster images — PNG, JPEG, or WebP. SVG isn't accepted. Images are downscaled
> to a square thumbnail before upload.

## Add details

On the **Details** tab you also control the text users see on the consent screen:

- **Tagline** — a one-line summary, shown on your app's card and the consent header.
- **Description** — a longer description shown in full when a user authorizes your app.
- **Tags** — up to six comma-separated keywords (for example `reporting, ai`).

## Set your links

On the same **Details** tab, fill in:

- **Homepage URL** — where users can learn about your app.
- **Privacy policy URL** — how you handle their data.
- **Terms of service URL** — optional.
- **Support email** — where users can reach you.

Click **Save** to persist the changes. Each URL must be a valid `https://` link.

## Where branding appears

The logo, name, and links show on the **consent screen** every time a user authorizes your app. A complete, professional presentation reduces drop-off and is a prerequisite for the **Verified** badge.

## Next steps

- [Register an OAuth app](/docs/api/registering-an-app) — create the app and its client credentials.
- Once branding is complete, request verification from the app's **Overview** tab.