Legal
Sub-Processor List
These are the companies that process customer data for HoneyRuns. Riggs reads telematics, texts drivers and shops, books service, and reads shop invoices into service history. Each company below handles one part of that work.
For each one we list what it does, the customer data it touches, and where it processes that data.
Current sub-processors
| Company | Where data is processed | What it does and the data it touches |
|---|---|---|
| Supabase | United States (Northern Virginia) | Database Our main database, sign-in and file storage. Data: all customer data in HoneyRuns, including accounts and users, vehicles and telematics readings, service history, runs, contacts, messages, and uploaded invoices and files. |
| Amazon Web Services (AWS) | United States (Northern Virginia) | Hosting and backup Application hosting and encrypted file backups. Data: customer data processed by the application, application logs, and backup copies of files. |
| Railway (transition) | United States (US West, California) | Legacy portal hosting Some existing customer-branded portals remain here until their domain migration is complete. Data: traffic and data processed by those portals. Ask us to confirm the status of your portal. |
| Cloudflare | Global network | Hosting and network protection Web hosting, content delivery and network protection. Data: web and API traffic, including what users send to and see in the app, and data processed when serving application pages. |
| OpenRouter | Ask us | AI routing Routes AI requests to the model providers listed below. Retention and data-use terms depend on the provider and endpoint. Contact us to review the terms for your workflow. Data: what each request carries, such as Riggs conversations, fleet and vehicle records, contact names and phone numbers, message content, and invoices and estimates. |
| Anthropic | Ask us | AI model AI processing for Riggs conversations and tasks, through OpenRouter. Data: Riggs conversations, plus the fleet records, contacts and messages Riggs reads to do its work. |
| Google (Gemini) | Ask us | AI model Document processing, summaries and Riggs conversations, through OpenRouter. Data: invoice and estimate files and their line items, vehicle details, run notes, Riggs conversations, contacts and messages. |
| Perplexity | Ask us | AI search Answers Riggs's web searches for facts that live outside HoneyRuns. Requests reach Perplexity through OpenRouter. Data: search questions only. We apply pattern-based filtering for phone numbers, email addresses and VINs before a search leaves HoneyRuns. This does not reliably remove names or every identifying detail. |
| Telnyx | Ask us | Phone and SMS Texts and calls with drivers, shops and vendors, including voicemail. When Riggs calls a shop, the call runs on a Telnyx voice assistant, which Telnyx runs with an OpenAI model and Deepgram speech recognition. Data: phone numbers and names, message text, call audio, call recordings and transcripts. |
| Resend | United States (Northern Virginia) | Email Sends sign-in, invite and notification emails. Receives the invoices fleets forward to their Riggs email address. Data: names and email addresses, email content, and forwarded invoices with their attachments. |
| Mapbox | Ask us | Maps Draws maps in the app and turns addresses into map points and back. Data: addresses entered in HoneyRuns, and map points we turn into street names, such as a vehicle's last location. |
| LangSmith (LangChain) | United States | Monitoring Records each step Riggs takes so we can find and fix mistakes. Data: Riggs's prompts, replies and tool calls, which include fleet records, contact details and message content. |
| Sentry | United States | Monitoring Error reports, plus replays of a sample of app sessions, so we can fix bugs. Data: error details and logs, the page or request involved, IP addresses, and session replays with on-screen text masked. |
| PostHog | United States | Analytics Shows which pages and features people use, and records app sessions so we can see where people get stuck. Data: user ID, name, email, company and role, page views and clicks, and screen recordings with typed inputs masked. |
Systems you connect
Riggs can connect to the telematics and fleet systems you already use, such as Samsara, Geotab, Motive, Verizon Connect, Ford Pro, Azuga, Bouncie, DIMO, GPS Insight, OneStepGPS, FleetSharp, Fleetio and Shopmonkey. It can also post to Slack, send events to webhooks you set up, and work with AI assistants you connect to your account.
These are integrations, not HoneyRuns sub-processors. You hold the account with each of these companies. HoneyRuns connects to one only when you turn it on, using the access you give it.
Public vehicle lookups
To decode a VIN or find a maker's maintenance schedule, HoneyRuns looks the vehicle up in public sources: the NHTSA vPIC database run by the US Department of Transportation, and carmaker websites. These lookups send the VIN or the year, make and model, and nothing about your people or your customers.
Our public website
The public site at honeyruns.com uses Google Analytics and PostHog to count visits and see which pages people read. They see website visitors, not the customer data inside HoneyRuns.
Changes to this list. We update this page when the list changes and change the date at the top. If your agreement with HoneyRuns requires notice before we add a sub-processor, we notify you as that agreement says. Send questions to support@honeyruns.com.