SoLoPrint Privacy Addendum

1. Our Relationship with SoLoVision

SoLoPrint is a product of SoLoVision LLC. This document explains privacy practices specific to SoLoPrint. By using SoLoPrint, you also agree to the master SoLoVision Privacy Policy, which covers our overall data protection principles.

2. Information We Collect Specific to SoLoPrint

In addition to the information described in the master policy, SoLoPrint collects:

• Printer Telemetry: Real-time data from your connected printers including temperatures, print progress, job status, and firmware-reported events. This data is transmitted through the SoLoPrint Connect bridge.
• Camera Streams: Live webcam feeds from your printers are streamed through encrypted real-time connections. Camera streams are not stored by default — they are relayed in real time only.
• 3D Model Files: STL, 3MF, OBJ, and G-code files you upload to the cloud file library. These files are stored in your private account space.
• Filament Inventory: Spool metadata you create (brand, material, color, weight) and consumption records tracked during print jobs.
• Print History: Records of print jobs including start/end timestamps, outcomes, file references, and filament usage attribution.
• Account and Organization Data: Email address, display name, authentication identifier, organization membership, role, notification preferences, and device registrations.
• Analytics and Diagnostics: Privacy-limited page views, referral and campaign parameters, sign-in and support actions, activation milestones, application version, device or browser type, performance measurements, and technical error context. We do not place passwords, printer access codes, API keys, private model contents, or support message contents in analytics events.

3. Third-Party Integrations & SDKs

SoLoPrint interacts with several third-party printer firmware ecosystems and tools:

• Printer Firmware APIs: OctoPrint REST API, Klipper/Moonraker JSON-RPC, and Bambu Lab MQTT protocol — connection happens through the local bridge daemon on your network.
• Account and Storage: We use trusted services for secure sign-in, protected data storage, and live printer updates.
• Slicing Engine: SoLoPrint uses an OrcaSlicer-compatible managed slicing runtime and an offline Workshop runtime. Files are processed only to perform the slicing action you request.
• Push Notifications: Firebase Cloud Messaging delivers Android notifications for print events when mobile push is configured and enabled.
• Customer Support: Chatwoot processes support conversations and may receive the SoLoPrint app name, platform, Android package name, app version, support topic, and information you choose to send. Do not send passwords, printer access codes, API keys, or private model files.
• Reliability Monitoring: Sentry processes privacy-limited crash and performance diagnostics. UptimeRobot and Netdata monitor availability and infrastructure health without receiving your model files or printer credentials.

4. Data Retention & Deletion

SoLoPrint allows you to manage your data directly within the application:

• You can delete individual 3D model files, print history records, and spool entries at any time.
• Camera streams are never persisted — they are relayed in real-time only and not stored on our servers.
• Upon a verified account-deletion request, associated printer configurations, files, spool records, and print history are removed from active systems, subject to narrowly required security, backup, dispute, transaction, and legal-retention obligations.

5. Android Permissions and Google Play Data Safety

The Android app requests internet and network-state access to connect to SoLoPrint, post-notification permission to show alerts on supported Android versions, and vibration permission for those alerts. It does not request broad file-system, contacts, SMS, microphone, or precise-location access. Google Play Data Safety answers must remain consistent with the account, analytics, diagnostics, support, uploaded-content, notification, and deletion practices described in this addendum.

6. Local Processing

The SoLoPrint Connect bridge daemon runs locally on your network. It processes printer communication and camera streams on your hardware before transmitting data to the cloud. This local-first architecture means:

• Printer-to-bridge communication stays on your local network.
• Only outbound connections are made — no incoming ports are opened on your network.
• The bridge stores minimal cached state locally (printer IDs and connection tokens) required for reconnection.