Dashivo^™ Privacy Policy

Version: 1.0
Last updated: October 1, 2026

Why Dashivo exists

Dashivo exists to keep drivers and authorities, including police, accountable — and to make it as hard as possible to destroy evidence or to make false reports or false charges. That only works if you can trust Dashivo with your recordings. So we collect as little as we can, your footage stays under your control, and our staff never see or hear your recordings.

This is our mission and our design goal. The specific commitments that bind us are the ones set out in this Privacy Policy.

At a glance

Your footage is private. Your messages are end-to-end encrypted. Dashivo staff never see or hear your recordings, and no one at Dashivo can read your messages.

The end-to-end part applies to Dashivo Pro messages while your company has end-to-end encrypted messages on, which is the default. If your company turns it off, your messages are not end-to-end encrypted: people in the chat under your company's roles can read them and we could be required to produce them under a search warrant, but Dashivo staff still never read them (Sections 3.8(h) and 7).

	What happens
Free and Plus plans	Your phone and Black Box send no footage, no audio and no location to Angry Owl Labs. What can reach us is limited to: your account details if you create an account (Section 3.3); your Terms acceptance record; purchase verification with Apple or Google; Driver Score summaries (numbers only, no locations — and you can turn this off); software update checks; and anything you choose to send us (such as a bug report by email). No analytics, no advertising, no location, no footage.
Dashivo Cloud and Cloud+ (not yet available)	Planned subscriptions for personal accounts. Before they launch we will update this policy to say exactly how uploaded footage is encrypted and who holds the keys (Section 2.2).
Dashivo Pro (company accounts)	A work tool controlled by your employer (the "Company"), which decides how it is used and is responsible for telling you about it; we run it on the Company's behalf (Section 3.8). Messages are end-to-end encrypted unless the Company turns that off. While you are on a work shift, your latest position is shared with the Company's owner, admins and dispatchers, and — only if the Company turns on driving paths and you acknowledge it — the path you drive on shift is kept for the period it chose (7, 30, 90 or 365 days). Nothing about your location is collected off shift, and opening the App never starts recording or a path. If the Company turns on automatic evidence uploads, short clips around police stops and impacts are stored in our cloud storage, encrypted at rest with keys we manage; our staff never view them.
Our staff	Support staff can help set up your account, but never see your messages, footage, audio or photos in any Dashivo tool. Support access is on by default, you can turn it off, and every session is shown to you (Section 3.7). Our staff never sign in as you or take over your account.
Legal requests	Content only for a valid search warrant, never for a civil case; we can't decrypt end-to-end encrypted messages; and we tell you about requests unless the law or a court stops us (Section 7).
Lookups your phone makes directly	Speed limits (OpenStreetMap), some map images (OpenFreeMap), street names (Apple or Google) and, in Dashivo Pro on iPhone, Apple Maps navigation are fetched by your phone directly from those services, not through us.
Advertising and sale	No ads. We do not sell your personal information or share it for targeted advertising.

We do not create faceprints or other biometric identifiers, and Dashivo does not perform face recognition or license plate recognition.

1. Who we are and what this policy covers

In short: Angry Owl Labs makes Dashivo. This policy explains what information Dashivo handles, where it goes, and your choices and rights.

1.1 Dashivo and Dashivo Pro are products of Angry Owl Labs LLC, a Colorado limited liability company, 2020 N Academy Blvd, Ste 261 #4690, Colorado Springs, CO 80909, USA ("Angry Owl Labs," "we," "us"). You can contact us at [email protected] or (303) 243-2659 (email is the best way to reach us); legal notices and legal process go to [email protected].

1.2 This Privacy Policy covers:

the Dashivo app for Android and iPhone (the "App"), on every plan (Free, Plus, Cloud and Cloud+), and the Dashivo Pro edition of the App;
the software on a Dashivo^™ Black Box (the "Black Box");
the Dashivo account portal at dashivo.app, the Dashivo Pro portal at pro.dashivo.app, our Dashivo websites, and our online services, including Dashivo Cloud and Cloud+ when they launch (together, the "Online Services"); and
our support, sales and other communications with you.

1.3 It does not cover third-party services that Dashivo works with, such as Apple (including Apple Maps), Google (including the Google Maps app), OpenStreetMap, OpenFreeMap, Mapbox, YouTube or your navigation app. Their own privacy policies apply. For Dashivo Pro, your employer's own policies also apply to how it uses the information it sees (Section 3.8).

1.4 Words defined in our Terms of Use (such as "Footage," "Telemetry," "Reports," "Company," "Owner," "Shift," "Trusted Contact" and "Detained Release") have the same meaning here.

1.5 Where to find this policy. This policy is available at https://dashivo.app/privacy, on the App's pages in the App Store and Google Play, and at any time in the App: on Android under Settings › Privacy & Security › Privacy Policy or Settings › Help & About › Help & legal; on iPhone under Settings › Privacy & security › Your data › Privacy Policy or Settings › Help & About › Help & legal. You can print it or save it from our website.

1.6 Personal accounts and Dashivo Pro: who decides. For a personal account (one you open for yourself), Angry Owl Labs decides how the information we receive is used, as described in this policy. For Dashivo Pro, your Company decides: the Company is the controller (the "business" under California law) of its members' Dashivo Pro information, and Angry Owl Labs is its service provider (processor), handling that information only on the Company's behalf and under its instructions (Section 3.8). The Company is responsible for telling its drivers and other members what it collects and why, and for any consent the law requires. Information we hold for our own purposes in both editions — such as sign-in and security records, billing, and records of legal requests — is covered by this policy directly.

1.7 Footage you record. Footage can include other people. You decide what to record and what to do with it, so you are responsible for respecting their rights (Terms Sections 9 and 11). For Dashivo Pro footage, the Company is responsible.

2. Our commitments

2.1 Free and Plus plans (no Dashivo Cloud subscription)

In short: your devices never send us footage, audio or location. They send only what's needed for your account, purchases, optional score summaries, update checks and what you choose to send.

If you use a personal account on the Free or Plus plan (and not Dashivo Pro), your phone, the App and your Black Box send no footage, no audio and no location to Angry Owl Labs' servers. The only information that can reach us is:

(a) update checks — when the App checks whether new software is available, it sends only the platform (Android or iPhone) and the App version. It contains no account, device or location information. Our server sees the IP address your device connects from, and it does not store update checks;
(b) account details, if you create an account — your email address, your name if you give it, your password (stored only as a salted hash) or your Sign in with Apple or Google identifier, and your Terms acceptance record (Section 3.3);
(c) purchase verification — information needed to confirm your Plus purchase or subscription with Apple or Google (Section 3.3);
(d) Driver Score summaries, if you are signed in and leave "Save driving scores to my Dashivo account" on — numbers only, such as distance, time spent speeding and counts of hard braking, and never the places you drove (Section 3.3). You can turn this off at any time in the App's Privacy & Security settings; and
(e) anything you choose to send us, such as a bug report, suggestion or support email. If you choose to share your screen with us (for example over a video call), you control what is shown.

There are no analytics, no telemetry, no location and no footage sent to us on these plans. Lookups your phone makes for speed limits, map images and street names go straight to those services, not to us (Section 3.2).

2.2 Dashivo Cloud and Cloud+ (not yet available)

In short: Dashivo Cloud for personal accounts hasn't launched. Before it does, we'll tell you exactly how your footage is encrypted and who holds the keys. Our staff will never view it.

Dashivo Cloud and Cloud+ are planned subscriptions for personal accounts; nothing is uploaded to them today. Footage you upload will be encrypted before it leaves your phone and stored encrypted, and Dashivo staff will never view, play or listen to it. Before they launch, we will update this policy, and tell you in the App, with: how the footage is encrypted and who holds the keys; whether it can be recovered if you lose your devices; the service information we can see (for example, your plan, how much storage you use and when uploads happen); and what we can produce in response to legal process (Section 7). Until then, footage we hold in our cloud storage is treated as Section 7.4 describes.

2.3 Sharing

Footage goes only where you send it. Footage you share from your phone (for example, from its share menu) goes directly to the app or person you choose, not through us. In Dashivo Pro, photos and videos you send in a message go to the chat's members, end-to-end encrypted unless the Company has turned that off (Section 3.8(h)). What a recipient does with footage you share is up to them and is not controlled by us.

2.4 "If I'm detained" release and Trusted Contacts (Cloud+, not yet available)

If you turn on the "If I'm detained" release (the "Detained Release"), and you do not check in within the time you chose after a police stop, Dashivo is designed to send that stop's footage and location securely to the Trusted Contacts you chose (for example, an attorney, a family member or a friend). To deliver it, we will hold your Trusted Contacts' names and contact details and the timing information described in Section 3.4.

2.5 Community reports

Speed trap, road hazard and accident reports are shared with other Dashivo users only if you opt in (Section 3.5). Sharing is not available yet; today, Reports stay on your phone.

2.6 Your Black Box

Angry Owl Labs has no remote access to your Black Box or to the Footage stored on it. Our servers do not connect to your Black Box. When you link a Black Box to your account, our server only issues short-lived signed sign-in passes and a signed list of the people you allowed, which the Black Box checks on its own. Software updates reach your Black Box only when you install them.

3. What information is handled, and where it goes

3.1 Information that stays on your devices

In short: this is the information Dashivo uses to record and show your drive. It stays on your phone, USB drive or Black Box. We don't receive it, except as described below.

The App and Black Box process the following on your own devices. Angry Owl Labs does not receive it, except (a) Dashivo Cloud uploads (when launched, Section 2.2), (b) Reports you opt in to share (when launched), (c) the Dashivo Pro information described in Section 3.8, and (d) anything you choose to send us.

