1. Publisher and scope
This policy applies to SVG Viewer for Android, version 1.0.0, package com.pngexport.svgviewer, published by SodCode. Contact sodcode.app@gmail.com about support or privacy.
2. Local file processing
SVG Viewer opens static SVG and SVGZ documents chosen through Android's file picker, Open with or Share. It copies selected files into private device storage, checks their content, previews them and exports PNG files. SVG contents, file names, embedded pictures and generated PNGs are not uploaded to SodCode, Firebase or the advertising SDK. No account is required and SodCode adds no separate analytics or crash-reporting SDK.
The SVG renderer blocks scripts and external resource requests, including external images, fonts and styles. Embedded images are handled locally. Network access used for advertising or public delivery settings does not permit SVG documents to fetch external resources. A cloud file provider you choose can use the network under its own policy.
3. Storage, retention and deletion
Private app storage contains imported SVG copies, sanitized documents, previews, thumbnails, the most recent 100 sessions, saved export presets, export job records and verification receipts. Session records can include file names, geometry, warnings, viewing position and export options. Preferences contain theme, backgrounds, the chosen export folder, cached advertising settings, launch counters and ad-frequency information. Google SDKs can store consent and advertising state.
Settings → Recent files → Clear removes the retained session copies and related app records. Individual recent items can also be removed. Saved presets can be deleted with a long press in the export inspector. Clearing Android app storage or uninstalling removes private files and preferences; it does not delete original documents, exported PNGs or copies in another app or provider. Android cloud backup and device-to-device transfer of private app data are disabled. Device storage has no additional app-level encryption layer, so protect access to your device.
4. Advertising and consent
When enabled, Google Mobile Ads can display banner, native, interstitial, rewarded, rewarded-interstitial and app-open ads. Banners appear on Home and native ads below Recent files. Interstitials can appear after closing a successful verified export result, with a two-minute frequency limit. App-open ads are limited to eligible launches or returns after at least five minutes away, only on idle Home, with a four-hour frequency limit and guards around documents, dialogs and file flows.
An optional rewarded ad in Settings can hide advertising for the current app process session. A successful batch can offer an optional rewarded-interstitial ad with an explanation and a skip action. Rewards apply only when the SDK reports completion and reset when the app process ends. Skipping or being unable to load an ad never restricts viewing, export sizes, presets, batch export or history. Test configurations use Google's demonstration units.
The app requests non-personalized ads. Google and its services can still collect and share IP addresses, approximate location inferred from the network, device or advertising identifiers, app/ad interactions and diagnostic information for advertising, measurement, fraud prevention and security. Document contents are not supplied with ad requests.
When advertising is enabled, Google's User Messaging Platform updates consent information and presents a consent form where required. Ad requests check whether ads may be requested. An Ad privacy choices entry appears in Settings when required by the SDK. Non-personalized ads do not replace consent where required. Device advertising privacy controls also apply.
See Google's Privacy Policy, Google services in partner apps and Google Mobile Ads data disclosures. Advertiser destinations are separate services with their own policies.
5. Public settings and hosted pages
The app reads public ad delivery settings from Firebase Realtime Database at startup, on resume and approximately every minute. These contain the advertising on/off switch, test/live mode, format switches, ad-unit IDs and an update timestamp. Valid settings are cached locally. Missing, invalid, failed or timed-out configuration keeps advertising off. A previously enabled cache cannot enable ads without fresh server confirmation. Opening the app does not wait for configuration, consent or ad loading. Received changes apply to subsequent ads and cannot recall an ad already on screen.
Configuration requests contain no SVG files, names, paths or export history. Hosting and network providers receive ordinary connection information such as IP addresses and can retain operational logs under their own policies. Opening the online legal documents uses your browser and the website host. Bundled legal documents can be read offline in Settings. Core viewing and export tools work without internet; ads and cloud file providers may be unavailable.
6. Export and sharing
Exports create new PNG files in your chosen folder. The app reopens each saved file and verifies its structure and dimensions before reporting success. Open and Share send the selected file to the app or destination you choose, which can copy, upload or retain it under its own policy. SodCode cannot recall shared files or delete copies held by other providers.
7. Children, security and changes
This general-purpose utility is not directed at children. Process and share only documents you have permission to use. No app or device is guaranteed secure; keep backups of important material. A parent or guardian can contact us with privacy concerns. We may update this policy as features or services change and communicate changes where required. The date above identifies this version. Read the related Terms & Conditions.