Privacy Policy

Visualize VR AR 3D Studio

DEEPSPACE Visualize

1. Who we are

DEEPSPACE Visualize ("the App", "we", "us", "our") is a 3D model viewer and editor for Android. It imports, renders and edits 3D models — chiefly the glTF binary format (.glb), plus common mesh and CAD interchange files (.obj, .ply, .stl, .igs/.iges, .step/.stp) — saves and exports them, works with its own project formats (.dsviz, .dsrender, .dsform, .dspart, .dsasm), and includes a public catalog of sample models ("Explore")[cite: 1].

2. The short version

3. Information you create in the App — stored only on your device

Everything in this section is created by you inside the App and remains in the App's own storage area on your device. It is not transmitted to us, and we have no way to read it[cite: 1].

4. Information collected automatically (diagnostics)

The App uses Google Firebase Analytics and Crashlytics to monitor usage metrics and app stability. Collected telemetry includes pseudonymous instance identifiers, session durations, screen views (Rendering, Explore, Settings), technical device properties, and approximate location (country/city level) derived from IP addresses[cite: 1]. File contents, part names, and notes are never sent[cite: 1].

5. Permissions

Requests only necessary permissions: INTERNET for catalog/diagnostics, legacy storage permissions (READ/WRITE_EXTERNAL_STORAGE) for older Android APIs, and WRITE_SETTINGS temporarily to hold screen orientation stable while the system file picker is open[cite: 1].


DEEPSPACE VR

1. Overview

DEEPSPACE VR ("the App", "we", "us", "our") is an Android application for viewing and working with 3D models and immersive Godot-based content in a Cardboard-compatible stereo VR view[cite: 2].

2. Information collected automatically & Firebase

Firebase Analytics automatically logs session metrics, screen views, device attributes, and coarse IP-derived location[cite: 2]. Firebase Crashlytics handles crash stack traces and diagnostic breadcrumbs[cite: 2]. Cloud Firestore delivers read-only catalog listings for the Explore screen[cite: 2].

3. Permissions

Requests INTERNET for data retrieval and telemetry, CAMERA and NFC exclusively for scanning Cardboard viewer setup codes, legacy storage permissions for older devices, and utilizes body sensors (gyroscope/accelerometer) strictly in-memory for real-time head tracking[cite: 2].

4. Imported Godot content (VR Content)

Godot packs (.pck, .zip, .dsplugin) imported by you run within an isolated process. Because third-party packs may execute arbitrary code, users should only import content from trusted sources[cite: 2].


1. At a glance

2. Content and local storage directories

All user artifacts (AR projects, imports, exports, captures, Explore downloads, stickers, and markers) are written exclusively to app-specific local directories under Android/data/com.deepspace.ar/files/DEEPSPACE/[cite: 4]. Auto-saves run locally every 10 minutes[cite: 4].

3. Camera and AR tracking

The CAMERA permission is requested at runtime to display camera previews and process marker detection locally via OpenCV. Frames are discarded instantly after processing[cite: 4]. Device rotation-vector sensors are processed purely in-memory for viewport stability[cite: 4].

4. Firebase Telemetry

Utilizes Google Firebase Analytics, Crashlytics, and Cloud Firestore under project deepspace-9977a to capture anonymous performance diagnostics, screen navigation paths, and load error exceptions without collecting personal identifiers or file contents[cite: 4].


DEEPSPACE 3DStudio

1. Quick summary

Question Answer
Do I need an account? No. There is no sign-up, sign-in, or profile[cite: 3].
Do you see my 3D models? No. Projects, meshes, exports, and screenshots stay on your device[cite: 3].
Do you use ads? No ads, no advertising profiles, and data is never sold[cite: 3].
Analytics Yes — Google Firebase Analytics and Firebase Crashlytics[cite: 3].

2. Information you create and keep on your device

3D projects (*.dsform), imported meshes, exports, capture gallery images, and project thumbnails are written to app-specific storage (Android/data/com.example.deepspace/files/DEEPSPACE/…) and are never uploaded[cite: 3]. Temporary import pick caches auto-expire after 1 hour[cite: 3].

3. Analytics, Crashlytics, and Firestore

Telemetry operates via Google Firebase using a random app-instance identifier. Firebase Analytics logs screen transitions and catalog load events alongside technical device parameters. Crashlytics tracks stack traces and non-fatal recovery reports. Explore catalogs are read via read-only Firestore requests[cite: 3].

4. Permissions

Requests INTERNET for core network communication, standard Firebase service states, legacy storage access for older Android platforms, and WRITE_SETTINGS strictly to manage screen rotation locks safely during system file picker activities[cite: 3]. No location, camera, microphone, or contact permissions are requested[cite: 3].