Information	Details	Why
Video	Rear camera (dash cam mode); front and rear cameras recorded as separate files (body cam mode). Clip file names include the local date and time (to the second) and the camera. Video can capture other people, vehicles, license plates, faces, homes and places. On the Free plan, video carries a Dashivo watermark.	Recording your drive or walk
Audio	Body cam mode only, from the phone's microphone, included in each camera's file when audio is on. Body cam audio is on by default; you can turn it off in Settings. Dash cam mode records no audio.	Recording your surroundings
Stamp on the video	"REC," date and time, location, speed, g-force and trip distance, burned into the video	Showing when and where Footage was recorded
Precise location	GPS position, speed, heading and altitude. On iPhone, if you allow "Always" location, trip logging can continue in the background.	Stamp, heads-up display, trip and mileage logs, Reports
Barometric pressure	From the phone's barometer, where available	Altitude and elevation
Motion sensors	Accelerometer and gyroscope readings, g-force and impact events	G-force display, marking and protecting clips after impacts, Driver Score
Trip and mileage logs	Trips, distance, times and places; mileage exports you create (Plus)	Your mileage log. If you have a Black Box, trips can also be copied to your own Black Box over its local connection.
Driver Score details	The trip-by-trip events behind your score. Only the summary numbers can leave your phone (Section 3.3).	Showing your score
Performance timing results (Plus)	Run type, times, speeds and distances, calculated on your phone, shown on screen, burned into your Footage, and saved in a log on your phone (on iPhone the log also notes where the run took place)	Showing and recording timed runs
Acknowledgements	Your acknowledgement of the performance timing rules	Kept on your phone only
Device information	Phone model, battery level, temperature and thermal state, network type, storage space	Status display, heat protection, managing recording and storage
Settings	Your App and Black Box settings	Making Dashivo work the way you chose
Reports	Type (speed trap, road hazard or accident), location, time, heading, your speed and nearby street name	Your own record; shared only if you opt in once sharing launches (Section 3.5)
Navigation notifications (Android)	If you allow notification access, the turn-by-turn notification from supported navigation apps (such as Google Maps or Waze)	Showing the next turn on the heads-up display
Cached speed-limit data	Road and speed-limit data downloaded from OpenStreetMap for your area, kept on your phone for 30 days	Speed limit display
Black Box logs	On the Black Box: clip lists, integrity records (such as file hashes and lock records), device status and events	Keeping and protecting your Footage
Encryption keys (Dashivo Pro messages)	Private keys generated on your devices for end-to-end encrypted messages; never sent to us (Section 3.8(h))	End-to-end encryption

About navigation notifications. Android's notification access permission technically lets an app see notifications from other apps. Dashivo uses only the ongoing navigation notification posted by supported navigation apps (Google Maps, Maps Go, Waze, HERE, Sygic and OsmAnd), ignores all other notifications, and does not store or send what it reads. You can turn this off at any time in the App or in Android settings.

Where footage is stored. On Android, videos are saved to the Gallery's "Movies/Dashivo" album or to the App's private storage, depending on your settings. On iPhone, videos are saved in the App's Documents folder, which you can see in the Files app, unless you turn on private clips, which moves them to private App storage that is excluded from iCloud and computer backups. If your phone backs up your photo gallery or app data to a cloud service (for example, Google Photos or iCloud Backup), your Footage may be copied to that service under its terms. On iPhone, clips in the Documents folder are included in device backups. You control those backup settings.

On iPhone, Apple's iOS stops the camera when the App leaves the screen, so recording stops. Dashboard mode only changes what is shown on your screen; it does not collect anything new.

3.2 Lookups your phone or browser makes directly with other services

In short: to show speed limits, maps and street names, your phone or browser contacts those services directly. They receive your internet address and the area being looked up. We don't.

Service	What it receives	Why	Whose policy applies
OpenStreetMap Overpass API servers (public servers run independently of Angry Owl Labs; currently overpass-api.de, with overpass.private.coffee as a backup)	Your phone's IP address, the App's name and version, and the boundaries of a map square about 1 km across (on a fixed grid) around your position and the square ahead of you. No account information and no exact position. Because squares are requested as you drive, the sequence of requests can reveal your approximate route to the server operator. Squares already saved on your phone (for 30 days) are not requested again.	Downloading speed-limit and road data	The server operator's policy
OpenFreeMap (tiles.openfreemap.org)	Your phone's or browser's IP address and the map area being shown	Drawing maps in the App and in the Dashivo Pro portal	OpenFreeMap's terms
Mapbox (only on the Trips page of the dashivo.app account portal, and only when enabled)	Your browser's IP address, the map area being shown, and basic map-load events that Mapbox collects	Drawing trip maps in the portal	Mapbox's privacy policy
Apple Maps (Dashivo Pro navigation on iPhone)	Your location and the points of the route you are navigating, sent by your phone to Apple to draw the map and get directions. Apple map data is shown on your phone only; we do not store it or receive it.	Turn-by-turn navigation	Apple's privacy policy
Google Maps app (Android, only if you choose the hand-off and your Company allows it)	The remaining stops of your route, handed to the Google Maps app on your phone	Directions in Google Maps	Google's privacy policy
Your phone's geocoder — Google (Android) or Apple (iPhone)	Your coordinates, sent by your phone's operating system	Looking up the street and city name	Google's or Apple's privacy policy
Apple or Google — sign-in and purchases	Your Sign in with Apple or Google sign-in (if you use it); your in-app purchases and subscriptions, which Apple and Google process and bill	Signing you in; selling Plus and subscriptions	Apple's or Google's privacy policy
App stores — optional statistics	If you have allowed it in your phone's settings, Apple or Google may give developers crash reports and aggregated usage statistics. Dashivo itself contains no analytics.	App quality	Apple's or Google's privacy policy
Your navigation app (Android)	Nothing from Dashivo. Dashivo only reads the navigation app's notification on your phone.	Directions	The navigation app's policy
Website fonts and scripts	When you visit dashivo.app, your browser loads fonts from Google Fonts, and the portal's map pages load the MapLibre map library from unpkg.com. Those services receive your IP address and browser information.	Displaying the website	Google's and unpkg's policies
YouTube (future live-streaming feature, if you use it)	Your live stream and your YouTube account authorization	Live streaming to your own YouTube account	YouTube Terms of Service and the Google Privacy Policy (Section 3.6)

3.3 Information Angry Owl Labs receives — all plans

In short: your account details, your acceptance record, purchase checks, optional score summaries, update checks, security logs, and what you send us.

Information	Examples	Source	Why we use it
Update checks	Platform and App version, and the IP address your device connects from (not stored)	Your device	Offering software updates
Account information	Email address; password (stored only as a salted Argon2id hash); name, if you provide it or your sign-in provider shares it; Sign in with Apple or Google account identifier; an Apple private relay email address if you choose "Hide My Email"; account creation date; two-step verification settings, passkeys and recovery codes (secrets are encrypted or hashed); devices and phones you link	You; Apple or Google	Creating and securing your account; signing you in; communicating with you
Security and sign-in records	Sign-in history (date, time, IP address and browser or device), sign-in approvals, "Confirm it's you" checks, automatic sign-outs, security emails, account recovery requests (during the 72-hour wait), email-change and owner-email-change requests (including, for an owner change, the verification documents, kept encrypted), and rate-limit records	Your device or browser	Protecting your account; detecting abuse
Terms acceptance record	The documents and versions you accepted (Terms and Privacy Policy); date and time; IP address; browser or app identifier (user agent); App platform and version	You and your device	Proving our agreement with you; compliance
Purchase verification	Your plan, product, store, purchase or subscription status, expiry, and the transaction or purchase identifiers Apple or Google provide. Our server checks your purchase with Apple or Google. We do not receive your payment card details.	Apple or Google; your device	Unlocking Plus; providing Dashivo Cloud; handling billing questions
Driver Score summaries (optional)	Per-trip numbers: distance, start and end time and time zone, moving time, time spent speeding, late-night and phone-use seconds, counts of hard braking, rapid acceleration and sharp turns, the score and the formula version. No coordinates, routes or places — our server refuses them.	Your App, if you are signed in and "Save driving scores to my Dashivo account" is on (it is on by default; turn it off in Privacy & Security)	Showing your score and trends across your phones and in your portal
Push notification tokens	A token from Apple Push Notification service or Firebase Cloud Messaging, if you use a feature that sends notifications (such as Dashivo Pro)	Your device	Sending you notifications
Arbitration opt-outs, legal notices and privacy requests	Your name, email and the content of your notice or request	You	Honoring your choices; resolving disputes; compliance
Support messages, bug reports and suggestions (only when you send them)	Your email address and message; attachments you choose to send. The App's "Report a bug" opens a draft in your own email app, so you see everything before you send it. The draft includes the App version, phone make and model, operating system version, recording settings and status, storage used, Black Box status, and (on iPhone) battery, plan and network type, and (on Android) up to 60 recent App log lines with location and navigation lines removed. Messages sent through the website contact form are stored on our servers and emailed to our support team.	You	Answering you; fixing bugs; improving Dashivo
Black Box orders, preorders and reservations	For a preorder or order placed on dashivo.app: name, shipping and billing address, email, order details (model, storage, price, preorder batch), shipping and delivery records, refund and cancellation records, and warranty and return records. For a free reservation or a "tell me when it's ready" signup: your email and the model or list you chose. Payment card details are handled by our payment processor, Stripe, and never reach us; we receive the order, the amount, the last four digits and the card brand. Stripe also collects the information it needs to process the payment and prevent fraud, under its own privacy policy.	You; Stripe	Taking and shipping your preorder or order; telling you about your batch, delays and your right to cancel for a full refund; refunds; support and warranty; fraud prevention; accounting and sales tax
Account portal and website technical data	IP address, browser type, pages requested, date and time, and security logs. We use only cookies that are strictly necessary to sign you in, remember a trusted browser, protect forms and keep the site secure (for example `dv_session`, `dv_csrf` and `dv_browser`). We use no advertising or analytics cookies.	Your browser	Operating and securing the portal and website
Website forms	Information you enter in our contact or early-access forms (such as your name, email, message, vehicle make and model, state and phone model)	You	Replying to you; planning early access
Communications preferences	Whether you asked to receive product emails	You	Honoring your choices

We do not ask for your date of birth. We ask you to confirm that you are 18 or older.

3.4 Information Angry Owl Labs will receive — Dashivo Cloud and Cloud+ (not yet available)

In short: your uploaded footage, plus the service information needed to run the Cloud. The full list will be published before launch.

When Dashivo Cloud launches, we expect to receive: your uploaded footage and audio (event clips, instant police-stop uploads, and shared or Detained Release packages), encrypted as described before launch (Section 2.2); service information such as which account and vehicle an upload belongs to, sizes, upload and expiry times, storage used and the IP addresses your devices connect from; device and vehicle registrations; your Trusted Contacts' names and contact details and whether they accepted your invitation; Detained Release timing (that a stop started, the check-in time you chose, whether you checked in, and delivery status); and who you shared footage with and when. We will confirm this list, and say which items are readable by us, before Cloud launches.

Note to Trusted Contacts. If someone names you as a Trusted Contact, we will hold your name and contact details so that we can invite you and, if the Detained Release is triggered, deliver a package to you. We will use them for no other purpose. You can decline the invitation or ask us to remove your details at any time by contacting [email protected].

3.5 Community reports (opt-in, when sharing launches)

Sharing Reports is not available yet; today every Report stays on your phone. When sharing launches, if you opt in, each shared Report will be sent to our servers and shown to other Dashivo users near that location. A shared Report will include its type (speed trap, road hazard or accident), location, time and direction. It will not include your speed, and we will not show your name, email address or account identity with it. To show you Reports near you, the App will send us your position rounded to about 1 km. Because a shared Report contains precise location, we will ask for your consent before you share your first Report, and you can turn sharing off at any time. Retention is in Section 8.

3.6 YouTube live streaming (future)

