1. Who this policy covers
This Privacy Policy is provided by the developer of SpaceCleaner (“we”, “us”) for the Android application com.spacecleaner.space and the official SpaceCleaner website linked below. It describes the current version 1.0.2 and the features supplied with that version.
Privacy contact: megaismine22@gmail.com
Official website: SpaceCleaner official website
The Android app, our support mailbox and our hosted webpages are separate contexts. Local processing inside the app does not mean that your browser, email provider, Android services or other apps process no data.
2. Information processed on your device
Photos, videos and media metadata
With the access you grant, SpaceCleaner reads media you make available through Android’s media library or a system picker. This can include file contents, thumbnails, content URIs, file names, sizes, formats, timestamps, dimensions, duration, orientation and embedded metadata. It uses this information to display galleries, identify duplicate candidates or visually similar suggestions, preview files, check compatibility, create copies and verify requested operations.
Media may already contain location tags or other personal metadata. Some generated copies preserve accessible source metadata. The app does not request device location permission or track your live location, and it does not promise to remove embedded metadata.
Storage analysis and media comparisons
The app reads device storage totals and available space, counts unique accessible photos and videos, and measures only SpaceCleaner’s own cache. Foreground analysis and shared scan results are held in memory and reused within the app session. Hashes and visual comparison information can be calculated locally. Visual similarity is a suggestion, not identity recognition or proof that an item should be deleted.
Settings, operation records and temporary files
App-private storage holds appearance and personalization choices, startup permission acknowledgments, widget configuration, selected charging options and device-compatibility preferences. Recovery records may contain media URIs, file names, byte sizes, timestamps, operation status, verification hashes and output receipts. Work and cache files may contain temporary media copies needed to process or verify an operation.
Charging and device state
Charging features read power connection, battery information, screen/keyguard state and relevant permission or capability status. Widgets can read battery and storage information. Manufacturer and Android capability information may be used to offer compatible behavior or settings guidance; it is not used as an advertising identifier.
3. Permissions and your choices
Permissions are used only for the associated features. You may deny access, grant limited photo access where Android supports it, or change access later in Android settings. Some tools will then show only accessible files or be unavailable.
Photos and videos
On Android 13 and later, the app requests photo/video read access as applicable. Android 14 and later may allow access only to photos and videos you select. On Android 12 and earlier, legacy media read permission is limited to API 32. A system picker can also grant access to individual files.
Saving copies on Android 9
WRITE_EXTERNAL_STORAGE is declared only through API 28 and is used to publish app-created copies. It is not used to silently delete your original media. Newer Android versions use MediaStore for supported output publication.
Notifications
On Android 13 and later, the notification permission can be requested in the initial Android permission batch together with missing media permissions. This supports the optional charging monitor’s ongoing status and stop control. Granting notification permission does not by itself enable charging automation. Denial does not cause repeated automatic prompts.
Display over other apps and optional charging monitoring
SYSTEM_ALERT_WINDOW is special access requested in context when you choose charging automation. On eligible Vivo/iQOO devices it can display a bounded, visible charging animation if the normal activity is delayed. It is not used to read other apps’ screens, create hidden windows or collect screen contents.
The app declares foreground-service permissions, including the special-use service type, for the user-enabled charging monitor and its notification. Explicitly applying a theme can enable the monitor after saving the choice and obtaining required access. Previewing, browsing, granting startup permissions or merely acknowledging manufacturer guidance does not enable monitoring or prove a permission is granted.
You can stop monitoring in the app or via its notification and revoke display access in Android settings. Android and manufacturer restrictions still apply. The visible overlay ends on close, expiry, unplug, screen-off, lock or lost eligibility. The app does not promise unattended restart after force-stop or reboot.
The current app does not request all-files access, contacts, microphone, camera, phone-call, live location, accessibility-service, advertising-ID or boot-start permissions. It has no Internet permission. Android’s internal receiver-protection declaration is not an additional user data permission.
4. Originals, copies and Android confirmation
Storage analysis and browsing are read-only. Compression and still-image conversion produce separate copies; originals are retained unless you independently choose an available original-media action and complete the required Android confirmation.
On Android 11 and later, supported trash, delete or restore operations use Android MediaStore consent. On Android 9 and 10, the app does not substitute silent permanent deletion for unsupported system consent: it directs you to your gallery app to manage originals. SpaceCleaner does not clear other apps’ private caches.
Only proven app-owned, unpublished pending outputs or private temporary work files may be removed automatically as part of processing or recovery. Published media copies are not automatically removed as temporary files. A larger copy or an unsuccessful conversion is not reported as space saved.
5. Uploads, sharing and external services
The current Android app has no SpaceCleaner account system, developer-operated upload endpoint, advertising SDK, analytics SDK or automatic remote crash-reporting service. It does not automatically transmit your photos, videos, scan results, local recovery records or charging diagnostics to us, and we do not sell app media or use it for targeted advertising.
Some actions deliberately hand control or data to Android or another app:
- A system media/file picker may retrieve content from a cloud-backed provider you have configured. That provider can use a network connection separately from SpaceCleaner.
- Opening an original in your gallery grants the selected gallery access to that item as needed.
- Wallpaper preview/export creates a local copy. If you choose to continue to Android’s wallpaper flow, a temporary read grant lets the system wallpaper component access that copy; the provider does not expose the whole media library.
- Opening the official website or privacy policy launches a browser or external handler. The browser and host receive the resulting web request.
- Published copies saved in shared media can be seen by other apps with permission and may be synchronized by a gallery/cloud-backup service you separately enabled.
These external services operate under their own policies. A private on-device workflow is not a guarantee that another app or provider you choose never transfers data.
6. Local diagnostic information
To diagnose charging reliability, the app keeps a bounded app-private event log and emits limited events to Android’s local diagnostic log. These records include timestamps, event names and non-identifying state such as power connection, screen/lock state, permission flags, outcomes or error categories. The private charging log retains recent complete events within a 64 KiB size limit, replacing older entries as new ones arrive.
The charging event log is designed not to contain media contents, media URIs, personal file paths, credentials, request tokens or device identifiers. Local codec-compatibility preferences may also be stored to avoid repeating unsupported encoding attempts. There is no automatic diagnostic upload. Android system-log access and retention are controlled by the operating system and authorized debugging tools, not by a SpaceCleaner server.
7. Retention and removal
In-memory analysis
Shared scan snapshots and thumbnails are used within the app process and invalidated when relevant state changes. They are not a permanent cloud copy of your gallery. A small amount of information about explicitly requested operations can remain in the private recovery records described below.
Settings and safety records
Preferences remain until changed, app data is cleared or the app is uninstalled. Operation journals retain up to 100 completed operation records and 50 terminal compression batches while preserving unresolved recovery-sensitive work. Each journal is bounded to 4 MiB; reaching a safety limit can prevent new work rather than silently erase unresolved records. These limits are size/count limits, not guaranteed time-based deletion schedules.
Work files, caches and published media
App-owned temporary files are cleaned when safe to do so; interrupted or unresolved work may be retained for verification or recovery. Wallpaper exports are bounded to eight recent files as new exports are made. Android may also evict cache files. Published copies and user originals in shared media remain until you remove them through the applicable Android or gallery controls; uninstalling SpaceCleaner does not automatically remove them.
You can revoke permissions or stop optional charging monitoring at any time. To remove app-private settings, records and files, use Android’s app storage controls or uninstall SpaceCleaner. First stop active work and resolve any pending operation: clearing app data can remove recovery evidence and does not undo a completed media action.
The app disables Android app backup and declares exclusions for app-private cloud backup and device transfer. This does not control separate gallery synchronization, manually exported files, or every manufacturer’s transfer behavior.
8. Support messages and privacy requests
If you choose to email megaismine22@gmail.com, we receive your email address, message, and any attachments or information you include. We use that correspondence to respond, troubleshoot and handle your request. You do not need to send your photo library, passwords, signing keys or other unnecessary sensitive information. The app does not automatically attach your media or diagnostic records to a support email.
The support address uses Gmail. Sending email involves your email provider, Google’s email services and the recipient’s mailbox; this is separate from automatic collection by the Android app. Support correspondence is retained only as needed to handle the request and any applicable recordkeeping or dispute obligations. There is no promised automatic deletion timer. You can ask for access, correction or deletion of support correspondence, subject to applicable law and legitimate retention requirements.
We cannot remotely inspect or delete files that exist only on your device. For those files, use the local controls described above. If a child has sent personal information to support, a parent or guardian can contact the same address; the app does not ask for date of birth or create user accounts.
9. Website hosting and cookies
The official website and this privacy policy are provided as static webpages. Our page content does not add advertising trackers, analytics tags, account forms, external-font requests or a SpaceCleaner cookie system. Visiting a hosted website is an online activity, separate from local processing in the Android app.
The provider delivering this website, any content-delivery or security service used by that provider, and your browser may process information needed to serve and protect the site, such as IP address, browser details, requested pages, timestamps and access logs. Depending on the provider and its configuration, cookies or similar technologies may also be used. The provider's processing, retention and locations are governed by its own practices and are not determined by SpaceCleaner's Android storage settings. This policy does not claim that the hosting platform sets no cookies or creates no access logs.
Earlier versions of the app may still point to SpaceCleaner pages hosted on Google Sites. Google-hosted pages and our Gmail support mailbox involve Google's services and their own data practices. For those services, see Google’s Privacy Policy and Google’s cookie information. Other external websites or services you choose may have different practices.
10. Security and your controls
The app uses Android’s app-private storage and permission boundaries for internal settings, work files and recovery records. It revalidates access and verification information before sensitive media operations and uses Android consent where supported. These controls reduce risk; no device, service or storage method can be guaranteed completely secure.
Protect your device and email account, review permissions, and avoid sharing media or diagnostic information unnecessarily. This policy does not promise additional end-to-end encryption for local files or third-party email. Local processing also does not erase metadata already present in your files.
11. Changes and contact
We may update this policy when features, permissions, data practices or external services change. The “Last updated” date identifies the current text. Any newly required permission or consent remains subject to the applicable Android or legal requirements.
For questions or privacy requests, contact megaismine22@gmail.com. You can return to the official SpaceCleaner website at any time.