Privacy Policy

Account details. Your email address, and the name and shop or company name you choose to enter when you create an account. Your password is handled by our authentication provider and is never stored in a form we can read.

What you put in the app. The records you create — equipment, meter readings, work orders and their tasks, preventive maintenance schedules, parts and inventory counts, links to manuals, and the notes and technician names you type. This is your shop's operating data. We treat it as yours.

Photos you attach to a work order. A work order can carry one optional photo of the problem being reported. Before it is uploaded, your browser resizes and re-encodes it to at most 750 KB — the full-resolution original stays on your device and is never sent to us. What we store is that resized image, the short caption you write for it, and which work order it belongs to. Photos are kept in private storage, are never public, and are readable only by signed-in members of the workspace that owns the work order. Removing the photo, or deleting the work order, removes it from the record and triggers deletion of the stored file; if storage cleanup fails, the app reports that failure so it can be cleared. Closing a work order keeps its photo as part of that repair's record. Photos live outside our database, so they are not part of the nightly database backup. Please do not photograph people or documents you would not want in your shop's records.

Approximate location, only if you allow it. The dashboard can show local weather. If you accept your browser's location prompt, your approximate coordinates are sent to Open-Meteo to fetch a forecast. We do not store them. If you decline the prompt, the dashboard simply shows the date and nothing about your location leaves your device.

Feedback you send. If you use the in-app feedback form, we receive your message and the email address on your account so we can reply.

Ordinary server logs. Our hosting and database providers record request metadata such as IP address, timestamp, and user agent, as part of operating and securing the service.

We do not sell your data. We do not share it with advertisers. We do not use the records you enter to train machine learning models. We do not read your shop data except when you ask us to help with a specific problem, or where we must to keep the service running or secure.

Photos used for camera-assisted equipment entry — pointing your camera at a machine's serial plate to fill in the form — are read in your browser and are never uploaded to us. That is a different thing from a photo you deliberately attach to a work order, which is stored, described above. We do not run face recognition or any other analysis on either one.

Sign-in cookies. FleetTend sets cookies to keep you signed in and to protect the sign-in process. These are strictly necessary for the service to work, and there is no way to use an account without them.

Aggregate site analytics. We use Vercel Analytics and Speed Insights to count page views and measure how quickly pages load. These do not set cookies and do not build a profile of you across sites. We also record a small number of signup events—when a signup is submitted, whether it succeeds or fails, whether it is waiting for email confirmation, and whether the confirmation is completed—so we can distinguish a broken signup or delivery problem from a quiet week. Failure events use general categories and never include the email address, password, or raw error message.

How you found us. If you arrive from an advertisement or a link on another site, we store the campaign source, medium, campaign name, term, content, advertising click identifiers, referring host, landing path, and first-visit date in a first-party cookie (ft_attr, 90 days). If you register, those details are attached to your account so we can measure which campaigns introduce customers. The cookie is not written on a direct visit, is not used to follow you across websites, and is not shared with an advertiser or used to target you.

We do not run advertising or retargeting pixels, and we do not sell or share this information.

Supabase — database, authentication, and transactional email (password resets and confirmations). Data is stored in the United States.

Vercel — application hosting and delivery, and the aggregate page-view and performance analytics described above.

Cloudflare Turnstile — the human check on the signup form, where enabled, to keep automated signups out.

Open-Meteo — weather forecasts, only when you allow the location prompt described above.

If you are in the EEA or UK, this means your data is transferred to and processed in the United States.

We keep your account and shop records for as long as your account is open. If you ask us to delete your account, we remove your workspace and its records from the live service; residual copies may persist in encrypted provider backups for a limited period before rotating out.

You can ask us to give you a copy of your data, correct it, or delete your account and everything in it. Depending on where you live you may also have the right to object to certain processing or to lodge a complaint with your data protection authority. Email support@fleettend.com and we will respond within 30 days.

Each organization's records are isolated at the database level, so one workspace cannot read another's. Traffic is encrypted in transit. No system is perfect: if we ever become aware of a breach affecting your data, we will tell you.

FleetTend is a tool for workplaces and is not intended for anyone under 16.

If we change this policy in a way that matters, we will update the date above and, for significant changes, tell account holders directly.

Questions about this policy, or about your data: support@fleettend.com.