Privacy & data
Beaver AI CRM is operated by Beaver Builders PGH LLC. It is a company workspace for invited employees and authorized company staff.
Account and company information
The app stores your account name, email, company memberships, sign-in sessions, and the business records your company adds. These can include employee and customer contact details, service addresses and job content, private messages, attachments, compensation settings, attendance and received-payment or expense records. Owners can access company financial information. Other access is limited by server-enforced company permissions.
Sign-in and devices
Passwords are stored as cryptographic hashes. Passkey private keys remain with your device or passkey provider; the app stores the public credential. Sessions renew as you use the app and expire after seven days of inactivity. Signing out ends the session on that device.
Photos and verification texts
Your personal account photo is stored on your device. Team profile pictures uploaded by authorized administrators are stored privately with company records. If SMS verification is connected and you request a code, your phone number is sent to Twilio to deliver and verify it. Private in-app messages are separate from SMS. Deliberately selected, consent-checked SMS is available only for companies with an enabled sender; invitation email and inbound SMS require their own configuration.
Service addresses and job dispatch
When company administrators activate Google Maps, selected service addresses and units may be sent to Google for lookup or validation. Provider coordinates have an expiry of at most 28 days in a separate temporary cache; expired results are not used for address lookup and become eligible for maintenance removal. Place IDs and explicitly confirmed service-address information are stored for the job. Raw provider responses are not retained. Authenticated tickets hold access directions and internal notes, with internal notes restricted to authorized job administrators. Explicitly selected job tickets may be sent through Twilio Messaging or a connected email service only after sender setup and recorded recipient consent. Job, dispatch and suppression records remain company-scoped. Company replies appear in the app inbox only when the company has connected authenticated inbound messaging. Contact your dispatcher to confirm whether that service is active.
When you open a native Google map, the Maps SDK can process SDK and device identifiers, map interactions and diagnostic information for app functionality and analytics. This is separate from Beaver's stored job records. Service-address map pins are also separate from optional employee device-location sharing. See the Google privacy information linked in our maps notices.
Attendance, pay and on-duty location
Attendance records use server check-in/out times. Jobsite checks use device-reported coordinates, accuracy and time; these are not tamper-proof. Managers may record audited overrides. Optional on-duty sharing requires company permission and your explicit action. It stops when you leave its visible panel or check out. Location is hidden after 15 minutes and becomes eligible for maintenance removal. Live scheduled cleanup requires the worker to run; Sample uses the manual maintenance described below. The app does not continuously track off-duty employees. Compensation rates and approved settlement history are private company records.
Optional active-visit travel sharing
In the native app, you can start a separate travel session for your assigned service visit after granting device location permission. Background permission allows updates while the screen is locked. Local collection stops when you choose arrival or Stop, sign out or change company; server synchronization can require an explicit retry when offline. Revoked or expired sessions cannot upload new fixes. A session lasts at most four hours and never continues past the service day. Only the latest precise fix is retained, replaced by the next fix and eligible for deletion after 15 minutes without updates. Physical removal depends on Live scheduled maintenance or Sample manual maintenance. Offline, denied or force-closed apps may stop updating. No coordinate history or off-duty tracking is requested.
Beaver workdays and internal location
Beaver Builders workday location is a separate internal feature. Start Day and End Day use current assigned-site checks unless the owner saved an explicit individual exemption. With informed consent and device permission, workday sharing can continue with the screen locked during an active day. End Day, Stop Sharing, sign-out, a company change, revoked access or the saved sharing lease stops it. Authorized attendance managers can see only the latest private fix; it is hidden after two minutes and eligible for maintenance removal. No coordinate history is kept or shown on customer links. GPS gaps never deduct pay. Raw presence, reviewed actual attendance, contractual job allocation and immutable payable Closing remain separate. Missing device End can be closed by an authorized recorded review, preserving the missing original End and recording actual time separately. Employee report links require current authenticated report access. Original messages are preserved; dynamic translation is not enabled in this release.
Private customer arrival links
Anyone who has a private arrival link can open its customer summary without signing in. Treat the link as confidential and avoid forwarding it. For eligible newly issued links that still match the current customer and service contact details, an earlier view can show only the company, booked appointment window and its time zone, and when arrival updates may become available. That availability time is not an arrival estimate or a promise that live sharing will be available. After that availability time, the gated summary can show the assigned technician's name, entered vehicle description, appointment and estimated arrival windows, visit stage, reviewed stops ahead and coarse progress. Only those eligible newly issued links may also show the reviewed service location on a Google map, after activation and on the service day. Google Maps receives the service-location coordinates needed to display that map. Point precision is labelled, and the point may be approximate. The map does not show a moving technician or travel route. The summary does not expose precise technician coordinates, other customers' addresses, internal notes or access codes. Phone updates can be stale or unavailable. Scheduled windows, technician estimates and traffic estimates do not guarantee an arrival time.
When created, links are set to expire 24 hours after the appointment end at that time. An approved reschedule does not extend an older link's expiry. Links can be revoked by an authorized company user, including after the visit closes or is cancelled. Changed appointments can make an older link unavailable. Link records include their creation and expiry times, an access count and the last access time. Expired link metadata becomes eligible for maintenance removal one day after expiry. Physical removal depends on maintenance actually running. Revocation removes the link record.
Messages, receipts and notifications
Technicians can choose at sign-in whether to receive work texts and emails. Customers can agree to receive service updates by text, email, or both. Contact details alone do not record permission. Service messages may include appointment confirmations, reminders, arrival updates and invoice links. This workflow does not send marketing. Message frequency varies. Message and data rates may apply. Reply STOP to stop texts, or contact the company to change your preferences.
Company messages, dispatch events, consent/opt-out records and uploaded receipts are stored privately. Push subscriptions belong to your account/device; permission is requested only after a tap. Expo and Apple Push Notification service process notification tokens, device or installation identifiers and notification content to deliver alerts. Alerts can include sender or company names and job or document context; device settings control whether alerts appear on a locked screen. Opening app content requires the relevant account access. A provider accepting a message does not prove delivery or reading.
Company phone
The first App Store version provides authorized call-history metadata; it does not provide outgoing calling or recording playback. The company's separately connected web and preview calling tools use CallTrackingMetrics / Callbox. If you use those tools, the provider processes call metadata and audio, and recording depends on provider settings and notices. Provider-side call history and recordings are managed in that service under the company's configuration and the CTM Privacy Policy. Deleting your Beaver login does not by itself delete those copies.
Optional Tesla connection
Where separately activated, optional Tesla navigation uses an owner-authorized Tesla connection. It remains conditional on credentials, vehicle authorization and reviewed billing; source support does not mean it is enabled for every account. Authorization tokens are encrypted on the server and are never sent to the mobile app. A deliberate destination send shares the saved service address, including its unit, with Tesla; internal notes, access codes and stored Google geometry are excluded. Beaver stores a vehicle VIN and safe command outcomes. Disconnect removes its saved authorization; account deletion removes its private Tesla connection. You can also revoke Beaver through your Tesla account.
Hosting and technical information
The web backend runs on Vercel and stores persistent records in Neon Postgres. These providers process information needed to operate the app, including authenticated requests and technical or security logs that may contain network, session or device information. Google handles selected map and address requests; Twilio handles enabled verification or SMS; Microsoft 365 or SendGrid handles configured email delivery; CallTrackingMetrics / Callbox handles connected phone use; Expo and Apple handle push delivery. Provider logs, diagnostic records and backup copies have separate service and account handling; deleting a Beaver login does not immediately erase every provider copy. Contact the responsible company about requests involving those records.
Sample workspace and maintenance
The separate Sample workspace starts with example records. Use example information for testing; information you enter there can still be personal information. Temporary location or link data can expire or become unavailable before it is physically removed. In Sample, eligible workday and visit location data, arrival-link metadata and expired road results are removed during maintainer-run cleanup. Maintainers run this cleanup after controlled fixture or location checks and before reviewer handoff, after known location-enabled support or test sessions, and for valid privacy or reset requests. This is not a fixed deletion deadline or an automatic reset of accounts and business history.
Maintainers review retained Sample fixtures after app review completes, the Sample cohort is replaced, or a valid removal request is received. Maintained review accounts stay available during active review. Sample maintenance does not change Live records or erase provider logs and backups. Live temporary-data cleanup depends on its scheduled worker running; a visibility or access expiry is separate from physical deletion.
Deleting your account
Successful account deletion removes your sign-in account, saved passkeys, sessions, personal account profile, Team profile, push registration and preferences, current location registrations and private Tesla connection. Company jobs, documents, messages, dispatch and consent/audit records, attendance/workdays, financial records and attachments can remain separately from the sign-in account. Company business records do not automatically expire in this version. This is not a promise that all associated personal information or copies held elsewhere are erased.
You can begin deletion from the app's Account screen. The account-deletion page may ask for a separate website sign-in. Review the account shown and confirm deletion with your password or recent sign-in. Contact the responsible company about access, corrections or retained company records, or email support@beaveraicrm.com. Requests are reviewed against account and company authority, the scope requested and the available correction or removal options. Some issued financial history is protected from direct editing and uses audited corrections. A request does not itself erase all retained records.