Privacy Policy
What CrewCommander receives, why we use it, and how to request your records.
CrewCommander is operated by Albert’s Road Service LLC. For beta support and privacy requests, email albertsroadservice@gmail.com.
1. Information we handle
We handle account details such as names, email addresses, company information, roles and subscription status. Businesses enter customer and contact details, multiple service locations, purchase orders, payment terms, asset history, estimates, jobs, notes, time entries, photos, signatures, invoices, inventory and payment records. They may import customer, asset and pricebook data from CSV. We also receive the technical information needed to keep sessions secure, diagnose errors and understand how the service is used.
2. How we use it
We use this information to authenticate users, keep each business's records separate, run its field-service workflow, deliver requested messages and documents, send estimate, invoice, receipt and reminder emails, process subscriptions and supported payments, respond to support requests, protect the service and improve its reliability. We do not use one business's private customer records as another business's data.
3. Service providers and connected features
Supabase hosts authentication, database and file storage; Vercel hosts the web app; Stripe handles subscription billing; customer invoice payments are recorded by the shop in this beta. Existing connected-account records are retained for payment history and reconciliation. Inngest runs background work; and Resend delivers service email. Sentry and PostHog may receive diagnostic or product-use events. Mapbox may process location data for map views, and NHTSA may receive a vehicle VIN when lookup is used. SMS, QuickBooks sync, native/offline workflows and AI capture are disabled in this beta; CrewCommander will not send their data to Twilio, Intuit or OpenAI for those workflows. Provider privacy notices also apply when a provider is used.
4. Payments
Stripe processes payment credentials for CrewCommander subscriptions. Online card and ACH customer invoice payments are not included in this beta; previously processed connected-account payments remain in the audit history. CrewCommander does not store full card or bank credentials. It stores provider identifiers, statuses, amounts and ledger history needed to show and reconcile payments, refunds and returns. A business can see payment information relevant to its own invoices and account.
5. Team access and customer records
The business that creates a CrewCommander account controls which people it invites and what roles they receive. Access to its records is limited by company membership and role. Its customers may receive hosted estimate, invoice, receipt or portal links when the related workflow is used. Businesses are responsible for the data they enter and for obtaining any permissions required for their customer communications.
6. Location, camera and offline data
The web app may use a browser's location or camera when you grant permission. This beta does not include a native mobile app or offline work storage. You can change browser permissions in your device settings; disabling location or camera access may limit the related web feature.
7. Retention and account closure
An owner can request an export and close a company account. Operational personal information and files remain recoverable for 30 days after closure. At the end of that window, eligible data is reviewed for removal; it is not automatically deleted. Financial and audit records, required linked records, backups and information subject to a legal or dispute hold may be retained longer. We will not describe a requested deletion as complete while records remain under a hold or in another unresolved location.
8. Cookies and local storage
The web app uses session cookies to keep users signed in. It may keep a submitted correction request and its reason in this browser tab's session storage until the result is confirmed or the tab session ends. Diagnostics and product-use tools may use identifiers to measure errors and service use. Browser and device settings provide controls for cookies, local storage and permissions; blocking required storage can prevent sign-in or use of saved correction requests.
9. Access, correction and questions
Company owners can review and export supported records in the app. For help accessing or correcting data, requesting closure or asking about retained records, email albertsroadservice@gmail.com. We may need to verify your identity and company authority before acting on a request. We will update this page and give notice when a material change to these practices takes effect.