Dashivo^™ Privacy Policy

Version: 1.26 Last updated: November 1, 2026

What changed in 1.26

• Black Box network names (Sections 3.1 and 3.4): a linked Black Box's status reports to dashivo.app now include the names of the Wi-Fi networks saved on it and the one it is using or, when it is wired, that network's domain, router name or local address, so your Black Box's page can show and manage them. Wi-Fi passwords never leave your phone and your Black Box.
• Version number: matches the Terms of Use.

What changed in 1.25

• Black Box remote support (At a glance and Sections 2.1, 2.6, 3.1, 3.7, 3.12 (new), 4, 6, 7.4, 8, 10, 14.3 and 17.1): if something on your Black Box needs a closer look, Dashivo support can now ask, from your support request, to connect to it. Nothing connects unless the account holder (in Dashivo Pro, one of the Company's Owners or Admins) approves, each time, with a passkey or two-step verification. A request lapses after 24 hours; a session lasts up to 3 days, can be ended at any time, and only you can extend it. The Black Box connects out to us; support gets a limited set of tools (no shell, no administrator rights, no Footage, no card or encryption keys, no saved Wi-Fi passwords), fixes are packages signed by Dashivo, and recording continues. Every command and its result is in a transcript you can read, and each step is also in our audit log. A session may be operated by our staff or by an AI assistant we direct, which runs on Anthropic's service. We keep a session's record and transcript for 90 days after it ends. Remote support is never used for police or legal requests. Where this policy said we have no remote access to your Black Box, it now says we have none unless you approve a support session, and never to your Footage.
• Accounts closed for breaking our Terms (Section 8): if we close an account because it broke our Terms of Use, we keep a scrambled copy of its email address and of its Apple and Google sign-in IDs after the account is deleted, only to stop the same person signing up again, for as long as the closure lasts.
• Version number: matches the Terms of Use.

What changed in 1.24

• Optional crash reports (At a glance and Sections 2.1, 3.1, 3.2, 3.3, 5, 8 and 14.3): the App can now send Dashivo a small report when it crashes or freezes, but only if you turn on "Send crash reports": the App asks once, and Settings changes your answer at any time. In Dashivo Pro, your Company decides for company-managed phones. A report holds only the kind of problem, the App's name and version, the platform, operating system and phone model, the part of the App you were in, a short signature of function names from our own code, the hour it happened, and a random install ID that the App replaces every month. It never includes your location, footage, audio, messages, name, email address, account or IP address. We keep reports for 90 days. Where this policy said the App sends no telemetry, it now says the only report it sends on its own is this optional one.
• Version number: matches the Terms of Use.

What changed in 1.23

• Hosting (Sections 6, 8, 17 and the service provider lists): our Online Services, application servers and databases now run on servers owned and operated by Angry Owl Labs in the United States, so we no longer use an outside hosting provider. Files uploaded to our Online Services stay in Cloudflare R2 in the USA, and Cloudflare still routes and protects network traffic. Where this policy listed our former hosting provider, it now says our own servers.
• Backups (Section 8): each database is backed up every night with an encrypted copy stored in Cloudflare R2, deleted after 30 days, and a continuously updated second copy of each database is kept on a standby server we operate in the United States.
• Version number: matches the Terms of Use.

What changed in 1.22

• The general area of your account (At a glance and Sections 3.3, 3.8, 4, 5, 6, 8, 11.2 and 14.3): when you sign in to your Dashivo account, and from time to time while you use the App (about once every 6 hours), we keep the general area your internet connection comes from, such as "Phoenix, Arizona, United States". Cloudflare, our network provider, works it out from your connection's IP address. It is not your device's GPS location, it is not real-time, and it says nothing about your trips or where you drive. We keep only the latest one for your account, with a map position rounded to about 11 km (7 miles), and never the IP address with it. We use it to understand roughly where our customers are, so we can see which areas our outreach and marketing are reaching and plan where to offer Dashivo, and its country to suggest the Record sound setting for your Black Box on dashivo.app. Our team sees it only as counts of customers by area, never with your name or contact details. We never use it for advertising, never sell it and never share it with other companies for their own use. It is in your data export and is deleted with your account. Dashivo Pro accounts are not affected.
• Version number: matches the Terms of Use.

What changed in 1.21

• Our phone line and Dash, our AI receptionist (At a glance and Sections 3.3, 3.7, 3.9, 3.11 (new), 4, 5, 6, 8, 9.1, 14.3, 16.1 and 17.1): our phone line, +1 970 807 0980, is answered by Dash, an AI receptionist. At the start of every call Dash says that it is an AI assistant and that the call may be recorded. For a call we keep your phone number, a recording of the call, a transcript of what you and Dash said, the time, length and outcome of the call, and any message you leave, which becomes a support request our staff answer. Telnyx carries and records the call and OpenAI runs Dash and the transcription, as our service providers. Recordings are stored encrypted. Recordings, transcripts and your number are deleted from the call log after 90 days; the rest of the call record after 24 months; a message is kept like other support conversations. Only support staff with the phone-call permission can see calls, and revealing a number, opening a transcript and playing a recording are logged. Dash can make mistakes, does not give legal advice and can't see any account; to reach a person, leave a message. We don't create voiceprints.
• We don't sell hardware (Sections 1.2, 3.3, 4, 6, 8 and 14.3): Angry Owl Labs no longer sells a Black Box device: Black Box OS is our software, which you install on your own board. We no longer take Black Box orders, so shipping carriers are no longer among our service providers. Records of Black Box preorders and reservations placed before are kept as before, to handle their cancellations and refunds and for tax.
• Phone recordings at Telnyx (Section 3.11): once our encrypted copy of a call recording is saved and checked, we delete Telnyx's copy, so recordings are kept only in our own storage, for 90 days.
• Version number: matches the Terms of Use.

What changed in 1.20

• Diagnostics logs stay with our support staff (Sections 3.3 and 3.9): a diagnostics log you send us is read only by our support staff. We never send it to an AI service or any other outside provider, and the Dashivo Pro support assistant can no longer read it.
• Satellite maps (Section 3.2): when you choose the Satellite view on a map in the dashivo.app or Dashivo Pro portal, your browser loads the imagery directly from the U.S. Geological Survey (basemap.nationalmap.gov), which receives your browser's IP address and the map area shown.
• Purchase and billing records after you delete your account (Sections 8 and 11.2): your billing details (name, address, tax ID and billing email) are deleted. We keep a Cloud invoice's amounts, dates and tax for 7 years, without your name, address or email; a record of an App purchase with only the store, the date, the price and a scrambled transaction reference, so the same purchase can't be claimed twice; and the stores' notices about your subscriptions, with no link to you.
• Reporting a shared link (Section 3.3): anyone with a shared link can report it to us from the link's page. We keep the report like a support conversation.
• Version number: matches the Terms of Use.

What changed in 1.19

• Support conversations (Sections 3.3 and 8): messages you send us from the App, the website contact form or by email to our support address are kept together as one conversation in our support inbox, where our support team reads and answers them. We delete a conversation 24 months after its last message, or sooner when you delete your account.
• Website visit totals (Sections 3.3 and 8): we keep totals of visits to dashivo.app, such as how many visits each page had, from which countries and websites, and how often our App Store and Google Play buttons were clicked. They are only totals: no visitor is tracked, no cookie is used for them, and nothing is linked to you.
• App Store and Google Play reviews (Sections 3.3 and 8): we keep the public reviews of the App that the stores give us, with our own labels on them (such as positive or negative, and the topic), so we can answer them and improve Dashivo.
• Version number: matches the Terms of Use.

What changed in 1.18

• Local time zone (Section 3.1): times in the App follow where you are, worked out on your phone; nothing is sent to us.
• Version number: matches the Terms of Use.

What changed in 1.17

• Recordings listed together (Privacy Section 2.2): your phone now gives each recording a random code and sends it with each piece, so the pieces of one recording (each minute and each camera) are listed together in your account, even with Maximum privacy. The code says nothing about when, where or what was recorded; the recordings themselves stay encrypted on your phone before upload.
• Version number: matches the Terms of Use.

What changed in 1.13

• Archive to your own Google Drive is available (Sections 1.3, 2.2, 3.2, 3.10, 6, 8, 10, 11.2 and 14.3): with Dashivo Cloud, you can connect your own Google account and your phones copy the clips you choose straight to your Drive, into a folder named Dashivo, with a short-lived access our server gives them. Dashivo asks Google only for the files it creates itself ("drive.file") and your Google account's email address. We keep the Google access encrypted and never send it to a phone or a browser. Disconnecting or deleting your account revokes our access at Google. Google's terms and privacy policy govern your Drive.
• Archive to iCloud Drive on iPhone is available (Sections 2.2, 3.2, 3.10, 8, 10 and 11.2): with Dashivo Cloud, your iPhone copies the clips you choose straight to the iCloud Drive of the Apple Account signed in on it (iCloud Drive › Dashivo). We keep only your choices and what each iPhone reports (when it last ran, how many clips it copied, couldn't copy or still has waiting, and the last problem). Apple's terms and privacy policy govern your iCloud Drive.
• Your archived copies are yours, outside Dashivo's encryption (Section 3.10(c) and (d)): archived copies are ordinary playable files protected only by your Google or Apple account, not by Dashivo's end-to-end encryption, and we can't see or delete them. Dashivo removes only files it put there itself, and only if you choose to delete them after 30, 90 or 365 days. Disconnecting, ending your plan or deleting your account leaves them in place.
• Google API Services Limited Use (Section 3.10(e)): how we use the access Google gives us for Google Drive and YouTube follows Google's API Services User Data Policy, including Limited Use: only for the features you turn on, never for advertising, profiling or training AI models, and not sold.
• Live streaming needs Dashivo Cloud (At a glance, Sections 2.4, 3.2 and 3.6): Dashivo live and YouTube live streaming need an active Dashivo Cloud plan, and one live stream runs during a police stop: Dashivo live (the default) or YouTube, with Dashivo live taking over if YouTube doesn't work. Without Cloud, a stop starts no stream and your Trusted Contacts still get your police stop alerts, without a live link. A stream that is running when a plan ends is not cut off. Your Trusted Contacts' alerts carry only their private Dashivo link, never a YouTube link, and "only when I tap Go live" is no longer offered.
• Police stop and accident uploads need Dashivo Cloud (Section 2.2): clips, police stop and accident clips included, upload only while you have an active plan; without one, they stay on your phone.
• Dashivo Cloud sets itself up (Section 2.2): once you have a plan, Cloud sets itself up on your phones with nothing to turn on. Your Recovery Key (shown in the App as your "backup key") is kept on your phones, in iCloud Keychain on iPhone or Google Block Store on Android (only when Google reports it is end-to-end encrypted), and on our servers only locked under your account's key, which only your phones can open. Saving your own copy is optional but strongly encouraged: the App reminds you, we send one email about it (it never contains the key), and "Email it to myself" sends it from your own phone's mail app, never through our servers. Another phone is approved with a 12-digit code, and removing a phone makes a new backup key. If you lose every phone, have no iCloud Keychain or Block Store copy and never saved your backup key, your Cloud clips can't be opened by anyone, including us.
• Version number: matches the Terms of Use.

What changed in 1.12

• Recently deleted (Sections 2.2, 3.8(g), 8 and 10): a Dashivo Cloud clip you delete goes to Recently deleted for 30 days, where it doesn't count against your storage and you can restore it, delete it now or empty Recently deleted. When an upload needs room, the oldest clips there are deleted for good first. After 30 days a clip is deleted for good. Nothing under a legal hold or preservation request is deleted. The same applies to Dashivo Pro cloud clips.
• Protected footage is deleted only on the web (Sections 2.2, 3.8(g) and 10): police stop, accident, impact, SOS, locked and evidence clips in the Cloud can be deleted only on dashivo.app (pro.dashivo.app for Dashivo Pro), after you confirm it's you and type DELETE, and not during a police stop or the 30 minutes after it. In Dashivo Pro only the Company's Owners and Admins can delete cloud clips, and each deletion is recorded in the Company's audit log.
• Trusted Contacts' levels of access (Sections 2.4 and 3.4): you say who a contact is (family, lawyer, friend or other) and choose what they see: Everything you share, Police stops and accidents only, or Custom. We keep the relationship and the level with the contact. The link sent when you end a police stop opens only that stop's clips.
• App purchase record (Sections 2.1, 3.3, 8, 11.2 and 14): the Dashivo app may send us the App Store's record of your purchase of the App (Apple's AppTransaction) or, on Android, that Google Play installed it, so your account can show that you bought the App. We keep the store, the original purchase date, a scrambled (hashed) copy of the transaction identifier and whether it was a test build, never the store's record itself.
• Trusted browsers (Sections 3.3, 8, 10 and 11.2): after you sign in on a browser with a second step or a passkey, a cookie lets that browser skip the second step for 30 days, and keeps dashivo.app signed in for up to 30 days. We store only a keyed hash of the cookie's value, with the browser's name (such as "Chrome on macOS") and dates. You can forget trusted browsers in Account › Security.
• Which country Cloud is offered in (Section 3.1): When your app store's country isn't available, the app works out which country you're in on your phone from its last location, to decide whether Cloud storage is offered. Only the two-letter country code is sent to us, never your location.
• Version number: matches the Terms of Use.

What changed in 1.11

• Live streaming is YouTube only, Unlisted or Private (Sections 1.3, 3.2, 3.6, 6 and 8): Twitch is no longer offered. Any Twitch connection has been disconnected: we revoked our access at Twitch and deleted the stored access and Twitch name. A YouTube stream is Unlisted unless you choose Private; there is no Public option.
• Version number: matches the Terms of Use.

What changed in 1.10

• Live streaming to YouTube or Twitch (Sections 1.3, 3.2, 3.6, 6 and 8): if you connect your YouTube or Twitch account, a police stop can stream from your phone straight to your own channel. We keep the access Google or Twitch gives us encrypted on our servers, use it only to run your streams, and revoke it when you disconnect or delete your account. We don't receive or keep the video.
• Live view during a police stop (Sections 2.4, 3.6, 3.8(g), 6, 8 and 14): your Trusted Contacts (and, in Dashivo Pro, your Company's dispatchers) can watch a stop live. Live view runs through Cloudflare Realtime, our service provider, which decrypts the video in memory to forward it, so it is not end-to-end encrypted there. It is never recorded or stored.

What changed in 1.9

• "If I'm detained" is now "If I'm arrested" (Sections 1.4, 2.4, 3.4, 4, 8 and 14): the feature has a new name, and "Detained Release" is now "Arrest Release".
• Police stop protections (Sections 2.4, 3.4 and 8): what we keep to run them: for each phone where you set your App PIN, a keyed hash of a value your phone derives from the PIN (and from your optional emergency PIN), never the PIN itself; the stop's times, including when your phone last reported in during the stop (about once a minute, with no location) and which alerts were sent; and the stop's location, sealed on your phone for your Trusted Contacts so that we cannot read it. If you enter your emergency PIN, your Trusted Contacts get the release at once and we email you that it was used.

What changed in 1.8

• Dashivo Cloud is available (Sections 2.2, 3.4, 7.4 and 8): how Dashivo Cloud encryption works. Clips are encrypted on your phone before they upload, and only keys you hold can open them: your phones, browsers you approve from a phone, your Recovery Key (and, on iPhone, a copy in your iCloud Keychain if you leave that on) and Trusted Contacts you confirm. We hold no key. We list what our servers can see (such as sizes, upload times, the hour a clip was recorded and which phone uploaded it), what we can produce under legal process (encrypted files and that service information only), and what happens to your clips when a payment is on hold or your plan ends.

What changed in 1.7

• Version number only, to match the Terms of Use.

What changed in 1.6

• Trusted Contacts (Sections 2.4 and 3.4): a Trusted Contact is a person you invite by email who accepts with their own Dashivo account, name and phone number. Within the limits you set for each contact, they can see your Cloud clips, events, Driver Scores and Miles day to day, and receive the "If I'm detained" release. Their key, not ours, opens your footage. We use a contact's details only to run their contact role and their own account. Former Viewers on shared accounts became Trusted Contacts.

• Parked Guard (Sections 3.1, 3.8(g) and 10): what Parked Guard uses and where it goes. Its sound triggers analyse sound on your phone to notice your car's alarm, breaking glass or something hitting the car; the audio is never saved or sent. Clips recorded while parked have no sound unless you turn on "Sound on clips while parked" (off by default). On iPhone, with your permission, iOS watches the spot where you parked and records motion while Dashivo is closed, so the App can tell you if your car moved and list the bumps when you're back. Its events stay on your phone, except in Dashivo Pro (below).

• Sound triggers run on your phone (Section 3.1): on Android with Google's YAMNet sound model and Google's LiteRT runtime, on iPhone with Apple's built-in sound classifier, both inside the App. Nothing is sent to us, Google, Apple or anyone else, and no analytics or MediaPipe components are used for it.

• Background location on Android (Section 3.1): in the Dashivo app, if you turn on Parked Guard's "Tell me if the car moves" and allow location all the time, the App checks the phone's location in the background while the car is parked, only to tell you that your parked car moved. It stays on your phone.

• Dashivo Pro (Section 3.8(g)): on a work shift with location sharing on, an impact Parked Guard senses is reported to your Company, on iPhone and Android alike, like the App's other safety alerts.

• Record sound (Section 3.1): on by default only in some countries; where it is off by default and you turn it on, the App shows a one-time note.

• Events and alerts with Dashivo Cloud (Sections 3.1 and 10): Parked Guard events and accident alerts can be uploaded end-to-end encrypted to show in Drive › Events and to alert your other phones.

• Diagnostics logs (Sections 3.1, 3.3, 3.9 and 8): the App keeps a diagnostics log on your device (no footage, audio, photos, messages, location, names, email addresses or passwords; kept 7 days). It reaches us only if you send it, or agree when our support team asks; we keep a sent log 30 days.

• Background location on iPhone (Section 3.1): with "Always" location, the App logs drives and keeps accident detection on during a drive in the background; nothing is sent to us.

What changed in 1.5

• Hosting (Sections 6 and 17): our Online Services ran with a hosting provider in its US region and files are stored with Cloudflare R2 in the USA, with Dashivo Pro files and personal Dashivo files kept in separate storage.
• Backups (Section 8): each database backup is deleted on a fixed schedule: the hosting provider's daily backups after 6 days and weekly backups after 27 days, and our own encrypted nightly backups after 30 days.
• Our own servers (Section 17): maps, routing, address search and voice run on our own servers in the USA.

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).

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]; legal notices and legal process go to [email protected].

