Skip to content
CommaView
Features How it works Install guide Team Sign in Join the beta
Menu
Features How it works Install guide Supported forks Team Sign in

Privacy Policy

Last updated November 16, 2026

CommaView is an Android app that shows your comma device’s Live View on your phone over your own network, with a small runtime on the comma. This policy explains what we collect, why, who helps us run CommaView, and the choices you have. Questions: support@commaview.com.

What stays on your devices

Live View video, recordings, drives, places and your comma’s data go from your comma to your phone over your own network. Recordings you save, live copies included, stay on your phone until you delete them, or share them yourself.

They leave your phone only when you choose:

  • A report or a recording you send us (Reports you send, and Recordings you send, below).
  • A drive you contribute to car detection, with a tap or automatically (Contributing to car detection, below).
  • A drive you stream (Going live).
  • Where your car is and where it’s going, when you search for a place, ask for a route or show a map (Navigation, and Who helps us run CommaView).
  • The daily totals of the commas you put on the leaderboard (The leaderboard).
  • Browser View’s code, the ports it serves on and your phone’s address on your car’s network, while you show Live View in your car’s browser (What we collect).
  • Which driving software your comma runs, and whether Live View plays on your phone or car screen, if you answer Send to Help improve CommaView (What we collect).

Diagnostics stay on your phone too. So that a report can say what happened, the app keeps its logs and counters from your last 10 drives, and navigation search counts. They leave your phone only in a report you send. Turn off Keep diagnostics on this phone (Settings › Support & diagnostics) to keep only the history of recording errors; Clear local diagnostic data, on the same page, deletes them.

What we collect

  • Account: your name, email address and picture from the way you sign in (Google, or a code sent to your email), and the ID our sign-in provider gives you.
  • Beta waitlist: your email address, your car and comma setup if you tell us, how you found us (the page or campaign link you came from) and, if you tick the box, your agreement to receive CommaView news.
  • The app on your phone: when you sign in to the app, the name you give that phone, the app’s version and a key the app makes, so the app stays signed in and we can offer you updates. We keep which releases you download, and the days the app reached us from your phone: the days it renewed its sign-in and the days it was open, with its version.
  • Your agreement to changes: when the app shows you that this policy or the terms changed and you tap Agree, which version you agreed to and when, kept with your account.
  • Your comma’s driving software: only if you answer Send to Help improve CommaView, which the app asks once, after its terms, and only while you’re signed in. When the app installs, updates or connects to CommaView on your comma, it then tells us which driving software the comma runs (its repository, such as github.com/sunnypilot/sunnypilot, its version and what it’s built on, which comma model it is, and whether CommaView could install on it or which check stopped it), with the app and runtime versions. It’s kept with your account, and your comma is identified only by a one-way key made from its ID, so we can count commas without keeping which comma it is. You can turn this off in the app (Settings › Privacy & sharing › Help improve CommaView).
  • Whether Live View plays on your phone or car screen: only if you answer Send to Help improve CommaView, and only while you’re signed in. At most twice for each version of the app, after you use Live View, the app tells us whether its video played, how many frames a second it showed, which video decoder it used (and whether it’s the phone’s hardware one) and how many times the decoder failed, with your phone’s manufacturer, model, board and hardware name, its Android version, the size and density of the app’s window, your text size, Screen edges’ margins, and the app and runtime versions. It’s kept with your account and that phone, so we can see which phones, head units and car screens Live View works on and ask you about one. Never your video, drives, places or network addresses, or which comma it is. You can turn this off in the app (Settings › Privacy & sharing › Help improve CommaView).
  • Browser View: when you show Live View in your car’s browser, your phone gets a name of its own under commaview.app, made of eight random characters (such as k7f2q4xm.vpn.commaview.app), and a certificate for it from Let’s Encrypt, so the car’s browser can trust the connection. The phone makes the certificate’s key and it never leaves the phone. We keep that name and when its last certificate was issued, with your phone. Certificates are public: every certificate’s names are listed in Certificate Transparency logs, for good, but the name says nothing about you, your car or your comma. While Browser View runs, the app also tells us its code, the ports it serves on, whether CommaView’s VPN address is on, and your phone’s address on its hotspot or Wi-Fi (a private address, not your internet one), so that commaview.app/<code> can open Live View in your car. Anyone who has the code can see these, and your phone’s commaview.app name, while Browser View runs, and for up to 2 hours after it stops unexpectedly (when the app is closed before it can say so); none of them opens anything without your phone’s hotspot or Wi-Fi.
  • Crash reports from the app: only if you answer Send to Help improve CommaView. When the app crashes, stops responding or hits an error, a report of where in its code it failed and which screens were open just before, the app’s version and the runtime version your comma runs, and your phone’s model, Android version and basics such as its screen size and language. When setting up a comma fails, a report of which setup step it stopped at and what kind of problem it was (such as the comma not accepting the SSH key); while you’re signed in, it can also say which driving software your comma runs (a listed fork’s repository, never one CommaView doesn’t list) and the installer’s error lines, with repositories and paths on the comma removed, and a setup that worked can say CommaView couldn’t add its view to your comma’s driving software yet. Problems the app works around are reported too, each with what kind of problem it was, where it stopped and any error code or count: a runtime update, uninstall or repair your comma refused or that failed, an overlay pack update that was refused or failed, an app update that failed, Live View giving up, losing your sign-in, your comma’s SSH host key changing (only its key type), and something the app saved on your phone that it can no longer read or save. A failed runtime update, uninstall or repair also gives the first line of the installer’s answer, such as its exit code, and while you’re signed in its error lines, with repositories and paths on the comma removed. None of these say which comma, network or account. Turning Help improve CommaView off stops them and deletes any the app hasn’t sent yet.
  • Error reports from our websites: when a page on commaview.com or my.commaview.com hits an error in your browser, a report of where in our code it failed, the page’s path and version, your browser type, and the site’s own requests just before it. These have no switch. Neither kind of report holds your video, drives, places, network addresses, names, email address, account details or the links that brought you to our website.
  • Feedback: the problems and ideas you send from the app (Reports you send, below), with our replies and yours about each, and the feature requests and votes you add to the feature board on my.commaview.com. Other members see the requests on the board, not who suggested them.
  • Technical: basic logs of requests and errors on our website and account service, including device and browser type, to keep them running and secure. The app, and the runtime’s installer on your comma, ask our website which release is current, and the app asks it for your car’s picture by your car’s model, never its VIN.

