BlastrAI.
Global
GlobalIndiaUnited StatesUnited KingdomEuropean Union
Book a demo
GlobalIndiaUnited StatesUnited KingdomEuropean Union
Sign inBook a demo
Back to Blastr AI Retention and deletion

Retention must be agreed before production data arrives.

Current Blastr AI retention capabilities and the process for defining or requesting deletion.

Last updated 29 August 2026
The current repository does not expose a self-service, per-campaign retention control. Blastr therefore does not claim configurable retention as a universal product feature.

Website requests

Pilot and demo-call records are retained to respond to the request, evidence the call permission and prevent abuse. The final period should be documented in internal policy and customer terms.

Call data

Status and provider-returned recording or transcript references may be stored in the application. Recording is not described as always on. Campaign-specific recording, disclosure, storage and deletion decisions must be made before launch.

Deletion requests

Send the submission reference, account email or phone number and request type to support@blastrai.com. Blastr may ask for identity or authority verification and will confirm any provider-side steps required.

Contract end

The signed scope or DPA should define return or deletion, legal retention exceptions, backup handling and a completion confirmation.

Need the customer-specific version?

Ask for the current scope, processing details or security response.

support@blastrai.com