Beta — the platform and this API are in beta. The rules on this page are binding; we may add features and tighten validation without notice.

Data protection & consent

You are sending us personal data about real people. This page explains what you declare, what the creator confirms herself, and what we keep.

consent_confirmed must be exactly true, otherwise 400 consent_required. With it you declare that the creator agreed to be referred to management agencies through Creator Guard and to you sending us her details — including her age and content types, which can reveal information about her sex life and are special-category data under the GDPR.

She confirms herself

Your declaration lets us create the lead. It is not enough to offer her to agencies: she confirms that she is 18 or older and gives her consent herself, through her personal consent link or the creator portal. Only she may confirm — never open her link and confirm for her. When and from where she confirmed is recorded; through the API you see only the status and the dates, never her IP address or browser. She can withdraw her consent at any time; her listing then leaves the marketplace and she is no longer offered to agencies.

Who sees what

Who What
You Your own leads, their stage, milestones and your earnings. Not which agencies were involved. If another account submitted a creator first, a 409 says only that — and only 20 times a day.
Agencies Offers without her contact details or your notes. Only the agency that accepts her and pays gets her contact details.
The creator Her own profile and confirmations, if she has a creator login.
Creator Guard Everything, to review, match and support.

What the API stores

  • The lead and listing — the fields you send, under your account.
  • A request log per request: key, account, method, endpoint (as a template such as /v1/leads/{id}), status, error code, request id, duration and time. No creator data and no request bodies. Kept 90 days. Requests without a valid key are not stored there; our server log keeps only their request id, method, endpoint template, status and error code.
  • Idempotency answers for 24 hours, so a retry gets the first answer.
  • Your API key only as a SHA-256 hash, plus its prefix in clear.
  • Photos and logos you upload, re-encoded without any metadata; your original bytes and file names are never stored. See Photos.
  • Events for 30 days, and per webhook delivery the status code, duration and a short error of each attempt — never the body your server answers. Events reference the object; its current state is read when the event is delivered or read. A few events also store a snapshot of their object for the 30 days: a removed photo's metadata (no file, no storage path) and the status of a creator API job or data request — see Data retention.
  • An audit trail of key, webhook and account changes for 90 days, with the IP address and client that made them — never secrets or creator data. See Usage, logs & audit.
  • Nothing from POST /v1/extract: neither the text you send nor the suggestions.

Always use https://.

Minimise what you send

Send only what helps place her. notes and notes_public are free text: no identity documents, passwords, payment details or explicit material. notes is for our team only; notes_public is shown to agencies.

Deletion and requests from creators

If a creator asks you to delete her data or what we hold about her, forward it to info@creator-guard.com with her creator number (CR-…). How Creator Guard processes personal data: privacy policy.