Privacy Policy

Effective date: 11/15/2026

Guard Tour Log ("the App", "we", "us", "our") is developed by Plainside Labs ("Developer"). This Privacy Policy explains how the App and our website, guardtourlog.com ("the Website"), handle information.

Plain-language summary: Guard Tour Log is an offline-first app. Everything you create — shifts, checkpoint scans, incident reports, photos, and location stamps — is stored locally on your device. The free App does not send this data to us. If your company subscribes to Guard Tour Log Team, our paid web service, we process the account, device and report-delivery information needed to provide it, as described in section 2. Section 3 says who that information is shared with and why. Our website separately measures which pages and advertisements lead to a purchase, but only if you agree to it — section 5 describes exactly what that involves, and you can refuse or change your mind at any time.


1. Information the App accesses

The App runs entirely on your device. It accesses the following, only on your device, to provide its features:

  • Camera — to scan checkpoint QR codes and to take photos for incident reports. Photos are saved in the App's private storage on your device.
  • Location (GPS) — to add a time-and-location stamp to shift events (shift start/end, checkpoint scans, incidents) so a report can show where an event occurred. Location is accessed only while you are using the App (foreground). If location is unavailable, the App still records the event without coordinates.
  • Content you enter — shift details, guard name, site/location name, and incident titles and descriptions.

All of the above stays on your device. The App does not require an account, sign-in, or internet connection to work.

2. Information we collect

Free App. When you use the App without Team, we (the Developer) do not collect, receive, store on our servers, or otherwise access any of the data you create in it.

Guard Tour Log Team. If your company uses Team, we process the following on our servers to provide it:

  • Account information — the company name, and each web user's name, email address and password (stored only as a secure hash).
  • Report branding — the company name and logo the company adds for its reports.
  • Guard seats and devices — the number of seats, any guard name assigned to a seat, activation codes (stored as hashes), and for each activated phone a random identifier generated by the App, a device credential (stored as a hash) and when it last checked in.
  • Subscription and billing — the email address used at checkout, and the subscription's status, seat count and billing period, as reported to us by Paddle. We do not receive or store card or other payment details.
  • Google Drive connection — if the company connects Google Drive, the Google account email, the folder reports are saved to, and an access token (stored encrypted). We request access only to files the App creates in that Drive.
  • Delivered-report records — when a report is delivered to the company's Drive: the report's ID, guard name and date, the Drive file ID, and when it was delivered. The report PDF itself is passed to Google Drive and not stored on our servers.

Shift details, checkpoint scans, photos, locations and incident descriptions stay on the guard's device, apart from what is contained in a PDF report delivered to the company's Drive.

Support. If you contact us through the support form or by email, we receive your name, email address and message so we can reply.

3. How your data is shared

The free App does not automatically share your data with us or with any third party.

The only time your data leaves your device is when you choose to export a PDF shift report and share it (for example, by email or a messaging app). In that case, you decide who receives the file, and its handling is governed by whatever app or service you use to send it. We are not involved in that transfer.

For Team, information is shared only as needed to run the service: with Paddle, which processes Team payments as our merchant of record; with Google, when the company connects Google Drive and reports are delivered to it; and with the hosting and database providers that run our servers.

The Website's analytics and advertising measurement is a separate thing from all of that, it runs only if you agree to it, and section 5 describes it in full. What matters most about it, because these are the questions people ask:

We do not include customer names, email addresses, activation codes, or shift-report content in our purchase measurement events. However, Google may receive browser identifiers and associate measurement data with visits or purchases, as explained in Section 5.

What a purchase does report is the value of the sale and the tax on it, the currency, the number of guard devices, and the measurement reference described in section 5.

The advertising cookie it sets is used to measure whether an advertisement led to a purchase, and advertising personalisation is never granted — see section 5, which also names every cookie involved.

Once measurement data reaches Google, what Google does with it is governed by Google's own policies, which section 5 links. We do not attempt to characterise that processing, here or anywhere else in this policy. Section 9 sets out your rights over it, including the United States opt-out, and how to reach us about them.

4. Third-party services

The App is distributed through Google Play and may use Google Play In-App Review to let you rate the App, along with standard Google Play services. Google may process certain information (such as aggregate install statistics or crash data reported by your device) under Google's own policies, independently of us. See Google's Privacy Policy: https://policies.google.com/privacy.

