Where Does the DRK Blutspende App Store Data?
DRK Blutspende keeps donor pass and appointment data in private storage on Android and iOS under distinct IDs.
Last updated
German Red Cross blood donation runs platform specific IDs with deltacity and blutspender flavors. Private storage holds donor login plus appointment cache. The deltacity vendor string belongs to the appointment booking platform behind several donation services.
Donation history lives server side with the donor number. Local data is session plus pass images. Fresh login restores the donor pass after reinstall, including eligibility countdown. Appointment reminders re register with the new install, so confirm the next date after moving.
Where DRK Blutspende stores this, by platform
/data/data/de.deltacity.android.blutspende
Private donor session and pass cache for the verified deltacity package. History syncs from DRK servers.
/var/mobile/Containers/Data/Application/<guid>/Documents
GUID container for the blutspender bundle (App Store ID 391098483). Note the string differs from Android.
Frequently asked questions
Does the DRK donor pass transfer phones?
Log into the same donor account on the new phone. Donations sync from servers. Local data holds session and pass cache, so the move needs no file copies. Eligibility countdown re syncs after login.
Why do DRK IDs differ?
Android uses a deltacity package while iOS uses a net.blutspender bundle. Same donation service, unrelated strings from platform history. Confirm in system app info.
Notice an outdated path? Let us know.