1.2 This Privacy Policy covers:

• the Dashivo app for Android and iPhone (the "App"), with or without the Dashivo Cloud storage add-on, and the Dashivo Pro edition of the App;
• Black Box OS, our software that you install yourself on your own board, such as an Arduino UNO Q (a board running it is a "Black Box"; we don't sell Black Box hardware);
• 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 (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 and iCloud Drive), Google (including the Google Maps app and Google Drive), 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 "Arrest 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 The Dashivo App without the Cloud storage add-on

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 the Dashivo App with a personal account and without the Dashivo Cloud storage add-on (and not Dashivo Pro), your phone, the App and your Black Box send no footage and no audio to Angry Owl Labs' servers, and the only position they send is used to answer a request and never stored (see the end of this section). 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 App purchase or Dashivo Cloud subscription with Apple or Google, or with Stripe for a subscription bought on dashivo.app, including, when you are signed in, the App Store's record of your App purchase or, on Android, that Google Play installed the App (the app purchase record, 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, and, only during a Black Box remote support session you approve, the technical information about your Black Box described in Section 3.12. 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 usage telemetry and no footage sent to us without the Cloud storage add-on. The only thing the App sends on its own is an optional crash report, and only if you turn it on (Section 3.3). To show weather, speed limits and, on Android, in-app navigation, the App does send our servers a position, and we do not store it:

• Weather: your position rounded to about 1 km. Our server asks a weather service for that 1 km area: the US National Weather Service in the USA and the Norwegian Meteorological Institute (MET Norway) elsewhere. The service never sees your phone, and our servers don't log your internet address or link the request to an account or device.
• Speed limits: only which map square about 1 km across (on a fixed grid) you are in or about to enter, never your position. Squares already saved on your phone (for 30 days) are not requested again. Because squares are requested as you drive, the sequence of requests could reveal your approximate route, which is why none of them is kept.
• In-app navigation (Android): your current position, what you type in the search box and the place you choose, sent to our own place-search and routing servers (never to Google, Apple or Mapbox) to find places and calculate the route.

These requests are not linked to an account, and the positions, squares and search text are used only to answer the request: they are not written to any database or log. Our servers keep the answers briefly in memory so repeated requests are quick (weather for each 1 km area for 10 minutes, road data for each square for up to 6 hours), without any record of who asked. To stop abuse, a counter of requests per internet address is kept for up to 2 days, with the address scrambled. Map images and street names go straight to those services, not to us (Section 3.2).

2.2 Dashivo Cloud storage add-on

In short: Dashivo Cloud is optional; recording never needs it. Your clips are encrypted on your phone before they upload, and only you can view them: by default we keep a locked copy of your key so you can open them after signing in, and with Maximum privacy we keep none. Our staff never view your footage. Our servers see only the service information listed below.

Dashivo Cloud is an optional paid storage add-on for personal accounts, offered in the countries listed in Section 27.2 of our Terms of Use. It needs a Dashivo account. Without it, nothing in this section applies and Section 2.1 describes everything that reaches us. Clips, police stop and accident clips included, upload only while you have an active plan; without one, they stay on your phone (and your Black Box, if you use one).

How your clips are encrypted. Cloud sets itself up on your phones once you have a plan, with nothing for you to turn on: the first of your phones to open the App creates your account's key. Each clip, and each Parked Guard event or accident alert your phones upload, is encrypted on the phone before it leaves that phone (AES-256-GCM, with a new random key for every file, and those keys sealed to your account's key). Your phone also signs each clip, so your phones and browsers can tell if a stored clip was changed. Our servers store only the encrypted files. Only you can view your clips. With Maximum privacy we never have your account's key or any key that opens your clips; with Standard protection we keep only the locked copy described below. Dashivo staff never view, play or listen to them.

Who holds the keys. Only these can open your Cloud clips:

• Dashivo, with Standard protection (the default). Your phones also seal your account's key to a key held only by our customer service systems. It is used for two things only: to open your clips in a browser where you are signed in to your account (within 12 hours of signing in or confirming it's you), and to let a new phone signed in to your account in without another phone's approval. Each use is recorded and listed on your account's Security page (what, when, the browser or phone), and we email you when a new phone gets your keys. No Dashivo staff tool can use it. Turn on Maximum privacy in the App (Settings › Cloud storage) and we delete that copy and your phones change your account's keys; copies in our backups expire with them (Section 8).
• Your phones and tablets (up to 4 devices on one account). Each phone keeps its own keys protected by the phone (the iPhone Keychain or the Android Keystore). A new phone joins by itself when it can open your copy in iCloud Keychain or Google Block Store (below). With Standard protection it is added when you sign in on it; with Maximum privacy it is added only when one of your other phones approves it ("Allow this phone?") after you check that both show the same 12-digit code, or when you enter your Recovery Key on it.
• Your Recovery Key (shown in the App as your backup key). Your phones create it when Cloud sets itself up and keep it in their own protected storage, in your iCloud Keychain or Google Block Store copy (below), and on our servers only locked under your account's key. Our server also keeps a recovery copy of your account's key that only your Recovery Key can unlock. We never see the Recovery Key itself. Saving your own copy is optional with Standard protection and part of turning on Maximum privacy: with Maximum privacy the App shows a reminder until you mark it saved, and we send you one email about it, which never contains the key. In the App you can save it as a PDF, copy it, or use "Email it to myself", which sends it from your own phone's mail app, never through our servers. When you remove a phone, your phones create a new Recovery Key and the old one stops working, so save the new one.
• Your iCloud Keychain (iPhone) or Google Block Store (Android). Your phone keeps a copy of your account's key and your Recovery Key there, so a new phone signed in to the same Apple Account or Google account can open your clips by itself. Apple encrypts iCloud Keychain end to end; on iPhone, "Keep a copy in iCloud Keychain" is on by default and you can turn it off. On Android, the copy is kept in Block Store only when Google reports that it is end-to-end encrypted on that phone.
• Browsers you approve. With Standard protection, signing in is enough. With Maximum privacy, to open your clips on dashivo.app you approve that browser from one of your phones after checking that both show the same safety code, for the length of time you choose (1 hour to 7 days). The browser then decrypts your clips itself. It loses access when that time ends, when you sign out or lock it, or when you remove it in your account or from a phone, and we email you when a browser is approved. You can instead type your Recovery Key in a browser; it is used only in that tab and is not kept.
• Trusted Contacts you confirm (Section 2.4), each with their own key.

