Privacy Policy

1. Contact and controller

Device Hub is being prepared under the name G-Works.

Contact for support and privacy inquiries: gworks.support@proton.me

The complete legal provider name and address for service will be added before final publication. A tax number will not be published.

2. Overview

Device Hub manages devices, documents, warranties, and maintenance history. Most data processing takes place locally on the device.

Completely local processing cannot be claimed for every function: manual search uses a dedicated search service and potentially external providers. Confirmed manufacturer sites and Google searches open in an external browser app. The integrated Google ML Kit SDK may also process technical diagnostic and SDK data.

3. Locally stored data

Depending on use, Device Hub locally processes manufacturer, model, category, a freely entered location, Serial Number, Product Number or PNC, local device and notification IDs, purchase and warranty data, reminder options, history with dates, titles, descriptions and costs, device/nameplate/history images, manuals, invoices, warranty documents and attachments, scanner images, quality values, OCR text, recognized values, and backup/restore data.

Device data and file references are stored in a local Hive database. Managed images and documents are held in private app directories. Device Hub creates no server-side device profile.

4. Images and documents

Images and documents are selected or captured only after a user action. Device Hub creates a managed copy in the app area for permanent use; the selected original outside the app remains unchanged.

When replacing or deleting an item, Device Hub removes its managed copy when no longer used. External originals and exported or shared files remain outside Device Hub’s control.

5. Nameplate Scanner and local OCR

The user starts the Nameplate Scanner through the camera or gallery. Image-quality analysis, OCR post-processing, and parsing run locally. The app code implements no cloud OCR and uploads neither nameplate images nor OCR text for recognition.

Temporary scanner and working files may be created in private app cache. OCR variants created by Device Hub and Android scanner sources explicitly marked as app-owned temporary files are deleted on a best-effort basis after use. Files that cannot safely be identified as app-owned temporary sources are retained to protect user originals.

6. Google ML Kit

Device Hub uses Google ML Kit for local Latin-script text recognition. The app code does not transmit image content or OCR text to Google for cloud recognition.

Separately, according to the provider information documented for the project, ML Kit may process device and app information, performance and diagnostic data, and, for bundled features, an installation-related identifier for diagnostics and usage analysis. Documented transmission of this technical SDK data is encrypted. Final legal, retention, and Google Play Data Safety classifications remain under review.

7. Manual search and Manual Search service

Opening manual search performs a technical availability check against the Device Hub Manual Search service. A user-initiated HTTPS search sends the manufacturer, model, an optional normalized Product Number or PNC, and preferred languages including an English fallback.

The app code does not send Serial Number, device or notification IDs, purchase or warranty data, history, costs, images, documents, or raw OCR text. Results are displayed during the workflow but not stored as search history in the local device database.

8. Cloudflare and manufacturer providers

The Manual Search service is provided through Cloudflare Workers. Normal server communication involves technically required connection and request information, particularly IP address, time, route, HTTP method, and other network metadata.

In the latest documented production state, Workers Logs and tracing were disabled, with no external telemetry, storage or analytics bindings, Worker caches, cron jobs, or queues configured. Formal retention, legal roles, processing regions, and full disclosures to manufacturer providers still require external and legal clarification.

The search service may contact external manufacturer services. Their processing and retention cannot be determined conclusively from the app code.

9. PDF downloads and external browser calls

After explicit confirmation, Device Hub may download a selected PDF directly from its HTTPS address. The host receives customary connection and request information such as the IP address. The manual is then stored locally.

Confirmed manufacturer sites and Google searches open in an external browser. A query may include manufacturer, model, an optional valid Product Number, and PDF-manual search terms. Browser and external-provider processing applies after opening.

10. Local notifications

Warranty reminders are optional and scheduled locally using purchase/warranty data, reminder time, and a local notification ID. Device Hub uses no push infrastructure, Firebase Cloud Messaging, or server-side reminder service.

11. ZIP backups, Restore, and Safety Backups

Device Hub ZIP backups are created only by user action and may contain the complete local inventory, including serial numbers, purchase/warranty data, history, costs, images, and documents. Archives contain SHA-256 integrity checks but are not additionally encrypted by Device Hub.

Export and sharing occur only after user confirmation through the operating system. Copies at external storage, cloud apps, or recipients are outside Device Hub’s control.

Before risky Restore or Merge operations, Device Hub creates a Safety Backup in the private app area. At most five are retained and older archives rotate. Users can view, share, restore, and delete them.

12. Android system backup and device transfer

Android Auto Backup and key/value backup are explicitly disabled. Additional rules exclude app data from automatic Android cloud backup and device-to-device transfer. The intended transfer method is a user-initiated Device Hub ZIP backup.

13. Accounts, analytics, and advertising

Device Hub has no registration or user account, hence no server-side account data or account deletion function.

The current app contains no conventional analytics, crash reporting, advertising, or tracking integration, including Firebase Analytics or Crashlytics, and no Advertising ID access. Separate technical ML Kit SDK collection is described in section 6.

14. Storage and deletion

Devices and history entries can be deleted in the app; associated managed files and scheduled reminders are cleaned up as technically provided. Safety Backups can be deleted individually and rotate at five archives.

External originals, exported/shared backups, and external copies must be deleted separately. Binding legal retention periods remain to be established before final publication.

15. Security

Internal data is generally stored in private Android app directories. Manual Search and accepted downloads use HTTPS only; external URLs are checked for prohibited local destinations or embedded credentials.

Backup archives have integrity checks but no additional Device Hub encryption. Users should share them only with intended recipients and protect them appropriately.

16. Privacy on this website

This static site has no code collecting personal data: no JavaScript, forms, cookies, tracking, analytics, external fonts, or embedded external media.

A hosting provider technically processes connection and server information when serving a site. Scope and retention depend on the later Cloudflare deployment and require review before final publication.

17. Outstanding legal details

Before final publication, the complete legal provider name, address for service, legal bases, data-subject rights, complaint options, binding retention periods, and outstanding roles and retention questions for external services will be legally reviewed and added.

18. Contact

Support and privacy inquiries may be sent to gworks.support@proton.me.