Data Deletion – Paymently

Last updated: 2025-08-20

Self‑hosted model: Paymently is deployed on the customer’s own VPS (your “Base URL”). Data that is synced from the mobile app goes only to your self‑hosted Paymently server and is governed by your organization’s policies. Paymently corporate systems do not receive SMS content unless you explicitly send it there.

Scope

This page explains how to remove data from: (a) the Paymently mobile app on your device, and (b) your self‑hosted Paymently server (dashboard). If you use third‑party infrastructure (e.g., cloud provider, backups), follow their deletion procedures as well.

A) Delete Data from the Mobile App (Local Device)

Open the App → Settings > SMS Cleaning.
Choose a retention period or tap Clean All to remove all locally stored Paymently SMS records.
Optionally filter by Status (Failed, Pending, Sent) before cleaning.
(Optional) Sign out to remove cached session data.
(Optional) Uninstall the app to remove remaining local data. Note: This does not remove records that have already been synced to your server.

B) Delete Data from Your Self‑Hosted Paymently Server (Dashboard)

Server‑side data is under your control. An organization admin can delete synced records using one or more of the following methods:

Dashboard (UI)

Sign in to your Paymently dashboard (your Base URL on your VPS).
Navigate to MFS Automation > SMS Data.
Select specific records or apply filters (date range, sender, status), then choose Delete.
Repeat for other entities you may want to remove (e.g., Users, Devices, Logs).

Administrative Actions

Bulk deletion & retention policies: configure scheduled clean‑ups or retention windows according to your compliance requirements.
Backups: if you maintain backups or snapshots, ensure deletions are reflected by pruning or expiring backups per your policy.
Access revocation: disable or remove user accounts to stop future data syncs.

Verification

After deletion, verify by:

Confirming the records no longer appear in MFS Automation > SMS Data.
Reviewing system logs/metrics (if enabled) to ensure no further uploads from removed devices or users.

Legal/Compliance Notes

Because Paymently is self‑hosted, you are the data controller for records stored on your VPS. Configure retention and deletion workflows that match your jurisdictional and contractual obligations.
If you process personal data, consider documenting deletion requests and outcomes for auditability.

Contact

If you have questions about these instructions, email [email protected]. For data stored on your self‑hosted server, contact your organization’s administrator.