SKIP TO CONTENT
Privacy Protocol

DATA DELETION POLICY

LAST UPDATED: May 27, 2026

Introduction

At PEPEBITS, we fundamentally respect the right of our clients and users to manage their digital footprint. This document details the processes, timelines, and scope for the permanent deletion of personal data, technical configurations, and credentials hosted on our systems.

01

Data That Can Be Deleted

  • Access tokens & API credentials
  • Webhooks & Callbacks
  • Integration contact data
  • Technical logs & Heartbeats
  • Configuration metadata

Infrastructure Note

Most operational data resides on client infrastructure. PEPEBITS only retains execution pointers and connectivity logs.

03

PURGE SLA

10Business Days

Maximum timeframe for technical execution of the purge from request confirmation.

02

Deletion Request

Send formal request to:

Required Information:

NAME/COMPANY
REGISTERED EMAIL
INTEGRATION/ASSET
BRIEF DESCRIPTION
04

Direct Effects

Token Revocation

Immediate invalidation of any access keys or associated API keys.

Config Cleanup

Deletion of JSON configuration files and database mappings.

Full Deactivation

Cessation of any active automation flows or workers.

05

Deletion Limitations

Legal Obligations

Billing data and contractual records will be retained as required by applicable tax laws.

External Platforms

We cannot delete data that has been propagated to third-party services (AWS, Azure, Google Cloud) managed by the client.

Own Infrastructure

Deletion from client's local or on-premise servers is the sole responsibility of their technical team.

Ready to initiate the purge?

Our security team will process your request immediately.

PURGE_REQUEST
SECURE_CHANNEL
COMPLIANCE_READY