> For the complete documentation index, see [llms.txt](https://docs.developer.singpass.gov.sg/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.developer.singpass.gov.sg/docs/getting-started/singpass-brand-guidelines.md).

# Singpass Brand Guidelines

If you are a Singpass partner referencing our brand in your marketing materials, these guidelines explain how to do so correctly.

Singapore residents use Singpass every day to access essential services — spanning government, financial transactions, and healthcare. This is made possible by thousands of partners across the public and private sectors who have integrated Singpass into their platforms.

Presenting our brands accurately strengthens awareness, recognition, and trust with the users we both serve.

#### **Download Singpass logo asset:**

{% file src="/files/GLm5lUdskiz5u4xn3HYH" %}

{% file src="/files/b0cCVS8jCtdbdNYhZ0gn" %}

***

### How to show the Singpass brand

#### Singpass logo

Always present Singpass’ role accurately, both in the content and visual. The Singpass logo is available in three variants to ensure it remains clear and legible across different backgrounds and contexts.

<table><thead><tr><th width="200.484375">Type</th><th>Use when</th><th>Variant</th></tr></thead><tbody><tr><td><p><strong>Full colour (Primary)</strong></p><p>The default logo.</p></td><td>Use this whenever possible on light or neutral backgrounds.</td><td><img src="/files/h27pHP7dJJazmywehOtC" alt="" data-size="original"></td></tr><tr><td><strong>White (secondary)</strong></td><td>For use on dark backgrounds where the full colour logo would not be legible.</td><td><img src="/files/9lYboJzAPCQUGPwodRJ0" alt="" data-size="original"></td></tr><tr><td><strong>Black (secondary)</strong></td><td>For use on high-contrast backgrounds, where neither the full colour nor white logo would stand out clearly.</td><td><img src="/files/KW1OejZmjM1KXB4hMWpV" alt="" data-size="original"></td></tr></tbody></table>

<i class="fa-thumbs-down" style="color:red;">:thumbs-down:</i> <mark style="color:red;">**DON'T**</mark>

* DON'T modify the Singpass logo — no stretching, skewing, or colour changes.
* DON'T place the Singpass logo on backgrounds that reduce legibility. Use white or black backgrounds where possible.

<figure><img src="/files/OKbvMFnLccy2aFWd74OZ" alt=""><figcaption></figcaption></figure>

#### **Logo placement**

For collaborative brand partnerships, the Singpass logo will come first, followed by respective brand partner logo(s).

* Both logos should be similarly proportioned. We recommend that you first start by matching the height or width of partner logo(s) to the Singpass logo.
* Both logos should be scaled to the same optical size for visual balance.
* Clear space should be used between the logos, denoted by the x-height of the ‘i’.

<figure><img src="/files/XJWtXdPaXPTexzNqGc9V" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/kUOm17c6OFcLwQgceK2Q" alt=""><figcaption></figcaption></figure>

**Minimum size**

Minimum sizes of the Singpass logo:

* Digital: **80 pixels wide**
* Print: **18mm wide**

<figure><img src="/files/xfMtJZLQiHivOt7FJX7v" alt=""><figcaption></figcaption></figure>

#### Singpass buttons

We provide standardised Singpass buttons for use across your websites, mobile applications, and connected platforms. Please refer to the button guidelines [here](#singpass-buttons).

***

### How to talk about the Singpass brand

Ensure you reflect how your service or product integrates with ours in a way that is truthful and precise.

{% hint style="success" icon="thumbs-up" %}

#### <mark style="color:green;">DO</mark>

* DO use the Singpass name only as a proper noun — e.g. "Log in with Singpass" or "Sign up with Singpass".
* DO only describe capabilities your integration actually uses.
  * e.g. If you use Singpass for login only, do not reference use of personal data.
    {% endhint %}

{% hint style="danger" icon="thumbs-down" %}

#### <mark style="color:red;">**DON'T**</mark>

* DON'T alter or combine the Singpass name. This includes:
  * Variations: "SingPass", "SINGPASS"
  * Abbreviations: "SP"
  * Compound names: "MyApp Singpass Login"
* DON'T use the Singpass name to imply a relationship beyond your actual integration. This includes:
  * Phrases like "Powered by Singpass", "Secured by Singpass"
  * Using Singpass to describe your own features, e.g. "a secure Singpass verification link"
* DON'T use the Singpass logo or make statements that imply endorsement from or overstate the involvement of Singpass.
  {% endhint %}

***

### Approval for Brand Usage

All use of Singpass brand elements and product visuals requires prior approval. Submit your proposed content before publishing or distributing any materials.

When submitting, include:

* Draft artwork or mockups showing how the Singpass brand will appear
* The intended placement and context (e.g. website, mobile app, printed collateral)
* Your planned publication or launch date

<a href="https://partnersupport.singpass.gov.sg/hc/en-sg/requests/new" class="button secondary">Submit your request here</a>

Allow at least 2 working weeks for approval. Submit early if your materials are time-sensitive.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.developer.singpass.gov.sg/docs/getting-started/singpass-brand-guidelines.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.