Quickstart
Get a consent banner live on your website: create an account, publish your first configuration, and install the SDK.
nastar.dev, the API answers on api.nastar.dev, and the SDK is served from cdn.nastar.dev. The one thing that isn't live is the npm package — @nastar/consent-sdk hasn't been published to the registry, so bundled apps load it from the CDN too (SDK reference). 1. Create your account
Sign up with your email address. There's no password — Nastar uses email + a one-time code, sent to your inbox.
2. Create an organization and a website
The setup flow after your first login asks for an organization name, then your website's name and domain. Once created, you land on the site's Overview tab, which shows its public site key — an identifier, not a secret, safe to embed in client-side HTML.
3. Configure and publish your banner
A new site starts as a draft — visitors never see a draft. Adjust banner copy and consent categories under the Banner tab, then click Publish changes on Overview. Publishing creates an immutable, versioned snapshot that your website's visitors will actually see.
4. Install the SDK
Copy the installation snippet from your site's Overview tab. It looks like this, with your real site key already filled in:
<script defer src="https://cdn.nastar.dev/sdk/v1/nastar.min.js"
data-site-key="YOUR_PUBLIC_SITE_KEY"></script> Paste it into your site's <head>, before any analytics or marketing scripts. That /sdk/v1/ path is a rolling one: it always serves the current SDK, so fixes reach your site without you redeploying. If you'd rather pin an exact version and review each upgrade yourself, the SDK reference covers the immutable per-version path — and the createNastarClient API, if you're bundling instead of using a plain <script> tag. Bringing an AI coding assistant to do this for you? Start with AI IDE integration instead.
Using Nuxt or a plain static site? There's a step-by-step guide for each: Nuxt · plain HTML.
5. Verify it
With the SDK installed, open your site and check:
- The consent banner renders before any optional script runs.
- Rejecting leaves every non-necessary category off, and stays that way on reload.
- Accepting all, then reloading, skips the banner and restores the same decision.
- Reopening your privacy settings control shows the same choice, and lets you change it.
See SDK reference for the full behavior contract, including what happens offline or if a visitor's browser blocks storage.