Skip to main content

Data retention

The Data retention feature allows you to control how long LoopMessage stores request history in its database.

You can configure separate retention periods for:

  • Message history
  • Webhooks history
  • API requests history

These settings can help your organization meet internal data-handling requirements and comply with policies that define how long service providers may retain customer data.

The minimum retention period is 1 day.

We recommend selecting a reasonable retention period rather than automatically choosing the minimum value. Once historical data has been deleted, it cannot be used for troubleshooting or restored for a future support request.

Why does LoopMessage store request history?

LoopMessage stores request history for two primary purposes:

  • To help you review and debug requests through the Dashboard or API;
  • To assist with technical troubleshooting when you contact LoopMessage Support.
  • For users who using no-coding solution and don’t know how to keep everything in their DB.

This information is not made available to the LoopMessage technical team by default. Access to customer message history is provided only when the customer requests tech assistance and the data is required to investigate the issue.

LoopMessage does not use this history for purposes unrelated to providing, maintaining, or troubleshooting the service. The history doesn’t shared with the 3rd party companies.

How does data retention work?

LoopMessage retains each type of history for the number of days configured in your organization settings.

If custom data retention is disabled, message history can be stored for up to 6 months, and request history for up to 2-8 weeks.

When the configured сгыещь retention period expires, the applicable records are automatically deleted from the LoopMessage database.

For example, when API request history is set to 14 days, requests older than 14 days will no longer be available through the Dashboard or API.

Retention periods can be configured independently. Your organization may, for example, retain message history for longer than webhook or API request history.

Choosing a retention period

Although the minimum available value is 1 day, a very short retention period may make it difficult to help you if you have any issues with messaging.

When you contact technical support, our team may need to inspect previous API requests, webhook deliveries, or message activity to determine what happened. If the relevant records have already been deleted according to your retention settings, we may not have enough information to investigate the issue.

Choose a period that balances your compliance requirements with your operational and support needs.

Consider:

  • How quickly your team normally detects and reports integration issues;
  • How long it may take to contact technical support;
  • Whether your organization requires an audit or debugging history;
  • The maximum retention period permitted by your internal or customer data policies.

How short retention periods may affect product features

Some LoopMessage features rely on previously stored message information.

Setting a very short message-history retention period may affect features such as:

  • Reply-to/Message threads;
  • Message reactions;
  • Group conversations;
  • Polls;
  • Other functionality that depends on message IDs

Deleting historical records does not cancel or change messages that have already been delivered. However, LoopMessage may no longer have the stored information required to process actions related to those messages.

How to configure data retention

Data retention settings are configured separately for each organization.

Step 1: Select your organization

Sign in to the LoopMessage Dashboard and select the organization whose retention settings you want to update.

Step 2: Open Data retention settings

In the left sidebar, navigate to:

Preferences → Data retention

Click Edit to change the settings.

Step 3: Enable custom data retention

Turn on Custom data retention.

You can then specify the retention period for each available category:

  • Message history
  • Webhooks history
  • API requests history

The value for each category must be at least 1 day.

Step 4: Save the settings

Review the selected periods and save your changes.

The updated settings will apply to data stored for the selected organization. Records that fall outside the configured retention periods may be permanently deleted and will no longer be available through the Dashboard, API, or technical support tools.

Scope of the feature

The Data retention setting applies only to data stored by LoopMessage for customer access, debugging, and technical support purposes.

It does not control or delete information that may be independently retained by:

  • Telecom carriers;
  • Destination messaging services (or their 3rd party services involved in the delivery process);
  • Recipient devices;

Those parties may process or retain message metadata according to their own systems, policies, and legal obligations.