Privacy policy

DockDuty (“we,” “us”) is a pre-launch company in Orlando. This policy explains, in plain English, what we do with the information you share through our website, and with the vehicle data you let us read when you connect a Tesla in the owner dashboard. If anything here is unclear, email support@dockduty.com.

What we collect

We only collect what you give us through forms on this site:

• Founding-customer form: first name, last name, email, role (owner / fleet operator / other AV operator / investor), number of cars, city, and phone number (optional, if you request a call).
• Call request form (Cybercab ownership planner): your name, phone number, the city or area you type (optional), your planner answers, and how you first arrived at our site (the campaign values in the link you clicked, the advertising click identifier if you came from an ad, the referring site, and the first page you landed on, from the dd_attr cookie described below). No email address is needed.
• Plan email form (Cybercab ownership planner): your email address, your first name (optional), your planner answers (whether you are learning or planning to own, how many cars, who would own them, your metro, your timeline and the topics you picked), and how you first arrived at our site, from the same dd_attr cookie. If you asked for a call on the same visit, the phone number you gave for that call is sent with it.
• Investor deck request form: first name, last name, email, and firm or organization (optional).
• Direct emails: when you write to us, we keep the message and your email address so we can reply.

We use Google Analytics 4 (provided by Google LLC) to understand how visitors find and use the site: which pages get traffic, what referral source sent you, and whether the site works on your device. GA4 sets a small number of cookies (e.g. _ga, _ga_*) and records standard browser-provided data (page URL, referrer, screen size, approximate region from your IP). It does not see your name, email, or any form-field content. We use it to improve the site and, through the Google Ads link described under Advertising measurement below, to see which of our ads work. We do not link analytics data to your individual account or sell it. Google’s handling of this data is governed by the Google Privacy Policy. You can opt out of GA4 entirely by installing Google’s browser opt-out add-on or with a tracker-blocking extension.

We use the OpenAI Ads Pixel on the public DockDuty marketing site and public reservation pages to measure ad-driven visits, genuine new contact leads, and completed reservations. When you click one of our ChatGPT ads, OpenAI may add an opaque oppref click reference to the URL. We store that reference in a first-party dd_openai_ref cookie on .dockduty.com for up to 30 days so it can follow you from the site to the reservation app. OpenAI may automatically normalize and hash eligible contact details from supported forms for advertising measurement. The Pixel is not loaded for browsers using Global Privacy Control or our targeted-advertising opt-out, and is not loaded on the private owner dashboard or founders’ board. See our Your Privacy Choices page to opt out and the OpenAI Privacy Policy for information about OpenAI’s handling of data.

We also use Microsoft Clarity (provided by Microsoft Corporation) for heatmaps and session recordings. A heatmap shows where visitors click and how far they scroll on a page. A session recording is a replay of how one anonymous visitor moved through the site: mouse movement, scrolling, clicks and taps, and the pages visited. We use it for one purpose, to see where a page confuses people so we can fix it. Clarity is set to mask what you type: text in form fields and dropdowns is never captured, and email addresses and numbers in page text are masked before anything leaves your browser. It runs only on dockduty.com and on the public pages of app.dockduty.com (the demo calculator, sign-in, and the reserve flow). It never runs inside the signed-in owner dashboard. Clarity sets two first-party cookies, _clck (a random visitor ID) and _clsk (which strings one visit’s page views into a single session), and, through Microsoft’s own domains, the cookies CLID, ANONCHK, MR, MUID and SM. Microsoft uses MUID across its own properties for analytics and advertising; we do not use Clarity for advertising and do not link it to your name or account. Microsoft keeps recordings for 30 days and heatmap and click data for 9 months, then deletes them. Microsoft’s handling of this data is governed by the Microsoft Privacy Statement. Any tracker-blocking extension stops Clarity entirely, and so does opting out under Your privacy choices, with no effect on browsing or reserving.

If you use the chat assistant on dockduty.com, what you type and its replies are sent to a third-party AI model provider to generate each answer, and the conversation is saved on DockDuty’s application backend so our team can read it and follow up. Before anything is saved, email addresses and phone numbers in your messages are removed, and a message that looks like card, ID or bank details is not saved at all. We save the conversation, the page you chatted from, its language, the fleet size you mentioned if any, and whether the assistant offered a call with a founder. If you ask to talk to a founder and choose to enter your email address (and, if you like, your name) in the chat’s contact form, we save them with that chat so a founder can email you back; they go only to our backend, never to the AI model provider. We do not save your IP address; we keep only a one-way code made from it, so we can tell that two chats came from the same visitor without knowing the address. Chats are shown only to DockDuty staff on our internal board, are never sold, and are deleted 180 days after the last message, or sooner if you ask us to delete them.

Inside the signed-in owner dashboard at app.dockduty.com we keep a small, first-party record of use: how many dashboard pages your account opens, the last page it was on, and when it was last open. It is tied to your account, stored on our own backend, shown only to DockDuty staff so we can see which owners are actively using the dashboard, and deleted with your account. It uses no third-party service and no cookies of its own, and it never records what you type or anything in a page’s address bar beyond the page itself.

