PushizoDocs
Users & segments

User data and KVKK/GDPR

Privacy tools for end-user data — consent (requiresPrivacyConsent), data export and deletion endpoints, retention periods, anonymization, webhook and backup implications.

Pushizo is the data processor; you are the data controller. This page describes the tools provided for end-user data; for the rights of account holders (dashboard users) and organizational compliance, see KVKK/GDPR compliance (KVKK is the Turkish data protection law).

Consent

  • In client SDKs, while requiresPrivacyConsent: true, no network requests are made until setConsentGiven(true) is called; tag/event operations wait on the device.
  • Location sharing requires separate, explicit consent (Location.setShared(true)); turning it off deletes the location (location).
  • Web slidedown texts and email/SMS collection prompts can be customized; the preference center gives users control over channels/categories (preferences).

Data export (portability)

GET /v1/apps/{app_id}/users/by/{label}/{value}/export (users:read) returns a single JSON document: profile, aliases, tags/properties, subscriptions (tokens masked), preferences, recent events and conversions. Dashboard: user detail → Export. In the server SDKs: hs.users.export(label, value).

Deletion

DELETE /v1/apps/{app_id}/users/by/{label}/{value} (users:write):

  • The user, aliases, subscriptions (including tokens), preferences, notification inbox items and in-app impression records are deleted.
  • In event and delivery records, user_id is anonymized (statistics are preserved but cannot be linked to the person).
  • All webhook delivery records for that user (sent and pending) are deleted; a user.deleted event is sent to the receiver.
  • The deletion also drops out of backups within 30 days (the backup retention period).

For merged users, deletion covers all merged records. At the app level, Clear data deletes all user data while keeping channel/segment/template definitions and the suppression list; organization deletion becomes permanent after a 30-day waiting period.

Retention periods

DataDefaultSetting
Events90 daysRETENTION_EVENTS_DAYS; org policy (7–3650 days) and per-event retention
Delivery records90 daysRETENTION_DELIVERIES_DAYS
Delivery events (timeline)30 daysRETENTION_DELIVERY_EVENTS_DAYS
Webhook deliveries30 daysfixed
Audit log365 daysRETENTION_AUDIT_DAYS
Import files7 daysIMPORT_FILE_RETENTION_DAYS

Retention is enforced by dropping partitions and, if ClickHouse is used, mirrored as TTL. The plan-based retention_days (30/90/365/730) is the upper bound of the org policy (plans).

Other surfaces that carry personal data

  • Webhook payloads carry user identifiers; retention in the receiving system is your responsibility.
  • Data warehouse export and Event Streams copy the fields you choose to external systems (analytics & data).
  • The suppression list does not store raw addresses; log masking hides email/phone/token values.
  • Data residency: an org's data stays in the selected cell (EU/TR) (data residency).

On this page