Effective October 11, 2026

Twinventory privacy policy

Leech Labs operates Twinventory, a mobile application for keeping inventory in searchable digital representations of shelves, racks, and cabinets. This policy covers the bundled iOS/iPadOS and Android mobile app and these information pages. The separate server-based Twinventory web product is not connected to this mobile app and is outside this mobile policy.

Inventory and information on your device

Twinventory stores workspace names, shelf and bin labels, geometry, items, quantities, serial and asset numbers, barcodes, notes, tags, custom fields, suppliers, purchase orders, prices, stock counts, borrower names and due dates, maintenance dates, and inventory history in the app database on your device. The mobile app has no online account, application server, cloud synchronization, or cloud AI processing. It does not send these inventory records to Leech Labs. Supplier orders are local documents; creating or exporting one does not send it to a supplier.

Photographs, camera, and tracking

You may choose photographs or grant camera access to document storage and items or decode barcodes. Photo correction, image-edge proposals, code decoding, and inventory search run locally. Guided structure capture requires your review; it does not autonomously recognize items. The selected front photograph is retained with the approved scan. Additional captured views and raw camera poses are transient in the current implementation. No microphone, geographic-location service, LiDAR, cloud anchors, or geospatial API is enabled.

On iOS, tracked capture uses Apple ARKit. Android tracked capture uses Google Play Services for AR (ARCore). AR tracking uses camera and motion information to estimate relative positions; these positions are not GPS locations.

Android ARCore processing and technical data

Optional Android tracked capture uses Google Play Services for AR, provided by Google under the Google Terms of Service and Google Privacy Policy. Google documents that ARCore collects account identifiers when signed in, device identifiers otherwise, API usage, and performance/diagnostic information for analytics and service improvement. Google stores these records. Their retention is governed by Google; we do not specify a deletion period. Google documents HTTPS encryption of collected ARCore data on supported devices originally shipped with Google Play. These system-service operations can occur outside Twinventory's own network permissions. You can use manual templates or photographs instead of tracked capture. See Google's ARCore data guidance.

Cloud Anchors and the Geospatial API are disabled in Twinventory. Its configuration does not activate the camera-video, precise-location, or anchor uploads associated with those features. The native app does not upload inventory photographs to Leech Labs or Google.

Exports and sharing

Backups include inventory, photographs, scan records, permanent identifiers, and history. CSV reports, QR label PDFs, and backups are created locally. Native exports use app cache files and the operating-system share sheet. You choose the receiving app, person, printer, or storage provider. Those destinations may transmit or retain the files under their own practices. Leech Labs does not receive a copy automatically. QR labels contain local workspace/item/location identifiers, not remote tracking links.

Advertising, purchases, and analytics

This candidate has no advertising SDK, advertising tracking, subscription, in-app purchase flow, or separate behavioral analytics or crash-reporting SDK. Android ARCore technical collection described above still applies. Future advertising plans are not active features in this version.

Website visits and support

These policy/support pages are hosted through Hostinger. Web requests expose network information such as an IP address to the host; its operational logging and retention are separate from local inventory. See Hostinger's privacy policy. The pages do not include app analytics scripts or visitor editing. If you email support, Leech Labs and its email service receive the contact details and message you send so we can respond. Do not send passwords, confidential inventory, or photographs unless necessary. There is no guaranteed published support-message retention period.

Security

Native inventory uses private app SQLite storage within the operating-system app sandbox. Use a device lock to protect access. There is no app password, local role system, or encrypted-database passphrase. Android automatic app backup is disabled; the iOS database directory is excluded from operating-system backup and requests file protection. Exports in app cache and copies you share need separate protection. Backup checksums detect corruption, not authorship. These controls do not guarantee that a device or exported file is risk-free.

Retention and deletion

Local records remain until you remove the app's data. Archiving keeps history. Restoring a backup creates another retained workspace and does not delete the original. There is no in-app deletion tool for individual retained workspaces in this candidate. On Android, the operating system's Clear storage action removes app data. On iOS/iPadOS, Delete App removes its local app data; Offload App retains documents and data. These actions are irreversible without a usable external backup. See local deletion instructions. Remove separately saved exports from the destinations you control. Uninstalling Twinventory does not erase copies shared with others or Google's ARCore records. For Google records and choices, consult Google's privacy controls. There is no Twinventory online account to delete.

Your choices and children

You may deny camera access, use manual templates and barcode entry, choose which photographs to import, avoid optional tracked capture, export records, and remove local data through your operating system. Twinventory is designed for inventory organization and is not designed as a children's service.

Changes and contact

We update this policy when data handling changes and show the effective date above.