Privacy Policy
Last updated: November 10, 2026
Crew Rivet ("we," "us," or "our") is operated by Avion LLC, a California limited liability company. This Privacy Policy describes how we collect, use, and share information when you use our platform at crewrivet.com and related services (the "Service").
1. Information We Collect
Information You Provide
- Account Information: Name, email address, phone number, business name, and trade when you create an account.
- Customer Data: Contact information (names, phone numbers, email addresses, addresses) for your customers that you add to the Service.
- Financial Information: Invoice amounts, payment records, line item descriptions, expense records, and receipt photos. Payment processing is handled by Stripe. Card numbers are entered on Stripe's own payment pages, so they go straight to Stripe: we don't receive or store card numbers to take a payment. (If someone reads out or types a card number in a call, text or message, it can end up in that call's transcript or that message like any other content.) If you enable instant payouts via Stripe Connect, Stripe collects your banking information directly — we never access or store your bank account details.
- Communications: Text messages sent and received through the Service, voice notes uploaded for quote and invoice drafting.
Information Collected Automatically
- Usage Data: Pages visited, features used, and actions taken within the Service. On this website, Cloudflare Web Analytics counts page views and visits (page, referring site, browser, operating system, device type, country) without cookies; until October 10, 2026, our self-hosted, cookieless Plausible analytics counted page visits on this website and in the app.
- Device Information: Browser type, operating system, and IP address.
- Message Delivery Data: Delivery status, timestamps, and carrier information for SMS messages sent through the Service.
People We Contact About Crew Rivet
When we run outreach campaigns, we email some trade businesses to tell them about Crew Rivet. We contact these businesses by email only; we do not call them, text them, send them direct messages or use their website contact forms. For this, we collect information from public sources: Google Maps (through Google's Places API, which receives the search text we send, such as a trade and city or a business's name and city), business websites, public web search, and public social media groups and pages. This can include the business name, trade, address and city, business phone number and email address, website, Google rating and review count, other details from its Google listing (its business hours, business status, business types or categories, number of photos and Google's place ID), details its website lists (such as its services and, when the website names them, the owner's first name), and our notes about the business, such as our estimate of its size. We also keep a record of the emails we send and of any replies. Our emails can mention details such as the business's Google review count. We use this information to contact the business about Crew Rivet and to check, before we email, that the address can receive mail. We share it with Google (the Places API searches described above), MillionVerifier (which checked email addresses from August 1 to October 22, 2026), Google Workspace (our outreach mailbox, which sends our emails and receives replies), Backblaze (encrypted backup storage in the United States), Hetzner (which hosts our server in Germany), Telegram (where we get a short alert with the business's name, email address, city, trade and type of reply when someone replies or an email bounces, and the address and the mail server's error when an email fails to send) and Anthropic (Claude), which, under its commercial terms, read the text of business homepages through its API (using Claude Haiku, from about August 4 to 6, 2026) to categorize businesses, including estimating their size, and which our staff used under its consumer terms until October 24, 2026 to help prepare our emails (see “Past third parties”). We store these records on our second server, in Germany, and keep lead lists and draft emails (including business phone numbers and email addresses) in working files on our computers in the United States. To stop our emails, reply to any of them from the address we emailed (for example, with “unsubscribe”). When we process a reply, we stop the sequence and add the address to our do-not-contact list, which we keep permanently so that we do not email it again; if you still get email from us, write to privacy@crewrivet.com. We keep these records while we may still use them for outreach and to keep our do-not-contact list accurate. Once we process your opt-out (a reply we match to the address we emailed, or a message to privacy@crewrivet.com), we stop contacting you and keep your address on a permanent do-not-contact list so that we do not email you again. If you ask, we delete the other records we hold and ask the providers that process them for us to do the same, except the do-not-contact entry, which we keep to honor your opt-out (Cal. Civ. Code §1798.105(d)). Copies already sent to others can't always be recalled: for example, information our staff gave Anthropic's Claude under its consumer terms until October 24, 2026 (see “Past third parties”), and copies in our email and alert history until they are deleted. Deleted records can remain in our encrypted backups until those expire: about a week on our server in Germany and up to about 7 months in Backblaze B2 (United States, US-East). We may keep copies longer where needed for legal or security-incident purposes.
2. How We Use Your Information
- To provide, maintain, and improve the Service.
- To send SMS messages, invoices, quotes, reminders, and review requests on your behalf to your customers.
- To process payments through our payment processor (Stripe).
- To classify inbound messages using AI to route them appropriately.
- To draft quotes, invoices and summaries with AI, and — when you turn these features on — to answer your customers' calls (AI receptionist) and website chats with AI.
- To transcribe voice notes for quote and invoice drafting.
- To send you account notifications and support communications.
- To send account owners product emails — getting-started tips, trial reminders, milestones, payment-setup reminders and the weekly Business Report (you can turn these off in Settings or with the unsubscribe link).
- To monitor service health and prevent fraud or abuse.
3. How We Share Your Information
Since October 24, 2026, we do not sell or share personal information (as the California Consumer Privacy Act defines those terms). In the 12 months before that, some of our disclosures may have counted as selling or sharing under those definitions: the advertising and analytics trackers described under “Past trackers” below (Meta and Google), Google's Gemini API if it was configured (until August 2, 2026), and our use of Anthropic's Claude under its consumer terms until October 24, 2026, by our staff, our engineering agent, our ops routine, our automated operations job and our automated support triage (see “Past third parties” below). We share, or in the past 12 months shared, information only with:
- Vendors (service providers, subprocessors and some vendors used under their standard terms): providers that process information to perform services for us, under their data-processing or service terms or, for some vendors, their standard terms. We use or used some of them under their standard terms of service, not under a data processing agreement with us, including the public map, weather, QR-code, font and script services, Google's Places API (our outreach searches), browser push services, the internal-alert services Telegram and Discord (Discord until October 22, 2026), GitHub (error-report issues, and our support triage until October 24, 2026), FormSubmit (our website contact form until October 1, 2026) and Sentry (our API error monitoring until October 2, 2026, and possibly our app's, on its server and in the browser). Because we have no data processing agreement with these vendors, they may count as third parties rather than service providers under California law; we disclose information to them only for the business purposes their entries describe (such as alerts, maps, weather, outreach searches (Google Places), QR codes, fonts and scripts, push notifications, error reports and support handling), not for sale or cross-context behavioral advertising. They receive the categories listed in their entries, including identifiers (such as IP addresses, names, email addresses and phone numbers), geolocation (job-site addresses and coordinates, and the map area shown), internet activity (browser details, and page and referring addresses), the content of alerts, messages and contact-form submissions, commercial and professional details in alerts (invoice numbers and amounts, payment and account IDs, and team members' names and certification expiry dates), and error reports. These include: Stripe (payments and payouts), Telnyx (SMS and voice, including the AI receptionist), Resend (transactional and notification email), GitHub (private issues for repeated errors, which can quote the error text, and, from July 24 until October 24, 2026, our support triage described under “Past third parties” below), Chatwoot (website support chat, self-hosted by us), browser push services (Google, Apple, Mozilla) for push notifications, map geocoding, map and weather services for dispatch, routing and the customer tracking page (OpenStreetMap Nominatim and map tiles, unpkg, Open-Meteo), Google Fonts (past: the app's fonts from June 29 to November 6, 2026, and this website's fonts from June 28 to August 22, 2026; it saw your IP address), goQR.me (QR-code images for marketing links, which sees the viewer's IP address and the link), Hetzner (cloud hosting and infrastructure), Backblaze B2 (encrypted off-site backup storage), Cloudflare (content delivery, DNS, TLS and bot protection, including Turnstile, and analytics for this website with Cloudflare Web Analytics), PostHog (product analytics in the app: usage events and page views; page addresses (URLs), which since October 25, 2026 we send without query strings or fragments (until then they included the query string, which on the password-reset page included your email address and on search pages could include search terms you typed, such as a customer's name or phone number, and included the one-time code in team-invite links (these expire after 7 days)); until October 25, 2026, page titles, which on some pages included a contact's name, the title of a job, an invoice or quote number, or an inventory item name (we no longer send page titles); device/session metadata; IP address; your account ID and account details (trade, plan, subscription status, demo-account flag, your role and the account's sign-up date); and, when you subscribe, your subscription ID and plan), MillionVerifier (checking the email addresses of businesses we contact about Crew Rivet, from August 1 to October 22, 2026, under MillionVerifier's data processing agreement, which forms part of its terms of service; run by GBD Software as a Service (Hungary) until Southern Vector Limited (New Zealand) took over the business, current agreement published October 19, 2026), Google Workspace (our outreach mailbox), Google's Places API (the search text we send to find businesses we contact about Crew Rivet, such as a trade and city or a business's name and city), and, for our internal team alerts, our own Cloudflare Workers relay, Telegram and our Google Workspace email inbox (Discord until October 22, 2026; that history was deleted on October 23, 2026). Errors are reported to GlitchTip, an error monitor we host ourselves; until October 2, 2026, our API's error reports went to Sentry (Functional Software, Inc., United States); we cannot confirm whether our app (its server and the in-browser app) also sent error reports to Sentry before it moved to GlitchTip; if it did, those reports had the same kinds of details and, from the browser, the visitor's IP address and the page address. If you connect an integration, the data you sync is shared with that provider: QuickBooks Online (new connections are paused for maintenance) or Xero for customers and invoices, Google Calendar for your jobs (title, time, customer name, address and notes). Xero and Google Calendar sync one way, from Crew Rivet to them. A full list, including past providers, is on our Subprocessors page.
- AI Providers: most AI features use Anthropic (Claude) first — drafting quotes and invoices from voice notes or typed notes, voicemail summaries (the transcript and the caller's phone number), neighborhood marketing suggestions (the job's address), the in-app help chat, and marketing advice (your marketing channels' spend, revenue, leads and jobs). If Claude is unavailable, our own self-hosted models take over; these features never fall back to Groq. Groq is the first choice for reading text from document photos, review-reply drafts (which include the customer's name) and forecast summaries, and reads photos our own model can't; Claude reads a photo quote only when neither can. For quality review, we send Anthropic receptionist call transcripts, after we remove the phone numbers, addresses, email addresses and card numbers we detect (names a caller mentions may remain). From about August 4 to 6, 2026, Claude (Claude Haiku) also assessed the homepage of businesses we contact about Crew Rivet (the business name, trade, city, the kind of email address it uses and its homepage text) to categorize them and returned an estimate of each business's size. Speech-to-text runs on our own Whisper server first, with Groq as the backup. Classifying the messages your customers send you, and the AI chat widget you can add to your own website for your customers, run only on our own self-hosted models. For these features, we use Anthropic and Groq under their commercial terms, under which your data is not used to train their models. The live phone receptionist is powered by Telnyx's voice-AI platform (including Deepgram speech-to-text), which processes the call audio and transcript in real time to understand and respond to callers. Until August 2, 2026, our code could also use Google's Gemini API as a backup for these features; we have no record that it was turned on in production (see “Past third parties” below).
- Past third parties: these recipients received, or may have received, information under their own terms, which let them use it for their own purposes, so for these uses they were third parties, not our service providers. Anthropic (Claude under its consumer terms, until October 24, 2026): Until October 24, 2026, our staff used Anthropic's Claude, and an automated engineering agent (Claude) worked on issues in our private GitHub repository (including error-report issues), to operate, support, debug and market the service (including preparing emails to businesses we contact about Crew Rivet). From July 24 until October 24, 2026, an automated job also had Claude classify the messages sent to our support team (email to support@crewrivet.com, including website contact-form messages, and messages in our website support chat, which is separate from the AI chat widget above). From May 17 until October 10, 2026, a scheduled Claude routine in Anthropic's cloud (our ops routine) also ran every 6 hours on that subscription account, read the error details of our automation server (n8n) and reported to us on Telegram; those errors could include details of the data the automations processed (such as support, contact-form or outreach messages and email addresses). From June 14 until October 24, 2026, an automated operations job, a daily health check of one of our servers (our second server, in Germany), also had Claude read files and system and service logs on that server and send its report to us on Telegram; those files and logs could include information about you (such as IP addresses, account email addresses, phone numbers or message metadata). These uses ran on a Claude subscription account, so Anthropic's consumer terms applied to them, not its commercial terms: they allow Anthropic to use the content to improve its services and develop other products, and to train its models unless training is turned off in the account's settings, and even then for content flagged for safety review or submitted as feedback (such as a thumbs-up or thumbs-down rating). We verified that training was turned off on October 24, 2026; we cannot confirm the setting before then. Anthropic could receive what our staff or the engineering agent worked with, which could include, among other things, contractors' account information (such as names, email addresses, phone numbers, and business and billing details), records contractors keep about their customers (such as names, contact details, addresses, and job and invoice details), text messages and call records or transcripts, team members' details (such as names, contact details, and time and location records), support messages and error reports; for the support triage, the message (an email's subject and text, up to 8,000 characters, or the chat message, which can contain anything the sender writes); and, for issues handed to our engineering agent, the whole issue, including the sender's email address and the account summary described on our Subprocessors page; for the operations job, the files and log lines it read on that server; for the ops routine, the automation error details it read; and, about businesses we contact about Crew Rivet, their contact details, trade, public business listing details (such as address, rating, review count, business hours, business status and business types), our estimate of the business's size (an inference), the emails we drafted to them and their replies. On October 24, 2026, our automated support triage stopped sending messages to Anthropic, we stopped our automated operations job and turned off our engineering agent, and our staff stopped using that account with customer information, support messages or information about businesses we contact about Crew Rivet (their contact details, trade, public business listing details, our estimate of the business's size, our draft emails to them and their replies); we had retired our ops routine on October 10, 2026. Google (Gemini API), until August 2, 2026: a backup AI in our code for classifying messages, drafting quotes and invoices, and reading photos, used only if it was configured. We have no record that it was configured in production; if it was, it may have received those messages, notes and photos under terms that let Google use them to improve its products. Meta and Google (past trackers): described under “Past trackers” below.
- Past trackers: from May 25 to June 26, 2026, every page of our marketing website loaded the Meta (Facebook) Pixel and Google Analytics, with no consent step. They received the pages you visited, clicks on our sign-up and demo buttons, your IP address, browser and device details, and their cookie identifiers; Meta uses this kind of data for advertising. From June 5 to July 6, 2026, the app loaded the Meta Pixel on the screen shown after sign-up, to report the completed sign-up to Meta. After that, until July 10, 2026, our code could load the Meta Pixel on our website (from July 5: page views and pricing views) and in the app (from July 6: sign-ups and checkout starts) only if a pixel ID was configured; we have no record that one was, so Meta may have received this data in that period. From July 5 to July 10, 2026, our code could also send Meta a server-side “Subscribe” conversion event (the subscriber's email address, hashed with SHA-256, the plan's price and an ID derived from the subscription or customer) when a subscription checkout completed, only if Meta Conversions API credentials were configured; we have no record that they were. From June 5 to October 4, 2026, the app sent sign-up events to Google Analytics to measure our advertising: on the screen shown after sign-up it loaded Google Analytics, which recorded the sign-up and page view, could keep recording page views and engagement in that browser session, and set its _ga cookie. Until September 11, 2026 this had no consent step; from September 11, 2026 it ran only with analytics consent (prior opt-in in the EU/UK; elsewhere unless you declined analytics or your browser sent a Global Privacy Control signal). None of these trackers is used today.
- Past AI voice tests: on May 23, 2026, while we were testing the AI receptionist, our code briefly sent the text of the receptionist's spoken replies, which can repeat what a caller said (such as a name or address), to ElevenLabs (if it was configured) and then to Microsoft's Edge text-to-speech service, to turn it into audio.
- Independent Third Parties: our payment processor (Stripe) and consumer-financing partners (Wisetack or Hearth, if you enable financing) act as independent controllers of information you or your customers provide directly to them, and their use of that data is governed by their own privacy policies. Financing is a link only: it carries the amount (and, for Wisetack, an invoice or quote reference), and we do not receive or store your customer's application.
- Your Customers: When you use the Service to send invoices, quotes, reminders, or review requests, your business information is shared with the recipients.
- Legal Requirements: When required by law, subpoena, or to protect our rights.
A current list of our subprocessors is available on our Subprocessors page, or on request at privacy@crewrivet.com.
4. SMS/Messaging Consent
When you use Crew Rivet to send messages to your customers:
- You are responsible for obtaining proper consent from your customers before sending them messages through the Service.
- Recipients can opt out at any time by replying STOP to any message. We automatically process opt-outs and cease all messaging to that number.
- We comply with TCPA, CTIA, and carrier guidelines for SMS messaging.
- Mobile information is never sold or shared for marketing. Crew Rivet (Avion LLC) does not sell, share, or transfer mobile phone numbers, SMS opt-in, or consent — whether collected by us for our own messages or by a business using the Service — to any third party or affiliate for their own marketing or promotional purposes. Mobile opt-in information is used solely to deliver the messages the recipient agreed to receive.
- Message frequency varies based on the sequences you configure (e.g., invoice reminders, review requests).
- Standard message and data rates may apply to recipients.
5. Data Retention
- Account data is retained while your account is active. If you cancel or your free trial ends, your account data is kept until you request deletion; items with their own schedule (such as recordings, transcripts and GPS pings) keep expiring on that schedule. A deletion request locks the account right away and erases it within 30 days; backups age out within about 30 days after that. Invoices you send your customers are your own business records: export them first, because they are erased with the account. Crew Rivet's own billing records for your subscription are kept for 7 years for tax purposes. Proof of messaging and recording consent (including, for consent given on a business's opt-in page on Crew Rivet or a quote-scheduling page, the consent wording shown) and monthly audit-log archives are kept for up to 7 years to comply with law and defend legal claims.
- Backups: encrypted offsite copies of the database and stored files (recordings, photos, e-signatures) are kept about 30 days in Backblaze (US-East); local copies on our app server about 28 days, protected like the live data. Encrypted backups of our outreach records stay on our server in Germany for about a week and in Backblaze B2 (United States, US-East) for up to about 7 months.
- Message records are retained for the life of your account and are deleted when you delete your account.
- Call recordings, call and voicemail transcripts, and the caller's name and address captured by the AI receptionist are retained for up to 90 days — per your recording-retention setting of 30, 60, or 90 days — then automatically deleted, including the copies in your conversation thread, owner summary texts and in-app notifications. What the caller asked for (the service, timing and job details) stays with the lead record, and the caller's name and number on their contact record and any job booked are kept as part of your customer records. Copies already delivered to your phone or email are outside our control. Basic call-log entries (caller number, date, and duration) are kept as part of your account records until you delete your account.
- Audit logs are kept for 90 days in the live system; an encrypted monthly archive that cannot be altered is kept offsite for 7 years.
- Business phone numbers we provision for you are kept while your plan or free trial is active. If it ends, they are released at least 30 days later, after two email warnings to the account owner, unless you choose a plan before then; a released number cannot be recovered.
- If you are an account holder (a contractor), the account owner can export the account's data or permanently delete the account at any time from Settings in the app, or by contacting us. The export is a ZIP with your data and files: a spreadsheet for each part of your account with every record (no limit), plus the files stored with it (call recordings, voicemails, voice notes, photos, e-signatures and receipts). A README inside lists what is left out on purpose (passwords and other sign-in or connection secrets, private link codes, payment and phone-carrier reference numbers, and our internal logs); for anything else, email privacy@crewrivet.com and we will provide it within 30 days. If you are a homeowner or customer of a contractor who uses CrewRivet, see “Your Rights” below.
6. Cookies
We use cookies and similar technologies to:
- Essential Cookies: Maintain your login session and remember your preferences (theme, language). These are required for the Service to function.
- Support Chat (Functional): Our live-chat widget — self-hosted Chatwoot at chat.aviontechs.com — sets a first-party cookie so a support conversation stays continuous as you move between pages or come back later. It is used only to run the chat you start, never for advertising or cross-site tracking.
- Analytics: Within the app, we use privacy-respecting product analytics (PostHog,
which stores a
ph_*identifier that is removed if you opt out, and records usage events and page views; page addresses (URLs), which since October 25, 2026 we send without query strings or fragments (until then they included the query string, which on the password-reset page included your email address and on search pages could include search terms you typed, such as a customer's name or phone number, and included the one-time code in team-invite links (these expire after 7 days)); until October 25, 2026, page titles, which on some pages included a contact's name, the title of a job, an invoice or quote number, or an inventory item name (we no longer send page titles); device/session metadata; IP address; your account ID and account details (trade, plan, subscription status, demo-account flag, your role and the account's sign-up date); and, when you subscribe, your subscription ID and plan) and error monitoring to understand how the Service is used and to fix problems. PostHog session replay was never turned on, so no session replays were ever recorded; since October 25, 2026 replay is also disabled in our code. On this website we count page views and visits with Cloudflare Web Analytics, which uses no cookies or other storage in your browser and is not affected by the opt-out; when you sign up, we save the campaign link (UTM tags) you arrived from with your account. Until October 10, 2026 we counted page visits and sign-ups by campaign on this website and in the app with our self-hosted, cookieless Plausible analytics. We do not use Google Analytics (we did until October 4, 2026; see Section 3). Product analytics in the app is optional — we honor a Global Privacy Control (GPC) signal and ask for your consent where required, and you can decline it without affecting your ability to use the Service. - Customer portal: when your customers sign in to their portal, a
cr_portalcookie keeps them signed in for 7 days (used only on the portal). - No advertising trackers: Our marketing website (crewrivet.com) ships no advertising or third-party ad-tracking cookies — no Meta (Facebook) pixel, and no Google Analytics (its traffic analytics, Cloudflare Web Analytics, use no cookies). It loaded both from May 25 to June 26, 2026 (see “Past trackers” in Section 3). We do not sell your data, and we do not run cross-site behavioral advertising or profile you across unrelated websites.
Browser storage on this website: we remember your theme (cr_theme) and which version of the homepage you were shown (cr_ab_hero) in your
browser's local storage, and — for the current visit only — the campaign link you arrived
from and whether you have already seen our sign-up pop-up. None of it identifies you. The
campaign tags, any referral code and the homepage version are added to our sign-up links;
if you create an account, the campaign you came from is saved with it, while the homepage
version is not saved with it (until October 10, 2026 it was counted in Plausible).
Disabling essential cookies may affect your ability to use the Service.
7. Data Security
We implement industry-standard security measures including:
- Encryption in transit (TLS/HTTPS).
- The database runs on the same server as the app, is not exposed to the internet, and its connections never leave that machine.
- Row-level security for multi-tenant data isolation.
- Bcrypt password hashing (cost factor 12) with per-user salts.
- Webhook signature verification for all inbound events.
- Daily backups, plus continuous database archiving, encrypted before they leave the server and stored in Backblaze B2 (US-East).
8. Your Rights
Depending on your jurisdiction, you may have the right to:
- Access the personal information we hold about you.
- Request correction of inaccurate information.
- Request deletion of your information.
- Export your data in a portable format.
- Opt out of certain data processing activities.
9. Location Data
For users of the crew tracking feature, we collect GPS location data:
- Location is collected only during active work sessions when tracking is enabled by the account owner.
- Location data is used for dispatch, route optimization, and customer-facing technician tracking: a tracking link shows your customer the job and the assigned team member's name, and — only after that team member taps "On my way", until they arrive — their live location (positions sent after "On my way" only). The link expires 12 hours after "On my way", or at the end of the scheduled day if "On my way" is never sent. The tracking page loads map images from OpenStreetMap and its map library from unpkg, which see the viewer's IP address and the map area shown.
- Continuous location-tracking data (the real-time position updates recorded while a worker is clocked in) is retained for 30 days, then automatically deleted. A single location captured at a clock-in or clock-out is kept as part of that timesheet and job record, for as long as the job record is retained, so it can be used to verify the visit later.
- Employees and contractors can see when tracking is active via the Service interface.
- Account owners are responsible for informing their workers about location tracking and obtaining any required consent.
10. Voice & Call Recording
Crew Rivet includes optional voice features — voice notes for AI quote generation and, where you enable it, an AI voice receptionist and call recording.
- When the AI receptionist talks with a caller, the call begins by telling them they are speaking with a virtual assistant, followed by a notice that the call may be recorded (if you record calls) or may be monitored or transcribed; every such caller hears it, wherever they are calling from. Before a voicemail is recorded (in voicemail mode, when your plan's receptionist minutes run out, or from the call menu), callers hear that the call may be recorded, and calls forwarded to you are recorded only after a recording notice plays.
- Call recordings are stored securely and retained for up to 90 days — per your recording-retention setting of 30, 60, or 90 days — then automatically deleted along with the call transcript and the caller's name and address the AI receptionist captured (Section 5 lists exactly what is kept).
- Voice notes for AI quotes and invoices are transcribed; a quote's transcript is removed on the same schedule as call recordings, and the audio recordings are kept until you delete your account.
- The AI receptionist and the AI chat widget on your website talk with your customers without approving each message; AI drafts (quotes, invoices, review replies) are presented to you for review before anything is sent. Missed-call text-backs and new-lead auto-replies (the latter only to callers who agreed to texts) are fixed template texts (not AI-written) sent automatically by default; for returning callers you can switch the text-back to review-first or off. If auto-booking is on, the receptionist books the job and sends the confirmation.
- We do not extract voiceprints or use voice data for biometric identification. We comply with the Illinois Biometric Information Privacy Act (BIPA).
Two-party consent states (all parties must consent to recording): California, Connecticut, Delaware, Florida, Illinois, Maryland, Massachusetts, Michigan, Montana, Nevada, New Hampshire, Oregon, Pennsylvania, and Washington — and any other state that requires all-party consent. If your business operates in — or places or receives calls to or from customers in — these states, you must enable recording disclosures. Crew Rivet provides configurable pre-call announcements for compliance, but you are responsible for determining which state's laws apply based on the location of both parties.
11. California Privacy Rights (CCPA/CPRA)
If you are a California resident, you have the following rights under the California Consumer Privacy Act, as amended by the California Privacy Rights Act:
Categories of Personal Information We Collect
- Identifiers: Name, email, phone number, IP address.
- Customer Records (Cal. Civ. Code 1798.80(e)): Name, address, phone number.
- Commercial Information: Transaction records, subscription data, invoice and quote history.
- Internet/Electronic Activity: Pages visited, features used, interactions with the Service.
- Geolocation Data: GPS coordinates from crew tracking (when enabled), and job-site addresses and coordinates you enter, and the map area shown (your browser loads map images from the map-tile provider).
- Professional/Employment Information: Job title, business name, trade, team members' certifications and their expiry dates.
- Audio, Electronic, and Visual Information: Voice call recordings (when call recording is enabled with consent), voice note recordings for AI quote generation, job photos (before/during/after), receipt photos, and digital signatures captured on quotes.
- Inferences and AI-Generated Data: AI-generated content including drafted invoices, quotes, chat responses, and message classifications. For businesses we contact about Crew Rivet, our estimate of the business's size and the AI categorization of their public homepage.
- Sensitive Personal Information (CPRA): Account login credentials, precise geolocation (GPS), contents of communications (SMS messages, call recordings), and payment information from Stripe (payment status and account IDs, not card or bank account numbers).
- Business-prospect information: for businesses we contact about Crew Rivet, business contact details, public business details, our estimate of the business's size (an inference) and our emails with them (see “People We Contact About Crew Rivet”).
Your CCPA Rights
- Right to Know: Request what personal information we collect, use, disclose, and the sources and purposes of collection.
- Right to Delete: Request deletion of your personal information, subject to certain legal exceptions.
- Right to Correct: Request correction of inaccurate personal information.
- Right to Opt Out: Opt out of the sale or sharing of personal information. Since October 24, 2026, we do not sell or share your personal information, and our website and app run no advertising pixels or ad-tracking cookies, so there is currently nothing to opt out of. Section 3 describes the 12 months before that. You can still send us an opt-out request, and we will honor it.
- Right to Limit: Limit use of sensitive personal information (such as precise geolocation) to what is necessary to provide the Service.
- Right to Non-Discrimination: We will not deny you the Service, charge different prices, or provide a different quality of service for exercising your rights.
How to Exercise Your Rights
Submit a request by emailing privacy@crewrivet.com with the subject line "CCPA Request." We will verify your identity and respond within 45 days (with a possible 45-day extension if needed).
For homeowners and customers of a contractor: If you are a customer of a contractor who uses CrewRivet and want to exercise rights over data a contractor stored about you, please contact that contractor directly. The contractor is the data controller for that information; CrewRivet acts as their service provider (processor) and will assist the contractor in fulfilling your request.
12. Do Not Sell or Share My Personal Information
Since October 24, 2026, Avion LLC does not sell your personal information or share it for cross-context behavioral advertising. Our website and app run no advertising cookies or tracking pixels (no Meta/Facebook pixel, no Google Analytics); Section 3 describes the trackers they ran, Google's Gemini API (if it was configured), and our use of Anthropic's Claude under its consumer terms by our staff, our engineering agent, our ops routine, our operations job and our support triage, in the 12 months before that. The categories involved in those disclosures included identifiers (such as names, email addresses, phone numbers, IP addresses and cookie identifiers), internet activity (such as pages visited, clicks and sign-up events), the content of support messages, commercial information (such as account, subscription, billing and invoice details), information contractors keep about their customers (such as names, contact details, addresses, job and invoice details, text messages and call records or transcripts), information about contractors' team members (such as names, contact details, and time and location records), error reports, files and log lines from our server, and information about businesses we contact about Crew Rivet: their contact details, trade, public business listing details (such as address, rating, review count, business hours, business status and business types), our estimate of the business's size (an inference), the AI categorization of their public homepage, and our emails with them and their replies. Most of the providers in Section 3 receive information to provide their services to us under a data processing agreement or service terms; the vendors we use or used under their standard terms, without a data processing agreement, may count as third parties rather than service providers under California law and receive information only for the business purposes Section 3 lists; and the past recipients Section 3 lists as third parties were not our service providers.
13. Data Processing Responsibilities
When you use the Service to collect and manage information about your customers, employees, and contractors:
- You are the data controller for that information. CrewRivet processes it on your behalf.
- Before October 24, 2026, some of that information may have been seen by Anthropic under its consumer terms, as described in Section 3.
- You are responsible for providing privacy notices to your end users about how their data is used.
- You are responsible for obtaining any required consents for data collection through the Service.
- We will cooperate with you in responding to data subject requests from your end users.
14. Children's Privacy
The Service is not directed to individuals under 13. We do not knowingly collect information from children under 13. If we learn we have collected such information, we will delete it promptly. Contact us at privacy@crewrivet.com if you believe a child has provided us with personal information.
15. International Users & Data Location
Our app and database are hosted by Hetzner in Hillsboro, Oregon (United States), and our encrypted backups are stored in the United States by Backblaze B2. A second server we run in Nuremberg, Germany handles error monitoring, website analytics (until October 10, 2026), website support chat, speech-to-text, document text recognition and our automations (including outreach to businesses), so error reports, page-visit counts, support chats, outreach records, and audio and document images being transcribed or read are transferred to Germany. Our subprocessors (for example Stripe, Telnyx, Resend, Anthropic and Groq) process data in the United States or wherever they operate. By using the Service, you consent to such transfers. Businesses we contact about Crew Rivet do not use the Service; for their outreach records, this section describes where those records are transferred.
16. Changes to This Policy
We may update this Privacy Policy from time to time. For material changes, we will provide at least 30 days' notice via email or in-app notification. The "Last updated" date at the top indicates when changes were last made.
17. Contact Us
If you have questions about this Privacy Policy or your data, contact us at:
Avion LLC
Email: privacy@crewrivet.com
For CCPA requests: email privacy@crewrivet.com with subject "CCPA Request"
Website: crewrivet.com