Data cleanup (7.x Beta)

7.x Beta

This page documents the 7.x beta line. For the stable release, see the 6.x cleanup page.

Data cleanup

Bugsee stores unsent reports and buffered capture data on disk. The deleteCollectedDataOnDevice(...) API wipes that store — useful after sign-out, account deletion, or when responding to a user data request.

The SDK must be stopped before calling it. The callback reports whether the deletion succeeded.

Java

// Bugsee must be stopped before deleting the data.
Bugsee.stop();

// includingIntermediate=true also wipes partially-captured / in-progress data.
Bugsee.deleteCollectedDataOnDevice(true, success -> {
    String msg = Boolean.TRUE.equals(success)
            ? "Data deleted successfully"
            : "Failed to delete data";
    Log.i("BugseeCleanup", msg);
});

Kotlin

// Bugsee must be stopped before deleting the data.
Bugsee.stop()

Bugsee.deleteCollectedDataOnDevice(/* includingIntermediate = */ true) { success ->
    val msg = if (success == true) "Data deleted successfully" else "Failed to delete data"
    Log.i("BugseeCleanup", msg)
}

Session attributes are separate

deleteCollectedDataOnDevice(...) does not remove session-scoped data such as user attributes. Clear those explicitly:

Bugsee.clearAttribute("email");
Bugsee.clearAllAttributes();

Pausing capture without deleting

To stop capture temporarily without wiping anything on disk, bracket the sensitive flow with Bugsee.startBlackout() / endBlackout() (these replace the 6.x Bugsee.pause() / resume() pair). For a full shutdown of the SDK rather than visual redaction, use Bugsee.stop() and relaunch with Bugsee.launch(...) later.

Automatic retention

The on-disk report store is a cyclical buffer — older reports are evicted automatically as new ones come in, so collected data does not grow unbounded on the device. deleteCollectedDataOnDevice(...) is the only API needed for an explicit wipe.