Inspectra Privacy Policy
Updated: November 9, 2026
Inspectra connects inspections, AM/PM Line Checks, Issues, Actions and reports across organizations and Sites. This policy describes the app and its public website. Inspectra currently has no subscription, payment or paid-trial system; anyone can try it. Access to an organization’s workspace still requires an approved membership and the appropriate permissions.
Account, organization and work data
- Account name, email, password-verification records, verification and recovery requests, sessions and optional profile picture.
- Organization memberships, join requests and decisions, roles, Site assignments, permissions, ownership and administration records.
- Organization names, logos, report watermarks, optional website addresses, timezone and operating schedules.
- Templates and scoring rules; inspection and Line Check answers, results, dates and managers; Issues, Actions, assignees, comments, mentions, activity and audit records.
- Photos, videos and associated metadata that you choose to upload, together with generated PDFs and report-sharing records.
- Push-notification tokens, delivery records, device/app information, network and security logs such as IP addresses, and error diagnostics needed to operate and protect the service.
Why we use this information
We use it to authenticate accounts, verify requests, approve and enforce organization access, synchronize supported offline work, calculate results, generate reports and deliver workflow, security and service messages. Activity records also determine inactivity reminders and retention eligibility. We use operational diagnostics to investigate failures and prevent misuse. No payment-card information is requested through a subscription or billing flow because the app has no such flow.
Optional biometric login
On a supported device and app installation, you may enable fingerprint, Touch ID or Face ID login after signing in. Your operating system performs biometric verification; Inspectra does not receive or store your fingerprint or facial biometric templates. The app stores a device-login credential in authentication-protected operating-system storage, with account email and credential identifiers kept locally for the saved-account presentation. The server stores a hash of that credential and enrollment/use/revocation records, rather than your biometric data. You can disable biometric login or forget the saved account. Account restrictions and server authorization still apply, and password sign-in remains available.
Device permissions and local storage
Camera, photo/video selection and notifications support the features you choose to use; their availability depends on device permissions. The app keeps organization-scoped records, queued changes, selected/cached files and preferences on your device to support offline work and faster access. Authentication material is managed separately from workspace data. Unsynchronized work has not necessarily reached the server and can be lost if app storage is cleared or the app is removed.
The website stores your light/dark preference in browser local storage when available. The current landing page does not include advertising trackers or marketing analytics. The app’s security and error monitoring is separate from the website’s theme preference.
Access, sharing and service providers
One login can have memberships in multiple organizations, each with separate records, roles and scope. Authorized teammates may see your name, work assignments, contributions and evidence within their permitted scope. Owners manage their organizations; platform administrators provision and administer organizations and account-lifecycle operations. Platform administrator status alone does not grant membership or general access to every workspace.
Authorized template-sharing or platform-copying workflows can copy template structure and scoring configuration to another organization. They do not copy that organization’s users, inspection results, private evidence or work history. A separately copied template can survive deletion of its source organization. Organization name/logo changes can notify members and send a corresponding service email to platform administrators. Report exports and files shared by users can leave Inspectra’s control.
We use hosting/database, email, notification, diagnostic and file-storage services to operate Inspectra. Integrations include Cloudinary and Cloudflare R2 for media/storage, Expo push delivery, Sentry error monitoring and configured email delivery. Media can move between configured storage providers for processing or retention, and superseded copies are queued for cleanup. Provider processing may take place outside your country. The app does not sell personal data or use it for third-party advertising.
Work records and media retention
Retention applies to records and their associated content, not just to attachments. The current standard periods below describe the implemented policy. Inspection/report periods are service-configurable. Eligibility is evaluated by background jobs, so removal is not guaranteed at the exact cutoff time; report protection, shared references, failed cleanup or unavailable services can delay completion.
- Standalone Actions and Issues: 90 days without accepted business activity makes the record eligible for permanent deletion, including its activity and attachments, whether open or closed. A genuine saved change, reassignment, comment or committed media change resets the inactivity period. Viewing, searching, exporting, unsaved edits and replaying unchanged synchronization do not reset it.
- Reminders: open standalone Actions receive a 30-day inactivity reminder to the creator; open Issues to the Reported to person. At 60 days they escalate to the current Owner. If the intended recipient has left or lacks access, the reminder goes to the current Owner. These can be grouped into summaries; a notification does not grant access. Complete/Can’t do Actions and Resolved Issues do not receive these open-work reminders.
- Linked Actions: Issue-linked Actions share the parent Issue’s clock, and activity on any linked Action resets that clock. They are deleted with the eligible Issue, including unfinished Actions. Inspection-linked Actions follow their parent inspection’s separate lifecycle.
- Line Checks: the default retains the creation calendar month, with eligibility from the next month’s start in the organization’s timezone; this is not a rolling 30-day promise.
- Ordinary inspections: the working inspection instance is normally eligible for retirement after three calendar months from creation. Retirement can preserve the accepted historical result, its protected report and qualifying retained video evidence. Historical results have a separate default of 365 days from their retention anchor; retirement safeguards can defer deletion. A report’s omission of images/videos does not mean all underlying evidence has already been erased.
- Combined history PDFs: generated artifacts normally expire after seven days. Artifact expiry does not by itself erase the underlying inspection results. Earlier source deletion or loss of authorized access can make a report unavailable sooner.
Organization suspension blocks workspace access and pauses Action/Issue inactivity clocks, reminders and retention deletion; reactivation resumes their remaining time. Inspection-retention processing also defers while suspended, but its calendar-based age is reassessed after reactivation rather than reset. Accepted permanent organization deletion takes precedence over independent retention.
Leaving, pausing and deleting
Leaving or pausing a membership, or Owner deactivation/removal of that membership, affects that organization’s access and does not delete the shared login or unrelated memberships. Historical workplace contributions may remain subject to the applicable record lifecycle. Owners must transfer ownership before leaving an organization they own. Losing access is different from permanently erasing the organization.
A platform administrator can accept permanent organization deletion after at least 24 hours of continuous suspension and the required confirmations. It removes the organization’s memberships, Sites, settings, branding, templates and work records, including historical results, linked work, associated reports and owned media, subject to safe shared-reference and cleanup checks. Other organizations, independent template copies and shared login accounts are preserved. Deletion is irreversible once accepted and may remain in progress or need attention until storage cleanup succeeds.
Permanent account deletion removes credentials, sessions, tokens, personal notifications, profile data and direct personal attribution. Organization work records may remain under “Deleted user” until their own retention or organization-deletion rules remove them. Account deletion is not a request to erase every organization’s operational history.
Our application-database backups may temporarily contain data from before a deletion. A separate deletion ledger is not included in application-database restores. After a restore, the service remains unavailable until ledger-listed accounts are removed again and the result is verified. The ledger contains opaque account and operation identifiers, integrity evidence, lifecycle version, source, phase, and timestamps; it does not contain the deleted person’s name, email, password, or profile data.
Every user can initiate permanent account deletion in Profile → Delete My Account, or through our secure web request form. Verified requests for the shared account and all its memberships are coordinated by the platform administrator within seven calendar days. Submitting a request does not pause the account. Owners must transfer ownership in every organization before full deletion. An organization Owner can remove only that organization’s membership; this does not delete the shared login or other memberships.
Minimal account/organization deletion receipts, synchronization outcomes and security/operation records have separate retention requirements; they are not all erased with the visible work card. Files you exported or shared, and offline devices that have not reconnected, cannot be remotely erased. The app reconciles applicable local workspace cleanup after verified reconnection; we do not promise an immediate wipe of every device or external copy.
Your choices and requests
You can edit permitted profile fields, add/replace/delete your picture, manage supported notification preferences and device permissions, disable biometric login, and leave or pause eligible memberships in the app. Owners have additional membership, branding and template-sharing controls. For access or correction help, contact your organization Owner or the privacy contact below. For permanent deletion, follow the account deletion instructions; the secure web request is available without installing the app. Do not send a password or biometric data by email.
Changes to this policy
We update this page when Inspectra’s data handling changes and identify the revision date above. Check it before using newly introduced features.
Privacy contact
For privacy questions or requests about your personal data, email muhamedmahmoud11226@gmail.com.