Privacy Policy — GCodeView
Effective date: August 18, 2026
GCodeView ("the app") is an Android app that opens and inspects G-code files — toolpath, layers, dimensions, filament use, and other metadata written by 3D printing slicers. This policy explains exactly what the app does and does not do with your information.
Your G-code files never leave your device
All parsing and rendering happen locally on your phone. The app does not upload, transmit, back up, or copy your G-code files, their contents, or any toolpath data to any server — ours or anyone else's. There is no account, no cloud storage, and no sign-in. Opening and viewing files works fully offline.
The app reads a file only when you explicitly choose it through the Android file picker, or when you share a file into GCodeView from another app (for example, a file manager's "Open with" menu, or your slicer's export/share action). It does not request broad storage access and cannot browse your device on its own.
Anonymous usage analytics
The app sends a small number of anonymous usage events through Aptabase, a privacy-focused analytics service, to understand which features are actually used and to guide future development. Aptabase is the only processor this data is sent to.
Every event is a discrete, named occurrence with a small number of fixed-value properties. There are 10 events in total:
- the app was opened
- a file was opened, plus its format, how it arrived (picked, or shared in from another app), and a coarse size band for its point count
- a file failed to open, plus the general kind of failure (for example, unsupported format or corrupt file)
- a .bgcode (binary G-code) file was opened and rejected as unsupported — this shows how often that format is encountered, separately from the cost of adding support for it
- the layer slider was scrubbed, once per drag
- travel moves were toggled on or off
- feature-type coloring was toggled on or off
- a filament price was saved in the cost calculator's dialog — no price value is sent, only that the action happened
- the camera view was reset to its default framing
- a cross-promotion link was tapped
Along with each event, Aptabase records standard technical context: operating system version, device model, app version, country (derived from IP address, which Aptabase does not store), and a session identifier that rotates and is not tied to you.
What is never sent, under any event:
- your G-code files, their contents, or any toolpath/geometry data
- file names, folder names, or file paths
- exact point counts — only coarse size bands (for example "100k–1m points"), never the precise number
- the filament price you enter, or any other value you type into the app
- your name, email address, or any account information (the app has no accounts)
- advertising identifiers or persistent device identifiers
- precise location
This data is anonymous and is not linked to your identity. It is transmitted over an encrypted connection (HTTPS) and is not sold or shared with third parties for advertising. Sending this data is required to use the app — there is no in-app toggle to turn it off, short of denying the app network access at the operating-system level (see below).
Permissions
GCodeView requests a single Android permission: Internet, used to send the anonymous analytics events described above, to open an external link in your browser when you tap one (this policy, or a cross-promotion), and to show the Play Store's own rating prompt. Opening and viewing G-code files works fully offline. The app does not request storage permissions — it uses the Android file picker and share system, which only ever hand it the specific file you chose.
In-app purchases
GCodeView has no in-app purchases and no paid features. Everything in the app, including feature-type coloring, computed print time, and the filament cost calculator, is free.
Children
The app is a general-purpose file utility and is not directed at children.
Data retention and your choices
Because the analytics data is anonymous and carries no identifier tied to you, there is no per-user record we can locate or delete on request. Aptabase retains aggregate event data under its own retention policy. If you prefer not to send any analytics at all, you can deny the app network access in your device settings — the app still opens and inspects files normally with no network connection — or uninstall the app, which removes all app data from your device.
Changes to this policy
If this policy changes materially, the updated version will be published at this same URL with a new effective date, and the app's Play Store Data safety declaration will be updated to match.
Contact
Questions about this policy: amantwd@gmail.com
Data safety summary (Google Play Console)
This section mirrors the Play Console Data Safety form, so the two can be checked against each other directly:
Does the app collect or share user data? — Collects, does not share
Data type — App activity → App interactions
Purpose — Analytics
Is data shared with third parties? — No
Is collection required or optional? — Required — no in-app opt-out
Is data encrypted in transit? — Yes (HTTPS)
Can a user request deletion of their data? — No per-user deletion — the data is anonymous and not linked to identity, so there is nothing to look up
Device or other IDs collected? — No
Files and photos collected? — No — G-code files are parsed entirely on-device and never leave it
Personal info (name, email, etc.) collected? — No
Location collected? — No
Purchases collected? — Not applicable — no in-app purchases exist