How HoneyRuns protects fleet data and keeps people in control
A fleet maintenance service handles more than vehicle mileage. It holds invoices, contact details, conversations and permission to coordinate work. The people connecting those systems deserve to know where that data goes and what controls its use.
This month we strengthened access checks, updated software dependencies and improved our infrastructure with AWS and Cloudflare. We also refreshed our public security information so customers can find clear answers about data protection, AI processing and the controls available today.
Access follows your company and role
HoneyRuns checks a user's company membership, role and access to the records they request. A repair shop's access to a managed fleet depends on an active relationship. We strengthened permission checks as work continues, including when a paused Riggs action resumes.
Your settings govern Riggs's work
Riggs works within application permissions and your configured approval settings. Those settings determine which supported actions need review and which may run automatically. An approved task can include several related steps. Runs and activity records help your team review decisions and outcomes.
Relevant records, messages and documents may be processed by AI providers. Our subprocessor list explains who handles that data and for what purpose. Teams with specific processing or retention requirements can review those terms with us before connecting.
Data protection includes recovery
HoneyRuns uses encrypted connections, private customer-document storage and temporary download links. We maintain separate encrypted backups of uploaded files alongside provider-managed database recovery. Our IT guide covers the retention, recovery and data-handling requirements to discuss with your team.
Straightforward answers for IT teams
Our security page summarizes current protections. The IT review guide covers data handling, integrations, AI use and procurement questions. The subprocessor list and privacy policy provide the supporting disclosures.
Security is part of how we build, release and operate HoneyRuns. Code review, automated testing and checks for known software vulnerabilities help maintain the platform. We monitor application errors and service availability, investigate security reports and apply security updates. Detailed technical evidence can be discussed privately during an IT review.
If your team is evaluating HoneyRuns, send your proposed workflow and security requirements to support@honeyruns.com. We can review the available evidence and agree what is needed before rollout.