If you lose your keys. With Maximum privacy: if you lose every phone, have no copy in iCloud Keychain or Google Block Store and never saved your Recovery Key, your Cloud clips can't be opened by anyone, including us, and we can't recover them for you. With Standard protection, signing in on a new phone restores access. When you remove a phone or a browser, your remaining phones change your account's keys, so it can't open clips uploaded afterwards.

What our servers can see. To store your clips, keep within your plan and show your clip list, our servers see: your plan, the store you bought it from and the storage you use; for each clip, the account and phone it came from, its size and the sizes of its pieces, when it was uploaded, the hour it was recorded (rounded to the hour), whether it is a kept clip (a police stop, accident, impact, SOS or a clip you locked) or an everyday clip, whether it was marked urgent, a random code your phone gives each recording, so that the pieces of one recording (each minute and each camera) are listed together; the code says nothing about when, where or what was recorded, and when it was replaced or deleted (and, for a clip in Recently deleted, who deleted it and when it will be deleted for good); the phones and browsers that hold your keys (their public keys, labels such as "Chrome on macOS" and when they were added or removed); whether and when you marked your Recovery Key as saved; for each device, what it uploads and its space limit; the IP addresses your devices connect from; a tamper-evident record of key changes, which your phones can check; and, with Standard protection, a locked copy of your account's key and a record of each use (purpose, time, browser or phone, IP address kept 30 days). We can't see what is in your clips or events, their exact recording time, which kind of event they are, where they were recorded, their file names, or anything else inside the encrypted files.

When your storage is full. By default the oldest everyday clips are replaced to make room. Police stops, accidents, impacts, SOS clips and clips you lock are never replaced this way, and police stops and accidents can still upload up to 110% of your storage. You can also choose for each device what it uploads (everything, police stops and accidents only, or nothing) and a space limit that comes out of your storage; together the limits can't exceed it. A device at its limit replaces only its own oldest everyday clips; its police stop, accident and locked clips are never replaced and still upload while your storage has room. A device set to upload nothing keeps recording and keeps what it already stored.

Deleting clips, and Recently deleted. You can delete clips yourself. A deleted clip is hidden at once and goes to Recently deleted for 30 days, where it doesn't count against your storage. There you can Restore it, Delete now or Empty Recently deleted. When an upload needs room, the oldest clips in Recently deleted are deleted for good first, so a clip may go sooner than 30 days. After 30 days, or when you choose Delete now or Empty, the clip is deleted for good (its encrypted file is queued for erasure from storage) and can't be recovered. Protected footage (police stop, accident, impact, SOS and locked clips, and clips that are part of an evidence item) can be deleted only on the web at dashivo.app, after you confirm it's you and type DELETE, and not while a police stop is running or in the 30 minutes after it ends; the App doesn't delete police stop or locked clips from the Cloud. Only you and your account's Admins can delete clips, never our staff. Each deletion, restore and permanent deletion is recorded in your account's Cloud security record. Nothing under a legal hold or preservation request (Section 7.3) is deleted, by you, by the 30-day clock or to make room, until it ends.

If a payment fails or is on hold. If a renewal fails, uploads continue while the App Store or Google Play retries the payment, or for 7 days for a plan bought on dashivo.app. If the payment is then on hold (the App Store's billing retry, Google Play's account hold or a pause you chose in Google Play, or an unpaid dashivo.app invoice), uploads pause but nothing is deleted while the payment can still be collected: for up to 75 days with the App Store or Google Play (100 days for a Google Play pause) or 60 days on dashivo.app, counted from when uploads paused. We tell you when this starts and remind you. Once you pay, Cloud works as before.

When your plan ends. If your subscription ends (you cancel and the paid period runs out, a payment hold above ends without payment, or a purchase is refunded or charged back), your Cloud becomes read-only for 30 days so you can download your clips, and we email you 30, 7 and 1 days before the end. Then everything in your Cloud is deleted, kept clips and clips in Recently deleted included, together with the encrypted keys stored with them. Clips under a legal preservation request (Section 7.3) are kept, still encrypted, until it ends. A new subscription before then keeps your clips; after deletion, a new subscription starts empty.

