Privacy Policy

This page covers three different things. This marketing website runs one analytics tool and a support chat widget. The owner/member dashboard runs that same analytics tool, plus a handful more, and the SimpleTelematics mobile app is different again. Fleet owners, team members, and drivers sign in to the dashboard and app, and they collect and process the data described below to do their job, including through a handful of third-party tools. Read the section that applies to what you're using.

The website

PostHog. Automatically records page views and clicks as you browse this site, such as which pages get read and which buttons get clicked, so we can tell which pages and messaging are actually working. It also records a session replay, a recorded playback of how you moved through and used the pages, so we can see where the experience is confusing. Anything you type into an input on this site is masked in that replay, not recorded. It's not used for advertising, and we don't sell it or share it with third parties for tracking.

Chatway. Powers the support chat bubble shown on this site. If you start a conversation, your name, email, and message are shared with Chatway so it can route and answer it. See the Chatway entry under "The dashboard" below for how it's also used there.

The "Start free trial" button and the sign-in link take you to the SimpleTelematics dashboard, a separate site, to create or access your account. See "The dashboard" section below for what that collects. The contact links here open your own email app with a message addressed to us. If you send that email, we receive your email address and whatever you write in it. There's no form and no database on this website itself collecting your details in the background.

The dashboard

Owners and team members sign in to the dashboard to see the fleet map, trip history, vehicles, beacons, and billing. A handful of third-party tools run there to help us operate and improve it. None of them are used for advertising, and we don't sell any of this data or share it with third parties for tracking.

PostHog. Automatically records clicks, page views, form submissions, and a session replay across the dashboard, such as which onboarding steps an owner completes and where the interface is confusing, and captures unhandled errors with a stack trace, both in the browser and on our backend, so we can fix bugs. Once you're signed in, PostHog also receives your account id, email, and name, so activity ties back to your account instead of staying anonymous.

Chatway. Powers the support chat bubble shown on this site, to signed-in owners on the dashboard, and to visitors on our help center. If you start a conversation, your name, email, and message are shared with Chatway so it can route and answer it.

Fider. Powers the Feature Requests page. Clicking into it from the dashboard signs you in there automatically using your account's name and email, so your posts and votes are tied to your identity rather than posted anonymously.

Stripe. Processes subscription billing for owners. Card details go directly to Stripe; we never see or store them ourselves.

Cloudflare Turnstile. Runs on the sign-in, sign-up, password-reset, and team-invitation pages to tell a real person from a bot before we process the request. It analyzes signals like your browser and IP address to make that call; we don't receive those details ourselves, only whether you passed. The same check runs inside the mobile app's sign-in and fleet-code setup screens.

The mobile app

The app is how drivers log trips automatically and how owners and team members see their fleet. Here's what it collects to do that.

Precise location. Used to log where a fleet vehicle has been while a trip is in progress. It's tied to your account and to the vehicle you're driving, so an owner or member can see trip history. We don't use it for advertising, and we don't share it with third parties for tracking.

Bluetooth beacon data. Each fleet vehicle carries a small Bluetooth beacon. The app reads the beacon's identifier to detect when you get in and out of that vehicle, which is what starts and stops trip logging. This is tied to the vehicle and driver assignment, not used for advertising.

Motion data. The app uses your phone's motion sensors on-device to tell when a vehicle starts and stops moving, so it doesn't have to keep GPS running constantly. Raw motion data isn't uploaded or stored on our servers.

Camera. Used only to scan the QR code printed on a beacon's label when setting one up. No photo is taken, stored, or uploaded.

Account information. An email address (or, for drivers who join with a fleet code, no email at all) to sign in and to know which fleet and vehicles you have access to.

Why we use it

On the dashboard, PostHog exists to show us which pages are actually getting used, which buttons get clicked, and, through session replay, where a visitor gets stuck or confused, before we spend more time improving the wrong ones. On the website, PostHog serves that same purpose. Beyond that, on the website, we read your message and reply. If you asked to be kept in the loop, we also contact you about SimpleTelematics early access. We don't use your address for unrelated marketing, and we don't sell it or share it for advertising.

In the app, location, beacon, and motion data exist to log trips and show fleet status to the account they belong to. That's the entire purpose. We don't use any of it for advertising, and we don't sell it or share it with third parties for tracking.

On the dashboard, the tools listed above exist to run and improve the product itself: seeing where owners get stuck during setup, watching a replay to fix a confusing screen, answering a support question, collecting feature requests, and processing payment for the subscription.

Where it lives

Website messages sit in our inbox, handled by our email provider like any other message you'd send a small business. The website itself stores nothing about you directly. It's hosted onNetlify, which, like any web host, may keep standard server logs including IP addresses. Page views, clicks, and session replay captured by PostHog live with PostHog under its own security practices, the same as the dashboard's copy of that tool, described below.

Dashboard and app data (location, trips, beacon and vehicle assignments, account info) is stored in our backend database, run on Supabase, and is only visible to your own fleet account. The dashboard itself is hosted on Vercel, which, like Netlify, may keep standard server logs. Emails the dashboard sends you, such as invitations and password-change confirmations, go out through Resend. Feature Requests (Fider, described above) runs on a server we operate ourselves on Google Cloud, not on Fider's own hosted service, so that data sits under our own security practices, the same as the rest of the dashboard. Data held by PostHog, Chatway, Stripe, and Cloudflare (described above) lives with each of those vendors under their own security practices, not ours.

