PushizoDocs
Security & compliance

KVKK and GDPR compliance

Roles (data controller/processor), account owner rights (data download, account deletion, marketing consent), end-user rights, sign-up consent and terms version, retention, subprocessors, DPA and data residency.

Pushizo processes its customers' (your) end-user data on their behalf: you are the data controller and Pushizo is the data processor. For Pushizo account owners (dashboard users), Pushizo is the data controller. This page brings together the rights and tools at both levels, under KVKK (Turkish data protection law) and GDPR.

End users (your users)

RightTool
ConsentSDK requiresPrivacyConsent, location consent, preference center, one-click email unsubscribe, SMS STOP
Access / portabilityGET /v1/apps/{app_id}/users/by/{label}/{value}/export (JSON)
Erasure / right to be forgottenDELETE /v1/apps/{app_id}/users/by/{label}/{value} — subscription tokens are deleted, events/deliveries are anonymized, webhook delivery history is deleted, and the data drops out of backups within 30 days
Storage limitationOrg retention policy (7–3650 days), per-event retention, plan ceiling

Details: user data and KVKK.

Account owners (dashboard users)

RightEndpoint / screen
Download my data (KVKK art. 11, GDPR art. 15/20)GET /internal/v1/auth/me/export → JSON: profile, consents, memberships, metadata of the last 200 sessions, OAuth identities, MFA factor types, MCP OAuth grants, the last 1,000 audit log entries where the account itself is the actor. Password hash, MFA secret and tokens are not included; cache-control: no-store; account.data_exported audit log entry. Dashboard My account → Download my data
Delete account (GDPR art. 17)POST /internal/v1/auth/me/delete { confirm: "<email>", password? | mfa_code? } — the password for accounts with a password; for passwordless accounts, a code if MFA is enabled. If you are the sole owner of an org, 409 owns_orgs (transfer/delete the org first); platform admin accounts get 409 platform_admin. Anonymization is shared with platform admin deletion; SSO recovery codes are deleted, MCP OAuth grants and associated API keys are revoked, marketing consent is cleared, sessions are closed, an account_deleted email goes to the old address, and an account.self_deleted audit log entry is written to the orgs you were a member of. Dashboard My account → Delete account
Marketing consentPATCH /internal/v1/auth/me { marketing_opt_in: true | false } (the first consent time is preserved; turning it off sets marketing_opt_in_at to null) + account.marketing_opt_in|opt_out audit log entry. Off by default at sign-up, with a separate checkbox
Sign-up consentA mandatory "I accept the Terms of Use + Privacy Policy and have read the KVKK Privacy Notice" checkbox on the sign-up form; without accept_terms: true the API returns 400 terms_not_accepted. The acceptance time and terms_version are stored on the account; on first login via OAuth/SSO they are written at the same time
Sessions and MFAMy account → Sessions (sign out of all), sessions are dropped when MFA changes

These endpoints work with a session (cookie + x-csrf-token) and are not part of the public API contract; they are used by the dashboard. Platform admins can see terms acceptance (time + version) and marketing consent in the account details.

Organization level

  • Org deletion: permanent purge after a 30-day waiting period (a window in which it can be undone).
  • App data purge: deletes user data and keeps the configuration.
  • Data export requests and audit log export (a plan feature); daily NDJSON for SIEM and the audit.created webhook.
  • Retention and session policies: from the org settings (retention days, session duration, mandatory MFA, IP allowlist).
  • Data residency: region (EU/TR) selection when creating an org; data stays in the selected cell, and region migration is a controlled process (data residency).

Agreements and subprocessors

Legal texts published on the marketing site: Terms of Use, Privacy Policy, KVKK Privacy Notice, Cookie Policy, Data Processing Agreement (DPA), subprocessor list and Acceptable Use Policy (https://pushizo.com/legal/…; English at /en/legal/…). In your own installation, these texts are published from the files in apps/web/content/legal/; if a file is missing, the page is not published (there is no placeholder text).

Push providers (Apple, Google, Huawei), email/SMS providers (SES, Resend, Twilio, Netgsm, Meta) and the integration destinations you choose are subprocessors that work with the credentials you configure; data is transferred only with the fields required for that channel.

Technical measures (summary)

Encrypted secret storage, tenant isolation with RLS, TLS, log masking, access control and audit logging, off-server backups with separate credentials, DR drills: security overview and ASVS checklist.

On this page