Global Privacy Control and Do Not Track. If your browser sends the Global Privacy Control signal, we treat it as an opt-out of sale and sharing for targeted advertising, automatically, as described under Your privacy choices. Do Not Track has no agreed meaning and our site does not change its behavior for it; turn on Global Privacy Control instead.

We also set one first-party attribution cookie of our own, dd_attr, scoped to .dockduty.com and kept for 90 days. It records only how you first arrived, the utm_source, utm_medium and utm_campaign values in the link you clicked, the advertising click identifier if you arrived from an ad (for example Google’s gclid, which Google appends to the link automatically), the referring site if it was an outside one, and the first page you landed on. It holds no name, email, IP address or form content, and it is never sold. If you go on to reserve a stall or send us a form, the advertising click identifier in it can be sent back to the ad platform that issued it, so that platform can count the result; that does not happen if you have opted out under Your privacy choices. Its only purpose is so that when someone reserves a stall we can tell which article, search or link brought them, which our reservation records previously could not show. Blocking cookies disables it with no effect on browsing or on reserving; clearing your cookies erases it.

If you arrive through a referral link an owner shared from their DockDuty dashboard (a dockduty.com/r/ address), we set one more first-party cookie, dd_ref, scoped to .dockduty.com and kept for 90 days. It holds only that owner’s referral code, so that if you go on to reserve a stall we can record which owner shared the link with you. It holds no name, email, IP address or form content, it is never sold or shared, and blocking or clearing cookies removes it with no effect on browsing or on reserving. Separately, this site shows aggregate reservation counts by metro (on the owner-demand dataset, the network page and each market page). Those are counts of stall reservations, published as totals only, and they identify no one.

If you reserve through an owner’s link, that owner sees that a reservation came through it and when, never your name, contact details or what you reserved.

Advertising measurement. Every page of dockduty.com, and app.dockduty.com, loads the X (Twitter) website tag (static.ads-twitter.com/uwt.js, pixel ID reg0j), never on preview or staging builds. It tells us whether an ad we paid X to show actually led to a visit or a reservation. It reports page visits to X, which may match them to an X account; it does not receive your name, email, or anything you type into a form. Google Analytics is linked to our Google Ads account, so Google can tell us which of our ads led to a visit, an inquiry or a reservation, and when a reservation or inquiry came from a Google ad we can send Google that ad’s click identifier for the same reason. We do not run any other advertising or social pixel. You can stop all of this by opting out under Your privacy choices, with any tracker-blocking extension, or (for X) through your X privacy settings, with no effect on browsing or reserving.

We do not sell your data for money. The advertising measurement above, and Microsoft Clarity (because Microsoft also uses its MUID cookie for advertising), are the only things that can count as “sharing” for targeted advertising under California and other state privacy laws, and you can switch both off under Your privacy choices. Through this website we do not collect precise location, device fingerprints, or browsing history outside our own site; Clarity recordings cover only pages on our own site. Vehicle location is collected only in the owner dashboard, only from a Tesla you connect, and only after you consent. That is covered in the next section.

Connected vehicle data

If you have an account at app.dockduty.com and connect your Tesla account, DockDuty reads data from your vehicles through Tesla’s Fleet API and can send them commands on your instruction. Nothing is read until you have done two things: accepted DockDuty’s own consent, which lists everything below and names location separately, and authorized DockDuty on Tesla’s screen. You can withdraw either at any time.

What we collect from a connected vehicle:

• Tesla account link: your Tesla account identifier and email, so the connection can be tied to your DockDuty account.
• Vehicle state: VIN, battery and charge state, odometer, lock and door state, climate, software version, and alerts or safety-related events the car reports.
• Precise location: live GPS position and heading, streamed while the car is awake. It is shown on your fleet map, used for trip history, and used to know when the car arrives at or leaves the depot. A live-location indicator is shown next to the map whenever this is on.
• Commands you send: lock, unlock, honk, flash, trunk, charge port, climate, start and stop charging, sentry mode, and send-to-navigation, with who sent each one and when. Every command is one that you or a team member you add taps. DockDuty never sends a command to a vehicle automatically.
• Charging sessions: energy added and charging events, so your statement can show the depot energy line.

How we use it. To show you your fleet, to service and charge your car at the depot, to build your statements, to log commands for your own audit trail, and to tell you about issues the car reports. We do not use it for advertising and we do not infer anything sensitive about you or your passengers from it.

Who sees it. You, any team members you add to your account, and DockDuty operations staff for depot work. We do not sell vehicle data. We do not share per-vehicle data with landlords, insurers, lenders, or anyone else without your separate written consent. Aggregate figures that cannot identify a vehicle, such as total fleet miles, may appear in company reporting. Tesla also receives and uses vehicle data under Tesla’s Customer Privacy Notice; that is Tesla’s processing, not ours.

