1. Publisher and scope
SodCode publishes JSON Viewer for Android, package com.json.losslesseditor, version 1.0.0. Contact sodcode.app@gmail.com for privacy or support questions.
The app opens, validates, searches, formats and edits JSON on your device. No account is required. SodCode does not operate a JSON upload or synchronization service and does not send your JSON contents, keys, values, filenames, paths, bookmarks or edit history with advertising or configuration requests. Advertising, consent, public delivery settings and hosted legal pages use the network separately from document processing.
2. Files, clipboard and permissions
You choose files through Android's document picker, Open With or Share. The app reads only documents or text you provide and copies imported JSON into app-private storage. It does not scan your storage or request broad storage access. The clipboard is read only when you explicitly choose Paste from clipboard; copying a value or path writes the selected text to the system clipboard.
A selected document provider may be a cloud service. That provider can download or upload files under its own policy. Android may retain a user-granted content-URI permission so selected files or exported copies can be accessed again. Network permissions support advertising, consent and public configuration. Google's advertising SDK may declare advertising-ID and related permissions. JSON inspection does not require contacts, precise location, microphone or camera access.
3. Local document storage
App-private files hold the original imported bytes, the current working copy and, when an edit is invalid, a snapshot of the last valid source. A local database stores document metadata, undo/redo edits, bookmarks and export verification records. Undo records can contain the removed and inserted JSON bytes; bookmarks can contain a preview of a value. Exports contain the JSON you choose to save and are separate files in your selected destination.
Preferences include theme, editor settings, cached ad delivery configuration and launch/frequency information. Google's consent and advertising services can maintain their own local SDK state. The app excludes its private data from Android cloud backup and device-to-device transfer. Private JSON files and the database do not have an additional app-level encryption layer; protect your device and its backups, clipboard and access permissions.
4. Advertising and consent
When enabled, Google Mobile Ads can display banner, native, interstitial, rewarded, rewarded-interstitial and app-open advertisements. Availability depends on connectivity, consent, inventory and publisher settings. Banners are on Home; native ads appear separately in History. Interstitials can appear after you finish a verified export. App-open ads are limited to eligible launches or long returns to idle Home, with guards around document editing, dialogs and external file flows.
Optional rewarded ads offer an ad-free current app process session when the SDK reports completion. Rewarded-interstitial offers after a successful batch include a skip option. Skipping, closing, failing to load or being unable to complete an ad does not remove JSON features. Tabs, bookmarks, batch formatting, undo, validation and verified export remain free. Ending the app process resets the optional session reward. Development configurations can use Google's demonstration ads.
The app requests non-personalized ads. This does not mean no information is processed. Google and its services can collect and share IP address, approximate location inferred from the network, device and advertising identifiers, app/ad interactions and diagnostic information for advertising, measurement, fraud prevention and security. We do not supply JSON content to Google Mobile Ads. SodCode does not add a separate analytics or crash-reporting SDK.
Google's User Messaging Platform updates consent information on launch and presents a consent message where required. The app checks whether ads may be requested before initializing ad delivery. An Ad privacy choices entry appears in Settings when required by the consent SDK. Device privacy controls may restrict advertising identifiers. A non-personalized request does not replace consent where required.
See Google's Privacy Policy, information about partner apps, and Google Mobile Ads data disclosures. SDK advertising traffic is protected in transit as described by Google. Advertiser destinations have their own policies.
5. Public settings and hosted pages
The app reads public advertising delivery settings from Firebase Realtime Database at startup, on resume and approximately every minute. These settings contain the advertising master switch, test/live mode, format switches, ad-unit identifiers and an update timestamp. Valid settings are cached locally. If a request fails, the app can use a valid cached copy or test-mode defaults. Remote changes apply after the app receives them and cannot recall an ad already on screen.
Configuration requests do not include JSON files, names, paths or edit history. Network and hosting providers receive ordinary connection information, such as an IP address, and can keep operational logs under their own terms. Opening a published legal page uses your system browser and the website host. Bundled copies of these documents are available in Settings without a network connection. Core JSON tools remain usable offline; online ads or cloud document providers may not be available.
6. Export, sharing and deletion
Export creates a new file, reads it back, compares its bytes and parses it before reporting success. Open and Share use the platform apps and destinations you choose. A receiving app, provider or recipient can copy, upload, retain or forward the content under its own policy. The app cannot recall a shared copy or erase files held by another provider.
Remove an imported document from Home, clear closed recent documents, or use Settings → Delete local data to remove private imported copies, history, bookmarks and export records. This does not delete originals or exported files. Clearing Android app storage or uninstalling removes app-private files, settings and cache; exports elsewhere can remain until you delete them. SodCode has no server copy from which to recover JSON documents. Copies in another app's clipboard history or cloud provider are controlled separately.
7. Children, security and changes
This is a general-purpose utility and is not directed at children. Use only content you have permission to process and share. A parent or guardian can contact us about privacy concerns. No device or service can be guaranteed secure; review JSON for credentials or personal information before sharing it.
We may revise this policy when features or service providers change and will communicate changes where required. The date above identifies this version. Read the related Terms & Conditions.