Reports you send: only when you tap Send in the app’s Send to CommaView, which opens from Settings › Support & diagnostics › Report a problem or send an idea, from a failure’s Report, or from a recording’s Send to CommaView. You choose a problem or an idea, and say what happened. It comes to us with the app and runtime versions, your phone’s model and Android version, which comma you have (comma 3, comma 3X or comma four), which driving software your comma runs (its repository, whether CommaView supports it, which kind it is, and the branch and commit it’s on), its openpilot version and driving model, and a line on whether CommaView reads the comma’s data (which of its data it reads, or why it can’t); one sent from a recording carries what Recordings you send lists instead. You choose what goes with it, and See shows exactly what each part holds before you send:

  • This phone’s diagnostics, on for a problem: the app’s logs and counters from the drive (the video stream, drawing, the connection and recording errors), the history of recording errors, the navigation search counts (Navigation, below) and, while you’re signed in, the leaderboard’s status: whether you’re on it, which of your commas count from this phone (numbered, not named) and what each last answered, how many drives wait to be sent and why, and what we did with the last ones. Never a drive’s distance, a place or a key (The leaderboard, below).
  • Your comma’s logs, on for a problem when your comma is in reach: CommaView’s logs, counters and settings on the comma, which openpilot processes stopped and why, and the comma’s out-of-memory warnings. An up-to-date runtime on the comma takes out GPS coordinates, VINs, Wi‑Fi names, public IP addresses and tokens first, and keeps only the last six characters of its dongle ID and serial number.
  • A recording, and Surround’s log, when you send from a recording (Recordings you send, below).

Diagnostics and logs never include video. Save as a file makes the same bundle, without a recording’s video, for you to share yourself: it goes only where you send it.

Replies: when we answer a report, we email our reply to your account’s email address, with the report’s first line, and show it with your report on my.commaview.com (Your feedback), where you can read the conversation and answer until we close it, and reopen it for 30 days after. The app lists your reports in Settings › Support & diagnostics and opens them there. The conversation is kept with your report (How long we keep it).

