[GH-ISSUE #207] there is no mechanism to delete old data #130

Closed
opened 2026-02-26 21:32:11 +03:00 by kerem · 2 comments
Owner

Originally created by @gdt on GitHub (Aug 23, 2025).
Original GitHub issue: https://github.com/seemoo-lab/AirGuard/issues/207

There should be a way to clear all state (other than having to use Android's "clear app data").

There should be a way to configure a retention interval, so that trackers not seen in the last n days are deleted from memory, so that memory use does not grow in an unbounded manner. I will throw out 30 days as a suggestion; having a choice of "no deletion" and "delete records for devices not observed in 30 days" (perhaps executed daily; there is no need for precision) seems adequate.

(I think it's important not to delete data by default, as this is more or less a research tool.)

Originally created by @gdt on GitHub (Aug 23, 2025). Original GitHub issue: https://github.com/seemoo-lab/AirGuard/issues/207 There should be a way to clear all state (other than having to use Android's "clear app data"). There should be a way to configure a retention interval, so that trackers not seen in the last n days are deleted from memory, so that memory use does not grow in an unbounded manner. I will throw out 30 days as a suggestion; having a choice of "no deletion" and "delete records for devices not observed in 30 days" (perhaps executed daily; there is no need for precision) seems adequate. (I think it's important not to delete data by default, as this is more or less a research tool.)
kerem 2026-02-26 21:32:11 +03:00
Author
Owner

@imbissbudenaesthetik commented on GitHub (Sep 30, 2025):

Hello,

the current behaviour of AirGuard regarding old entries is the following:
We periodically delete data of trackers which have not been seen in the last 30 days and have not triggered a notification.

At the moment this behaviour cannot be changed. We have adding the option to make this configurable in our backlog and might implement it one day.

Greetings
AirGuard-Team

<!-- gh-comment-id:3351649434 --> @imbissbudenaesthetik commented on GitHub (Sep 30, 2025): Hello, the current behaviour of AirGuard regarding old entries is the following: We periodically delete data of trackers which have not been seen in the last 30 days and have not triggered a notification. At the moment this behaviour cannot be changed. We have adding the option to make this configurable in our backlog and might implement it one day. Greetings AirGuard-Team
Author
Owner

@imbissbudenaesthetik commented on GitHub (Nov 28, 2025):

Hello again.

We have just released AirGuard 2.7.0. It includes a new menu only accessible when expert mode is activated where you can set rules how and if trackers should be deleted.

The default behavior will remain that old tracker data is deleted after 30 days if they did not trigger a notification, but this timeframe can now optionally be adjusted to be longer or shorter or be turned off completly.

<!-- gh-comment-id:3588469564 --> @imbissbudenaesthetik commented on GitHub (Nov 28, 2025): Hello again. We have just released AirGuard 2.7.0. It includes a new menu only accessible when expert mode is activated where you can set rules how and if trackers should be deleted. The default behavior will remain that old tracker data is deleted after 30 days if they did not trigger a notification, but this timeframe can now optionally be adjusted to be longer or shorter or be turned off completly.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/AirGuard#130
No description provided.