Privacy and data.

GitHub release downloads

MobileSlicer beta builds are distributed through GitHub Releases. GitHub hosts release files, source snapshots, and download pages under GitHub's policies.

Model files and G-code

Model loading, slicing, preview, and saved plates are handled on your Android device. MobileSlicer does not upload model files or generated G-code to MobileSlicer servers.

Files can leave the device when you choose to export, share, or send a generated print file to a configured printer or print service.

Thingiverse sign-in

If you choose to sign in to Thingiverse from MobileSlicer, MobileSlicer uses a server-side OAuth bridge on mobileslicer.com to complete Thingiverse's browser authorization flow without putting the Thingiverse Client Secret inside the Android app.

The OAuth bridge exchanges the authorization code with Thingiverse, validates the returned token with Thingiverse, and redirects a short-lived one-time handoff code back to the app. The app redeems that code over HTTPS. The bridge does not persist Thingiverse access tokens beyond the short handoff window and does not persist model files, search queries, thumbnails, or model metadata.

The app stores the returned Thingiverse token locally on your device with Android Keystore-backed encryption so it can search Thingiverse and import files you select through the official API. Thingiverse receives the sign-in, search, file-list, and file-download requests needed for the actions you start.

Printer connections

If you configure printer sending, MobileSlicer contacts the printer or print service you choose. That can include printer status requests, connection credentials or tokens, generated G-code files, filenames, and print commands.

Local printer connections stay on the local network when the printer host is local. Cloud print services, including SimplyPrint, Obico, or PrusaConnect when configured, receive the data needed for the action you start.

Printer credentials

Printer API keys, usernames, passwords, and access tokens are stored locally. MobileSlicer encrypts stored printer secrets with Android Keystore-backed encryption and excludes app data from Android backup and device transfer.

Local network discovery

Printer discovery can use local network discovery, multicast/mDNS, and local subnet checks to find compatible printers on your network.

Camera permission

MobileSlicer may request camera permission when a printer web interface or camera feature shown inside the app asks for it. Camera access is used only after Android permission is granted.

Support contact

If you email MobileSlicer or join the Discord, the information you choose to send is used to answer questions, investigate bugs, and improve device and printer support.

Telemetry and diagnostics

The current MobileSlicer app does not include an automatic analytics or crash-reporting SDK. MobileSlicer does not automatically upload logs, model files, G-code, or diagnostics to MobileSlicer.

If diagnostics are added in a future build, this page will be updated before that build is distributed. If you choose to send support messages, screenshots, logs, or files, that information is used for support and compatibility work.

Retention and removal

Support messages are kept while they are useful for troubleshooting, compatibility work, or required record keeping.

Contact

Questions about privacy, licensing, or support can be sent to [email protected].