Loading Kronus…
Skip to main content
Kronus Instruments
Kronus Instruments
PricingPortal
Legal

Privacy Policy

Last updated: September 12, 2026

This Privacy Policy explains how Kronus Instruments Inc. collects, uses, stores, and shares information when you use Kronus Field, CorrosionMapper, our website, web portal, iOS app, cloud services, hardware/device integrations, report generation tools, and AI-assisted features.

1. Data We Collect

We collect data needed to provide inspection, measurement, collaboration, reporting, security, diagnostics, billing, and support features.

CategoryExamplesSourcePurposeRequired or optional
Account and contact dataName, email, phone, job title, company, profile photo, user ID, role, device tokensAccount, profile, authentication, notificationsAuthentication, profiles, team access, notificationsMostly required for accounts; notifications optional
Company and team dataCompany membership, project roles, invitations, assigners, membersAdmins and collaboration workflowsRole-based access and collaborationRequired for team use
Project, site, and job dataProject names, addresses, GPS coordinates, client info, notes, standards, thresholds, captures, schedulesUsers, location features, project setupManage inspection projects and reportsRequired for project workflows; location auto-fill optional
Photos, videos, and inspection mediaPhotos, videos, captions, tags, comments, annotations, before/after pairs, upload metadataCamera, photo library (read and, if enabled, write-back of captured media to your device), web uploadInspection evidence and reportsOptional feature content
Measurements and sensor readingsGrid points, corrosion potentials, moisture, temperature, humidity, timestamps, instrument typeManual entry, Bluetooth hardware, environmental sensorsInspection analysis and heatmapsRequired for measurement features
Bluetooth and hardware identifiersPeripheral UUIDs, advertised sensor names, app-assigned sensor UUIDs, RSSI, batteryBluetooth pairing and sensor syncConnect devices and import readingsOptional hardware feature
LiDAR, AR, and 3D scan dataRoomPlan geometry, USDZ/GLB models, depth metadata, camera intrinsics, transforms, area measurementsCamera, ARKit, RoomPlan, LiDAR devicesArea measurement and 3D inspectionOptional feature content
Notes, audio, and transcriptsVoice notes, audio files, transcripts, word timestamps, commentsMicrophone, speech recognition, user text entryField notes, annotations, AI-assisted parsingOptional feature content
Reports and exportsReport templates, drafts, runs, PDFs, report assets, signed photo linksReport builder and export workflowsGenerate and share inspection deliverablesOptional but core to reporting
Diagnostics and security dataCrash logs, error reports, stack traces, page URLs, user agent, device model, OS, session ID, memory/disk/network stateCrashlytics, web error reporter, Firebase Performance, Cloud Functions logsReliability, abuse prevention, security, supportRequired for service operation
Payment, subscription, and contact lead dataStripe customer/subscription IDs, billing plan, checkout metadata, contact form name/email/company/messageBilling and public contact/demo formsBilling, sales, supportOptional unless using paid/contact features
AI prompts and outputsPrompt text, report prompts, transcripts, project facts, measurement summaries, AI responsesAI chat, report analysis, inspection parsing, measurement assistantAI-assisted analysis and writingOptional AI features
Local and browser storageOffline Firestore cache, encrypted sync queue, local media/cache files, settings, remembered email, session profile cache, signed URL cacheiOS app and web portalOffline use, sync, preferences, performanceRequired for core/offline functionality

2. App Permissions

  • Camera: used to capture inspection photos, videos, LiDAR/AR frames, and RoomPlan scans. If denied, camera-based capture features will not work.
  • Photos: used to attach existing images from the photo library, and, when you enable it in settings, to save newly captured inspection photos and videos into project albums in your device's photo library. If denied, you can still use other project features.
  • Location: used to auto-fill project addresses and attach optional location/heading metadata to project media. If denied, you can enter addresses manually and use most features without GPS metadata.
  • Motion sensors: used to estimate camera tilt/level (a level guide) when capturing inspection photos. If denied, capture still works but the level guide will not be available.
  • Bluetooth: used to connect to external corrosion and environmental measurement sensors. If denied, Bluetooth hardware import will not work.
  • Microphone: used for voice notes and video audio. If denied, audio recording features will not work.
  • Speech recognition: used to convert voice recordings into text notes. If denied, you can keep audio notes without speech transcription where supported.
  • Notifications: used for invitations, assignments, mentions, and deadline reminders. If denied, in-app data remains available but push alerts will not be delivered.
  • Face ID: used for local biometric sign-in preference where enabled. If denied, standard authentication remains available.
  • Files/document picker: used when you choose files, images, plans, reports, or exports. Access is user-initiated.
  • LiDAR, ARKit, and RoomPlan: used for area measurement, depth metadata, and 3D/room scans on supported devices. These features use the camera permission.

3. How We Use Data

  • provide inspection, measurement, mapping, photo, video, audio, LiDAR, 3D scan, and hardware integration features;
  • save, synchronize, and recover offline project data across the iOS app, web portal, and Firebase cloud services;
  • generate heatmaps, charts, reports, PDFs, exports, report templates, and customer-facing deliverables;
  • support team collaboration, project membership, invitations, mentions, capture assignments, reminders, and notifications;
  • authenticate users, enforce role-based access controls, prevent abuse, and protect accounts and project data;
  • provide customer support, diagnose errors, monitor reliability, and maintain service security;
  • operate billing, subscriptions, contact/demo requests, and related administrative workflows;
  • provide AI-assisted report generation, transcript cleanup, inspection parsing, project assistance, and measurement analysis when those features are used.

