More in Privacy and security
- Cookieless analytics and consent
- The compliance center explained
- How does TapCub count visitors without cookies?
- What are the three collection tiers?
- Do I need a consent banner?
- Does TapCub honor Do Not Track and Global Privacy Control?
- What does the compliance center control?
- How do I set privacy rules per region?
- What does China mode do?
- How do IP truncation and data retention work?
- How do I export my raw data?
- How do I handle a data-subject (DSAR) request?
- How do I delete a site or my whole account?
- How do I keep personal data out of my analytics?
- All guides in this category
Still have a question?
Could not find it? A person reads every message, usually within a few hours on business days.
Chat with usAnswered step by step on their own pages:
Create an export
Console reports are aggregates. For reconciliation, a backup or your own warehouse you need the rows. Open InsightsDataData export:
- Pick a kind.
events,sessions,persons,autocaptureorconsent_log— events, sessions, people, autocapture records and consent receipts. - Pick a date range. One job can span at most 12 months. Rows older than your retention are already gone.
- Create the job. Status goes queued → running → done. At most two jobs run at once. A finished file is gzip JSONL and stays downloadable for 48 hours; after that the job shows as expired.
Plan limits: Free cannot create raw exports; Pro allows 3 jobs a day; Max and Ultra are not capped per day. A member whose access is narrowed by a scope cannot start a raw export. The same job can be created through the export API.
The row count on a finished job is exported rows, not visitors on a chart. Properties marked export-only are included even though reports cannot break down by them.
Export a report instead
If you only need the numbers on a screen, every table has a CSV download, and any saved report can be scheduled by email weekly or monthly from Pro. Shared links are read-only and can be white-labeled on Max and Ultra. Chat transcripts are exported from the inbox by Owners and Admins.
Data-subject requests
When a visitor or user asks what you hold about them or asks you to delete it, open Compliance centerRequests and create a request. Four types:
| Type | What happens |
|---|---|
| Access | Collects every row for the subject into a downloadable file. |
| Erasure | Deletes the subject's rows after the cooling-off period — 3 days by default, 7 in China mode. Cancel is possible during that window. |
| Restrict | Freezes processing for the subject after the same cooling-off period. |
| Portability | Like access, in a machine-readable layout. |
The subject can be a device ID, a login ID, an email or a person. Requests can also be created with an API key that has privacy:write, and an external privacy platform can submit them through the OpenDSR path. Each request shows who filed it, when it runs and the result.
Opt-out is not deletion
A visitor who opts out on your site stops future collection for their devices. Rows already stored stay until retention expires or an erasure request removes them. If someone asks you to "stop tracking me and delete my data", that is an opt-out plus an erasure request.
Delete a site or your account
- Delete a site: SettingsGeneralDelete site, Owner only. Reports, people and chat history for that site are removed; the site key stops accepting hits immediately.
- Delete your account: Account settingsDelete account. It asks for your password again. All your sites are deleted with it and purged after 30 days.
- Expired plan: data beyond the Free retention is read-only for 30 days, then deleted. See plans and limits.
Deletion is permanent. Create an export first if there is any chance you will need the rows.
Did this answer your question?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.