Legal requests. With Maximum privacy we hold no key, so in response to valid legal process we can produce only the encrypted files, which we cannot open, and the service information above. With Standard protection we hold a locked copy of your account's key and would use it only for a valid search warrant, telling you unless the law or a court stops us (Section 7.4).

Archiving to your own Google Drive or iCloud Drive. With the add-on, your phones can also copy clips to your own Google Drive or, on iPhone, your own iCloud Drive. Archived copies are the clips' video and audio only, with no route trace, and are not encrypted by Dashivo. They go straight from your phone to Google or Apple, not through us, and Google's or Apple's terms and privacy policy apply to them. Section 3.10 describes this in full.

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 arrested" release and Trusted Contacts (Dashivo Cloud)

Trusted Contacts. You can invite people you trust (for example, an attorney, a family member or a friend) by email, and you say who each one is to you (family, lawyer, friend or other). A contact accepts with their own Dashivo account and confirms their name and phone number. For each contact you choose a level of access: Everything you share (all your Cloud clips, which they can download, events, Driver Scores, Miles and the Arrest Release); Police stops and accidents only (only the clips kept from a police stop, accident, impact or SOS, which they can download, and the Arrest Release, and nothing else); or Custom (you set each item: clips or only police stop and accident clips, downloads, events, Driver Scores, Miles, which cars, and whether they receive the Arrest Release). Within that level they can see your Cloud information day to day; you can change the level or remove them at any time, and removal ends their access at once. When you check in and end a police stop, the contacts who receive your Arrest Release are told that you're OK, with a link that opens only that stop's clips. During a police stop, and after a possible accident, the contacts who receive your Arrest Release can also watch live, in the Dashivo App or a browser, and after a possible accident a contact watching can call you in the App (Section 3.6). Your clips and live view reach your Trusted Contacts only while you have Dashivo Cloud; without it, they still get your police stop alerts (below), without a live link. Your footage stays encrypted: approving a contact on your phone wraps your account's footage keys for that contact's own key; we never hold your contacts' keys, and with Maximum privacy none of yours either (Section 2.2). People who were Viewers on a shared account became Trusted Contacts with similar access.

"If I'm arrested." If you turn on the "If I'm arrested" release (the "Arrest Release", formerly called "If I'm detained") and do not check in within the time you chose after starting a police stop (or you tap "Send now"), Dashivo is designed to send that stop's kept clips and its location to the Trusted Contacts you chose for it, by email and notification with a link. Unless you turn it off, those contacts are also told when you press POLICE and when you check in, and told once if your phone stops responding for 5 minutes during the stop. If you enter your optional emergency PIN, the release goes to them at once with a note that you entered it, and we email you that it was used. Your phone seals the location for each contact, so we cannot read it. Police stop and accident clips keep uploading on a low battery, down to 5%.

What we keep to run this. Your Trusted Contacts' names, email addresses, phone numbers, who they are to you (family, lawyer, friend or other) and the level of access and limits you chose. For each phone (each installation of the App) where you set your App PIN: a keyed hash of a value your phone derives from the PIN, and from your emergency PIN if you set one. Your phone never sends us either PIN and we never store them; we use the hash only to check, during a police stop and for 30 minutes after, that a check-in or another change to the release came from you. We also keep how many wrong PIN attempts were made, so that we can make you wait. For each stop: its times (start, the check-in time you chose, check-in, end, the last time your phone reported in, and when each alert or release was sent and why), the release records described in Section 3.4, and the stop's location, sealed on your phone for your Trusted Contacts, which we cannot read. During a stop your phone reports to us about once a minute; each report carries only its timing, not your location. If the App is closed or crashes during a stop, your phone tells us when the stop really started once it opens again. A check-in on the web during a stop uses a one-time code we email you. Retention is in Section 8.

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 unless you approve a remote support session, each time (Section 3.12), and a session gives us no way to open the Footage stored on it. Our servers do not connect to your Black Box: it connects to us, including during a support session. 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; the only exception is a support package signed by Dashivo, installed during a support session you approved (Section 3.12).

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, (d) the technical information your Black Box sends during a remote support session you approve (Section 3.12), (e) the status reports a linked Black Box sends, which include the names of the Wi-Fi networks saved on it (Section 3.4), and (f) anything you choose to send us.

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.

Diagnostics log. The App keeps a diagnostics log on your device: the App and operating system version, phone model, permission and setting states, recorder, camera, microphone, GPS, battery, heat, storage, network and upload events, and crash and freeze reports. It never includes footage, audio, photos, messages, your location, names, email addresses or passwords. It is kept for 7 days and leaves your device only if you send it (Section 3.3).

Optional crash reports. Separately from this log, the App can send Dashivo a small crash or freeze report, but only if you turn on "Send crash reports". The App asks once, after you first open it, and Settings changes your answer at any time. In Dashivo Pro, your Company decides for company-managed phones, and the App shows the setting as "Managed by" your Company. A report holds only the kind of problem (crash, freeze, or memory or processor limit), the App's name, version and build, the platform, operating system version and phone model, the part of the App you were in, a short technical signature made of function names from our own code, the hour it happened, and a random install ID that the App replaces every month so we can count affected phones. It never includes your location, footage, audio, messages, name, email address, account or IP address, and we do not store your IP address with it. It is not linked to you or your account (Section 3.3).

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 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. (Weather, speed limits and Android in-app navigation come from our own servers: Section 2.1.)

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, the general area of your account, and what you send us.

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 receives — Dashivo Cloud storage add-on

In short: your uploaded footage, encrypted on your phone before upload; only you can view it (Section 2.2), plus the service information needed to run the Cloud (Section 2.2).

With Dashivo Cloud, we receive: your uploaded footage and audio (event clips, instant police-stop uploads, and shared or Arrest Release packages), encrypted on your phone before upload; only you can view it (Section 2.2); by default, the GPS track recorded with each clip, your saved trips (routes, miles, mileage log and odometer readings) and your Parked Guard events and accident alerts, also encrypted on your phone so only you can view them (turn each off in Settings); service information such as which account, phone and vehicle an upload belongs to (we count the devices using each storage pool, because a pool covers up to 4 phones or tablets, and keep what each device uploads and its space limit), 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, who they are to you, the level of access you chose and whether they accepted your invitation; Arrest Release timing and alerts (that a stop started, the check-in time you chose, whether you checked in, when your phone last reported in during the stop, which alerts were sent, and delivery status); the PIN check values described in Section 2.4; and who you shared footage with and when. Section 2.2 lists what our servers can see; the locations sealed for your Trusted Contacts are not readable by us.

Black Box network names. A linked Black Box sends dashivo.app status reports. They include the names of the Wi-Fi networks saved on it and the one it is using or, when wired, that network's domain, router name or local address. Wi-Fi passwords never leave your phone and your Black Box.

Note to Trusted Contacts. If someone invites you as a Trusted Contact, we hold your name and email address (and, once you accept, your phone number and your Dashivo account) so that we can invite you, show the account holder who you are, let you see what they share with you, and deliver an Arrest Release and its alerts to you. We record when you view what is shared with you (at most once a day) in that account's security record. We use your details for no other purpose than your contact role and your own Dashivo account. You can decline the invitation, leave as a contact at any time in your account, or ask us to remove your details by contacting [email protected].

Shared links. When you create a shared link we store: which clips it includes, the encrypted copy of those clips' keys, your choices (how long it works, whether location and download are included), who in your account created it and when, when it expires or was revoked, and how many times it was opened and when it was last opened. We don't record who opened it: no name, no IP address beyond our normal short-lived security and rate-limit records, no device. We email you each time a link to your clips is created. The encrypted keys are deleted when the link is revoked, or within minutes of it expiring; the rest of the record is deleted 90 days after the link ended. People who open a link don't need an account; we don't set cookies for them or track them, and the page tells search engines not to index it. Retention is in Section 8.

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 Live streaming to YouTube, and live view

In short: in the Dashivo App, live streaming needs Dashivo Cloud, and one live stream runs during a police stop. A stream to YouTube goes from your phone straight to your own channel; we keep only the access to run it, encrypted. Live view (Dashivo live) goes to the people you or your Company chose through Cloudflare, which decrypts it in memory to forward it; nobody records it. After a possible accident, a Trusted Contact watching can call you in the App; calls are never recorded.

Live streaming needs Dashivo Cloud. In the Dashivo App, live streaming during a police stop, Dashivo live and YouTube alike, is part of Dashivo Cloud and needs an active plan. In Settings › Live stream you choose the one live stream your police stops use: Dashivo live (the default, part (b)) or YouTube, once connected (part (a)). Without an active plan, a police stop starts no stream: your phone records as usual, its clips stay on your phone, and your Trusted Contacts still get your police stop alerts, without a live link. If your plan ends while a stream is running, that stream is not cut off: it carries on until the stop ends, and only new streams need the plan. Live view in Dashivo Pro does not depend on Dashivo Cloud (Section 3.8(g)).

(a) Live streaming to YouTube (Dashivo Cloud, optional). If you connect your YouTube account in Settings › Live stream and choose YouTube as your live stream, Dashivo streams each police stop live to your own channel: when you start a police stop, your phone sends the camera picture and, if the recording has sound, the microphone straight to YouTube. If the YouTube stream doesn't start, or stops for about a minute, Dashivo live (part (b)) takes over for the rest of that stop. The video does not pass through our servers, and the stream does not show the recording's stamp (no speed or location on it).

