MilepostBook a demo
Home › Privacy
Legal

Privacy Policy

Milepost is timekeeping and accountability software for public-works departments, municipalities, and private crews. This policy explains what data the Milepost app and web portal collect, how it is used, who it is shared with, and how long it is kept.

Effective October 4, 2026 · Applies to the Milepost mobile app (iOS and Android), the wall-station kiosk, and the web portal at milepostonline.com.

Who we are & how Milepost is used

Milepost is operated by Armstrong Intelligence (“Milepost,” “we,” “us”), based in the United States. Milepost is a business and government tool, not a consumer app. Our customer is the employing organization: a town, village, district, or private company (the “employer”). The employer is the controller of its workforce records; Milepost processes that data on the employer’s behalf to run their timekeeping, payroll, fleet, and accountability record.

The people who use the Milepost app are the employer’s workers and supervisors. Their accounts are provisioned by their employer. Milepost does not offer public sign-up, and a worker cannot create their own account (see Accounts). If you are a worker with a question about your own data, your employer is the first point of contact; we help them fulfill your request.

What we collect

We collect only what the product needs to keep an accurate, defensible record of work. Specifically:

  • Identity. Your name, work email address, job role, and the account and device identifiers Milepost assigns you. Sign-in is passwordless. We email a one-time code, so we do not store or ask for a password.
  • Precise location, while you are on the clock. When you clock in, the app records this device’s location (including in the background, when the app is closed or the phone is locked) as an on-duty timekeeping trail. On iPhone, the app records location at each punch and while it is open. While you are clocked in, it also keeps an approximate route with your phone locked (about every 500 meters of travel), unless you turn that off in the app or don’t allow it in your iPhone’s settings. The continuous background trail runs on Android. Location is collected only while Milepost has you on the clock. If a punch reaches Milepost late, or is corrected later, the points recorded in between stay on that day’s route. See How on-duty location works.
  • Photos you take in the app. Vehicle pre-trip (DVIR) inspection photos and license or certification photos, when your role uses those features.
  • A verification photo, only at a shared wall-station kiosk. When you punch on a shared garage tablet (clocking in or out, or starting or ending a break), it captures a photo at the moment of the punch so the office can confirm the right person clocked in, compared to a reference photo on file. It is used only to verify the punch. If the office approves the punch, that photo is deleted about 30 days later. If the office never reviews it, the photo is deleted about 30 days after it was taken. The one exception: while the punch is still held for the office, carries a flag nobody has resolved, or has a correction request nobody has decided, the photo is kept, and the 30 days start once the office has dealt with the punch. Your employer’s records officer can set a shorter window, never a longer one. The reference photo and the record of the check are kept. If it is flagged as a mismatch, the photo is kept as evidence of the discrepancy, and so is the photo on a held punch the office turned down. Clocking in from your own phone takes no such photo.
  • Device information. A security key the app generates to sign your punches (so “which device recorded this time” is evidence, not a claim), the platform (iOS/Android/web), and, if you allow notifications, a push-notification token so the app can be alerted, for example, of a vehicle change.
  • Service logs kept by Milepost. So Milepost can support the service, its own console keeps a log of what kind of action happened in an organization and when (for example, “a worker asked for time off”), and a log of errors and refused actions. Each entry holds the organization, the person’s role, the kind of action or error, the app version, the time, and a coded reference in place of the person’s name. The code is the same for every entry by the same person, so Milepost can tell that two entries came from one person, but the entry holds no name, email address or user id. Punches are counted by organization in 15-minute blocks. These logs do not copy your time, pay or location records. How long they are kept is under “Retention” below.
  • Work content you enter. Clock-in/out notes, the job or cost code on a shift, time-off requests, the licenses and certifications you hold (their type, number and dates), fuel and service logs, task and inspection entries, and, for kiosk use, a hashed wall-station PIN (we store only a one-way hash, never the PIN).
  • Compensation data, for payroll. Your pay rate, and how your hours map to your employer’s funds, budget lines, and job codes (set by your employer’s bookkeeper), so Milepost can total hours and estimate gross pay for the employer’s payroll. Milepost does not process payments, take bank or card details, or move money; it produces the hours and figures your employer’s payroll is prepared from.
  • Meeting recordings and papers, when your organization keeps its minutes in Milepost. The recordings, transcripts, documents and notes a town uploads for a board meeting, and the minutes drafted from them for the clerk to review and approve.
  • Sign-in and security signals. Limited technical data used only to protect access: the IP address a one-time sign-in code is requested from, and the device and browser type of a session. We do not use it to build a profile or track you across the web.

