---
title: "Compliance Hub: consent and data subject requests · Countly"
description: "Consent recorded per feature, a person’s data exported in one file or purged for good, and every action written to an audit trail."
url: https://countly.com/feature/compliance-hub
last_modified: 2026-11-11
---

Compliance Hub

# Answer a privacy request, with the proof attached

Consent recorded per feature, a person’s data exported in one file or purged for good, and every action written to an audit trail. All of it on the server that holds the data, not in another vendor’s inbox.

In this demo health app, every export of a person’s data is on record: who ran it, for which profile, from where and when.

Part of data control

## Consent your app asks for, recorded the way it was given

Countly doesn’t guess at consent. Your app asks, the SDK reports the answer, and Compliance Hub keeps both the current state and every change.

Per feature

### Not one checkbox for everything

A person can allow sessions and crashes and decline push. Each answer is its own opt-in or opt-out, and the profile carries the current state of every one.

Opt-in · Opt-out · Current state

Enforced in the SDK

### Nothing tracked before the answer

Turn on Require consent, and every SDK of the project waits for a decision before it tracks anything. One setting, applied to all of them.

Require consent · Every SDK

Counted

### The whole picture over time

Opt-ins, opt-outs, exports and purges, counted for any date range, so a quarterly privacy report starts from numbers that already exist.

Overview · Any date range

Data requests

## Four requests, one place to answer them

Privacy requests come from people, in their own words. Each one has an answer here, found by device ID and recorded as it is given.

“What do you hold about me?” Export profile data Everything Countly holds for that profile, in one file. A large export runs in the background. Delete the stored file once you have handed it over.

“Delete my data.” Purge profile data Properties, custom events and consent records, removed after a confirmation. It is permanent, and that is the point.

“I never agreed to that.” Consent history Every opt-in and opt-out per feature, with the date, the device and the app version. Download it as evidence.

“Who touched this data?” Export and purge history The account, the time and the IP address of every export and purge. Only global administrators can read it.

Works with

## Compliance Hub, with the rest of Countly

Every feature reads the same live data, so an answer in Compliance Hub doesn’t stop there. These are the handoffs built in.

[All features](https://countly.com/platform/features)

Profiles

Every profile, with its current consent, export and purge in its row menu.

Open

[(Profiles Every profile, with its current consent, export and purge in its row m](https://countly.com/feature/profiles)

Journeys

A consent change can start a journey, such as a thank-you when someone opts in to push.

Open

[(Journeys A consent change can start a journey, such as a thank-you when someone](https://countly.com/feature/journeys)

Audit Logs

Every profile export and purge also appears in the audit log, with who ran it.

Open

[(Audit Logs Every profile export and purge also appears in the audit log, with w](https://countly.com/feature/audit-logs)

SDK Manager

Require consent in every SDK of a project from SDK Manager, and the answers people give arrive here.

Open

[(SDK Manager Require consent in every SDK of a project from SDK Manager, and the](https://countly.com/feature/sdk-manager)

Data ownership

## The data a request is about never left your control

A request is easier to answer, and easier to prove, when the data was never copied into somebody else’s system to begin with.

[Data privacy](https://countly.com/platform/data-privacy)

Aspect Flex Enterprise

Environment Dedicated single-tenant instance Your cloud, your data center or air-gapped

Data residency The Google Cloud region you choose Wherever you deploy, including air-gapped networks

Vendor access Operated by Countly; access limited, granted by you and logged No default access

ISO 27001 Certified

ISO 27017 Certified

ISO 27018 Certified

SOC 2 Type II examined

TISAX® Participant*

*Countly Ltd. is a TISAX® Participant. TISAX® is a registered trademark of and governed by ENX Association. Learn more at [enx.com/tisax](https://enx.com/tisax)