4. AI Processing

Some features send data to AI services, currently OpenAI through authenticated Firebase Cloud Functions. Depending on the feature, this may include user prompts, report prompts, voice transcripts, tags, comments, project facts, measurement summaries, report context, and related AI outputs. AI features are optional, but project data submitted to them may include customer confidential information.

Kronus Instruments Inc. does not use customer project data to train Kronus-owned AI models. OpenAI states that API inputs and outputs are not used to train OpenAI models unless a customer explicitly opts in. Kronus does not opt in to AI provider training on customer project data. TODO: confirm the production OpenAI account's retention settings, including whether standard abuse-monitoring retention, Modified Abuse Monitoring, or Zero Data Retention applies. Enterprise customers should contact us before enabling AI workflows that involve confidential project data.

5. Sharing and Subprocessors

We share data with service providers and subprocessors that help us provide the service. They may receive customer content, personal data, or diagnostic data depending on the feature used.

  • Google Firebase and Google Cloud: authentication, Firestore database, Cloud Storage, Cloud Functions, App Check, Firebase Cloud Messaging, Crashlytics, Performance Monitoring, backups, logging, and hosting.
  • OpenAI: AI-assisted analysis and text generation when AI features are used.
  • Stripe: payment, checkout, subscription, and billing workflows if enabled for your workspace.
  • SendGrid, SMTP, or email providers: invitations, contact/demo requests, account-related messages, and support communications where configured.
  • OpenStreetMap/Nominatim and Open-Meteo: address geocoding and historical weather context for project locations.
  • Apple services and frameworks: iOS camera, photos, location, speech recognition, Bluetooth, ARKit, RoomPlan, APNs, and biometric features.
  • Third-party app libraries: Firebase/Google iOS SDK dependencies and bundled image/3D processing libraries such as OpenCV.

TODO: publish a current subprocessor list and enterprise DPA details.

6. What We Do Not Do

We do not sell personal data. We do not share personal data for cross-context behavioral advertising. We found no code evidence of third-party advertising SDKs, cross-app advertising trackers, or advertising networks in the audited app, web, or cloud source.

7. Data Ownership and Customer Content

Customers own their project data, reports, photos, videos, measurements, notes, uploaded files, and generated inspection content. We process customer content to provide, secure, support, and maintain the service. Organization admins and project owners may control access to projects, invite or remove members, assign roles, generate reports, and delete or archive records depending on account settings and permissions.

TODO: confirm the admin access policy, support access policy, and enterprise data export/deletion controls.

8. Retention

We retain account, project, inspection, media, report, billing, diagnostic, and support data for as long as needed to provide the service, maintain project history, comply with obligations, resolve disputes, enforce agreements, and protect the service.

The platform uses soft deletion for many project records. Code evidence shows that soft-deleted projects, measurements, test spots, plans, photos, and videos are scheduled for permanent deletion after approximately 60 days, with best-effort deletion of related storage files in some cleanup paths. Read notifications may be deleted after approximately 90 days, and all notifications may be deleted after approximately 180 days.

Daily Firestore backups are created for disaster recovery. TODO: confirm and publish the backup lifecycle period, log retention period, support/contact retention period, account deletion SLA, project deletion SLA, AI request log retention, and Stripe/email-provider retention.

9. Security

The service uses Firebase Authentication, custom claims, Firestore security rules, Storage rules, role-based project/company membership checks, App Check, authenticated Cloud Functions, short-lived signed upload URLs, and signed download URLs for certain report/photo workflows. Firebase and Google Cloud provide encryption in transit and at rest for their hosted services.

On iOS, the app supports offline use with Firestore persistent cache, encrypted sync queues, Keychain-stored encryption keys, file protection for some local files, and local cache controls. Some local media and browser storage are not separately app-encrypted. No internet or software service can be guaranteed completely secure.

TODO: confirm backup controls, audit-log availability, support access controls, and formal SOC 2/security claims before publishing enterprise security statements.

10. User Choices and Rights

You can export or delete your personal account data yourself from Settings in the web portal (Export my data / Delete account). Account deletion removes your profile, company memberships, and personal notifications; if you are the sole owner of a company, you will need to transfer ownership or delete that company first, since project and billing data belong to the company, not to any one person. Company-owned project, photo, video, and report data is controlled by the organization or project owner — requests affecting that data may require approval from an authorized admin. For anything the self-service tools don't cover, including correction requests, you may also contact us.

You can manage iOS permissions in device settings, disable push notifications, remove project members where your role allows it, revoke invitations, delete or archive records where permitted, and avoid AI features if you do not want project data sent for AI processing.

TODO: confirm California, EEA, UK, and other jurisdiction-specific rights language, export controls, deletion controls, marketing opt-out, and AI opt-out/admin controls.

11. International Transfers

Our service providers may process data in the United States and other countries where they or their infrastructure operate. TODO: confirm international transfer mechanisms, including any data processing agreements or standard contractual clauses used for enterprise customers.

12. Children

The services are intended for business, engineering, inspection, and professional use. They are not intended for children under 13 or under the applicable age in the user's jurisdiction, and we do not knowingly collect personal information from children.

13. Changes to This Policy

We may update this Privacy Policy from time to time. When we make material changes, we will update the date above and may provide additional notice through the website, app, or account communications.

14. Contact Us

Privacy requests may be sent to privacy@kronusinstruments.com. Support requests may be sent to info@kronusinstruments.com.