If we offer live streaming to your YouTube account, Dashivo will use YouTube API Services. By using that feature you agree to be bound by the YouTube Terms of Service (https://www.youtube.com/t/terms), and the Google Privacy Policy (https://policies.google.com/privacy) applies to Google's handling of your information. We will explain what YouTube account data Dashivo accesses, uses and stores before the feature launches. You can revoke Dashivo's access to your Google account at any time at https://security.google.com/settings/security/permissions.

3.7 Support access and staff access

In short: our support team can view and help set up your account, it is on by default under our Terms, you can turn it off, and you can see every session. Staff never see your messages, footage, audio or photos.

To help you, authorized Angry Owl Labs support staff may view your account portal and, with Admin View, change settings on your behalf ("support access," Terms Sections 25.6 to 25.11). Admin View is on by default once you accept the Terms that include it, and you (or, for a Dashivo Pro Company, its Owner) can turn it off, or back on for a set time, in Account › Security › Support access. Even when it is off, a staff member may view your account read-only for up to 30 minutes at a time to answer a request, with a recorded reason.

What staff can see: the pages you see in your account portal — for example your profile, devices, plans, trips and Driver Score summaries, and for Dashivo Pro the Company's teams, routes and settings — with message text, previews and captions replaced by "Hidden from Dashivo support." Staff never receive message content (encrypted or not), Footage, audio or photo files, and message search is refused. Staff cannot see your password, two-step verification secrets, passkeys, recovery codes or payment card details, cannot change your email or ownership, and cannot open the end-to-end encryption or Company oversight pages.
Live co-browse: only when you approve a specific request or read out a one-time code, for at most 30 minutes. We then receive a temporary capture of the page you have open (using an open-source page-capture tool), including your pointer movements and clicks, so we can guide you. Form fields are masked in your browser before anything is sent; sign-in, password, two-step, recovery, email, billing, checkout and deletion pages are never captured; and message bubbles and previews, voice notes, photos, videos, clips and other media are blurred and emptied. The capture is used only during the session and deleted within 1 hour after it ends, and it is not kept after that.
Records we keep: for each support session, the date and time, the staff member, the reason, the pages viewed and a summary of changes made (never secret values). You can see these records in your account's security activity, and we notify you and email you a summary when a session ends. We keep them as shown in Section 8.
Staff tools: our internal staff tools are protected by Cloudflare Access sign-in, and every time staff view a customer's details or change anything, it is recorded in an internal audit log. No staff tool shows the content of messages, Footage or audio; for legal requests, staff see only counts, sizes, dates and integrity hashes (Section 7).
No account takeovers: staff never sign in as you, and never change your email or owner to reach your account or its content (Section 9.4).
Why: to provide the support you request or that the Services need, to set up and maintain your account, to keep the Services secure, and to comply with the law. Where a legal basis is required, it is performing our contract with you and our legitimate interest in providing reliable, secure support.

3.8 Dashivo Pro (company accounts)

In short: Dashivo Pro is a work tool. Your Company controls the account and its data, decides how it is used and must tell you about it; we run it on the Company's behalf. Messages are end-to-end encrypted unless the Company turns that off. Location is collected only on shift, and opening the App never records. Here is what the Company can see, what we store, and what you control.

(a) Who is in charge. A Dashivo Pro account belongs to a company or other organization (the "Company"), not to the individual driver. The Company's Owner and the admins it appoints decide who joins, which teams and roles people have, the driver policy, and how the Company uses Dashivo Pro. For the Dashivo Pro information described in this Section, the Company is the controller (the "business"), and Angry Owl Labs processes personal information only on the Company's behalf and under its instructions (as its "service provider" or "processor"). If you are a driver, your employer's policies also apply to you, and questions about how your employer uses this information should go to your employer. We will pass on to the Company any privacy request we receive about Company data, and help it respond.

(b) The Company's notice duties. Under our Terms (Section 21(c)), the Company must tell its drivers and other members, in writing and before using Dashivo Pro with them, what it collects and why — including location sharing on shift, driving paths (if on), automatic recording (if on), automatic evidence uploads (if on), Driver Score reporting, phone status and battery alerts, and Company oversight of messages (if on) — and must obtain any consent the law requires (for example, under state electronic-monitoring, location-tracking, wiretap and labor laws). The App also shows you notices of its own: the shift and location notice when you join, the driving-path notice you must acknowledge, the evidence-upload policy, and "Your company can read work messages." while Company oversight is on.

(c) What Dashivo Pro stores on our servers. Dashivo Pro runs on a separate database from personal Dashivo accounts.

Information	Details	Who can see it
Membership and roles	Your name, email, role (Owner, admin, dispatcher, driver or viewer), teams, invitations, and the phones you register (install ID, name, platform, phone model and App version)	The Company's Owner and admins; your name and role are visible to people you can message
Messages	Messages in company, team and direct chats, with sender, time, delivery and read receipts. Messages are protected in transit by TLS. Unless the Company turns end-to-end encrypted messages off, new messages, photos, videos and voice messages are end-to-end encrypted, and we store only encrypted data we cannot read (see (h)). If it is off, they are stored on our servers in readable form.	Members of the chat. Company, team and direct chats are visible according to the Company's roles and settings, and, while Company oversight is on, to the Company's managers (see (h)). Never Dashivo staff
Push-to-talk voice messages	Short recordings (up to 60 seconds) you choose to send	Members of the channel; the audio is deleted after 30 days
Photo and video attachments	Photos and videos you choose to send in a message, with a preview image	Members of the channel; deleted after 30 days
Dispatch and routes	Routes, stops and addresses the Company creates, assignments, and the progress you report (for example started, arrived, completed or skipped a stop)	The Company's Owner, admins and dispatchers, and the assigned driver
Driver location (during work shifts)	See (d) below	The Company's Owner, admins and dispatchers (never viewers)
Phone status (with location sharing)	While you are on a shift and sharing your location, the App also sends a small status reading about the phone: mobile carrier name, phone brand and model, operating system and App version, whether it is on Wi-Fi or mobile data and the signal strength (bars), battery level and whether it is charging, GPS accuracy, whether the dashcam is recording, and the miles driven so far this shift (counted on your phone). Like location, we keep only the latest reading, never a history. It is not used for your Driver Score.	The Company's Owner, admins and dispatchers (never viewers)
Driver Score summaries	The same numbers-only summaries described in Section 3.3, never coordinates. If the Company's policy turns on score reporting, your summaries are shared with the Company (by default, only trips during a work shift).	The Company's Owner, admins, dispatchers and viewers. Because they are Company records, drivers cannot delete them; the Company can
Driver policy	The Company's settings for your App, such as whether recording is required on shift, whether you can end your own shift, direct messages, push-to-talk, message previews in notifications and score reporting	The Company; you can see the policy that applies to you in the App
Spoken messages and directions (text-to-speech)	If you use the natural voice, the text of the message (never an end-to-end encrypted message) or navigation prompt is sent to our own speech server, which returns audio. Nothing is sent to a third party. The audio may be cached on our server for up to 7 days so repeated phrases play quickly. If you don't use it, your phone's own voice is used instead.	No one; the cache is used only to play the audio back
Notifications	Push notifications go through Apple Push Notification service or Firebase Cloud Messaging (Google). For end-to-end encrypted messages a notification says only "New encrypted message." Otherwise, by default it shows the sender and the start of the message (up to 120 characters); if the Company turns previews off, it says only "New message."	Apple or Google deliver them
Routing and address search	Addresses and positions used to plan routes and give directions are processed by our own self-hosted routing (Valhalla) and address-search servers, based on OpenStreetMap data. They are not sent to a third-party mapping company.	No one outside Angry Owl Labs
Vehicles, fuel and charging	Vehicle profiles the Company enters (name, make, model, year, optional VIN, fuel type, tank or battery size). When an owner or admin asks Dashivo to look a vehicle up, its VIN is sent from our server to the U.S. government's NHTSA vPIC service, and its make, model and year to the U.S. EPA's fueleconomy.gov service; nothing about drivers or locations is sent. Fuel and charging stations, fuel prices and fuel-economy figures are public data (NREL / U.S. DOE Alternative Fuels Data Center, © OpenStreetMap contributors, U.S. EIA, U.S. EPA) that we download and keep on our own servers, so finding stations along a route sends no positions to anyone. Cost figures are estimates. No driver location history is created or kept for this.	The Company's Owner, admins and dispatchers (vehicle profiles); public reference data is not personal
Evidence clips (only if the Company turns on automatic evidence upload)	Short clips the App saves around a police stop or an impact, with their recording identifier and fingerprint, uploaded to our cloud storage (Cloudflare R2) and encrypted at rest with keys we and our storage provider manage (not end-to-end encrypted). See (g)	The Company's roles that can view evidence. Never Dashivo staff, who see only counts, sizes, dates and integrity hashes
Devices and device history	For billing accuracy, security and fraud prevention, each time you sign in, a device is added, swapped, released or removed, a driver switches on a shared vehicle device, or a device check runs, we record: your member id and name, the Company, the server time, what happened and its outcome, the Dashivo device id our server gave the App, a keyed hash of the app-vendor identifier (identifierForVendor on iOS, ANDROID_ID on Android; used only to recognise a reinstall on the same phone), the App Attest / DeviceCheck or Play Integrity result and attestation key id, the device make, model (identifier and name), phone or tablet, operating system and version, App version and build, the device name when the system provides one, the mobile carrier, network type and SIM country when available, and the IP address and approximate city at sign-in. We do not collect MAC addresses, IMEI/MEID, serial numbers, UDIDs, phone numbers or a combined hardware fingerprint, and these records contain no GPS location. They are kept for 2 years (billing disputes); IP addresses are shortened to their network after 90 days.	The Company's Owner and admins (Seats & devices); Angry Owl Labs staff for support, billing and fraud review

(d) Driver location sharing. On a Dashivo Pro company account, sharing your location is part of being on a work shift: it starts when you start a shift and stops when you end it, and it cannot be turned off while you stay on shift. The App shows you a notice explaining this the first time you join a Company, and your phone's own location permission still applies (if you do not allow location, the App will not start a shift). When you are not on a shift, or the App has been closed, your location is not shared. While you are on shift:

your phone shares your location only while you are on a work shift and the App is running (in the foreground or the background; if you close the App completely, sharing stops and you appear offline). How often depends on the phone's state, to save battery: about every 1–2 seconds while it is charging and moving, about every 5–10 seconds on battery while moving, and about every 30 seconds when you are stopped, the battery is below 20% or the phone is in Low Power or Battery Saver mode;
we keep your latest position (latitude, longitude, accuracy, direction of travel, speed and time) and the latest phone status described in (c). Positions older than 10 minutes are not shown. We do not keep a location history unless your Company has turned on driving paths and you have acknowledged it, as described in (e);
your last position and phone status are deleted when your shift ends; and
your location is visible only to the Company's Owner, admins and dispatchers;
from your position, our server works out your live arrival times at your stops; it keeps your pace as distance along the route (never coordinates) for 10 minutes and deletes arrival times when your shift ends;
if your phone battery runs low on shift (by default below 20%, critical below 15%), the Company's Owner, admins and dispatchers are alerted, from the same latest-only reading; the alert state is deleted when your shift ends;
the Dashivo Pro App keeps a list of your recent navigation destinations (up to 50) only on your phone, so you can navigate to them again. It is never sent to Angry Owl Labs or your Company, you can clear it in the App's settings, and it is deleted when you sign out;
while a dispatcher has the Dashivo Pro dispatch console open, it may draw the path you have driven since they opened it, built from the positions it receives. That path exists only in that dispatcher's browser, disappears when the page is closed or reloaded, and is not saved by Angry Owl Labs.

Phone settings during a shift. While you are on a work shift, the App also tells your Company when certain settings on your phone change: Dashivo's own permissions (the location level, camera, microphone, notifications, and background refresh or battery optimization), whether location services (GPS) are on, the type of network connection (Wi-Fi, mobile data or none) and airplane mode, Low Power or Battery Saver mode, and a battery level at or below 5%. Each entry has only the time and the change — no location, no Wi-Fi network names, and nothing about other apps, calls or messages — and nothing is recorded when you are not on a shift. If the App stops sending updates during a shift (for example because it was closed or lost signal), your Company sees an "Offline" entry for that time. These entries are part of the Company's activity record (visible to its Owner, admins and dispatchers) and are kept for as long as the Company keeps that record.

Apple's and Google's operating systems control whether and how often an app can use location and the network in the background, and they may pause or slow these updates (for example, in Low Power Mode or Battery Saver, when the phone is hot, or if you close the App). Updates may therefore be less frequent than described above; the App will never send them more often.

(e) Driving paths (only if your Company turns them on). Driving paths are off unless the Company's Owner or an admin turns on "Keep driving paths" and chooses how long to keep them: 7, 30, 90 or 365 days (30 days is preselected). When they are on:

You are told first and must acknowledge. Before any path is kept for you, the App shows a one-time notice — "<Company> keeps the path you drive while you're on shift, for N days. Dispatch, admins and owners can see it." — with an "I understand" button. We record when you acknowledged, the notice version and the retention period. If the Company changes the period or we change the notice, you are asked again, and no path is kept for you until you acknowledge. You can see the notice again at any time in the App's Settings ("Your company keeps your driving path for N days").
Only on shift. A path is built from the shift locations described in (d), or from a recording you started yourself while on shift. Nothing is recorded off shift, nothing is recorded because you opened the App (for example to read a message or check a route), and nothing is recorded after the App is closed. A recording you start yourself while off shift stays on your phone; its path is not sent to your Company.
What is kept. For each trip: its start and end time, miles, Driver Score and number of clips, and the path line, simplified to about 10 metres. A trip ends when the App pauses in Parked mode, when your shift ends, or when updates stop for the Parked interval.
Who can see it. The Company's Owner, admins and dispatchers, and you (your own trips). Viewers cannot. Angry Owl Labs support staff see trip times and miles only, never the path, unless the law requires otherwise (Section 7).
Deletion. Trips are deleted automatically after the Company's period. If the Company turns driving paths off, every stored path line is deleted straight away (trip times and miles may remain as part of the Company's activity record).

