Privacy Policy

ContractorOS helps contractors and project teams organize workspaces, customers, projects, schedules, field updates, photos, files, and related work information. This policy describes the information processed by the current private beta.

Information We Process

Depending on the features you use, ContractorOS may process:

• Account and profile information, such as your email address, name, username, avatar, contact details, bio, authentication records, and profile-sharing choices.
• Business and workspace information, including workspace membership, roles, customers, projects, areas, stages, tasks, schedules, preferred vendors, updates, photos, files, and other content you or your team submit.
• App-usage and diagnostic information that you have approved, such as screen names, platform, app version, timestamps, bounded event metadata, and error information used to operate, secure, and improve the service.
• Information you submit through feedback, support, onboarding, or trade-suggestion features.

Profile Sharing

External profile sharing is off by default. If you explicitly enable it, you can separately choose whether a signed-in external viewer requesting your profile may receive your name, username, bio, email, phone number, or website. Turning external sharing off revokes that consent. Workspace members may still receive limited identity information needed to collaborate, subject to workspace authorization.

The current beta does not provide a customer portal. Marking a project update as customer-visible records the intended future audience but does not by itself create customer access.

Photos, Files, and Device Access

ContractorOS requests camera or photo-library access only when you choose to capture or attach project evidence or update your avatar. It uses the system file picker when you choose project documents. The current Expo product does not request location access for geofenced notifications.

Project media is stored in private cloud storage with authorization checks and scoped object paths. Sharing or downloading a project file is an explicit user action. Files saved to another app or provider are then governed by that destination's settings and policies.

Offline and Local Data

ContractorOS caches workspace data and pending changes locally so supported workflows can continue through a weak or interrupted connection. Native builds use application-scoped SQLite and document storage; the web beta uses browser storage. Pending operations keep visible retry and failure state rather than being silently discarded.

Signing out may retain account-scoped local changes so unsynchronized work is not destroyed without warning. Self-service account deletion removes the signed-in account's local ContractorOS data after the remote deletion plan completes. Removing the app, clearing browser data, or using operating-system storage controls may also remove local copies.

How We Use Information

We use information to provide authentication, workspace collaboration, synchronization, project and schedule management, storage, support, security, diagnostics, and product improvement. ContractorOS does not sell personal information or use account content for behavioral advertising.

Access, Retention, and Deletion

Workspace records are available only through the authorization rules associated with the signed-in account and workspace. If you leave a retained shared workspace, content created for that workspace may remain available to its authorized members.

Self-service account deletion is available. If you own a workspace with other members, you must first transfer ownership or remove those members. ContractorOS warns when unsynchronized changes may be lost and purges account-scoped local data after deletion. Contact us if you need privacy or deletion assistance.

Diagnostics and Feedback

Diagnostic submission is controlled by an in-app preference. ContractorOS uses a bounded event catalog and redaction rules intended to exclude passwords, authentication tokens, email addresses, phone numbers, and internal record identifiers from diagnostic payloads. Feedback may include text and screenshots you deliberately attach.

Data Security

ContractorOS uses authentication, database row-level authorization, private object storage, scoped object paths, secure native authentication storage, and redacted diagnostics to reduce unauthorized access. Offline workspace data also relies on device and browser application isolation. No storage or transmission system can guarantee absolute security.

Beta Access and Payments

The current private beta does not offer a paid App Store, Google Play, or web subscription. ContractorOS will publish updated pricing, payment, and privacy terms before offering a paid plan.

Contact

For privacy questions or deletion assistance, contact craftsmannsoftware@gmail.com.