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 WebRTC tunnels. 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.

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.
• Database & Auth: We use Supabase for secure data storage, authentication, and real-time database operations.
• Slicing Engine: Kiri:Moto is used for in-browser 3D model slicing. Model data is processed client-side in your browser.
• Push Notifications: Firebase Cloud Messaging (FCM) and Apple Push Notification service (APNs) deliver mobile notifications for print events.

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 account deletion, all associated printer configurations, files, spool records, and print history are permanently removed from our active databases.

5. 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.