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 addendum for API partners (v1)

Effective: upon publication · Applies to: every account that uses the Creator Guard API, from the acceptance by its owner or an admin, in addition to the terms you accepted for your account and the API Terms of Use.

This addendum covers the personal data that you and Creator Guard exchange through the Creator Guard API. It applies in addition to the terms you accepted for your account (GET /v1/agreements).

You and Creator Guard LLC are independent controllers: each of us decides why and how it uses the creator data it holds. You send us a creator so that we can introduce her to vetted management agencies, which is our own purpose. Neither of us processes data on behalf of the other.

An owner or admin accepts this addendum once for your whole account, as its own agreement type: in the portal (Settings → API) or with POST /v1/agreements/api_dpa/accept. The acceptance is recorded with its time and, through the API, the key used. Your account needs it for live keys, live OAuth apps and live writes through the API; an account that already held a live key when this addendum was published may keep working without it for 30 days. Test keys work without it.

1. Parties

  • Creator Guard: Creator Guard LLC, a limited liability company organized under the laws of the State of New Mexico, United States of America, Business ID 0008125377, 1209 Mountain Road Pl NE #11622, Albuquerque, NM 87110, USA, info@creator-guard.com.
  • Our representative in the EU (Article 27 GDPR): MOXAMO GROUP Ltd, Palaion Patron Germanou 11, 8011 Paphos, Cyprus, info@moxamogroup.com.
  • You: the company or person that holds a Creator Guard partner or agency account and uses the API with it.

2. Subject and purpose

Through the API you, as a referral partner, submit creators and keep their details up to date, upload their photos, send them consent and claim links, follow their progress and your commissions. As an agency you receive offers, accept or decline them, pay reservations, receive a creator's contact details after payment and report the outcome. Either kind of account can manage its team members, receive webhook events on its own servers and register OAuth apps through which a creator can connect her Creator Guard account to your dashboard. We use the data to review creators, introduce them to vetted management agencies, run your account and keep the API secure (rate limits, request log, audit events).

3. Roles

  • For the data you collect and keep in your own systems, you are the controller.
  • For the data we receive and process for our brokerage, Creator Guard LLC is the controller.
  • Neither of us processes data on behalf of the other under this addendum.
  • Creator data you receive through an OAuth app (her profile, status, consent state, her data-export file) is sent to you because she authorised your app on our consent screen. From then on you are the controller for that copy and process it under your own privacy policy, which your app must name.

4. Data and data subjects

  • Creators you submit: Name, Instagram handle, other contact details, platforms, follower count, niche and your notes; profile details such as age, gender, country, languages, content categories, availability and deal terms; photos; the status of her consent and age confirmation
  • Creators who connect your OAuth app: What she allowed with the app's scopes: profile, stage, matched agency (after payment), consent and 18+ status without IP address or browser, support messages, her data-export file
  • Agencies' offers (agency accounts): Before payment: the listing under her creator number (CR-…), photos she agreed to share as links valid for 1 hour. After payment: her name and contact details (creator_name is null until then)
  • Your team: Members and invitations (email address, role, who invited whom); account and key details (label, scopes, last use); the request log (route, status, time — no IP address, no request body); audit events (who changed keys, webhooks, members, the key policy or an authenticator, when, and from which IP address and client — in the portal and with an API key; kept 90 days). Fraud check on consent records: when a creator you submitted gives her consent or 18+ confirmation, we compare its IP address with the IP addresses your account's logins (owner and members) used within 30 days before or after — sessions and sign-ins, two-factor checks, audit events and terms acceptances, read where they are already kept, not copied. We store only the result (match yes / no, which kind of record and which login matched, when, same browser), never the IP addresses, for as long as her consent record exists. A match shows our admins a warning; nothing is blocked, no decision is taken on it alone, and you are not told

Special-category data. A creator's age and content categories can reveal information about her sex life, which makes them special-category data under the GDPR (Article 9). With consent_confirmed: true you declare that she agreed to the referral and to you sending us these details. She confirms her consent and that she is 18 or older herself before any agency sees her profile.

5. Your obligations

  • Send a creator only with her agreement, and tell her that Creator Guard receives her details.
  • Send only what helps place her. Never put identity documents, passwords, payment details or explicit material into notes.
  • Keep API keys secret and revoke a leaked key at once.
  • Forward a creator's request for access or deletion that concerns our copy to info@creator-guard.com, with her creator number (CR-…).