What we do not collect: we do not collect your phone number, home address, date of birth, contacts, calendar, photo library, browsing history, or any special-category data (such as race, religion, health, or sexual orientation). Some records can still hold some of this. A photo of a license or certification shows what is printed on the card, such as the date of birth and home address on a driver’s license, and a DOT medical card on file is a health certificate. Time off recorded as sick shows that you were out sick, and a note, such as the reason for a time-off request, holds whatever its writer puts in it. A meeting recording, transcript or document holds whatever people said at the meeting or wrote for it, which can include names, home addresses and more. Milepost contains no advertising, no advertising identifier, and no third-party analytics or tracking SDKs.

How on-duty location works

Location is the most sensitive thing Milepost handles, so it is bounded deliberately:

  • On the clock only. The background location trail is recorded only while Milepost has you on the clock. Clock out and it stops. We do not track evenings, weekends, or time off. If a punch reaches Milepost late, or is corrected later, the points recorded in between stay on that day’s route.
  • What it is for. To confirm you were at the job site, to keep an on-duty route trail if a question comes up later, and to show your position on a live crew safety map to people in your own organization whose role can see it: by default supervisors, bookkeepers and auditors (the read-only role a town board holds), and your employer can change which roles see it. It is never shown to the public or to other organizations.
  • You are asked first. Before the background trail starts, the app shows a plain-language disclosure and asks you to turn location on. If you decline, the background trail does not run: instead, while Milepost is on your screen and you are on the clock, it records your location about every 2½ minutes, if your phone allows it. You can still clock in, and a punch may still carry a single location reading at the moment you press the button.
  • It is kept short. On-duty location breadcrumbs are an operational trail, kept separate from the tamper-evident time record, and are automatically purged about 90 days after they are captured, though backup copies can last up to about 15 months.

This on-duty-only boundary follows New York’s highest court in Cunningham v. NY State Dept. of Labor (2013), which found GPS tracking of a state employee went too far because it also covered evenings, weekends and vacation. Milepost records location only while it has you on the clock.

How we use data

We use the data above only to provide and support the service for your employer:

  • To record and verify hours worked, and to flag punches that need review (for example, off-site or from an unrecognized device).
  • To total payroll hours, coded to the correct fund, budget line, or job, for the employer’s payroll.
  • To run the fleet, pre-trip, work-scheduling and meeting-minutes features your organization has enabled.
  • To keep a tamper-evident, exportable accountability record for the employer, its board, and its auditors.
  • To secure accounts, notify devices of relevant events, and provide customer support.

We do not use your data for advertising, we do not sell or rent it, and we do not use it to build profiles for anyone other than your employer’s own operational record.

Who we share with

Milepost does not sell personal data and does not share it with third parties for their own purposes. Data is disclosed only:

  • To your employer: the organization whose account you belong to, and its authorized supervisors and administrators. This is the whole point of the product: your hours and on-duty record belong to your employer.
  • To service providers who process data on our behalf, under contract and only to run the service. They are our US-based cloud hosting provider, our transactional email provider (to send sign-in codes), the platform push-notification service (to deliver notifications), a mapping-tile provider that draws the base map under the supervisor crew view (it receives only the map area being viewed, never a worker’s location), Plaud, which transcribes a meeting recording a town uploads for its minutes (it reads the recording through a link that expires within an hour), and Anthropic, whose AI model drafts minutes for the clerk to review. Anthropic receives text, never the recording: the meeting’s transcript, with the names the clerk matched to its speakers and without the parts the clerk marks as executive session, or the minutes a town typed and uploaded; the board’s member list; the clerk’s notes; the meeting’s town, board, type, date, start time and place; and the clerk’s name. These providers may not use the data for any other purpose.
  • When required by law, or to protect the rights, safety, and security of users and the service.