Recordings you send: only when you choose Send to CommaView on a recording in the app (where it’s available to you) and leave This recording on. Your phone first downloads, from your comma, the road and wide road video and the drive’s full log for the minutes the recording covers. It keeps only part of the log, and sends us:

  • The drive’s video from your comma’s road and wide road cameras, in the minute-long pieces that cover the recording. It shows the road around your car, including other vehicles and people on it.
  • Your comma’s log for those minutes, kept to what we study: the car’s speed, steering and controls, openpilot’s view of the road and its plans, the radar, the cameras’ calibration and state, the comma’s state and clocks, and the car’s GPS location along the drive. Your phone takes out the rest first, such as your car’s details (its VIN among them), your comma’s identity and the driver camera’s state. Sent to improve car detection, it keeps what a contribution’s log keeps instead (Contributing to car detection, below).
  • The attachments you leave on (Reports you send, above), and Surround’s log if you leave it on: what Surround detected around your car and the roads it drew from offline maps, if Surround was showing.
  • How fast your phone or head unit runs CommaView’s car detectors, with its model, chip and Android version.
  • About the recording: when it was made and how long it ran, how the app recorded it, the drive’s name on your comma, the last six characters of your comma’s dongle ID and serial number (never its name or address), which driving software it runs, the app version, your phone’s model and Android version, the note you write, and whether you let it improve car detection.

It never includes the driver camera, sound, a live copy, your car’s full VIN or video from other drives. Your phone deletes what it downloaded for it once it’s sent; the drive stays on your comma.

Car detection: a recording you send also goes into CommaView’s training collection, for good, only if Use recordings I send to improve car detection was on when you tapped Send (Settings › Privacy & sharing › Car detection, or under This recording in Send to CommaView). It’s off until you turn it on, and turning it off later doesn’t take back a recording already sent with it (Contributing to car detection, below). Recordings sent without it are used only to look into what you reported and how CommaView did on that drive.

Where it’s available to you, Diagnostics can also send a Surround drive log on its own: what Surround detected and drew during a Live View session, how fast your phone ran its detectors, and your note, with the app version and your phone’s model and Android version. Never video.

Contributing to car detection

Where it’s available to you, you can give your drives to car detection. A drive you contribute becomes a permanent part of CommaView’s training collection, much as comma.ai keeps drives to train openpilot: it can’t be removed later, and it stays after you delete the recording or your account. The app asks you to agree to this before your first contribution. A drive goes there three ways:

  • Contribute to car detection, on a drive in Recordings: that drive.
  • Contribute drives automatically (Settings › Privacy & sharing › Car detection): any recent drive your comma still has, not only those you recorded, one minute-long segment at a time, the newest drives first, within a daily allowance. A long drive can go over several days.
  • Use recordings I send to improve car detection: a recording you send us (Recordings you send, above).

Contributions upload only on the networks you allow: by default, Wi-Fi networks you choose, which your comma names, as a phone can take a hotspot for home Wi-Fi. You can choose any Wi-Fi, or any network including mobile data, instead. The networks’ names stay on your phone: they’re never sent to us. While a drive is being contributed, your comma keeps it from openpilot’s deleter (unless the comma runs short of space), and comma’s own uploader skips it, so comma connect gets none of its files until the contribution is done or stopped.

A contribution is the whole drive, or the whole recording, with nothing cut from it:

  • Its video from your comma’s road and wide road cameras, which shows the road around your car, including other vehicles and people on it.
  • Its log, including where the car went, from start to end: what a recording’s log keeps (above), and what openpilot’s screens are drawn from besides, such as what openpilot asked the car to do, its alerts, what it learned about how your car steers, and its settings for your car, with the last six characters of the VIN (its serial number) masked. For some driving software, such as sunnypilot and StarPilot, its own messages of those kinds go too.
  • Surround’s log, if Surround was showing.
  • Its details: when it started and how long it ran, which driving software your comma ran, the app and runtime versions and, for a recording, the rest of About the recording (above) except your note. Your comma’s name is left out, and its IDs and address are masked.

It never holds the driver camera, sound, your note, the app’s diagnostics or your comma’s logs, and nothing in it names you, your account or your comma: with it we keep only what it holds, when and how long the drive was, the drive’s name on your comma, the app and runtime versions, your phone’s model, which driving software your comma ran, and which upload it came from.

That upload is kept with your account, like any recording you send, until 180 days pass, you ask us to delete it, or you delete your account (How long we keep it). Deleting it deletes that copy, not the contribution. The contribution names neither you nor your comma, but a drive’s route and video can show where you drive. Turning contribution off stops what hasn’t started sending; what’s sent stays.