6. Our obligations

  • Agencies see a creator's profile under her creator number, without her name or contact details, and only after she has confirmed her consent and her age. Only the agency that accepts her and pays the placement fee receives her name and contact details.
  • Her consent, her 18+ confirmation and her acceptance of the creator terms are given only on our own pages (consent link, creator portal), never through an app of the account that referred her (such a call answers 403 referrer_app_not_allowed). She can withdraw her consent through any app she connected.
  • If she withdraws her consent, her listing goes offline for every agency that has not completed a placement with her, her deals that are not yet paid are cancelled, and every agency holding an offer for her receives the event offer.consent_revoked; it must then delete what it received about her within 30 days (Agency Terms).
  • We never tell you which agencies were involved, and we never tell another partner who submitted a creator first.
  • We answer data-subject requests for our copy and tell you when a request concerns data you sent.
  • What the API keeps about requests and integrations is deleted on fixed schedules (Data retention).

7. Security measures

  • Transport: HTTPS only, TLS 1.2 or newer, HSTS.
  • Keys: stored only as SHA-256 hashes, with scopes per key and an optional IP allowlist and expiry; a revoked key stops working with the next request.
  • OAuth: authorization codes (60 seconds), access tokens (1 hour) and refresh tokens (30 days from last use) stored only as hashes; PKCE required; a creator can disconnect an app at any time.
  • Passwords set on our pages (join and claim links): checked against known breaches with the k-anonymity range API of Have I Been Pwned — only a 5-character hash prefix leaves our server.
  • Members: member changes in the portal need two-factor authentication; every change is in the audit trail.
  • Least data: each account sees only what its role allows; agencies never see who referred a creator; another account's resource answers 404.
  • Logs without creator data: the request log holds the route template, status and timing, no creator data and no request bodies; events carry ids and are built from the current object at delivery time, except a few stored snapshots without creator contact data (a removed photo's metadata, the status of an export job or data request), kept 30 days.
  • Photos: re-encoded on upload; location and camera metadata are removed.
  • Hosting: our own server in France (OVHcloud, data centre in Gravelines) holds the database, logins and files; nightly encrypted backups on the same server, and OVHcloud keeps an encrypted copy of the server's files in Strasbourg, France, for 30 days.
  • Administration: admin access requires a two-factor login.

8. Sub-processors

We use the providers listed under Sub-processors. We announce a new provider there and in the changelog, where reasonably possible before it receives API data. If you object, you may stop using the API.

9. Transfers outside the EU

Creator Guard LLC is established in the USA; data you send from the EU is therefore transferred to the USA, although our database and servers are in France.

The EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914, Module One, controller to controller) apply between you and us; they are incorporated into this addendum and concluded when you accept it. Creator data an agency outside the EU receives is covered by the Standard Contractual Clauses (Module One) in the Agency Terms.

10. Personal data breaches

If a breach affects data the other party sent, each of us tells the other without undue delay, at the latest within 72 hours after becoming aware, and with what is known — to info@creator-guard.com for us, to your account's contact address for you.

11. Retention and deletion

Leads stay while the creator is in the pipeline; she can ask for deletion at any time — by email, a support ticket or through an app she connected (POST /v1/creator/deletion-request). On deletion her consent records keep the decision, text version, channel and time, and lose the IP address and browser; these records are deleted 3 years after the placement ended or her data was deleted. What the API keeps about requests and integrations is deleted on fixed schedules (Data retention): request log and audit events 90 days, idempotency keys 24 hours, events and webhook deliveries 30 days, OAuth codes and tokens 1 day after expiry, ended app connections 90 days, jobs 30 days, data-export files 7 days, unused claim links 30 days after expiry.

Leads and listings have no fixed retention period: we keep them as long as necessary for the introduction and delete them on request. Team invitations are deleted 30 days after they were accepted, revoked or expired.

12. Term

This addendum applies while you use the API and afterwards for as long as either of us still holds data received under it.

13. Governing law and venue

This addendum is governed by the laws of the State of New Mexico, United States of America. Courts: the state and federal courts located in Bernalillo County, New Mexico. This does not limit a creator's rights under the GDPR or her right to complain to a supervisory authority.