Projects

A project is the container for everything you use at TrustComponent. It holds one or more modules — the products — together with what they share: the team, billing, contracts, the audit log, API keys and webhooks.

flowchart TD
    U["Your account"]
    A["Agency (optional)"]
    P["Project"]
    C["CAPTCHA"]
    M["Monitoring"]
    V["VAT Checker"]
    S["Shared: team and roles, billing, add-ons,
contracts, audit log, API keys, webhooks"]
    U -->|member| P
    A -.manages.-> P
    P --> C
    P --> M
    P --> V
    P --- S

Most teams use one project per website, product or customer. Agencies and service providers who look after many projects for their clients use an agency on top.

A module is one product inside a project:

A project contains each module at most once. Every module has its own plan, its own included volume and its own trial; the modules share everything else in the project. If you need two separate CAPTCHAs with separate teams or invoices, create two projects.

1. Sign in or create an account, then open Create project.
2. Modules — pick a module and its plan. You can add the other modules right away or later. Have an offer code from our sales team? Redeem it here.
3. Add-ons — optionally book project add-ons such as support or governance. Module add-ons are offered together with their module.
4. Billing and payment — enter the billing profile and choose a payment method. This step is skipped when nothing in the project is charged.
5. Review — name the project (3 to 50 characters), optionally link it to your agency, accept the terms and create it.

Every paid module starts with a 14-day trial. The project opens on its overview page, where the setup guide of each module takes you through the first steps.

You can create as many projects as you like and rename a project at any time under Settings › General.

The overview is the start page of a project:

• Needs attention — open items that someone has to act on, for example a failed payment. Items disappear as soon as the cause is fixed.
• Project — members, API keys, webhooks and the DPA at a glance, plus the next steps of the project setup guide.
• One panel per module — its state (trial, active, cancelled), its key figures and its setup guide. A guide lists the steps that make the module work — required steps first, then optional ones. A step is ticked off automatically once it is done.

A project can show two notices above everything else:

• Scheduled for deletion — all modules are cancelled. Until the date shown, you can restore them under Settings › Modules & Add-ons.
• Locked — our team has locked the project. Members can still sign in and read everything, but the modules reject API requests and CAPTCHA verifications, and no add-ons or credits can be booked. Billing continues while the project is locked. Contact support to find out why and how to unlock it.

Every paid module starts with a free trial of 14 days.

• During the trial, the module and its usage are free. Project add-ons you book are free during the trial as well.
• You receive a reminder 7 days before the trial ends.
• At the end of the trial, the module switches to the paid plan automatically and is billed from that day on. You don’t need to do anything to keep using it.
• To start the paid plan earlier, choose Activate under Settings › Modules & Add-ons.
• To pay nothing, cancel the module before the trial ends. Cancelling a module in its trial ends it immediately.
• Free plans (for example CAPTCHA Non-Commercial) have no trial; they stay free for as long as you use them. Moving a module from a free plan to a paid plan starts its 14-day trial.

Each module has its own trial. A module you add to an existing project starts its own 14-day trial. A module gets a trial only as long as it has never been paid: once paid, it stays paid.

Before a paid module starts its trial, the project needs its billing details. If they are missing, you enter them in the same step.

Each module has a plan with a fixed monthly price and an included volume per calendar month:

The counter starts again on the first day of every month (UTC). Besides the volume, plans differ in features and limits — number of domains, monitors, status pages, stored identifiers, seats, how far back the audit log reaches and so on. The dashboard shows the current usage of a limit next to the respective create button, for example 7 / 10 monitor locations.

• Admins receive an email when a module has used 80 % of its included volume, and another one at 100 %.
• Nothing stops. The module keeps running without interruption, and exceeding the volume is not charged automatically — unless an individual offer sets a price for additional usage.
• If you exceed the included volume significantly or repeatedly, upgrade to a plan that fits your usage — or contact us for an individual arrangement.

Settings › Modules & Add-ons › Upgrade plan moves a module to a higher plan.

• The upgrade applies immediately. You pay the difference for the rest of the current month, then the new price.
• During the trial, the upgrade applies immediately as well; billing still starts when the trial ends.
• From a free plan, the upgrade starts the module’s 14-day trial; billing starts when it ends.
• To move to a lower plan, contact support.

An offer is an individual agreement with our sales team, delivered as a code such as AB2C-D2EFG-HI34-JKL5. Redeem it while creating a project or later with Settings › Modules & Add-ons › Redeem offer code. Before you accept, you see the modules, add-ons and the monthly total of the offer. Redeeming an offer replaces the plans of the project’s modules that the offer includes, and the add-ons of the types it contains, with the terms of the offer. Modules and add-ons the offer doesn’t cover stay as they are. If the offer includes a trial, a module on a free plan starts a trial of the length the offer states; a module that is already paid stays paid.

Add-ons extend a project beyond what the module plans include. Book, change and cancel them under Settings › Modules & Add-ons.

There are two kinds:

• Project add-ons apply to the whole project and every module in it:
  • Support — guaranteed response times, included support hours and, at higher levels, direct access to our engineers. See Support.
  • Governance — more seats, a longer audit log with export and API, two-factor enforcement and invitation rules. The Enterprise level adds single sign-on with automatic provisioning, advanced and multiple roles, expiring memberships, audit log streaming and an even longer audit log.
• Module add-ons extend one module, for example the branding options of the CAPTCHA widget or additional status page features in Monitoring.

How booking works:

• Every add-on type has levels. A project holds one level per type, which covers every module in the project.
• Booking or upgrading applies immediately and is billed for the rest of the current month.
• A lower level cannot replace the one you pay for. Cancel the current level at the end of its period, then book the lower one.
• Cancelling ends an add-on at the end of the current billing period (you can undo this until then) or immediately — there is no refund for the rest of the period.
• Project add-ons booked during a trial are free until the trial ends.

The add-ons you can currently book yourself in the dashboard. Individual offers and add-ons booked under earlier terms can differ — what your project actually has is always shown under Settings › Modules & Add-ons.

As of October 2026. Prices per month, plus VAT.

Working hours are Monday to Friday, 8:00 to 18:00 (Europe/Berlin). For agencies, see Agency add-ons.

Open Settings › Modules & Add-ons and choose Cancel on a module, or Cancel modules or delete the project at the bottom of the page.

• A paid module runs until the end of the period you have paid for and is then removed. Until then you can undo the cancellation. If you want it gone right away, choose End it immediately — there is no refund for the rest of the period.
• A module in its trial, or on a free plan, ends immediately.
• A module takes its module add-ons with it.
• Cancelling the last module deletes the whole project, including its project add-ons, team, API keys and settings.
• A module scheduled for removal can be deleted now instead of waiting.
• You pick a reason and can leave a comment — it helps us improve.

These topics are shared by projects and agencies and have their own pages.

Who has access to the project and what they may change — members, seats, roles, invitations, invitation rules, expiring memberships and two-factor enforcement — is described in Identity & Access. Sign-in through your identity provider is described in Single Sign-On.

Open Team & Access, choose Create Invitation, enter the email address and the roles. See Inviting members.

The billing profile, the bill recipient, payment methods and invoices are described in Billing.

Every change in the project is recorded under Governance › Audit Logs — see Audit Logs.

Open a ticket under Support, the last entry of the project menu — see Support.

API keys authenticate your own servers against the TrustComponent API — to fetch CAPTCHA results, send heartbeats, validate VAT IDs or read the audit log. Manage them under Settings › API Keys & Webhooks.

• Keys start with ak_ and are shown in full exactly once, right after you create them. Afterwards only a shortened form like ak_AbCd…WxYz is shown. We store only a hash — a lost key cannot be recovered; create a new one.
• Give each key a description (up to 256 characters) so you can tell them apart, and optionally an expiry: 30 days, 6 months, 1 year or never.
• A key belongs to its project and works for every module in it. It has no roles or scopes — treat it like a password and keep it in your server’s secret store, never in frontend code.
• To rotate a key, create a new one, deploy it, then delete the old one.
• Creating and deleting keys needs the Member role. Both are recorded in the audit log.

Send the key as bearer token:

Authorization: Bearer ak_your_key_here

Webhooks push events to an HTTPS endpoint of yours as they happen — for example when a VAT validation result is ready. Manage them on the same page, Settings › API Keys & Webhooks.

• Every endpoint has a signing secret (whsec_…). Verify the TC-Webhook-Signature header of every delivery with it; you can rotate the secret at any time.
• Test sends a platform.webhook-endpoint.test event, so you can check your endpoint end to end.
• The detail page lists the latest deliveries with their status (Sent, Pending, Waiting for retry, Failed, Cancelled), attempts and the response of your endpoint. Failed deliveries are retried automatically up to 5 times with increasing delays.

Signature verification, retries and the event catalog are described in the Webhooks API reference.

Agreements between your company and TrustComponent are concluded per project under Governance › Contracts. The most common one is the Data Processing Agreement (DPA) according to Art. 28 GDPR. Opening and concluding contracts needs the Legal role.

1. Open Governance › Contracts › Create Data Processing Agreement.
2. Enter your company details — your company is the controller in the agreement.
3. Confirm and create. The DPA is generated and concluded right away, becomes Active and can be downloaded as PDF at any time.

Contracts are either generated by the platform (like the DPA) or uploaded by our team after an offline signature. A contract that needs your approval shows as Pending approval with Accept and Decline. Afterwards it is Active, and later possibly Cancelled, Revoked or Superseded by a newer version. Every contract stays downloadable as PDF, including archived ones.

The Consents table below lists lighter acceptances — terms and conditions, privacy policy, contract confirmations — with date and version.

Agencies conclude contracts for themselves under their own Governance › Contracts. Agreements with you as a person are listed under Contracts & consents in your user profile.

Can I extend the trial? The trial lasts 14 days. If you need more time to test, open a ticket and tell us what you still need to test.

I booked something by mistake. Cancel it under Settings › Modules & Add-ons — a module in its trial ends immediately and costs nothing. For a paid module or add-on, open a ticket with the invoice number if you already have one.

My module has reached its included volume. Nothing stops — see When you exceed the included volume. Upgrade the plan if your usage stays above it.

A feature shows “Not included · See options”. Your plans and add-ons don’t include it. See options takes you to the plans and add-ons that do.

Which key goes where? See API keys: the API key stays on your server, the site key goes into the widget.

Where do I get the DPA? Under Governance › Contracts in your project — see Signing a DPA. You need the Legal or Admin role.

I can’t see the Settings or Governance menu. These areas need specific roles. Ask an admin of the project.