If driving paths are off, trip summaries (times and miles, no path line or coordinates) may still be kept for the Company's activity record.

(f) Traffic colours and rerouted routes. While you are on shift, the speed in your shift locations (described in (d)) is also matched to the road you are on by our own routing server and turned into an average speed for that stretch of road, so your Company's route lines can show slow (orange) and jammed (red) stretches. Only the road-segment speed is kept, with no name, driver ID, position or route (just a random tag that changes every day, so the same driver isn't counted twice), for 15 minutes, and only for your own Company (it is never shared with or shown to another company). Positions are not kept for this beyond what (d) and (e) already allow, and nothing is collected off shift. If your navigation takes you off your planned route, the App may send your Company the new route ahead (calculated by our own routing server, never by Apple or Google) so dispatch sees where you are heading and an updated arrival time; it replaces the previous one and is deleted when you rejoin the plan, arrive, end the route or end your shift. See (i) for Apple Maps and Google Maps.

(g) Recording, Parked mode, work modes and evidence clips. In Dashivo Pro, the camera and microphone start only when you tap Start, when you start a police stop, or — only while you are on shift and only if your Company has turned on "Auto-start recording when driving" — when the phone detects driving (about 8 mph or more). Opening the App, including from a notification, never starts the camera, the microphone or a path. When the phone has not moved for the Company's Parked interval (5, 10, 20 or 30 minutes), the App enters Parked mode: it stops video, the camera, the microphone and high-rate GPS and keeps only a low-power motion and location watch so it can resume when you drive; an active police stop is never paused. The App always shows when the camera, microphone or path is active, and whether your location is shared ("Location shared · on shift" or "Not sharing · off shift").

Work modes. Your Company may set you as "dispatched" (assigned routes, with alerts such as late, idle or off route) or "self-directed" (no route or idle alerts; only safety alerts and low-battery alerts while driving). The work mode changes which alerts are raised, not what location information is collected.

Evidence clips. Your recordings stay on your phone, with two exceptions: photos or videos you choose to send in a message, and, if the Company's driver policy turns on "Upload evidence clips automatically," the short clips the App saves around a police stop or an impact, which upload to the Company's Dashivo Pro cloud storage as locked evidence (the App shows when this policy is on). They are encrypted at rest with keys we and our storage provider manage, which means we can be required by valid legal process to produce them (Section 7). Evidence clips can be viewed according to the Company's roles, cannot be changed or deleted by drivers or dispatchers, and are kept as described in Section 8. Angry Owl Labs staff never view, play or listen to them.

(h) End-to-end encrypted messages (on unless your Company turns them off). "End-to-end encrypted messages" is on by default for every Company; the Company's Owner or an admin can turn it off. While it is on, messages in direct chats and in team and company group chats — including the text, photos, videos and voice messages you send there — are encrypted on the sender's device and can only be decrypted on the recipients' devices: their phones running the App, and web browsers that a person has set up and verified for themselves. Our servers store and forward only encrypted data and cannot read it; Angry Owl Labs staff cannot read it, and neither can the Company's Owner or admins. Messages sent before it was turned on stay as they were. If the Company turns it off, new messages are not end-to-end encrypted: they are stored on our servers in readable form, people in the chat under the Company's roles can read them, and we could be required to produce them under a valid search warrant (Section 7), but Dashivo staff still never read them. Whether or not it is on, Angry Owl Labs staff never see or hear your recordings or read your messages, including when they help your Company through support access.