How we use it

  • To confirm your place on the beta list, send your invite and let you in.
  • To give you the app, keep it signed in, and offer you its updates.
  • To see how many people use CommaView, how often, and which versions of the app they have.
  • To read your reports and feedback, answer you and fix problems.
  • To make place search work in more languages, from the navigation search counts in reports you send us.
  • To see which phones, tablets, head units and car screens Live View works on, list the ones that do, and ask the people who have one which car and unit it is.
  • To decide which driving software (openpilot and its forks) CommaView supports next, from what people’s commas run.
  • To look into the recordings you send: what went wrong, and how CommaView’s features, such as Surround’s car detection, did on that drive, so we can fix them.
  • Only for the drives in our training collection (Contributing to car detection): to train and test the models CommaView uses to recognise what’s on the road and place it around your car, and to build and test how CommaView shows what your driving software sees.
  • To plan your routes, and to run the leaderboard for the people on it.
  • To show you in the app when this policy or the terms change, and keep a record that you agreed.
  • To send CommaView news, only if you ticked the box.
  • To keep CommaView working and secure, prevent abuse and fix problems.

We do not sell your information and do not use it for advertising.

Who helps us run CommaView

We share information only with companies that run parts of the service for us, and only what they need:

  • Auth0 (Okta): sign-in.
  • Google Cloud: runs the account service, stores the app downloads, the comma runtime’s releases, support bundles, the recordings you send and the training collection, runs the training of CommaView’s models on it, and keeps logs.
  • Neon: our database.
  • Sentry: receives crash and error reports from the app, commaview.com and my.commaview.com.
  • Resend: sends email, such as your waitlist confirmation, your invite and our replies to your reports.
  • Cloudflare: delivers our domains, passing each request to my.commaview.com on to our account service; serves our website, the runtime’s downloads and, from a copy it keeps, which release is current; runs CommaView’s route service (Navigation, below); checks that the app’s requests come from a phone that’s signed in, against the list of signed-out and removed phones we keep with it; serves Browser View’s short links (commaview.app) and holds the records that show Let’s Encrypt a phone’s Browser View name is ours; holds the leaderboard’s live state (the public names and commas on it and their daily totals, kept in the United States), which it passes to our database every few hours; and checks that sign-ups come from people, not bots (Turnstile). It sees the IP address of the browser, phone or comma that asks: installing or updating the runtime downloads it from commaview.com, for example.
  • Let’s Encrypt: issues the certificates for Browser View’s names (What we collect). It gets the names and the certificate’s public key from us, never your account, and lists every certificate publicly.
  • Stadia Maps: plans Navigation’s routes, asked by your phone (Navigation, below). With your own Stadia key, Stadia acts for you under your own Stadia account, not as our provider.
  • Buy Me a Coffee, with Stripe: if you support CommaView at buymeacoffee.com/commaview, they take your payment, and we never see your card. Buy Me a Coffee tells us your name, email, the amount and any message you leave, which we use only to thank you and keep our accounts. Supporting unlocks nothing in the app.

Your phone or comma also reaches these services itself. Each sees the IP address it asks from, and what it asks for:

  • OpenFreeMap: if you turn on Vehicle location in the app, your phone downloads the map around your car from it, for the map on Home and on the Vehicle location page. A phone that can’t draw OpenFreeMap’s map downloads it from OpenStreetMap instead. Your phone keeps what it downloaded, out of backups, and deletes it when you turn off Vehicle location.
  • OpenFreeMap, komoot (Photon) and FOSSGIS (Valhalla): if your account has Navigation, the map in Live View, its place search, and its routes when the app isn’t signed in (Navigation, below).
  • map-data.pfeifer.dev (pfeiferj’s offline maps): if you download offline maps, your phone downloads the regions you choose from it.
  • comma.ai: the CommaView runtime on your comma asks comma.ai’s API for that comma’s driving totals (the past week and all time), signed in with the comma’s own comma.ai identity, so comma.ai knows which comma asked. That sign-in never reaches us. The totals go to your phone, and the all-time distance to us only for the leaderboard.
  • GitHub: only an installer set to use a release repository other than CommaView’s own asks GitHub for its releases and downloads them from it, and GitHub then sees your comma’s IP address. CommaView’s own installs and updates come from commaview.com.
  • YouTube, or another streaming server you choose: when you go live (Going live, below).

