Skip to main content

Privacy and data cleanup

note

Looking for the previous SDK? See the 6.x cleanup page.

Bugsee does not continuously stream any personal data. What it records, and the reports built from it, stay on the device until a report is uploaded. When you need that data gone — a user signs out, or withdraws consent — delete it with deleteCollectedDataOnDevice.

Deleting everything​

The completion-only form deletes everything Bugsee has collected for reports:

  • the recording;
  • the data set aside for reports that are not assembled yet;
  • the reports waiting for upload, whose uploads are cancelled;
  • the crashes not reported yet;
  • the performance baselines that anomaly detection has learned from the app.

Stop Bugsee first; a deletion on a running SDK deletes nothing.

[Bugsee stop:^{
[Bugsee deleteCollectedDataOnDevice:^(BOOL success) {
NSLog(@"Bugsee data deleted: %d", success);
}];
}];

Deleting less​

Two more forms delete only part of it, and keep the pending crashes and the anomaly baselines, so the next launch can still report those crashes.

// The recording, plus the data set aside for reports not assembled yet.
// Reports waiting for upload are kept.
[Bugsee deleteCollectedDataOnDevice:YES completion:^(BOOL success) { /* ... */ }];

// The same, plus the reports waiting for upload.
[Bugsee deleteCollectedDataOnDevice:YES
includingBundles:YES
completion:^(BOOL success) { /* ... */ }];
FormRecordingData set aside for reports not assembled yetReports waiting for uploadPending crashes, anomaly baselines
deleteCollectedDataOnDevice:DeletedDeletedDeleted, uploads cancelledDeleted
deleteCollectedDataOnDevice:includingBundles:completion:DeletedWith includingIntermediateWith includingBundlesKept
deleteCollectedDataOnDevice:completion:DeletedWith includingIntermediateKeptKept

With includingBundles, a report the system is uploading at that moment cannot be stopped: it is kept and the completion receives NO; call again once it is done. The completion-only form cancels and deletes uploads in progress instead. A report still being assembled cannot be stopped by either of the two: it is kept and the completion receives NO.

How every form behaves​

  • Stop first. Call stop: and delete from its completion. On an SDK that is not stopped, nothing is deleted and the completion receives NO.

  • The completion is called on the main thread once the deletion has finished or been refused, with YES if everything asked for was deleted.

  • A launch waits. A launch called before the deletion has finished starts after it, unless you call stop: before it starts.

  • It is not a reset. No form deletes:

    • the user identifier and the attributes;
    • the notification relay queue: notifications not sent yet are still sent on a later launch;
    • the Feedback package's conversation cache (unsent messages included) and the email address the user gave the chat.

    Clear the user identifier and the attributes with their own calls:

[Bugsee clearUserIdentifier];
[Bugsee clearAllAttributes];

See User & session data.

Crash Report Extension documents​

If your app embeds the Crash Report Extension, the documents it writes into your App Group are not deleted by these calls. The SDK reads and deletes them on its next launch while exit detection is on. To remove them yourself, delete Library/Bugsee/corpses/corpse-*.json in the App Group container (and, in Debug builds, Library/Bugsee/crash-extension.log).

Found an issue, typo, or wrong statement on this page? Report it now →