Where it lives and how long. On DockDuty’s application backend (app.dockduty.com and its database provider). We delete a vehicle’s data within 30 days after you disconnect your Tesla, ask us to delete it, or the vehicle leaves your account, unless the law requires us to keep a record.

Stopping it. Click Disconnect on your Account page, remove DockDuty’s key on the car’s Locks screen, or revoke DockDuty in your Tesla account security settings. Any one of these stops collection immediately. You can review the categories you consented to on your Account page at any time.

Recordings. DockDuty does not collect camera images, video, or audio from your vehicle. If that ever changes, it will require a separate, specific opt-in and an on-screen indicator, and this policy will be updated first.

How we use it

• To follow up about founding-customer onboarding when our targeted Q4 2026 launch approaches.
• To send the investor deck when you request it, and to share material company updates if you stay on the list.
• To answer questions you email us.
• To call you when you ask us to. A founder dials by hand. We do not text a number given for a call request, use autodialers or recorded messages, or add it to any marketing list, and we stop calling when you ask.
• To run the owner dashboard for connected vehicles, as described under Connected vehicle data.
• To send you owner updates: news when it’s real, such as a depot milestone or a stall opening up, plus a periodic update on where the build actually stands. If you give us your email through a form on this site, this is the list you are on.

We will not sell your information, and we do not give your name, email or phone number to anyone for their own marketing.

Leaving the list. Every owner update carries an unsubscribe link, and your mail app’s own one-click unsubscribe works too. You can also reply to any of our emails with the word “unsubscribe” and a person will take you off the same day, or write to support@dockduty.com. We record the request against your email address, so it holds even if you are in our system more than once.

Unsubscribing stops the updates. It does not stop email tied to something you hold with us, such as a reservation receipt, your executed agreement, or a notice about your account, because those are part of the arrangement rather than marketing. If you want those to stop as well, ask us to delete your information and we will.

Where it’s stored

Form submissions, and vehicle data from a Tesla you connect, are transmitted to and stored by DockDuty’s application backend (app.dockduty.com and its database/hosting provider); Netlify hosts only the static marketing site. Reservation payments are processed by Stripe, which handles your payment-card information under its own privacy terms. Email correspondence sits in our company email inbox. Aggregate analytics data is held by Google as part of the GA4 service described above, and heatmap and session-recording data is held by Microsoft as part of the Clarity service described above. All of these providers carry standard industry security practices.

How long we keep it

We keep your contact information until you ask us to delete it, or until we shut the company down, whichever comes first. There’s no scheduled purge. Connected vehicle data is the exception: it is deleted within 30 days of disconnection or a deletion request, as described above. Chat assistant conversations are deleted 180 days after their last message. Clarity session recordings expire after 30 days and Clarity heatmap data after 9 months, on Microsoft’s side.

Your privacy choices

California law, and similar privacy laws in other US states, give you the right to opt out of the sale or sharing of your personal information and of targeted advertising. At DockDuty that means the advertising tags and the ad click identifier described under What we collect. There are three ways to opt out, and any one of them is enough:

• One click: press the button on Your Privacy Choices (linked, next to the blue toggle icon, in the footer of every page on dockduty.com and of the reservation and demo pages on app.dockduty.com). It saves a cookie, dd_privacy, on this browser for 13 months, covering dockduty.com and app.dockduty.com.
• Global Privacy Control: if your browser sends it, you are opted out automatically on every visit.
• Email: write to support@dockduty.com with the subject “Do not sell or share” and the email address or phone number you used with us. We will remove the ad click identifiers we hold for that address or number, so none is sent to an ad platform from then on, and confirm when it is done. An email request covers what we already hold; to keep a new ad click from being recorded on a later visit, opt out on that browser too or turn on Global Privacy Control. Someone you authorize in writing can ask for you.

Once you opt out, the X tag and Microsoft Clarity stop loading, an ad click identifier is removed from the page address before Google Analytics reads it, Google Analytics runs with Google’s advertising cookies, ad personalization and Google signals off, and no ad click identifier is attached to anything you send us. Opting out never changes the price, the terms or the service you get from us. We do not show a cookie banner. The advertising side of every one of these tools can be switched off here instead, and a tracker-blocking extension stops them entirely.

Your rights

You can ask us at any time to:

• Tell you what we have on file for you.
• Correct anything that’s wrong.
• Delete everything.
• Stop contacting you.
• Show you which vehicle-data categories you consented to, and withdraw that consent.
• Stop any sale or sharing of your information for targeted advertising (see Your privacy choices).

Email support@dockduty.com with the request and the email address or phone number you used with us, and we’ll respond within 14 days.

Children

This site is not directed at anyone under 18. We don’t knowingly collect information from minors.

Changes to this policy

If we change this policy in a meaningful way, we’ll update the “Last updated” date above and, if we have your email, send you a heads-up.

Contact

DOCK DUTY LLC
37 N Orange Ave, Ste 222 #3069
Orlando, FL 32801
support@dockduty.com