Privacy Policy

JobSiteMap (“we”, “us”) operates the JobSiteMap web app and mobile app (the “service”).

The service is used by organisations, usually a company, and the people they invite. The organisation decides what goes into its account: its sites, its equipment, its members. For that information the organisation is in charge of it and we process it on the organisation’s behalf. For your own account details, and for the records we keep to run and secure the service, we are responsible.

Questions about privacy go to privacy@jobsitemap.com.

Your account

• Your name, your email address and, if you add one, a phone number.
• Your password, stored only as a one-way hash, never as the password itself. If you sign in with Google instead, the Google account identity described below.
• The secret for your authenticator app, if you turn on two-step sign-in.
• A profile picture, if you upload one.

Your organisation

• The organisation’s name and the industry template it started from.
• Who is a member, the roles each member holds, invitations, and which sites each person can see.
• Its configuration: the types of equipment it tracks, the fields and statuses it defines, and its branding.

Sites and equipment

• Sites: the name, address, location and boundary of each job site, and any contract number.
• Equipment: each unit’s type, the values of its fields, its status, where it is placed on the map and its rotation, and delivery runs and stops.
• Photographs that you or your colleagues upload of units, sites or completed stops.
• The history of every change: what changed, from what to what, when, by whom, and from which device. This history is what makes undo and the audit trail work.

Devices and sessions

Each account is tied to approved devices, so a new device has to be approved before it can sign in. To do that we keep, for each device: its platform (web, iOS or Android), a name such as the browser or phone model, the app and operating system version, when it was last seen, and a push notification token on mobile. In a browser, “this device” is a random identifier kept in the browser’s own storage, of which we only ever receive a hash. We do not fingerprint your browser or hardware. For each signed-in session we keep the IP address and the browser’s user agent.

We briefly count failed sign-in attempts per email address and per IP address, so that repeated guessing locks the account for a short time.

Audit and usage records

• A read audit: which person, on which device and from which IP address, searched for an address or viewed a site, a unit or a photograph, and when. Organisations use this to see who looked at what.
• Security flags raised from those records, for example an unusual number of searches in a short time.
• Usage counts, such as address searches and map tiles loaded, recorded against the organisation so we can understand our costs and keep within fair limits.

We do not collect the location of your device. The locations we store are the ones you type or place: a site’s address and boundary, and where a unit sits on the map.

The mobile app may offer to open the site nearest to you. If it does, that is worked out on your phone, from your phone’s location and the site locations already on it. Your location is never sent to us and never stored. The web app does not ask your browser for its location at all.

If you choose to sign in with Google, we ask Google only for the openid, email and profile scopes. That gives us your Google account identifier, your email address and whether Google has verified it, and your name and profile picture.

We use this only to sign you in and to fill in your name on your account. We do not ask for access to your Gmail, contacts, calendar, files or any other Google data, we do not use Google data for advertising, we do not sell it, and we do not let anyone else use it.

JobSiteMap’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

• To provide the service you or your organisation signed up for: your account, the map, the equipment records, photographs and delivery runs. The legal basis is our contract with you or your organisation.
• To keep it secure: device approval, two-step sign-in, lockout after repeated failures, the audit trail and the flags raised from it. The legal basis is our legitimate interest, and your organisation’s, in protecting accounts and data.
• To run it responsibly: usage counts, so we understand costs and capacity. The legal basis is our legitimate interest.
• To send emails you need: invitations, sign-in links and codes, and device approvals. The legal basis is our contract with you.
• To meet legal obligations, where a law requires us to keep or disclose something.

We do not sell personal information, and we do not use it for advertising.

We use a small number of companies to run the service. Each one receives only what it needs for its job.

• Hosting: Heroku (the application server and database) and Vercel (the web app).
• File storage: Amazon Web Services S3, for photographs and profile pictures.
• Email: Resend, to deliver account emails.
• Maps and imagery: MapTiler, which supplies the satellite imagery. Map tiles are fetched through our servers, so MapTiler does not receive your IP address or your account details.
• Address search: Google Maps Platform. The text you type into address search is sent to Google from our servers, without your name or email, and the results are cached for up to seven days.
• Push notifications: Google Firebase Cloud Messaging, to deliver notifications to the mobile app.
• Payments: when paid plans launch, payments will be processed by Stripe. Card details will go to Stripe directly and will not be stored by us.

Some of these companies process data outside your country, including in the United States. Where the law requires it, we rely on appropriate safeguards for those transfers, such as standard contractual clauses.

We may also disclose information if the law requires it, or to a successor if the service is sold or transferred, in which case this policy continues to apply to it.

The web app uses only what it needs to work. There are no advertising, analytics or tracking cookies.

• sessionid: keeps you signed in. Strictly necessary.
• csrftoken: protects your account against forged requests from other sites. Strictly necessary.
• jsm-theme and jsm-sites-view: remember whether you chose light or dark mode and how you like your sites listed.

The browser’s local storage holds the random device identifier described above and a few display preferences, such as whether the sidebar is collapsed. None of it is used to track you.

Every organisation’s data is kept apart from every other’s inside the database itself, not only by the application. Connections are encrypted. Passwords are hashed. Photographs are served through signed links that stop working after five minutes. New devices need approval, and administrators can see who viewed what. No system is perfectly secure, but we design for the case where something goes wrong.

We keep an organisation’s data for as long as its account is active. When an organisation closes its account, or asks us to, we delete or anonymise its data, except where the law requires us to keep something for longer.

The read audit is kept for 90 days by default and then deleted. The history of changes is kept for the life of the account, because it is what undo and the audit trail rely on. The exact periods for archived read-audit records and for closed accounts are being finalised, and this policy will be updated when they are.

Address search results are cached for up to seven days. Counts of failed sign-in attempts expire within minutes.

Depending on where you live, you can ask us to:

• tell you what personal information we hold about you, and give you a copy;
• correct anything that is wrong (you can change your own name and details in the app);
• delete it;
• give it to you in a portable format;
• stop or limit a particular use of it, or object to it.

Email privacy@jobsitemap.com and we will reply within 30 days. If the information belongs to your organisation’s account, such as sites, equipment or photographs, we may need to refer your request to the organisation, since it decides what happens to that data. An organisation’s owner can ask us for a copy of all of the organisation’s data in the same way.

You also have the right to complain to the data protection authority where you live.

JobSiteMap is a tool for businesses and is not directed at children under 16. We do not knowingly collect information from them. If you believe a child has given us information, contact us and we will delete it.

When we change this policy we will update the date at the top. If a change is significant we will tell account owners by email or in the app before it takes effect.

Privacy questions and requests: privacy@jobsitemap.com.
Everything else: support@jobsitemap.com.