What does HoneyRuns do?
HoneyRuns helps fleets and repair shops coordinate maintenance. Riggs uses connected fleet data, conversations and service documents to prepare and carry out authorized work. Each Run records a maintenance case, its decisions and progress.
What customer data does HoneyRuns process?
Depending on the features you use, this can include account and contact details, vehicle and telematics records, maintenance history, messages, invoices and other uploaded files. Relevant data may be processed by providers for hosting, AI, communications and monitoring. Our subprocessor list identifies those providers, their roles and data categories.
Where is data stored and processed?
Our primary application data is stored in the United States. Some service providers operate globally or have processing locations that depend on the service. Review the location disclosures with us if your organization requires a specific region.
How do access and integrations work?
Company membership, user roles and active fleet-management relationships determine access. Connected systems use the authorization you provide. The data an integration can read or change depends on its supported capabilities and granted permissions.
Before connecting, confirm the users and roles involved, required integration permissions and how access will be revoked. We can review sign-in options, offboarding and any SSO or MFA requirements with your team.
How is customer data used with AI?
Riggs and document-processing features may send relevant records, messages and files to the AI providers on our subprocessor list. Application permissions and your approval settings govern supported actions; an approved task may include multiple steps.
AI providers' training, retention and processing terms depend on the provider and endpoint. We can review the applicable terms and permitted data categories with your team before rollout.
What should we confirm about recovery and retention?
HoneyRuns uses provider-managed database recovery and scheduled, encrypted file backups. Review retention, export, deletion and recovery requirements with our team before rollout, including how retained backups are handled.
What security practices does HoneyRuns use?
HoneyRuns combines encryption, company-based access controls and protected cloud infrastructure with code review, automated testing and checks for known software vulnerabilities. We monitor application errors and service availability, investigate security reports and apply security updates. Our security page explains these practices, and we can discuss relevant technical evidence privately.
How do we start an IT review?
Send your proposed workflow, systems to connect, data categories and mandatory requirements to support@honeyruns.com. We can help with your security questionnaire, review the relevant controls and evidence, and agree requirements before rollout. The privacy policy covers our data practices.