Hosted pages for creators
You do not have to build anything for creators. Create a link with your API key, send it to her, and she does the rest on our pages on app.creator-guard.com. Building your own screens is the alternative: OAuth.
Consent link
POST /v1/leads/{id}/consent-link (also in consent.url of the 201 that created a lead) returns a URL https://app.creator-guard.com/creator-consent/<token>, valid for 30 days. We store links only as hashes, so a link is shown once: each call makes a new link, and the previous one can then only be used to withdraw a consent (like an expired link). She reads the consent text, agrees (or declines) and confirms she is 18 or over. After the 30 days the link can no longer be used to agree, but she can still withdraw a consent she gave through it. Each step is recorded in the consent ledger with the channel hosted_link.
Claim link
POST /v1/leads/{id}/claim-link (scope leads:write) returns https://app.creator-guard.com/claim/<token>, valid for 7 days and usable once. On that page she chooses her own email address and password (at least 10 characters) for the creator portal — you never see or set her password, and nobody else can. The URL is shown once (url: null in an Idempotency-Key replay); a new claim link makes the previous one invalid. A lead whose creator already has a login, or that was withdrawn or rejected, gets 409 invalid_state (current_state claimed, withdrawn or rejected) instead of a link.
If no login can be set up with the email address she enters (for example because it already has one), the page says so in neutral words — it never confirms that an address is registered — and asks her to sign in instead or to use another address. A link takes at most 5 submissions per hour, and after 10 failed attempts (login not set up, password refused) it stops working; create a new one. Her login is what she signs in with on our OAuth consent screen when she connects your app.
The login works as soon as the form is sent. So that nobody can quietly claim it in her place, we record when the link was used, from which IP address and browser, and which account issued it. She sees this in her creator portal ("Your login was set up on …"), and our team sees it; it is never shared with partners, agencies or apps. The page tells her so before she sends the form, with a link to our privacy policy. Send the link only to her.
Creator portal
After claiming, she signs in at https://app.creator-guard.com/creator-portal: her status, profile and photos, consent and 18+, creator terms, support tickets, and the apps she connected (she can disconnect any of them there). A forgotten password is reset from the login page (/reset-password) once password e-mails are switched on; until then our support helps her.
Embedding
Our hosted pages and the OAuth screens cannot be shown inside a frame (X-Frame-Options: DENY, frame-ancestors 'none'), send no referrer and are never cached. Link to them, open them in a new tab, or redirect — never embed them in an iframe.