• Connecting. You sign in at Google; Dashivo never sees your password. Our server keeps the access Google gives it (access and refresh tokens), encrypted, never on your phone, never exported and never shown to staff. We use it only to: list your YouTube channels so you can choose one; create a live video on that channel for each police stop, with the title and visibility you chose, start it and end it, and delete it after the stop if you turned off "Keep the recording on YouTube". We do not read, change or delete anything else in your YouTube account.
• What we store. Your YouTube channel's name and ID, when you connected it, your live streaming choices, and for each stream its link, visibility, title and times. We do not store the video or your stream key. These records are included when you download your data.
• Who can watch. A stream is Unlisted unless you choose Private (Dashivo does not offer Public streams): anyone who has the link of an Unlisted stream can watch it. What YouTube does with your stream is governed by its terms and Google's privacy policy: the YouTube Terms of Service (https://www.youtube.com/t/terms) and the Google Privacy Policy (https://policies.google.com/privacy). By using live streaming with YouTube, you agree to be bound by the YouTube Terms of Service. Dashivo's use of information received from YouTube API Services follows the YouTube API Services Terms of Service. If you have Trusted Contacts who receive your Arrest Release, their alert carries only their own private Dashivo link (part (b)), never the YouTube link itself; while your YouTube stream is live, that page links to it, or, for a Private stream, says that the stream is private on YouTube.
• Disconnecting. You can disconnect at any time in Settings › Live stream. We then revoke our access at Google (retrying for up to 30 days if that fails) and delete the stored access. Deleting your Dashivo account does the same and also deletes your live streaming records. You can also remove Dashivo's access in your Google account (https://myaccount.google.com/permissions). Videos already on YouTube stay there unless you delete them there.

(b) Dashivo live: live view for your Trusted Contacts (Dashivo Cloud). If "Share live with Trusted Contacts during a police stop" is on (it is on by default once a contact receives your Arrest Release) and Dashivo live is your live stream (or takes over from YouTube, part (a)), starting a police stop sends a smaller live copy of your camera, and your microphone if the stop records sound, to the Trusted Contacts who receive your Arrest Release. The same live view starts after a possible accident that the App detects, when you confirm the accident or call your emergency number from the App's question, or after 60 seconds without an answer (not if you answer that you're OK first); your contacts' alert then carries the approximate place (a place name your phone looks up, and a map link), and they are told when you tap I'm OK. Each contact gets their own private link for that stop or accident only, which opens in the Dashivo App (for a contact who has it) or in a browser without an account while the live view runs and for 15 minutes after. While it runs, your phone sends us its position about every 15 seconds so the contacts watching can see where you are; we keep only the latest one, show it only while it is fresh (2 minutes), never log it, and delete it, and the accident's place, when the live view ends. The secret part of the link stays in the browser and is not sent to our servers in the address; we keep only a keyed hash of it. Removing a contact, or switching off their Arrest Release, ends their link at once.

Live view is encrypted in transit on every hop, but it is not end-to-end encrypted: it runs through Cloudflare Realtime, a service of Cloudflare, Inc. (USA) that acts as our service provider, and to forward the video to each viewer, Cloudflare decrypts it in memory as it passes through. Cloudflare does not store it, and the video never reaches our own servers. If Cloudflare Realtime is not available, the video may instead go directly from the phone to each viewer's browser (peer to peer, for up to 3 viewers), through our own relay server when a direct connection is not possible; that way it is end-to-end encrypted and the relay forwards only encrypted data. Live view is never recorded or stored, by us or by Cloudflare.

Calls after a possible accident. While an accident's live view runs, a Trusted Contact watching it can call you in the App, audio only. The call goes directly between the two devices, or through our relay server when a direct connection is not possible, encrypted so that the relay forwards only encrypted data; it is never recorded. Your phone rings as a call, and while you are on it your recording continues without sound. There are no calls during a police stop, so the stop's recording keeps its sound.

What we keep about live view. For each stream: whether it is a police stop or a possible accident, when it started and ended, which cameras it used and whether it had sound, which contacts got a link and when each one opened it (also recorded in your account's security record), for each call, who called, when, whether it was answered and how it ended; and the network connection details needed to set up the video and calls, which include IP addresses. The connection details are deleted when a connection or call closes and at the latest an hour after the stream ends; the other live view records are deleted 30 days after the stream ends. Live view in Dashivo Pro is described in Section 3.8(g).

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. Connecting to your Black Box is separate and always needs your approval (Section 3.12).

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 (recordings of support calls, Sections 3.9 and 3.11, are the only audio staff can play); 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).
• Your Black Box is separate: support access never reaches your Black Box. Support can connect to a Black Box only through a remote support session you approve, each time (Section 3.12); turning support access on or off does not change that, and staff using support access cannot approve a session for you.
• 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 while you record off shift, opening the App never records, and your everyday clips upload to the Company's cloud unless it turns that off. 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.

The general area of an account described in Section 3.3 is not kept for Dashivo Pro accounts.

