Data Deletion Policy
Publication draft. Developer identity and contact details are pending. This document describes the current build with online collection disabled.
1. Stop access to an active share
Use the app’s stop-sharing action to end the local server and invalidate current sharing access. This prevents further access through that session but does not remove bytes a recipient has already received. Stopping sharing is not a remote file deletion operation.
2. Delete local DropLAN data on Android
- Stop active sharing before clearing data.
- Open Android Settings → Apps → DropLAN → Storage & cache (labels vary by device).
- Choose Clear cache to remove app cache, including cached archives where stored. This does not reset all preferences.
- Choose Clear storage / Clear data to remove local app settings and app-controlled stored data, or uninstall DropLAN.
Your selected source documents remain in their original storage locations. To delete them, use the Files app or the provider that owns those files. Check that you no longer need them before deleting.
3. Delete downloaded files and browser data
On each receiving device, delete downloaded files using that device’s file manager or browser download controls, and empty its trash or recently deleted folder if needed. Removing an item from browser download history alone may not delete the file.
Clear cookies and site data for the sender’s local address in the receiving browser to remove browser-held session information. Browser cleanup does not delete downloaded files. DropLAN cannot erase a recipient’s files remotely.
4. Backups and other copies
Android backup, device migration, cloud file providers, and recipient backups may retain separate copies. Manage those copies through the relevant device or provider. Clearing app storage or uninstalling does not guarantee removal of backups or prevent settings from being restored later.
5. Server data and account deletion
No DropLAN account is created in this version. The DevHub collection master switch is disabled, and no Google sign-in or purchase integration is enabled. There is therefore no DropLAN account-deletion workflow or enabled SDK server-data collection to delete in this build.
Country/region, language, manufacturer, model, and Android version are configured as optional statistics but are not currently sent. If enabled later, server deletion arrangements must cover these records and associated installation identifiers. Uninstalling or clearing app data alone does not delete server records.
If online services are enabled in a future version, this policy must identify the data collected, request channel, deletion process, retention periods, and any applicable exceptions. Turning SDK collection off is not equivalent to deleting previously stored server records.
6. Timing and limits
Local deletion is performed by Android, your browser, or your file provider when you use their controls. DropLAN does not guarantee physical overwrite, deletion from backups, or deletion of recipients’ copies. Deletion of app storage resets app preferences and may interrupt an active transfer.
7. Questions or assistance
The developer’s legal name and privacy contact must be supplied before publication. This draft does not submit a deletion request and contains no request form. Read the Privacy Policy for details of local processing.