# Sending Notifications URL: /docs/sending-notifications *** title: 'Sending Notifications' description: 'Send a message to Slack, Discord, Telegram, email, or a signed webhook when something happens in Concord, such as a privacy request arriving, a scan finding issues, or your balance running low.' created: '2026-10-30T00:00:00.000Z' updated: '2026-11-18T00:00:00.000Z' ----------------------------------- ## Overview A **Send Notification** action listens for the events you choose, such as a privacy request arriving, a scan finding issues, or your balance running low. When one happens, it sends a message to every destination you added: * **Slack:** a channel in a workspace you connected. * **Discord:** a channel you connected. * **Telegram:** a direct message or group chat you linked to the Concord bot. * **Email:** people in your organization. * **Webhook:** a signed `POST` request to your own system. One notification can listen for several events and send to several destinations, and you can set up as many notifications as you like. Notifications never carry a requester's personal details, such as their name or email address, so personal data doesn't spread into Slack channels, chat histories, or inboxes, and stays in one place when someone asks you to delete it. Each message says what kind of request it is and links straight to it in Concord. ## Plans and Permissions Send Notification and email destinations work on every plan. Slack, Discord, and Telegram destinations are on Concord Privacy **Essentials** and up, or any paid Concord Trust plan. Webhook destinations are on Concord Privacy **Pro** and up, or any paid Concord Trust plan. A destination your plan doesn't include shows the plan it needs. If you change to a plan without it, that destination stops sending, and Activity says why. Owners and Admins can set up notifications, which needs permission to edit actions. Connecting a chat app needs permission to edit integrations. ## What It Costs * **1 Action each time a notification sends,** however many destinations it sends to. It's charged only when at least one destination gets the message. * **Billing alerts are free:** Balance running low, Billing update, Self-learning skipped, Data Credits auto-purchased, and Actions auto-purchased. * **Send Test and retries are free.** * When your organization has no Actions left, nothing is sent, and Activity says "Not sent: this organization has no Actions left." See [Actions and Data Credits](/docs/actions-data-credits) for how Actions are counted and topped up. ## Connect Your Chat Apps Connect a chat app once in **Integrations**, then pick it in any notification. ### Slack 1. In **Integrations**, open **Slack** and click **Connect**. 2. Slack asks you to allow the Concord app in your workspace. Click **Allow**. 3. In a notification, add a Slack destination, then pick the workspace and the channel. Public channels work right away. A private channel shows in the list once someone invites the Concord app to it in Slack. A Slack workspace can be connected to one Concord organization. Deleting the connection in Concord removes the app from your channels. Slack keeps it listed in your workspace until one of your Slack admins removes it. ### Discord 1. In **Integrations**, open **Discord** and click **Connect**. 2. Give the connection a name, such as the channel's, so your channels are easy to tell apart. 3. Discord asks which server and channel to post to. Pick them and click **Authorize**. You need the **Manage Webhooks** permission on that server. Concord adds a webhook to that channel, named after the Concord app, and posts through it. Each connection is one channel, so connect again for another channel. Deleting the connection also deletes the webhook Concord added. If someone deletes the webhook in Discord, sends to it stop, and the connection asks you to reconnect. ### Telegram 1. In **Integrations**, open **Telegram** and click **Connect**. 2. The dialog links to the Concord bot. Open it for a direct message, or add it to a group. 3. Send the `/start` message the link fills in. The bot replies with that chat's code. 4. Paste the code into **Chat Code** and click **Connect**. For a group the bot is already in, send the command the dialog shows instead. It ends with your organization's ID. A code only works for your organization. If the bot is removed from the chat, sends to it stop. Add the bot back, send `/start` again, and paste the new code into the connection's **Settings** in **Integrations**. ## Set Up A Notification 1. Go to **Actions → Browse Catalog**. 2. Open **Send Notification** and click **Set Up**. 3. Give it a **Name**. 4. Under **Run When**, pick the events it listens for. See [Events](#events). 5. Under **How Often**, pick how often it may send: | Option | Sends | | ----------------------------- | ------------------------------------------------- | | Every time | Once for each event | | At most once every 15 minutes | Once per quarter hour, for each event and project | | At most once an hour | Once per hour, for each event and project | | At most once a day | Once per day (UTC), for each event and project | | At most once a week | Once per week, for each event and project | The limits use fixed blocks of time, such as each hour on the clock, so two events either side of a boundary both send. 6. Under **Send To**, click **Add Destination**, pick where it goes and fill it in. Add as many as you need. 7. Leave **Enabled** on, then save. Your notifications are listed under **Actions → Your Actions**, where you can edit, turn off or delete them. ## Write Your Own Message Each Slack, Discord, Telegram, and email destination has a message box. Leave it empty to send Concord's default message: the event's headline, its details and a link to it. To write your own, type the message and click **Insert Field** to add details from the event. A field such as `{{event.name}}` is filled in when the notification sends. | Field | Fills in | | ------------------------------ | ------------------------------------------------------------------------------ | | `{{event.name}}` | What happened, for example "Privacy request received" | | `{{event.title}}` | The event's headline, which names the task or scan it's about | | `{{event.properties}}` | Every detail on the event, one per line | | `{{event.properties.request}}` | One detail, here the request type. **Insert Field** lists each event's details | | `{{project.name}}` | The project it happened in, when there is one | | `{{organization.name}}` | Your organization | | `{{link}}` | A link to it in Concord | A few things to know: * **Fields go exactly where you put them.** Add spaces or new lines between them. `{{event.name}}{{project.name}}` sends "Privacy request receivedAcme Store". * **A message with no fields gets the default details below it.** Once your message uses a field, it's sent as you wrote it. * **A field shows in red** when none of the events you picked has it. * **Slack and Discord messages can use their own formatting,** such as `*bold*` in Slack or `**bold**` in Discord. Values filled in from the event always show as plain text. * **Email also has an Email Subject,** which can use fields too. It's always one line. ## Test And Check Delivery Click **Send Test** on a destination to send it a sample message right away. A test is marked as one, isn't charged, and isn't retried. To see what was sent, go to **Actions → Your Actions → Activity**. Each run shows every destination with its outcome: delivered, or the reason it wasn't. ## Retries And Limits When a destination can't take the message because of a problem that may pass, Concord tries again after **1 minute, 5 minutes, 30 minutes and 2 hours**. Such problems include a timeout, a server error, Slack or Discord limiting requests, or a webhook answering `429` or `5xx`. When a webhook answers `429` with a `Retry-After` header, that can make the wait longer, up to 2 hours. Each retry uses the destination as it's set up at the time. So if you fix a webhook address, the next retry uses the fix. A problem that won't pass on its own isn't retried. That includes a webhook answering a `4xx` other than `429`, or a redirect. A notification sends at most **100 times a day** (UTC). Billing alerts don't count toward that. ## Webhooks A webhook destination sends each event to an address on your own system as an HTTPS `POST` with a JSON body, signed so you can check it came from Concord. ### The Address * It has to start with `https://` and use a hostname, not an IP address. * It can't contain a username or password. * It has to be reachable from the internet. Addresses on private networks are refused. * Concord doesn't follow redirects, so use the final address. Answer with any `2xx` status within **10 seconds**. Do any slow work after you've answered. ### The Request | Header | Value | | ----------------------- | ---------------------------------------------------------------------------------- | | `content-type` | `application/json` | | `user-agent` | `Concord-Webhooks/1.0` | | `x-concord-event-type` | The event, such as `compliance_requests.received` | | `x-concord-delivery-id` | The delivery's ID, the same as `id` in the body | | `x-concord-timestamp` | When this attempt was signed, in seconds since 1970 | | `x-concord-signature` | `v1=` followed by the signature. See [Verify The Signature](#verify-the-signature) | | `x-concord-test` | `true`, on a Send Test only | The body for a privacy request: ```json { "id": "6f1d2c3b-4a5e-4f60-8b7a-9c0d1e2f3a4b", "type": "compliance_requests.received", "createdAt": "2026-10-19T18:44:28.425Z", "data": { "event": "compliance_requests.received", "eventName": "Privacy request received", "title": "Privacy request received", "organizationId": "0a1b2c3d-4e5f-4a6b-8c7d-9e0f1a2b3c4d", "organizationName": "Acme", "projectId": "1b2c3d4e-5f6a-4b7c-9d8e-0f1a2b3c4d5e", "projectName": "Acme Store", "entityId": "2c3d4e5f-6a7b-4c8d-9e0f-1a2b3c4d5e6f", "properties": { "complianceRequestId": "2c3d4e5f-6a7b-4c8d-9e0f-1a2b3c4d5e6f", "request": "delete" }, "link": "https://admin.concord.tech/acme/privacy-requests/request-log?complianceRequestId=2c3d4e5f-6a7b-4c8d-9e0f-1a2b3c4d5e6f" } } ``` | Field | Means | | ------------------------------------ | ----------------------------------------------------------------- | | `id` | The delivery's ID. A retry keeps it, so use it to drop duplicates | | `type` | The event. See [Events](#events) | | `createdAt` | When Concord created the message. A retry keeps it | | `test` | `true` on a Send Test, and left out otherwise | | `data.eventName` | The event's name, as shown in Concord | | `data.title` | The event's headline | | `data.projectId`, `data.projectName` | The project, when the event has one | | `data.entityId` | What the event is about, such as the privacy request's ID | | `data.properties` | The event's details, which differ by event | | `data.link` | Where to see it in Concord | ### Verify The Signature When you add a webhook, Concord makes its signing secret, which starts with `whsec_`, and shows it once. Copy it before you save: it's never shown again. To check a request: 1. Take the raw body exactly as it arrived, before parsing the JSON. Most frameworks give you a parsed copy that won't match. 2. Join the `x-concord-timestamp` header, a `.`, and the raw body. 3. Compute an HMAC-SHA256 of that with your signing secret, as lowercase hex. 4. Compare it with the part of `x-concord-signature` after `v1=`, using a constant-time comparison. 5. Refuse the request if the timestamp is more than 5 minutes old, so a copied request can't be replayed. A retry is signed again with a new timestamp, so it passes this check. Node.js, with Express: ```js import crypto from 'node:crypto'; import express from 'express'; const SECRET = process.env.CONCORD_WEBHOOK_SECRET; function isFromConcord(rawBody, headers) { const timestamp = headers['x-concord-timestamp']; const signature = headers['x-concord-signature'] ?? ''; if (!timestamp || !signature.startsWith('v1=')) return false; if (Math.abs(Date.now() / 1000 - Number(timestamp)) > 300) return false; const expected = crypto .createHmac('sha256', SECRET) .update(`${timestamp}.${rawBody}`) .digest('hex'); const received = Buffer.from(signature.slice(3)); return ( received.length === expected.length && crypto.timingSafeEqual(received, Buffer.from(expected)) ); } const app = express(); app.post( '/concord-webhook', express.raw({ type: 'application/json' }), (req, res) => { if (!isFromConcord(req.body.toString('utf8'), req.headers)) { return res.sendStatus(401); } const event = JSON.parse(req.body.toString('utf8')); res.sendStatus(200); // Handle the event after answering. }, ); ``` Python: ```python import hashlib import hmac import os import time SECRET = os.environ["CONCORD_WEBHOOK_SECRET"] def is_from_concord(raw_body: bytes, headers) -> bool: timestamp = headers.get("x-concord-timestamp") signature = headers.get("x-concord-signature", "") if not timestamp or not signature.startswith("v1="): return False try: signed_at = int(timestamp) except ValueError: return False if abs(time.time() - signed_at) > 300: return False expected = hmac.new( SECRET.encode(), timestamp.encode() + b"." + raw_body, hashlib.sha256 ).hexdigest() return hmac.compare_digest(signature[3:].encode(), expected.encode()) ``` ### Duplicates A retry carries the same `id`, the same `x-concord-delivery-id` and the same body as the first attempt. Only `x-concord-timestamp` and `x-concord-signature` change. Keep the IDs you've handled and skip any you've seen. A Send Test's `id` starts with `test-`. ### Rotate The Secret 1. Edit the notification and click **Rotate Secret** on the webhook. 2. Copy the new secret it shows. 3. Save, and update your system with the new secret at the same time. From the save on, requests are signed with the new secret only. A webhook with no secret shows **Requests are not signed**. Click **Add Signing Secret** to start signing it. ### Webhooks Added Before Signing Version 1 A webhook added before Concord signed with `v1` keeps its original format, so your system doesn't break: * The body is the event's details alone: what sits under `data` above, with no `id`, `type` or `createdAt` around it. * `x-concord-signature` is the HMAC-SHA256 of the raw body alone, as hex, with no `v1=` and no `x-concord-timestamp`. To move one to `v1`, remove the webhook destination and add it again with the same address, then update your system. ## Events | Event | `type` | Details in `properties` | | ----------------------------------------- | ------------------------------------- | -------------------------------------------------------------------------------------------- | | Privacy request received | `compliance_requests.received` | `request`: `change`, `delete`, `view` or `do_not_sell`. Also `complianceRequestId` | | Daily privacy request summary | `compliance_requests.daily` | `received.count`, `resolved.count`, `dueSoon.count`, `overdue.count` | | Weekly privacy request summary | `compliance_requests.weekly` | `received.count`, `resolved.count`, `dueSoon.count`, `overdue.count` | | Scan found issues | `configuration.issues` | `domain` | | Task assigned | `tasks.assigned` | `dueAt`, when the task has a due date | | Balance running low | `billing.low_balance` | `pool`: `action` for Actions, `credit` for Data Credits, or `entitlement` for plan capacity | | Billing update | `billing.updates` | None | | Self-learning skipped | `billing.self_learning_skipped` | None | | Data Credits auto-purchased | `billing.data_credits_auto_purchased` | None | | Actions auto-purchased | `billing.actions_auto_purchased` | None | | Trust center access needs review | `trust_center.access_requested` | `trustCenter`, `trustCenterSlug` | | Trust center access granted automatically | `trust_center.access_granted` | `trustCenter`, `trustCenterSlug`, `approvalType`: `auto_domain`, `auto_email` or `returning` | | Trust center NDA signed | `trust_center.nda_signed` | `trustCenter`, `trustCenterSlug` | | Control test failing | `controls.test_failing` | `control`, `test`, `controlId` | | Vendor review due | `vendors.review_due` | `vendor`, `vendorId`, and `riskTier` when the vendor has one | | Vendor document expiring | `vendors.document_expiring` | `vendor`, `vendorId`, `documentType`, `expiresAt` | | Risk review overdue | `risks.review_overdue` | `risk`, `riskId`, `dueAt` | The billing events are free to send. See [What It Costs](#what-it-costs). Trust events never carry a visitor's name, email, or company. ## Troubleshooting | Problem | What to do | | --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | | A destination type shows a plan instead of its settings | Your plan doesn't include it. See [Plans and Permissions](#plans-and-permissions). | | A webhook says "not a public host Concord can reach" | Use an `https://` address with a hostname that's reachable from the internet. | | A webhook says "Delivery failed with status 4xx" | Your system refused the request, so it isn't retried. Check the address and any authentication in front of it. | | A webhook's signature doesn't match | Check against the raw body as it arrived, with the timestamp and a `.` in front, and the current secret. If you lost the secret, rotate it. | | A private Slack channel isn't in the list | Invite the Concord app to the channel in Slack, then open the list again. | | Telegram says the code didn't come from Concord's bot | Send `/start` to the bot again in the chat you want, and paste the new code. A code only works for the organization it was made for. | | Activity says "This Discord webhook was deleted" | Someone deleted it in Discord. Reconnect the channel in **Integrations**. | | Fields run together in the message | Add spaces or new lines between them. | | Activity says "Not sent: this organization has no Actions left" | Top up your Actions. Billing alerts still send. | | A notification sent less often than expected | Check **How Often**. Repeats inside its time block are skipped, and a notification sends at most 100 times a day. | # Using Actions URL: /docs/using-actions *** title: 'Using Actions' description: 'Run Concord scans, checks, and AI agents on demand or on a schedule from one place, see every run, and turn failed checks into tasks for your team.' created: '2026-11-18T00:00:00.000Z' updated: '2026-11-18T00:00:00.000Z' ----------------------------------- ## Overview **Actions** is where Concord runs work for you: scans of your sites, checks of your connected systems, AI agents, and notifications. Set up an action once, run it now or on a schedule, and see everything it found in one place. Anything that needs fixing can become a task your team owns. Actions read your sites and connected systems; they don't change them. Open **Actions** in the sidebar. It has two parts: * **Browse Catalog:** everything you can set up. * **Your Actions:** everything you've set up, with its schedule, its runs, and its results. ## Browse the Catalog Go to **Actions → Browse Catalog** to see what you can set up. Filter by category, such as **Compliance** or **Consent & Trackers**, or search by name. The catalog includes: * **Compliance Scan:** tests how your live site handles consent, from the regions you choose. See [Running Compliance Scans](/docs/running-compliance-scans). * **Cookie & Tracker Scan:** finds the cookies, scripts, and other trackers on your sites. See [Scanning Your Site for Trackers and Cookies](/docs/scanning-trackers-cookies-scripts). * **Google Consent Mode Scan:** checks that your Google tags pick up consent correctly. See [Google Consent Mode V2 (GCM) Scanning User Guide](/docs/google-gcm-scanning-user-guide). * **Send Notification:** sends the events you choose to Slack, Discord, Telegram, email, or your own systems. See [Sending Notifications](/docs/sending-notifications). Open an action to see **What You Get**: the checks it runs, the data it draws on, any AI agent it uses, and an estimate of the Actions and Data Credits a run uses. Choose **Add to Your Actions**, or **Add & Configure** to set it up right away. If the project already has that action, the catalog shows it's in **Your Actions** instead of adding a second one. ## Set Up an Action Each action asks for what it needs, such as the project, the domains, the jurisdictions, or the checks to run. Then choose how it runs: * **On demand:** run it whenever you like with **Run Now**. * **On a schedule:** turn on **Run on a schedule** and choose a **Frequency**, such as daily, weekly, monthly, or quarterly, up to what your plan allows. Some actions are **Managed**: Concord sets them up and runs them for you, like the weekly Google Consent Mode Scan of every project's domains. You can still run a managed action now. ### Open a Task When a Check Fails Turn on **Open a task when a check fails** (or **Open a task if the scan fails**) and a failed check becomes a tracked [task](/docs/tasks-my-work) for your team. When a later scan passes, the task resolves on its own. It's off by default. ## Your Actions Go to **Actions → Your Actions** to manage what you've set up. It has three tabs. ### Library Everything you've set up, with its **Schedule**, **Last Run**, **Next Run**, and **Status**: **Active**, **Paused**, **Idle**, or **Configure to Run** when it still needs settings. Search your actions, filter them by how they run, and from each row: * **Run Now** to run it immediately. * **Edit** or **Configure** its settings. * **Pause** or **Resume** its schedule. * **Duplicate** it, for example to scan another domain with the same settings. * **Remove from Library** when you no longer need it. ### Monitors The checks that keep your controls current: the check groups of your connected cloud accounts and your AI Reviews. Search them, filter by provider, run one now, or choose **Run All** on a connection to start all of its check groups at once. See [Automated Control Checks](/docs/automated-control-checks). ### Activity Log Every run, with its **Time**, **Action**, **Trigger**, **Result**, and **Duration**. Expand a run to see exactly what it found, such as the domains scanned, the trackers found, or a compliance scan's risk level. ## AI Agents Some actions include an AI agent that makes a judgment call a rule can't, then shows its work: * **Privacy Policy Analyst:** part of every Compliance Scan. It reads the privacy policy the scan finds and pulls out a summary and risk signals. * **Tracker Identifier:** optional on the Cookie & Tracker Scan. It suggests a name, company, category, domain, and description for each new tracker a scan finds. Nothing is added until you add it. * **AI Review:** checks a control against the connected systems you choose and records a pass, a fail, or an inconclusive result with its reasoning. See [AI Evidence Collection](/docs/automated-control-checks#ai-evidence-collection). ## What It Costs Runs use Actions, and AI agents also use Data Credits. Each action shows an estimate in the catalog before you set it up, and some runs are free, such as scheduled tracker scans of your registered project domains and the weekly Google Consent Mode Scan. See [Actions and Data Credits](/docs/actions-data-credits). ## Permissions Setting up, editing, and running actions needs permission to edit actions. Owners and Admins have it. See [User Roles and Permissions](/docs/user-roles-permissions). ## Related Articles * [Sending Notifications](/docs/sending-notifications) * [Running Compliance Scans](/docs/running-compliance-scans) * [Scanning Your Site for Trackers and Cookies](/docs/scanning-trackers-cookies-scripts) * [Google Consent Mode V2 (GCM) Scanning User Guide](/docs/google-gcm-scanning-user-guide) * [Automated Control Checks](/docs/automated-control-checks) * [Actions and Data Credits](/docs/actions-data-credits) # Adding and Managing API Keys URL: /docs/adding-managing-api-keys *** title: 'Adding and Managing API Keys' description: 'Learn how to generate and manage secure API keys for integration with other services like CRMs, CDPs, and your help desk software.' created: '2021-05-13T20:50:56.000Z' updated: '2026-10-17T00:00:00.000Z' ----------------------------------- ## Overview * You can add, edit, and delete API keys by going to **Integrations → AI & API Access → API Keys**. * You can change the API Key’s name and permissions. * To connect an AI assistant such as Claude or ChatGPT, you don't need an API key. See [Connecting AI Assistants to Concord (MCP)](/docs/connecting-mcp-clients). {/* Screenshot: adding-managing-api-keys-nav-ai-api-access.png (the API Keys tab under Integrations → AI & API Access) */} ## How to Add an API Key 1. To add an API key, click on the **Add API Key** button. 2. Choose a friendly name for the API Key. Concord typically recommends you use the name of the application for which the API key will be created. 3. Select a permissions role for this API key for the Concord app. Your choices are: * **Admin:** An Admin API key has full rights to everything in an Organization. * **Limited:** A Limited API key has read only rights to all projects plus the ability to add or edit individual compliance requests. * **Owner:** Shown only to Owners. An Owner API key has full rights to everything in an Organization, including billing. ![](/docs/adding-managing-api-keys-add-api.png) ## How to Edit an API Key To edit an API key, click the **Edit** button for the specific API key you’d like to change. ![](/docs/adding-managing-api-keys-edit-api.png) ## How to Delete an API Key To delete an API key, click on the **Delete** button for the specific API key you’d like to remove. **CAUTION:** Be certain no external applications require this API key for proper functionality. ![](/docs/adding-managing-api-keys-delete-api.png) # Connecting AI Assistants to Concord (MCP) URL: /docs/connecting-mcp-clients *** title: 'Connecting AI Assistants to Concord (MCP)' description: 'Connect Claude, ChatGPT, Codex, Cursor, and other MCP clients to your Concord account with one server URL, then manage write access and connected applications.' created: '2026-10-16T00:00:00.000Z' updated: '2026-11-18T00:00:00.000Z' ----------------------------------- ## Overview Concord's MCP server connects the AI assistants your team already uses to your Concord account. Once an assistant is connected, you can ask Claude, ChatGPT, Codex, Cursor, VS Code, or any other MCP client about your privacy and compliance program in plain language, and it answers from your live Concord data. * **One URL, no API keys.** Every assistant connects to `https://api.concord.tech/mcp`. You sign in with your normal Concord login, approve the connection, and choose an organization. * **Read access on every plan.** Assistants can read consent and tracker data, privacy request and consent summaries, your data map, policies and documents, and tasks, plus risks, vendors, controls, and frameworks when your organization uses them. * **Data subject details are opt-in.** Individual privacy requests and consent events include people's names, emails, and messages, so assistants can't see them until an Owner or Admin turns on **Share Data Subject Details**. * **Write access is opt-in.** On plans that include API access, an Owner or Admin can let assistants create and update records. Writing stays off until they turn it on. * **Your permissions apply.** Every request is checked against your current Concord role, so a connection can never do more than you can do in the app. If your role changes, your connections change with it. If you don't see **AI Assistants (MCP)** under **Integrations → AI & API Access**, contact [support@concord.tech](mailto:support@concord.tech) to turn it on for your organization. ## Before You Start * **Who can connect:** any Concord user. An assistant can only see and do what your role allows. See [User Roles and Permissions](/docs/user-roles-permissions). * **Read tools:** included on every plan. * **Write tools:** available on Concord Privacy **Pro**, **Premium**, and **Enterprise**, and on Concord Trust **Pro**, **Premium**, and **Enterprise**. An Owner or Admin also has to turn them on. See [Turn On Write Tools](#turn-on-write-tools). * **Module tools:** tools for risks, vendors, controls, and frameworks appear only when those modules are on for your organization. * **Privacy request and consent event tools:** off until an Owner or Admin turns on **Share Data Subject Details**. See [Share Data Subject Details](#share-data-subject-details). ## Find the Setup Steps in Concord Go to **Integrations → AI & API Access → AI Assistants (MCP)**. The **Connect an Assistant** card shows the server URL with a copy button, and setup steps for each assistant under the **Claude**, **ChatGPT**, **Cursor**, and **Other** tabs. {/* Screenshot: connecting-mcp-clients-connect-an-assistant.png (the Connect an Assistant card on the AI Assistants (MCP) tab, Claude tab selected) */} The steps for each assistant are below as well. ## Connect Your Assistant ### Claude and Claude Desktop 1. In Claude, open **Settings → Connectors** and choose **Add custom connector**. 2. Paste the server URL, `https://api.concord.tech/mcp`. Leave the advanced fields (client ID and secret) empty. 3. Sign in to Concord when the browser prompt appears, then approve the connection. See [Sign In and Approve](#sign-in-and-approve). Concord is also listed in Claude's connector directory, so you can find **Concord** there and add it instead of pasting the URL. Sign-in and approval work the same way. Anthropic's guide to [custom connectors](https://support.claude.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp) has more detail. ### Claude Code Run this command in your terminal: ```bash claude mcp add --transport http --scope user concord https://api.concord.tech/mcp ``` Then run `claude mcp login concord` in your terminal and approve the browser sign-in. `--scope user` makes Concord available in every project, not only the folder you ran the command in. ### ChatGPT 1. Turn on developer mode in ChatGPT. 2. Add a connector with the server URL, `https://api.concord.tech/mcp`. 3. Sign in to Concord when prompted, then approve the connection. Connectors are available on paid ChatGPT plans on the web. OpenAI's [developer mode guide](https://developers.openai.com/api/docs/guides/developer-mode) has the steps. ### Codex Run this command in your terminal: ```bash codex mcp add concord --url https://api.concord.tech/mcp ``` Then run `codex mcp login concord` and approve the browser sign-in. ### Cursor Click **Add to Cursor** on the **Cursor** tab in Concord (or [Add to Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=concord\&config=eyJ1cmwiOiJodHRwczovL2FwaS5jb25jb3JkLnRlY2gvbWNwIn0=) here), or add the server to `~/.cursor/mcp.json` (or `.cursor/mcp.json` in a project): ```json { "mcpServers": { "concord": { "url": "https://api.concord.tech/mcp" } } } ``` Cursor asks you to sign in the first time you use it. ### VS Code and Other Clients Any MCP client that supports remote servers over HTTP, such as VS Code, Windsurf, or Gemini CLI, can connect with the server URL. Add it in the client's MCP settings, then approve the sign-in. In VS Code, add the server to `.vscode/mcp.json`, or use **MCP: Add Server** from the command palette: ```json { "servers": { "concord": { "type": "http", "url": "https://api.concord.tech/mcp" } } } ``` ## Sign In and Approve The first time an assistant connects, it opens your browser: 1. **Sign in** on the Concord login page the way you normally do. If you're already signed in, you go straight to the consent screen. 2. **Review the consent screen.** It names the assistant asking for access and what it's asking for: **Read your privacy and trust data**, and, if the assistant requests it, **Create and update records on your behalf**. Write access is optional and stays off unless you turn it on. 3. **Choose the organization** for this connection. Each connection works with one organization. To use another, connect again and choose it. 4. **Approve.** The browser hands control back to your assistant, and you can start asking questions. {/* Screenshot: connecting-mcp-clients-consent-screen.png (the consent screen showing the assistant name, scopes, and organization picker) */} ## Share Data Subject Details Privacy requests and consent events hold personal details about the people they belong to: names, email addresses, phone numbers, messages, and browser details. Assistants can't see them until an Owner or Admin allows it, so this is off by default. Summaries such as request counts and consent rates stay available either way. 1. Go to **Integrations → AI & API Access → AI Assistants (MCP)**. 2. In the **Tool Access** card, turn on **Share Data Subject Details**. This makes the tools that read privacy requests and consent events available, along with **Create Privacy Request** and **Update Privacy Request** when write tools are on. Turning it off refuses those tools from the next request on. ## Turn On Write Tools Write tools let an assistant make changes in Concord, such as logging a privacy request or adding a data system. They're off by default. To turn them on, you need the **Owner** or **Admin** role and a plan that includes API access. 1. Go to **Integrations → AI & API Access → AI Assistants (MCP)**. 2. In the **Tool Access** card, turn on **Allow Write Tools**. This makes every write tool available to connected assistants. 3. To limit what assistants can change, open **Customize Which Tools** and turn off the tools you don't want them to use. If your plan doesn't include write tools, the card shows a note instead and the switch stays off. {/* Screenshot: connecting-mcp-clients-write-tools.png (the Tool Access card with Allow Write Tools on and Customize Which Tools open) */} | Tool | What It Does | | -------------------------- | --------------------------------------------------------------------------------------------- | | **Create Task** | Create a task and optionally assign it. | | **Assign Task** | Assign a task to a user. | | **Transition Task** | Move a task to a new status. | | **Create Privacy Request** | Log a new privacy request (DSAR) on behalf of a data subject. | | **Update Privacy Request** | Add notes, set a resolution status, or acknowledge a request. | | **Add Data System** | Add a data system to your data map. | | **Update Data System** | Update the fields on an existing data system. | | **Classify Trackers** | Add discovered trackers to a project with a consent category. | | **Run Tracker Scan** | Start a cookie and tracker scan. A scan uses Actions, as it does when you run one in the app. | | **Create Risk** | Add a risk to your risk register. Requires the Risks module. | | **Create Vendor** | Add a vendor from the catalog or as a custom record. Requires the Vendors module. | | **Update Vendor** | Update a vendor and its linked data systems. Requires the Vendors module. | | **Open Vendor Review** | Open a review for a vendor. Requires the Vendors module. | | **Add Control Evidence** | Link a document or URL as evidence for a control. Requires the Controls module. | Write tools add and update records. They don't delete anything, and an assistant can't resolve a privacy request: a person on your team still does that in Concord. For how a scan uses Actions, see [Actions and Data Credits](/docs/actions-data-credits). ### Approving Write Access on a Connection Turning on write tools for your organization doesn't give existing connections write access. Each connection needs its own approval: * If your assistant asks for write access when you connect, turn on **Create and update records on your behalf** on the consent screen. * If you approved a connection as read-only and your assistant later tries a write tool, Concord asks it for write access, and your assistant shows a sign-in prompt where you can approve it. ## Example Prompts Consent and trackers: * "List the trackers our latest scan found that aren't in a project yet." * "Summarize this month's consent opt-in and opt-out rates by region." Privacy requests (with **Share Data Subject Details** on): * "How many privacy requests are open right now, and which ones are past due?" Data map and policies: * "List our data systems and the processing activities they support." * "Summarize our privacy policy and show its version history." Controls and evidence, if your organization uses them: * "Which controls are due for evaluation in the next 30 days?" * "What evidence expires in the next 30 days?" With write tools turned on: * "Add our new Snowflake instance to the data map." * "Create a task to review our cookie policy and assign it to me." ## Revoke a Connection You can see and revoke the assistants connected to your account under **Connected Applications**, in two places: * **My Profile**, which you open from the account icon in the upper right of Concord. * **Integrations → AI & API Access → AI Assistants (MCP)**, below the setup steps. Click **Revoke Access** next to an assistant and confirm. That assistant loses access to your Concord data on its next request, and it has to sign in and approve again to reconnect. Removing Concord from an assistant's own settings stops that assistant from using the connection, but it doesn't revoke it. Use **Connected Applications** to revoke. Because every request is checked against current permissions, removing a person from your organization or changing their role applies to their connections too. ## Troubleshooting ### The Browser Doesn't Open Start the sign-in again from your assistant (run `claude mcp login concord` for Claude Code, or reconnect in the client's MCP settings) and check that a pop-up blocker didn't stop the window. Most command-line clients also print the sign-in link so you can copy it into your browser. ### The Connection Is Refused After Sign-In Your organization may not have AI Assistants (MCP) turned on yet. Contact [support@concord.tech](mailto:support@concord.tech) to turn it on. ### Tools Are Listed but a Request Is Refused Either the connection was approved as read-only, or your Concord role doesn't allow that action. The refusal message says which. For write access, approve it when your assistant asks. For a role change, ask an Owner or Admin. ### New Tools Don't Appear Your assistant keeps the list of tools it received when it connected. If an Owner or Admin turned on write tools or **Share Data Subject Details**, or your organization turned on a module such as Controls after you connected, reconnect in the assistant's MCP settings to load the new list. Reconnecting doesn't add write access on its own; see [Approving Write Access on a Connection](#approving-write-access-on-a-connection). ### Answers Come From the Wrong Organization Each connection is tied to the organization you chose when you approved it. Connect again and choose the right one. ### The Connection Stopped Working Connections expire after a period of time. Reconnect in your assistant's MCP settings. If you're already signed in to Concord in your browser, it only takes a few seconds. ## Related * [Adding and Managing API Keys](/docs/adding-managing-api-keys), for calling the Concord REST API directly. * [User Roles and Permissions](/docs/user-roles-permissions) * [Actions and Data Credits](/docs/actions-data-credits) # Actions and Data Credits URL: /docs/actions-data-credits *** title: 'Actions and Data Credits' description: 'How Actions and Data Credits work together to power advanced features in Concord, and how to manage each pool.' ----------------------------------------------------------------------------------------------------------------------------- ## Overview Concord uses two separate consumption pools for advanced features: **Actions** and **Data Credits**. Core functionality (your public Trust Center, consent management, policy generation, and privacy request handling) does not require either. Advanced workflows like questionnaire generation, RFP automation, AI chat, and document indexing consume both pools: Actions for the orchestration, Data Credits for the AI inference or external data lookup. ## Actions Actions are an organization-level pool included with your plan. They cover orchestration and in-house processing for advanced features. * **Included with your plan.** Every plan includes an allocation of Actions. * **Resets each billing cycle.** Unused Actions do not roll over. * **Add more as a recurring add-on.** If you need more than your plan includes, purchase additional Actions from the **Actions** tab in **Global Settings → Billing**. ## Data Credits Data Credits are a separate pre-paid pool that covers costs passed through from third-party services. When an advanced feature calls an external AI model or third-party data source, the cost is metered against your Data Credit balance. * **Not included in your plan.** You purchase Data Credits separately. * **One-time packs.** Stripe charges your card and credits land within seconds. * **Expire 12 months after purchase.** ## What Consumes Credits Any advanced feature that goes beyond core platform functionality uses Actions. Features that also call an external AI model or third-party data source additionally draw from your Data Credit balance. Current examples include: * **Questionnaire and RFP generation**: AI draft responses use LLM inference to match Knowledge Base documents against each question and produce answers. * **AI chat on your Trust Center**: visitor questions answered by the AI chat agent consume credits for each inference call. * **Document indexing in Knowledge Base**: processing and indexing uploaded documents for AI search and retrieval. * **Scans and checks**: tracker scans, Google Consent Mode scans, Compliance Scans, and control checks against connected systems. Some examples of what common operations use: | Operation | Actions | Data Credits | | -------------------------------------- | ----------------------------------- | ------------ | | Compliance Scan (per jurisdiction) | 2,500 | Up to 50 | | Cookie & Tracker Scan, on demand | 1,000 per domain | None | | Cookie & Tracker Scan, extra subdomain | 1,000 per subdomain, every run | None | | Google Consent Mode Scan, on demand | 500 per domain | None | | Control check group run | 50 per group, per connected account | None | | AI Evidence Collection | 200 | Up to 100 | | Questionnaire or RFP row | 400 | Up to 20 | | Regenerate one row | 200 | Up to 20 | | ROPA report | 100 | None | Some scans run at no cost: scheduled tracker scans of your registered project domains, and the weekly Google Consent Mode scan of all project domains. Where a Data Credit amount says "up to", you're charged for what's actually used. ## Checking Your Balance Navigate to **Global Settings → Billing** and select the **Actions** or **Data Credits** tab. ![Billing: Data Credits tab](/docs/billing-data-credits.png) Each tab shows your current balance and usage analytics broken down by product, agent, reason, and Trust Center or Privacy project. ## Purchasing Data Credits Data Credits are purchased as one-time packs: 1. Navigate to **Global Settings → Billing** and select the **Data Credits** tab. 2. Under **Buy More (One-Time)**, select a credit pack from the dropdown. 3. Click **Update** to complete your purchase. ## Auto-Purchase You can enable auto-purchase so Concord automatically buys the smallest pack that covers the next request when your Data Credit balance hits zero. A monthly cap limits how much can be auto-purchased. 1. On the **Data Credits** tab, toggle **Auto-Purchase** on. 2. Select your monthly cap from the dropdown. 3. Click **Update**. ## Purchasing Additional Actions If your plan's included Actions are not enough, you can add more as a recurring add-on: 1. Navigate to **Global Settings → Billing** and select the **Actions** tab. 2. Select an add-on pack. 3. Click **Update**. The add-on renews with your billing cycle. ## Bring Your Own Key (BYOK) Bring Your Own Key support is on the roadmap and will be available on higher paid plans. Once available, you will be able to connect your own AI provider API key to use most AI features without consuming Concord Data Credits. ## Related Articles * [Billing Overview](/docs/billing-overview) * [Billing FAQ](/docs/billing-faq) # Billing FAQ URL: /docs/billing-faq *** title: 'Billing FAQ' description: 'Answers to common billing questions: plans, payment methods, credits, and trials.' ------------------------------------------------------------------------------------------------ ## Overview Answers to the most common billing and subscription questions. For a full walkthrough of billing features, see the [Billing Overview](/docs/billing-overview). ## How Do I Change My Plan? Navigate to **Global Settings → Billing** and click **Manage Plan & Add-Ons**. From there, select the plan you want to switch to and confirm. Upgrades take effect immediately. Downgrades take effect at the end of your current billing cycle. ## How Do I Update My Payment Method? Go to **Global Settings → Billing** and click **Billing Settings** under one of your licensed products. Enter your new card details and save. The updated payment method will be used for all future charges. ## What Is the Difference Between Actions and Data Credits? **Actions** are included with your plan and cover orchestration and in-house processing for advanced features. Your allocation resets at the end of each billing cycle, and you can purchase more as a recurring add-on. **Data Credits** are a separate pre-paid pool that covers AI inference (LLM passthrough) and third-party data source costs. Data Credits are not included in your plan. You purchase them as one-time packs, and they expire 12 months after purchase. Advanced workflows like questionnaire generation, RFP automation, AI chat, and document indexing consume both Actions and Data Credits. See [Actions and Data Credits](/docs/actions-data-credits) for details. ## What Happens When I Run Out of Data Credits? When your Data Credit balance reaches zero, features that require AI inference or third-party data (such as questionnaire generation, RFP automation, and AI chat) will pause until you purchase more credits or enable auto-purchase. Core platform features are not affected. Your Trust Center, consent management, and privacy request handling continue to work normally. To purchase more, navigate to **Global Settings → Billing**, select the **Data Credits** tab, and choose a credit pack. You can also enable **Auto-Purchase** to automatically buy credits when your balance hits zero. ## What Happens When I Run Out of Actions? If your Actions pool is exhausted before your billing cycle resets, advanced features that consume Actions will pause. You can purchase additional Actions as a recurring add-on from the **Actions** tab in **Global Settings → Billing**. ## How Does the 14-Day Free Trial Work? When you sign up for Concord, you get full access to your selected products for 14 days at no cost. During the trial you can set up your Trust Center, configure Consent Management and your Privacy Center, and explore all features. At the end of the trial, your subscription begins and billing starts on the plan you selected. ## How Do I Cancel My Subscription? To cancel, navigate to **Global Settings → Billing** and click **Cancel Subscription** on the plan that you would like to cancel. Your access continues until the end of your current billing period. If you need help, contact [support@concord.tech](mailto:support@concord.tech). ## Related Articles * [Billing Overview](/docs/billing-overview) * [Actions and Data Credits](/docs/actions-data-credits) # Billing Overview URL: /docs/billing-overview *** title: 'Billing Overview' description: 'How to view and manage your Concord subscription, payment methods, and invoices.' ----------------------------------------------------------------------------------------------- ## Overview The Billing section in Concord lets you manage your subscription, update payment information, and access invoices. All billing settings are available to account administrators. Navigate to **Global Settings → Billing** to access your billing dashboard. ![Billing overview](/docs/billing-overview.png) ## Billing Tabs The Billing page is organized into five tabs: * **Privacy**: your Concord Privacy plan, usage (sessions, domains, users, policies, privacy requests), and subscription management. * **Trust**: your Concord Trust plan and subscription management. Premium and Enterprise Trust plans can also add framework packs here for compliance frameworks (see [Adopting frameworks](/docs/adopting-frameworks)). * **Actions**: your organization's Actions pool. Actions are included with your plan and cover orchestration and in-house processing for advanced features. See [Actions and Data Credits](#actions-and-data-credits) below. * **Data Credits**: your pre-paid Data Credits balance. Data Credits cover AI inference (LLM passthrough) and third-party data source costs. See [Actions and Data Credits](/docs/actions-data-credits). * **Invoices**: past invoices available for download as PDFs. ## Actions and Data Credits Concord uses two separate consumption pools for advanced features: **Actions** are included with your plan and reset at the end of each billing cycle. They cover orchestration and in-house processing. Every plan includes an allocation of Actions, and you can purchase additional Actions as a recurring add-on. **Data Credits** are a separate pre-paid pool that covers costs passed through from third-party services, primarily AI/LLM inference. Data Credits are not included in your plan. You purchase them as one-time packs, and they expire 12 months after purchase. You can also enable auto-purchase to automatically buy credits when your balance hits zero. Advanced workflows consume both. For example, generating AI draft responses for a questionnaire or RFP uses Actions for orchestration and Data Credits for the underlying AI inference. The same applies to AI chat on your Trust Center, document indexing in the Knowledge Base, and other AI-powered features. For details on managing Data Credits, see [Actions and Data Credits](/docs/actions-data-credits). ## Viewing Your Current Plan Your billing dashboard displays your current plan, including: * **Plan name** and billing cycle (monthly or annual) * **Current usage** relative to your plan limits ## Changing Your Plan To upgrade or downgrade your plan: 1. Navigate to **Global Settings → Billing**. 2. Click **Manage Plan & Add-Ons**. 3. Select the plan that fits your needs. 4. Confirm the change. Plan upgrades take effect immediately. Downgrades take effect at the end of your current billing cycle. If you have questions about which plan is right for your organization, contact [support@concord.tech](mailto:support@concord.tech). ## Managing Payment Methods To update your payment method: 1. Navigate to **Global Settings → Billing**. 2. Under one of your licensed products, click **Billing Settings**. 3. Enter your new card details and save. ## Accessing Invoices Past invoices are available in the Billing section. Click the **Invoices** tab to view and download invoices as PDFs. Each invoice includes the billing period, charges, and payment status. ![Billing: Invoices tab](/docs/billing-invoices.png) ## Related Articles * [Actions and Data Credits](/docs/actions-data-credits) * [Billing FAQ](/docs/billing-faq) # Assessments URL: /docs/assessments *** title: 'Assessments' description: 'Run DPIAs, privacy impact assessments, California risk assessments, transfer impact assessments, and more from ready-made templates, with review, approval, and a permanent record.' created: '2026-10-30T00:00:00.000Z' updated: '2026-10-30T00:00:00.000Z' ----------------------------------- ## Overview An assessment is a written record showing you thought about the privacy risk in something before you did it. Regulators ask for them by different names in different places, and Concord gives you one place to run all of them. You'll find them under **Data Hub → Assessments**. ## What You Can Do * Start an assessment from a ready-made template * Fill in what you can from records you already keep, instead of retyping * Send it to someone to review, and approve it when it's right * Get reminded when it's time to look at it again * Hand a regulator the exact assessment you approved, even years later ## The Templates Concord ships eight. Pick the one that matches what you're being asked for. | Template | Use it when | | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Data Protection Impact Assessment (GDPR) | European rules say your processing is likely high risk | | Privacy Impact Assessment | You want a general privacy review. It starts with a few questions and tells you whether you need a full DPIA | | Risk Assessment (California) | California requires one before you sell or share personal information, handle sensitive personal information, or let software make significant decisions about people | | Data Protection Assessment (US states) | A US state law asks for one, such as Colorado or Connecticut | | Transfer Impact Assessment | You're sending personal data to another country | | Legitimate Interests Assessment | You're relying on legitimate interests and need to show you weighed it up | | Fundamental Rights Impact Assessment | The EU AI Act asks you to assess an AI system | | Fundamental Rights section | Same as above, but added onto a DPIA you're already doing, so you answer once | The two AI templates are marked provisional. The EU is still writing the official form, and we'll update ours when they publish it. ## Making a Template Your Own You don't have to use ours as-is. Open **Assessments → Templates**, find one, and choose **Customize**. Give the copy a name and it becomes a private template for your organization. Edit it however you like: add questions, remove ones that don't apply, reword anything. Nobody else sees your copy, and we never overwrite it. You can take more than one copy of the same template (say, one DPIA per business unit); each has its own name and its own edits. When we improve the original later, your copy shows an **Update available** note. You choose what happens: * **Apply the changes**: we add what's new and leave your edits alone * **Start over from ours**: throws away your edits and takes the new version * **Dismiss**: keeps your copy exactly as it is and stops asking Anywhere your edits clash with ours, we tell you and change nothing until you decide. ## Building a Template From Scratch Choose **New Template** on the same page, name it, and you get an empty template that belongs to your organization. The builder is the same one our team uses. Drag a question type in from the left, group questions into sections, and see a live preview of the finished assessment as you go. Two things worth knowing: **Questions can depend on answers.** Set a question to show only when an earlier answer says something in particular. If it stays hidden, it isn't asked and it isn't required. **Publishing is a separate step.** Editing a template changes nothing for the people filling it in. When you publish, we tell you whether the change affects the questions themselves or only the wording, so you know whether older answers still line up. ## Filling One In Open an assessment and answer the questions. It saves as you go, and you can leave and come back. **Prefill.** If the assessment is about a processing activity or a system you've already recorded in Concord, choose **Prefill**. We fill in what your records already say: what it's for, whose data, what kinds of data, your legal basis, where it goes, how long you keep it. Every prefilled answer is marked as coming from your records, with a link back to where, and you can change any of it. Nothing is filled in quietly. **Risk findings.** Some assessments ask you to record specific risks. For each one you score how likely it is and how bad it would be, describe what you're doing about it, then score it again afterwards. The second score is the point: it's what shows the safeguards actually helped. Choose **Add a Risk from the Catalog** to start from a standard risk, and say which systems it affects. Risks you record also appear in your [Risk Register](/docs/data-hub-risks). ## Assigning and Sharing You don't have to answer every question yourself. * **Assign to a teammate:** on the assessment's **Assignments** tab, assign the whole assessment, a section, or a single question to a teammate, with a due date. They get a [task](/docs/tasks-my-work) and see it in **My Work**. * **Invite someone outside your organization:** choose **Invite an Outside Respondent**, enter their email, and choose **What to Share**: the whole assessment or one section. They're invited as a guest, sign in with a one-time passcode sent to their email, and can answer only what you shared with them. You can revoke an invite at any time. See [Guest Access](/docs/guest-access). ## Getting It Approved An assessment moves through four steps: 1. **Draft**: anyone assigned to it can edit 2. **In review**: sent to a reviewer, locked from editing 3. **Changes requested**: the reviewer wants something fixed, so it's editable again 4. **Approved** or **Rejected**: the decision is made and the record is fixed On approval we save a permanent copy of the whole assessment exactly as approved. That copy never changes, even if you later reopen the assessment or edit the template it came from. ## Keeping It Current When you approve an assessment you set how often it should be looked at again. When that date arrives we open a task for the owner. We don't reopen the assessment on our own: a compliant record shouldn't quietly stop being approved because a date passed. If something material changes about what you assessed, reopen it yourself. That gives you 45 days and puts the assessment back in draft, with the previous approval kept as history. ## When a Regulator Asks Two things sit ready. **The assessment itself.** Choose **Produce** on any approved assessment and you get it back exactly as approved: the questions as they were worded then, the answers given, the risk findings, and the approval. It doesn't matter how many times the template has changed since. **The annual summary.** California wants a yearly summary rather than the assessments themselves. Concord builds it: how many assessments you did, broken down by the kind of processing each one covered, which categories of personal information were involved, the sworn statement California words for you, who to contact, and who is signing. The assessments stay with you. One thing to know: California requires the person signing to be a senior executive who is responsible for this work and has the authority to submit it. Concord asks for their name and title rather than assuming whoever ran the export is the right person. ## How Assessments Connect to Everything Else Every system, vendor, control and document an assessment mentions gets linked to it. So on any of those pages you can see which assessments cover it, and from an assessment you can see everything it touches. Approving an assessment also files it as evidence against any controls it supports, so your compliance frameworks pick it up without you doing anything. ## What It Costs Assessments are an add-on to the Privacy Premium and Enterprise plans, billed with your subscription. Turn it on under **Global Settings → Billing**, in your plan's **Add-ons**. If the add-on ends, everything you already approved stays readable and exportable; you just can't start or edit assessments until you add it back. # Data Hub: Documents URL: /docs/data-hub-documents *** title: 'Data Hub: Documents' description: 'How to add and manage documents in the Data Hub, including statements, FAQs, links, reports, and policies.' created: '2026-06-14T00:00:00.000Z' updated: '2026-06-14T00:00:00.000Z' ----------------------------------- ## Overview The **Data Hub > Documents** page is a shared global library where you manage compliance-related documents for your organization. Documents you add here, including statements, FAQs, reports, policies, and links, can be featured on your Concord Trust Center for prospects, customers, and partners to review. ![Data Hub: Documents page](/docs/data-hub-documents.png) ## Document Types When you add a document, you first select a document type. Each type has a different content format: | Type | Format | Description | | --------------------- | ------------ | --------------------------------------------------------------------------------------------------------------------------------- | | **Statement** | Text | A public-facing statement or declaration written in Markdown. | | **FAQ** | Text | A frequently asked question with a question and answer pair. | | **Link** | URL | A reference to an external URL or resource. | | **FAQs (via Import)** | Spreadsheet | Bulk-create FAQs from a spreadsheet. Review and edit every row before importing. | | **Report** | File or Text | A compliance or audit report. Upload a file or enter content directly. | | **Policy** | File | A legal or compliance document such as a privacy policy, cookie policy, or terms of service. You can also use the Policy Builder. | ## Adding a Document The Add Document flow is a three-step wizard: **Type, Content, Details**. ### Step 1: Select Document Type 1. In the Concord Admin UI, go to **Data Hub > Documents**. 2. Click **Add Document**. 3. Select the document type that matches what you want to add. 4. Click **Next**. ![Add Document wizard: Type selection](/docs/data-hub-add-document-type.png) ### Step 2: Add Content The content step varies by document type: * **Statement:** Write your statement content in Markdown. * **FAQ:** Enter the question and answer. * **Link:** Enter the external URL. * **FAQs (via Import):** Upload a spreadsheet file. Review and edit each row before importing. * **Report:** Upload a file or enter the report content directly as text. * **Policy:** Upload a policy file, or use the Policy Builder to create one. Click **Next** when your content is ready. ### Step 3: Configure Details Configure the document metadata: * **Name:** A display name for the document. * **Description:** A description of the document. * **Category:** The category the document belongs to. * **Access Level:** Controls who can see this document when it is featured on your Trust Center. Click **Save**. The document is now in your global document library. ## Featuring Documents on Your Trust Center Adding a document to the Data Hub makes it available in your global library. To display it on your Trust Center for customers and prospects: 1. Go to **Trust > Trust Center**. 2. Select which documents from your global library to feature. 3. Featured documents appear on your Trust Center according to their access level setting. This two-step approach (add globally, then feature selectively) lets you maintain a complete document library while controlling exactly what external visitors see. ## Viewing and Filtering Documents The Documents table in **Data Hub > Documents** shows all documents in your library with the following columns: * **Name:** The document name. * **Type:** The document type (Statement, FAQ, Link, Report, or Policy). * **Category:** The document category. * **Status:** Active or Archived. * **Access Level:** Who can access the document. * **Date Created:** When the document was added. Use the **All**, **Active**, and **Archived** tabs to filter by status. You can also sort and filter individual columns. ## Live Policy Sync If you use Concord Privacy for policy management, your policies can be displayed on your Trust Center automatically through the shared Data Hub. When you update a policy in Concord Privacy (such as your Privacy Policy or Cookie Policy), the Trust Center reflects the current version without any manual re-upload. Synced policies appear alongside your other documents in the Trust Center. This means your visitors always see the latest version. ## Editing a Document 1. Go to **Data Hub > Documents**. 2. Click on the document you want to edit. 3. Update the details as needed. 4. Click **Save**. ## Deleting a Document 1. Go to **Data Hub > Documents**. 2. Click on the document you want to delete. 3. Click **Delete**. Deleting a document removes it from your global library and from your Trust Center if it was featured. ## Related Articles * [Data Hub Overview](/docs/data-hub-overview) * [Data Hub: Systems](/docs/data-hub-systems) * [Data Hub: Processing Activities](/docs/data-hub-processing-activities) # Data Hub Overview URL: /docs/data-hub-overview *** title: 'Data Hub Overview' description: 'Overview of the Data Hub in Concord, including Systems, Processing Activities, Documents, Vendors, and Controls and Audits.' created: '2026-06-14T00:00:00.000Z' updated: '2026-09-28T00:00:00.000Z' ----------------------------------- ## Overview The Data Hub is where you manage your organization's inventory of data systems, processing activities, vendors, and compliance documents, along with the controls and audits behind your compliance program. It provides a centralized view of the technology systems your organization uses, how data flows through them, and the documentation that supports your compliance posture. Data Hub is available to all Concord customers with Concord Privacy, Concord Trust, or both. The features available depend on your plan. ## What's in the Data Hub The Data Hub sidebar contains these sections: * **Systems:** Add and manage the technology systems your organization uses (e.g., CRM, cloud storage, analytics platforms). Every Data Hub plan includes the ability to add, edit, archive, and delete systems with basic details. Customers on plans that include Data Mapping can also configure processing info, data flow, security measures, and contacts for each system. * **Processing Activities:** Define and document how your organization processes personal data across systems. Available on plans that include Data Mapping. * **Documents:** Upload and organize compliance-related documents such as DPAs, DPIAs, and vendor agreements. Available on plans that include Data Mapping. * **Vendors:** Keep an inventory of the third parties that process data for you, link them to the data systems they provide, and publish them as sub-processors on your Trust Center. See [Managing Vendors and Sub-Processors](/docs/managing-vendors). * **Controls & Audits:** Controls, Frameworks, Evidence, and Audits for your compliance program, on Concord Trust **Premium** and **Enterprise**. See [Controls and Evidence](/docs/controls-overview). Connections to outside systems, such as cloud accounts, live under **Integrations**, a separate section of the sidebar. See [Automated Control Checks](/docs/automated-control-checks). ## Feature Availability by Plan | Feature | Privacy with Data Mapping | Privacy without Data Mapping | Trust Only | | ------------------------------------------------------------------------ | :-----------------------: | :--------------------------: | :--------: | | Documents | Yes | Yes | Yes | | Data Systems (Name, Status, Relationship, Notes) | Yes | Yes | Yes | | Associate Data Systems w/ Privacy Projects | Yes | No | No | | Data System Attributes (Processing, Data Flow, Security, Contacts, etc.) | Yes | No | No | | Processing Activities | Yes | No | No | Customers on plans without Data Mapping will see a simplified Add Data System wizard with two steps (Type and Details). The system detail view will show the basic fields only. ## Getting Started * To add and manage systems, see [Data Hub: Systems](/docs/data-hub-systems). * To configure processing, data flow, security, and contact attributes (Data Mapping required), see [Data Hub: System Attributes](/docs/data-hub-system-attributes). * To document your organization's processing activities (Concord Privacy required), see [Data Hub: Processing Activities](/docs/data-hub-processing-activities). * To manage compliance documents, policies, and reports, see [Data Hub: Documents](/docs/data-hub-documents). # People and Policy Acknowledgements URL: /docs/data-hub-people *** title: 'People and Policy Acknowledgements' description: 'Keep a list of your personnel, require the policies and training they must complete, record background checks and offboarding, and export the evidence auditors ask for.' created: '2026-10-30T00:00:00.000Z' updated: '2026-10-30T00:00:00.000Z' ----------------------------------- ## Overview Auditors for SOC 2 and ISO 27001 want proof that your staff read and accepted your current policies, completed security training, were screened when they joined, and lost access when they left. **People** keeps that record in one place, in **Data Hub → People**, and turns it into control evidence automatically. People has five tabs: **Personnel**, **Policies**, **Training**, **Background Checks**, and **Groups**. ## Who Can Use People People is part of Concord Trust **Premium** and **Enterprise**. Owners and Admins manage it. Everyone listed completes their own policies on **Your Policies** and their training on **Your Training**, whether or not they have a Concord account (see [How People Acknowledge](#how-people-acknowledge)). ## Adding People 1. Go to **Data Hub → People → Personnel**. 2. Add a person, or choose **Import CSV** from the menu to add many at once. 3. For each person, set whether they're an **employee** or a **contractor**, and add a start date if you have one. Adding a person never sends them an email. Emails go out only when you send them yourself or when the weekly reminder runs. ## Groups Groups decide who owes which policy or training. * **All Personnel** is built in and always includes everyone. * Create other groups on the **Groups** tab, such as Engineering or Customer Support, and add people from the group or from the person's form. * A group that is the only one assigned to a policy can't be deleted. Someone who joins a group, or whose group is assigned a policy later, owes it from that date and gets the full time to complete it. ## Requiring Policies 1. Open the **Policies** tab and add a required policy. 2. Choose a published policy. Policies written in Concord and uploaded PDF or DOCX policies both work. 3. Choose the groups who must acknowledge it. **All Personnel** is the default. Each policy shows how many people have acknowledged it and who is overdue. Someone is overdue once **Days to Acknowledge** has passed (30 days by default, see [Settings](#settings)). ### Asking Everyone Again When a policy changes, you can start a new round so everyone acknowledges the new version: * Choose **Ask Everyone Again** on People, or * Tick the option in the **Publish** dialog when you publish the new version. ## Requiring Training Training works the same way as policies. Create the training in **Documents → Training**, optionally with a short quiz (see [Training and Quizzes](/docs/training-quizzes)), then require it on the **Training** tab and assign it to groups. * People complete in-app training on **Your Training**. When the training has a quiz, the score that passed it is recorded. * For training done on another platform, choose **Record Completion**, pick who completed it and when, and add an **Evidence Link** to the provider's completion record. Upload a certificate only when there's no link. * A completion counts for one year. Training completed more than a year ago can't be recorded for the current round. ## How People Acknowledge Everyone acknowledges policies on **Your Policies** and completes training on **Your Training**. Each page is one table of everything they owe, are overdue on, or have completed. * **People with a Concord account** open these pages from the email, or from their task in **My Work**. * **People without a Concord account** are invited as guests. The button in their email signs them in with a one-time passcode sent to their address. They see only their own policies and training, and offboarding them ends that access. Opening an owed policy shows it in full with a statement to tick. Opening one they already acknowledged shows the exact version they agreed to. Each acknowledgement is recorded permanently and pinned to the version they saw: the version and its content fingerprint, the policy name, their name and email at the time, the time, and their IP address and browser. Acknowledgement records can't be edited or deleted. ## Reminders * **Email Outstanding** emails everyone who still owes something. * **Send Link** on a person's row emails just that person. * A weekly reminder goes out automatically to everyone with something outstanding, plus one more a set number of days before it's due (**Reminder Days Before Due** in [Settings](#settings)). ## Offboarding When someone leaves, offboard them instead of deleting them. People with acknowledgements can be offboarded but never deleted, so the audit history stays intact. When you offboard someone, record when their system access was removed, with an optional link to the ticket, or mark it **Not Required** and say why. **Days to Remove Access** (1 day by default) sets how quickly access must be removed after their end date. ## Background Checks The **Background Checks** tab records that each person was screened, without storing the screening report itself. 1. Choose **Record Background Checks** and pick the people. 2. Choose the outcome: **Completed**, with the date and an evidence link to the result in your screening provider, or **Not Required**, with the reason (for example, the role has no access to customer data, or local law doesn't allow it). 3. Upload a file only when there's no link, and only a one-page summary or certificate, never the full report. Background check records can't be changed. To correct one, record a new one; auditors rely on earlier records staying as they were. ## Evidence for Audits People feeds your [controls](/docs/controls-overview) automatically: * **Policy acknowledgement** and **Code of Conduct acknowledgement** controls pass when everyone in scope has acknowledged the current version. * **Offboarding** controls pass when access was removed in time. * **Background check** controls pass when everyone has a completed or not-required check. From the menu, you can also export: * **Export Personnel:** everyone who was active during an audit window you choose. * **Export Acknowledgement Log:** every acknowledgement, with the version and time. ## Settings Choose **Settings** from the People menu: | Setting | What it does | | ---------------------------- | ---------------------------------------------------------------------------------- | | **Days to Acknowledge** | How long someone has to acknowledge a required policy before they're overdue. | | **Days to Remove Access** | How long after someone leaves their system access must be removed. | | **Reminder Days Before Due** | When to send one extra reminder before something is due, on top of the weekly one. | # Data Hub: Processing Activities URL: /docs/data-hub-processing-activities *** title: 'Data Hub: Processing Activities' description: 'How to add, view, edit, and manage processing activities in the Concord Data Hub.' created: '2026-06-14T00:00:00.000Z' updated: '2026-06-14T00:00:00.000Z' ----------------------------------- ## Overview The **Data Hub > Processing Activities** page is where you define and document how your organization processes personal data. Processing activities describe specific business operations that involve collecting, storing, or using personal data, such as "Customer Onboarding," "Marketing Email Campaigns," or "Employee Payroll." Documenting your processing activities is a key requirement for GDPR compliance (Article 30 requires a Record of Processing Activities, or ROPA) and helps demonstrate accountability across other privacy regulations. > Processing Activities is only visible in the Admin UI for customers subscribed to Concord Privacy. If your organization has Concord Trust but not Concord Privacy, this section will not appear in the Data Hub sidebar. ## Viewing Processing Activities 1. In the Concord Admin UI, go to **Data Hub > Processing Activities**. ![Processing Activities page](/docs/data-hub-processing-activities.png) The Processing Activities table shows all activities in your organization with the following columns: | Column | Description | | ---------- | ------------------------------------------------------------ | | **Name** | The name of the processing activity. | | **Status** | Active or Test. Active activities are included in your ROPA. | Use the tab bar to switch between the main list and related configuration pages: * **Processing Activities:** The main list of all processing activities. * **Article 9 Conditions:** Special category processing conditions under GDPR Article 9. * **Legal Bases:** The legal bases that apply to your data processing (e.g., consent, legitimate interest, contractual necessity). * **Legitimate Interests:** Documented legitimate interest assessments. ## Adding a Processing Activity 1. Go to **Data Hub > Processing Activities**. 2. Click **Add Processing Activity** in the upper right corner. 3. **Select a template.** Choose a pre-built template to pre-fill details like data subjects, categories, and legal basis. Select **Custom** to start from scratch. Available templates include: * Billing * Business & Customer Intelligence * Consent Management * Customer Lifecycle Management * Customer Service * Event Registration & Attendance * Expense Management * Human Resources & Employee Development * Internal Communications * Lead Generation & Management * Loyalty Program * Marketing Automation * Personalization * Recruiting & Applicant Management ![Add Processing Activity wizard, template selection](/docs/data-hub-add-processing-activity-type.png) 4. Click **Next** and select the **Data Systems** associated with this processing activity. You can select any systems already added to your organization in the Data Hub. 5. Click **Next** and fill in the **Details**: ![Add Processing Activity wizard, details step](/docs/data-hub-add-processing-activity-details.png) * **Name** (required): A clear, specific name that identifies the purpose of the processing. * **Description:** The nature and scope of the processing, including what data is collected and why. * **Status:** Set to **Active** (included in your ROPA) or **Test** (for internal review only). 6. Click **Next** and configure **Processing** attributes: * **Data Categories:** The types of personal data processed in this activity. * **Data Subjects:** The types of individuals whose data is processed. * **Processing Purposes:** The purposes for processing the data. * **Legal Basis:** The legal justification for processing (e.g., consent, legitimate interest, contractual necessity). * **Article 9 Conditions:** If special category data is processed, the applicable Article 9 condition. 7. Click **Next** and configure **Data Flow** attributes: * **Data Origins:** Where the data originates from. * **Data Destinations:** Where the data is sent to and who it is shared with. * **Data Retention Period:** How long data is retained for this activity. * **Cross-Border Transfer:** Whether data is transferred across international borders. 8. Click **Next** and configure **Security** measures, then click **Done**: * **Security Measures:** The security measures in place for this processing activity. The processing activity appears in the table immediately. ## Editing a Processing Activity 1. Go to **Data Hub > Processing Activities**. 2. Click the name of the activity you want to edit, or click the **Actions** menu (three dots) and select **Edit**. 3. Update the fields as needed and click **Save**. ## Deleting a Processing Activity 1. Go to **Data Hub > Processing Activities**. 2. Click the **Actions** menu (three dots) for the activity you want to remove. 3. Select **Delete** and confirm. ## Managing Article 9 Conditions, Legal Bases, and Legitimate Interests Use the tabs on the Processing Activities page to manage the configuration options used across your processing activities: * **Article 9 Conditions:** Add, edit, or delete the special category conditions available when configuring processing activities that involve sensitive data (e.g., health, biometrics, political opinions). * **Legal Bases:** Add, edit, or delete the legal basis options used to justify processing. Predefined options include Consent, Legitimate Interest, Contractual Necessity, Legal Obligation, Vital Interest, and Public Interest. * **Legitimate Interests:** Document legitimate interest assessments that support your use of legitimate interest as a legal basis. ## Related Articles * [Data Hub Overview](/docs/data-hub-overview) * [Data Hub: Systems](/docs/data-hub-systems) * [Data Hub: Documents](/docs/data-hub-documents) # Risk Register URL: /docs/data-hub-risks *** title: 'Risk Register' description: 'Record the risks your organization faces, score them before and after treatment, link them to the controls that reduce them, and review them on a schedule.' created: '2026-10-30T00:00:00.000Z' updated: '2026-10-30T00:00:00.000Z' ----------------------------------- ## Overview The **Risk Register** in **Data Hub → Risks** is where you keep track of what could go wrong, how likely and how harmful it is, and what you're doing about it. SOC 2, ISO 27001, and most privacy laws expect a documented, regularly reviewed risk assessment, and the register gives auditors one place to see it. Each risk has an owner, a category, an **inherent** score (before treatment), a **residual** score (after treatment), a treatment plan, and a review schedule. Risks can link to the controls that reduce them and to the vendor they came from. ## Who Can Use the Risk Register The Risk Register is included in **Premium** and **Enterprise** plans of Concord Privacy or Concord Trust. Linking risks to controls also needs [Controls](/docs/controls-overview), which are part of Concord Trust Premium and Enterprise. ## Adding Risks Go to **Data Hub → Risks** and add a risk. You can start from Concord's library of common risks, which fills in the description and suggests the controls that usually reduce it, or write your own. For each risk, set: * **Title**, **description**, and **category**. * **Owner:** the teammate responsible for it. * **Inherent likelihood** and **impact:** how likely the risk is and how bad it would be, before anything is done about it. * **Review frequency:** annual, semi-annual, or quarterly. Each risk gets a reference like `R-001`. ### Importing and Exporting To add or update many risks at once, choose **Import CSV** from the register's menu. Only a title column is required. A row whose key matches an existing risk, such as `R-004`, updates that risk instead of creating a duplicate, and rows with problems are reported one by one without stopping the rest of the file. Owners are matched by email. Choose **Export CSV** to download the register at any time. ## Scoring A risk's score is its likelihood multiplied by its impact. The score falls into a severity band, such as Low, Medium, High, or Critical, and the register shows each risk's band and a heatmap of the whole register. The scale (5 by 5 by default) and the bands are yours to change: choose **Scoring** from the register's menu. Before you save, the page shows how your existing risks would move between bands, because changing a band re-scores every risk. ## Treating Risks On a risk's **Treatment** tab, choose a strategy: | Strategy | Meaning | | ------------ | -------------------------------------------------------- | | **Mitigate** | Reduce the risk, usually with controls. | | **Transfer** | Shift it to someone else, for example through insurance. | | **Accept** | Live with it, with a recorded reason. | | **Avoid** | Stop the activity that causes it. | Any strategy other than untreated needs a rationale. **Mitigate** and **Transfer** also take a **residual** likelihood and impact, so you can show how much the treatment reduced the risk. When a mitigate, transfer, or avoid plan has a target date, Concord creates a task for the risk owner in [My Work](/docs/tasks-my-work). Accepting the risk, closing it, or archiving it resolves that task. ## Linking Controls On a risk's **Linked Controls** tab, link the controls that reduce it. Each linked control shows whether it's currently passing, so you can see at a glance whether a mitigated risk is really covered. The register flags risks with no linked controls. ## Reviewing Risks Every risk has a next review date based on its review frequency. When a review is due, the owner gets a task, and one nightly check makes sure each overdue risk has exactly one review task. Choose **Record Review** on a risk to log the review. The reviewer can update the scores at the same time, and the next review date moves forward. ## Where Risks Come From Besides adding risks yourself, risks can come from other parts of Concord: * **Vendor reviews:** a finding in a [vendor review](/docs/managing-vendors#reviewing-vendors) can become a risk linked to that vendor. * **Assessments:** findings in an [assessment](/docs/assessments) can be promoted to the register. ## Reports Choose **Reports** from the register's menu to see the inherent and residual heatmaps, how many risks fall in each band and status, how many have a linked control, and how many reviews are overdue. # Data Hub: System Attributes URL: /docs/data-hub-system-attributes *** title: 'Data Hub: System Attributes' description: 'How to add, edit, and delete data system attribute types such as Relationships, Origins, Destinations, and more.' created: '2026-06-14T00:00:00.000Z' updated: '2026-06-14T00:00:00.000Z' ----------------------------------- ## Overview Data system attributes let you categorize and describe the data flowing through your systems. You can manage attribute types from the **Data Systems** tab bar or directly within an individual system's detail page. > This feature requires a Concord Privacy plan that includes Data Mapping. Customers without Data Mapping can add systems with basic details (Name, Status, Relationship, Notes) but cannot configure attribute types. ## Attribute Types The Data Systems page includes tabs for managing each attribute type. You can view, add, edit, and delete entries for: * **Relationships:** The relationship your organization has with a data system. Predefined options: Controller, Joint Controller, Processor, Sub-Processor. You can also create custom relationship types. * **Origins:** Where the data in a system originates from. Predefined options include Legacy Data Systems, 3rd Party Data Provider(s), Integrated Data System(s), Built-In Data Collection, and User Submitted Forms. * **Destinations:** Where the data is sent to and who it is shared with. Predefined options include Data Partners, Payment Processors, Analytics Providers, Security & Fraud Vendors, Auditors & Compliance Vendors, Researchers & Academic Institutions, Law Enforcement & Government, and Advertisers & Advertising Platforms. * **Processing Purposes:** What the data is used for. Predefined options include Business Operations, Sales & Account Management, Customer Support, Security & Fraud, Analytics, and Advertising. * **Data Subjects:** The types of individuals whose data is processed. * **Data Categories:** The types of personal data stored. Predefined options include Military Status, Location, Demographics, Business/Company, Employment, Education, Device, IP Address, User Generated Content, and Credit/Payment Card Number. * **Security Measures:** The measures in place to protect data. Predefined options include Reviews & Audits, Training & Awareness, Risk Management, Information Security Program, ISO 27001 Compliance, SOC 2 Compliance, and Multi-Factor Authentication. * **Contacts:** The people at your company or partner companies associated with a data system. In addition to the predefined options, you can create custom entries for all of the above categories. ## Adding an Attribute Type The process is the same for all attribute types. This example walks through adding a new Destination. 1. Go to **Data Hub > Systems**. 2. Navigate to the **Destinations** tab. ![Destinations tab with Add Destination button](/docs/managing-data-system-attributes-add-destination.webp) 3. Click **Add Destination** in the upper right corner. 4. Enter a **Name** (required) and **Description** (optional), then click **OK**. ![Add Destination dialog](/docs/managing-data-system-attributes-add-destination-modal.webp) The new entry appears in the list and is immediately available for use when adding or editing data systems. ## Editing an Attribute Type 1. Go to the relevant attribute tab on the Data Systems page. 2. Click the **Actions** menu (three dots) for the entry you want to update. 3. Select **Edit**, update the fields, and click **OK**. ## Deleting an Attribute Type 1. Go to the relevant attribute tab on the Data Systems page. 2. Click the **Actions** menu (three dots) for the entry you want to remove. 3. Select **Delete** and confirm. Deleting an attribute type removes it from the list of available options. Existing data systems that reference the deleted attribute will retain the association until the system is edited. > Attributes can also be added directly from the Add Data System wizard or from within an individual system's detail page. Any attribute you create in-line is saved to the organization-wide attribute list. ## Related Articles * [Data Hub Overview](/docs/data-hub-overview) * [Data Hub: Systems](/docs/data-hub-systems) # Data Hub: Systems URL: /docs/data-hub-systems *** title: 'Data Hub: Systems' description: 'How to add, view, edit, archive, and delete data systems in the Concord Data Hub.' created: '2026-06-14T00:00:00.000Z' updated: '2026-06-14T00:00:00.000Z' ----------------------------------- ## Overview The **Data Hub > Systems** page is where you catalog the technology systems your organization uses. Adding your data systems gives you a structured inventory of the vendors, tools, and internal applications in your environment, which is foundational to demonstrating your security and compliance posture. Systems you add in the Data Hub can be referenced across Concord as part of your compliance documentation, vendor management program, and privacy request fulfillment. ## Viewing Your Data Systems 1. In the Concord Admin UI, go to **Data Hub > Systems**. ![Data Hub Systems table](/docs/data-hub-systems.png) The Systems table shows all data systems in your organization with the following columns: | Column | Description | | ---------------- | ------------------------------------------------------------------------------ | | **Name** | The display name of the system. | | **Type** | The category of system (e.g., CRM, Cloud Storage, HR). | | **Relationship** | Your organization's relationship to this system (Controller, Processor, etc.). | | **Status** | Active, Test, or Archived. | | **Actions** | Options to edit, archive, or delete the system. | Click the **+** icon to the left of any row to expand it and see additional details such as the Data System ID, Origins, Destinations, Processing Purposes, Data Categories, Security Measures, Contacts, and more. Click the system name to open the full detail view. ## Adding a Data System 1. Go to **Data Hub > Systems**. 2. Click **Add Data System** in the upper right corner. ![Add Data System button](/docs/data-hub-systems-add-button.png) 3. **Select the system type.** Start typing to search, or scroll to browse available system types. Concord provides 100+ pre-built templates. If your system is not listed, select **Custom**. ![Add Data System wizard, type selection](/docs/data-hub-add-system-type.png) 4. Click **Next** and fill in the system details: ![Add Data System wizard, details form](/docs/data-hub-add-system-details.png) * **Name:** The display name for the system in Concord. * **Status:** Set to **Active**, **Test**, or **Archived**. * **Relationship:** Your organization's role with respect to this system: * **Controller:** Your organization determines the purpose and means of processing data in this system. * **Processor:** This system processes data on behalf of a controller (e.g., a SaaS vendor). Internally managed systems are usually a Controller; external SaaS products are usually a Processor. * **Joint Controller:** Two or more parties jointly determine how data is processed. * **Sub-Processor:** A third party engaged by a processor who also accesses the data. * **Projects:** Associate this system with one or more of your Concord projects. * **Additional Notes:** Any context about this system you want to record. 5. Add **Processing** attributes (optional) and click **Next**: * **Data Categories:** The categories of data being processed. * **Data Subjects:** The types of individuals whose data is processed. * **Processing Purposes:** The purposes for which data is processed. * **Processing Activities:** The activities performed on the data. ![Add Data System wizard, processing step](/docs/add-data-system-processing.webp) 6. Add **Data Flow** attributes (optional) and click **Next**: * **Data Origins:** Where the data in this system originates from. * **Data Destinations:** Where the data is sent to and who it is shared with. * **Data Retention Period:** How long data is held in this system. The default is 12 months. * **Cross-Border Transfer:** Whether data is transferred across international borders. ![Add Data System wizard, data flow step](/docs/add-data-system-data-flow.webp) 7. Add **Security** measures (optional) and click **Next**: * **Security Measures:** The security measures implemented for this data system such as audits, MFA, training, SOC 2 Compliance, etc. ![Add Data System wizard, security step](/docs/add-data-system-security.webp) 8. Add **Contacts** (optional) and click **Done**: * **Contacts:** Select the contact(s) responsible for this data system. The data system appears in the Systems table immediately. > **Plans without Data Mapping:** If your plan does not include Data Mapping, the Add Data System wizard has two steps: Type and Details. The Details step includes Name, Status, Relationship, and Additional Notes. The Projects field and the Processing, Data Flow, Security, and Contacts steps are not available. ## Viewing a System's Detail Page Click on a system name in the table to open its detail page. ![System detail view](/docs/data-hub-system-detail-view.png) The detail page displays: * The system name, type, status, and relationship at the top. * Summary cards for Categories, Purposes, Activities, Origins, Destinations, Security, and Contacts. * Metadata: data retention period, cross-border transfer status, and last updated date. * Tabbed sections for **Details**, **Processing**, **Data Flow**, **Security**, and **Contacts** where you can edit each area. > **Plans without Data Mapping:** The detail page shows the Details tab with Name, Status, Relationship, and Additional Notes. The Processing, Data Flow, Security, and Contacts tabs and the summary cards are not displayed. ## Editing a Data System 1. Go to **Data Hub > Systems**. 2. Find the system you want to update. 3. Click the system name to open the detail view, or click the **Actions** menu (three dots) on the right side of the row and select **Edit**. 4. Update the fields as needed and click **Save Changes**. ## Archiving a Data System Archiving removes a system from your active inventory without permanently deleting it. Use this when a system is no longer in use but you want to retain its history. 1. Go to **Data Hub > Systems**. 2. Click the **Actions** menu (three dots) for the system you want to archive. 3. Select **Archive**. Archived systems move to the **Archived** tab. You can restore an archived system at any time by going to the Archived tab, opening the Actions menu, and selecting **Restore**. ## Deleting a Data System Deleting a system permanently removes it from Concord. This action cannot be undone. 1. Go to **Data Hub > Systems**. 2. Click the **Actions** menu (three dots) for the system you want to delete. 3. Select **Delete** and confirm the action. If you are unsure whether you need the system record in the future, archive it instead of deleting it. ## Connecting Data Systems to a Project You can associate data systems with specific Concord projects from two places: * **From the Add Data System wizard or system detail page:** Use the **Projects** field to select one or more projects. This field is available on plans that include Data Mapping. * **From Global Settings:** Go to **Global Settings > Projects**, click the Actions menu for a project, and select **Edit Project**. Use the Data Systems selector to add or remove systems. ## Related Articles * [Data Hub Overview](/docs/data-hub-overview) * [Data Hub: System Attributes](/docs/data-hub-system-attributes) # Tasks and My Work URL: /docs/tasks-my-work *** title: 'Tasks and My Work' description: 'Track compliance work as tasks your team can assign, prioritize, and close, and see everything assigned to you in My Work.' created: '2026-10-30T00:00:00.000Z' updated: '2026-10-30T00:00:00.000Z' ----------------------------------- ## Overview Compliance work happens in many places: a vendor review comes due, a privacy request needs an answer, a risk needs treating, a scan fails. **Tasks** pull that work into one list, so nothing waits on someone remembering it. * **Data Hub → Tasks** is your organization's full task list. * **My Work** is your own: your notifications, the tasks assigned to you, and the policies, training, and assessments you owe. Tasks are available on every plan, to anyone whose role can view them. ## Tasks Concord Creates for You Many tasks appear on their own, assigned to the right person, and close when the work is done: * **Risks:** a treatment plan with a target date, and every review that comes due ([Risk Register](/docs/data-hub-risks)). * **Vendors:** scheduled vendor reviews, and documents about to expire ([Managing Vendors](/docs/managing-vendors)). * **Privacy requests:** on Concord Privacy Premium and Enterprise, one task per request, assigned to the project's default assignee and due when the request is due ([Managing Privacy Requests](/docs/managing-privacy-requests)). * **Scans:** a compliance scan that failed and needs a look. * **Controls:** a control test that fails ([Controls and Evidence](/docs/controls-overview)). * **Assessments:** a question or section assigned to you ([Assessments](/docs/assessments)). * **People:** policies and training someone still owes ([People](/docs/data-hub-people)). Concord never stacks duplicates: each item has at most one open task, and finishing the work resolves it. ## Creating a Task 1. Go to **Data Hub → Tasks** and choose **Create Task**. 2. Give it a title and an optional description. 3. Choose what it's about: a general task, or one linked to a control, data system, privacy request, or other record. A linked task opens its record in one click. 4. Set the **Assignee**, **Priority** (low, medium, high, or urgent), and **Due Date**. ## Working Tasks Each task moves through **Backlog**, **To Do**, **In Progress**, **Done**, or **Cancelled**. Open a task to change its details, status, or assignee. Filter the list by status, assignee, or priority, switch between open and closed tasks, or search by title. **Assigned to Me** shows only your tasks. For a privacy request task, changing the due date also changes the request's due date, so the two never disagree. ## My Work **My Work** in the sidebar collects everything that's yours in an organization: | Page | What it shows | | ----------------- | --------------------------------------------------------------------------------------------- | | **Notifications** | Your notifications. See [Notification Settings](/docs/notification-settings). | | **Tasks** | Tasks assigned to you. | | **Policies** | Policies you need to acknowledge. See [People](/docs/data-hub-people#how-people-acknowledge). | | **Training** | Training you need to complete. | | **Assessments** | Assessments shared with you to answer. | **Policies**, **Training**, and **Assessments** appear only when you have some. Guests, such as staff without a full Concord account, see only My Work. See [Guest Access](/docs/guest-access). # Training and Quizzes URL: /docs/training-quizzes *** title: 'Training and Quizzes' description: 'Create security, privacy, AI, HIPAA, and secure coding training from Concord templates or upload your own, add a quiz people must pass, and turn completions into control evidence.' created: '2026-10-30T00:00:00.000Z' updated: '2026-10-30T00:00:00.000Z' ----------------------------------- ## Overview Most frameworks expect your staff to complete security training when they join and every year after. Concord lets you write that training, quiz people on it, and track who completed it, without a separate training platform. Completions feed your training controls automatically. Training is part of [People](/docs/data-hub-people), included in Concord Trust **Premium** and **Enterprise**. ## Creating Training Go to **Documents → Training** and choose **Add Training**. You can: * **Create with Training Builder:** pick a template and answer a few questions. Concord writes the training and a quiz to go with it, both of which you can edit. * **Upload Existing Training:** upload slides or a document you already have, then add a quiz if you like. The Training Builder includes these templates: | Template | Covers | | ----------------------------------- | --------------------------------------------------------------------------------------- | | Security Awareness Training | Phishing, accounts, devices, data handling, and reporting | | Privacy Awareness Training | Handling personal data under GDPR and US state privacy laws, requests, and breaches | | AI Awareness Training | Approved AI tools, protecting data, checking output, and human oversight | | HIPAA Privacy and Security Training | What PHI is, the minimum necessary rule, safeguards, vendors, and reporting breaches | | Secure Coding Training | Untrusted input, access checks, secrets, dependencies, protecting data, and code review | By default you see the templates for your frameworks. Choose **Show all templates, including other frameworks** to see the rest. Like a policy, training is a draft until you publish it. Only published training can be required of your staff. ## Adding a Quiz Open the training and go to its **Quiz** tab. A quiz is optional: without one, people read the training and confirm they completed it. * Add up to 20 questions. Each is **Single Choice**, **Dropdown**, or **Multiple Choice** (select all that apply), so Concord can mark it automatically. * For each question, tick the **Right Answers**. Single Choice and Dropdown questions have one; Multiple Choice can have several. * Set the **Pass Mark (%)**. It starts at 80%. Quiz changes reach your staff when you publish the training, together with any content changes. ## Requiring Training On **Data Hub → People → Training**, choose **Add Training**, pick the published training, and choose the groups who must complete it. Training gets the same due dates and [reminders](/docs/data-hub-people#reminders) as policies. To count training done on another platform, see [Requiring Training](/docs/data-hub-people#requiring-training). A completion counts for one year, so people owe the training again each year. To ask everyone again sooner, for example after a big update, see [Asking Everyone Again](/docs/data-hub-people#asking-everyone-again). ## Taking Training People find their training on **Your Training**, under **My Work**. They open it, go through the content, answer the quiz, and tick the box to confirm. If they don't reach the pass mark, Concord marks the answers to change and they can try again straight away. Nothing is recorded until they pass. When they pass, the completion is recorded with their score, the exact version they completed, and when. Staff without a Concord account take training the same way, as [guests](/docs/guest-access). ## Training as Control Evidence When you run [Controls](/docs/controls-overview), completions become evidence for the matching automated check: * **Security Awareness Training (CR-HRS-03):** training from the Security Awareness, Privacy Awareness, HIPAA, and Secure Coding templates. * **AI Training (CR-AI-01):** training from the AI Awareness template. Training from a template counts automatically. For training you uploaded, choose the check in **Counts Toward** when you require it. # Adding Projects URL: /docs/adding-projects *** title: 'Adding Projects' description: 'How to add new Projects to your Organization.' created: '2021-05-13T20:44:47.000Z' updated: '2024-10-18T16:45:58.000Z' ----------------------------------- ## Overview * Concord uses Projects as the basic unit of deployment and configuration. * This article provides instructions on adding a new project to your Organization. * To learn more about how projects work, refer to this article: [Projects Overview](/docs/projects-overview) ## Step 1: Add a Project * Login to Concord’s Admin UI. * If this is your first login, a website project setup wizard will automatically start. Otherwise, click on **Global Settings -> Projects** and **click the** +Add Project \*\*button. This will launch the Project Wizard. ![](/docs/adding-projects-nav-global-settings-projects.png) ## Step 2: Name the Project and Add the Domain * Give your **Project** a descriptive name. Should you believe you will need multiple Projects (for example, because you have many different websites that may require different configurations) it is advisable to establish a systematic naming convention. * List the domain with which the Project will be associated. The UI will confirm if you have entered a properly formatted domain. It is not necessary to prepend “http\://” or “https\://” to your domain. ![](/docs/adding-projects-add-project-wizard-projects-dark.png) ## Step 3: Link to your Privacy Policy and Terms of Service * Input a valid URL that links to your online Privacy Policy. Note that in this case, you will have to prepend “http\://” or “https\://”. * (Optional) Input a valid URL that links to your Terms of Service if your site has one. Note that in this case, you will have to prepend “http\://” or “https\://”. ![](/docs/adding-projects-add-project-wizard-disclosures-dark.png) ## Step 4: Choose the Color for Your Privacy Center Widget (Optional) * Choose a color that will be used for your Privacy Center website widget. * You can either choose a new pre-existing color by clicking on any of the default colors shown or you can input a Hexadecimal color value (for example: “#22194D”). * If you do not know the proper Hexadecimal color value for your desired branding, you may search online for “hexadecimal color picker” to find free tools for choosing a color and finding its hexadecimal value. ![](/docs/adding-projects-add-project-wizard-colors-dark.png) ## Step 5: Upload a Logo (Optional) * Click on the logo icon and navigate to your saved logo file. * Logo file size is limited 512KB. * Logos are restricted to .png formats. * There are no height or width restrictions, but logos are resized in the widget to a max-height of 40px so 40px is the preferred height. ![](/docs/adding-projects-add-project-wizard-logo-dark.png) ## Step 6: Input Email Addresses for Project Notifications (Optional) * Emails can be added to your Project under Additional Notification Email(s). Those emails receive notifications for that Project and should typically be used for catch-all emails vs. notifications for specific users (as all users added to a project can instead manage their own notification settings without being added to the Additional Notification Email(s) section). ![](/docs/adding-projects-add-project-wizard-email-dark.png) * Click **Done** when complete. You have configured your Project. # Assigning Send From Emails to Projects URL: /docs/assigning-send-from-emails *** title: 'Assigning Send From Emails to Projects' description: 'Step-by-step guide to assigning Send From Emails to Projects.' created: '2021-10-05T00:15:12.000Z' updated: '2024-10-18T16:50:59.000Z' ----------------------------------- ## Overview Assigning a Send From Email to your Project allows you to choose what address and sender your customers see when receiving email communications related to their compliance requests for that specific project. The default Send From Email for Projects is [support@concord.tech](mailto:support@concord.tech), but can easily be changed by following the steps below. \*\*Note: \*\*Before changing a Project’s Send From Email, one must be created first under the **Global Settings -> Email** section. For more information on adding Send From Emails, see [Managing Send From Emails](/docs/managing-send-from-emails) 1. Go to **Global Settings -> Projects** and click **Edit** next to the desired Project. ![](/docs/assigning-send-from-emails-global-settings-projects-left-nav-add-projects.png) 2. In the **Edit Projects** window, click the **Send From Email** drop-down menu. ![](/docs/assigning-send-from-emails-projects-edit-project.png) 3. Select the email address you would like users to receive emails from. 4. Click **OK**. # Guest Access URL: /docs/guest-access *** title: 'Guest Access' description: 'Invite people outside your team, such as vendors, contractors, and staff without a Concord account, to answer what you share with them or acknowledge their policies, without giving them access to anything else.' created: '2026-10-30T00:00:00.000Z' updated: '2026-10-30T00:00:00.000Z' ----------------------------------- ## Overview Sometimes the person who needs to act isn't on your Concord team: a vendor answering part of an assessment, or a staff member who has to acknowledge your policies but never uses Concord otherwise. Instead of sending them a link anyone could open, Concord invites them as a **Guest**. A guest signs in, so you always know who answered or acknowledged. They see only what was shared with them, and nothing else in your organization. ## How Someone Becomes a Guest You don't add guests by hand. They're invited when you share something with them: * **Assessments:** invite an outside respondent to an assessment, or to one section of it. See [Assessments](/docs/assessments#assigning-and-sharing). * **People:** add someone without a Concord account to your personnel list and ask them to acknowledge your policies or complete training. See [People](/docs/data-hub-people#how-people-acknowledge). Guests never take a paid seat. ## Signing In The invite only works for the email address it was sent to. 1. The guest opens the button in the invite email. 2. Concord sends a one-time passcode to that address. There's no password to create. 3. They enter the passcode and land on **My Work**, which lists what they've been asked to do. If they already have a Concord account, the invite adds your organization to it, and they sign in the way they normally do. ## What Guests Can See A guest has no permissions of their own. Everything they can open comes from what you shared with them: | Shared with them | What they see in My Work | | -------------------------------- | ----------------------------------------------- | | An assessment or a section of it | **Assessments**, with only the parts you shared | | Required policies | **Policies**, to read and acknowledge | | Required training | **Training**, to complete | They can't see your projects, settings, other people, or any other records. ## Ending Access A guest's access ends when what you shared with them ends: * **Revoke** an assessment invite, and they can no longer open it. * **Offboard** a person on your personnel list, and their policies and training disappear from their My Work. Their records, such as answers they submitted or policies they acknowledged, stay in place for your audit history. # Managing Projects: Add, Edit, Archive, and Clone URL: /docs/managing-projects *** title: "Managing Projects: Add, Edit, Archive, and Clone" description: 'This article provides instructions on how to add, edit, archive, and clone your Projects.' created: '2021-05-13T20:53:28.000Z' updated: '2025-07-25T04:35:17.000Z' ----------------------------------- ## Overview Concord uses Projects as the basic unit of deployment and configuration. This article provides instructions on managing existing Projects. To learn more about how projects work, refer to this article: [Projects Overview](/docs/projects-overview) From the **Global Settings → Projects** section in the Admin UI, you will be able to: * Add new projects. * Edit existing projects. * Archive projects. * Clone existing projects. ## How to Add a New Project Domain 1. Click on the **Global Settings** drop-down menu and choose **Projects**. 2. Click **Add Project** to open the Add Project wizard. 3. On the **Project** step, enter your **Project Name** and **Domain** URL and click **Next**. * The UI will confirm if you have entered a properly formatted domain. Do not prepend “http\://” or “https\://” to your domain. ![](/docs/managing-projects-add-project.webp) 4. On the **Disclosure** step, add the URL for your organization’s **Privacy Policy** (required) and **Terms of Service** (optional but recommended if you have a terms of service page). ![](/docs/managing-projects-disclosures.webp) 5. On the **Consent** step, configure your organization’s consent settings. For more information on how to configure your consent settings, see this article: [Configuring Auto-Blocking of Cookies and Scripts](/docs/understanding-configuring-auto-blocking-of-cookies-scripts) ![](/docs/managing-projects-google-add-project.webp) 6. On the **Colors** step, select your primary and secondary colors. * **Primary:** The primary color is used in your Consent Banner, Privacy Center, and Floating Button for most of your custom branding (buttons, links, etc.). * **Secondary:** Your secondary color is used for the background of the header in your Privacy Center. ![](/docs/managing-projects-colors-add-project.webp) 7. On the **Logo** step, add the logo you want to use in your Privacy Center. Horizontal logos are recommended. There are no height or width restrictions, but logos are resized in the widget to a max-height of 40px so 40px is the preferred height. ![](/docs/managing-projects-logo-add-project.webp) 8. We will display a message letting you know the project has successfully been added and is now ready for use. ![](/docs/managing-projects-add-project-confirmation.webp) ## How to Edit a Project The options to edit a project located on the right-hand side of the domain list in the **Actions** menu. ![](/docs/managing-projects-edit-project.webp) Select **Edit** to change an existing domain’s name or URL. You’ll be able to edit: * Project Name * Status * Send From Email * Notification Email(s) * Data Systems ![](/docs/managing-projects-edit-project.webp) ## How to Archive and Unarchive Projects You can archive a project by clicking the “+” to the right of the project name to view the project details. Click the **Archive** button and you will be prompted to confirm you want to archive the project. ![](/docs/managing-projects-archive.webp) To view and restore archived projects. Login to your Concord account, navigate to Global Settings, and Projects. Click the filter option to the right of the Project Status column, select Archived and click OK. You'll now see a list of your archived projects. Click the Actions Menu to the right of the project you want to change, select Edit Project, and change the project status. ## How to Clone a Project The options to clone a project located on the right-hand side of the domain list in the **Actions** menu. When cloning a project, the core configuration settings will be copied to the new project (branding, consent settings, privacy request settings, etc.). ![](/docs/managing-projects-clone-project.webp) 1. In the Clone Project wizard, on the **Project** step, enter your **Project Name** and **Domain** URL and click **Next.** * The UI will confirm if you have entered a properly formatted domain. Do not prepend “http\://” or “https\://” to your domain. ![](/docs/managing-projects-clone-project.webp) 2. On the **Disclosure** screen, add the URL for your organization’s **Privacy Policy** (required) and **Terms of Service**. If the Project you are cloning has no additional regions, this is the final step and you can click **Done**. You will now see your new project in the list of projects. If the project being cloned has additional regions, click **Next** to continue to the final step. ![](/docs/managing-projects-clone-project.webp) 3. If you are cloning a project that has additional regions, you will see a **Regions** step, where you can select the additional regions you would like copied to the new project. Please note that this section will not show in the wizard if you only have a default region configured. Click **Done** and you will see the new project in your list of projects. ![](/docs/managing-projects-clone-project.webp) # Managing Send From Emails URL: /docs/managing-send-from-emails *** title: 'Managing Send From Emails' description: 'Step-by-step guide to adding and managing Send From Emails in Concord.' created: '2021-10-05T00:10:33.000Z' updated: '2023-10-03T08:43:21.000Z' ----------------------------------- ## Overview When your customers take certain actions within the Privacy Center, such as submitting compliance requests, they will receive communications generated by Concord, such as emails providing verification codes or confirming a received request. * The default address for each newly created Project is **[support@concord.tech](mailto:support@concord.tech) (Concord Support).** You may want to choose a different address and sender name that is in line with your company’s customer support or privacy teams. This can be accomplished by configuring Send From Emails. Adding and using a new Send From Email is an easy two step process: 1. Add a new Send From Email (instructions below). 2. Assign a Send From Email to a specific project. For information on assigning Send From Emails to a Project, see [Assigning Send From Emails to Projects](/docs/assigning-send-from-emails) 3. (Optional) DMARC/DKIM Setup. If you use strict email security policies, you may need to configure DKIM and DMARC. For detailed instructions on configuring email authentication, see our guide on [Send From Email Authentication (DKIM & DMARC)](/docs/send-from-email-authentication-dkim-dmarc). ## Adding Send From Emails 1. You can add, edit, and delete Send From Emails in the **Email** section under **Global** **Settings**. 2. To add a send from email, click on the **Add Email** button on the top right. ![](/docs/managing-send-from-emails-add-email.webp) 3. Enter a name. This is the sender name your end users will see attached to email communications. 4. Enter an email address. This is the address that your end users will receive email communications from. ![](/docs/managing-send-from-emails-address.png) 5. Click **Ok**. Your new Send From Email will now show a “Pending” status in the Send From Emails table. ![](/docs/managing-send-from-emails-table.webp) 6. Check the corresponding email account for your verification link. Click the link to verify your email address. 7. You will be brought back to the Admin UI with a notice that your email has been successfully verified. Click the **Back Home** button to return to the project dashboard. You are now able to assign your new Send From Email to a Project. ![](/docs/managing-send-from-emails-verification.png) ## Editing Send From Emails To edit a Send From Email, click on the **Edit** button to the right of the desired email. Update the **Name** and click the **Ok** button. ![](/docs/managing-send-from-emails-name.png) Any changes made to the Send From Email will appear across all associated Projects. ## Deleting Send From Emails To delete a Send From Email, click the **Delete** button to the right of the desired email. You will be asked to confirm the deletion. ![](/docs/managing-send-from-emails-delete.png) After deleting a Send From Email, any Projects associated with that email will revert back to using **[support@concord.tech](mailto:support@concord.tech)** as the Send From Email. # Managing Users URL: /docs/managing-users *** title: 'Managing Users' description: 'Step-by-step guide to managing users in Concord.' created: '2021-05-13T20:51:29.000Z' updated: '2023-10-03T08:44:45.000Z' ----------------------------------- ## Overview You can add, edit, and delete Concord users from the **Users** section under **Global Settings**. ## Adding Users To add a user, click on the **+ Add User** button on the top right. ![](/docs/managing-users-add-user.png) See also: [User Roles and Permissions](/docs/user-roles-permissions) ## Confirming User Accounts New users must first confirm their account to access projects. When initially added in the Admin UI, users will receive an email invitation to join your organization. The user will need to follow the provided link to confirm their account. * To resend the invite link to a user, click **Resend** next to their pending account. ![](/docs/managing-users-resend.png) ## Editing Users To edit a user, click on the **Edit** button to the right of the row displaying the user’s information. * You can edit the user name, role, and user notes from here. ![](/docs/managing-users-edit-user.png) ## Deleting Users To delete a user, click the **Delete** button to the right of the row displaying that user’s information. You will be asked to confirm the user deletion. ![](/docs/managing-users-delete-user.png) # Projects Overview URL: /docs/projects-overview *** title: 'Projects Overview' description: 'Guide to understanding projects and viewing project details.' createdAt: '2021-05-13T20:53:18.475Z' updatedAt: '2023-10-03T06:43:36.997Z' publishedAt: '2024-11-29T06:37:44.074Z' --------------------------------------- ## Understanding Projects * Concord uses Projects as the basic unit of deployment and configuration. * Most organizations will create a Project for each unique website or application they own. * Most companies will generally use a single domain per Project, although it's possible you will have several different websites that require similar Consent and Compliance configurations. * When logging into Concord's Admin User Interface (UI) for the first time, you will be guided through a Project Setup Wizard where you will create your organization's first Project. * If you have a test, development, and/or QA version of your site, you may wish to create a project for each of these site versions. * You can switch Projects from any screen within the Project Setup module via a drop-down Project selector box on the top left of the window. * From the **Global Settings** and **Projects** section in the Admin UI you will be able to: * Add additional Projects. * View Project details. * Edit existing Projects. * Archive Projects. * Export the list of Projects to a CSV file for internal auditing and workflow processes. * For more information on adding or editing Projects, see these articles: * **[Adding Projects](/docs/adding-projects)** * **[Managing Projects](/docs/managing-projects)** ## Viewing Project Details 1. Click on the **Global Settings** drop-down menu and choose **Projects**. ![Navigation to Global Settings Projects](/docs/projects-overview-nav-global-settings-projects.webp) From this screen you will be able to view Project details such as: * Project Name * Status * Send From Email * Notification Email(s) 2. To view additional Project details, click on the **+** to the left of your desired Project. ![Projects table view with expand button](/docs/projects-overview-projects-table-view.png) This expanded view will display Project details such as: * Organization ID * Project ID * Date Created * Date Updated * Data Systems ![Expanded project details view](/docs/projects-overview-projects-details.webp) # Send From Email Authentication (DKIM and DMARC) URL: /docs/send-from-email-authentication-dkim-dmarc *** title: Send From Email Authentication (DKIM and DMARC) description: How to configure DKIM and DMARC for emails sent by Concord, and when stricter email security settings are required. -------------------------------------------------------------------------------------------------------------------------------- ## Overview Concord sends certain system and product emails on your behalf (for example: notifications, consent or privacy-related messages, and account communications). To ensure reliable delivery and alignment with modern email security best practices, you may optionally configure **DKIM** and **DMARC** for your domain. Before configuring authentication, you must first add your sender email address in the Concord app. See [Managing Send From Emails](/docs/managing-send-from-emails) for step-by-step instructions. This is **typically only required** if you use **stricter DMARC policies** (such as `p=quarantine` or `p=reject`), or if your internal security policies require authenticated sending. *** ## What Are DKIM and DMARC? ### DKIM (DomainKeys Identified Mail) DKIM cryptographically signs outgoing emails and allows receiving mail servers to verify that: * The email was authorized by your domain * The message was not altered in transit DKIM is configured using **DNS records** and requires no ongoing maintenance once set up. *** ### DMARC (Domain-based Message Authentication, Reporting & Conformance) DMARC tells receiving mail servers what to do **if authentication fails**. Common DMARC policies include: | Policy | Meaning | | -------------- | ------------------------------------------------- | | `p=none` | Monitor only (no enforcement) | | `p=quarantine` | Suspicious emails may be filtered or sent to spam | | `p=reject` | Emails that fail authentication are rejected | **Important:** If your domain uses `p=quarantine` or `p=reject`, DKIM **must** be configured or emails sent by Concord may fail to deliver. *** ## Do I Need to Set This Up? You **do not need to configure DKIM** if: * You do not have a DMARC policy * Your DMARC policy is `p=none` * You are not enforcing strict outbound email controls You **should configure DKIM** if: * You use `p=quarantine` or `p=reject` * Your security team requires authenticated email * You want maximum email deliverability and trust *** ## Recommended Setup (Easy DKIM via CNAME) For most customers, Concord recommends **Easy DKIM** using DNS **CNAME records**. This method: * Does **not** require managing keys * Does **not** require sharing sensitive material * Is fast to set up * Is fully compatible with strict DMARC policies *** ## How to Configure DKIM (CNAME Method) ### Step 1: Request DKIM Records from Concord Contact Concord support and let us know: * The domain you send email from (for example: `example.com`) We will generate **three DKIM CNAME records** for your domain. *** ### Step 2: Add the CNAME Records to Your DNS Add the provided CNAME records to your domain’s DNS provider. #### Example ```txt Type: CNAME Name: abc123._domainkey.example.com Value: abc123.dkim.amazonses.com Type: CNAME Name: def456._domainkey.example.com Value: def456.dkim.amazonses.com Type: CNAME Name: ghi789._domainkey.example.com Value: ghi789.dkim.amazonses.com ``` The exact record names and values will be unique to your domain. *** ### Step 3: DNS Propagation & Verification * DNS changes typically propagate within minutes, but may take up to 24 hours * Concord will automatically verify DKIM once records are visible * No further action is required on your side *** ## About BYODKIM (Bring Your Own DKIM) Some organizations require full control over DKIM private keys. In these cases, Concord **can** support BYODKIM, but it: * Requires generating and managing DKIM keys on your side * Requires securely sharing public key details for verification * Adds operational complexity For most customers, **CNAME-based DKIM is strongly recommended** and provides equivalent security and deliverability. If you believe BYODKIM is required due to internal policy, please contact Concord support to discuss next steps. *** ## Updating or Enforcing DMARC Once DKIM is configured, you may safely enforce stricter DMARC policies such as: ```txt v=DMARC1; p=quarantine; adkim=s; aspf=s; ``` or ```txt v=DMARC1; p=reject; adkim=s; aspf=s; ``` If you are unsure what policy to use, we recommend starting with `p=none` and monitoring DMARC reports before enforcing. *** ## Need Help? If you’re unsure whether DKIM or DMARC is required for your setup, or want help validating your DNS records, contact Concord support and we’ll be happy to assist. # Single Sign-On (SSO) URL: /docs/single-sign-on *** title: 'Single Sign-On (SSO)' description: 'Connect your identity provider to Concord so your team signs in through it, with domain verification, role mapping, and break-glass access. Available on the Enterprise plan.' created: '2026-09-15T00:00:00.000Z' updated: '2026-09-15T00:00:00.000Z' ----------------------------------- ## Overview Single sign-on lets your team sign in to Concord through your own identity provider instead of a Concord password. Concord speaks OpenID Connect, so any OIDC provider works, including Okta, Microsoft Entra ID, Google Workspace, Auth0, and Ping Identity. If your provider or security team requires SAML, Concord supports SAML 2.0 as well. SSO is available on the **Enterprise** plan, and only an **Owner** can set it up. You will move through five steps: verify your email domain, create an application in your provider, configure the connection in Concord, optionally require SSO, and optionally map roles from your provider's groups. ## Before you start * You are an **Owner** of your Concord organization. * You can create applications in your identity provider. * You can add a DNS TXT record for your company's email domain. ## Step 1: Verify your email domain 1. Go to **Global Settings → Single sign-on**. 2. Under **Email Domains**, add your company domain (for example `acme.com`). Public domains such as gmail.com cannot be used. 3. Concord shows a TXT record. Add it with your DNS provider, then click **Verify** once it propagates. Add every domain your people use — a user whose email is on an unverified domain is refused. ## Step 2: Create the application In your identity provider, create a **web application** using the **authorization code** flow, set its sign-in redirect URI to the value shown in Concord's SSO settings, and copy the **Issuer**, **Client ID**, and **Client secret**. Follow your provider's own documentation for the exact screens. ### If your provider uses SAML 2.0 Concord also federates SAML 2.0 (through AWS Cognito). Pick **SAML 2.0 provider** in Step 3. The named options above (Okta, Entra ID, and so on) use OpenID Connect. The SAML flow differs in a few places: * **In your provider,** create a **SAML 2.0 application** and set its **ACS / Reply URL** and **Audience URI / Entity ID** to the two values Concord shows in the connection settings. * **Email (required):** your provider must send the user's email in a SAML attribute named `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress`. Concord matches users by email. * **In Concord,** instead of an Issuer, Client ID, and Client secret, you provide your provider's **SAML metadata URL**. For role mapping, send group membership as a SAML attribute and enter that attribute's name in Concord's **groups attribute** field. OpenID Connect is the simpler path and the one we recommend; use SAML 2.0 when your provider or security team requires it. ## Step 3: Configure the connection 1. In **Global Settings → Single sign-on → Connection**, choose your provider and enter the Issuer, Client ID, and Client secret. 2. Pick the **default role** for new users. Limited is recommended; you can promote people afterward. 3. Click **Test sign-in** and complete the login. The result reports what happened, including the reason if it failed. You stay signed in as yourself throughout. 4. Click **Activate**. Users entering an email on a verified domain are now sent to your provider automatically. {/* Screenshot pending: Single sign-on connection -> /docs/single-sign-on-connection.png. See docs-screenshot-backfill plan. */} ## Step 4 (optional): Require SSO Once logins work, turn on **Require SSO** to block password sign-in for everyone on your verified domains. Concord requires two things first: at least one break-glass owner, and one sign-in that has already succeeded through the connection. Once SSO is required, **your provider enforces multi-factor authentication** — Concord no longer challenges an authenticator app at sign-in, because your provider has already decided how people authenticate. If you rely on MFA, make sure it is required in your provider. ### Break-glass owners A break-glass owner keeps password and MFA sign-in while everyone else is sent to your provider — your way back in if the provider is ever unavailable. To qualify, someone must be an **Owner** with an authenticator app enrolled (set up under **My profile → Security**), and then have **Break-glass access** turned on from **Global Settings → Users**. Designate **two**, so one lost phone is not a lockout. ## Step 5 (optional): Map roles from your provider By default, every SSO user gets the connection's default role. **Role Mapping** reads a claim from your provider and assigns roles from it instead, re-applied on every sign-in — so removing someone from a group takes effect the next time they log in. Owner is never mappable, and while mapping is on, SSO users' roles cannot be edited in Concord. 1. Create groups for Concord (usually two are enough, one per access level — for example `concord-admins` and `concord-limited`). Concord has two mappable roles, so map by access level, not by team. 2. Have your provider send the group claim in the ID token, and confirm it arrives before configuring anything in Concord. 3. In **Role Mapping**, set the **Claim name**, add a rule per group (name to role), and choose what happens **When nothing matches**. 4. **Save**, then **Test sign-in** — a result naming the role confirms the rules resolve. ## Launching from your provider's dashboard Sign-in must **start at Concord**. Concord generates a request it recognizes on the way back, so a login launched from your provider's app tile arrives unsolicited and is rejected before Concord ever sees it. Every active connection has a **direct sign-in link**, `https://admin.concord.tech/sso/your-org`, shown in the connection settings. Bookmark it, and make it what your dashboard tile opens: * **OpenID Connect (Okta):** on the app, set **General → Initiate login URI** to the direct link and **Login initiated by** to **Either Okta or App**. * **SAML 2.0 (Okta):** a SAML app tile always performs provider-initiated sign-on, which Concord rejects. No setting on the SAML app changes this, and **Default Relay State** does not help. Instead create an Okta **Bookmark App** whose URL is the direct link, assign it to the same people, and hide the SAML app's own tile. Keep the SAML app assigned, since it answers the sign-in request; users just should not click it directly. * **Other providers:** point the dashboard tile at the direct link the same way. ## How users are created * Anyone assigned to the application who signs in gets a Concord user automatically, with the default role (unless they were invited first, in which case the invite's role wins). Each new user consumes a seat. * Users created through SSO sign in **only** through your provider — they never have a Concord password, which is what makes removing them in your provider actually remove their access. * Removing a user in your provider blocks new sign-ins immediately; an open session can remain valid for up to 12 hours. ## Troubleshooting | Symptom | Likely cause | | ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | | "Single sign-on is not configured for this email domain" | Domain not verified, or the connection is not active | | "TXT record not found" during verification | DNS has not propagated, or the host/value does not match exactly | | `redirect_uri` mismatch from your provider | The application's redirect URI does not exactly match the value Concord shows | | Role mapping shows no groups after a successful test | Your provider is not putting the group claim in the ID token | | Sign-in refused with a seat-limit note in the audit trail | Your plan's user limit is exhausted; remove users or upgrade | | `Invalid samlResponse or relayState from identity provider` | The user launched Concord from your provider's SAML app tile (provider-initiated). Give them a Bookmark App that opens the direct sign-in link instead. | | Your provider reports a successful login but Concord never signs the user in | Same cause: the sign-in did not start at Concord. Use the direct sign-in link, or a dashboard tile that opens it. | See also [User Roles and Permissions](/docs/user-roles-permissions) for what each mapped role can do. # User Roles and Permissions URL: /docs/user-roles-permissions *** title: 'User Roles and Permissions' description: 'An overview of the roles you can assign in Concord and what each one can do.' created: '2021-05-13T20:51:43.000Z' updated: '2026-09-15T00:00:00.000Z' ----------------------------------- ## Overview Concord has four roles you can assign to people in your organization. You set a person's role when you invite them under **Settings → Users** (Owners and Admins can invite). * **Owner** — Full access to everything, including billing. Owners can view and update the organization's billing details (billing address, payment method, invoices, plan, and add-ons) and can add or remove other Owners. The person who first sets up an organization is its Owner, and every organization must always have at least one. If an organization is ever suspended over a billing issue, only an Owner can resolve it. * **Admin** — The same access as an Owner, with one exception: billing. Admins manage users, settings, and every product area, but cannot view or change billing details. * **Limited** — A contributor role for people who work in Concord day to day without managing configuration. A Limited user can view the dashboards and the work assigned to them, handle privacy requests (DSARs), complete tasks, and add evidence to controls. They cannot change consent configuration, deployment, branding, framework setup, or organization settings. * **Auditor** — A scoped, read-only role for external auditors. An Auditor has no standing access on their own. You grant them time-boxed access to specific frameworks through the [Auditor Portal](/docs/auditor-access), and that grant is the only thing they can see. What a Limited user can reach depends on which products your organization uses: in a privacy-focused organization they act as a privacy contributor, and in one using Concord Trust's compliance tools they act as a controls contributor. Owners and Admins always have full access across every product your organization has enabled. ![](/docs/user-roles-permissions-add-user.png) # Managing Your Personal Account Profile URL: /docs/managing-personal-profile *** title: 'Managing Your Personal Account Profile' description: 'A step-by-step guide to accessing and updating your personal account profile details and security options.' created: '2021-10-04T23:54:35.000Z' updated: '2026-10-17T00:00:00.000Z' ----------------------------------- ## Access Your Personal Profile To access your personal profile, click the account profile icon in the upper right of the Admin UI. From here you are able to access and update your profile settings and notification settings, browse Concord’s help documentation, change between light and dark mode, see details about our latest releases, and logout. ![](/docs/managing-personal-profile-dropdown.webp) ## My Profile Settings From the My Profile page, you can do things like: * Update your **Profile Details** * Update **Account Settings** include your email and password * Setup and update **Multi-Factor Authentication** settings * See and revoke **Connected Applications**, the AI assistants you've connected to Concord. See [Revoke a Connection](/docs/connecting-mcp-clients#revoke-a-connection). ![](/docs/managing-personal-profile-my-settings.webp) ## Updating Your Personal Profile Details To change your personal profile details: 1. In **My Profile**, navigate to **Profile Settings**. 2. From here you can change your profile details, such as first name, last name, and phone number. Click **Edit** to update a field and click **Save** to save changes. ![](/docs/managing-personal-profile-edit.webp) ## Changing Your Email To change your email address in your personal profile: 1. In **My Profile**, navigate to **Security Settings,** and **Account Settings**. 2. Click the **Change Email** button. To change your email address, you must enter your current password along with your updated email address. 3. Click **Ok** to save the changes or **Cancel** to cancel the changes and return to My Profile. ![](/docs/managing-personal-profile-email.png) ## Changing Your Password To change your security settings in your personal profile: 1. In **My Profile**, navigate to **Security Settings,** and **Account Settings**. 2. Under **Security Settings**, click the **Change Password** button to update your password. To change your password, you’ll be asked to enter your current password, as well as confirm your desired new password. 3. Click **Ok** to save the changes or **Cancel** to cancel the changes and return to My Profile. New passwords must: * Contain at least one number * Contain at least one special character: ^$\*.[]()?&"!@#- Contain at least one uppercase letter * Contain at least one lowercase letter * Contain at least 8 characters ![](/docs/managing-personal-profile-password.png) ## Multi-Factor Authentication To setup an extra layer of security you can setup a second form of authentication. Concord offers the following options: * Authenticator App (TOTP) * Passkey ### How to Configure an Authenticator App in Concord To configure an Authenticator app like Google Authenticator, Authy, or 1Password with Concord: * Navigate to the **My Profile**, **Security Settings,** and **Account Settings.** * Under the **Authenticator App (TOTP), c**lick the **Enable** button to open the setup window. * Using your chosen Authenticator app, scan the QR code or enter the secret key manually in your authenticator app. * Enter the **Device Name** (optional) and **Verification Code** from your authenticator app and click the **Verify & Enable** button. ![](/docs/managing-personal-profile-authenticator-app.png) You’ll now see **MFA Enabled** in the Multi-Factor Authentication section and **Enabled** by the Authenticator App (TOTP) option. ![](/docs/managing-personal-profile-mfa-enabled.webp) ### How to Login to Concord with Your Authenticator App Once you’ve configured your preferred Authenticator app with Concord: * Login to Concord ([https://admin.concord.tech/signin](https://admin.concord.tech/signin)). * Enter your **Email** address and click **Continue**. * Enter your **Password** and click **Sign In**. * You will be prompted to enter the **Verification Code** from your Authenticator App. Enter the code and click **Verify**. ![](/docs/managing-personal-profile-mfa-verification.webp) ### How to Disable Multi-Factor Authentication To remove multi-factor authentication protection from your Concord account: * Navigate to the **My Profile**, **Security Settings,** and **Account Settings.** * Click the delete \*\*\*\*button icon to the left of the Authenticator App (TOTP) section. * In the Disable Multi-Factor Authentication window, enter your **Current Password** and click the **Disable MFA** button. ![](/docs/managing-personal-profile-disable-mfa.png) ### How to Configure a Passkey in Concord For additional security, you can configure a Passkey in Concord. Passkey uses your device's biometric sensor, security key, or platform authenticator for secure passwordless verification. * Navigate to the **My Profile**, **Security Settings,** and **Account Settings.** * Under **Passkey** section\*\*, c\*\*lick the **Register Passkey** button to open the setup window. * In the **Register a Passkey** window, enter a **Passkey Name** and click the **Register Passkey** button. ![](/docs/managing-personal-profile-register-passkey.png) * Select the login to associate to the passkey. Once the registration, you will see Enable next to the Passkey section. ![](/docs/managing-personal-profile-passkey-enabled.png) When you login to Concord in the future, you can enter your can click the Passkey button. You will be prompted to select the associated account/passkey at login. ### How to Disable Passkey Authentication To remove Passkey protection from your Concord account: * Navigate to the **My Profile**, **Security Settings,** and **Account Settings.** * Click the delete \*\*\*\*button icon to the left of the \*\*Passkey\*\* section. * In the Disable Passkey window, enter your **Current Password** and click the **Delete Passkey** button. ![](/docs/managing-personal-profile-delete-passkey.png) # Notification Settings URL: /docs/notification-settings *** title: 'Notification Settings' description: 'A step-by-step guide to configuring your personal notification settings.' created: '2021-05-13T20:52:05.000Z' updated: '2023-10-03T08:49:09.000Z' ----------------------------------- Users can configure their personal notification settings here. You have the option of toggling each notification type on or off, and selecting if notifications are available via in-app messages, via email, or both. ![](/docs/notification-settings-dropdown.png) ## Choosing Your Notifications To enable or disable any particular notification type, simply slide the toggle switch to **On** or **Off** for your choice of in-app and/or email notifications. ![](/docs/notification-settings-options.webp) Note that in addition to your personal notification settings, emails can be added to Projects under Additional Notification Email(s). Those emails also receive notifications for that Project and that feature should typically be used for catch-all emails vs. notifications for specific users (as all users added to a project can instead manage their own notification settings without being added to the Additional Notification Email(s) section). ![](/docs/notification-settings-additional-emails.png) ### Compliance Request Notification Types * **Each Compliance Request.** Enables in-app or email notification for every individual compliance request as they occur. * **Daily Summary: Compliance Requests.** A collected daily summary of all that day’s requests. * **Weekly Summary: Compliance Requests.** A collected weekly summary of all that week’s compliance requests. ![](/docs/notification-settings-compliance.png) ### Configuration Notification Types * **Each Configuration Issue.** Enables in-app or email notification when a configuration issue occurs. * **Daily Summary: Configuration Issues.** A collected daily summary of all that day’s configuration issues. * **Weekly Summary: Configuration Issues.** A collected weekly summary of all that week’s configuration issues. ![](/docs/notification-settings-configuration.png) ### Product Update Notification Types * **Concord Product Updates.** Use this notification type to receive notifications regarding new and important Concord product updates. ![](/docs/notification-settings-product.png) # Concord Support Commitment URL: /docs/concord-support-commitment *** title: Concord Support Commitment description: This article outlines Concord's support commitment to our customers including support channels and response times available to customers across different plans. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ## Overview At Concord, we are committed to providing excellent support to our customers. We understand the importance of timely and effective assistance, especially when it comes to navigating the complex landscape of data protection and privacy compliance. Our support policy is designed to ensure that you receive prompt, reliable, and knowledgeable assistance whenever you need it. Here are the key aspects of our support commitment: * Response Time: We strive to provide an initial response to all customer inquiries within 2 business days of receipt. * Support Channels: Depending on your plan, we offer support through various channels including web, email, and chat, including an extensive knowledge base for self-service support. * Expertise: Our dedicated support team is here to assist you with any questions or issues related to our privacy and compliance software. This document outlines the details of our support services, including available channels, response times, and the types of assistance we provide. We're committed to your success and are here to support you as you implement our products. | | Free | Essentials | Pro | Premium | Enterprise | | ---------------------- | --------------- | --------------- | ------------------ | ---------------------------------- | ------------------------------------------ | | Support Channels | Web | Web & Email | Web, Email, & Chat | Priority Web, Email, Chat, & Phone | Priority+ Web, Email, Chat, Phone, & Slack | | Initial Response Times | 4 business days | 2 business days | 1 business day | Within 1 business day | Within 1 business day (priority queue) | To ensure we can help you as quickly as possible, please include the following information when contacting Concord support: * **Organization Name:** This allows us to link your request to your specific Concord organization. * **Detailed Issue Description:** Provide a clear description of the problem you're experiencing. The more specific you are, the better we can understand and address your concern. * **Steps to Reproduce:** If applicable, outline the exact steps that lead to the issue. This helps our team replicate and diagnose the problem more quickly. * **Screenshots or Error Messages:** Please include any relevant screenshots or error messages you encounter. Please note, Concord's business hours are Monday through Friday, 8:00am to 5:00pm Pacific Standard Time. **Enterprise — Priority+:** Enterprise accounts receive Priority+ handling: a priority support queue ahead of standard Priority, a dedicated Slack channel for direct access to the Concord team, and expedited escalation for critical issues. ## Escalations In accordance with our support commitment, escalations for critical issues follow a structured process to ensure swift and effective resolution. Critical issues, defined as incidents causing complete service outages, significant performance degradation, or major security concerns, are prioritized immediately upon detection or report. Our frontline support team will notify the appropriate technical specialists and escalate the issue to senior engineers or product teams within 60 minutes of confirmation. Updates will be provided to affected customers at regular intervals, and a dedicated escalation manager will oversee the resolution process to ensure adherence to service level agreements (SLAs). ## Google Consent Management Partner (CMP) Support At Concord, our support team is dedicated to ensuring you are successful when it comes to integrating Concord’s CMP with Google. We offer comprehensive assistance for all aspects of our platform, including setting up Concord and integrating with Google via our Google Consent Mode V2 integration. In addition to the above support policies, Concord offers dedicated support staff and account managers for support when troubleshooting Google CMP issues, and all support here should begin with our team as opposed to Google. We offer multiple ways to get the support you need including: * Live chat via our in app chat at [https://admin.concord.tech/](https://admin.concord.tech/). * Email support via [google@concord.tech](mailto:google@concord.tech) or [support@concord.tech](mailto:support@concord.tech). * Self-service web support via comprehensive resources and guides via our [Help Center](/docs). * [Understanding & Configuring Google Consent Mode](/docs/google-understanding-configuring-google-consent-mode-gcm-v2) * Guided CMP setup calls with one of our knowledgeable support agents and account managers/executives including: * Activating and configuring Consent Mode V2. * Setting up your consent banner to comply with Google’s guideline. # Concord Platform URL: /docs/platform *** title: 'Concord Platform' description: 'Account-level guides shared across Concord Privacy and Concord Trust, including organization and user management, billing and credits, the Data Hub, data mapping, and your support options.' icon: RocketIcon ---------------- ## Overview The **Platform** section covers the account-level features that are shared across both Concord Privacy and Concord Trust. These are the settings and tools that live at the organization level rather than inside a single product — how you manage projects and users, how billing and credits work, and how you catalog and map the systems that hold your data. ## Organization & Users Manage the projects, users, roles, and sending domains for your Concord organization. * [Projects Overview](/docs/projects-overview) * [Managing Users](/docs/managing-users) * [User Roles and Permissions](/docs/user-roles-permissions) * [Managing Send-From Emails](/docs/managing-send-from-emails) ## My Profile Configure your personal profile and notification preferences. * [Managing Your Personal Profile](/docs/managing-personal-profile) * [Notification Settings](/docs/notification-settings) ## Billing & Credits Understand your plan, invoices, and how Actions and Data Credits are consumed. * [Billing Overview](/docs/billing-overview) * [Actions and Data Credits](/docs/actions-data-credits) * [Billing FAQ](/docs/billing-faq) ## Data Hub & Data Mapping Catalog the systems in your environment and map data to regulation-ready categories. * [Data Hub Overview](/docs/data-hub-overview) * [Data Mapping Overview](/docs/data-mapping-overview) ## Support Have questions? Reach our support team at [support@concord.tech](mailto:support@concord.tech), or review our [Support Commitment](/docs/concord-support-commitment) for the full list of support options. # Classifying Trackers (Cookies and Scripts) URL: /docs/classifying-trackers-cookies-scripts *** title: 'Classifying Trackers (Cookies and Scripts)' description: 'How to classify and configure the various tracking cookies and scripts on your website.' created: '2023-10-06T01:21:42.000Z' updated: '2024-10-02T20:12:31.000Z' ----------------------------------- ## Overview Websites may use a surprising number of tracking scripts, resulting in many cookies being set on users’ browsers. Concord automatically recognizes and categorizes a wide array of different tracking scripts and their cookies, helping you discover and properly categorize the tracking scripts and resulting cookies. Concord can also be configured to block these scripts until consent is obtained or to allow them until consent is denied. You may chose different options based upon the regionally applicable privacy legislation. For more details on those configuration options, please refer to the following article: [Configuring Auto-Blocking of Cookies and Scripts](/docs/understanding-configuring-auto-blocking-of-cookies-scripts) ## Consent Categories Tracking scripts and cookies can fall into many categories. The particular category will determine if a script is blocked or not and blocking is based on which types of categories an individual user decides to block based on their consent choices. We use the following base categories: * **Strictly Necessary:** These trackers set cookies that are required by the site for proper functionality. They may include things like authentication cookies, session cookies, shopping cart status cookies, and others. Strictly necessary scripts and cookies are never blocked, so only items that are truly strictly necessary should be categorized as such. * **Analytics:** These scripts track visitors’ activities, typically in aggregate form, allowing website owners to better grasp how their sites or apps are being used. * **Functional:** these scripts are not “strictly necessary” but can result in a better, more personalized web site experiences. As they may collect more data than needed for basic site functionality, they are considered non-essential. * **Marketing:** These trackers set cookies for the purpose of behavioral and demographic targeted marketing. If your project has Global Privacy Control (GPC) enabled, which is recommended in the United States and other jurisdictions that require signal detection, users with a detected GPC browser signal will have this category automatically disabled. * **Unclassified: A**ny tracking script and resulting cookie that can’t be categorized automatically by Concord. It is highly recommended that these scripts be properly categorized to enable compliance with users’ consent choices. * **Malicious:** Scripts that are known to be used for improper purposes will be listed here. Any scripts found here are automatically blocked by Concord and should be removed from your site as soon as possible. ## Blocking Mode & Initial Discovery of Cookies & Scripts If this is your first time configuring Concord for your organization, we typically recommend starting in the **Discovery** mode found within the **Blocking Mode** setting within **Consent → Consent Settings.** That mode isn’t GDPR compliant, but allows you to capture the cookies and scripts on your site for categorization without blocking while you are initially setting things up. More details on those settings can be found here: [Configuring Auto-Blocking of Cookies and Scripts](/docs/understanding-configuring-auto-blocking-of-cookies-scripts) ![](/docs/classifying-trackers-cookies-scripts-consent-consent-settings-blocking-mode.png)Once any of the blocking modes are active on your site for a short period of time, we will start populating a list of all the cookies and trackers that we find. To view the list of discovered cookies and scripts: * Navigate to **Consent Settings > Cookies & Scripts.** * You will see a list of all discovered cookies and scripts. * Click on the “+” symbol by each script in order to see the full details. ## Categorizing Cookies & Scripts Once a comprehensive list of cookies and scripts is populated, it will be necessary to categorize the discovered scripts in order for cookie and script consent setting choices to work properly. To categorize tracking cookies and scripts: * Navigate to **Consent → Cookies & Scripts.** * You will see a list of all discovered cookies and scripts. * If desired, click on the **+** symbol by each script in order to see the full details. ![](/docs/classifying-trackers-cookies-scripts-consent-cookies-scripts-view-details.png) * If you want to change the details for a specific cookie or script, including the desired category, click on the **Edit** button. ![](/docs/classifying-trackers-cookies-scripts-consent-cookies-scripts-edit.png)- You may now change the following fields: * **Name:** Use this to create a user friendly and meaningful name. - **Category:** Use this to categorize the tracker. It is crucial to properly categorize the tracking script for proper handling of user consent choices. - **Pattern:** A regular expression identifying the script’s name. In most cases, Concord administrators won’t need to change this, but can be used for advanced adjustments when needed. - **Company:** The originating organization for the tracking script. - **Domain:** The domain of the company associated with the tracker. - **Description:** Use this to input any additional information you wish about the tracker. * **Category:** Use this to categorize the tracker. It is crucial to properly categorize the tracking script for proper handling of user consent choices. * **Pattern:** A regular expression identifying the script’s name. In most cases, Concord administrators won’t need to change this, but can be used for advanced adjustments when needed. * **Company:** The originating organization for the tracking script. * **Domain:** The domain of the company associated with the tracker. * **Description:** Use this to input any additional information you wish about the tracker. * Click on the **Ok** button when you are done. ![](/docs/classifying-trackers-cookies-scripts-consent-cookies-scripts-edit-details.png) # Configure a Consent Banner for Different Regions URL: /docs/configure-consent-banner-different-regions *** title: "Configure a Consent Banner for Different Regions" description: 'How to enable different settings for different geographical regions.' created: '2024-04-23T23:07:11.000Z' updated: '2026-04-16T00:00:00.000Z' ----------------------------------- ## Overview Regions are used to customize the behavior and experience based on an individual user's location. As an example, this allows you to provide different experiences to users based on regional differences (like GDPR in the EU vs. CCPA/CPRA in California). When a user visits your site, we will automatically determine their location and will match them to the most granular region rule that you have setup in Concord. This can go down to the state/province level, which allows for different experiences for different laws (like CCPA/CPRA in California). While you can get as granular as you want, we typically recommend a single global policy that meets the strictest guidelines across regions, or higher splits (like separate GDPR and United States regions). If you have any questions on how and why to configure your regions in certain ways, please reach out to our support team. ### Adding a Custom Region 1. Login to Concord and navigate to Privacy → Deployment → Regions. Note that the Default region cannot be deleted and that a user will see the Default consent banner if there are no other matching region rules based on the user’s location. ![](/docs/configure-consent-banner-different-regions-page.webp) 2. Click the **Add Region** button to open the **Add Region** wizard. Select one of the following region template options, and click the **Next** button. ![](/docs/configure-consent-banner-different-regions-selector.webp) * **GDPR (EU/EEA + UK):** Applies prior consent and strict blocking before activating non-essential technologies, with granular category controls aligned to GDPR and ePrivacy requirements. * **United States:** Provides notice and opt-out controls aligned with U.S. state privacy laws. Appropriate for most U.S. businesses, including many operating in California that do not require additional state-specific features. * **California:** Enables California-specific rights under CCPA/CPRA, including Do Not Sell/Share and the ability to limit certain uses of sensitive personal information. Uses an opt-out approach for marketing technologies through the Do Not Sell/Share control. * **California (Express + Do Not Sell Only):** Maintains a simplified Do Not Sell/Share experience while requiring user consent before activating marketing technologies. Marketing remains disabled until the user clicks Accept/Okay or confirms their choices in the Privacy Center. Other categories continue under implied settings. * **California (Express + Categories + Do Not Sell):** Requires user consent before activating marketing, analytics, and similar technologies, while also providing Do Not Sell/Share controls. Displays full category-level controls for a granular consent experience in California. * **PIPEDA (Canada):** Applies meaningful consent and category-based controls before activating advertising and similar technologies, reflecting Canadian privacy law requirements. * **LGPD (Brazil):** Applies prior consent and category-based controls before activating non-essential technologies, reflecting Brazil’s data protection framework. * **DPDPA (India):** Applies consent-based activation controls aligned with India’s Digital Personal Data Protection Act (DPDPA), supporting transparent and user-driven data practices. * **Custom:** Fully customizable settings to meet your specific privacy requirements and preferences. Start with a blank slate and configure consent, blocking, and category controls as needed. Note that we will pre-populate the region settings on the following screens based on that choice, but the specific settings can always be adjusted later if preferred. 3. Click **Next** to keep the default regions based on your previous selection or add or remove the regions that you want to apply to this region template. ![](/docs/configure-consent-banner-different-regions-selector-regions.webp) 4. On the Consent page you can review and customize the consent settings for your selected region. ![](/docs/configure-consent-banner-different-regions-selector-consent.webp) On the **Consent** page, you can configure the following settings: * **Name:** Add a descriptive name for the region template. * **Blocking Mode:** For global compliance, including compliance with stricter privacy laws like GDPR, this should typically be set to Strict mode after categorization. If this is disabled, no blocking or detection of cookies and scripts will occur. * During the setup process, we recommend that you initially set the blocking mode to **Discovery.** This mode collects information from your site which is used to classify tracking scripts and cookies without blocking them. * This allows Concord to automatically classify the most common types of cookies and scripts, while giving you the flexibility to customize the categorization and blocking to your needs. * You will keep this setting in place until you are ready to go-live on your production site. * When deploying to production, you will set this to Strict or Permissive. * **Strict** is recommended as all scripts and cookies that aren’t categorized as strictly necessary are blocked. This is required for full compliance with stricter privacy laws like GDPR. * **Permissive** mode will allow Strictly Necessary, Ignored, and Unclassified cookies and scripts to run until user consent preferences are set. * Note that in all modes, ignored scripts, iframes, images, and links will not be blocked. We capture a larger list of these items than most others tools to ensure true compliance by helping to make sure that nothing falls between the cracks. Ignored items should be regularly reviewed, but only need to be categorized if they touch customer data (including things like IP address in the case of stricter laws like GDPR). * **Express/Implied Consent Mode: \~\~Consent:** Configure your organization’s consent settings including:\~\~ * **Express:** In Express Consent Mode, the user must interact with the Consent Banner or the Privacy Center to set their preferences. No consent is initially assumed merely by landing on or using the site. * **Implied:** When using Implied Consent Mode, Concord will automatically generate implied consent events for all categories when the user lands on the site. They can later choose to opt-out of certain categories via your Consent Banner or Privacy Center (depending upon your configured settings and options there). * **Privacy Controls Experience:** This setting works in conjunction with the Express and Implied Consent Modes to determine the experience for users when they interact with your Consent Banner and Privacy Center. You can choose one of the following configuration options: * **Category Controls + Do Not Sell/Share** * Provides both granular category-level controls and a Do Not Sell/Share toggle switch. Suitable for deployments that combine granular consent with sale/share opt-out rights. * All categories are enabled on arrival. Users can opt out of individual categories and use the Do Not Sell/Share toggle. Common in U.S. deployments that combine category controls with opt-out rights. * **Category Controls** * Users choose which specific categories to allow. The Do Not Sell/Share toggle is not shown. Appropriate for regions where sale/share opt-out rights do not apply. * All categories are enabled on arrival. Users can opt out of individual categories. The Do Not Sell/Share toggle is not shown. Appropriate for regions where sale/share opt-out rights do not apply. * **Do Not Sell/Share Only** * Simplified consent experience where category controls are hidden and users see a single Do Not Sell/Share toggle. Suitable for regions that emphasize opt-out rights. * All categories are enabled on arrival. Users can opt out of individual categories. The Do Not Sell/Share toggle is not shown. Appropriate for regions where sale/share opt-out rights do not apply. * **Global Privacy Control (GPC)** is a browser configuration that automatically signals users’ privacy preferences to a website. Various regulations such as CCPA and CPRA require websites to respect users’ choices when this browser setting is detected. * Global Privacy Control detection is required by some regional data privacy laws like CCPA/CPRA in California. When this is enabled and a GPC signal is detected, Do Not Sell or Share My Personal Information consent will be set to true and Marketing consent will be disabled. * Note that you must select either the Category Controls + Do Not Sell/Share or Do Not Sell/Share Only option in the Privacy Controls Experience section if you want to enable Global Privacy Control. * When you enable this feature within Concord, and the user has GPC turned on in their browser settings, Concord’s consent banner will display the following message: **Your Opt-Out Preferences Was Honored. Do Not Sell or Share My Personal Information** will also be automatically checked. * **Enable Limit Sensitive Information Consent:** Enables the Limit the Use of My Sensitive Personal Information consent option in your Privacy Center. This is required by some regional data privacy laws like CCPA/CPRA in California. * **Consent Duration:** The Consent Duration field defines how many months the consent is valid for. Once the duration has expired, the user will be prompted to re-consent. The normal recommended duration is 12 months, but some regions have different requirements and recommendations, including countries like Germany, where the guidance is 6 months. * **Show Deny Button:** The show Show Deny toggle allows you to set if the Deny button shows on your consent banner. Note that this option is only available if you choose the **Category Controls + Do Not Sell/Share** or **Category Controls** in the **Privacy Controls Experience** section. * [**Advanced Options**](https://www.concord.tech/docs/understanding-configuring-auto-blocking-of-cookies-scripts#advanced-options) * **Hide Unused Categories:** When enabled, consent categories that have no trackers assigned to them will be hidden from the Privacy Center and Consent Banner. In Implied mode, hidden categories still receive implied consent. In Express mode, hidden categories are excluded from Accept All but included in Reject All. Categories automatically reappear when trackers are detected. * **Implied Consent Delay:** Sets a delay (in seconds) before implied consent is automatically granted when the user first visits your site. A value of 0 means consent is implied immediately. Increasing this value gives users more time to interact with the consent banner before implied consent is recorded. You can set the number of seconds to wait before generating implied consent events after a user arrives on your site. This only applies when using Implied consent mode. 5. On the **Requests** page, you can enable or disable the following options: * **Privacy Requests Enabled:** If this is enabled, the option to submit e-mail verified Privacy Requests (also known as Data Subject Access Requests) via your Privacy Center will be enabled. * **Enable Do Not Sell or Share Requests:** This option adds a Do Not Sell or Share request form to your Privacy Center. This is separate from the Do Not Sell or Share consent option and is recommended in addition to it for full compliance coverage. ![](/docs/configure-consent-banner-different-regions-selector-requests.webp) 6. On the **Language** page, you can customize the following text on the consent banner for the region you are configuring including: * Banner Title * Banner Text — supports inline **Policy Link tokens**. Insert a reusable link to your Privacy Policy, Terms of Service, Cookie Policy, Data Protection Agreement, or any custom policy via the Insert Link menu in the text editor. Policy Links are managed under **Policies → Links** — see [Managing Policy Links](/docs/managing-policy-links). * Accept Button Label * Customize Button Label ![](/docs/configure-consent-banner-different-regions-selector-language.webp) 7. On the **Branding** tab, you can customize the look and feel of the consent banner by region including: * Primary Color * Secondary Color * Logo * Font * Button Radius * Card Radius * Powered by Concord Logo ![](/docs/configure-consent-banner-different-regions-selector-branding.webp) For teams on Premium, or Enterprise that need tighter brand fit than the built-in branding controls allow, each widget editor (consent banner, privacy center, floating button) also exposes a **Custom CSS** accordion pinned to the bottom of its settings tab, with CSS variable and raw CSS overrides. See [Customizing Consent Banner Styling](/docs/customizing-consent-banner-styling). Click Save to save and apply your new region settings. To add additional regions, repeat the above steps. ### Editing a Region Your newly configured region template will now show in the Regions table. You can click **Edit** to change your template configuration or **Delete** to delete any of you region templates other than the Default region. ![](/docs/configure-consent-banner-different-regions-edit.webp) # Configuring Concord for GDPR Compliance URL: /docs/configuring-concord-for-gdpr-compliance *** title: 'Configuring Concord for GDPR Compliance' description: 'Important information about GDPR and how to configure your website via Concord to be GDPR compliant. ' created: '2024-02-01T00:07:00.000Z' updated: '2024-10-02T20:02:18.000Z' ----------------------------------- ## Overview On May 25th, 2018, the European Union’s General Data Protection Regulation (GDPR) came into effect, replacing the 1995 EU Data Protective Directive. Enforced by the Information Commissioner’s Office (ICO), the GDPR is built around seven basic principles: * **Data Minimization:** Only data that is necessary for the intended purpose can be collected, stored, and/or processed. * **Purpose Limitation:** Organizations can only use data for the declared purposes * **Accuracy:** Business must have processes in place to ensure accurate data. Users have the right to correct data, and must be provided the means to do so. * **Storage Limitation:** Justification for storage lengths must be provided and data retention limits must be set. * **Security:** Business must take reasonable means to secure their users’ data, to include necessary security measures, policies, protocols, and training. * **Accountability:** Business must have appropriate measures in place to demonstrate compliance, and are accountable and responsible for how they use and safeguard user data. * **Fairness & Transparency:** Personal data must be handled in a fair and transparent manner. Communication should be in plain language, be clear, concise, and honest about data collection and handling, and business should not handle or process user data in a detrimental, unexpected, or misleading manner. ## Configuring Concord for GDPR Compliance There are a few, easy steps to take to ensure that Concord is properly configured for GDPR compliance, First, enable Express Consent Mode of Cookies and Scripts which requires user to interact with the consent banner or Privacy Center to set their preference. 1. Navigate to **Consent** → **Consent Settings**. 2. From the **Express/Implied** **Consent Mode** dropdown, select **Express**. **Note:** Concord recommends you initially set **Blocking Mode** to **Discovery** mode, typically during an implementation period. **Discovery** mode can be used to test and configure your implementation without blocking, including during the cookies and script classification process. [See here](/docs/classifying-trackers-cookies-scripts) for more detail on classifying Cookies and Scripts. ![](/docs/configuring-concord-for-gdpr-compliance-2520consent-2520config.webp) 3. Click to toggle **Enable Do Not Sell Consent** to **On** or **Off**. Current GDPR requirements do not explicitly require Do Not Sell, but you can enable this feature if you choose to. This can be a good strategy if you want a single privacy-first configuration that you can use globally since regulations like CCPA/CPRA do require Do Not Sell. 4. Click to toggle **Enable \*\***Global Privacy Control\*\* to **On** or \*\*Off.\*\* Current GDPR requirements do not explicitly require GPC, but you can enable this feature if you choose to. This can be a good strategy if you want a single privacy-first configuration that you can use globally since regulations like CCPA/CPRA do require GPC. 5. Click the **Save** button in the upper right of the page to commit your changes. ## Additional Recommendations Concord highly recommends that you also take full advantage of our [Data Mapping](/docs/data-mapping-overview) functionality in order to fully comply with GDPR, including their requirements around maintaining a Record of Processing Activities. This can be done by adding all of your organization's data systems via Data Mapping for centralized compliance documentation, while also enabling easier handling of privacy requests. As part of that process, you will also make use of our [Data System Attributes](/docs/data-hub-system-attributes) functionality, in order to properly classify and understand how the aforementioned Data Systems handle user data. This will help ensure that your data systems are fully documented. # Configuring the Consent Banner URL: /docs/configuring-consent-banner *** title: 'Configuring the Consent Banner' description: 'How to configure the look, feel, and content of your consent banner.' created: '2024-04-24T00:21:01.000Z' updated: '2026-11-18T00:00:00.000Z' ----------------------------------- ## Overview Consent banners are required by many regulatory regimes to explicitly ask for user consent before deploying cookies or other tracking identifiers, or to notify the user that tracking technologies like cookies are being utilized. When fully complying with laws like GDPR, consent banners do not merely notify the user about the usage of cookies or other trackers on a website, but ask for express/explicit consent before setting non-essential identifiers or cookies (often referred to as strictly necessary cookies) on the user's browser. Depending upon the configuration settings, consent banners can also provide a quick means for users to choose their consent preferences. ## User Experiences: Consent Banner Setup and configure the consent banner that is shown to your users. To configure or update the Consent Banner, click on **Privacy →** **User Experiences → Consent Banner** to configure the banner. Note: If you have multiple regions setup, select the region you want to configure from the Region drop-down selector in the top left of the page above the Consent Banner title. ![](/docs/configuring-consent-banner.webp) ### How to Configure the Consent Banner - General Settings Login to Concord and navigate to **Privacy → User Experiences → Consent Banner → General Setting** tab. In this section, you can setup and configure how the consent banner is displayed to your users. In this section you can configure the following: * **Show Banner:** If the Consent Banner is shown to your users or not. This only pertains to the live site and will not affect the preview so you can always see and edit the Consent Banner, even when it isn't live. * **Layout:** The layout for your consent banner. Options: bar or box. * **Position:** Where the Consent Banner appears on your page. Options: Center, Left Bottom, Left Top, Right Bottom, Right Top. * **Theme:** The theme used for your Consent Banner. Can be set to brand, light, or dark. All themes use your primary color for most of your custom branding (buttons,links, etc.). Brand will use your secondary color as the background. Light uses a white background. Dark uses a very dark gray/black background. * **WCAG AA:** WCAG AA is the internationally recognized standard for web accessibility, ensuring digital content is usable by people with disabilities. Contrast is adjusted to a minimum 4.5:1 ratio for text to background, ensuring readability for visually impaired users. * **Show Banner Title:** Choose if the Deny button is shown or not on your Consent Banner. * **Show Customize Button:** Choose \*\*\*\*If the Customize button is shown or not on your Consent Banner. ### Consent Banner: Language In the **Privacy → User Experiences → Consent Banner → Language** tab, you can setup and customize the verbiage displayed in your Privacy Center. Concord provides suggested text however, we also offer extensive customization options so you can change text to align with your business needs and language style. You can customized the following text in your company’s Privacy Center: * **Banner Title Text:** The title text shown on your Consent Banner. * **Banner Text:** The text shown on your Consent Banner. Supports inline **Policy Link tokens** — see [Inserting Policy Links into banner text](#inserting-policy-links-into-banner-text) below. * **Accept Button Text:** The Accept button text shown on your Consent Banner. * **Deny Button Text:** The Deny button text shown on your Consent Banner. * **Customize Button Text:** The Customize button text shown on your Consent Banner. Once you’ve updated the banner configuration options, click **Save Changes** to save your changes. ### Inserting Policy Links into Banner Text The Banner Text field is a rich text editor. To link to your Privacy Policy, Terms of Service, Cookie Policy, Data Protection Agreement, or any custom policy, insert a **Policy Link token** rather than pasting a URL: 1. Place the cursor where the link should appear in your banner text. 2. Click **Insert Link** in the text editor toolbar. 3. Pick the Policy Link you want to embed. The menu lists every Policy Link configured under **Policies → Links**. 4. Optionally override the displayed text for this banner and language — the default is the Policy Link's Name. ![Consent banner text editor — Insert Link menu](/docs/consent-banner-text-editor-insert-link.webp) Tokens render inline with the banner copy and resolve to the Policy Link's URL at runtime. If you update the destination URL later under **Policies → Links**, every banner that embeds that token picks up the change automatically — you don't re-edit the banner. ![Consent banner with inline Policy Link token](/docs/consent-banner-token-inline.webp) #### Google Privacy Policy Link Google recommends linking to its privacy policy wherever you use Google Consent Mode. For a new region that uses Google Consent Mode, Concord adds a **Google Privacy Policy** link to the banner text for you, and the link also appears in your privacy center's disclosures. It's a link like any other in the banner text, so you can change its wording, move it, or delete it, and add it back from **Insert Link**. For the list of built-in policy types, the create/edit flow, and how tokens behave when a Policy Link is deleted, see [Managing Policy Links](/docs/managing-policy-links). ## Related Documentation * [Managing Policy Links](/docs/managing-policy-links) * [Customizing Consent Banner Styling](/docs/customizing-consent-banner-styling) * [Consent Management Overview](/docs/consent-management-overview) # Consent Events and Exports URL: /docs/consent-log-report *** title: 'Consent Events and Exports' description: 'Review individual consent events, look up a person’s full consent history by Concord ID, and export consent events as CSV or JSON.' created: '2021-05-13T20:44:02.000Z' updated: '2026-09-28T00:00:00.000Z' ----------------------------------- ## Overview The **Consent → Reports** section shows the consent events Concord records for your project. You won't need it every day, but it's where you go for compliance documentation, audits, and data subject requests. It has three tabs: * **Overview:** consent metrics for the selected date range. See [Consent Reports and Metrics](/docs/consent-reports-metrics). * **Events:** individual consent events. * **Export:** a file of consent events for any date range. {/* Screenshot pending: Consent > Reports > Events -> /docs/consent-reports-events.png */} ## Reviewing Consent Events On the **Events** tab, choose a date range to see the consent events recorded in it. Events are grouped by visit, with counts of what the visitor accepted, declined, or implied. Expand a visit to see each event's subcategory, label, action, and expiration date. * **Subcategory:** the consent subcategory the event belongs to. * **Label:** the label of the consent event, as defined when the consent type was created. * **Action:** the action the visitor took. Some actions are implied. * **Expiration Date:** when the consent expires, based on the duration configured for the consent type and the date of the visitor's action. ## Looking Up a Person by Concord ID Use **Search by Concord ID...** on the **Events** tab and enter a full Concord ID. The results show every event for that Concord ID across all time; the date range doesn't apply while an ID is entered. This is what you need when responding to a data subject request or an audit. ## Exporting Consent Events 1. Go to **Consent → Reports → Export**. 2. Select the date range and the file format, **CSV** or **JSON**. 3. Click **Export**. The file is prepared in the background, and large ranges can take a few minutes. You can leave the page while it runs. When it's ready, download it from the **Export** tab, or later from **Global Settings → Exports**, where it stays for seven days. ## Related Articles * [Consent Reports and Metrics](/docs/consent-reports-metrics) * [Consent Management Overview](/docs/consent-management-overview) # Consent Management Overview URL: /docs/consent-management-overview *** title: 'Consent Management Overview' description: 'Overview of consent management in Concord for consent controls, consent capture, and compliance. How to view and export consent and event log details. ' created: '2024-04-23T23:30:55.000Z' updated: '2024-04-23T23:30:55.000Z' ----------------------------------- ## Overview The need to gather and log consent events arises from different regulatory acts worldwide. As an example, the EU’s General Data Protection Regulation (GDPR) requires an affirmative consent for the collection of visitor data in Article 7 (”Conditions for Consent”). > 7.1 Where processing is based on consent, the controller shall be able to demonstrate that the data subject has consented to processing of his or her personal data. Which means that site owners are required to provide consent controls and document that European Union users have given consent to the collection, storage, and processing of their data. Similar laws in multiple US states, such as the CCPA/CPRA in California, also require consent to be provided, although with less strict requirements in some areas. For example, the CCPA/CPRA requires affirmative consent be obtained at the point of or prior to data collection for minors under the age of 16. Consent is also required for users over the age of 16, but implied consent is acceptable. Most regulations also require website owners’ to support specific “data subject” rights. Generally, these include: * The right to be informed of what data is being collected and how it is used. * The right to access a subject’s data. * The right to correct or change a subject’s data. * The right to delete a subject’s data. * The right to restrict processing of a subject’s data. * The right to object. ## How Does Concord Help? Concord’s consent management solution enables robust and flexible consent management configuration settings in order to properly comply with existing and future regulations, establish visitor trust, and differentiate your business. Concord provides both consent logs and privacy request handling (often referred to as Data Subject Access Requests, or DSARs) in order to store and access subjects’ consent records and record and execute on subjects’ data subject rights requests. These are necessary to prove compliance with privacy and consent regulations, and may need to be produced upon request if audited by the relevant authorities. ## How Does Consent Capture and Storage Work? When a user first arrives at your site after deploying Concord, Concord will create a consent token containing an alpha-numerical identifier for the visitor in local storage. Local storage is a browser feature used to store data locally in the form of key-value pairs. This Concord ID is then used to associate consent with that specific browser. ## What Consent Data Does Concord Capture and Store? Concord’s data store will contain the users Concord ID as well as multiple attributes to describe each consent event. These will include: * Consent type, sub-type, version, and label of each consent event. * Date of each consent event, including updated dates. * Consent action * What action did the user take when it comes to the consent event. Can be user\_click, implied, or import (for consent data that is imported from other systems). * Consent state * The user’s new state of consent after a consent event is captured. Can be accepted, declined, viewed, or implied. * Anonymized IP address. * Expiration date of the consent event. * The domain and project the event originated from as configured in your Concord account. ## How Do I Access Consent and Request Logs? The **Events** tab under **Consent → Reports** shows detail on individual consent events that occurred during the selected date range. More information on that report can be found [here](/docs/consent-log-report). The Request Log report within the **Privacy Requests → Request Log** section of Concord shows extended detail on individual Privacy Requests received during the selected date range. More information on that report can be found [here.](/docs/privacy-requests-request-log) # Consent Reports and Metrics URL: /docs/consent-reports-metrics *** title: 'Consent Reports and Metrics' description: 'The Consent Reports section in Concord is where you can find reporting on consent metrics and user preferences.' created: '2025-12-15T20:44:02.000Z' updated: '2025-12-15T20:44:02.000Z' ----------------------------------- The Consent Reports section in Concord is where you can find reporting on consent metrics and user preferences. You will find the following information in the Consent Reports section: * Overview - A dashboard of consent metrics and user preferences. * Events - A detailed list of consent events so you can view and analyze the consent events from your users. * Export - Export consent events from your users as a CSV or JSON file for any date range. ## Consent Reports - Overview To view your consent metrics in Concord, navigate to **Consent → Reports → Overview** tab in Concord. ![](/docs/consent-reports-metrics-overview.webp) The Consent Reports Overview is a graphical representation of consent metrics and user preferences for a specific time period. The Overview tab includes the following information: * **Consent Events** - The number of consent events by day for the selected date range. * **Consent Distribution** - The number of users that gave full consent, partial consent, or no consent for the select date range. * **Category Acceptance Rate** - The percentage of consent by consent event type submitted (Analytics, Functional, Unclassified, Marketing, Do Not Sell, Limit PII Use) for the selected date range. * **Category Acceptance Trend** - A trending view of the number of consent event types submitted (Analytics, Functional, Unclassified, Marketing, Do Not Sell, Limit PII Use) for x period. * **Consent by Geography** - The number of consent events submitted by geographical region for the selected date range. * **Consent by Category** - The number of consent events submitted by type (Analytics, Functional, Unclassified, Marketing, Do Not Sell, Limit PII Use) and if the user accepted or declined consent. * **Consent by Browser** - The number of consent events submitted by browser version. * **Consent by Operating System** - The number of consent events submitted by operating system. ## Consent Reports - Events To view a detailed report of consent events in Concord, navigate to **Consent → Reports → Events** tab in Concord. In this section you’ll be able to view a list of consent events for the selected time period with the ability to: * **Search by Concord ID** - Enter the Concord ID you would like to view details for. * **Filter by State** - Accepted, Declined, Implied Consent. * **Filter by Category** - Analytics, Do Not Sell, Functional, Global Privacy Control, Limit PII Use, Marketing, Privacy Policy, Strictly Necessary, Unclassified. ![](/docs/consent-reports-metrics-events.webp) When viewing a list of consent events, you can click on the **View Details** link to view the consent event details associated to a specific Concord ID including: * Event category * Event state * Label * Action - For example, implied or user click. * Expiration date - The date the consent action expires. ![](/docs/consent-reports-metrics-events-details.webp) ## Consent Reports - Export To export consent events from your users, navigate to **Consent → Reports → Export** tab in Concord. Select the following export options and click the **Export** button: * Date range * Export file type - CSV, JSON ![](/docs/consent-reports-metrics-export.webp) # Cookies and Storage Used by Concord URL: /docs/cookies-and-storage-used-by-concord *** title: 'Cookies and Storage Used by Concord' description: 'Every cookie and browser storage item the Concord consent banner sets on your site, for your cookie policy or vendor review' created: '2026-11-19T00:00:00.000Z' updated: '2026-11-19T00:00:00.000Z' ----------------------------------- The Concord consent banner stores a small amount of data in each visitor's browser so it can remember their choices and apply them on every page. All of these items are **strictly necessary** and none are used for advertising or analytics. They already appear in your tracker list, classified as strictly necessary. ## Cookie | Name | Purpose | Lifetime | | -------------------------------- | -------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- | | `concord-allow-state-` | Records which consent categories the visitor allowed, so the banner doesn't ask again and the right tags load. | Your region's **Consent Duration** (1 to 24 months, set per region) | The value is a list of true or false flags, one per consent category. It contains no identifiers or personal data. | Attribute | Value | | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Type | First-party, set by the Concord script in the browser (not `HttpOnly`) | | `Secure` | Yes | | `SameSite` | `Strict` | | `Path` | `/` | | `Domain` | The current host. With **Enable Cross-Site Tracking** on and your domains listed, the parent domain (for example `.example.com`), so one choice covers your subdomains. | ## Browser storage | Name | Storage | Purpose | Lifetime | | ---------------------------------------- | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------- | | `concord-consent-state-` | Local storage | The visitor's full consent choices, so the banner can apply them right away. | Your region's **Consent Duration** | | `concord-banner-closed` | Local storage | Whether the visitor has closed the banner. | Until the visitor clears their browser data | | `concord-transient-token-` | Local storage | A session token that links the visitor's consent records to a random Concord ID. With **Identity Resolution**, this also carries consent across your sites and devices. | Until the visitor clears their browser data | | `concord-compliance-requests-` | Local storage | The status of privacy requests the visitor submitted through the banner. | Until the visitor clears their browser data | | `concord-language-` | Session storage | The language the visitor picked for the banner. | Until the browser tab closes | | `concord-tcf-tcString-` | Local storage | The IAB TCF consent string. Only when TCF is on. | 1 year | | `concord-tcf-consent-state-` | Local storage | TCF vendor and purpose choices. Only when TCF is on. | 1 year | ## Where the data goes These items stay on your site. When a visitor makes or changes a choice, the banner sends a consent record to Concord, along with the session token, for your consent log. We process consent records on your behalf under our [Data Processing Agreement](/legal/data-protection-agreement). # Customizing Consent Banner Styling URL: /docs/customizing-consent-banner-styling *** title: 'Customizing Consent Banner Styling' description: 'Fit the Concord consent banner, privacy center, and floating button to your brand with built-in branding controls, CSS variable overrides, and full custom CSS.' created: '2026-04-16T00:00:00.000Z' updated: '2026-10-30T00:00:00.000Z' ----------------------------------- ## Overview Concord gives you three layers of customization for the consent banner, privacy center, and floating button, in order of how much responsibility you take on: 1. **Built-in branding controls** — theme, primary/secondary colors, typography, and layout options exposed in the admin UI. These ship with accessibility checks and professionally designed states (hover, focus, disabled, active) and keep your experience on the right side of regulatory expectations around dark patterns. 2. **CSS Variables** — override individual `--cd-*` design tokens (colors, radii, offsets, font scale) when you need to go beyond the built-in controls. 3. **Custom CSS** — write scoped CSS rules for selector-level changes that tokens don't cover. Use the layers in order. Most companies get what they need from layer 1 alone. Layers 2 and 3 are available on Pro, Premium, and Enterprise plans and are intended for teams that need tighter brand fit and are willing to own the visual QA themselves. ## Customization and Compliance Concord's built-in branding controls are designed so that whatever you pick, the result stays compliant and accessible: * **Accept, Deny, and Customize buttons maintain balanced visual weight.** Treating Accept differently from Deny (bright color for Accept, grayed-out for Deny) is a documented dark pattern under GDPR and CCPA/CPRA enforcement guidance. The built-in controls don't let you create that imbalance by accident. The buttons are always the same size: side by side when they fit, stacked at full width when they don't. * **Contrast ratios designed and adjusted as needed to meet WCAG AA.** Text-to-background contrast is targeted to stay at or above 4.5:1. The built-in **WCAG AA** checks and adjustments help enforce this automatically. * **Hover, focus, active, and disabled states are designed for you.** Links, buttons, form controls, and focus rings all get consistent interactive states that work across themes, without you having to design each one. When you step past the built-in controls into CSS Variables or Custom CSS, those guardrails are yours to maintain. Concord applies your overrides last in the cascade, so the final rendering reflects exactly what you specified, including styling that may not meet accessibility standards or that creates a dark-pattern imbalance between Accept and Deny. If compliance and accessibility matter for your deployment (and for most Concord customers, they do and should), the built-in branding controls are the right starting point and usually the right stopping point as well. ## Availability CSS Variables and Custom CSS are included on **Pro**, **Premium**, and **Enterprise** plans. If your organization is on a lower plan, the Custom CSS section appears in the banner, privacy center, and floating button editors but is disabled, and saved overrides don't render publicly until you upgrade. Built-in branding controls are available on every paid plan. ## Where to Configure Styling Each widget has its own editor in the admin: * **Privacy → User Experiences → Consent Banner** * **Privacy → User Experiences → Privacy Center** * **Privacy → User Experiences → Floating Button** Each editor surfaces a **Custom CSS** accordion pinned to the bottom of its settings tab. Inside the accordion you'll find: * A **Reference** card with the canonical scope selector (for example `.cd-consent-banner`) and the CSS variables that apply to that widget. * A **CSS Variables** textarea for `--cd-*` declarations. * A **Custom CSS** textarea for scoped CSS rules. ![Consent banner Custom CSS panel](/docs/banner-custom-css-panel.webp) ![Privacy center Custom CSS panel](/docs/privacy-center-custom-css-panel.webp) ![Floating button Custom CSS panel](/docs/floating-button-custom-css-panel.png) ## How Overrides Are Applied Concord composes the widget stylesheet in this order: 1. Base widget stylesheet. 2. Generated branding and theme CSS (from the built-in controls). 3. Your `customCssVariables`. 4. Your `customCss`. Raw CSS wins over token declarations when both target the same final property. Because the widget renders inside a shadow DOM, page-level CSS doesn't leak into the widget and widget CSS doesn't leak into your site. ## Scope Selectors Each widget renders with one of these classes on its root element — you don't add them yourself: * `.cd-consent-banner` * `.cd-privacy-center` * `.cd-floating-button` In the **CSS Variables** textarea, declarations are wrapped automatically in the correct scope. In the **Custom CSS** textarea, prefix your selectors with the matching `.cd-*` class so a rule meant for the privacy center doesn't accidentally match the consent banner or floating button. ## Token Reference (Common) These are the tokens you'll reach for most often. The full list is shown in the **Reference** card inside each widget's Custom CSS panel. ### Shared | Token | Purpose | | ------------------------------- | ---------------------------------------------------------------------------- | | `--cd-color-primary` | Main action color | | `--cd-color-primary-foreground` | Text/icon color on primary actions | | `--cd-color-primary-hover` | Hover state for primary actions | | `--cd-color-secondary` | Secondary / brand background color | | `--cd-color-background` | Base background | | `--cd-color-foreground` | Base text color | | `--cd-color-link` | Link color | | `--cd-color-ring` | Focus ring color | | `--cd-font` | Widget font family | | `--cd-font-scale` | Unitless multiplier that scales every text size proportionally. Default `1`. | | `--cd-radius-button` | Button corner radius | | `--cd-radius-card` | Card corner radius | ### Consent Banner | Token | Purpose | | ---------------------------------------- | ------------------------------------------------------------------ | | `--cd-color-cb-accept-button` | Accept button background | | `--cd-color-cb-accept-button-foreground` | Accept button text | | `--cd-color-cb-deny-button` | Deny button background | | `--cd-color-cb-deny-button-foreground` | Deny button text | | `--cd-color-cb-customize-button-border` | Customize button border | | `--cd-color-cb-link` | Inline link color inside the banner | | `--cd-offset-cb-y` | Distance (px) from the anchored vertical edge | | `--cd-offset-cb-x` | Distance (px) from the anchored horizontal edge (box layouts only) | ### Privacy Center | Token | Purpose | | ------------------------------------- | ------------------------- | | `--cd-color-pc-button` | Primary button background | | `--cd-color-pc-button-foreground` | Primary button text | | `--cd-color-pc-button-outline-border` | Secondary button border | ### Floating Button | Token | Purpose | | -------------------------- | ------------------------------------------------ | | `--cd-color-fb-background` | Floating button background | | `--cd-color-fb-foreground` | Floating button text/icon | | `--cd-offset-fb-circle-x` | Horizontal offset for the circle floating button | | `--cd-offset-fb-circle-y` | Vertical offset for the circle floating button | ## Examples ### Brand Color Swap Paste into the **CSS Variables** box of any widget: ```css --cd-color-primary: #0f766e; --cd-color-primary-foreground: #ffffff; --cd-color-primary-hover: #115e59; ``` ### Consent Banner — Brand Fit Without Breaking Accept/Deny Parity ```css --cd-color-cb-accept-button: #0f766e; --cd-color-cb-accept-button-foreground: #ffffff; --cd-color-cb-deny-button: #e5e7eb; --cd-color-cb-deny-button-foreground: #111827; --cd-color-cb-link: #0f766e; --cd-radius-button: 9999px; ``` Keep Accept and Deny at comparable visual weight — both are real choices and regulators treat them that way. ### Typography ```css --cd-font: 'Inter', system-ui, sans-serif; --cd-font-scale: 1.0625; ``` ### Floating Button Shadow (Raw CSS) Paste into the Floating Button's **Custom CSS** box: ```css .cd-floating-button { box-shadow: 0 12px 32px rgba(3, 7, 18, 0.24); } ``` ### Lift the Banner Above a Sticky Mobile Footer Paste into the Consent Banner's **Custom CSS** box: ```css @media (max-width: 639px) { .cd-consent-banner { --cd-offset-cb-y: 72px; } } ``` ## Troubleshooting ### My Changes Don't Appear * Confirm your plan includes widget custom styling (Pro and above). * Check for typos in the `--cd-*` token name. * Confirm Custom CSS rules use one of the documented `.cd-*` selectors. ### Raw CSS Is Being Overridden by Something Else Raw CSS is applied after token overrides, but if another `.cd-*` rule targets the same property with higher specificity, increase your selector's specificity rather than using page-level CSS. ### I Already Use Legacy Variables Like `--primary`, `--cb-*`, or `--pc-*` Legacy variables are still supported via aliasing. New overrides should prefer the `--cd-*` tokens, but existing configurations don't need to be rewritten immediately. ## Related Documentation * [Configuring the Consent Banner](/docs/configuring-consent-banner) * [Managing Policy Links](/docs/managing-policy-links) * [Consent Management Overview](/docs/consent-management-overview) # Configuring IAB TCF v2.4 URL: /docs/iab-tcf-v2-3-configuration *** title: 'Configuring IAB TCF v2.4' description: 'How to enable and configure IAB Transparency and Consent Framework (TCF) v2.4 in Concord for GDPR-compliant advertising consent, including vendor management, stacks, legitimate interest, and privacy center integration.' created: '2026-02-15T07:00:00.000Z' updated: '2026-10-30T00:00:00.000Z' ----------------------------------- ## Overview IAB TCF v2.4 is the industry-standard framework for collecting and managing user consent across the digital advertising ecosystem. It produces machine-readable Transparency and Consent (TC) strings that tell ad-tech vendors exactly what a user has consented to, replacing ambiguity with a clear, auditable signal. TCF v2.3 introduced a key change that v2.4 keeps: the **Disclosed Vendors** signal is a required component of every consent string. This means vendors can verify whether they were actually presented to the user at the point of consent, strengthening accountability, particularly for legitimate interest scenarios, and aligning more closely with GDPR expectations around informed consent. Organizations that serve ads in GDPR-regulated regions or work with IAB-registered ad-tech vendors should enable TCF in Concord. ## What's New in TCF v2.4 IAB Europe published TCF Specifications v2.4 and the matching Global Vendor List update on July 23, 2026. CMPs must implement the new disclosures on the web by October 23, 2026, and on mobile apps and CTV by February 23, 2027. Concord already supports TCF v2.4. When you select **IAB TCF v2.4** or **IAB TCF v2.4 with Google ATP**, Concord handles the following: * **Standard Features explanation**: the Features layer shows IAB's standard explanation of Features, in the visitor's language. * **Special Purposes notice**: the Vendors layer explains that vendor choices cover purposes and special features only, and that visitors cannot object to special purposes. * **Cross-device notice**: when cross-device consent is on, the first layer says that choices also apply on the visitor's other devices. * **Feature illustrations and Special Feature 2 name**: both come from the Global Vendor List, so they update when the GVL does. * **Disclosed Vendors**: every IAB vendor you select is listed in the Disclosed Vendors segment of the TC string. * **AC strings**: in Google ATP mode, AC strings follow Google's AC v2 format, and Google provider consent is kept separate from IAB vendor consent. * **Languages**: the new strings ship in all 58 banner languages. Purpose, feature, and stack text comes from IAB's own translations, and shows in English for the languages IAB doesn't translate (Irish, Tamil, Telugu, Marathi, Gujarati, Kannada, Malayalam, and Urdu). ## Prerequisites Before enabling TCF, confirm the following: * **Admin access** to your Concord organization * **A project with a configured region template** (TCF settings apply per-project) * **A list of advertising technology vendors** your organization uses * **Understanding of your Google advertising requirements**: specifically whether you need Google Additional Consent support for providers not on the IAB Global Vendor List ## Enabling TCF 1. Navigate to **Privacy > Consent > Consent Settings**. 2. Under **IAB TCF Framework**, open the **Mode** dropdown and select a mode: | Mode | When to use | | -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Disabled** | TCF functionality is off (default). Use if you do not serve ads in GDPR-regulated regions. | | **IAB TCF v2.4** | Standard TCF for IAB-registered vendors. Generates TC strings conforming to the v2.4 specification. | | **IAB TCF v2.4 with Google ATP** | Adds support for Google Additional Technology Providers (ATPs) that are not on the Global Vendor List. Use if your organization runs Google Ad Manager, AdSense, or other Google advertising technologies. | 4. Click **Save**. Once saved, the **Vendors**, **Stacks**, and **Purposes** sub-tabs appear under the IAB TCF section. ### Visitors Outside the GDPR TCF only gathers consent where the GDPR applies. For visitors outside it, the TCF API (`__tcfapi`) still answers, so ad tech can call it everywhere, but it reports `gdprApplies: false`, returns only the fields the TCF CMP API allows in that case, and doesn't write a TC string when the page loads. ### Language The TCF purposes, the banner text, and the language recorded in the TC string always match, following the visitor's language. See [Configuring Automatic Language Translation](/docs/configuring-automatic-language-translation-in-the-consent-banner-concord-privacy-center). ## Managing Vendors ### IAB Vendors 1. With TCF enabled, click the **Vendors** sub-tab under **Privacy > Consent > Consent Settings > IAB TCF**. 2. The vendor table lists all IAB-registered vendors from the Global Vendor List (GVL), showing: * **Vendor Name** and **Vendor ID** * **Purposes**: the data processing purposes each vendor declares * **Framework**: always "IAB" for standard vendors 3. Use **Search** to find vendors by name. 4. Check the box next to each vendor your organization uses. Hover over purpose numbers to see detailed descriptions. 5. Click **Save Selected Vendors** to apply. Click **Discard Changes** to revert. The GVL syncs automatically. Any time you change advertising providers, check for new vendors relevant to your organization. ### Google Additional Technology Providers Available only in **IAB TCF v2.4 with Google ATP** mode: 1. Click the **Google ATPs** tab. 2. Select the Google advertising technology providers your organization uses. 3. Click **Save Selected Providers**. This generates both TC strings and AC (Additional Consent) strings, covering providers outside the standard GVL. ## Configuring Stacks TCF Stacks group related purposes and special features together, simplifying the consent experience for end users. Instead of presenting each purpose individually, stacks bundle related processing activities. 1. Click the **Stacks** sub-tab. 2. Review the available stacks. Each shows a name, description, included purposes, and special features. 3. Check the stacks that match your use case and click **Save Selected Stacks**. ### Resolving Stack Conflicts Concord automatically detects when selected stacks share purposes or special features. If a conflict is flagged: * Select only one stack from the conflicting group, or * Switch to individual purpose management instead of stacks * Consult your privacy team if the correct grouping is unclear ## Purposes and Special Features Click the **Purposes** sub-tab for a reference view of all IAB purposes, including purpose ID, name, description, and legal description. Purposes align with standard categories: Analytics, Marketing, Functional, and Strictly Necessary. Two **special features** require explicit user consent: * **Precise Geolocation**: access to precise location data * **Device Scanning**: active device fingerprinting ## Legitimate Interest TCF v2.4 recognizes legitimate interest as a legal basis separate from consent. Enabling it gives users independent controls for consent and legitimate interest on applicable purposes. ### Enabling Legitimate Interest 1. In TCF Settings, locate the **Enable Legitimate Interest** toggle. 2. Toggle **ON** and click **Save**. When enabled, users see separate controls for consent and legitimate interest. Legitimate interests are never automatically assigned. Users must explicitly grant them, even when they consent to a related category such as marketing or analytics. When disabled, only consent controls are displayed and all processing requires explicit consent. Disabling legitimate interest is appropriate for organizations following a strict interpretation of TCF v2.4. ## Google Advertiser Consent Mode Google can derive Consent Mode signals directly from your TCF consent string. When you enable this integration, Concord sets the `enableAdvertiserConsentMode` flag on the `TCData` object exposed through the TCF API. Google then infers **`ad_storage`**, **`ad_user_data`**, and **`ad_personalization`** from the TC string, rather than relying on separate Google Consent Mode signals for those types. This integration is your choice and is **off by default**. ### Enabling Advertiser Consent Mode 1. In TCF Settings, locate the **Allow Google Consent Mode to read TCF signals** toggle. 2. Toggle **ON** to set `enableAdvertiserConsentMode` on the TCData object. 3. Click **Save**. ### Notes * This setting is independent of the **Google Consent Mode (GCM)** mode you select on the **Integrations** tab under **Privacy > Consent > Consent Settings** (per region). `analytics_storage` is still driven by Google Consent Mode, so keep GCM set to **Basic** or **Advanced** (not **Disabled**) to signal it alongside TCF. * If TCF is enabled but Google Consent Mode is set to **Disabled**, no Consent Mode signals are sent to Google at all, including `analytics_storage`. Concord shows a warning in the admin in that case. * For background, see Google's [Implement the Transparency & Consent Framework](https://developers.google.com/tag-platform/security/guides/implement-TCF-strings) guide. For full setup of the Google Consent Mode integration, see [Understanding & Configuring Google Consent Mode (GCM) V2](/docs/google-understanding-configuring-google-consent-mode-gcm-v2). ## Privacy Center Integration When TCF is enabled, the privacy center automatically adapts to present TCF-specific information. ### Tab Ordering The privacy center displays **Purposes & Features** before **Vendors**, so users understand what their data is used for before seeing which vendors process it. ### Button Layout * **Accept All** and **Reject All** are grouped together for quick decisions * **Confirm Choices** appears separately for users who customize individual preferences ### Category Detail Pages When a user views a consent category (e.g., Marketing or Analytics), the detail page shows: * **Vendor Information**: TCF vendors that process data for this category * **Purpose Details**: specific IAB purposes associated with the category * **Navigation Links**: direct links to the full vendor and purpose lists The layout is responsive: two-column grid on desktop, single-column on mobile. ## Cross-Device Consent If cross-device identity is enabled for your organization, TCF consent follows users across devices automatically. A user who grants consent on their laptop will have that same TCF consent applied on their phone once identified. No additional TCF-specific configuration is required. For setup details, see [Implementing Cross-Device Identity and Consent](/docs/implementing-cross-device-identity-and-consent). ## Reporting TCF consent events appear in the standard Concord reporting dashboards alongside other consent activity. You can filter by consent type, purpose, and vendor to see which vendors users accept or reject most frequently. TC string generation events and consent updates are logged as part of your project's consent audit trail. ## Testing Your Configuration ### Verify the TCF API 1. Visit your website where Concord is installed. 2. Open browser developer tools (Console tab). 3. Run: ```javascript __tcfapi('ping', 2, function (pingData) { console.log('TCF API Status:', pingData); }); ``` The response should show `cmpLoaded: true` and our CMP ID, 491. ### Verify TC String Generation 1. Clear your browser's localStorage for the site. 2. Visit the site and interact with the consent banner. 3. Run: ```javascript __tcfapi('getTCData', 2, function (tcData) { console.log('TC String:', tcData.tcString); console.log('Vendor Consents:', tcData.vendor.consents); console.log('Purpose Consents:', tcData.purpose.consents); }); ``` 4. Confirm the TC string is non-empty and vendor/purpose consent objects reflect your selections. ### Verify Google AC String If using Google Additional Consent mode, check for `addtlConsent` in the TC data: ```javascript __tcfapi('getTCData', 2, function (tcData) { console.log('AC String:', tcData.addtlConsent); }); ``` ### Verify Advertiser Consent Mode If you enabled **Allow Google Consent Mode to read TCF signals**, confirm the flag is present on the TCData object: ```javascript __tcfapi('getTCData', 2, function (tcData) { console.log('Advertiser Consent Mode:', tcData.enableAdvertiserConsentMode); }); ``` This returns `true` when the setting is enabled and `false` (or `undefined`) when it is off. The flag is also present in `addEventListener` callbacks, so it persists as consent changes. ## Ongoing Maintenance | Cadence | Action | | ------------- | -------------------------------------------------------------------------------------------------------- | | **Weekly** | Review the GVL sync for new vendors relevant to your organization. The sync runs automatically. | | **Monthly** | Audit selected vendors to confirm they are still in use. Review consent metrics in reporting dashboards. | | **Quarterly** | Review stack selections. Audit compliance with current regulations. | ## Troubleshooting **TCF API not available** (`__tcfapi` is undefined) * Verify TCF mode is not set to Disabled on the **General Settings** tab under **Privacy > Consent > Consent Settings**. * Confirm the Concord script is loading without errors. **Vendors not appearing in the table** * Confirm TCF mode is saved and active. * Wait for the weekly GVL sync to complete. * Verify the vendor exists in the current IAB Global Vendor List. **Consent not persisting across visits** * Check that browser localStorage is not disabled or full. * Verify third-party cookie settings are not blocking storage. * Confirm the domain configuration matches between your site and Concord settings. **TC string is empty or malformed** * Verify at least one vendor is selected. * Confirm required purposes are configured. * Check the browser console for error messages. **Google is not deriving ad consent from TCF** * Confirm the **Allow Google Consent Mode to read TCF signals** toggle is ON on the **General Settings** tab (IAB TCF box). * Verify Google Consent Mode is not set to **Disabled**. When TCF is enabled but GCM is Disabled, no Consent Mode signals are sent. Set GCM to **Basic** or **Advanced** on the **Integrations** tab under **Privacy > Consent > Consent Settings**. * In the browser console, run the `getTCData` check above and confirm `enableAdvertiserConsentMode` returns `true`. If these steps do not resolve the issue, contact Concord support at [support@concord.tech](mailto:support@concord.tech) with your organization ID and any console error messages. # Implementing Cross-Device Identity and Consent URL: /docs/implementing-cross-device-identity-and-consent *** title: 'Implementing Cross-Device Identity and Consent' description: "A step-by-step guide for developers to implement Concord's cross-device identity resolution, ensuring a user's consent choices follow them across every browser and device." created: '2026-03-17T00:00:00.000Z' updated: '2026-03-17T00:00:00.000Z' ----------------------------------- ## Overview A single person often visits your site from multiple devices — a phone, a laptop, a tablet. Without cross-device identity, each device is treated as a separate visitor with its own consent state. Concord's Identity system solves this by linking anonymous browser sessions to a known user. When someone identifies themselves (for example, by logging in), their consent choices follow them across every device and project in your organization. This guide walks you through the full integration, from generating authentication keys to calling `identify()` in your frontend code. ## How Concord Identifies Users Before diving into code, it helps to understand the three layers Concord uses to track visitors and their consent. | Concept | What It Represents | Lifetime | | ------------ | ------------------- | ------------------------------------------------ | | **Identity** | The person | Permanent — survives across devices and sessions | | **Context** | A browser or device | Created once per browser, never changes | | **Session** | A single visit | Short-lived, used for API authentication | Here's how they relate: ```text One Person (Identity) └── Many Devices (Context) └── Many Visits (Session) ``` * One identity can have many contexts — the same person on their laptop and phone. * One context can have many sessions — multiple visits from the same browser over time. * **Consent is stored on the identity**, so it follows the person everywhere. ### What Happens When a Visitor Arrives When someone first visits your site, Concord automatically creates all three: a new session for this visit, a new context for this browser, and a new anonymous identity. At this point the visitor is anonymous, but their consent choices are already tied to their identity. ### What Happens During `identify()` When the visitor identifies themselves (for example, after login), Concord links their anonymous identity to a known one: * **First device**: The visitor's anonymous identity gains an email (or userId) alias. Nothing else changes — `synced: false`. * **Second device**: A different anonymous identity exists on this browser. When the visitor identifies with the same email, Concord finds the existing identity from the first device, merges the two, and syncs consent — `synced: true`. After a merge, the browser's context stays the same — only which identity it belongs to is updated. The visitor's consent from the first device is now available on the second. ## Prerequisites Before beginning the integration, ensure the following: 1. **Cross-device consent enabled** in your Concord Organization settings (**Advanced Settings > Cross-Device Consent**). 2. **Concord site-client snippet** installed and initialized on your site. 3. **An asymmetric key pair** for JWT authentication (required for email and userId flows — not needed for contextId). ## Step 1: Set Up Authentication Keys Concord uses JWT authentication to verify identity requests. Your server signs a short-lived token with a private key; Concord verifies it with the corresponding public key you upload. ### Generate an EC P-256 Key Pair ```bash # Generate EC private key openssl ecparam -genkey -name prime256v1 -noout -out identify-key.pem # Extract public key openssl ec -in identify-key.pem -pubout -out identify-key-pub.pem ``` ### Convert to JWK Format Concord accepts public keys in JWK format. You can convert your PEM keys using a tool like [jwt.io](https://www.jwt.io/) or with the Node.js scripts below. **Private key JWK** (keep this secret — used on your server to sign tokens): ```bash node -e " const crypto = require('crypto'); const fs = require('fs'); const priv = crypto.createPrivateKey(fs.readFileSync('identify-key.pem')); const jwk = priv.export({ format: 'jwk' }); jwk.kid = 'my-key-1'; jwk.alg = 'ES256'; jwk.use = 'sig'; console.log(JSON.stringify(jwk, null, 2)); " > identify-private.jwk ``` **Public key JWK** (upload this to Concord): ```bash node -e " const crypto = require('crypto'); const fs = require('fs'); const pub = crypto.createPublicKey(fs.readFileSync('identify-key-pub.pem')); const jwk = pub.export({ format: 'jwk' }); jwk.kid = 'my-key-1'; jwk.alg = 'ES256'; jwk.use = 'sig'; console.log(JSON.stringify(jwk, null, 2)); " > identify-public.jwk ``` ### Upload the Public Key Upload your public key via the Concord admin UI under **Deployment > Advanced Settings > Public Keys**. The `kid` value you set here (e.g., `my-key-1`) must match the `kid` in the JWT header your server generates. ## Step 2: Generate Tokens on Your Server Your server must generate a JWT for each identify call. The token proves the request is legitimate and prevents impersonation. ### Required JWT Fields | Field | Location | Required | Description | | ----- | -------- | -------- | ----------------------------------------------------- | | `alg` | Header | Yes | Algorithm — e.g., `ES256` for EC P-256 | | `kid` | Header | Yes | Must match the `kid` of an uploaded public key | | `sub` | Payload | Yes | Must exactly match the `value` passed to `identify()` | | `exp` | Payload | Yes | Expiration timestamp (maximum 10 minutes from now) | | `aud` | Payload | Optional | If present, must match your Organization ID | ### Option A: Node.js `crypto` (Zero Dependencies) ```javascript const crypto = require('crypto'); const fs = require('fs'); const privateKey = crypto.createPrivateKey(fs.readFileSync('identify-key.pem')); function generateIdentifyToken(identifyValue) { const b64url = (obj) => Buffer.from(JSON.stringify(obj)).toString('base64url'); const header = { alg: 'ES256', kid: 'my-key-1' }; const payload = { sub: identifyValue, exp: Math.floor(Date.now() / 1000) + 300, // 5 minutes }; const data = b64url(header) + '.' + b64url(payload); const sig = crypto .sign('SHA256', Buffer.from(data), privateKey) .toString('base64url'); return data + '.' + sig; } ``` ### Option B: Using `jsonwebtoken` ```bash npm install jsonwebtoken ``` ```javascript const jwt = require('jsonwebtoken'); const fs = require('fs'); const privateKey = fs.readFileSync('identify-key.pem'); function generateIdentifyToken(identifyValue) { return jwt.sign({ sub: identifyValue }, privateKey, { algorithm: 'ES256', expiresIn: '5m', keyid: 'my-key-1', }); } ``` ### Deliver the Token to the Browser Pass the token to your frontend via an API endpoint, a page template variable, or any secure channel. The token is short-lived and scoped to a single identity value. ```javascript // Example: API endpoint (behind your existing auth) app.get('/api/identify-token', authenticate, (req, res) => { const { email } = req.user; // from your auth/session const token = generateIdentifyToken(email); res.json({ token, email }); }); ``` On the client side, fetch the token and pass both values to `identify()`: ```javascript const { token, email } = await fetch('/api/identify-token').then((r) => r.json(), ); await window.concord.identify(email, { token }); ``` ## Step 3: Identify Users in the Browser There are several integration patterns depending on when and how you know the user's identity. ### Pattern A: After Login (Most Common) Call `identify()` after the user logs in or when your app confirms their identity. The first argument is the identifier value (such as an email address), and the `token` option is the JWT from your server. ```javascript async function onUserLogin(email, jwtToken) { const result = await window.concord.identify(email, { token: jwtToken, }); if (result.synced) { // Consent was synced from another device. // The SDK has already refreshed consent data — no action needed. console.log('Consent synced from another device'); } else { // First time identifying with this email, or same identity. // No merge happened — consent banner will show as normal. console.log('Identity registered'); } } ``` ### Pattern B: Server-Rendered Pages (Pre-Init) For pages where the user's identity is known before the Concord snippet loads (for example, server-rendered authenticated pages), set `window.concordIdentity` before the SDK initializes. This resolves identity during initialization, **before** the consent banner renders — preventing a "flash of consent banner" for returning users. ```html {/* Concord snippet */} ``` ### Pattern C: Customer ID (userId) If you identify users by an internal customer ID rather than email: ```javascript const result = await window.concord.identify('customer-12345', { type: 'userId', token: jwtToken, // JWT sub must be 'customer-12345' }); ``` The userId is stored as-is (not hashed) and is scoped to your organization. The same userId will match across all projects within your organization. ### Pattern D: ContextId (No JWT Needed) If you have a contextId from another session (for example, from a cross-domain flow), you can use it to link two sessions without JWT authentication: ```javascript const result = await window.concord.identify(otherContextId, { type: 'contextId', }); ``` Or via pre-init: ```javascript window.concordIdentity = { type: 'contextId', value: otherContextId, }; ``` **Why no JWT?** A contextId is a cryptographically random UUID — it is not personally identifiable. Concord validates that the referenced context exists before merging. ## Step 4: Handle the Result ### Return Values | Field | Type | Description | | -------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------- | | `synced` | `boolean` | `true` if consent was synced from another device; `false` if this is the first identification or the identity already matches | | `error` | `Error` (optional) | Present if something went wrong | When `synced` is `true`, the SDK automatically: 1. Updates the session token 2. Refreshes consent data from the server 3. Dispatches a `concord-identity-synced` event You do not need to manually refresh consent or update the session. ### Event Listeners ```javascript // React to identity sync window.addEventListener('concord-identity-synced', (event) => { console.log('Identity synced:', event.detail.synced); }); // React to identity reset (logout) window.addEventListener('concord-identity-reset', () => { console.log('Identity reset to anonymous'); }); ``` ## Step 5: Handle Logout When a user logs out, call `reset()` to clear the session and create a new anonymous identity. This ensures the next visitor on a shared device starts fresh and does not inherit the previous user's consent. ```javascript async function onUserLogout() { await window.concord.reset(); // Session cleared, new anonymous identity created. // The consent banner will reappear on the next page load. } ``` ## Advanced: Pre-Hashed Emails By default, Concord hashes emails server-side using a per-organization salt. If you prefer to hash emails on your own server before sending them to the browser (to avoid exposing plaintext emails in client-side code), use the `format: 'hashed'` option: ```javascript const result = await window.concord.identify(hashedEmail, { type: 'email', format: 'hashed', token: jwtToken, // JWT sub must match the hashed value }); ``` When using `format: 'hashed'`: * The value is used as-is (Concord does not hash it again) * No email format validation is performed * The JWT `sub` claim must match the hashed value, not the original email ## Configuration Reference ### `identify()` Parameters ```javascript window.concord.identify(value, options); ``` | Parameter | Type | Required | Description | | ---------------- | ------ | ----------- | ----------------------------------------------------------------------------------------- | | `value` | string | Yes | The identifier — an email, userId, or contextId | | `options.type` | string | No | `'email'` (default), `'userId'`, or `'contextId'` | | `options.format` | string | No | `'plain'` (default) or `'hashed'` — only applies to email type | | `options.token` | string | Conditional | JWT signed by your server. Required for `email` and `userId`. Not needed for `contextId`. | ### `window.concordIdentity` (Pre-Init) | Property | Type | Required | Description | | -------- | ------ | ----------- | ----------------------------------------------------------------------------------------- | | `type` | string | Yes | `'email'`, `'userId'`, or `'contextId'` | | `value` | string | Yes | The identifier value | | `format` | string | No | `'plain'` (default) or `'hashed'` — only applies to email type | | `token` | string | Conditional | JWT signed by your server. Required for `email` and `userId`. Not needed for `contextId`. | ## Frequently Asked Questions 1. **I'm getting a `403 Forbidden` error on `/identify`.** Cross-device consent is not enabled for your organization. Enable it in the admin UI under **Advanced Settings > Cross-Device Consent**, or contact your Concord administrator. 2. **I'm getting a `401 Unauthorized` error on `/identify`.** The JWT is missing, expired, or invalid. Check that: * The `token` option is included in your `identify()` call (required for email and userId) * The JWT `sub` claim matches the `value` you passed to `identify()` exactly * The JWT `kid` matches a public key uploaded to your organization * The JWT `exp` is in the future (maximum 10 minutes from now) * The algorithm is asymmetric (ES256, RS256, etc.) — HMAC algorithms are not accepted 3. **`identify()` returns `synced: false` — is something wrong?** Not necessarily. `synced: false` is expected in these cases: * **First identification**: The first time Concord sees an email or userId, no match exists yet. The alias is registered for future matches. * **Same identity**: If the current session already belongs to the matched identity, no merge is needed. * **Different organization**: Alias lookups are scoped to your organization. Sessions from different organizations will not match. 4. **The consent banner still shows after calling `identify()`.** * Verify that `identify()` returned `synced: true` with no error. * The SDK automatically refreshes consent data after a successful sync. If the banner persists, check that consent was actually recorded on the target identity (the one that was identified first on another device). * Ensure the consent types in the target identity's project match the active Region Template for your current project. 5. **My pre-init identity (`window.concordIdentity`) isn't working.** * It must be set **before** the Concord snippet loads. * The value must be an object with at least `type` and `value` properties. * The property is consumed once during initialization — it cannot be reused on the same page. 6. **Does the contextId flow require a JWT?** No. Since a contextId is a cryptographically random UUID (not personally identifiable), it does not require JWT authentication. This makes it ideal for cross-domain syncing where you may not have a server-side token endpoint on every domain. 7. **What happens to consent when a user logs out?** When you call `reset()`, the session is cleared and the browser returns to an anonymous state. The next visitor on that device will not inherit the previous user's consent — they will start fresh with a new anonymous identity. # Manually Blocking Trackers Before Consent URL: /docs/manually-blocking-trackers-before-consent *** title: 'Manually Blocking Trackers Before Consent' description: 'Learn how to manually block a tracker when needed using Concord' created: '2025-06-20T11:02:57.000Z' updated: '2025-12-05T13:29:11.000Z' ----------------------------------- In most cases, **manual intervention is not required** thanks to Concord's advanced tracker **auto-detection and blocking system**. However, if you're encountering a particularly problematic script or want to **guarantee a tracker is blocked** before consent is given, you can use one of our **manual blocking methods**. ## When to Use Manual Blocking Use this approach **only when**: * A tracker is **executing too early** before Concord can intercept it * An inline tracker is **making a network request** you would like to stop prior to auto-blocking * You're troubleshooting a script that **evades detection** * You want **complete control** over when and how a script loads based on consent * A script **dynamically constructs URLs** at runtime (e.g., from configuration variables) ## Method 1: HTML Attribute Blocking (For Scripts with Static URLs) This method works for scripts that have a **static `src` attribute**. Concord will restore the `src` and re-enable the script when consent is granted. ### Instructions To manually block a tracker from running until Concord has processed the page and consent is determined, update the ` {/* Manually blocked version (will wait for consent) */} ``` This will prevent the script from loading or executing **until** Concord detects and reactivates it, based on user consent. *** ## Method 2: JavaScript API (For Dynamic or Inline Scripts) Some trackers use **inline scripts that dynamically inject other scripts** at runtime. These cannot typically be blocked using HTML attributes because: * The script URL is **constructed dynamically** (e.g., from configuration variables) * There's **no static `src`** for Concord to restore For these cases, use Concord's **JavaScript API** to conditionally load scripts based on consent. ### API Reference #### window\.concord.consent.hasConsent(category) Check if consent has been granted for a specific category. ```javascript if (window.concord.consent.hasConsent('marketing')) { // User has consented to marketing - safe to load tracker loadTracker(); } ``` Parameters: * `category` (string): The consent category (`'marketing'`, `'analytics'`, `'functional'`, etc.) **Returns:** `boolean` - `true` if consent granted, `false` otherwise #### window\.concord.consent.onConsent(category, callback) Register a callback to execute when consent is granted. If consent is **already granted**, the callback executes **immediately**. The callback will only fire once, then the listener is automatically removed. ```javascript window.concord.consent.onConsent('marketing', function () { // This runs when marketing consent is granted loadTracker(); }); ``` Parameters: * `category` (string): The consent category * `callback` (function): Function to execute when consent is granted ### Example: Blocking a Dynamic Script Loader Some trackers configure settings in a variable and then dynamically inject scripts. Here's how to make them consent-aware: **Original script (ignores consent):** ```html ``` **Consent-aware version:** ```html ``` ### Example: Simple Conditional Loading For simpler cases where you just need to check consent before loading: ```html ``` *** ## Which Method Should I Use? | Scenario | Recommended Method | | ------------------------------------------ | ------------------------- | | Script has a static `src` attribute | Method 1: HTML Attributes | | Script dynamically builds URLs from config | Method 2: JavaScript API | | Inline script that injects other scripts | Method 2: JavaScript API | | Custom tracking code you control | Method 2: JavaScript API | *** ## Best Practices * **Don't use this for every tracker.** Use only for problematic scripts or scripts that require guaranteed pre-consent blocking * Concord will automatically handle most common marketing, analytics, and advertising trackers * Method 1 (HTML attributes) is fully compatible with `async` and `defer` attributes - Concord will restore them when reinserting the script * **Prevent double-loading** when using Method 2 - use a flag variable to ensure your tracker only loads once * **Always check for `window.concord`** - the API may not be available immediately if your script runs before Concord loads *** ## Events Reference Concord emits events you can listen to for custom integrations: | Event | Description | | ------------------------------- | ------------------------------------------------------------ | | `concord-loaded` | Fired when the Concord script has loaded | | `concord-config-ready` | Fired when Concord configuration is loaded | | `concord-ready` | Fired when Concord has fully initialized and is ready to use | | `concord-unavailable` | Fired when Concord aborts and is unavailable | | `concord-consent-state-loading` | Fired when consent state is being fetched | | `concord-consent-state-loaded` | Fired when consent state has finished loading | | `concord-consent-state-changed` | Fired when the user updates their consent preferences | ### Example Usage ```javascript window.addEventListener('concord-ready', function () { console.log('Concord is ready'); }); ``` ```javascript window.addEventListener('concord-consent-state-changed', function () { console.log('User updated consent preferences'); }); ``` *** If you're unsure whether manual blocking is needed for a particular script, [contact support](mailto:support@concord.tech) and we'll help you evaluate the best approach. # Running Compliance Scans URL: /docs/running-compliance-scans *** title: 'Running Compliance Scans' description: 'Test how your live site handles consent: choose jurisdictions and checks, run a Compliance Scan once or on a schedule, and turn failed checks into tasks.' created: '2026-09-28T00:00:00.000Z' updated: '2026-10-30T00:00:00.000Z' ----------------------------------- ## Overview A **Compliance Scan** loads your live site the way a visitor would and tests how it actually behaves: whether trackers fire before consent, whether rejecting really stops them, whether the site honors Global Privacy Control, and more. Choose the jurisdictions you care about, and each scan loads your site from that region, so it sees the consent experience a visitor there would see. Compliance Scans are included in Concord Privacy **Premium** and **Enterprise**. If you don't see **Compliance Scan** in the Actions catalog, check your plan under **Global Settings → Billing**, or [contact us](/contact?subject=demo). {/* Screenshot pending: Actions > Browse Catalog > Compliance Scan configuration -> /docs/compliance-scan-configure.png */} ## Setting Up a Compliance Scan 1. Go to **Actions → Browse Catalog** and choose **Compliance Scan**. 2. Choose the domain or subdomain to scan. 3. Choose one or more jurisdictions. 4. Choose which checks to run. Checks a jurisdiction requires are turned on for you. 5. Run the scan once, or set it to run on a schedule. ## Jurisdictions * California (CCPA/CPRA) * European Union / UK (GDPR) * United States (General) * Canada (PIPEDA) * Brazil (LGPD) * India (DPDPA) Checks follow the jurisdiction. Under opt-in regimes like GDPR, tracking before consent is a failure. Under opt-out laws like CCPA/CPRA, it's advisory. ## Checks * **Pre-consent tracking:** checks whether non-essential trackers fire before the visitor gives consent. * **Global Privacy Control:** sends a GPC signal and checks that the site treats it as an opt-out, as several state laws require. * **Choice symmetry:** checks that rejecting is as easy as accepting, with no dark-pattern imbalance in the banner. * **Reject efficacy:** after the visitor rejects, checks that non-essential trackers actually stop firing. * **Privacy policy freshness:** finds the linked privacy policy and checks that it was updated in the last 12 months. * **Data-subject request intake:** scans the policy for a way to exercise data rights, such as a form, an email address, or an account page. * **Consent-state mismatch:** checks that observed tracking matches the consent the visitor actually granted. * **Do Not Sell or Share (CCPA):** checks for a working Do Not Sell or Share opt-out, as CCPA/CPRA requires. * **Third-party tracking (CIPA):** checks whether third-party pixels or session replay send data before consent. ## Reading Results Each run appears in the **Activity** list under **Actions**. Expand a run to see: * An overall **Risk** level of **Low**, **Medium**, or **High**, based on the problems found. * Each check's result: **Pass**, **Fail**, or **Inconclusive** when there isn't enough evidence to call it. A check can also show **Not applicable** for the jurisdiction, or **Disabled** if you turned it off for this scan. * For each check, what was checked, what was found, and how to fix it. {/* Screenshot pending: Actions > Activity, expanded Compliance Scan run -> /docs/compliance-scan-results.png */} ## Turning Failures Into Tasks On any failed check, click **Create task** to open a task for the fix, so it stays on your team's list until it's resolved. ## Cost Each scan uses **2,500 Actions** plus up to **50 Data Credits** for each jurisdiction it covers. If the scan can't load your site at all, it isn't charged. See [Actions and Data Credits](/docs/actions-data-credits). ## Related Articles * [Scanning Your Site for Trackers and Cookies](/docs/scanning-trackers-cookies-scripts) * [Google Consent Mode V2 (GCM) Scanning User Guide](/docs/google-gcm-scanning-user-guide) * [Actions and Data Credits](/docs/actions-data-credits) # Scanning Your Site for Trackers and Cookies URL: /docs/scanning-trackers-cookies-scripts *** title: "Scanning Your Site for Trackers and Cookies" description: 'Choose which domains and subdomains Concord scans for trackers, set a schedule or scan on demand, have AI suggest details for new trackers, and review what each scan finds.' created: '2025-11-01T11:02:57.000Z' updated: '2026-11-18T00:00:00.000Z' ----------------------------------- Concord's tracker scanning finds the cookies, scripts, iframes, images, and other trackers running on your websites, so your Cookies & Scripts list stays current. You control exactly what each scan covers, how often it runs, and what it costs. This guide covers how to: * Choose which domains and subdomains a scan covers * Scan on a schedule or on demand * Understand scan frequency and cost * Turn on Deep Scan and Real-Time Scan * Have AI suggest details for new trackers * Review scan history and scan results {/* Screenshot pending: Consent > Cookies & Scripts > Settings (Scan Coverage & Schedule) -> /docs/trackers-scan-coverage-schedule.png */} ## Choosing What a Scan Covers Each project has one tracker scan that covers its domains in a single run. Set it up under **Consent → Cookies & Scripts → Settings**, in the **Scan Coverage & Schedule** card. * **Project Domains:** every domain in the project is included by default. Uncheck a domain to leave it out of the scan. * **Extra Subdomains:** add subdomains beyond your project domains, like `app.yourdomain.com`. Each extra subdomain uses 1,000 Actions on every run, scheduled or on demand. ## Scanning on a Schedule 1. Go to **Consent → Cookies & Scripts → Settings**. 2. In **Scan Coverage & Schedule**, turn on **Enable Scheduled Scans**. 3. Choose how often the scan runs: daily, weekly, monthly, or quarterly, up to what your plan allows (see [Scan Frequency by Plan](#scan-frequency-by-plan)). New schedules default to monthly. 4. Save your settings. Concord picks an off-peak time for each scheduled run, so there's no day or hour to set. Scheduled runs include your registered project domains at no cost; only extra subdomains use Actions. ## Scan Frequency by Plan Your plan sets how often scheduled scans can run. See [pricing](https://concord.tech/pricing) for plan details. * **Lite:** quarterly * **Essentials:** monthly * **Pro:** weekly * **Premium and Enterprise:** daily Scheduled scans are available on paid plans. On-demand scans are available on every plan, including Free. ## Scanning on Demand 1. Go to **Consent → Cookies & Scripts → Scan History**. 2. Click **Scan Now**. 3. Review the cost shown in the confirmation, then confirm. Your first 5 on-demand scans each month are free. After that, an on-demand scan uses 1,000 Actions for each domain it scans, including your project domains. The confirmation tells you which applies before you run it. See [Actions and Data Credits](/docs/actions-data-credits). ## Tracker Scan Settings Under **Consent → Cookies & Scripts → Settings**, the **Tracker Scan Settings** card has options for broader coverage: * **Enable Deep Scan:** looks for less common potential trackers (scripts, iframes, links, images, and more) that don't match Concord's global tracker library. Deep Scan surfaces many more items and usually needs a longer review. Most can be ignored, but anything that interacts with or stores customer data should be classified. It's most useful during audits or stricter compliance checks. * **Enable Real-Time Scan:** detects cookies and scripts as visitors use your site, which catches trackers that only load in certain situations. Detected items appear in **Scan Results** for review. * **Auto-Add Backend Scan Matches:** adds scheduled and on-demand scan detections that match Concord's global tracker library to your Cookies & Scripts list automatically. When it's off, matches still appear in **Scan Results** for you to add. * **Auto-Add Real-Time Scan Matches:** does the same for real-time detections. It's off by default so you can review real-time matches first. ## Identifying New Trackers With AI A tracker with no known match shows as **New**, with no name, company, or category. Concord can ask AI to suggest those details for you: * **After every scheduled scan.** In **Consent → Cookies & Scripts → Settings → Scan Coverage & Schedule**, turn on **Identify New Trackers With AI**. After each scan, AI suggests a name, company, category, domain, and description for each new tracker it found. * **For trackers you select.** On **Scan Results**, ask AI to suggest details for the new trackers you choose. Suggestions are prepared in the background. Nothing is added to your Cookies & Scripts list until you add it, so you review each suggestion first. Each tracker sent to AI uses Actions and Data Credits, and a tracker whose pattern was already identified in this project is free. See [Actions and Data Credits](/docs/actions-data-credits). ## Scan History Go to **Consent → Cookies & Scripts → Scan History** to see every scan run for the project, with its date, trigger, result, and duration. Expand a run to see its results, including total trackers, new trackers, project matches, and global matches. If a scan run fails before it can report, Concord opens a [task](/docs/tasks-my-work) so someone looks into it. The task resolves on its own after the next scan that runs cleanly. {/* Screenshot pending: Consent > Cookies & Scripts > Scan History -> /docs/trackers-scan-history.png */} ## Scan Results Go to **Consent → Cookies & Scripts → Scan Results** to categorize and associate the cookies and scripts discovered by real-time and scheduled scans. This list is different from the **Cookies & Scripts** tab. **Cookies & Scripts** is your production list: it decides which trackers are blocked and shown to visitors on your site. **Scan Results** shows what recent scans found, so you can decide what to add. Each detected tracker shows how it matched: * **Project:** already in your Cookies & Scripts list. * **Global:** matches a tracker in Concord's global library. * **New:** no known match. You can add it to your Cookies & Scripts list from here. Each tracker appears once, however many times it's found. The **Source** column shows where it was last found: **Scan** for scheduled and on-demand scans, or **Live Site** for [Real-Time Scan](#tracker-scan-settings) detections. When a scan finds a tracker that was already detected on the live site, the scan's result replaces the live-site row. **Last Seen** shows when it was most recently found, so you can sort by it to spot trackers that may have been removed from your site. Click **Add** to move a discovered tracker into your Cookies & Scripts list. For how to categorize unclassified or ignored trackers, see [Discovery and Classification of Trackers (Cookies & Scripts)](/docs/classifying-trackers-cookies-scripts). You can also sort, filter, and export the list to CSV. The export includes the Source and Last Seen columns. ## Related Articles * [Running Compliance Scans](/docs/running-compliance-scans) * [Google Consent Mode V2 (GCM) Scanning User Guide](/docs/google-gcm-scanning-user-guide) * [Understanding & Configuring Google Consent Mode (GCM) V2](/docs/google-understanding-configuring-google-consent-mode-gcm-v2) * [Actions and Data Credits](/docs/actions-data-credits) # Configuring Auto-Blocking of Cookies and Scripts URL: /docs/understanding-configuring-auto-blocking-of-cookies-scripts *** title: "Configuring Auto-Blocking of Cookies and Scripts" description: 'Understanding and configuring Concord to enable auto-blocking of cookies and tracking scripts and required user consent settings.' created: '2023-10-06T02:03:51.000Z' updated: '2026-03-16T04:38:21.000Z' ----------------------------------- ## Overview When visitors arrive on your website, their browser may download tracking scripts and accept cookies by default upon the first page view of their session. In some jurisdictions, like the EU with GDPR, this can violate privacy regulations that require a user to actively consent prior to the serving of cookies or tracking scripts. Concord provides a **Blocking Mode** that can be configured per project in order to either prevent or allow this from happening. There are four options available when it comes to **Blocking Mode**: * **Disabled:** No blocking of cookies and scripts will occur. * **Discovery:** Used to capture the cookies and scripts on your site for categorization without blocking. This is helpful for implementation when you are not certain about the number and nature of tracking scripts and cookies in use by the site. * **Permissive:** This mode will allow Strictly Necessary, Ignored, & Unclassified cookies and scripts to run until user consent preferences are set. * **Strict:** This mode will only allow Strictly Necessary & Ignored cookies and scripts until user consent preferences are set. Scripts that are set as Ignored are not known trackers and are marked as Ignored to avoid issues on your site, but should be classified when they track users in any fashion. This is required for compliance with stricter data privacy regulations like GDPR. The selected **Blocking Mode** then works in tandem with the selected **Consent Mode** to give you the flexibility to adjust the desired behavior per project. Where **Blocking Mode** determines how cookies and scripts are blocked, **Consent Mode** determines if the user has to expressly indicate consent or if consent is implied. Express consent is required by stricter laws like GDPR, while implied consent is all that is required in jurisdictions like California with CCPA & CPRA. We typically recommend going with the stricter version to be globally compliant (**Blocking Mode = Strict** and **Consent Mode = Express**), but you can adjust these per region if desired. ## Configuring Auto-Blocking of Cookies & Scripts Use the following information to setup and configure the general consent settings for a specific region in your project. ### Configuring Blocking Mode In order to configure the **Blocking Mode**: * Navigate to **Privacy → Consent → Consent Settings → General Settings**. * Under the **General Settings** tab, you will see a drop down list for **Blocking Mode**. Choose your desired blocking mode (Disabled, Discovery, Permissive, Strict). * **Discovery** mode collects information from your site which is used to classify tracking scripts and cookies without blocking them. * **Permissive** mode blocks categorized scripts and cookies, while unclassified cookies are still allowed. * **Strict** is recommended as all scripts and cookies that aren’t categorized as strictly necessary are blocked. This is required for full compliance with stricter privacy laws like GDPR. ![](/docs/understanding-configuring-auto-blocking-of-cookies-scripts-consent-settings.webp) ### Configuring Consent Mode For all blocking modes except Disabled, you may also select the **Consent Mode**, which has the following options: * **Express:** In Express Consent Mode, the user must interact with the Consent Banner or the Privacy Center to set their preferences. No consent is initially assumed merely by landing on or using the site. * **Implied:** When using Implied Consent Mode, Concord will automatically generate implied consent events for all categories when the user lands on the site. They can later choose to opt-out of certain categories via your Consent Banner or Privacy Center (depending upon your configured settings and options there). ### Privacy Controls Experience This setting works in conjunction with the Express and Implied Consent Modes to determine the experience for users when they interact with your Consent Banner and Privacy Center. You can choose one of the following configuration options: * **Category Controls + Do Not Sell/Share:** * Provides both granular category-level controls and a Do Not Sell/Share toggle switch. Suitable for deployments that combine granular consent with sale/share opt-out rights. * All categories are enabled on arrival. Users can opt out of individual categories and use the Do Not Sell/Share toggle. Common in U.S. deployments that combine category controls with opt-out rights. * **Category Controls** * Users choose which specific categories to allow. The Do Not Sell/Share toggle is not shown. Appropriate for regions where sale/share opt-out rights do not apply. * All categories are enabled on arrival. Users can opt out of individual categories. The Do Not Sell/Share toggle is not shown. Appropriate for regions where sale/share opt-out rights do not apply. * **Do Not Sell/Share Only** * Simplified consent experience where category controls are hidden and users see a single Do Not Sell/Share toggle. Suitable for regions that emphasize opt-out rights. * All categories are enabled on arrival. Users can opt out of individual categories. The Do Not Sell/Share toggle is not shown. Appropriate for regions where sale/share opt-out rights do not apply. ### Enabling Global Privacy Control Global Privacy Control (GPC) is a browser configuration that automatically signals users’ privacy preferences to a website. Various regulations such as CCPA and CPRA require websites to respect users’ choices when this browser setting is detected. * Use the **Enable Global Privacy Control** switch under **Privacy → Consent → Consent Settings → General Settings** to toggle this automatic detection and control on or off. * Global Privacy Control detection is required by some regional data privacy laws like CCPA/CPRA in California. When this is enabled and a GPC signal is detected, Do Not Sell or Share My Personal Information consent will be set to true and Marketing consent will be disabled. * Note that you must select either the Category Controls + Do Not Sell/Share or Do Not Sell/Share Only option in the Privacy Controls Experience section if you want to enable Global Privacy Control. When you enable this feature within Concord, and the user has GPC turned on in their browser settings, Concord’s consent banner will display the following message: **Your Opt-Out Preferences Was Honored. Do Not Sell or Share My Personal Information** will also be automatically checked. ![](/docs/understanding-configuring-auto-blocking-of-cookies-scripts-banner.webp) ### Enable Limit Sensitive Information Consent Enables the Limit the Use of My Sensitive Personal Information consent option in your Privacy Center. This is required by some regional data privacy laws like CCPA/CPRA in California. ### Consent Duration The Consent Duration field defines how many months the consent is valid for. Once the duration has expired, the user will be prompted to re-consent. The normal recommended duration is 12 months, but some regions have different requirements and recommendations, including countries like Germany, where the guidance is 6 months. ## Show Deny Button The show Show Deny toggle allows you to set if the Deny button shows on your consent banner. Note that this option is only available if you choose the **Category Controls + Do Not Sell/Share** or **Category Controls** in the **Privacy Controls Experience** section. ### Advanced Options #### Hide Unused Categories When enabled, consent categories that have no trackers assigned to them will be hidden from the Privacy Center and Consent Banner. In Implied mode, hidden categories still receive implied consent. In Express mode, hidden categories are excluded from Accept All but included in Reject All. Categories automatically reappear when trackers are detected. #### Implied Consent Delay Sets a delay (in seconds) before implied consent is automatically granted when the user first visits your site. A value of 0 means consent is implied immediately. Increasing this value gives users more time to interact with the consent banner before implied consent is recorded. You can set the number of seconds to wait before generating implied consent events after a user arrives on your site. This only applies when using Implied consent mode. ## Consent Integrations In addition to our general consent settings, we also provide powerful consent syncing integrations with multiple major platforms in **Privacy → Consent → Consent Settings → Integrations**. For more details on these integrations, refer to the sections below. ### Configuring Google Consent Mode V2 You can pick from three different modes when enabling Google Consent Mode V2 in Concord: * **Disabled:** Concord functions normally, blocking any Google tags until consent is received based on your standard consent and tracker settings. After user consent is received, no consent data is synced with Google. * **Basic Mode:** Basic Consent Mode offers a simplified privacy friendly option to sync data with Google. Google tags remain inactive until the user interacts with the consent banner. Once users consent, Google tags are enabled, consent data is synced, and Google begins collecting data based on the user’s consent settings. Without consent, no data is sent to Google, and Google Ads relies on a general conversion model. * **Advanced Mode:** Advanced Consent Mode offers a more robust option that shares additional data with Google prior to consent. Google tags load immediately and while waiting for user consent, a minimal amount of cookieless measurement data is sent to Google to allow for more accurate conversion modeling. Once consent is granted, full measurement data is then sent to Google based on each user’s consent settings. This mode provides additional data insights, but is not as privacy-friendly as Basic Mode, so we recommend Basic Mode for most people. For more details on Google’s conversion modeling please refer to [this article.](https://support.google.com/google-ads/answer/12443859) ![](/docs/understanding-configuring-auto-blocking-of-cookies-scripts-google.png) ### Microsoft UET (Universal Event Tracking) Consent Microsoft UET (Universal Event Tracking) settings control how your website tag collects data based on user consent. UET helps companies comply with privacy laws (like GDPR) by adjusting data collection when users deny cookies, ensuring you still get valuable insights while respecting user choice.  UET is Required for 2025 compliance in EEA, UK, and Switzerland. ![](/docs/understanding-configuring-auto-blocking-of-cookies-scripts-uet.png) To configure Microsoft UET consent within Concord, select one of the following options: * **Disabled**: The UET tag is completely turned off and sends no data to Microsoft Advertising, fully respecting user privacy but providing zero insights. * **Enabled (UET Only)**: This is the default for many regions and uses "cookieless pings" or anonymized data when consent is denied. It loads the tag immediately but collects only basic, aggregated data, then upgrades to full tracking when consent is granted, offering more precise modeling and better compliance. * **Enabled with Microsoft Clarify**: This integrates UET with Clarity, Microsoft's free analytics tool, using one tag for both ad tracking and behavioral analysis (heatmaps, session recordings). It uses Consent Mode principles: Clarity loads but waits for consent before setting cookies or recording sessions, respecting `analytics_storage` and `ad_storage` signals. ### WordPress & Webflow Integrations Enabling the WordPress or Webflow integrations will allow you to easily sync consent data from Concord to those platforms to respect user consent. Note that the WordPress integration requires the use of the WordPress Consent API plugin that is found here: [https://wordpress.org/plugins/wp-consent-api/](https://wordpress.org/plugins/wp-consent-api/) ## Related Articles * [Understanding & Configuring Google Consent Mode (GCM) V2](/docs/google-understanding-configuring-google-consent-mode-gcm-v2) # Unified Identity and Consent Management Explained URL: /docs/understanding-unified-identity-and-consent-management *** title: "Unified Identity and Consent Management Explained" description: 'Concord''s Unified Identity and Consent Management system bridges anonymous browsing and known customer profiles to ensure a user''s privacy choices are consistently respected across all their devices. By utilizing a "most recent wins" logic and cryptographic hashing, the platform maintains a single source of truth, across devices, for consent without storing raw personal data, simplifying global regulatory compliance.' created: '2026-03-17T00:00:00.000Z' updated: '2026-03-17T00:00:00.000Z' ----------------------------------- A single person often interacts with a brand across multiple devices - a smartphone, a tablet, and a work laptop. Traditionally, privacy preferences were "siloed" on each device. If a user opted out of tracking on their phone, the brand might still track them on their laptop because the two sessions weren't connected. Concord's Unified Identity and Consent system solves this challenge. We bridge the gap between anonymous browsing and known customer profiles, ensuring that privacy choices are respected everywhere the user goes. ## The Core Identity Model Concord views a visitor not as a collection of cookies, but as a single identity. Our system operates on three integrated levels: 1. **The Context (Device):** The specific browser or hardware being used. 2. **The Identity (The Person):** A persistent profile that connects various contexts. 3. **The Consent State:** The actual choices made by that person (e.g., "Yes to Analytics," "No to Marketing"). To maintain a privacy-first approach, Concord never stores raw personal information, like email addresses, for syncing privacy choices. Instead, we use advanced cryptographic hashing to create a unique "digital fingerprint" for each user. This allows us to recognize a returning customer without ever holding their sensitive data. ## The Cross-Device Experience The primary benefit of Concord's architecture is the ability to maintain a "Single Source of Truth" for consent across the entire customer journey. * **Seamless Synchronization:** When a visitor logs into your site, Concord identifies them and instantly checks for any existing privacy preferences in our global vault. * **Consent Inheritance:** If a user has already opted into marketing communications on their desktop, those preferences are automatically applied when they log in on their mobile device. The user isn't pestered with the same consent banners repeatedly. * **Anonymous-to-Known Transition:** If a visitor makes a choice while browsing anonymously and later logs in, Concord "merges" that session into their permanent profile, ensuring their most recent decision is the one that sticks. ## Flexible Compliance Frameworks Every region has different legal requirements (such as GDPR in Europe or CCPA in California). Concord adapts its behavior based on the regulatory environment: * **Express vs. Implied Consent:** In stricter regions, we can ensure no tracking occurs until the user takes an explicit action (**Express**). In other areas, we can allow tracking to begin immediately while providing a clear path to opt-out (**Implied**). * **Adaptive Controls:** Our system can toggle between standard "Category" controls (Analytics, Functional, Marketing) and specific "Do Not Sell/Share" requirements to meet diverse global standards without needing multiple privacy tools or different approaches per region. ## Conflict Resolution: "Most Recent Wins" Privacy choices aren't static. A user might change their mind or update their settings at any time. To ensure accuracy, Concord follows a deterministic logic: **Explicit user actions always take priority over automatic defaults, and among actions of the same type, the most recent one wins.** For example, if a user clicks "Accept All" on one device and later clicks "Reject All" on another, the rejection takes effect everywhere because it is the more recent explicit action. Importantly, automatic defaults from a permissive region will never override a deliberate choice the user made elsewhere. This ensures that the brand always operates based on the user's actual stated intent. ## User Experience and Global Signals Concord is designed to be "quiet" and respectful of the user's time. * **Banner Suppression:** If we already know a user's global consent state, we can suppress the cookie banner entirely, creating a cleaner, more professional browsing experience. * **Respecting Browser Signals:** We actively listen for **Global Privacy Control (GPC)** signals. If a user has configured their browser to signal a preference for privacy, Concord automatically honors that request, even before the user interacts with the site. By unifying identity and consent, Concord enables brands to build trust through consistency while significantly simplifying the technical burden of global privacy compliance. ## Frequently Asked Questions 1. **Does Concord store personal information like email addresses?** No. When it comes to identity and syncing of privacy choices via user identifiers like emails, we prioritize privacy by using cryptographic hashing. This transforms those identifiers into a unique digital fingerprint, allowing us to recognize returning users without ever storing actual email addresses or names. 2. **What happens if a user updates their preferences on a different device?** The system follows a "most recent wins" logic. If a user changes their settings on their phone, that decision is instantly synced to their global profile. The next time they visit on their laptop, their preferences will reflect that update. 3. **Will users see a consent banner every time they switch devices?** Not necessarily. If a user is identified and preferences are already on file, Concord can suppress the banner, providing a smoother experience by not asking the same questions twice. 4. **How does Concord handle browser-level privacy signals?** The platform is fully compatible with Global Privacy Control (GPC). If a user has enabled GPC in their browser, Concord recognizes this as a valid opt-out preference for do not sell or share rights and adjusts their consent state automatically. 5. **What happens to consent when a user logs out?** When a user logs out, the identity link is reset. The browser returns to an anonymous state, ensuring that the next person using that device does not inherit the previous user's privacy settings. 6. **How does this help with regulations like GDPR or CCPA/CPRA?** It ensures GDPR style Opt-In/Explicit/Express consent choices or CCPA/CPRA style Opt-Out/Implicit/Implied & Do Not Sell/Share requests are honored globally, not just on a single browser. This maintains a higher standard of compliance and builds trust by respecting choices across the entire digital journey. # Dashboard Overview URL: /docs/dashboard-overview *** title: 'Dashboard Overview' description: 'The Dashboard section within Concord provides an at-a-glance view of important Consent and Compliance metrics.' created: '2021-05-13T20:43:21.000Z' updated: '2024-10-18T18:47:57.000Z' ----------------------------------- ## Overview The Concord Dashboard is one of the first items you see upon logging in to Concord. You will be presented with multiple widgets that are aligned with your current Concord plan. These can include: People, Privacy, Consent, Consent Distribution, Consent by Geography, All Open Requests, and Resolution Metrics. You may also select which Project you would like to view (should your organization have multiple Projects), as well as the month for which you would like to see data. The dashboard defaults to the current month. ![](/docs/dashboard-overview.webp) * **People** - The People widget shows a count of visitor sessions on your site for the selected month. See also: [Key Metrics Report](/docs/key-metrics-report) * **Compliance** - The Compliance widget shows an aggregate count of the total number of Compliance Requests for the selected month. Requests that are still pending end-user verification are not included in this total. You may click on the **View Report** button to view the full Compliance Requests report. See also: [Privacy Requests Request Log](/docs/privacy-requests-request-log) * **Consent** - The Consent widget shows an aggregate count of the total number of Consent Events for the selected month. You may click on the **View Report** button to view the full Consent Events report. See also: [Consent Events and Exports](/docs/consent-log-report) * **Consent Distribution** - The Consent Distribution widget shows a count of the total number of users that provided consent, no consent, or partial consent for the given date range. * **Consent by Geography** - The Consent by Geography widget shows the total count of users and their associated geographical region for the given date range. * **Open Requests (last 12 months)** - The Open Requests widgets shows the number of Privacy Requests (View, Change, Delete, and Do Not Sell) grouped by status (Pending Verification, Submitted, Acknowledged). * **Requests by Geography** - The Requests by Geography widget shows the total number of Privacy Requests grouped by geographical region for the given date ranged. # Key Metrics Report URL: /docs/key-metrics-report *** title: 'Key Metrics Report' description: 'The Key Metrics Report provides detailed day-by-day information for your key metrics, including Visitor Sessions, Visitors, Consent Events, and Privacy Requests.' slug: 'key-metrics-report' topic: 'dashboard-reports' created: '2021-05-13T20:43:47.000Z' updated: '2023-10-03T08:32:43.000Z' ----------------------------------- ## Overview The Key Metrics report will show you daily counts for Visitor Sessions, Visitors, Consent Events, and Privacy Requests. You can choose the starting and ending month for the report using the date range picker as seen below: ## Selecting a Date Click within the starting date range, select a starting month, and then click within the ending date range and select an ending date. ![](/docs/key-metrics-report-date-range.webp) ## Using the Key Metrics Report The report shows distinct days within the requested date range with discrete counts for each metric displayed. Consent Events and Privacy Requests are aggregated within this report and do not show the specific type of Event or Request. You can see additional detail in the Consent Events report or the Request Log report. ![](/docs/key-metrics-report-table-light.webp) # Connecting Data Systems to a Project URL: /docs/connecting-data-systems *** title: 'Connecting Data Systems to a Project' description: 'How to connect Data Systems to a specific Privacy Project.' created: '2022-02-21T20:51:29.000Z' updated: '2026-03-16T18:27:39.000Z' ----------------------------------- ## Overview This article provides instructions on connecting Data Systems to a specific Privacy Project. For more information on Data Systems, you can take a look at the following articles: * To learn more about how Data Systems work, refer to this article: [Data Systems Overview](/docs/data-mapping-overview) * For details on how to add a new Data System, refer to this article: [Adding Data Systems](/docs/data-hub-systems) ## Connecting Data Systems to a Project Before associating Data Systems with a specific Privacy Project, you must first add those systems to your organization. To learn more about adding a new Data System, refer to the Adding Data Systems article above. Once your organization has created at least one Data System, follow the steps below to connect your Data System(s) to a Privacy Project. * Click on **Global Settings** and choose **Projects**. * Click **Edit Project** in the actions menu for the Privacy Project you would like to connect your Data Systems to. ![](/docs/connecting-data-systems-projects-edit-projects.webp) * From the Data Systems selector, select the Data Systems associated with this Project. You can only select Data Systems that have already been added to your Organization. To remove Data Systems, click **X** next to the system or uncheck the Data System from the drop-down selector. Click **OK**. ![](/docs/connecting-data-systems-edit-projects-add-data-systems.png) * Click **Ok** to save your changes. # Data Mapping Overview URL: /docs/data-mapping-overview *** title: 'Data Mapping Overview' description: 'Understanding Data Mapping and viewing Data System details.' created: '2022-02-21T20:35:09.000Z' updated: '2026-09-15T00:00:00.000Z' ----------------------------------- ## Overview Data Mapping allow you to easily add different data systems and attributes to your organization to help with data mapping, compliance documentation, and the handling of data privacy requests. Data Systems are not only a critical component when it comes to managing data privacy requests, but they are also essential to demonstrating regulatory compliance by providing a full picture of your organization's capture, processing, and usage of data. Concord provides 100+ out-of-the-box integrations to connect to, as well as the ability to add your own custom-built systems, and Data Systems can be used to: * Identify the systems in your organization where personal data resides. * Catalog and inventory all personal data across your organization. * Associate data across sources with user identities for privacy request fulfillment. For more information on how to setup and use Data Systems, refer to the information and articles below: * For instructions on adding new Data Systems, refer to this article: [Data Hub: Systems](/docs/data-hub-systems). * To learn about managing Data System attributes, refer to this article: [Data Hub: System Attributes](/docs/data-hub-system-attributes). * For information about connecting Data Systems and Projects, refer to this article: [Connecting Data Systems to a Project](/docs/connecting-data-systems). * To generate a GDPR Article 30 register from your data map, see [Generating ROPA Reports](/docs/generating-ropa-reports). * To track the third parties that process data for you and publish sub-processors, see [Managing Vendors and Sub-Processors](/docs/managing-vendors). ## Viewing Data System Details * Go to **Data Hub -> Data Systems** via the navigation menu and choose **Systems**. ![](/docs/data-mapping-overview-data-mapping-data-systems-table-light.webp) From this screen, you will be able to view Data System details such as: * **Name:** The friendly name used to identify your data source in the Admin UI. * **Type:** The type of system where data is stored. * **Relationship:** Relationship is for identifying the relationship of this data system in regards to your company. While you can add your own custom options as well, in most cases this will be set to one of the following predefined options: * **Controller:** Legal or natural person, an agency, a public authority, or any other body who, alone or when joined with others, determines the purposes of any personal data and the means of processing it. * **Joint Controller:** Third party data processor engaged by a Data Processor who has or will have access to or process personal data from a Data Controller. * **Processor:** Legal or a natural person, agency, public authority, or any other body who processes personal data on behalf of a data controller. * **Sub-Processor:** Two or more data controllers that jointly decide why and how to process personal data. * **Status:** Active, Test, Archived. * **Actions:** Menu options where you can View / Edit, Quick Edit, Archive, or Delete a data system. To view additional details, click on the + to the left of your desired Data System or click the name of the Data System to go to the full system view for that Data System. ![](/docs/data-mapping-overview-data-mapping-systems-details.webp) This expanded view will display further Data System details such as: * **Organization ID:** The identifier for the organization this system belongs to. * **Data System ID:** The identifier for this particular system. * **Origins:** Where does the data from the data system originates from. * **Destinations:** Where the data is sent to and who the data is shared with. * **Processing Purposes:** What the data in this system is used for. * **Processing Activities:** The activities associated with the data in this system. * **Personal Data Categories:** The types of personal data that are stored in the data system. * **Security Measures:** The security measures that are in place to protect the data in this system. * **Contacts:** The contacts at your company or other companies associated with this Data System. * **Cross Border:** If data in this system is sent outside of your country. * **Retention:** How long data is held in this system by default. * **Additional Notes:** Any additional details associated with this Data System. * **Date Created:** When this Data System was created. * **Date Updated:** When this Data System was last updated. # Generating ROPA Reports URL: /docs/generating-ropa-reports *** title: 'Generating ROPA Reports' description: 'Produce a GDPR Article 30 Record of Processing Activities from your Data Mapping, edit it as a draft, finalize a point-in-time record, and export it.' created: '2026-09-15T00:00:00.000Z' updated: '2026-09-15T00:00:00.000Z' ----------------------------------- ## Overview A Record of Processing Activities (ROPA) is the register GDPR Article 30 asks you to keep: what personal data you process, why, and how. Concord builds this register from the data you already maintain in [Data Mapping](/docs/data-mapping-overview), so you can generate a compliant draft in one step and refine it, rather than filling in a spreadsheet by hand. ROPA reports are a **Premium** add-on. Generating a report uses Actions from your organization's shared pool. ## What a report contains A ROPA report has two parts: * **A summary** — rich text describing the register, with insertable tokens (for example, a live processing-activity count) that resolve to real values when you finalize. * **Rows** — one Article 30 record per processing activity, each capturing the purposes, data subjects, data categories, recipients and transfers, origins, legal basis, and security measures. ## The lifecycle: draft, finalize, export 1. **Generate a draft.** From **Data Mapping → ROPA reports**, generate a report. Concord selects your processing activities, turns each into an Article 30 row, and seeds the summary from a template. 2. **Edit the draft.** While a report is a draft, you can edit the summary and the rows freely. You can also **exclude** a row you don't want in this report — it's hidden from the counts and the export but kept for your audit trail. 3. **Finalize.** Finalizing freezes a point-in-time record: the summary's tokens are resolved to their values and the rows become read-only. A finalized report can't be returned to draft, which is what makes it a defensible snapshot. 4. **Export.** Export the finalized report for your records or to share with a regulator or auditor. {/* Screenshot pending: ROPA report -> /docs/generating-ropa-reports-detail.png. See docs-screenshot-backfill plan. */} ## Cross-border transfers Each row reflects where the data systems behind an activity are located, so the register surfaces cross-border transfers as part of the Article 30 record. Keep your data systems' geography accurate in Data Mapping and it flows through to the report. ## Editing a report The report detail page organizes the work into tabs — the report's **details**, its **summary** (the rich-text editor), and its **activities** (the rows). Edits to a report stay local to that report; they don't change your underlying Data Mapping. ## Who can generate reports Owners and Admins can generate, edit, and finalize reports. A Limited user can view them. See [User Roles and Permissions](/docs/user-roles-permissions). ## Next steps * [Data Mapping overview](/docs/data-mapping-overview) — the systems and processing activities a ROPA is built from. # Managing Vendors and Sub-Processors URL: /docs/managing-vendors *** title: 'Managing Vendors and Sub-Processors' description: 'Keep an inventory of the vendors that process data for you, review their risk on a schedule, track their documents, and publish your sub-processor list to your Trust Center.' created: '2026-09-15T00:00:00.000Z' updated: '2026-10-30T00:00:00.000Z' ----------------------------------- ## Overview Your vendors are the third parties that store or process data on your behalf, and buyers increasingly ask you to name them. Concord keeps a **vendor inventory** in the Data Hub, alongside your [Data Mapping](/docs/data-mapping-overview), so the vendors you track are connected to the systems they actually support, and the sub-processor list you publish stays consistent with your data map. ## Adding Vendors 1. Go to **Data Hub → Vendors** and add a vendor. 2. **Choose Vendor:** pick a vendor from Concord's catalog to fill in its details for you, or choose **Custom** to start from scratch. 3. **Details:** review and edit the vendor's name, categories, website, privacy policy URL, DPA URL, country, and description. 4. **Data Systems:** link the data systems this vendor provides. Catalog details are copied into your vendor record when you add it, and you can edit them at any time. ## Linking Vendors to Data Systems Link a vendor to the data systems it supports, from either side: * From a vendor, open its **Data Systems** tab and choose **Add Data System**. * From a data system, choose **Link Vendor**. Concord suggests a vendor from its catalog when it recognizes the system. This keeps your data map clear about who is involved in each system and which third parties have access to the data it holds. ## Publishing Sub-Processors to Your Trust Center You can publish your sub-processor list on your public Trust Center, so prospects and customers can see who processes their data without emailing your team. 1. Open your Trust Center's settings and turn on the **Sub-processors** section. 2. Choose the vendors, or data systems, to list. Each sub-processor shows its name, description, and the countries where it processes data. Publishing from your maintained vendor list keeps the public list current instead of drifting from a separate document. A vendor's page shows which of your Trust Centers list it. See [Trust Center Overview](/docs/trust-center-overview) for how the public page is organized. ## Plans The vendor inventory, catalog, data system links, vendor documents, and sub-processor list are on every plan of Concord Privacy and Concord Trust, including Free. **Vendor risk** (risk tiers, data sensitivity, review cadence, and vendor reviews) is part of the **Premium** and **Enterprise** plans of either product. ## Risk Tier, Sensitivity, and Owners Each vendor has: * **Data sensitivity:** worked out from the data its linked data systems hold. * **Inherent risk tier** (low, medium, high, or critical): suggested from its data sensitivity and categories. You can set the tier yourself, and a tier you set by hand isn't overwritten when the vendor's data systems change. * **Business owner** and **security owner:** who answers for the vendor, and who reviews it. ## Vendor Documents Keep each vendor's assurance documents on its **Documents** tab: SOC 2 reports, ISO 27001 certificates, penetration test summaries, DPAs, insurance certificates, questionnaires, and anything else. Each document can be a link, an uploaded file, or a document from your library, with the dates it's valid for. * Concord reminds you before a document expires, with a task due on the expiry date. * The vendor's **Details** tab shows whether its DPA is **On file**, **Expiring**, **Expired**, or **Missing**, with an **Add DPA** button. * When you add a vendor from the catalog, its published DPA terms are added as a link for you. ## Reviewing Vendors A vendor review records that someone looked at the vendor's risk and decided whether to keep using it. * **Scheduled reviews:** every vendor has a next review date. Critical vendors are reviewed every six months and the rest every year by default, or on the cadence you choose. When a review is due, Concord opens it and gives the security owner (or the business owner, if there's no security owner) a task. * **Reviews on demand:** start a review at any time from the vendor's **Reviews** tab, for example after the vendor has a security incident. A vendor has at most one open review. To finish it, choose **Complete Review** and record your findings: * **Approve:** choose the **residual risk tier**, the vendor's risk once your review and its controls are taken into account. * **Reject:** give the reason. The vendor is marked rejected. Approving a review adds it as evidence to your supplier management control. If the review found something worth tracking, raise its findings as a risk in the [Risk Register](/docs/data-hub-risks), linked to the vendor. The vendor list's **Reviewed**, **In Progress**, and **Never Reviewed** tabs show where every vendor stands. ## Importing Vendors To add many vendors at once, import a CSV. Rows that match an existing vendor update it, and a row with a problem, such as an invalid URL or country code, is reported on its own without stopping the rest of the file. A **DPA URL** column adds each vendor's DPA as a link document. ## Who Can Manage Vendors Owners and Admins can add and edit vendors. A Limited user can view them. See [User Roles and Permissions](/docs/user-roles-permissions). # Adding Concord to Your Website URL: /docs/adding-concord-to-your-website *** title: 'Adding Concord to Your Website' description: 'Quickly deploy Concord to your website with a single line of code using your direct embed code.' createdAt: '2021-05-13T20:50:23.281Z' updatedAt: '2025-06-25T21:19:32.250Z' ------------------------------------- ## Overview You can add Concord to your website to enable the use of the Concord Site Client Library and the Concord Privacy Center website widget. Our Site Client Library allows you to easily capture consent events on your website, while Privacy Center allows you to give your users access to our simple-to-understand data privacy information and controls. * Adding Concord to your website is as simple as copying the single line of code that you can find in the Concord Admin UI by navigating to **Deployment → Installation.** ![](/docs/adding-concord-to-your-website-Install.webp) * From the **Install Concord** tab, click the "Copy" icon to the right of the Manual Installation code box. Have your website developers add that right after the `<head>` tag on your website. It should be above all other scripts to ensure full compliance (when blocking mode is set to strict and consent mode is set to express). * If you are using Google Tag Manager, and you wish to comply with Googles latest guidelines, you may leverage GTM's Consent Mode in either Basic or Advanced mode. We recommend first following our Manual Installation Code instructions above to add the Concord code to your website. Then copy your Project ID and use that when setting up Google Tag Manager using the template in the linked article below. We do not recommending skipping the Manual Installation option above and using the Inject Script option in the Google Template unless you have already setup all of your other tags in Google Tag Manager. For more detail on Google Consent Mode and additional configuration instructions, see [here](/docs/google-understanding-configuring-google-consent-mode-gcm-v2). # Capturing Consent Events on Your Website URL: /docs/capturing-consent-events *** title: 'Capturing Consent Events on Your Website' description: 'How to capture consent events for users on your website using custom JavaScript code.' created: '2021-10-05T00:35:28.000Z' updated: '2024-10-18T16:56:01.000Z' ----------------------------------- ## Overview This article provides instructions on capturing consent events for users on your website using custom JavaScript code. This code can be added directly to your website or via our Custom Script option. To learn more about capturing consent via Custom Scripts, refer to this article: * [Managing Custom Scripts](/docs/managing-custom-scripts) ## Capturing Consent Events Based on User Actions We provide a number of convenience methods in our site client library that make it easy for your web developers to capture any type of consent on your website or in your applications. The basic code examples below can be used or expanded upon to add your own custom code to capture new Consent Events when your users perform certain actions that change their state of consent. Consent state represents the state of consent for the user after an event occurs and the options include: * **Accepted / Declined (accepted / declined):** The default consent states are “accepted” and “declined” as most cases will require the end user to accept or decline consent. * **Viewed (viewed):** This is less common, but the “viewed” state is used to track views instead of or in addition to click activities like accepts or declines. An example would be a user that clicked on a link to view your privacy policy page. * **Implied (implied):** The “implied” state is used if the end user does not need to take positive action to consent, but consents by using your website or application, like with a privacy policy. Note that all Consent Types that include implied as an option are sent automatically when we first see a new visitor to your website or application. Consent actions are how the user gets into one of the states above and include: * **User Click (user\_click):** Agreements accepted after a user clicks on something as part of acceptance flow (buttons, links, form submits, etc.). This is the most common way that consent is captured. * **Implied (implied):** As noted above, this is captured automatically the first time we see a new visitor without a given consent type. * **Import (import):** Represents consent captured and imported via another system. A common example is consent captured via an email marketing system and imported into Concord via API or our integration options. As noted above, Concord automatically captures Implied Consent Events for your website Privacy Policy on each of your projects. The first implied Consent Type is automatically generated when configuring your first project and is the only one you need in most cases. Disclosure URLs that drive these events — privacy policy, terms of service, cookie policy, and any custom disclosures — are configured as Policy Links: * [Managing Policy Links](/docs/managing-policy-links) ### Basic On-Click Consent Event Example Custom script example for when a user clicks a button on your website: ```javascript // Replace (elementId), (category), (subcategory), (label), (consentState) document.getElementById('(elementId)').addEventListener('click', function () { window.concord && window.concord.captureConsentEvent({ category: '(category)', subcategory: '(subcategory)', label: '(label)', consentState: '(consentState)', }); }); ``` IMPORTANT: Replace `(elementId)` with the id of the button and `(category)`, `(subcategory)`, `(label)`, `(consentState)` with the values that match your defined Consent Type. For example, the Consent Type in the image below would contain the following: * **category:** `disclosure` * **subcategory:** `terms_of_service` * **label:** `example_terms_of_service` * **consentState:** `accepted` or `declined` Also replace the `(elementId)` with the name of your HTML element that represents the clicked button. ![](/docs/capturing-consent-events-capturing-consent-events-image-vsx0f.png) ### Submit with Checkbox Example The following Custom Script example outlines capturing consent when a user submits a basic form on your website. In this example, we’re gathering on-click consent for collecting first name, last name, and email from a form that might look like this: ```html
``` # Configuring Automatic Language Translation URL: /docs/configuring-automatic-language-translation-in-the-consent-banner-concord-privacy-center *** title: 'Configuring Automatic Language Translation' description: 'Show your Consent Banner and Privacy Center in each visitor''s language, adjust any translation yourself, and let visitors switch languages.' created: '2024-07-31T05:01:57.000Z' updated: '2026-10-30T00:00:00.000Z' ----------------------------------- ## Overview With automatic language translation on, your Consent Banner and Privacy Center appear in each visitor's language, in any of the 58 languages Concord supports (see [Supported Languages](#supported-languages)). Right-to-left languages, such as Arabic, Hebrew, and Urdu, display right to left automatically. Your own wording is translated too, so customized text never falls back to Concord's stock wording. * **Your default language** is your region's own text, shown exactly as you typed it. It's never machine-translated. * **Every other language** is translated from that text, and you can reword any translation yourself. Languages are included in every paid Concord Privacy plan. ## Choosing Your Default Language Each region has a **Default Language**: the language you write your text in on the **User Experiences** pages. Set it on **Deployment → Languages**. Visitors who get the default language see your text exactly as written, and visitors whose browser language isn't supported get it too. If you change the default language, Concord translates your existing text into the language it replaced. ## Turning On Translation 1. Open your project and region, and go to **Deployment → Languages**. 2. Turn on **Translate Automatically** and save. Concord translates your text into every supported language. From then on, when you change text on any region page, the change is translated in the background, usually within a minute. ## How a Visitor's Language Is Chosen Concord goes through the languages set in the visitor's browser in order of preference and uses the first one it supports. If none match, the visitor sees your region's default language. The banner text, the IAB TCF purposes, and the consent record all use the same language, so they always agree. Dates in the widget, such as consent history and privacy request dates, and each tracker's type and expiration in the Privacy Center are shown in that language too. ### Letting Visitors Switch To add a language menu to the Privacy Center header: 1. On **Deployment → Languages**, turn on **Language Switcher**. Translate Automatically must be on. 2. Under **Switcher Languages**, pick the languages to offer. Your default language is always included, so pick at least one more. A visitor's choice is remembered for the rest of their visit in that browser tab. ### Choosing the Language Yourself If your site already knows the visitor's language, you can choose it for them: * Add `?lang=` and a language code to the Concord script's URL, or * Call `window.concord.setLanguage()` with a language code, for example from your own language menu. ## Editing Translations The **Translations** panel on **Deployment → Languages** shows each language's text, grouped by where visitors see it. For each key you see the default text and the text visitors get: * **Translated** text came from Concord's translation of your wording. * **Customized** text is wording you set yourself in that language. To change a translation, edit the key in that language. To go back to the translation, reset it. If Concord's stock wording under one of your customized keys changes later, the key is marked **Default Text Changed**, and you can choose **Keep Mine** or take the new wording. Policy link names can be reworded per language in the **Policy Links** section of the same panel. Policy links belong to the project, so wording you set there shows in every region. ## What Translation Costs Each translation that sends text to be translated costs **1 Action**. Saving text that doesn't need translating doesn't cost anything. See [Actions and Data Credits](/docs/actions-data-credits). * If your organization runs out of Actions, your text still saves, and translation resumes within an hour of a top-up. * Turning on Translate Automatically needs Actions available. * Each organization can translate up to 5 million characters a day. Past that, the rest is translated the next day. The Languages page shows where translation stands: | Status | Meaning | | ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------- | | **Translating Your Changes** | Your other languages update in about a minute. You can keep working. | | **Translation Paused** | Out of Actions: your text is saved and translated within an hour of a top-up. Daily limit reached: it's translated tomorrow. | | **Text Too Long to Translate** | The text is more than Concord can translate in a day. Shorten it and save again. | | **Translation Didn't Finish** | Your text is saved, but translating it didn't finish. Save it again to retry. | ## Supported Languages * Albanian (Albania) * Arabic (United Arab Emirates) * Basque (Spain) * Bengali (Bangladesh) * Bosnian (Bosnia and Herzegovina) * Bulgarian (Bulgaria) * Catalan (Spain) * Chinese Simplified (China) * Chinese Traditional (China) * Croatian (Croatia) * Czech (Czech Republic) * Danish (Denmark) * Dutch (Netherlands) * English (United States) * Estonian (Estonia) * Finnish (Finland) * French (Canada) * French (France) * Galician (Spain) * German (Germany) * Greek (Greece) * Gujarati (India) * Hebrew (Israel) * Hindi (India) * Hungarian (Hungary) * Icelandic (Iceland) * Indonesian (Indonesia) * Irish (Ireland) * Italian (Italy) * Japanese (Japan) * Kannada (India) * Korean (Korea) * Latvian (Latvia) * Lithuanian (Lithuania) * Macedonian (North Macedonia) * Malayalam (India) * Maltese (Malta) * Marathi (India) * Norwegian Bokmål (Norway) * Polish (Poland) * Portuguese (Brazil) * Portuguese (Portugal) * Punjabi (India) * Romanian (Romania) * Russian (Russia) * Serbian (Latin) * Slovak (Slovakia) * Slovenian (Slovenia) * Spanish (Latin America) * Spanish (Spain) * Swedish (Sweden) * Tamil (India) * Telugu (India) * Thai (Thailand) * Turkish (Turkey) * Ukrainian (Ukraine) * Urdu (India) * Vietnamese (Vietnam) # Configuring the Privacy Center Floating Button URL: /docs/floating-button-configuration *** title: "Configuring the Privacy Center Floating Button" description: 'A step-by-step guide to configuring the Floating Button for easy access to your Privacy Center on your website.' created: '2024-01-31T23:49:04.000Z' updated: '2024-10-02T20:06:22.000Z' ----------------------------------- ## How to Configure the Floating Button to Access the Privacy Center Login to Concord and navigate to **User Experiences** → **Floating Button** * **Show Button**: Whether or not the Floating Button is shown on your website. * **Button Icon**: The icon used for the Floating Button on your website. You can choose between a fingerprint or a cookie. * **Tab Text**: The tab text used for the Floating Button on your website. ![](/docs/floating-button-configuration-floating-button-configuration-image-7s4ho.webp) Click the **Save** button in the upper left portion of the workspace to save your changes. ## **Related Help Documents** * [Privacy Center Direct Access Links](/docs/privacy-center-direct-access-links) # Managing Custom Scripts URL: /docs/managing-custom-scripts *** title: 'Managing Custom Scripts' description: 'Understanding and managing custom scripts.' created: '2021-05-13T20:47:31.000Z' updated: '2023-10-13T08:43:26.000Z' ----------------------------------- ## Overview * Custom JavaScript can be added to the Site Config for a Project so that it is automatically executed when our Site Client Library is loaded on your website. * Some potential examples of when customized JavaScript may be needed could include. * Capturing consent events when users perform specific actions on your website (like clicking a button).[](/docs/capturing-consent-events) * Opening the Concord Privacy Center Website Widget when a user clicks on a link on your website (like a footer link or a link in your privacy policy). * To add custom JavaScript, go to **Deployment -> Deploy Settings -> Custom Script,** click **Edit**, and paste in your required JavaScript. * There is an included JavaScript validator embedded in the solution to help you identify potential issues with your script. ![Custom Scripts](/docs/managing-custom-scripts.webp) # Managing Project Domains URL: /docs/managing-project-domains *** title: 'Managing Project Domains' description: 'How to manage the domains associated with your project.' created: '2021-05-13T20:53:47.000Z' updated: '2023-10-03T08:38:08.000Z' ----------------------------------- ## Overview * When logging into Concord’s Admin User Interface (UI) for the first time, you will be guided through a Project Setup Wizard where you will be asked to enter your website’s domain. This will be the primary domain associated with your first Project. * Domains are used in Concord to restrict the domains that can use that Project’s Privacy Center website widget and to determine which domains can send consent events to that Project. * Most companies will generally use a single domain per project, although it’s possible you will have several different websites that require similar configurations. * From the **Domains** section in the Admin UI, you will be able to: * Add additional domains. * Edit existing domains. * Delete domains. ## How to Add a New Project Domain 1. Click on the **Domains** drop-down menu and choose **Domains**. ![](/docs/managing-project-domains.webp) 2. Click **Add Domain.** ![](/docs/managing-project-domains-add-domain.png) 3. Enter your domain name and URL. * The UI will confirm if you have entered a properly formatted domain. Do not prepend “http\://” or “https\://” to your domain. ![](/docs/managing-project-domains-add-domain-modal.png) 4. Click **Ok**. We will display a message letting you know the domain has successfully been added and your new domain is now connected to your Project. ## How to Edit and Delete Domains 1. Click on the **Domains** drop-down menu and choose **Domains**. ![](/docs/managing-project-domains.webp) 2. Click on the domain you want to edit or delete. 3. Make your changes or click **Delete** to remove the domain. # Privacy Center Direct Access Links URL: /docs/privacy-center-direct-access-links *** title: 'Privacy Center Direct Access Links' description: 'Configuring Direct Access Links to Your Privacy Center.' created: '2023-08-15T21:19:33.000Z' updated: '2026-02-22T12:00:00.000Z' ----------------------------------- ## Overview Privacy Center allows you to use direct access links when you want to directly load a specific area of Privacy Center. As an example, your organization may want to add a direct access link in your privacy policy or via email that allows people to go directly to the Privacy Options section to submit a privacy request to view, delete, or change their data. This document will help you add the URL query parameters that will load Privacy Center and show a specific area of Privacy Center including: * Details * Privacy Options * Do Not Sell * Consent Currently you can include the following direct access links on your website, in email communications, etc.: Details * `?cord_section=details` * Example: [https://concord.tech/?cord\_section=details](https://concord.tech/?cord_section=details) Privacy Options (Requires **Privacy Requests Enabled** to be enabled in the Admin UI in **Privacy Requests → Request Settings**) * `?cord_section=privacy_options` * Example: [https://concord.tech/?cord\_section=privacy\_options](https://concord.tech/?cord_section=privacy_options) Do Not Sell (Requires **Privacy Requests Enabled** & **Enable Do Not Sell** to be enabled in the Admin UI in **Privacy Requests → Request Settings**) * `?cord_section=privacy_options_dns` * Example: [https://concord.tech/?cord\_section=privacy\_options\_dns](https://concord.tech/?cord_section=privacy_options_dns) Consent (Requires **Consent Mode** to be set to anything other than disabled in the Admin UI in **Consent → Consent Settings**) * `?cord_section=consent` * Example: [https://concord.tech/?cord\_section=consent](https://concord.tech/?cord_section=consent) *** ## Programmatic Widget Control If loading speed is of the utmost importance, or you need to open a specific section from a button or link, you can use the widget's JavaScript API to control the Privacy Center programmatically. This approach is slightly faster than using direct access links because it doesn't require a page navigation. ### When to Use Each Approach 1. **Direct Access Links** - The recommended approach for most use cases. Link to your privacy policy page with the query parameter, providing a graceful fallback if the widget fails to load. 2. **Programmatic API** - Use `window.concord.plugin.widget` methods for optimal load performance. Ideal for footer links, navigation elements, or any interactive component where you want instant access to the Privacy Center. ### API Methods All methods are available on `window.concord.plugin.widget`. #### `toggle(options?)` Toggles the Privacy Center open or closed. If the widget is currently closed, it opens (optionally to a specific section). If it is already open, it closes, regardless of which section is specified. ```js // Open or close the Privacy Center window.concord.plugin.widget.toggle(); // Open to a specific section, or close if already open window.concord.plugin.widget.toggle({ section: 'consent' }); window.concord.plugin.widget.toggle({ section: 'details' }); window.concord.plugin.widget.toggle({ section: 'privacy_options' }); window.concord.plugin.widget.toggle({ section: 'privacy_options_dns' }); ``` #### `openSection(section)` Always opens the Privacy Center to a specific section. Unlike `toggle()`, this never closes the widget. ```js window.concord.plugin.widget.openSection('consent'); window.concord.plugin.widget.openSection('details'); window.concord.plugin.widget.openSection('privacy_options'); window.concord.plugin.widget.openSection('privacy_options_dns'); ``` #### `setOpen(open, options?)` Explicitly sets the open state of the Privacy Center. ```js // Open the Privacy Center window.concord.plugin.widget.setOpen(true); // Open to a specific section window.concord.plugin.widget.setOpen(true, { section: 'consent' }); window.concord.plugin.widget.setOpen(true, { section: 'privacy_options_dns' }); // Close the Privacy Center window.concord.plugin.widget.setOpen(false); ``` ### Implementation Example Here's how we implement this on our own site in the footer and nav bar: ```tsx { if (window.concord?.plugin?.widget?.toggle) { e.preventDefault(); window.concord.plugin.widget.toggle(); } }} > Privacy Settings ``` To open directly to a specific section, for example, a "Do Not Sell" footer link: ```tsx { if (window.concord?.plugin?.widget?.toggle) { e.preventDefault(); window.concord.plugin.widget.toggle({ section: 'privacy_options_dns' }); } }} > Do Not Sell My Data ``` These examples check if the Concord widget is loaded and available before calling the API. If the widget isn't available, the link falls back to the direct access URL, ensuring users can always access the Privacy Center. ### Section Reference The valid section values are the same for both URL parameters and the programmatic API: | Section | Description | Requirement | | --------------------- | -------------------------------------------- | ------------------------------------------------ | | `details` | Opens the Privacy Center to the Details view | None | | `consent` | Opens to the Consent view | Consent Mode must be enabled | | `privacy_options` | Opens to the Privacy Options selector | Privacy Requests must be enabled | | `privacy_options_dns` | Opens directly to the Do Not Sell form | Privacy Requests and Do Not Sell must be enabled | #### Deprecated Section Values The following section values still work but will log a deprecation warning to the browser console. Update any existing links or code to use the new values above. | Deprecated | Replacement | | ------------------ | ----------- | | `privacy_center` | `details` | | `consent_settings` | `consent` | # Privacy Center Widget Configuration URL: /docs/privacy-center-widget-configuration *** title: 'Privacy Center Widget Configuration ' description: 'A step-by-step guide to configuring the Privacy Center widget for use on your website.' created: '2021-05-13T20:46:20.000Z' updated: '2026-03-16T22:27:16.000Z' ----------------------------------- ## Overview To configure or update the Privacy Center widget, click on **Privacy →** **User Experiences → Privacy Center** to configure the widget. Note: If you have multiple regions setup, select the region you want to configure from the Region drop-down selector in the top left of the page above the Privacy Center title. ![](/docs/privacy-center-widget-configuration.webp) ## Privacy Center: General Settings In the **Privacy Center → General Setting** tab, you can setup and configure the Privacy Center that is shown to your users. In this section you can configure the following: * **Privacy Center Themes:** The theme of the Privacy Center on your website. Can be set to classic, light, dark, or brand. All themes use your primary color for most of your custom branding (buttons, links, etc.). For the background, brand will use your secondary color, dark uses a very dark gray. light uses white, and classic uses a white background with a header in your secondary color. * **WCAG AA:** WCAG AA is the internationally recognized standard for web accessibility, ensuring digital content is usable by people with disabilities. Contrast is adjusted to a minimum 4.5:1 ratio for text to background, ensuring readability for visually impaired users. * **Show Consent History:** When enabled, each consent category displays its current state (e.g. Accepted, Declined, Implied) along with the date the choice was last made. * **Consent History Mode:** Options include legacy, standard, or both. Legacy shows the full Consent History panel. Standard shows status labels on each consent category. Both enables both experiences. * **Legacy Mode Deprecated:** Use Standard mode for the new simplified consent history treatment. Legacy mode will be removed soon. * **Show All Vendors Section:** Displays a combined list of all vendors across all consent categories. This is in addition to per-category vendor details shown when categories are enabled, and is recommended in all modes. * **Show Disclosures Section:** Whether or not the Privacy Disclosures panel is shown to your users in your Privacy Center. When enabled, the panel surfaces the [Policy Links](/docs/managing-policy-links) configured under **Policies → Links** — privacy policy, terms of service, cookie policy, data protection agreement, and any custom policies. ## Privacy Center: Language In the **Privacy → Privacy Center → Language** tab, you can setup and customize the verbiage displayed in your Consent Banner. Concord provides suggested text however, we also offer extensive customization options so you can change text to align with your business needs and language style. You can customized the following text in your company’s Consent Banner: * **Consent Settings** * **Consent Settings Title:** The text used for the Consent Settings title. * **Consent Setting Text:** The text used for the Consent Settings description. * **Confirm Button:** The text used for the Consent Settings button. * **Consent Categories** * **Strictly Necessary Title:** The text user for the Strictly Necessary title. * **Strictly Necessary Text:** The description user for the Strictly Necessary section. * **Analytics Title:** The text user for the Analytics title. * **Analytics Text:** The description user for the Analytics section. * **Functional Title:** The text user for the Functional title. * **Functional Text:** The description user for the Functional section. * **Marketing Title:** The text user for the Marketing title. * **Marketing Text:** The description user for the Marketing section. * **Unclassified Title:** The text user for the Unclassified title. * **Unclassified Text:** The description user for the Unclassified section. * **Privacy Disclosures** * **Privacy Disclosures Title:** The text used for the title of the Privacy Disclosures panel in your Privacy Center. * **Privacy Disclosures Description:** The text used for the description of the Privacy Disclosures panel in your Privacy Center. * **Vendors** * **Vendors Title:** The heading displayed above the All Vendors section in your Privacy Center. * **Vendors Description:** The description shown in the All Vendors section of your Privacy Center. * **Vendors Link Title:** The text of the link button in the All Vendors section of your Privacy Center. * **Privacy Requests** * **Privacy Requests Title:** The text used as a title for the Privacy Requests panel. * **Privacy Options Title:** The text used as a title for the Privacy Options section. * **Privacy Options Description:** The text used as a title for the Privacy Options description. * **Options Button Text:** The text of the button to show Privacy Request options. * **Change Request Title:** The text of the button for requesting changes to a user’s data. * **Change Request Description:** The text describing data change requests. * **Delete Request Title:** The text of the button for requesting deletion of a user’s data. * **Delete Request Description:** The text describing data deletion requests. * **View Request Title:** The text of the button for requesting a copy of a user’s data. * **View Request Description:** The text describing user data copy requests. * **Do Not Sell Request Title:** The text used for the title of the Do Not Sell or Share Request form in the Privacy Center widget. * **Do Not Sell Request Description:** The text used for the description of the Do Not Sell or Share Request form. ## Privacy Center: Branding - Setting Your Company Logo, Colors & Branding You can also configure the branding of the Privacy Center Widget by navigating to **Privacy → User Experiences → Branding**. Your secondary color is used for the header color of the Privacy Center and the primary color is used throughout the Privacy Center for items like buttons, links, and hover colors. You can customize the following to align with your brand: * **Logo** * Logo file size is limited 512KB. * Logos are restricted to .png formats. * There are no height or width restrictions, but logos are resized in the widget to a max-height of 40px so 40px is the preferred height. * **Primary and Secondary Color** * Primary color is used for the buttons and links in your Consent Banner. * Secondary color is used for the background of the header in your Privacy Center. * You can either choose a preexisting color by clicking on any of the default colors shown or you can input a Hexadecimal color value (for example: “#22194D”). HSB and RGB color codes are also accepted. * If you do not know the proper Hexadecimal color value for your desired branding, you may search online for “hexadecimal color picker” to find free tools for choosing a color and finding its hexadecimal value. * **Font:** Choose a font that represents your brand identity. The selected font will be applied to all text elements in your privacy experiences. * **Button Radius:** Choose how your buttons display in the Privacy Center (square, standard, round, pill). * **Card Radius:** Choose the radius of the cards in your user experiences. * **Powered by Concord:** Branding (this is only customizable on Pro and Premium plans) ![](/docs/privacy-center-widget-configuration-branding.webp) ## Privacy Center: Floating Button You can also configure the branding of the Privacy Center Widget by navigating to **Privacy → User Experiences → Floating Button**. In this section you can setup and configure the Floating Button that enables your users to easily access your Privacy Center. On the **General Settings** tab, you can customized the following Floating Button features: * **Show Button:** Turn the floating button on or off. * **Button Position:** The position of the Floating Button on your website. Can be placed on the right or left of the screen and will be 24px from the bottom and 24px from the side. * **Button Offset X:** The horizontal offset of the Floating Button on your website. * **Button Theme:** The theme of the Floating Button on your website. Can be set to brand, light, or dark. Brand will use your primary color as the background. Light uses white. * **Button Type:** The type of Floating Button you want to use on your website. Options are a tab with text or a circle with an icon. * **Button Icon:** The icon used for the Floating Button on your website. You can choose between a fingerprint, a cookie, or a shield. * On the **Language Settings** tab, you can customize the following Floating Button features: * **Tab Text:** The tab text used for the Floating Button on your website. ![](/docs/privacy-center-widget-configuration-floating-button.webp) # Custom Branding: Logo, Colors, Font, and Radius URL: /docs/setting-up-custom-branding-logos-colors *** title: "Custom Branding: Logo, Colors, Font, and Radius" description: 'How to update the logo colors, font, and button/card radius within Concord for use in your unified Privacy Center and Consent Banner website experiences.' created: '2023-10-03T23:08:02.000Z' updated: '2024-12-04T02:45:47.000Z' ----------------------------------- ## Overview This document explains how to: * Add your company logo in the branding section. The logo is used in your unified Privacy Center. * Customize the primary and secondary colors in the branding section so they match your company’s desired look and feel. Primary and secondary colors are used in both the Consent Banner and the Privacy Center. * Customize the font, button radius, and card radius in the Privacy Center and on the consent banner. ## Logo To customize your logo, go to **User Experiences** → **Branding** in the Admin UI. ![](/docs/setting-up-custom-branding-logos-colors-1branding.webp) ## Primary & Secondary Colors Concord allows you you customize the branding of the Consent Banner and Privacy Center so they align with your desired look and feel. The secondary color is used for the background of the header in your Privacy Center and the primary color is used for buttons, links, switches, and other elements in your Consent Banner and Privacy Center. To customize the primary and secondary colors, go to **User Experiences** → **Branding** in the Admin UI. ![](/docs/setting-up-custom-branding-logos-colors-website-experiences-branding-colors.webp) ## Customizing Font & Button/Card Radius You can customize the font, button radius and card radius by going to **User Experiences** → **Branding** in the Admin UI. * Font style can be changed to have a custom font in the Privacy Center and on the consent banner. * Card radius settings will affect box/dialog consent borders and larger card styled items in the privacy center. * Button radius settings will affect buttons in the consent banner and Privacy Center. # Embedding Tracker Tables and Policies URL: /docs/website-embeds *** title: 'Embedding Tracker Tables and Policies' description: 'Show your tracker table or one of your policies on your own website with a small snippet that stays in step with what is live in Concord.' created: '2026-10-30T00:00:00.000Z' updated: '2026-10-30T00:00:00.000Z' ----------------------------------- ## Overview An embed is a small snippet you paste into a page on your website. It shows one of two things: * **Tracker table:** the trackers your site uses, grouped by consent category. It usually goes on your /cookies page. * **Policy:** one of your organization's policies, with a "Last updated" date. It usually goes on your /privacy page. You no longer need to copy text out of Concord by hand. When you edit a tracker or publish a new version of a policy, the embed updates on its own. A few things to know: * **It works with or without the consent banner.** The embed has its own script, separate from the banner script. * **It never creates a session.** Embed views are never counted or billed. * **Search engine crawlers can read it.** Crawlers that run JavaScript, such as Google's, see the table or policy like a visitor does. * **It needs JavaScript.** With JavaScript turned off, the embed shows nothing. * **It only shows on your project's domains.** The domains under **Deployment → Domains** work, with their subdomains, along with `localhost` for testing. Unlike the consent banner, the embed doesn't automatically work on Webflow and Framer staging sites (`webflow.io` and `framer.app`), since anyone can host a site there: add your staging site's own domain, such as `acme.webflow.io`, to test the embed on it. On any other site the embed shows nothing and logs a `[Concord embed]` warning in the browser console. The preview on the Embeds tab always works. This check only limits which websites can show the embed. The content itself is public, so anyone can still fetch it directly. ## Availability And Permissions Embeds come with every Privacy plan. No plan feature turns them on or off. To use the **Embeds** tab, you need permission to: * view integrations, to open the tab; * view the project, to see **Your Embeds**; * view documents, to pick a policy; * edit documents, to make a policy Public; * edit the project, to add an embed to **Your Embeds** when you click **Embed**, or delete one from it. Without it, **Embed** still shows the code. ## Get The Snippet 1. Open your project and go to **Deployment → Integrations**, then open the **Embeds** tab. 2. Click **New Embed**, then choose **Tracker Table** or **Policy**. 3. Set the options. For a tracker table, you can limit the table to some tracker types. For a policy, pick which one; only published, active policies are listed. 4. Check the preview next to the options, then click **Embed**. 5. Copy the snippet from the window that opens, and paste it into the page where the content should appear. The Embeds tab fills in your project id and policy id for you. A policy can only be embedded once it's Public, so **Embed** stays off until it is. ## See What's Embedded **Your Embeds**, at the top of the Embeds tab, lists what you've embedded and whether it's live. It starts with a count, such as "2 policies and 1 tracker table embedded. 2 are live." Clicking **Embed** adds the embed to the list. Clicking it again for the same policy, or for a tracker table with the same tracker types, doesn't add a second one. Concord also lists any embed it finds loading on your domains, even one you never added with the button, such as a snippet copied before the button existed. Those show **Found on your site** under **Added**. Each embed has a status: | Status | Means | | -------------------- | ----------------------------------------------------------------------- | | **Live** | A page with the embed loaded on one of your domains in the last 7 days. | | **Not Seen Lately** | It loaded on your site before, but not in the last 7 days. | | **Not Detected Yet** | Concord hasn't seen it load on your site. | **Last Seen** shows the site it last loaded on, how long ago, and how many other sites it's on. An embed you didn't add with the button drops off the list 90 days after it last loaded. How Concord knows: when a visitor's browser fetches an embed's content, it tells Concord which site the page is on, and Concord notes the site. Concord only notes sites that are one of your project's domains, never `localhost` or an IP address, and only for a table whose `data-concord-types` lists real tracker types. The CDN answers most loads for five minutes, so **Last Seen** can be a few minutes behind. The preview on the Embeds tab doesn't count, since it isn't on your site. To get an embed's code again, open its menu and choose **Show Code**. **Delete** takes an embed off the list, not off your site: if its code is still on a page, it keeps showing there and comes back to the list a few minutes after the page next loads. ## The Snippet Every snippet has two parts: * a container `div`, which marks where the content appears; * a script tag, which loads the embed and fills the container. ### Tracker table ```html
``` To show only some tracker types, add `data-concord-types`: ```html
``` ### Policy ```html
``` ### Attributes | Attribute | Used on | Required | What it does | | ----------------------- | ----------------- | ----------------- | ------------------------------------------------------------------------------------------------------ | | `data-concord-embed` | Any container | Yes | `trackers` or `policy`. | | `data-concord-document` | Policy container | Yes, for a policy | The id of the policy to show. | | `data-concord-types` | Tracker container | No | A comma-separated list of tracker types to show. Leave it out to show every type. | | `data-concord-lang` | Any container | No | The language to show, for example `fr`. A policy shows in its own language. See [Language](#language). | Tracker types you can list in `data-concord-types`: | Type | Means | | ----------------- | ----------------------- | | `cookie` | Cookies | | `local_storage` | Local storage | | `session_storage` | Session storage | | `script` | Scripts | | `iframe` | Iframes | | `image` | Pixels and other images | | `link` | Links | You only need one script tag per page, even when the page has several embeds. Put the container where you want the content, and the script anywhere on the page. All embeds on a page use the project of the first embed script that loads, so don't mix embeds from different projects on one page. ### Single-page apps and server-rendered sites The script looks for containers once, when the page loads. If your site adds containers later, for example after client-side navigation in a single-page app or after hydration on a server-rendered site, call `mount()` to render them: ```js window.ConcordEmbed?.mount(); ``` `mount()` only renders containers it hasn't handled yet, so it's safe to call after every navigation. It doesn't re-render a container that already rendered, or retry one that failed. To change what a container shows, for example to switch to another policy, render a new container element in its place and call `mount()` again. If the script hasn't loaded yet, `window.ConcordEmbed` doesn't exist; the script renders every container on the page once it loads. ## Tracker Table The table lists every tracker on your project's **Cookies & Scripts** page, not only cookies. * Trackers are grouped by consent category, in the same order as the privacy center. * Trackers in the **Ignored** and **Malicious** categories are left out. * Categories with no trackers are hidden. * The columns are name, provider, type and description. Every category's table uses the same column widths, so the tables line up. * A tracker with a duration shows it under its type, for example "Duration: 400 days". It's "Session" for a session cookie and "\< 1 day" for one that expires within a day. Most trackers other than cookies have no duration, so they show only their type. * On screens 640 pixels wide or less, each tracker shows as its own block, with its name in bold at the top and each other value next to its column name. Empty values take no space. * The table shows up to 1,500 trackers, the same limit as the consent banner's tracker list. If your project has more, the most recently added ones are shown. Category names and descriptions match what your privacy center shows. If you've customized them, the embed uses the text from your project's default region, the one visitors see when no geography rule matches. ## Policy The policy embed shows the latest **published** version of the policy, with a "Last updated" date. Edits you haven't published yet never appear. A policy only renders when all of these are true: * it's published; * its access level is **Public**; * it isn't archived; * its content was written in Concord's editor. A policy whose content is an uploaded file, such as a PDF, Word or Excel file, or Markdown, can't be embedded. The Embeds tab marks these policies **Can't Be Embedded** and doesn't let you pick them. Formatting such as headings, bold and italic text, lists, tables and links carries over, and so does left, center, right or justified alignment set in the editor on a paragraph or heading. Alignment on a list item isn't kept. Only headings up to level 3 are kept: a smaller heading is left out, along with its text. Images and other inline styles, such as text color, are removed, so the policy picks up your site's own styling. Scripts and anything else that could run code are removed too. ### Making a policy Public If you pick a policy that isn't Public and you can edit documents, the Embeds tab asks whether to make it Public. Without that permission, the tab tells you to ask an admin on your team. Making a policy Public affects more than the embed: * **Trust center access:** if a trust center lists the policy, anyone can open and download it there without requesting access or signing an NDA. * **Unpublished edits:** the trust center serves the policy's current version, not its published one, so it can show edits you haven't published yet. The embed only ever shows the published version. * **AI chat:** your trust center's AI chat can quote the policy, if the chat has indexed it. ## Language The embed asks for a language in this order: 1. the container's `data-concord-lang` attribute; 2. the page's `lang` attribute, for example ``; 3. the visitor's browser language. It uses the first one it finds. Only the language part counts, so `fr-CA` asks for French; the exception is Chinese, where tags such as `zh-TW` and `zh-Hant` ask for Traditional Chinese. If that language isn't one Concord supports, the embed asks for English. * **Tracker table:** category names, descriptions and column headings show in the language asked for when your plan includes the **Languages** feature and languages are turned on in your project's default region. Otherwise they show in the default region's default language, whatever `data-concord-lang` or the page says. Tracker descriptions show exactly as they're written in Concord. * **Policy:** shows in the language the policy is written in, whatever language the embed asks for. The "Last updated" label and date use that language too, and the embed sets that language as the policy's `lang` attribute. If Concord has no "Last updated" text for that language, the label shows in English. If the policy has content in more than one language, the embed always shows the same one. ## Styling The embed renders straight into your page, not inside a shadow root like the banner does. It inherits your site's font and text color, and adds a few default styles: category headings, table borders, a shaded header row, and spacing for the policy's headings, paragraphs and lists. Those defaults survive a CSS reset, such as Tailwind's preflight, Chakra's or Bootstrap's, so a reset doesn't flatten the policy into plain text or strip the table's borders. ### Colors The quickest way to match your branding is to set these CSS custom properties, anywhere in your CSS: | Property | Sets | Default | | ------------------------------------ | ----------------------------------------------- | ------------------------------ | | `--cd-color-embed-border` | Table borders and the dividers between trackers | Your text color at 20% opacity | | `--cd-color-embed-header-background` | The background of a table's header row | Your text color at 6% opacity | | `--cd-color-embed-muted-foreground` | The "Last updated" line and tracker durations | Your text color at 70% opacity | ```css :root { --cd-color-embed-border: #e5e7eb; --cd-color-embed-header-background: #f9fafb; --cd-color-embed-muted-foreground: #6b7280; } ``` Custom properties work from inside a CSS cascade layer too, so Tailwind v4 sites can set them in `@layer base`. The Embeds tab lists every token and class under **Styling**, in **Reference**. ### Class names For anything else, target these class names. They are stable. Each default style is only as specific as one of these classes, because any element in its selector is wrapped in `:where()`, and the embed adds its styles at the very start of ``, so your CSS loads after them. A rule of yours wins when its selector is at least as specific as a single class, such as `.cd-embed__table` or `.cd-embed__policy h2`. That includes Tailwind Typography's `.prose` styles and WordPress global styles. Plain element rules, such as a CSS reset's, are less specific, so they don't affect the defaults. A rule inside a CSS cascade layer loses to the defaults whatever its selector, so put overrides outside a layer. Custom properties work from anywhere. | Class | Element | | ------------------------------------------------------------------------- | --------------------------------------------------- | | `cd-embed` | The root of every embed | | `cd-embed--trackers` | The root of a tracker table embed | | `cd-embed--policy` | The root of a policy embed | | `cd-embed__category` | One consent category in the tracker table | | `cd-embed__category-title` | A category's heading | | `cd-embed__category-description` | A category's description | | `cd-embed__table-wrapper` | The scroll wrapper around a table | | `cd-embed__table` | A table of trackers | | `cd-embed__duration` | A tracker's duration, under its type | | `cd-embed__policy` | The policy body | | `cd-embed__updated` | The "Last updated" line on a policy | | `cd-embed__align-left`, `-center`, `-right`, `-justify`, `-start`, `-end` | A paragraph or heading aligned in the policy editor | Example: ```css .cd-embed__table { font-size: 0.875rem; } .cd-embed__table th { text-transform: uppercase; letter-spacing: 0.04em; } .cd-embed__policy h2 { font-family: var(--your-heading-font); } ``` ### Alignment Text in the tables and policy follows your page's alignment. To align it another way, set `text-align` on the embed, or on one part of it: ```css .cd-embed { text-align: center; } .cd-embed__table th, .cd-embed__table td { text-align: right; } ``` A paragraph or heading that has its own alignment in the policy editor keeps it. Embed tokens and classes use the same `cd-` prefix as the banner's `--cd-*` variables and classes, but the two don't affect each other. The banner's **Custom CSS** settings don't apply to embeds, and embed tokens don't change the banner. ## How Fast Changes Appear Changes appear within a few minutes: up to about **six**, five while our CDN caches the embed plus one while the visitor's browser does. This covers: * adding, editing or removing a tracker; * publishing a new version of a policy; * archiving a policy or changing its access level. Embeds are cached for a few minutes so they load quickly and handle heavy traffic. ## Take An Embed Down * **Policy:** archive the policy, or change its access level from Public to something else. The embed stops showing it within a few minutes. * **Any embed:** remove the snippet from your page. Its status in **Your Embeds** turns to **Not Seen Lately** after 7 days. Deleting it from **Your Embeds** doesn't take it off your site. ## Troubleshooting When the script loads but an embed can't render, the script leaves the container as it was, sets `data-concord-embed-status="error"` on it, and logs one warning starting with `[Concord embed]` in the browser console. A tracker table with nothing left after `data-concord-types` filtering isn't an error: it shows nothing and logs no warning. | What you see | Likely cause | | --------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | The policy embed is empty | The policy isn't published, isn't Public, or is archived. Or its content is an uploaded file, such as a PDF, Word or Excel file, or Markdown, which embeds can't show. Check it in **Documents**. | | A recent policy edit doesn't show | The edit isn't published yet, or it's been less than about six minutes. | | The tracker table is empty, with no console warning | No trackers are left after filtering. Check that `data-concord-types` lists the types you want, spelled as in the table above, and that the project has trackers outside the Ignored and Malicious categories. | | A tracker is missing from the table | It's in the Ignored or Malicious category, or `data-concord-types` leaves its type out. | | A category is missing | It has no trackers left after filtering. | | Nothing renders, and the console says the site isn't one of the project's domains | Add the site's domain under **Deployment → Domains**, then reload the page. A subdomain is covered by its parent domain, so adding `acme.com` also covers `www.acme.com` and `help.acme.com`. | | Nothing renders at all | Check that the script tag is on the page, the project id is right, and the project is active. If the script itself doesn't load, there's no `[Concord embed]` warning, so look for the failed request in your browser's network tab. If your site has a Content Security Policy, its `script-src` directive has to allow `https://api.concord.tech`. | | Nothing renders, and the `[Concord embed]` warning mentions a failed fetch | The browser blocked the script's request for the content, so the warning reads `[Concord embed] Nothing rendered:` followed by an error such as `TypeError: Failed to fetch`. If your site has a Content Security Policy, allow `https://api.concord.tech` in `connect-src`. | | The embed's default styles don't apply | The default styles are added as a `