Team payments are processed by Paddle under its own privacy policy: https://www.paddle.com/legal/privacy. Google Drive delivery uses Google's services under Google's Privacy Policy, linked above.

If you reach our website to purchase Team from the App through Google Play's external content links flow, Google Play gives us a reporting identifier for that visit. If you start a checkout, we keep that identifier with it, and if you complete the purchase we send it to Google, as Google Play requires, to report that purchase. It is not used for anything else.

The App contains no advertising, no third-party analytics, and no tracking SDKs. That is about the App on your phone, and it is unchanged. The Website is different, and section 5 says exactly how.

5. Website analytics and advertising

None of this runs until you agree to it. On your first visit we ask. Until you accept, we load no Google Analytics or Google Ads script and send no measurement request to Google. If you refuse, nothing is loaded on any later visit either, and you can still read every page, choose a number of guard devices and buy Team exactly as before. You can change your answer at any time, here:

Analytics and advertising measurement

Checking your current choice…

This one choice covers Google Analytics and Google Ads conversion measurement.

Turning it off stops any further measurement immediately, and nothing is loaded on your later visits. It does not remove a Google script already running in this page — that goes when you reload or leave it — and it does not delete cookies already stored on your device. You can clear those in your browser settings.

Your choice is kept in this browser only, under the name gtl_consent. It is never sent to us or to anyone else.

What follows describes what happens if you accept.

Our Website uses Google Analytics and Google Ads conversion measurement to understand which pages and which advertisements lead people to buy Guard Tour Log Team. These set first-party cookies in your browser — _ga and _ga_<id>, which tell repeat visits apart; _gcl_au, which Google uses to connect a visit to a later purchase; and _gcl_aw, set only if you arrived by clicking one of our advertisements, so that a purchase can be counted against it. Google may also set cookies on its own domains (google.com, googleadservices.com, doubleclick.net) as part of the same measurement.

If you buy Team, we tell Google that a purchase happened. It is identified by a measurement reference we generate ourselves, on our own server, for this purpose only. It is not your Paddle transaction or order number: it cannot be used to open your activation codes or to look up your purchase, and it contains no name, email address or other personal detail. It is the same reference every time, so that one purchase is not counted twice. Your real transaction reference is never sent to Google.

What that reference does not do is make your purchase anonymous, and we would rather say so than let the paragraph above imply otherwise. It is sent together with the Google cookies described above, so Google can associate it with its own identifier for your browser — and therefore with the other visits that browser made to our Website. Think of it as a label that tells one purchase apart from another, not as a guarantee that the purchase cannot be connected back to you.

The confirmation page also keeps a record of which purchases this browser has already reported, in your browser's local storage, under the name gtl_tracked. It is there for the same reason: so that reloading or revisiting that page does not count the same purchase twice. It stays on your device, is never sent to us or to anyone else, says nothing about you beyond which purchase was yours, and you can remove it by clearing your browsing data.

We use this to measure our own advertising. Two limits are built into the Website itself rather than left to a setting in a Google account: the Website never grants Google permission for advertising personalisation, and it never sends Google your name, email address or any other personal detail alongside a purchase. What Google may do with the data it does receive is governed by Google's own policies, linked below.

Google processes this data under its own policies. See Google's Privacy Policy: https://policies.google.com/privacy and how Google uses information from sites that use its services: https://policies.google.com/technologies/partner-sites.

Your answer to the question above is kept in your browser's local storage under the name gtl_consent. It holds four things and nothing else: whether you allowed analytics, whether you allowed advertising measurement, the version number of the question you answered — so that we can ask again if what we are asking about changes — and the date and time you answered. It contains no identifier for you or for your browser. Like gtl_tracked, it stays on your device, is never sent to us or to anyone else, and you can remove it by clearing your browsing data — after which we will ask again.