What we still handle. To deliver encrypted messages we hold: each device's public encryption keys and their signatures (never private keys); who is in each chat; who sent a message to which chat and when; message and file sizes; delivery and read receipts; whether a message is urgent; and the encrypted messages and files themselves. Dispatch information, routes, stop progress, locations, journey events and automatic Dashivo notices (for example battery or route alerts) are not end-to-end encrypted, because the Company's dispatch tools must read them.
Notifications for encrypted messages say only "New encrypted message," without the sender or the text; the App shows the message after decrypting it on your phone. Spoken read-aloud of encrypted messages uses your phone's own voice, never our server.
Encrypted photos, video and voice messages are stored as encrypted files and deleted after 30 days, like other attachments; files that are uploaded but never sent are deleted after a day.
New phones and browsers. When you sign in on a new phone or browser, your existing phone asks "New sign-in on … Allow it to read your messages?" Only if you tap Allow does that phone send the new device the keys it needs (encrypted end to end); "Not me" removes the new device and ends that sign-in. Your first device is trusted automatically. A browser can also be allowed by confirming it's you with your account's sign-in protection (for example a passkey or an emailed code).
Automatic encrypted backup. So that a new phone can read your earlier messages, the App keeps an encrypted backup on our servers of the keys needed to read your past messages (and of past direct messages your phone decrypted). The key that unlocks it is created on your phone and kept only in your phone's own end-to-end-encrypted sync (iCloud Keychain on iPhone; Google's Block Store, only where Google offers end-to-end encryption, on Android) or, if that isn't available, on the phone only. We never receive that key. A new phone signed in to the same Apple ID or Google account restores your history automatically; otherwise it starts with new messages only.
Security codes. Each conversation has a security code (a "safety number"), available under Advanced in the App's encryption panel. When someone adds or removes a phone or browser, the conversation shows a short note that their security code changed.
Company can read work messages (only if the Company's Owner turns it on). The Owner may turn on "Company can read work messages." While it is on, the App also encrypts every new end-to-end encrypted message in the Company — including direct messages between drivers and group chats the managers are not in — to the devices of the Company's Owner and admins (and dispatchers, if the Owner includes them), so they can read them in a read-only "Company oversight" view. This is done by the senders' devices; we still cannot read the messages. It applies only to messages sent while it is on, never to earlier messages. While it is on, every member sees "Your company can read work messages." in Messages and is told when it is turned on, and each time a manager opens a conversation they are not part of, the Company's audit log records who opened which conversation and when. Turning it off stops this for new messages.
Consequences for the Company. Because no one but the recipients (and, while "Company can read work messages" is on, the Company's managers) can decrypt these messages, we cannot provide their content to the Company (for example for its records, an export, an investigation or eDiscovery) or in response to legal process (Section 7); we can only provide the information listed above. Support staff using support access never see message content (Section 3.7). A Company that must keep or produce message content should leave end-to-end encryption off, or turn on "Company can read work messages" and keep content through its managers' devices under its own policies.
How it works. The App uses vodozemac, an open-source implementation (independently audited by Least Authority in 2022) of the Olm protocol (the Double Ratchet with triple Diffie-Hellman key agreement on Curve25519) for one-to-one chats and for sharing keys, and the Megolm protocol for group chats, with Ed25519 signatures, AES-256 encryption and HMAC-SHA-256 integrity checks. No encryption is unbreakable, and the protection depends on the security of the devices involved: anyone who can unlock a recipient's phone or browser can read messages there.

(i) Navigation: Apple Maps and Google Maps. On iPhone, turn-by-turn navigation in Dashivo Pro uses Apple Maps: your phone sends Apple the route's points and your location to get the map and directions, under Apple's privacy policy. Directions, arrival times and traffic from Apple Maps are shown only on your phone; Dashivo does not store them or send them to our servers. On Android (and on iPhone when you choose the Dashivo map), the map comes from our own servers and routes from our own routing server, so no mapping company receives your route. Google Maps hand-off (Android, only if your Company allows it): if you tap Google Maps on a started route, the App hands that route's remaining stops (their addresses or map positions, in order) to the Google Maps app on your phone, and Google Maps will see them under Google's own privacy policy. We never send your route or location to Google ourselves. The App shows a one-time note saying so the first time you use it. While you navigate there, the App keeps recording (only if it already was; it never starts recording because of the hand-off) and keeps sharing your shift location as described in (d), and your Company sees "Navigating in Google Maps" and an estimated arrival time. Time spent in Google Maps opened this way is not counted as phone handling in your Driver Score; to tell whether you switched to another app during it, the App uses Android's usage access only if you have already granted it, and only on the phone (which apps you used is never sent or stored).

(j) Calls between dispatch and drivers. Members can call each other in the Dashivo Pro App or portal ("in-app calls"), or open their phone's dialer to call a member's phone number.

We never record, store or listen to call audio. In-app call audio travels directly between the two devices and is encrypted between them (WebRTC with DTLS-SRTP). When a direct connection isn't possible, it passes through a relay server we run (TURN), which forwards only the encrypted audio and cannot decrypt it.
To connect a call, our server passes technical connection details between the two devices (network addresses and encryption parameters). It deletes them within an hour of the call ending.
We keep a call record: who called whom, when, whether the call was answered, missed, declined or cancelled, whether it was marked urgent or held while the driver was moving, and how long it lasted. The record appears in the conversation between the two members ("📞 Call · 3:12") and, for drivers, in the Company's activity history. It is kept like other Company records (Section 8).
When you tap Call phone, we record that a phone call was started (who and when) before your phone's dialer opens. The call itself goes through your phone carrier, not Dashivo, and we never receive any of its content.
Driving safety. If a driver is moving at 3 m/s (about 7 mph) or faster, a non-urgent call does not ring. It waits until the driver stops, or becomes a "missed call: call back" note. Urgent calls ring and can be answered hands-free.
Phone numbers. The Company's Owner, admins and dispatchers can see the phone number in a member's profile. Drivers can see a staff member's number only if that staff member turns on "Show my phone number to drivers". This is off unless the staff member turns it on.
Incoming-call notifications are delivered by Apple (including PushKit on iPhone) or Google (Firebase Cloud Messaging), and contain the caller's name and the call identifier only.
The Company can turn calling off for everyone.

(k) What drivers control. You can start and end your shift (unless the Company's policy says only a dispatcher can end it); location sharing runs only while you are on a shift and the App is running, and ending the shift deletes your last position. You decide when to record (unless the Company turns on auto-start, which works only on shift), and you see the notices described in (b) before driving paths are kept for you. You can also allow or deny the App's phone permissions in your phone's settings (if location is not allowed, you cannot start a shift), choose whether to use the natural voice, and choose what photos, videos and voice messages to send. You cannot delete Company records such as messages you sent or score summaries; ask your Company. If you leave the Company, it keeps its records of your work under its own policies.

(l) Retention. Dashivo Pro information is kept as set out in Section 8, or deleted sooner at the Company's request. When a Company closes its account, we delete its Dashivo Pro information, except what we must keep by law.

4. How we use personal information

In short: to run Dashivo, keep it secure, support you, and meet our legal obligations — nothing else.

We use the personal information we receive to:

provide, operate and maintain Dashivo and the Online Services you use, including software updates;
create and manage your account, and sign you in;
verify purchases, provide the features of your plan, and handle billing questions;
show your Driver Score summaries to you (and, for Dashivo Pro, to your Company as its policy allows);
provide Dashivo Pro messaging, dispatch, routing, voice, notifications and location sharing on behalf of the Company;
store Dashivo Pro evidence clips for the Company, and (when Cloud launches) store Cloud data, invite Trusted Contacts and deliver Detained Release packages and shares;
show opted-in community Reports to other users (when launched);
record and prove your acceptance of our Terms and your choices (such as an arbitration opt-out);
respond to your messages, provide support (including support access, Section 3.7), and investigate and fix bugs;
sell, ship, support and service Black Boxes, and handle warranty claims and returns;
send you service messages (for example, about security, changes to our Terms, your subscription or your orders), and, only if you agree, product news;
secure Dashivo, and detect, prevent and respond to fraud, abuse, security incidents and violations of our Terms;
improve Dashivo, using information you send us such as bug reports and feedback; and
comply with law, respond to lawful requests (Section 7), and establish, exercise or defend legal claims.

Legal bases (where required). Where a law requires a legal basis for processing (for example, if you are outside the United States), we rely on: performance of our contract with you (or, for Dashivo Pro, with the Company); our legitimate interests in operating, securing and improving Dashivo (balanced against your rights); your consent (for example, for community Reports and marketing), which you may withdraw at any time; for Dashivo Pro, the legal basis the Company relies on as controller; and compliance with legal obligations.

5. What we do not do

In short: no ads, no analytics, no selling, no tracking you for advertisers, no face recognition, and our staff never see or hear your recordings or read your messages.

No advertising. Dashivo contains no ads, and we do not use your information for targeted advertising.
No analytics or telemetry. The App contains no analytics, advertising or tracking software, and it does not send us usage telemetry. The Android App includes Google's Firebase Cloud Messaging only to deliver notifications, with Firebase analytics collection turned off. Our websites use no analytics or advertising trackers; the only third-party requests are those listed in Section 3.2.
No sale and no sharing for targeted advertising. We do not sell personal information, and we do not "share" it for cross-context behavioral advertising, as those terms are defined in California and other state laws. We have not done so in the past 12 months.
No staff access to content. Dashivo staff never view, play or listen to your Footage or audio, and never read your messages, in any Dashivo tool (Section 3.7). We cannot read end-to-end encrypted messages at all.
No biometrics. Dashivo does not perform face recognition, voice recognition or license plate recognition, and does not create faceprints, voiceprints or other biometric identifiers or templates. Dashivo Pro text-to-speech turns text into audio; it does not analyze anyone's voice.
No data broker activity. We do not collect personal information about people we have no direct relationship with in order to sell it.
No selling of location. We do not sell or license location data to anyone.

6. How we disclose personal information

In short: only to service providers working for us, at your direction, to your Dashivo Pro Company, or when the law requires.

We run our own servers and databases. Dashivo Pro routing (Valhalla), address search, map tiles (Protomaps), text-to-speech, the call relay (TURN) and real-time message delivery run on our own servers, so those requests are not sent to an outside company. We disclose personal information only:

To service providers that process it on our behalf and under our instructions:

Service provider	What it does for us	What it handles
Cloudflare	Our websites and Online Services are reached through Cloudflare's network (content delivery and an encrypted tunnel to our servers); Cloudflare Access protects our staff tools; and Cloudflare R2 stores uploaded files (Dashivo Pro evidence clips, attachments, voice messages, backups and exports), encrypted at rest	All web and App traffic to our servers, in transit, including IP addresses; the stored files (end-to-end encrypted message files stay encrypted)
Resend (with a standard email service as a backup)	Sending our emails, such as verification codes, security alerts, order emails, invitations and replies to support	Your email address and the email's content
Stripe	Payments for Black Box orders and preorders, Dashivo Pro billing, and any subscriptions sold on our website	Name, email, billing details and plan; card details go directly to Stripe
Apple (App Store and StoreKit, Sign in with Apple, Apple Push Notification service, App Attest and DeviceCheck) and Google (Google Play and the Play Developer API, Sign in with Google, Firebase Cloud Messaging, Play Integrity)	In-app purchases and purchase verification, sign-in, push notifications, and Dashivo Pro device-integrity checks	Purchase records, sign-in identifiers, push tokens, notification content (for end-to-end encrypted messages, only "New encrypted message") and device-integrity results
TomTom (only where we enable live traffic tiles)	Traffic map tiles for Dashivo Pro, fetched by our server	Map tile coordinates only; your IP address and identity are not sent
U.S. government data services (NHTSA vPIC, EPA fueleconomy.gov)	Vehicle lookups an owner or admin asks for	A vehicle's VIN, or its make, model and year; nothing about drivers or locations
Shipping carriers (for example, the U.S. Postal Service)	Delivering Black Boxes	Your name, shipping address and order

We require service providers to protect personal information with the same or equal protection as this Privacy Policy, to use it only to provide services to us, and to comply with applicable privacy laws. Services your phone or browser contacts directly (Section 3.2) are not our service providers.

To Apple and Google as needed for Sign in with Apple or Google and to verify purchases.
To your Dashivo Pro Company, as described in Section 3.8, if you use Dashivo Pro.
At your direction, for example when you share footage, when you opt in to community Reports (when launched), or when you use an optional integration.
To your Company's own cloud storage, if it turns it on. The Company's Owner or admins may connect storage the Company controls (for example Amazon S3, Backblaze B2, Google Cloud Storage, Azure Blob Storage, Cloudflare R2 or Wasabi) and have us copy the Company's evidence clips and Driver Score reports there. Once copied, those files are held under the Company's own account with that provider and are governed by that provider's terms and privacy policy, not this one, and are kept and deleted as the Company decides.
For legal reasons, as described in Section 7.
In a business transaction, such as a merger, acquisition, financing, reorganization or sale of assets, subject to this Privacy Policy or a notice to you. End-to-end encrypted messages would remain unreadable to any successor.

Our internal staff tools are used only by authorized Angry Owl Labs personnel who need access to account information to do their jobs. They are protected by Cloudflare Access sign-in, and every view of a customer's details and every change is recorded in an audit log. No staff tool shows the content of messages, footage, audio or photos (Section 3.7).

7. Law enforcement and other legal requests

In short: we give the content of your messages, footage or audio only to a valid search warrant, never in a civil case. Our staff never open, view, play or listen to it. We can't decrypt end-to-end encrypted messages, and footage that stays on your devices isn't ours to give. We tell you about requests unless the law or a court stops us.

7.1 Civil matters. We do not provide the content of messages, footage or audio in response to a civil subpoena or a discovery request; the federal Stored Communications Act (18 U.S.C. §§ 2701–2713) does not allow it. A party in a civil case must get content from you (or, for Dashivo Pro, from the Company), and you can download your own footage and messages from your account. We may provide basic subscriber records (such as your name, email address and sign-up date) in response to a valid subpoena, after notifying you, unless a court order prohibits notice. We may provide content if you give us your written consent.

7.2 Government legal process. We disclose information we hold to government authorities only in response to valid legal process, or as otherwise required or permitted by law: content (messages, footage in our cloud storage, audio and driving paths) only with a valid search warrant; other records (logs and metadata) only with a court order under 18 U.S.C. § 2703(d) or a warrant; and basic subscriber information and session logs with a valid subpoena, court order or warrant (18 U.S.C. § 2703(c)(2)). Requests from California government entities must also meet the California Electronic Communications Privacy Act (Cal. Penal Code § 1546 et seq.). We review each request for validity, the issuing authority and scope, produce only what it specifically names (the accounts, the kinds of data and the dates), and push back on requests that are overbroad, defective or sent to the wrong provider. For Dashivo Pro, we may ask the requester to seek Company data from the Company where the law allows.

7.3 Preservation. On a valid preservation request under 18 U.S.C. § 2703(f) we preserve the data it names for 90 days, renewable once for another 90 days; holding it longer needs legal process. While data is preserved, our normal deletion schedules (Section 8) are paused for that data only, and the preserved copy is deleted when the hold ends. Preserving data does not mean we disclose it.

7.4 What we can and can't provide.

Footage stored only on your devices (your phone, drive or Black Box): we don't have it, so we can't provide it.
Footage in our cloud storage (for example, Dashivo Pro evidence clips): it is encrypted at rest with keys that we and our storage provider manage, so we can be required by valid legal process to produce it. Our staff never view it outside that process, and never through it.
End-to-end encrypted messages: we have no key and no copy of one, so we can provide only the encrypted data and records about it (for example who sent it, to which chat, when, and its size). U.S. federal law does not require a provider to keep a way to decrypt them (47 U.S.C. § 1002(b)(3)). Your Company may be able to read its own work messages through Company oversight, if it turned that on (Section 3.8(h)).
Messages sent while end-to-end encryption is off for your Company: we hold them in readable form and may produce them in response to a valid search warrant, through the same process.

7.5 How we handle a request. Our staff review the legal document itself. Two authorized staff members must approve every production, and every step is logged. Retrieval, decryption where possible, packaging and delivery are done by automated backend systems. Our staff do not open, view, play or listen to the content; they see only technical details such as file counts, sizes, dates and integrity checksums. Packages are encrypted and delivered to the requesting agency through a secure, invitation-only agency portal (or, as a fallback, an encrypted file whose password is sent separately), and are deleted from our servers within 7 days after they are prepared, or when they are delivered.

7.6 Emergencies. We may disclose information we hold without legal process where the law permits, if we believe in good faith that an emergency involving danger of death or serious physical injury to any person requires disclosure without delay (18 U.S.C. § 2702(b)(8) and (c)(4)). We require a written explanation of the emergency.

7.7 Notice to you. We notify the account holder (for a Company, its Owner) of legal requests before disclosing anything, unless the law or a court order prohibits it (for example, an order under 18 U.S.C. § 2705(b)), or it is an emergency. If a nondisclosure order ends, we notify you then. If we delayed notice for an emergency, we notify you once it has passed, unless the law prohibits it. No notice is needed for a preservation request alone, because nothing is disclosed.

7.8 No account takeovers. Dashivo staff never sign in as you, change your account's email or owner, or transfer ownership of your account in order to reach your content, including when an agency asks.

7.9 Records we keep about requests. For each request we keep the legal document (encrypted), the decisions, the approvals and an append-only record of every step, including which staff member acted and from where (time, network address, approximate location and browser). These are records about our staff and the agency, kept with the request.

7.10 Transparency. We publish a transparency report every year, with the number of legal requests we received by type and how we responded.

7.11 How to send a request. Legal process may be sent to [email protected] with the subject "Legal Process," from an official address, with the document attached, or by mail to the address in Section 19. After we verify an agency, it receives an invitation to our secure agency portal to submit legal process and receive productions. See our law enforcement guidelines.

8. How long we keep information

In short: only as long as needed. Footage on your devices is up to you. Most records expire automatically on the schedules below. Deleting your account deletes your account data right away. For Dashivo Pro, several periods are the Company's choice.

Information	How long
Footage, Telemetry, Reports and performance timing logs on your phone, USB-C drive or Black Box	Controlled by you. Loop recording deletes old unlocked clips when storage fills.
Cached speed-limit data on your phone	30 days, then refreshed or deleted
Update checks	Not stored
Account information	While your account is open; deleted immediately when you delete your account, except as below
Terms acceptance records and acknowledgements	While your account is open; deleted when you delete your account
Arbitration opt-outs and legal notices	For the life of your account plus 6 years, so either of us can prove what was agreed
Sign-in history	90 days
Sign-in approvals, email-change requests and owner-email-change codes	Deleted 30 days after they expire (codes are valid for up to 7 days)
Account recovery requests	Until finished or cancelled (the wait is 72 hours)
Rate-limit records	2 days
Signed-in sessions	Until they end: website sessions after inactivity or at most 24 hours (30 days with "Keep me signed in"), Dashivo Pro portal sessions as the Company sets (by default 30 minutes' inactivity, at most 12 hours), App sign-ins after 180 days, and staff sessions after 8 hours
Staff audit log (staff views and changes)	2 years, unless needed longer to investigate a security incident
Account notifications (the notifications list in the account portal)	12 months
Driver Score summaries (personal accounts)	2 years after the trip, then deleted automatically. You can delete your personal score history at any time in the account portal; deleting your account deletes it
In-app purchase records we keep	While your account is open; deleted when you delete your account. Apple and Google keep their own records.
Black Box order, invoice, warranty and tax records	7 years, as tax and accounting law requires. If you delete your account, we erase your name, street address and invoice links from these records and keep only what tax law needs (such as the city, state and ZIP code).
Dashivo Cloud and Cloud+ data (not yet available)	Planned: Cloud event clips 30 days after upload and Cloud+ 60 days; Cloud data deleted 30 days after the end of your last paid period; Trusted Contacts until you or they remove them; Detained Release packages 30 days after delivery or cancellation and timing records 90 days after the stop. Confirmed before launch.
Shared community Reports (when launched)	Shown to others for up to 24 hours; deleted, with their link to your account, within 30 days
Support messages, bug reports and contact-form messages	Until you delete your account, and in any case no longer than 24 months after the conversation ends, unless needed longer for a legal claim
Website early-access sign-ups	Until early access ends or you ask us to remove you
Support access session records	2 years after the session, so you and we can review what support did; deleted when you delete your account
Live co-browse data (masked page capture, pointer and clicks)	Only during the session; deleted within 1 hour after it ends
Legal requests and their audit records	Kept with the request (Section 7.9). Production packages are deleted 7 days after they are prepared, or when delivered. Preserved copies are deleted when the preservation ends (90 days, renewable once).
Dashivo Pro messages (text) and route records	While the Company's account is open, unless the Company deletes them sooner
Dashivo Pro voice messages and photo and video attachments (encrypted or not)	30 days after they are sent, then the file is deleted automatically (the message shows that it expired). Files uploaded but never sent: 1 day
Dashivo Pro undelivered encryption-key messages	Until the recipient's device collects them, at most 30 days
Dashivo Pro text-to-speech audio cache	Up to 7 days
Dashivo Pro evidence clips in cloud storage (if the Company turns on automatic evidence upload)	90 days after the clip was recorded, then deleted automatically, unless the Company arranges a longer period with us (6 months, 1 year or 2 years). A clip under a legal hold is kept until the hold is lifted. An Owner's deletion takes effect after 24 hours. Deleted when the Company closes its account, except what we must keep by law
Dashivo Pro activity log and metrics (shifts, stop reasons and durations, route progress, app status, and the Driver Score summaries shared with the Company)	90 days by default; the Company can choose 6 months, 1 year or 2 years. Never includes GPS coordinates
Dashivo Pro journey events	30 days
Dashivo Pro driver location and phone status	Only the latest position and phone status; hidden after 10 minutes and deleted when your shift ends
Dashivo Pro live arrival-time data and rerouted route	Pace data 10 minutes; arrival times and the rerouted route are deleted when you rejoin the plan, arrive, end the route or end your shift
Dashivo Pro fleet traffic speeds	15 minutes
Dashivo Pro driving paths (only if the Company turns them on and you acknowledged)	The Company's chosen period (7, 30, 90 or 365 days; 30 by default), then deleted automatically; path lines deleted at once if the Company turns paths off
Dashivo Pro device history	2 years; IP addresses are shortened to their network after 90 days
Dashivo Pro push tokens and registered phones	Until you sign out, unregister the phone or leave the Company

We may keep information longer where the law requires it, or where we need it to resolve a dispute, enforce our agreements, or prevent fraud or abuse (for example, under a legal hold or preservation request).

9. Security

In short: we protect what we hold, require strong sign-in protection, never let staff take over accounts, and end-to-end encrypt Dashivo Pro messages by default. Your devices' security is in your hands.

9.1 We use reasonable administrative, technical and physical safeguards designed to protect the personal information we hold, including:

encryption in transit: connections to our websites and Online Services use TLS (HTTPS), with HTTP Strict Transport Security, and reach our servers through an encrypted Cloudflare tunnel, so our servers have no open ports on the internet;
encryption at rest for files in our cloud storage (Cloudflare R2), and AES-256-GCM encryption for legal documents, verification documents and the cloud-storage credentials a Company connects;
passwords are stored only as salted Argon2id hashes; sign-in tokens are stored only as keyed hashes; two-step verification secrets are encrypted;
access controls: our staff tools require Cloudflare Access sign-in, staff views and changes are recorded in an audit log, and no staff tool shows message, footage or audio content;
separation: our databases are not reachable from the internet, and Dashivo Pro data is kept in a database separate from personal Dashivo accounts; and
keeping our software up to date.

9.2 Account protection. A personal account must have a passkey or two-step verification; sensitive changes ask you to confirm it's you (within 5 minutes, or 10 minutes in Dashivo Pro); and we sign you out automatically after inactivity (Terms Section 5). A Company sets its own sign-in rules for its members. We email you when your account's security settings change.

9.3 Account recovery (personal accounts). If you lose every way to sign in, recovery uses a code sent to the email address on file and then waits 72 hours, while that address is told and anyone signed in can cancel. Only the browser that started it can finish it, and finishing removes passkeys, two-step verification and recovery codes and signs the account out everywhere. Our staff cannot complete or shorten recovery, and cannot reset a personal account's two-step verification.

9.4 Owner email changes and no takeovers. If a business asks us to move the owner email of its account to a new address because the owner left or lost access, we verify the request (documents and a call back to a number on file or the company's public business number), and two members of our staff approve it (three for an emergency shortening of the wait). We keep the verification documents encrypted, and only the staff who handle these requests can open them. We tell the current owner email and the company's other owners and admins, who can cancel during a 24 to 72 hour cooling-off, and the new address must confirm with a code. Every step is logged with who did it, when, and from which IP address and device. Addresses at our own domains and staff addresses are refused. Our staff never gain access to the account and never see its messages, footage, audio or photos. In Dashivo Pro, a Company's owners and admins change members' work emails, and the member confirms the change while signed in as themselves.

9.5 End-to-end encrypted messages. Dashivo Pro messages are end-to-end encrypted by default (Section 3.8(h)). Keep your devices and your backup key (in iCloud Keychain or Google's Block Store) safe: if you lose every device and that key, your encrypted message history cannot be recovered by anyone, including us.

9.6 No method of transmission or storage is completely secure, and we cannot guarantee security.

9.7 You control the security of your own devices, including your phone passcode, your Black Box password and Black Box Wi-Fi password, and any USB drive. Anyone who gains access to your phone, drive or Black Box may be able to view your Footage. Keep them locked and physically secure, and keep your software up to date.

9.8 Data breaches. If a security breach affects personal information we hold, we will notify affected people and authorities as required by applicable state and federal law. For Dashivo Pro, we will also notify the Company.

10. Your choices

In short: you decide what Dashivo can access, and you can delete your data and your account at any time.

Permissions. You can allow or deny camera, microphone, location (including background location on iPhone), notification access, local network and storage permissions in your phone's settings. Some features will not work without them.
Audio. Turn body cam audio off in the App's settings.
Navigation display (Android). Turn off Dashivo's notification access in the App or in Android settings.
Driver Score. Turn off "Save driving scores to my Dashivo account" in the App's Privacy & Security settings, and delete your personal score history in the account portal. (For Dashivo Pro, the Company's policy decides whether scores are shared with it.)
Dashivo Pro location. Location is shared only while you are on shift; ending your shift stops sharing and deletes your last position. Off shift, nothing is collected.
Community Reports. Opt in or out at any time in the App (when sharing launches).
Dashivo Cloud. Choose what to upload, delete Cloud clips, and add or remove Trusted Contacts at any time (when launched).
Account protection. Add passkeys or two-step verification, review your sign-ins and sign out everywhere in Account › Security.
Footage. View, copy, lock and delete your Footage on your phone, USB drive and Black Box. We cannot do this for you.
Support access. Turn Dashivo support access off or on at any time in Account › Security › Support access (for Dashivo Pro, the company Owner controls this). Live co-browse always needs your approval for each session.
Marketing emails. Unsubscribe using the link in any marketing email or by contacting us. We will still send service messages.
Account deletion. See Section 11.

11. Deleting your account

In short: delete your account on our website or by email. We then delete your account data right away, except what we must keep. Your footage on your own devices is not affected.

11.1 How. You can delete your account at any time at https://dashivo.app/account/delete (sign in first), which you can reach from any browser, including your phone's. You can also email [email protected] with the subject "Delete my account" from the email address on your account. If you have a Black Box preorder that has been paid but not shipped, or a website subscription that still renews, we will ask you to cancel it first (the preorder is refunded in full).

11.2 What happens. Deletion from our live systems is immediate and permanent. We delete your email, name, password hash, Apple and Google identifiers, sessions and App sign-ins, registered devices, Terms acceptance records, the support messages you sent, your community Reports, push tokens, purchase entitlements, Driver Score summaries, Trusted Contacts, and any Cloud data (queued for erasure from storage). We keep only a record holding the random account ID and the dates it was created and deleted, so our audit records still make sense, and the minimized tax records described in Section 8. We do not hold Sign in with Apple tokens; you can also remove Dashivo from your Apple ID or Google Account settings.

11.3 What is not affected. Deleting your account does not delete Footage, Telemetry, Reports or settings stored on your phone, USB drive or Black Box. Delete those yourself if you wish, for example by deleting them in the App, uninstalling the App, and erasing your Black Box and drives. On Android, uninstalling deletes the App's private storage but not videos saved to your Gallery. On iPhone, uninstalling deletes the App's files, including clips in its Documents folder, but copies may remain in your iCloud or computer backups.

11.4 Subscriptions. Deleting your account or the App does not cancel a subscription purchased through the App Store or Google Play. Cancel it in your App Store or Google Play subscription settings.

11.5 Dashivo Pro. If you are a member of a Dashivo Pro Company, deleting your personal account does not delete the Company's records of your work (Section 3.8). Ask the Company to remove you.

12. Children and teens

In short: Dashivo is for adults. It isn't directed to children, and you must be 18 or older to use it.

12.1 Dashivo is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If we learn that we have collected personal information from a child under 13, we will delete it. This is consistent with the Children's Online Privacy Protection Act (COPPA) and the FTC's COPPA Rule.

12.2 You must be at least 18 years old to use Dashivo (see our Terms). We do not knowingly allow anyone under 18 to create an account, and we do not sell personal information of anyone, including consumers under 16 or under 18.

12.3 If you believe a child or a person under 18 has given us personal information, contact [email protected] and we will delete it.

12.4 Footage recorded by users may incidentally include children who happen to be nearby. That Footage is controlled by the user who recorded it (see our Terms).

13. Your privacy rights in the United States

In short: depending on where you live, you may have the right to know, access, correct, delete and port your information, and to opt out of certain uses. We extend the core rights to all U.S. users, whether or not a law requires it.

13.1 Rights for everyone. Regardless of which state you live in, you may ask us to:

confirm whether we process your personal information and give you access to it;
give you a copy in a portable format (you can also download your account data from the account portal);
correct inaccurate information; and
delete your information (subject to the exceptions the law allows).

We can provide end-to-end encrypted messages only in encrypted form, because we cannot decrypt them. For Dashivo Pro information, the Company is the controller: we act for it and will refer your request to it (Section 3.8). We will not discriminate against you for exercising any privacy right.

13.2 Opt-out rights. Some state laws give you the right to opt out of the sale of personal information, targeted advertising, and profiling in furtherance of decisions that produce legal or similarly significant effects. We do not sell personal information, do not engage in targeted advertising, and do not engage in such profiling, so there is nothing to opt out of today. If that ever changes, we will update this policy and provide the required opt-out methods before doing so. Driver Score summaries are shown to you (and, for Dashivo Pro, to your Company); we do not use them to make decisions about you.

13.3 Sensitive data. Some state laws treat precise geolocation (and, in some states, other data) as "sensitive" and require your opt-in consent before a business processes it. Precise geolocation recorded by personal Dashivo accounts stays on your devices (community Reports, when launched, will be shared only after you opt in, and you can withdraw that consent at any time). For Dashivo Pro, the Company is the controller of on-shift location and driving paths and is responsible for any notice and consent the law requires (Section 3.8(b)); drivers must acknowledge driving paths in the App before any path is kept.

13.4 How to make a request. Email [email protected] with the subject "Privacy Request," or use the contact form on dashivo.app. Tell us which right you want to exercise and which state you live in.

13.5 Verification. To protect you, we will verify your identity before acting on a request, usually by confirming that you control the email address or account associated with the request. We will not ask for more information than we need. If we cannot verify you, we will explain why.

13.6 Authorized agents. You may use an authorized agent to make a request for you where the law allows. We may ask the agent for proof of your signed permission and may ask you to verify your identity directly with us, unless the agent holds a valid power of attorney.

13.7 Timing. We will respond within the time the law requires — generally within 45 days, which may be extended once where the law allows, and we will tell you if we need more time.

13.8 Appeals. If we decline your request, you may appeal by replying to our decision or emailing [email protected] with the subject "Privacy Appeal" within 45 days. We will respond to your appeal within the time required by law (generally 45 or 60 days, depending on your state) and explain our decision. If you are not satisfied, you may contact your state attorney general — for example, in Colorado at https://coag.gov, in Connecticut at https://portal.ct.gov/ag, in Virginia at https://www.oag.state.va.us, or in California at https://oag.ca.gov.

13.9 Global Privacy Control. Because we do not sell or share personal information or engage in targeted advertising, a Global Privacy Control (GPC) signal from your browser does not change how we process your information: we already treat every visitor as opted out. If we ever sell or share personal information, we will honor GPC as a valid opt-out request before we do.

13.10 Do Not Track. We do not track you across third-party websites or online services, and we do not allow third parties to do so through Dashivo. Our websites do not respond differently to "Do Not Track" browser signals, because they do not track you.

14. California privacy rights (CCPA/CPRA)

In short: California residents have specific rights under the California Consumer Privacy Act. Here are the details California law requires.

14.1 Applicability. This section applies to California residents. It is provided to meet the California Consumer Privacy Act, as amended by the California Privacy Rights Act (together, the "CCPA"), to the extent the CCPA applies to Angry Owl Labs. Even where it does not, we follow it voluntarily. For Dashivo Pro information, including information about a Company's employees and drivers, the Company is the "business" and Angry Owl Labs is its "service provider" under a written contract (our Terms); requests about that information go to the Company (Section 3.8).

14.2 Notice at collection. We collect the categories of personal information listed in the table below, for the purposes described in Section 4, and keep each for the periods described in Section 8. We do not sell or share (for cross-context behavioral advertising) personal information. A link to this Privacy Policy is shown in the App (including in its settings menu) and on our websites wherever we collect personal information.

14.3 Categories of personal information we collected in the past 12 months.

CCPA category	Examples	Sources	Business purposes	Disclosed to (for business purposes)	Sold or shared?
Identifiers	Name, email, account identifier, Sign in with Apple/Google identifier, IP address, device identifiers and push tokens; Trusted Contacts' names and contact details	You; Apple/Google; your device	Account, security, support, Terms acceptance, purchases, notifications, Detained Release delivery	Service providers (Cloudflare, Resend, Stripe); Apple/Google; your Dashivo Pro Company	No
Customer records (Cal. Civ. Code § 1798.80(e))	Name, address, telephone number	You	Black Box orders, shipping, warranty	Stripe, shipping carriers	No
Commercial information	Plus purchase, subscription status, Black Box purchases, returns, warranty claims	You; Apple/Google; Stripe	Purchases, plan features, warranty, accounting	Stripe, Apple/Google, accountants	No
Internet or other electronic network activity	Portal and website logs; sign-in history; App version; Terms acceptance records; Driver Score summaries; Cloud service information (Section 3.4); diagnostics you send	Your device or browser; you	Security, support, compliance, Driver Score, running Dashivo Cloud	Cloudflare, Resend; your Dashivo Pro Company (score summaries, per its policy)	No
Geolocation data	Approximate location inferred from IP address; Dashivo Pro latest location while on shift, and driving paths if the Company turns them on; Dashivo Pro route addresses; location stamped into Dashivo Pro evidence clips; precise location in community Reports you opt in to share (when launched); precise location in anything you choose to send us	Your device; you; your Company	Security; Dashivo Pro dispatch; community Reports; support	Cloudflare (in transit); your Dashivo Pro Company	No
Audio, electronic, visual or similar information	Dashivo Pro voice messages, photos and videos you send (end-to-end encrypted by default); Dashivo Pro evidence clips (if the Company turns on uploads), which our staff never view; Footage you choose to send us	You	Dashivo Pro messaging and evidence storage; support	Cloudflare (in transit); members of your Dashivo Pro channels	No
Professional or employment-related information (Dashivo Pro)	Your Company, role, teams, work shifts, route assignments and progress, messages, and Driver Score summaries shared with the Company	You; your Company	Providing Dashivo Pro to the Company	Your Dashivo Pro Company	No
Sensitive personal information	Account log-in (email and password); Dashivo Pro precise location on shift; precise geolocation in opted-in community Reports (when launched); the contents of Dashivo Pro messages	You	Providing the services you request; security	Cloudflare (in transit); your Dashivo Pro Company	No

We do not collect biometric information, protected-classification characteristics (other than confirmation that you are 18 or older), education information, or inferences about you. We do not derive characteristics about you from sensitive personal information.

14.4 Sensitive personal information. Under the CCPA, precise geolocation, account log-in credentials and the contents of messages (where we are not the intended recipient) are "sensitive personal information." Audio and video Footage is "audio, electronic, visual or similar information"; we treat it with the same care as sensitive information. We use and disclose sensitive personal information only for purposes that the CCPA regulations permit without offering a right to limit — such as performing the services you request, security and integrity, and short-term transient use — and only as reasonably necessary and proportionate for those purposes (Cal. Code Regs. tit. 11, § 7027(m)). We do not use or disclose sensitive personal information for any other purpose. For that reason we do not provide a "Limit the Use of My Sensitive Personal Information" link. If that changes, we will provide one.

14.5 Your California rights. You have the right to: (a) know what personal information we collected, used and disclosed about you, including the categories and specific pieces; (b) delete personal information we collected from you; (c) correct inaccurate personal information; (d) opt out of the sale or sharing of personal information (we do not sell or share); (e) limit the use and disclosure of sensitive personal information (see Section 14.4); and (f) not be retaliated against or discriminated against for exercising your rights. To exercise them, see Sections 13.4–13.7.

14.6 Financial incentives. Our paid plans (Plus, Cloud and Cloud+) and Dashivo Pro are priced for features and storage, not for personal information. We do not offer financial incentives related to personal information.

14.7 Consumers under 16. We do not have actual knowledge that we sell or share the personal information of consumers under 16 years of age. We do not sell or share anyone's personal information.

14.8 Automated decision-making. We do not use automated decision-making technology to make significant decisions about consumers, so the CCPA rights to opt out of and access automated decision-making technology do not currently apply. A Driver Score is a calculated summary shown to you and, for Dashivo Pro, to your Company; any decision a Company makes about its drivers is the Company's, not ours.

14.9 Shine the Light. California Civil Code § 1798.83 lets California residents ask for information about disclosure of personal information to third parties for their direct marketing purposes. We do not disclose personal information to third parties for their direct marketing purposes.

14.10 CalOPPA. This policy is intended to meet the California Online Privacy Protection Act (Cal. Bus. & Prof. Code §§ 22575–22579), including our disclosures about Do Not Track signals in Section 13.10, and the date at the top of this policy.

15. Other state privacy laws

In short: many states now have consumer privacy laws. We follow them where they apply to us, and give the core rights in Section 13 to everyone.

15.1 Comprehensive state privacy laws. Residents of the following states may have rights under their state's consumer privacy law, to the extent it applies to Angry Owl Labs:

State	Law	In effect
Virginia	Consumer Data Protection Act, Va. Code § 59.1-575 et seq.	Jan. 1, 2023
Colorado	Colorado Privacy Act, Colo. Rev. Stat. § 6-1-1301 et seq.	July 1, 2023
Connecticut	Connecticut Data Privacy Act, Conn. Gen. Stat. § 42-515 et seq.	July 1, 2023
Utah	Utah Consumer Privacy Act, Utah Code § 13-61-101 et seq.	Dec. 31, 2023
Texas	Texas Data Privacy and Security Act, Tex. Bus. & Com. Code § 541.001 et seq.	July 1, 2024
Oregon	Oregon Consumer Privacy Act, Or. Rev. Stat. § 646A.570 et seq.	July 1, 2024
Montana	Montana Consumer Data Privacy Act, Mont. Code § 30-14-2801 et seq.	Oct. 1, 2024
Iowa	Iowa Consumer Data Protection Act, Iowa Code ch. 715D	Jan. 1, 2025
Delaware	Delaware Personal Data Privacy Act, 6 Del. C. § 12D-101 et seq.	Jan. 1, 2025
Nebraska	Nebraska Data Privacy Act, Neb. Rev. Stat. § 87-1101 et seq.	Jan. 1, 2025
New Hampshire	N.H. Rev. Stat. ch. 507-H	Jan. 1, 2025
New Jersey	N.J. Stat. § 56:8-166.4 et seq.	Jan. 15, 2025
Tennessee	Tennessee Information Protection Act, Tenn. Code Ann. § 47-18-3201 et seq.	July 1, 2025
Minnesota	Minnesota Consumer Data Privacy Act, Minn. Stat. § 325M.10 et seq.	July 31, 2025
Maryland	Maryland Online Data Privacy Act, Md. Code, Com. Law § 14-4701 et seq.	Oct. 1, 2025 (applies to processing from Apr. 1, 2026)
Indiana	Indiana Consumer Data Protection Act, Ind. Code § 24-15	Jan. 1, 2026
Kentucky	Kentucky Consumer Data Protection Act, Ky. Rev. Stat. § 367.3611 et seq.	Jan. 1, 2026
Rhode Island	Rhode Island Data Transparency and Privacy Protection Act, R.I. Gen. Laws § 6-48.1-1 et seq.	Jan. 1, 2026
Oklahoma	Oklahoma Consumer Data Privacy Act (SB 546, 2026), 75A Okla. Stat. § 300 et seq.	Jan. 1, 2027
Louisiana	Louisiana Data Privacy Act (SB 386, Act 502 of 2026), La. R.S. 51:1780.1 et seq.	Jan. 1, 2027
Alabama	Alabama Personal Data Protection Act (HB 351, 2026)	May 1, 2027
Vermont	Vermont Data Privacy and Online Surveillance Act (Act 145 of 2026), 9 V.S.A. ch. 61A	Jan. 1, 2028

Florida's Digital Bill of Rights (Fla. Stat. § 501.701 et seq.) applies mainly to very large companies, but its rule requiring consent before selling sensitive data applies more broadly; we do not sell any personal data. This list may change as new laws take effect; we review it at least once a year.

15.2 Your rights under these laws generally include the rights to confirm and access, correct, delete and obtain a portable copy of your personal data; to opt out of sale, targeted advertising and certain profiling; and to appeal our decision. Some states also give the right to obtain a list of the categories of third parties, or the specific third parties, to which we have disclosed personal data (for example, Oregon and Minnesota) and, in Minnesota and Connecticut, the right to question the result of certain profiling decisions. The service providers we use are listed in Section 6. We do not sell personal data to any third party. Exercise these rights as described in Sections 13.4–13.8.

15.3 What we disclose. The categories of personal data we process, the purposes, the categories of third parties to which we disclose it and how to exercise your rights are described in Sections 3, 4, 6 and 13. We do not sell personal data, process it for targeted advertising, or engage in profiling that produces legal or similarly significant effects.

15.4 Nevada. Nevada residents may submit a request directing us not to sell covered information, as defined by Nev. Rev. Stat. § 603A.300 et seq. We do not sell covered information, but you may still submit a request to [email protected].

16. Biometric and health privacy laws

In short: Dashivo doesn't collect biometric identifiers or consumer health data.

16.1 Biometric laws. Illinois (Biometric Information Privacy Act, 740 ILCS 14), Texas (Capture or Use of Biometric Identifier Act, Tex. Bus. & Com. Code § 503.001), Washington (RCW 19.375), Colorado (Colo. Rev. Stat. § 6-1-1314) and other states regulate biometric identifiers such as faceprints, voiceprints and scans of face geometry. Dashivo does not create or use biometric identifiers or biometric information. It records ordinary video and audio, and it does not perform face recognition, voice recognition or any analysis to identify people. If we ever consider such a feature, we will not introduce it without first providing the notices and obtaining the consents these laws require.

16.2 Washington My Health My Data Act and similar laws. Washington's My Health My Data Act (RCW 19.373), Nevada's consumer health data law (Nev. Rev. Stat. § 603A.400 et seq.), Vermont's 2026 law (from 2028) and similar laws protect "consumer health data," which can include precise location information that could reasonably indicate an attempt to obtain health services. Dashivo is not a health product and Angry Owl Labs does not collect consumer health data. Location recorded by personal Dashivo accounts stays on your own devices, except (when launched) opted-in community Reports. In Dashivo Pro, location is collected only on shift: the latest position, and driving paths only if the Company turns them on, for the period it chose. We do not use location to infer anything about health. We do not set up geofences around health care facilities to identify or track people, collect health data, or send health-related messages.

17. Where your information is stored, and time zones

In short: Dashivo is intended for the United States. Our servers are in Colorado, uploaded files are stored with Cloudflare R2, and times are shown in your own time zone.

17.1 Dashivo is designed for and offered to users in the United States. Angry Owl Labs runs its own servers and PostgreSQL databases in Colorado, United States. Uploaded files (such as Dashivo Pro evidence clips, attachments, voice messages and exports) are stored with Cloudflare R2. Traffic to our servers passes through Cloudflare's global network, which may handle it at a location near you before it reaches our servers.

17.2 Users outside the United States. If you use Dashivo from outside the United States, your information will be transferred to, stored and processed in the United States, where privacy laws may differ from those in your country. Where a law gives you rights such as access, correction, deletion, objection or portability, you can use the process in Section 13. The legal bases we rely on are described in Section 4.

17.3 Time zones. We store times in Coordinated Universal Time (UTC) and show them in your own device's or browser's time zone. For Dashivo Pro, planned times (such as route starts, stop windows and shifts) use the local time zone where the driving happens; our server works out that time zone from a stop's location using offline time-zone boundary data kept on our own servers (timezone-boundary-builder, © its contributors and OpenStreetMap contributors, ODbL 1.0), so no location is sent to anyone for this.

18. Changes to this policy

In short: we'll tell you about important changes, and we won't quietly weaken our commitments.

We may update this Privacy Policy from time to time, and we review it at least once a year. We will post the new version with a new version number and effective date. If we make a material change — especially one that would use personal information in a new way, send new kinds of information off your devices, or change the commitments in Section 2 — we will notify you in advance in the App or by email and, where the law requires, ask for your consent. Changes will not apply retroactively to information collected under an earlier version without your consent where the law requires it. When this policy's version changes, the Dashivo Pro App asks drivers to review its location notice again.

19. Contact us

In short: questions go to [email protected]; legal notices and legal process go to [email protected].

Angry Owl Labs LLC 2020 N Academy Blvd, Ste 261 #4690, Colorado Springs, CO 80909, USA Support and privacy requests: [email protected] — use the subject "Privacy Request" or "Privacy Appeal" for privacy matters Legal notices and legal process: [email protected] — use the subject "Legal Process" for law enforcement requests and "Legal Notice" for other legal notices Phone: (303) 243-2659 (email is the fastest way to reach us)

Map and data attributions are listed in Section 14.3 of our Terms of Use.