(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 and while recording off shift, driving paths (if on), automatic recording (if on), automatic evidence uploads and everyday driving 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 tells you itself, in one place: when you first sign in, the step where you accept this Privacy Policy and the Terms lists short checkbox lines, already ticked, for location on shift and while recording off shift, phone status on shift, driving paths (if on, with the Company's period), navigation shared on shift, driving scores (if the Company receives them) and Company oversight of messages (if on). You give consent by accepting that step. The Company's lines are required: Accept works only while they are ticked, because they are rules of the Company's account. The location line can be unticked: that turns location sharing off until you next start a shift, because sharing your location is part of being on shift (see (d)). There is no other notice to accept before location, driving paths or uploads begin. The same lines stay in the App's Settings › Privacy & security. The evidence-upload and everyday-upload policies are shown in the App as well.

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

(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. You agree to this when you first sign in, in the step where you accept this Privacy Policy and the Terms (see (b)), 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, your location is shared only while you are recording with the App: it is shown to the same people, marked "Off shift · recording", it stops and your last position is deleted when you stop recording, and it is never shared after the App has been closed. Off-shift positions are not used for arrival times, alerts or traffic. While you are on shift:

• your phone shares your location only while you are on a work shift, and while you record off 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. About every 1–2 seconds while a dispatcher is following you on the map: while an Owner, admin or dispatcher has you selected on the Company's fleet map (on shift, or while you record off shift), updates come about every 1–2 seconds, also on battery and while stopped (while stopped, an update is sent when the phone turns), and go back to normal within about a minute after they stop. This faster rate is not used when the phone is hot, below 20% and not charging, or in Low Power or Battery Saver mode;
• we keep your latest position (latitude, longitude, accuracy, direction, speed and time). The direction is your direction of travel while you move and the phone's compass direction while stopped (or moving slowly), so dispatch can see which way you are facing and the latest phone status described in (c). Positions older than 10 minutes are not shown. We do not keep a location history except driving paths, which are on unless your Company turns them off, 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, dispatchers and viewers (viewers do not see phone status, alerts or the activity record);
• 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 (on unless your Company turns them off). "Keep driving paths" is on by default for every Company, kept for 30 days; the Company's Owner or an admin can choose 7, 30, 90 or 365 days, or turn driving paths off. When they are on:

• Consent at sign-in. When you first sign in, the step where you accept this Privacy Policy and the Terms includes the line "<Company> keeps the path you drive on shift, and while you record off shift, for N days. Owners, admins, dispatchers and viewers can see it." It is one of the Company's required lines (see (b)). You give consent by accepting that step; there is no separate notice. We record the Privacy Policy version you accepted and when. If we change this Privacy Policy, you are asked to accept the new version. The line stays in the App's Settings › Privacy & security. If the Company turns driving paths off, the line is not shown.
• On shift, and while you record off shift. A path is built from the shift locations described in (d), and from the locations shared while you record off shift. Nothing is recorded because you opened the App (for example to read a message or check a route), nothing is recorded off shift unless you are recording, and nothing is recorded after the App is closed.
• 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, dispatchers and viewers, and you (your own trips). 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, when you start or continue a route, or navigate to a place from the App, while you are on shift (the App says "Recording started with your route"; you can stop recording and the route continues), 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"). Parked Guard (Settings › Parked mode, off until you turn it on) works as described in Section 3.1 while the App keeps recording in a parked vehicle; its sound triggers never save or send audio, and its events stay on your phone, except that on a work shift with location sharing on, an impact it senses is reported to your Company like the App's other safety alerts, on iPhone and Android alike: that an impact happened, when, and where the phone was, as a journey event (kept as described in Section 8). Bumps, sounds and the other Parked Guard events are not reported.

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 three exceptions: photos or videos you choose to send in a message; everyday driving uploads (below); 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. Only the Company's Owners and admins can delete cloud clips: police stop, accident, impact, SOS, locked and evidence clips only on the web at pro.dashivo.app, after confirming it's you and typing DELETE, and not during a police stop or the 30 minutes after it (the Dashivo Pro App doesn't delete police stop or locked clips from the cloud). A clip deleted from the Company's cloud clips goes to Recently deleted for 30 days, as Section 2.2 describes, and every deletion, restore and permanent deletion is recorded in the Company's audit log. Angry Owl Labs staff never view, play or listen to them.

Live view for dispatch. When you start a police stop in the Dashivo Pro App, the App sends a smaller live copy of the stop's camera (and its microphone, if the stop records sound) to your Company's dispatch console, where its Owner, admins and dispatchers can watch while the stop lasts; viewers and Dashivo staff cannot. Live view is encrypted in transit on every hop, but it is not end-to-end encrypted: it runs through Cloudflare Realtime, a service of Cloudflare, Inc. (USA) that acts as our service provider, and to forward the video to each viewer, Cloudflare decrypts it in memory as it passes through. Cloudflare does not store it, and the video never reaches our own servers. If Cloudflare Realtime is not available, the video may instead go directly from the phone to each viewer's browser (peer to peer, for up to 3 viewers), through our own relay server when a direct connection is not possible; that way it is end-to-end encrypted and the relay forwards only encrypted data. Live view is never recorded or stored, by us or by Cloudflare. Each time someone in the Company opens live view, and when it starts and ends, is recorded in the Company's audit log. Connection details (including IP addresses) are deleted when a connection closes and at the latest an hour after the stream ends; the other live view records are deleted 30 days after the stream ends.

Everyday driving uploads. Unless the Company turns them off, the App also uploads your everyday dash cam clips to the Company's Dashivo Pro cloud storage. This is on by default, and on Wi-Fi only by default. Clips upload only while your phone is charging, or while it is on Wi-Fi with the battery at 80% or more and the phone not warm; otherwise they wait on your phone. With the Wi-Fi-only setting, they also wait until the phone is on Wi-Fi. The Company's Owner or an admin can change both settings for the whole Company, for a driver or for a single phone (the most specific setting applies), and each change is recorded in the Company's audit log; the App shows the setting that applies to you. If mobile data is allowed and the phone reaches its monthly mobile-data limit, clips wait for Wi-Fi. Police-stop and accident clips never wait for Wi-Fi. Everyday clips are encrypted at rest with keys we and our storage provider manage (not end-to-end encrypted), so we can be required by valid legal process to produce them (Section 7). The Company's Owner, admins and dispatchers can play them, and you can play your own; viewers see only their details. Angry Owl Labs staff never view, play or listen to them.

The Company's storage pool. Everyday clips, evidence clips and chat photos, videos and voice messages share the Company's one cloud storage pool. Footage may use up to 95% of the pool; the last 5% is kept for chat files (which may also use any free space). When footage reaches its 95%, the oldest everyday clips are replaced first. When the whole pool is full, the oldest chat file is replaced first, then the oldest everyday clip. Police-stop, accident, impact, SOS, locked and evidence clips are never replaced to make room (police-stop and accident clips may use up to 10% more than the pool); if they alone fill the footage share, everyday uploads wait and the Company is alerted. Instead of "until storage is full," the Company may choose to keep everyday clips for a fixed period (30, 60, 90, 180 or 365 days). If the pool becomes smaller, nothing is deleted at once: everyday uploads pause for 14 days, and then the oldest everyday clips are replaced until the pool fits.

(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 kept like other attachments (Section 8); 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 accept the lines described in (b) at sign-in 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. To close a Company's account, its Owner asks Dashivo (for example, with "Request a change" › "Delete our company account" on the billing page); Dashivo then starts the closure. For 30 days the Company's account is read-only, its Owner can download a copy of its data, and the Company can ask us to keep the account. After 30 days we delete its Dashivo Pro information, including its cloud footage, except what we must keep by law (for example, evidence under a legal hold), and email its Owners to confirm. Members' own sign-ins are not deleted with the Company; each Member can delete theirs (Section 11). The only Owner, or the primary Owner, of a Company must hand ownership to another Member, or ask us to close the Company, before deleting their own sign-in.

3.9 Dashivo Pro Support (in the app and the portal)

In short: Dashivo Pro customers can get help by chat or voice with our AI assistant and our staff. Calls and chats are recorded and transcribed after we tell you and you tap Start. Audio and transcripts are deleted after 90 days. We don't create voiceprints.

What it is. Dashivo Pro customers in the USA can contact support inside the Dashivo Pro App and the Dashivo Pro portal: by chat or by voice with Dashivo's AI assistant ("Dash" or "Dasha"), and with our support staff. Dashivo Pro Support has no phone number of its own; calls take place in the App or the portal. Our public phone line, which anyone can call, is separate and is described in Section 3.11.

Recording and transcription. Support calls (the part with the AI assistant and the part with our staff) and support chats are recorded and transcribed for quality and support. Before a call starts we tell you that the call is recorded, and you tap Start; nothing is recorded before that. We keep the time you agreed, the version of the notice you saw and your account. If you don't agree, you can still write to us (a support request) without a call.

What we collect. The audio of the call (your voice and the assistant's or staff member's voice); a written transcript (codes, card numbers and other long numbers are removed before it is stored); the assistant's summary of your request; your support requests and messages; which tools the assistant used (for example "looked up your account summary"); and technical details of the session: App or browser version, device model, operating system and a coarse country or region (never your IP address or precise location). If you ask for help with the App, your Dashivo Pro App also sends a device setup snapshot: App version, operating system, permission and settings states, battery, storage and network type, and error codes. It never includes footage, clips, messages, contacts or locations. During live help, the screen images you share (with footage, camera views and messages masked on your device) are shown to our staff while the session runs and are stored with your support request so that we can review the support we gave. In a support chat or call you can also choose to share a picture of the Dashivo page or App screen you are on (the same parts are masked on your device, and you see it before you send it); the assistant uses it to help you, and it is stored with your support request.

Who processes it. The AI assistant runs on OpenAI's API (OpenAI, L.L.C., USA) as our service provider: OpenAI receives the conversation to produce answers, and under OpenAI's API terms, API data is not used to train its models (Section 6). Recordings are stored encrypted in our cloud storage (Cloudflare R2, USA).

Who can see it. Dashivo support staff with the support permission, to help you and to check the quality of our support. Every playback, download, transcript view and screen image view is logged. Our staff never see your Company's footage, messages or locations through support.

How long we keep it. Audio and transcripts: 90 days, then deleted. Live help screen images, pictures you shared in a support chat or call, the summary of your request, the request itself and the record that a call or chat happened (time, length, outcome) are kept with your support history, for 24 months after the last activity (Section 8).

Diagnostics. The assistant cannot read the diagnostics logs you send us; only our support staff do (Section 3.3).

No voiceprints. We do not create voiceprints or identify people by their voice. Recordings and transcripts are used only to help you and to check the quality of our support (Section 16).

Your choices. You can ask for a person at any time (say or type "person"). You can use chat or a written request instead of voice. You can ask us to delete a recording early by writing to [email protected]; we delete it within 30 days.

3.10 Archive to your own Google Drive or iCloud Drive (Dashivo Cloud)

In short: with Dashivo Cloud, your phones can copy clips into your own Google Drive or, on iPhone, your own iCloud Drive. The clips go straight from your phone to Google or Apple, not through us. For Google Drive we keep the connection, encrypted; for iCloud Drive we keep only your choices and what your iPhones report.

Archiving is part of Dashivo Cloud and needs an active plan; without one, archiving stops and your choices are kept. It uses only your own storage: Dashivo has no Google Drive or iCloud storage of its own for your clips. For each destination you choose which clips to archive (police stops, accidents, locked clips, Parked Guard clips, or all clips), how often (as soon as a clip is saved, daily or weekly), whether to use Wi-Fi only, whether to keep the sound, and whether to delete archived files after 30, 90 or 365 days. Each phone archives only its own clips, never during a police stop's recording, and copies each clip once to each destination. Archived copies are the clips' video and audio files only, with no route trace, and they are not encrypted by Dashivo: once in your Google Drive or iCloud Drive, they are protected by Google's or Apple's security and your account there, and anyone who can open that account can play them.

(a) Google Drive (Android and iPhone). You connect your own Google account by signing in at Google; Dashivo never sees your Google password. Dashivo asks Google only for access to the files Dashivo itself creates in your Drive (Google's "drive.file" permission), not to anything else in your Drive, and for your Google account's email address, so that the App and your account can show which Google account is connected. When you connect, our server creates a folder named Dashivo in your My Drive (and creates it again if you delete it); each phone puts its clips in a folder for that phone and month inside it.

• What we store. The access Google gives us (access and refresh tokens), encrypted on our servers, never sent to your phone or a browser, never exported and never shown to staff; the connected Google account's email address; the Dashivo folder's ID; when you connected; your archive choices; and what your phones report after each run (when it last ran, how many clips were copied or failed, and the last problem). These records are included when you download your data, without the tokens.
• How clips get there. When a phone has clips to archive, our server gives it a short-lived access (at most one hour) to your Drive, and the phone uploads the clips straight to Google. The clips do not pass through our servers.
• Disconnecting. You can disconnect at any time in the App or in your account on dashivo.app. We then revoke our access at Google (retrying for up to 30 days if that fails) and delete the stored access. Deleting your Dashivo account does the same. You can also remove Dashivo's access in your Google account (https://myaccount.google.com/permissions).
• Google's terms apply. Your Google Drive and the copies in it are governed by Google's terms and the Google Privacy Policy (https://policies.google.com/privacy).

(b) iCloud Drive (iPhone only). Your iPhone copies clips into the iCloud Drive of the Apple Account signed in on that iPhone, under iCloud Drive › Dashivo, in a folder for that phone and month. There is no separate sign-in, nothing passes through our servers, and Dashivo holds no access to your iCloud. We keep only your iCloud Drive choices and, for each iPhone, what it reports: when it last ran and reported, how many clips it copied or couldn't copy, how many are waiting on the phone, and the last problem (such as not signed in to iCloud, iCloud Drive turned off for Dashivo, or iCloud storage full). These records are included when you download your data. Your iCloud Drive and the copies in it are governed by Apple's terms and privacy policy. Android phones can't archive to iCloud Drive.

(c) Your copies are yours. Copies in your Google Drive or iCloud Drive are not in Dashivo Cloud, and we can't see, change or delete them. The only files Dashivo removes there are files Dashivo put there itself, and only if you choose to delete archived files after 30, 90 or 365 days; your phone removes them. Disconnecting, ending your plan or deleting your Dashivo account does not delete your archived copies; delete them yourself in Google Drive or iCloud Drive if you want. Retention is in Section 8.

(d) Archived copies are not protected by Dashivo's encryption. Clips in Dashivo Cloud are encrypted on your phone and only you can view them. Archived copies are different: they are ordinary, playable video files, and Dashivo's encryption does not protect them once they are in your Google Drive or iCloud Drive. They are protected only by the security of that Google or Apple account and the protections Google or Apple apply. Anyone who can sign in to that account, or any device or app you have given access to it, may be able to open, copy, share or delete them, and Google or Apple may process them under their own terms (for example to scan for abuse or to comply with the law). Before you turn archiving on, consider whether you are comfortable keeping sensitive footage, such as police stops, accidents or recordings of other people, outside Dashivo's encryption. We recommend a strong, unique password and two-step verification on that account. Turning archiving on is your choice and is off until you turn it on.

(e) Google API Services: Limited Use. Dashivo's use and transfer of information received from Google APIs (Google Drive, and YouTube for live streaming, Section 3.6) to any other app will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements. In particular, we use the access you give us only to provide the features you turned on (copying your clips into the Dashivo folder in your Drive, and running your YouTube live streams) and to show which Google account is connected; we do not use it, or any information from it, for advertising, to build user profiles, to train or improve artificial-intelligence or machine-learning models, or for any purpose unrelated to those features; we do not sell it or transfer it to anyone except as needed to provide those features, to comply with the law, or as part of a merger, acquisition or sale of assets with notice to you; and no person at Dashivo reads it unless you ask us to for support and agree to it, it is needed for security (such as investigating abuse), or the law requires it.

3.11 Our phone line and Dash, our AI receptionist

In short: calls to +1 970 807 0980 are answered by Dash, our AI receptionist, which tells you that the call may be recorded. We keep your phone number, a recording of the call, a transcript of what you and Dash said, and any message you leave, which becomes a support request for our staff. Telnyx carries and records the call and OpenAI runs Dash. Recordings, transcripts and your number are deleted from our call log after 90 days. Dash can make mistakes, does not give legal advice and cannot see any account.

What it is. Dashivo's phone line, +1 970 807 0980, is answered by Dash, an AI receptionist, not a person (Terms Section 25.13). Dash answers general questions from our public FAQ and help articles on dashivo.app and from our Terms of Use and this policy, and can take a message for our team. Dash has no access to customer data: it cannot look up, confirm or change anything about any account, subscription, device, recording or payment, and it never uses the number you call from to look you up.

What you are told. At the start of every call, Dash says that it is Dashivo's AI assistant and that the call may be recorded. If you don't want that, hang up and write to us at [email protected] or through the contact page at dashivo.app.

What we collect.

• Your phone number (the caller ID your phone network sends, unless you withhold it), with the time, length and outcome of the call (for example answered, message taken or limit reached) and our estimate of what the call cost us.
• A recording of the call. Telnyx records the call; a few minutes after it ends, we copy the recording into our own storage, encrypted.
• A transcript of what you and Dash said: OpenAI transcribes your words, and Dash's own words are kept as text.
• Your message, if you leave one: the name, callback number, team and reason you give, and the number you called from. It becomes a support request in our support inbox, and our support team receives an email about it.
• Call counters. To apply the limits on calls (Terms Section 25.13(d)), we count each number's calls and minutes under a scrambled form of the number (a keyed hash), not the number itself.

Our server logs show only a masked form of your number (such as +1******80), never the call's audio or what was said. Please don't tell Dash passwords, codes, card numbers or ID numbers.

Who processes it. Telnyx (Telnyx LLC, USA), our phone provider, carries the call and makes the recording. OpenAI (OpenAI, L.L.C., USA) runs Dash on its realtime voice API: it receives the call's audio to understand you, answer you and transcribe the call, and under OpenAI's API terms, API data is not used to train its models (Section 6). The call's audio goes from Telnyx to OpenAI, not through our servers; our servers receive the transcript, the message and, after the call, the recording. Recordings are stored encrypted (AES-256-GCM) in our cloud storage (Cloudflare R2, USA). Emails to our support team about phone messages are sent through Resend.

Why we use it. To answer your call and the message you leave, to check and improve the quality of our support, to apply the limits on calls and prevent abuse of the line, and to keep track of what the line costs. Where a legal basis is required, it is our legitimate interest in providing support and keeping the line available.

Who can see it. Only our staff with the phone-call permission, in our internal staff tools (Section 3.7). Your number is masked on screen, and showing it in full, opening a call's transcript, and playing or fetching a recording are each recorded in our audit log. A message you leave is handled like any other support conversation.

How long we keep it. In our call log, the recording, the transcript, your phone number and the summary of your message are deleted 90 days after the call (the recording file is then removed from our storage); the rest of the call record (time, length, outcome, cost estimate and the number of the support request, without your number) is deleted after 24 months. A message you leave is kept as a support conversation, 24 months after its last message. Call counters are deleted after 40 days. OpenAI may keep API data for up to 30 days to monitor for abuse, unless the law requires longer (Section 6). Once our encrypted copy of a recording is saved and checked, we delete Telnyx's copy of it, so the recording is not kept at Telnyx after that; if our copy never arrives, we delete Telnyx's copy by the time our call log would have deleted ours.

AI answers. Dash's answers are generated automatically and may be incomplete, out of date or wrong. Dash does not give legal advice, and nothing it says changes our Terms of Use or this policy. Dash cannot put you through to a person: to reach one, leave a message, email [email protected] or use the contact page.

No voiceprints. We do not create voiceprints or identify people by their voice. Recordings and transcripts are used only as described here (Section 16).

Not for emergencies. Dash cannot contact 911 or any other emergency service. In an emergency, call your local emergency number yourself.

3.12 Black Box remote support

In short: if something on your Black Box needs a closer look, Dashivo support can ask to connect to it from your support request. Nothing connects unless you approve, each time, with a passkey or two-step verification. A session lasts up to 3 days, you can end it at any time, and only you can extend it. Support gets a limited set of tools and never your Footage, and everything they run is in a transcript you can read. Remote support is never used for police or legal requests.

(a) Asking and approving. When you ask us for help with your Black Box (for example, with a USB device it doesn't recognize), our support staff may ask to connect to it. A request belongs to one of your support requests and shows who at Dashivo is asking and why. We tell you with a notification in your account, a push notification on your phone and an email. Only the account holder can answer (for a Dashivo Pro Company, its Owners and Admins). To approve, you first confirm it's you with a passkey or two-step verification (an authenticator code, approval on your phone or a recovery code; a password or an emailed code alone is not enough), then choose how long: 1, 2 or 3 days. You can also deny it, and a request nobody answers lapses after 24 hours. Support cannot start a session without that approval, and staff using support access (Section 3.7) cannot approve one for you. Remote support works only on a Black Box running a Black Box OS release that includes it.

(b) What support can and can't do. During a session your Black Box connects out to our servers, as it does for its other reports, to collect support's commands and send back their results; nothing on the Black Box listens for a connection from outside. Support works only through a fixed set of tools, run by a locked support account on the Black Box that has no password, no shell and no administrator (root) rights. With them, support can:

• see technical information about the Black Box: its software release, uptime, load, memory, system storage and temperatures, the state of its Black Box services, the USB devices connected to it and the driver of each, its network interfaces, and Black Box and system log lines;
• change Black Box settings that you can change yourself on dashivo.app (such as device names, camera modes and the order of its connections), which the Black Box applies with its own rules; and
• install or run a support package (for example, a driver fix) that Dashivo has made and signed, for that Black Box or for every Black Box. The Black Box checks our signature itself and refuses anything else.

Support cannot read your Footage, the card or drives your Black Box records to, its encryption keys or credentials, your saved Wi-Fi networks and passwords or its hotspot password, and cannot open a shell or run any other program. Your Footage stays encrypted, and a session gives support no key or other way to open it. Your Black Box keeps recording during the session. A support package runs with full rights on the Black Box, like a Black Box OS update; we make packages only to fix or set up your Black Box, never to read, copy, change or delete Footage.

(c) How long it lasts, and ending it. A session ends by itself at the end of the time you chose, at most 3 days after you approved or last extended it; turning the vehicle off and on does not end it. You can end it at any time on dashivo.app (pro.dashivo.app for Dashivo Pro) or in the App. Only you can extend it, again after confirming it's you with a passkey or two-step verification, and each extension lasts at most 3 days from then. Support can end a session too. When a session ends, our servers stop accepting it at once and we tell you in your account.

(d) Who operates a session. A session is operated by our authorized support staff from our staff tools, or by an AI assistant that we run and direct (Claude Code, made by Anthropic), which acts only when the owner of Angry Owl Labs instructs it. The assistant uses only the same limited tools, only on sessions you approved, and appears in your transcript and in our audit log under its own name, "claude (owner-prompted)". To work, it sends what it reads and types during the session (the commands and their redacted results) to Anthropic, PBC (USA), which runs it as our service provider (Section 6). We are responsible for what the assistant does in a session, as we are for our staff.

(e) What we keep. For each request and session we keep: the Black Box (its serial number and name) and the support request it belongs to; the reason given, who asked and when; who answered, when, where (web, iPhone or Android) and with what kind of confirmation (for example "passkey"), and the length chosen; when the Black Box connected and last checked in, and the public half of the key it made for the session; every command, who ran it (a staff member's name or the AI assistant) and when, and its result and output after redaction; the support packages sent and installed; each extension; and when and how the session ended. Before any output leaves your Black Box, and again on our servers before it is stored, we remove anything that looks like a key, token, password or other credential, email addresses, positions (latitude and longitude), Wi-Fi network names, and USB and disk serial numbers, and network hardware addresses show only their maker's part. Redaction works by recognizing patterns, so it may miss something, and log lines can still include, for example, device names or addresses on your local network. When a session ends we add a short note to your support request with how it ended, how many commands ran and where to read the transcript. Each request, approval, extension, end, command (its name and first arguments, never its output) and console connection is also recorded in our audit log. Your Black Box keeps its own list of the support packages installed on it.

(f) Who can see it. You can read the transcript on the web and in the App while the session runs and afterwards, for as long as we keep it (Section 8); for a Dashivo Pro Company, its Owners and Admins can. Our support staff can see it in our staff tools.

(g) Never for police or legal requests. Remote support is only ever used to help you with your Black Box. It is never used for police or legal requests, or to obtain Footage or other information for anyone; those requests are handled only as Section 7 describes.

(h) Dashivo Pro. For a Company's Black Box, the Company's Owners and Admins approve, extend and end sessions and read their transcripts, and we handle a session's information on the Company's behalf, like its other Dashivo Pro information (Section 3.8(a)).

(i) Why. To give the support you asked for with your Black Box, and to keep it and our services secure. Where a legal basis is required, it is performing our contract with you and your consent to each session.

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 everyday and evidence clips for the Company, and store Cloud data, invite Trusted Contacts, deliver Arrest Release packages, alerts and shares, and check your App PIN during a police stop;
• 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, Dashivo Pro Support, Section 3.9, our phone line, Section 3.11, and Black Box remote support, Section 3.12), and investigate and fix bugs;
• handle Black Box preorders and reservations placed before we stopped selling hardware, including their cancellations and refunds;
• 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;
• understand roughly where our customers are, from the general area of each account (Section 3.3), so we can see which areas our outreach and marketing are reaching and plan where to offer Dashivo; 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, and in understanding roughly where our customers are from the general area of each account (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 software, 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 only report it sends on its own is the optional crash report described in Section 3.3, and only if you turn it on. (When you sign in, we keep the general area your internet connection comes from, never your phone's GPS location, to know roughly where our customers are, Section 3.3; it is never used for advertising.) 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). The only recordings our staff can play are recordings of your own calls to our phone line (Section 3.11) and of your own Dashivo Pro Support calls and chats (Section 3.9). 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. Recordings of calls to our phone line and of Dashivo Pro Support are not used to create voiceprints or to identify anyone by voice (Sections 3.9 and 3.11).
• 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.

Our Online Services, including our application servers and databases, run on servers owned and controlled by Angry Owl Labs in the United States. Files uploaded to our Online Services are stored with Cloudflare, Inc.'s R2 storage service in the United States. Network traffic to and from our Online Services is routed through and protected by Cloudflare's network. Dashivo Pro routing (Valhalla), address search, map tiles (Protomaps) and text-to-speech run on servers owned and controlled by Angry Owl Labs in the United States, which our Online Services reach through Cloudflare's network. We store personal information only in the United States. Those services, the call relay (TURN) and real-time message delivery run on software we operate ourselves, so those requests are not sent to an outside mapping, speech or messaging company. Our service providers may process personal information only on our instructions. We disclose personal information only:

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

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 connect YouTube and stream a police stop to your channel (Section 3.6), when your phones archive clips to your own Google Drive or iCloud Drive (Section 3.10), 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), other than recordings of support calls (Sections 3.9 and 3.11).

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, with Maximum privacy we can't open your Cloud footage either, 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. Black Box remote support (Section 3.12) is never used to obtain it, or anything else, for a legal request.
• Dashivo Cloud footage (personal accounts): it is encrypted on your phone. With Maximum privacy we have no key, so we can provide only the encrypted files, which we cannot open, and the service information listed in Section 2.2. With Standard protection we hold a locked copy of your account's key and would use it only for a valid search warrant, telling you unless the law or a court stops us.
• Footage in Dashivo Pro cloud storage (everyday and 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 signs it out at once and deletes your account data 30 days later, unless you keep it. For Dashivo Pro, several periods are the Company's choice.

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).

If we close an account because it broke our Terms of Use (Terms Section 30.3), we keep a scrambled (keyed-hash) copy of its email address and of its Apple and Google sign-in IDs after the account is deleted, never the address itself, only to stop the same person signing up again (Terms Section 4.3(d)). We keep it for as long as the closure lasts and delete it if we lift it.

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 (other than recordings of support calls, Sections 3.9 and 3.11);
• separation: our databases are not reachable from the internet, and Dashivo Pro data is kept in a database and file storage separate from personal Dashivo accounts; and
• keeping our software up to date.

Our infrastructure providers. As each provider stated on October 4, 2026: Cloudflare (network, security and R2 storage) has a SOC 2 Type II report and ISO/IEC 27001, 27018 and 27701 certifications for its platform; and OpenAI (the Dashivo Pro Support assistant and Dash, our phone receptionist) is ISO/IEC 27001 certified for its API. These cover the providers' own services, not Dashivo: our application servers and databases run on hardware we operate ourselves, and Angry Owl Labs itself is not SOC 2 audited or ISO certified.

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: "Always" on iPhone, "All the time" on Android), motion (Motion & Fitness on iPhone), notification access, local network and storage permissions in your phone's settings. Some features will not work without them.
• Audio. Turn "Record sound" on or off in the App's settings.
• Parked Guard. Off until you turn it on. In Settings › Parked mode you can turn it off, turn its sound triggers off, keep "Sound on clips while parked" off (the default), turn off "Tell me if the car moves" and "List the bumps when I'm back" (iPhone), and turn off "Alerts from my other phones".
• 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, or recording off shift; ending your shift (or stopping the recording) stops sharing and deletes your last position. Off shift and not recording, nothing is collected. You can untick the location line in Settings › Privacy & security; sharing then stays off until you next start a shift.
• Community Reports. Opt in or out at any time in the App (when sharing launches).
• Dashivo Cloud. Choose what to upload, delete Cloud clips (they go to Recently deleted for 30 days, where you can restore them or delete them for good; protected footage only on the web, Section 2.2), and add or remove Trusted Contacts or change their level of access at any time. Turn archiving to Google Drive or iCloud Drive on or off, change what it archives, or disconnect Google Drive at any time (Section 3.10).
• Account protection. Add passkeys or two-step verification, review your sign-ins, forget trusted browsers 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. Footage in Dashivo Cloud is deleted as Section 2.2 describes.
• 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.
• Black Box remote support. Approve or deny each request, choose how long a session lasts, extend it or end it at any time, and read its transcript, under Support access for your Black Box on dashivo.app or in the App (for Dashivo Pro, the Company's Owners and Admins).
• 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 in the App, on our website or by email. You're signed out at once and have 30 days to change your mind; then we delete your account data, except what we must keep, and email you to confirm. Your footage on your own devices is not affected.

11.1 How. You can delete your account at any time in the App (Settings › Profile › Delete account), or 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. When you ask, your account is signed out on every phone and browser at once and scheduled for deletion 30 days later. During those 30 days no one can sign in to it, nothing uploads to Dashivo Cloud, your cloud clips are not shown to anyone, and the people you shared the account with lose access to it. We email you when we receive the request. To keep your account, sign in and choose "Keep my account", or use the link in that email, before the 30 days end; nothing is lost. After 30 days the deletion is final and cannot be undone, and we email you to confirm it. We then 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, trusted browsers, purchase entitlements, your billing details (name, address, tax ID and billing email), Driver Score summaries, the general area of your account, Trusted Contacts, and your Dashivo Cloud clips and any other Cloud data (queued for erasure from storage), and we tell the people you shared the account with. 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 and purchase records described in Section 8, which hold no name, email address or street address. If you used Sign in with Apple, we ask Apple to cancel Dashivo's Sign in with Apple authorization and then delete the token we held for it (Section 3.3). If you connected YouTube or Google Drive, we revoke our access at Google and delete it, and we delete your live streaming and archive records (Sections 3.6 and 3.10); clips already archived to your own Google Drive or iCloud Drive stay there. 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. A Dashivo Cloud subscription bought on dashivo.app is cancelled in your account's Billing page.

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. The same 30-day hold applies to a Dashivo Pro sign-in. The only Owner, or the primary Owner, of a Company must first hand ownership to another Member or ask us to close the Company (Section 3.8(l)). A Driver without an email address can use "Request deletion" in the Dashivo Pro app; we carry the request out within 30 days if the Company has not removed the Driver by then.

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 location shared on shift and while recording off shift, and of driving paths and is responsible for any notice and consent the law requires (Section 3.8(b)); drivers give consent to driving paths in the App's sign-in acceptance 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.

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. The paid Dashivo App, the Dashivo Cloud storage add-on 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:

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. Dashivo Pro Support calls (Section 3.9) and calls to our phone line (Section 3.11) are recorded and transcribed, but we do not create voiceprints or identify people by their voice. 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 and while you record off shift: the latest position, and driving paths unless the Company turns them off, 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: the Dashivo App is offered in many countries, but your information is stored in the USA, and times are shown in your own time zone.

17.1 The Dashivo App is offered in many countries; Dashivo Cloud is offered only in the countries listed in Section 27.2 of our Terms of Use, and Dashivo Pro and Dashivo Pro Support only in the United States. Wherever you use Dashivo, the information we hold is stored in the United States: our Online Services and PostgreSQL databases run on servers we operate in the United States, with a standby copy of each database on a second server we operate in the United States; uploaded files (such as Dashivo Pro everyday and evidence clips, attachments, voice messages, Dashivo Pro Support recordings, phone line call recordings, exports and our own encrypted nightly database backups) are stored with Cloudflare R2 in the USA; and Dashivo Pro routing, address search, map tiles and text-to-speech run on our own servers in the USA. Traffic to our servers passes through Cloudflare's global network, which may handle it at a location near you before it reaches our servers. We do not store personal information outside the United States. The AI assistant in Dashivo Pro Support runs on OpenAI's API, which processes the conversation to produce answers (Section 3.9). Calls to our phone line are carried and recorded by Telnyx and answered by Dash on OpenAI's API (Section 3.11). When the AI assistant operates a Black Box remote support session, Anthropic processes what it reads and types in that session (Section 3.12(d)).

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 App and the account portals ask you to accept the new version before you continue.

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

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

© 2026 Angry Owl Labs LLC and its licensors.

Back to top