We may also share information when the law requires it or to protect someone’s safety.

Going live

Go live streams what Live View shows, from your phone or head unit straight to YouTube or another streaming server you choose. The stream doesn’t pass through us and we don’t keep a copy. If you turn on Save each stream, the app keeps a live copy of it on your phone or head unit, like any other recording.

  • Driver camera: the stream shows what Live View shows, so the driver picture-in-picture is in your stream whenever it’s on, and anyone watching sees the driver and front passengers. Turn it off in Live View to keep the driver camera out.
  • Microphone: off unless you choose one in the app (Settings › Live streaming): your comma’s, or your phone’s or head unit’s, including a car’s hands-free microphone over Bluetooth. Its sound goes only into your stream, or a live copy kept on your phone or head unit (Record’s live copy, or Save each stream): CommaView never sends it to us. Using your comma’s microphone doesn’t turn on openpilot’s own audio recording or upload.
  • Signing in to YouTube: CommaView uses YouTube API Services. If you sign in to YouTube in the app, it gets permission to manage your YouTube live streams, and uses it only to show which channel you’re signed in to, set up your stream and its broadcast, start and end it (or remove one that never started), and show you its watch link. That permission and your broadcast’s details stay on your phone or head unit; they aren’t sent to us. Google’s Privacy Policy covers what YouTube receives (https://policies.google.com/privacy), and YouTube’s Terms of Service apply to using YouTube (https://www.youtube.com/t/terms).
  • Disconnect YouTube in the app at any time, which deletes that permission and your broadcast’s details from the device, or remove CommaView’s access in your Google Account (https://myaccount.google.com/permissions).
  • Stream key: if you go live with a stream key instead, the key is sealed on your phone or head unit, kept out of backups and sent only to the server you set.

Navigation

Where your account has it, Navigation finds places and routes from your phone or head unit. Its guidance is shown on your screen only: nothing is sent to your comma or your car.

  • Searching: what you type in Where to? or say to the map in Live View, your comma’s position so that places near it come first, and your phone’s language when it’s English, French or German, go from your phone straight to Photon, komoot’s OpenStreetMap search, which sees them and your phone’s IP address.
  • Speaking a destination: when you tap the map’s microphone, your phone’s microphone listens until you stop speaking (Android asks first). Your phone’s speech service turns the sound into words: on the phone where it has your language offline, otherwise by sending the sound to its provider, Google on most phones. CommaView gets only the words and searches them as typed ones; it never records or keeps the sound.
  • Search counts: while Keep diagnostics on this phone is on (Settings › Support & diagnostics), each place search adds one to a count of its kind: your phone’s language, the search’s writing system (such as Latin letters or Chinese characters) and length, whether your comma’s position went with it, how many places came back or why it failed, and how long it took. The counts never include what you typed, places, positions, when you searched or any ID. They stay on your phone or head unit with its diagnostics, out of backups, and never go to Photon. They leave your phone only in a report you send with This phone’s diagnostics on, and See shows you their exact text first. Turning diagnostics off, or Clear local diagnostic data, deletes them.
  • Routes: each time a route is asked for (when you start, and when you leave the route), your phone sends Stadia Maps where your car is, which way it’s going and where you’re going, with the language and units for the directions. With our key, Stadia sees the route request and your phone’s IP address, not your name, email address or account. The request carries our Stadia key, which our service gives your phone once your account’s sign-in shows it has Navigation. The key is sealed on your phone or head unit, kept out of backups, diagnostics and support bundles, and deleted when you sign out. Earlier app versions send the request to CommaView’s route service instead, which keeps nothing about it and asks Stadia, which then sees the service’s address, not your phone’s; that service is being switched off, and those versions are asked to update. If the app isn’t signed in, your phone asks FOSSGIS’s public Valhalla server (valhalla1.openstreetmap.de) instead, which sees the request and your phone’s IP address. If you add your own Stadia Maps key in the app, your phone or head unit sends these route requests straight to Stadia Maps with your key instead, under your own Stadia account and Stadia’s terms and privacy policy: Stadia can link them to your Stadia account, and CommaView never receives your routes. Your key is sealed on your phone or head unit only, kept out of backups, diagnostics and support bundles like ours, never sent to CommaView, and deleted when you clear it or sign out.
  • Mainland China: Navigation (search, routes and guidance) is off while your comma or phone is in mainland China. The app decides that on your phone, from your comma’s position or your phone’s mobile network, and sends nothing to find out or from there.
  • The map in Live View: while a trip is guided, and without one once you turn on Map in Live View, your phone downloads the map around your car and its lettering straight from OpenFreeMap, which sees your phone’s IP address and that part of the map. Your phone keeps what it downloaded (up to 50 MB), out of backups, and deletes it when you turn off Vehicle location.
  • Your places: Home, Work and your recent destinations stay on your phone or head unit. They aren’t sent to us and are kept out of backups. A replay made after a drive doesn’t show Navigation.

The leaderboard

The leaderboard ranks commas by the distance each one recorded. You’re not on it unless you join in the app, with a public name you choose, after reading what’s shared.

  • What’s sent: each comma you add signs its own daily totals with a key of its own, and your phone passes them on: for each UTC day it drove, the distance, the driving time and the number of drives. With them come which comma it is (comma four, comma 3X or comma 3) and, when the comma has it, the all-time distance comma.ai’s records give it, which the comma asks comma.ai for itself. When you add a comma, it signs to prove it’s yours, and sends a one-way code it makes from its ID, so the same comma is known after a reinstall.
  • Never sent: positions, routes, addresses, when drives started or ended, video, your car or its VIN, or your comma’s dongle ID.
  • What members see: CommaView beta members, signed in, see your public name and rank and, for each comma you add, the name you give it, which comma it is, the distance it recorded this week, last week and all time, and comma.ai’s all-time figure for it. Driving time and drive counts stay private. We can see whose entry is whose, to hide a name that breaks the rules.
  • Signed history: importing a comma’s earlier days (the distance it recorded each day before it joined, up to 62 days back) is a separate choice you agree to for each comma.
  • Leaving: leave whenever you like in the app. Leaving, or deleting your account, deletes your public name, your commas’ names and keys, every day total, any history you imported and your achievements.

Where your information is stored

In the United States (Google Cloud and Neon, both in Virginia, and Sentry). If you live elsewhere, your information is transferred to and processed in the United States.

How long we keep it

  • While your account exists. When you delete your account (on my.commaview.com), we delete it right away with what we keep about it: your waitlist entry, your phones, feedback and votes, the support bundles and recordings you sent, your place on the leaderboard, which driving software your commas ran, and which versions of this policy and the terms you agreed to. Drives you contributed to car detection stay (below).
  • A waitlist entry stays until you remove it (every waitlist email has a link) or delete your account.
  • If you give us your email address but don’t finish signing up for the waitlist, we delete it after 30 days.
  • Feedback, with our replies and yours about it, stays while your account exists, or until you ask us to delete it at support@commaview.com. A feature request stays on the board after the idea it came from is deleted, and the requests you suggested stay after you delete your account, no longer linked to you.
  • Support bundles and recordings you send are deleted 180 days after you send them, or sooner when you ask us to delete one or delete your account. Either way their files are gone at once: we keep no copy to restore them from. Only a contribution’s copy in the training collection stays (below).
  • Drives you contribute to car detection are kept for good in our training collection, with what we make from them to train and test our models: we don’t delete them, and deleting the recording you sent, or your account, doesn’t remove them. Turning contribution off stops it for the drives from then on.
  • The days the app reached us from your phone are deleted after 90 days.
  • Which driving software your comma runs is deleted with your account, and once the app hasn’t reported it for a year.
  • Whether Live View plays on your phone or car screen is deleted with your account, and once the app hasn’t reported it from that phone for a year.
  • Your leaderboard name and totals stay while you’re on it; leaving deletes them.
  • Browser View’s name for your phone, and when its last certificate was issued, stay while your account exists, after you sign that phone out too. Its certificates stay in the public Certificate Transparency logs, which nobody can delete from.
  • The code, ports, VPN setting and private address Browser View last sent are deleted 30 days after Browser View last ran on your phone, or with your account. Until then the code stays your phone’s; after that another phone can take it.
  • Our record of each certificate issued for Browser View (which phone, and when), which we keep to stay within Let’s Encrypt’s limits, is deleted after 90 days.
  • Our server logs are kept for about 30 days, and crash reports for at most 90 days.
  • Your sign-in record at Auth0 stays until you ask us to remove it at support@commaview.com.
  • What we delete from our database can still be restored from its history for up to 6 hours. Then it’s gone.

Your choices and rights

  • Choose what leaves your phone in the app, in Settings › Privacy & sharing: Help improve CommaView; under Car detection, Use recordings I send to improve car detection, Contribute drives automatically and the networks contributions upload on; and, in Settings › Support & diagnostics, Keep diagnostics on this phone.
  • Ask us at support@commaview.com what you’ve sent, or to delete any of it with its files; deleting your account deletes all of it. A drive you contributed stays in the training collection.
  • Leave the leaderboard in the app whenever you like.
  • Stop our emails, or take yourself off the waitlist, with the link at the bottom of any of them.
  • Delete your account at any time in the app (Settings › Account) or on my.commaview.com.
  • Ask us for a copy of your information, to correct it or to delete it: support@commaview.com.

Depending on where you live (for example Canada, the European Union, the United Kingdom or California) you may have further rights. We will answer within the time the law requires.

Children

CommaView is not meant for children under 13. If you are under 18, use it with a parent’s or guardian’s permission.

Security

Your information travels encrypted, access to it is limited to the systems and people that need it, and we use providers with strong security practices. No system is perfectly secure; tell us right away if you think your account has been misused.

Changes

When this policy changes, we update the date at the top and list what changed here. We show you important changes in the app, not by email, and you agree to them there.

November 16, 2026:

  • A contribution names neither you nor your comma, but a drive’s route and video can show where you drive.
  • Crash reports also cover problems the app works around (updates, Live View, sign-in, saved data), never which comma, network or account.
  • Browser View gives your phone a random commaview.app name with a public certificate (Let’s Encrypt); we keep the name with your phone.
  • Browser View sends its code, ports and private address so commaview.app/<code> finds your phone; we delete them 30 days after it last ran.

November 12, 2026:

  • You can add your own Stadia Maps key in the app. Your phone then asks Stadia for routes with it, under your Stadia account and terms.
  • Stadia can link those routes to your Stadia account. CommaView never receives them, or your key, kept on your phone or head unit.

November 11, 2026:

  • From the app version that adds it, your phone asks Stadia Maps for routes itself, with a key we give it.
  • Stadia then sees the route and your phone’s IP address, not your name, email or account.
  • Navigation is off in mainland China, decided on your phone. Nothing is sent to find out.

November 10, 2026:

  • From the app version that adds it, a report you send also says which comma you have and the branch and commit of its driving software.
  • From that version it also has its openpilot version, driving model and which of its data CommaView reads.
  • These go only with a report you choose to send, and that version of the app shows them to you before you send.

November 9, 2026:

  • With Help improve CommaView on, the app tells us whether Live View plays on your phone or car screen.
  • That report has its make and model, Android version, screen size and text size, frame rate and video decoder.
  • It also has your comma’s software version, never video.

November 6, 2026:

  • With Vehicle location on, your phone downloads the map around your car from OpenFreeMap (from OpenStreetMap on phones that can’t draw it).

November 4, 2026:

  • When setting up a comma fails, crash reports say which step it stopped at.
  • While you’re signed in, they can also say which driving software your comma runs and what its installer reported.
  • While you’re signed in, a setup that worked can say CommaView couldn’t add its view yet.

November 2, 2026:

  • A report you send can include the leaderboard’s status, never a distance or a place; See shows it before you send.

November 1, 2026:

  • Crash reports and which driving software your comma runs are sent only if you answer Send to Help improve CommaView.
  • Drives you contribute to car detection, by a tap or automatically, join our training collection for good: they can’t be removed.
  • Deleting your account, or asking us to delete something you sent, deletes its files at once, and we email our replies to what you report.
  • Routes go through our route service, a spoken destination through your phone’s speech service, and you agree to changes in the app.

Contact

Email support@commaview.com.

CommaView

Your comma’s Live View on Android, over your own network.

Support the project

Product

Features How it works Install guide Supported forks Car screens What’s new How releases work Blog

Beta

Join the beta Sign in Questions Send a support bundle

Follow

YouTubeXInstagramDiscordGitHub

Company

Team Privacy Terms

CommaView is unofficial and not affiliated with comma.ai. It is beta software and not a safety system: never let it distract you from driving.

© 2026 RhynoTech