Paytia Data Processing

Customer Personal Data Storage, Retention, and Deletion at Paytia

Overview

This article explains:

• What personal data Paytia stores about end customers

• Why that data is stored

• How customer data can be deleted or erased

• Whether deletion can be self-served or requires support

• What data (if any) is retained in anonymised or limited form

• How long customer data is retained

• Where customer data may exist behind the scenes (logs, backups, linked systems)

Paytia is designed to minimise personal data, never store sensitive card data, and support GDPR and PCI-DSS compliance.

What Personal Data Does Paytia Store About End Customers?

Paytia stores only the personal data required to support secure payments, receipts, scheduling, workflow, and reconciliation.

Important:
Paytia does not store full card numbers (PAN), CVV, or card expiry dates.

Categories of Personal Data Stored

Audio Call Recordings

Paytia can store audio recordings of telephone calls where enabled by the merchant.

Key Points

• Recording is optional and configurable per account

• Paytia custom payment flows ensure that payment card entry is never recorded

• DTMF tones are suppressed before recording

• Recordings may contain:

  • Customer voice

  • Agent voice

  • Non-sensitive conversation content

Recordings are used for:

• Quality assurance

• Training

• Dispute handling

• Regulatory or contractual requirements

Where Is Customer Data Visible in the Platform?

Customer-related data is available through the Log Information menu.

Log Information Sub-Menus

1. Transaction Logs

• Transaction ID and status

• Reference / invoice number
  

• Customer name, address and email data

2. Reports

• Reference / invoice number
  

• Transaction ID and status
  

• Customer name, address and email data

2. Call Records

• Call timestamps

• Call status

• CDR ID

• Telephone number

• Transaction linkage
  

• Phone numbers

3. Third-Party Logs

• Webhooks sent from Paytia

• Delivery status

• Responses received

• Customer name, address and email data

4. Third-Party Webhook Logs

• Payloads received from merchant systems

• Paytia responses

Why Does Paytia Store This Data?

Data is stored strictly for defined operational and regulatory purposes:

• Processing secure payments

• Sending payment links and receipts

• Managing scheduled payments

• Reconciling payments with merchant systems

• Linking calls to transactions

• Supporting audits, disputes, and chargebacks

• Operational support and troubleshooting
  

• Support workflow

Stored Identifiers Explained

Where Is Customer Data Stored?

All Paytia customer data is stored in AWS Ireland (EU-West).

• No customer data is transferred outside the EU

• No processing occurs in non-EU regions

• Regional storage may be introduced in future per account configuration

How Can Customer Data Be Deleted or Erased?

Self-Service via the Platform

Merchants can:

• Export transaction and log data via Excel export

• Manage retention settings where available
  

• Tag data as sensitive where available
  

At present, full deletion of customer data is not self-service. When your account is removed all data is automatically deleted as well.

Deletion via Support Request

To delete customer data:

• Raise a ticket via the Paytia Support Portal

• Or email
  techsupport@paytia.com

Please include:

• Merchant account name

• Customer identifiers (email, reference number, date range)

• Data types to be deleted (e.g. recordings, transactions)

Does Deletion Fully Remove the Data?

Yes — With Limited, Controlled Exceptions

Limited Retention (Anonymised)

Some non-identifiable metadata may be retained in a restricted or anonymised form for:

• Financial audit obligations

• Fraud detection and prevention

• Regulatory compliance

This data:

• Contains no personal identifiers

• Cannot be linked to an individual

• Cannot be reverse engineered

Is Any Customer Data Automatically Deleted?

Yes.

Paytia applies configurable data retention policies based on data type and merchant configuration.

Typical Retention Timeframes

Exact retention settings can be confirmed per merchant account.

Is Customer Data Stored Anywhere Else?

Yes, in tightly controlled supporting systems.

Supporting Storage Locations

Backups and Deletion

• Backups are encrypted at rest

• Backups rotate automatically

• Deleted data is not restored

• Residual backup data expires as backups age out

Account Deletion

If you request full account deletion:

• All customer personal data is removed

• All transaction history is deleted

• All call records and recordings are erased

• Secure payment numbers are released and cannot be reused

Merchants should export any required records before requesting deletion.