Sign in

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, a purge waits for its confirmation, and the audit trail behind it already shows who exported or purged what, 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 dataEverything 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 dataProperties, custom events and consent records, removed after a confirmation. It is permanent, and that is the point.

“I never agreed to that.”

Consent historyEvery 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 historyThe 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
Compliance Hub ⇄ User ProfilesUser Profiles

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

Open Compliance Hub → JourneysJourneys

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

Open

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
AspectFlexEnterprise
EnvironmentDedicated single-tenant instanceYour cloud, your data center or air-gapped
Data residencyThe Google Cloud region you chooseWherever you deploy, including air-gapped networks
Vendor accessOperated by Countly; access limited, granted by you and loggedNo default access
ISO 27001Certified
ISO 27017Certified
ISO 27018Certified
SOC 2Type 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

Try it

Every feature.
One data layer.

Start free trialAll features