Turning it off, exactly. Withdrawing is worth describing precisely, because "off" covers six different things and only two of them are immediate:

  • The tab you are in: we stop sending anything immediately, and Google's tag is told that you have refused.
  • Your later visits: nothing is loaded at all, in any tab, until and unless you turn it back on.
  • Other tabs you already have open: they are not told. A tab you opened before you withdrew carries on as it was until you reload it or close it — so if you have this site open elsewhere, reload those tabs to be certain.
  • A Google script already loaded: it stays in the page you are on. A script cannot be unloaded once it is running; it goes when you reload or leave that page.
  • Cookies already stored: we do not delete them. You can delete them yourself in your browser settings, or install Google's Analytics opt-out browser add-on: https://tools.google.com/dlpage/gaoptout.
  • Data already sent to Google: withdrawing is not a deletion request and it does not recall or erase measurements already transmitted. Google holds those under its own policies and its own retention periods, linked above. If you want data already sent about you dealt with, write to us using the details in section 12 and we will tell you what we are able to do.

None of this affects your ability to buy or use Guard Tour Log Team. The App sets none of these cookies, and the free App on your phone is unaffected by anything in this section.

6. Data retention and deletion

Because all data is stored locally, you remain in full control:

  • You can delete individual shifts, incidents, or photos within the App (where supported).
  • Uninstalling the App removes all data it stored on your device.

For the free App, we hold no copy of your data and therefore cannot access or delete it on your behalf.

For Team, we keep the information in section 2 while the company's account or subscription is in use. A company can disconnect Google Drive and deactivate guard devices at any time, and can contact us to ask for its Team data to be deleted.

7. Children's privacy

The App is intended for use by security personnel and is not directed to children. We do not knowingly collect any data from children.

8. Security

Your data is kept in the App's private storage on your device and is protected by your device's own security (screen lock, operating-system sandboxing). Because the free App does not transmit or store your data externally, it is not exposed to any server-side breach on our side. You are responsible for the physical and access security of your device.

For Team, data is sent over encrypted connections, passwords, activation codes and device credentials are stored only as hashes, and Google Drive access tokens are stored encrypted.

9. Your rights

The free App does not collect or store your personal data on our servers, so for it we hold no personal data to provide, correct, or delete — you manage all of that data directly on your device. For Team, you can ask us to access, correct, or delete the personal data described in section 2. If you have questions about your rights — including under the GDPR or CCPA, where applicable — contact us using the details below.

Withdrawing consent. Website analytics and advertising measurement run only if you agree to them. You can withdraw that agreement at any time, using the control in section 5, and withdrawing is as easy as giving it — one button, in the same place. Section 5 sets out item by item what withdrawing does and does not do, including what it does not reach: other tabs you already have open, scripts already loaded, cookies already stored, and measurements already sent.

United States. California and several other states give you the right to opt out of the sale or sharing of personal information for cross-context behavioural advertising, and to have that right honoured however we would characterise what we do.

How to exercise it here. The clearest way is the control in section 5: you can decline the Website's analytics and advertising measurement before anything loads, or switch it off afterwards. You can also delete the cookies named in section 5, use Google's opt-out add-on linked there, or write to us using the details in section 12 — and if you write to us, we will act on your request and tell you what we have done.

What we can tell you about our own side of it. Two things, both of which are properties of this Website rather than assurances about anyone else: the advertising cookie is used to measure whether an advertisement led to a purchase, and the Website never grants Google permission for advertising personalisation. Beyond that, your data goes to Google and what Google does with it is governed by Google's own policies, linked in section 5. We do not attempt to characterise Google's processing, and nothing in this section should be read as a legal conclusion that it does or does not amount to a sale or to sharing for cross-context behavioural advertising under your state's law. If that distinction matters to your decision, the safest course is simply to decline the measurement, which costs you nothing.

10. Permissions summary

  • CAMERA — QR checkpoint scanning and incident photos.
  • ACCESS_FINE_LOCATION (foreground) — event location stamps.

The App requests each permission at the moment the related feature is first used. You can revoke permissions at any time in your device settings; the related features (scanning, photos, location stamps) will then be limited.

11. Changes to this policy

We may update this Privacy Policy from time to time. Any changes will be posted at this URL with an updated effective date.

12. Contact

Plainside Labs support@plainsidelabs.com


Guard Tour Log is an independent product and is not affiliated with, endorsed by, or associated with TrackTik, Silvertrac, GuardsPro, QR-Patrol, GuardMetrics, or any other mentioned company.