Security

Hosted in the United States. Data is encrypted at rest by our hosting provider. It is also encrypted in transit, and access is role-based. Every change to the record is written to a per-organization, hash-chained audit trail, so tampering is detectable by mechanism rather than by trust. A punch from a worker’s own phone is cryptographically signed on that phone.

The first two sentences of this section don’t cover the files a town uploads for its minutes (recordings, and transcript, document and notes files): those are kept in a separate file store, not yet named here. Transcripts, the text of uploaded documents and every version of the minutes are kept with the rest of the record, which those two sentences do cover.

Milepost staff can see each town’s list of people and their roles to support setup. Time, pay and location records are visible to Milepost staff only during a support session, which is recorded in the town’s own audit trail.

Retention & the tamper-evident record

Milepost is an accountability system, so the time and payroll record is append-only and is not silently deleted or edited. Correcting a mistake writes a new, linked entry that explains the change; the original stays. Employers retain these records for as long as their own municipal or business records-retention obligations require.

  • On-duty location breadcrumbs are purged automatically about 90 days after capture, though backup copies can last up to about 15 months.
  • Wall-station verification photos for an approved punch are deleted about 30 days after approval. A photo the office never reviews is deleted about 30 days after it was taken, unless its punch is still held or flagged, or has a correction request waiting: then it is kept until the office has dealt with the punch, and deleted about 30 days after that. Your employer’s records officer can set a shorter window, never a longer one. A mismatch photo and the photo on a held punch the office turned down are kept as evidence, and the reference photo and the record of who checked the punch are always kept. Only the image is deleted; the punch and the record of it stay.
  • Milepost’s own service logs (the activity and error logs described under “What we collect”) are not cleared on a schedule yet. Milepost has not built that, so for now they are kept. Closing an account does not remove them. They hold a coded reference in place of a name.
  • The time and payroll record is retained by the employer per their retention rules; a worker who leaves is deactivated, not erased, so their historical time record stays attributable and auditable.

Accounts & your choices

The Milepost app does not allow users to create their own accounts. Accounts are created and managed by the employing organization’s administrator. You sign in to an account your employer has already set up, using an emailed one-time code.

You control location sharing at any time through your device’s operating-system settings. You can decline or revoke location permission, and then Milepost records no location from your phone: the background trail will not run, and a punch from your phone is recorded without a location. Turning it off does not lock you out; you can still clock in.

Data access & deletion

Because accounts and records are owned and controlled by the employing organization, requests to access, correct, or delete personal data are handled through that employer. If you are a worker, contact your employer’s Milepost administrator. If you are an employer, or you cannot reach one, contact us at [email protected] and we will act on the account holder’s verified instruction.

Some records cannot be deleted on request while a legal retention obligation applies to them. A municipal time and payroll record is kept for the period the law requires, and the tamper-evident audit trail is retained so the record stays verifiable. Where deletion is not possible, we will explain why. Deleting or de-identifying data once its retention obligation ends is not built yet. On-duty location breadcrumbs, which carry no such obligation, are purged on the 90-day schedule described above.

See also Close your account: what’s removed and what stays.

Children

Milepost is a workplace tool intended for employees and is not directed to, or intended for use by, children. We do not knowingly collect data from anyone under 16.

Changes & contact

If we change this policy, we will post the updated version here with a new effective date and, for material changes, notify the organizations that use Milepost. Questions about this policy or your data: