RigDig privacy and permissions
Draft disclosure, updated November 2, 2026. Not finalized for app-store submission.
Information used
RigDig processes sign-in identity, organization membership, roster names and contact details, qualifications and training documents, physical-training entries, incident coordinates, operational reports, signatures, and user-submitted files. Your organization uses this information for crew readiness, incident reporting, fleet maintenance, and record keeping.
Who can access information
Operational records are shared within your organization according to workspace permissions. Organization administrators manage roster and operational data. Platform operators administer the service. Hosting and authentication are provided by Base44. Browser speech providers and map providers may process requests when you use those features. Files previously uploaded publicly or downloaded and shared outside the app are not protected by later workspace access revocation.
Optional location access
Choosing Use My Location requests a one-time precise location fix to fill a fire report with WGS 84 coordinates, accuracy, and capture time. The location is saved with the report when you save it. No background location tracking is implemented. You can refuse permission and type coordinates instead.
Optional microphone and speech
Voice controls use your browser or device speech-recognition service, which may send audio to its provider for transcription. The app does not implement audio recording storage; transcribed words may become saved report text after your review. Decline microphone access and use typing instead. Avoid speaking information you are not authorized to share with the speech provider.
Files and device controls
Document uploads use files you select with the device picker. No address-book access or continuous camera capture is implemented. You can change microphone and location permissions in your browser or device settings without deleting your account. Native iOS and Android permission declarations still require review against the final packaged app.
Deletion and retention
You may request permanent account and associated personal-data deletion without an active organization membership. Submission revokes workspace access but is not completed deletion. Organization-owner requests require an ownership review without deleting the organization. Incident, signed reports, and audit evidence remain during review; lawful retention grounds and durations must be established by the operator.
Request account and personal-data deletionBefore release
The operator must supply its legal identity, privacy contact, data retention periods, deletion processing deadline, processor inventory, and accurate Apple App Privacy and Google Play Data safety declarations. Platform analytics, cookies, backups, and final native permissions require verification. No claim of store approval or complete policy compliance is made.