1. Publisher and scope
SodCode publishes Image Splitter, version 1.0.0, Android package com.image.pixelsplitter. Contact sodcode.app@gmail.com for privacy questions or support.
Image Splitter divides a selected image into tiles on your device. No account is required. SodCode does not operate an image-upload service or send selected image pixels, filenames, cut positions, saved layouts or export history to advertising services. Advertising, consent, public delivery settings and hosted legal pages use the network separately from image processing.
2. Images and file access
You select an image with Android's system document picker or share one from another app. The app receives access to the document you choose and copies it into app-private storage for processing and recovery. It does not scan your gallery or request broad storage, photo-library, camera, microphone, contacts or precise-location access for splitting.
Images are read rather than overwritten. Separate tiles, ZIP files and optional JSON tile maps are written to a folder or document you choose, or staged temporarily for the Android share sheet. The app can retain system-granted access to selected documents and folders so it can reopen files or resume an export. A cloud document provider may download or upload files under that provider's own terms.
Android network permissions support ads, consent and remote configuration. Google's advertising SDK can declare advertising-related permissions, including access to the advertising identifier where available. Device privacy controls can restrict those identifiers.
3. Local storage and retention
The local SQLite database contains job records, tile bounds, output filenames and references, checksums, result/error statuses, saved layouts and preferences. The app aims to retain the 500 most recent finished exports and three recent drafts, while keeping interrupted or partially failed jobs that need attention. Pruning occurs when another image is imported; the number of retained records can exceed those targets while unresolved jobs remain.
App-private source copies allow editing and retrying jobs and can remain until their job is removed or pruned. Orphaned working copies and previous share-staging files are cleaned on startup. Temporary encoding files can remain after an interrupted process until app or operating-system cleanup. Exported files in user-selected folders are separate from the app's private copies.
Advertising delivery settings and limited launch/frequency counters are cached locally. Google SDKs may keep their own consent and advertising state. Android backup of the app's private data is disabled. Local history is not a backup service and may become unusable if a file is deleted or a document provider revokes access.
4. Advertising, rewards and privacy choices
When enabled, Google Mobile Ads may show banner, native, interstitial, rewarded, rewarded-interstitial and app-open ads. Delivery depends on connectivity, consent, inventory and publisher settings. Fullscreen ads are limited to eligible launches/returns or breaks after an export; they are suppressed during image editing, active exports and system file/share flows.
Optional rewarded offers can hide ads for the current app process session after the SDK reports completion. Declining an offer, closing an ad, or an ad being unavailable does not remove image-splitting, saved-layout, ZIP, tile-map or history features. There are no purchases, subscriptions or paid feature unlocks in this version.
The app requests non-personalized ads. Advertising can still process IP addresses, approximate location inferred from the network, device or advertising identifiers, ad/app interactions and diagnostics for delivery, measurement, fraud prevention and security. SodCode does not attach selected image contents to these requests, add a separate analytics SDK, or sell your images.
Google's User Messaging Platform updates consent information on launch when advertising is enabled and presents a form where required. Ads are requested only when the consent SDK permits it. An Ad privacy choices entry appears in Settings when the SDK requires a privacy-options entry point. Non-personalized requests do not replace any required consent.
Read Google's Privacy Policy, Google's information about partner apps, and Google Mobile Ads data disclosures. Advertisers and destinations have their own privacy practices.
5. Public delivery settings and hosted pages
The app reads the public Firebase Realtime Database record appConfig/imageSplitter/ads. It contains the advertising master switch, test/live mode, per-format switches, ad-unit IDs and an update timestamp. A valid copy is cached. The app refreshes at startup, on resume and approximately every minute while running. If a request fails, the last valid cache or test-mode defaults can be used. Disabling ads takes effect when the app receives the change and cannot recall an ad already displayed.
Configuration requests do not upload images, filenames, layouts or job history. Firebase, Google and hosting providers receive ordinary connection information, such as an IP address, and may keep operational logs under their own policies. Opening a hosted legal page uses the system browser. The app also includes offline copies of these documents.
7. Security, children and changes
Platform permissions and app-private storage help restrict access, but no device, network or service is guaranteed secure. Protect your device and check where sensitive files are exported. This is a general utility app and is not designed to collect information from children. Use images only with appropriate rights and permissions; parents or guardians may contact us about concerns.
We may update this policy as features or providers change and will communicate changes where required. The date above identifies this version. Read the related Terms & Conditions.