Customer exports. JSON or PDF.
Authenticated users can request a data export from the privacy area. Ticaga packages profile data, tickets, responses, IP addresses, and consent records into JSON or PDF.
48h download windowauth protected
GDPR TOOLKIT · COREIncluded with every Ticaga licence
Privacy requests. Sorted.
Give customers a clear path to export or delete their data, give admins an approval trail, and keep optional scripts behind consent. No separate SaaS portal, no per-seat privacy add-on, no spreadsheet of requests to chase.
Deletion requests. Not guesswork.
Customers can request deletion, admins can approve or reject it, and scheduled processing anonymises personal data while preserving the operational ticket record where needed.
approval queuescheduled job
Every consent, timestamped.
Consent records store the consent type, text, IP address, user agent, consent time, and revocation time so you can see what changed and when.
privacy · terms · cookiesrevocable
// CUSTOMER DATA WORKFLOW
Built into the help desk. Not bolted on later.
Most teams handle privacy requests in email threads, spreadsheets, and admin notes. Ticaga keeps the request, approval, export, deletion schedule, and notifications in the same system as the customer record.
- +Customer self-service export and deletion routes under /privacy
- +Admin deletion queue with approval, rejection, notes, and scheduled deletion date
- +Anonymises profile fields, public ticket identity, IP addresses, and active consents
- +Can notify configured third parties by webhook, API-style request, or email when deletion completes
privacy/export request received
→ collect profile, tickets, responses
→ include consent records and IP addresses
✓ PDF or JSON ready for authenticated download
privacy/delete request submitted
→ admin review pending
→ scheduled after retention window
✓ anonymisation job runs daily
Cookie Consent Settings
Banner: enabled
Region: EEA + UK only
Position: top or bottom
Blocks: live chat · tracking
Expiry: 1–3650 days
// COOKIE CONSENT
Consent that can actually control scripts.
The cookie banner is not just decoration. Admins can target EEA/UK visitors, customise the text and colours, choose top or bottom placement, set expiry, and block live chat or tracking until consent allows it.
- +Region-aware banner with fallback behaviour if GeoIP is unavailable
- +Helpers such as gdpr_allows('livechat') and gdpr_allows('tracking')
- +Live Chat integration can show an in-widget consent screen before a visitor starts chatting
| Area | What the extension does | Why it beats ad-hoc compliance |
|---|---|---|
| Data access | Authenticated JSON or PDF export with expiring download token | No manual copy/paste from tickets, profiles, and consent rows |
| Data deletion | Request queue, admin approval, scheduled anonymisation, login disablement | No deleting the wrong customer because someone forwarded an email |
| Retention | Configurable retention years and backup anonymisation scheduling | Legal hold and operational history can be handled deliberately |
| Consent | Consent type, text, IP, user agent, timestamp, and revocation tracking | Proof lives beside the customer, not in a separate consent vendor |
| Cookies/scripts | EEA/UK banner, custom styling, expiry, live chat and tracking gating | Consent changes behaviour, not just a banner message |
| Third parties | Configured webhook, API-style, or email deletion notifications | Article 19 follow-up is tracked instead of remembered manually |
¹ This is compliance tooling, not legal advice. Your organisation still chooses retention rules, lawful basis, subprocessors, and customer-facing policy wording.
// INCLUDED
Privacy tooling should not be a paid panic button.
GDPR Compliance Tools ship with the core Ticaga licence, alongside ticketing, knowledge base, and SLA management.