Cookies and analytics

This marketing website runs PostHog; the dashboard runs that same tool, plus the support, feature request, and billing tools described above. PostHog uses browser storage, not necessarily a cookie, to recognize repeat visits during a session, on either the website or the dashboard. Its fonts are served from our own domain, so opening a page doesn't quietly call out to a font provider on top of that. The dashboard runs more tools on top of that: PostHog, Chatway, and Fider each set their own cookies or use browser storage to do their job, and Stripe's checkout does the same during payment. Cloudflare Turnstile, which runs the bot check on sign-in and sign-up, keeps any state it sets within its own challenge page, not as a cookie on our domain. None of them, on the website or the dashboard, carry an advertising identifier, and none are used for cross-site profiling.

How long we keep it

We hold on to a website email for as long as we're helping you or you want to hear about early access, or until you ask us to delete it, whichever comes first. Server logs kept by our host are retained on their schedule, not ours. PostHog analytics data follows PostHog's own retention schedule, the same as the dashboard's copy of that tool.

App and dashboard data tied to your account (trips, location history, vehicle and beacon assignments) is kept for as long as your account is active, so you and your team can see fleet history. If you close your account, we delete the data tied to it. Feature Requests data on Fider is self-hosted, so it follows our own retention practices too, not a vendor's schedule. Data held by PostHog, Chatway, Stripe, and Cloudflare follows each vendor's own retention schedule, not ours.

Your choices

Email hello@simpletelematics.com at any time to see what we hold about you, correct it, or have it deleted, whether that's a website message, dashboard account data, or something held by one of the tools above. You can also turn off location or Bluetooth permissions for the app anytime in your phone's Settings, though the app won't be able to log trips without them.

California residents (CCPA and CPRA)

If you're a California resident, this section adds the specific disclosures required by the California Consumer Privacy Act and the California Privacy Rights Act on top of everything above. Everything else on this page already says what we collect and why; this maps that to the categories and rights the law defines.

Categories of personal information we collect. In the past 12 months we've collected identifiers (your name, email address, and account or device identifiers, including a beacon's Bluetooth identifier), geolocation data (precise location while a trip is in progress, from the mobile app), internet or electronic network activity information (page views, clicks, and session replay on this website and the dashboard, and dashboard form interactions, all captured through PostHog, as described above, plus browser and IP information Cloudflare Turnstile analyzes during sign-in and sign-up to detect bots), and commercial information (your subscription plan and billing history, processed by Stripe). We get this directly from you when you sign up or use the dashboard and app, automatically as you browse this website or use the dashboard and app, and from the service providers named on this page. We use it for the purposes already described here: seeing which pages and messaging work, logging trips, showing fleet status, running and improving the dashboard, billing, and support. We don't use it for anything materially different without telling you first.

Sensitive personal information. Precise geolocation, described above, counts as sensitive personal information under the CPRA. We only use it to log trips and show fleet status to the account it belongs to, which is necessary to provide the service a fleet owner signs up for, so no separate opt-in or "limit use" mechanism applies to it. We don't collect other categories of sensitive personal information, such as government ID numbers, health data, or biometric identifiers.

We do not sell or share personal information. We haven't sold personal information, and we haven't shared it for cross-context behavioral advertising, in the past 12 months or at any point before that. The third parties named on this page (PostHog, Chatway, Stripe, Cloudflare, Resend, Supabase, Netlify, Google Cloud, and Vercel) process data only to provide their service to us, as service providers, not as buyers or advertising partners.

As a California resident, you have the right to:

• Know what personal information we collect, use, disclose, sell, or share.
• Know the categories of sources we collected it from, our purposes for collecting it, and the categories of third parties we disclose it to.
• Request a copy of the specific pieces of personal information we have about you.
• Request deletion of personal information we collected from you, subject to legal exceptions.
• Request correction of inaccurate personal information we maintain about you.
• Opt out of the sale or sharing of your personal information. We don't sell or share it, so there's no opt-out mechanism required for those activities.
• Limit the use of sensitive personal information. We don't use or disclose it beyond what's necessary to provide the service, so no limit request is needed for that either.
• Non-discrimination for exercising any of these rights.
• Appeal if we deny a request you've made.

To submit a request, email hello@simpletelematics.com with the subject line "California Privacy Request." Include your name, the email address associated with your account (or the one you contacted us from), and the right you want to exercise. We'll verify your identity before acting on it and respond within the time required by law, generally 45 days. If we deny your request, reply with "Appeal" in the subject line and we'll explain why in writing.

You may designate an authorized agent to submit a request on your behalf. The agent must show proof that you authorized them to act for you, and we may still ask you to verify your identity directly.

Children

SimpleTelematics is a tool for businesses. Neither the website, the dashboard, nor the app is directed at children under 16, and we don't knowingly collect their information.

Changes to this policy

As the product grows, what we collect will change, and this policy will change with it. When it does, we'll update the "last updated" date at the top of the page.

Contact

Questions about your privacy or this policy? Email hello@simpletelematics.com.