Privacy Policy

1. Introduction / Who we are

MyHopLog (“MyHopLog,” “we,” “us,” or “our”) provides a workforce application for delivery and field drivers and for company administrators. The Android app helps employers record timekeeping, mid-shift breaks, mileage, and route information related to work shifts, and helps managers administer schedules, policies, corrections, and related company workflows.

This Privacy Policy explains how the MyHopLog Android app (the “App”) accesses, collects, uses, stores, shares, retains, and deletes information when you use it. It is intended so that drivers and administrators can understand what happens on their devices, especially regarding location, and so that Google Play reviewers can see how background location is limited to clocked-in mileage recording.

By using the App, you acknowledge this Policy. If you do not agree, do not use the App. Your employer may also have workplace policies about timekeeping, mileage, and device use. Those policies are between you and your employer.

Privacy point of contact: privacy@myhoplog.com
Other inquiries: john@myhoplog.com

2. Scope

This Policy applies to the MyHopLog mobile App used by:

• Drivers and similar field roles who clock in and out, take breaks, and (when enabled) record mileage routes; and
• Company administrators and managers who use in-app admin features for their company (for example schedules, team, corrections, policies, or reports, depending on role and company configuration).

Employer-controlled company data. MyHopLog is typically used under a company account. Much of the information you enter, or that the App generates during work (shifts, breaks, routes, receipts attached to company records, and similar), is processed so your employer and authorized company administrators can operate timekeeping, mileage, compliance, and management features. Your employer often decides how long workplace records are kept and who may view them inside the company. This Policy describes what the App and MyHopLog’s supporting systems do. It does not replace your employer’s HR or privacy notices.

What this Policy does not cover

• Web products that are separate from this mobile App (for example a platform-owner portal or a company admin website), except where they process the same backend data created by the App.
• Third-party websites or services that are not part of MyHopLog.
• Practices we do not perform: we do not sell location data, and the App does not include a third-party advertising SDK or an analytics SDK used for advertising.

3. Information we collect

Depending on your role, company settings, and how you use the App, we may process the categories below. We collect information that is needed for App functionality, reliability, and employer timekeeping and mileage workflows.

3.1 Account and profile

• Email address and authentication credentials (through our authentication provider).
• Name and display identity as configured in your profile.
• Role (for example driver or company administrator) and company membership.
• Profile settings that affect product behavior, including whether mileage tracking is enabled for your profile.

3.2 Timekeeping and work activity

• Clock-in and clock-out events and related shift records.
• Mid-shift break start and end, and break-related state.
• Workplace or hub context associated with shifts where the product uses hubs.
• Schedule-related information your company assigns, viewed or acted on in the App.
• Corrections, policy acknowledgments, training assignments, and similar company-admin workflows when those features are enabled for your company.

3.3 Location information

See Section 4 for the detailed rules. In brief:

• Continuous GPS route capture only while you are clocked in, mileage tracking is enabled for your profile, and you are not on a mid-shift break.
• Limited location uses that are not continuous route logging (for example a one-shot punch location stamp, an optional receipt geotag, or a map “blue dot” while you view a map).

3.4 Photos and media

Photos from the camera or gallery when you choose to attach them (for example receipts). The App does not continuously access your photo library. Access is tied to actions you take.

3.5 Push notification tokens

Device tokens so we can deliver push notifications such as schedule updates, policy or training alerts, and operational alerts related to tracking, as configured by the product and your company.

3.6 Device and diagnostics

Technical information related to GPS capture health and App reliability, used to determine whether location recording is working as intended during a shift. These diagnostics support App functionality. They are not advertising identifiers collected for ads.

3.7 Hosting and related services

App data is processed through our cloud infrastructure, including authentication, database, and file storage used for company records. Uploaded routes, account data, and company records are held under company access controls. Stop addresses, when generated, may be looked up so a shift can show a place name. Maps shown in the App are for display.

3.8 Information we do not collect for advertising

As of the last updated date above, the mobile App:

• Does not include a third-party analytics SDK for advertising or marketing analytics.
• May use Google crash reporting for stability (crash and limited non-fatal error reports). Reports can include device and app version, stack traces, and non-location technical keys. They do not include GPS coordinates, route paths, or street addresses.
• Does not sell location or other personal data.
• Does not use continuous GPS for advertising, remarketing, or unrelated profiling.

If that changes in a future version, we will update this Policy and the relevant Google Play Data safety disclosures.

4. Location information

Location is central to MyHopLog’s mileage and route features. We limit continuous tracking as described in this section. Google Play treats device location as personal and sensitive user data. Background location is used only for the core mileage function described below, not for advertising or analytics.

4.1 Why we need location

Your employer uses MyHopLog to record work mileage and routes while you are on an active shift (when mileage tracking is enabled). Accurate miles and route evidence require collecting location points while you are clocked in, including when the App is in the background or the screen is locked, so recording does not stop merely because you switched apps or locked the phone during a delivery shift.

4.2 Continuous GPS (only while clocked in)

Continuous GPS route capture runs only when all of the following are true:

1. You are clocked in (active shift); and
2. Mileage tracking is enabled for your profile; and
3. You are not in a mid-shift break pause (see Section 4.3).

While continuous recording is active, the App may use Android background location permission (“Allow all the time”), a location foreground service, a wake lock, and a request for battery-optimization exemption, so mileage can keep recording when the App is backgrounded or the screen is locked. Those capabilities apply only to an active, non-paused clocked-in shift with mileage enabled.

While recording, a persistent notification informs you. The notification text is along the lines of: “Recording miles while you are clocked in…”

Before punch-in, the App presents an in-app disclosure explaining that location is used for mileage while you are clocked in, and that route points remain on the device until they are uploaded after punch-out (subject to successful sync, as described below).

4.3 Mid-shift breaks (continuous GPS paused)

During a mid-shift break:

• Continuous route GPS is paused.
• The App does not collect route points for the break period.
• The location foreground service used for clocked-in mileage is stopped for the break.

When the break ends and you return to active tracking (still clocked in, mileage enabled), continuous recording may resume under the same rules as Section 4.2.

4.4 Clock-out (continuous tracking stops)

When you clock out:

• Continuous GPS stops.
• The location foreground service used for mileage recording stops.
• There is no continuous route tracking while you are clocked out.

After punch-out, route points are prepared for upload to your company’s account. After a successful upload, local route points are removed from the device.

4.5 Off-shift and other limited location uses

When you are not in continuous clocked-in mileage recording, the App does not run continuous shift-route GPS. Limited uses may still occur when needed for a specific action or screen:

These limited uses support timekeeping stamps, optional receipt context, and map display. They are not a substitute for, and are not the same as, continuous background route capture.

4.6 What we do not do with location

• We do not sell location data.
• We do not use continuous GPS for advertising or advertising profiling.
• We do not keep continuous GPS running after clock-out.
• We do not keep continuous GPS running during a mid-shift break pause.
• We do not use background location for personal navigation or other purposes unrelated to employer mileage and timekeeping.

4.7 Employer access to route and mileage data

Route and mileage information uploaded after a shift is available to your company under its access controls so authorized administrators can review miles, routes, timekeeping, and related reports. How your employer uses workplace records is governed by your employment relationship and company policies in addition to this Policy.

5. How we use information

We use information to:

• Authenticate you and maintain your account and company membership.
• Operate timekeeping (clock-in and clock-out, breaks, hubs) and related shift records.
• Record mileage and routes while clocked in (when mileage tracking is enabled), including background recording during an active shift as described in Section 4.
• Sync work data to the company account after punch-out and as otherwise designed for the product.
• Support receipt attachments and related documentation when you attach photos.
• Deliver push notifications (schedule, policy or training, tracking alerts, and similar operational messages).
• Provide company admin features to authorized company users.
• Maintain reliability and diagnostics for GPS capture health and App stability.
• Secure the service, prevent abuse, troubleshoot issues, and comply with legal obligations.
• Improve App functionality, without relying on a third-party advertising analytics SDK.

We process information because it is needed to provide the App you and your employer requested (app functionality), to operate a workforce mileage and timekeeping product, and where required by law. Where applicable law requires consent for certain permissions (such as location or notifications), we rely on the permission dialogs and in-app disclosures you see on the device.

6. How we share information

We do not sell your personal information, including location data.

6.1 Your employer / company administrators

Authorized users at your company can access workplace data appropriate to their role, such as shifts, breaks, mileage, routes, schedules, policy acknowledgments, corrections, and related records, through MyHopLog’s products and access controls.

6.2 Service providers

We use service providers that process information on our instructions to operate the App. That includes cloud hosting, authentication, database and file storage, map display, push notifications, crash reporting, and converting coordinates into addresses where the product shows stop addresses. These providers may not use that information to sell ads on our behalf.

Some of those functions are provided by Google (maps shown in the App, push notifications, and crash reports). Maps are for display. Continuous route logging is MyHopLog’s shift-recording logic as described in Section 4. Crash reports do not include GPS coordinates.

6.3 Legal and safety

We may disclose information if required by law, legal process, or governmental request, or to protect the rights, safety, and integrity of users, MyHopLog, or others.

6.4 Business transfers

If MyHopLog is involved in a merger, acquisition, financing, reorganization, or sale of assets, information may be transferred as part of that transaction, subject to applicable law and continued protection consistent with this Policy (or a successor notice).

7. Retention

Retention depends on the type of data and whether it is still on the device or in the company account:

• On-device route points during a shift: kept locally while recording. After punch-out they are uploaded. After successful sync, local points are removed from the device.
• Uploaded routes, shift, break, and company records: retained in the company account for as long as needed for employer timekeeping, mileage, compliance, reporting, and ordinary business operations, and as instructed by the company or required by law. Exact company retention periods may be set by your employer’s policies.
• Account and profile data: retained while your account remains active and thereafter as needed for legitimate business, security, and legal purposes, until deleted under Section 8.
• Notification tokens: retained while needed to deliver notifications to your device, and updated or removed when tokens change or the account or device is no longer used for push.
• Photos and receipts you attach: retained as part of the related company records according to company storage practices.
• Diagnostics: retained as needed for reliability, support, and security.

If you leave your company, workplace records may still be retained by the employer in the company account as business records unless the company requests deletion of the company account.

8. Account and data deletion

If the App allows you to create or hold an account, you may request that the account and associated data we control be deleted. This page is the public web resource for that request. Email privacy@myhoplog.com and include:

• the email address on the MyHopLog account;
• whether this is an individual account deletion or a company account deletion; and
• the company name, if you know it.

Send the request from the address on the account, or from the company owner’s address for a company-wide request, so we can verify that you control it. We aim to complete requests within 30 days. We may send a short follow-up if we cannot match the account.

Temporary deactivation, disabling, or freezing of an account does not qualify as deletion.

8.1 Individual users (drivers and similar)

We will delete your MyHopLog login and the personal profile data we control for that account (for example name, email, role on the account, and device push token).

If you are an employee, some workplace records (shifts, miles, receipts, policy acknowledgments) may still be retained by your employer as their business records. Say in your email if you want only your login deleted. Deleting an employee login does not by itself erase the company’s timekeeping history. Where we must retain a limited record for security, fraud prevention, or law, we will say so.

8.2 Company accounts

A company owner may request deletion of the company account and the workplace data we host for that company (shifts, routes, receipts, memberships, and similar records). We will delete the company data we host, except a limited record we must keep for security, fraud prevention, or law (for example, that a deletion request was completed). We will tell you if any such limited retention applies.

8.3 In the App

Email is the working deletion method on this web resource. The Android App will also include a readily discoverable in-app way to start the same request before the App is submitted for production review on Google Play. Uninstalling the App removes it from the device but does not by itself erase company records.

9. Security

We use administrative, technical, and organizational measures designed to protect information, including:

• Authentication and access controls, including role-based access for company data.
• Encrypted transport to backend services (HTTPS/TLS for network communication).
• Security features offered by our infrastructure providers.
• Limiting continuous location collection to active clocked-in mileage recording as described in Section 4.
• Removing local route points after successful post-punch-out sync.

No method of electronic storage or transmission is completely secure. We cannot guarantee absolute security. Please use a strong password, protect your device, and notify your employer or us promptly if you suspect unauthorized access to your account.

10. Your choices and permissions

• Clock out. Stops continuous GPS route recording and stops the location foreground service used for mileage.
• Mid-shift break. Pauses continuous route GPS for the break period.
• Location permission. You may change Android location permission, including revoking “Allow all the time.” If background location is denied or revoked, the App may be unable to record miles reliably while backgrounded or screen-locked during a clocked-in shift.
• Battery optimization. If you deny or reverse battery-optimization exemption, background recording during a shift may be less reliable on some devices.
• Notifications. You can disable notification permission in system settings. You may miss schedule, policy, or tracking alerts.
• Camera and photos. Deny or revoke media permissions if you do not want to attach receipts. Some attachment features will not work.
• Account and employer. For access, correction, or deletion of workplace records controlled by your company, contact your employer’s administrator. You may also email privacy@myhoplog.com.

11. Children’s privacy

MyHopLog is a workforce application intended for adult employees and contractors of customer companies. It is not directed to children under 13 (or the equivalent minimum age in your jurisdiction), and we do not knowingly collect personal information from children for the App. If you believe a child has provided personal information through the App, contact us and we will take appropriate steps to delete it where required.

12. International transfers

App and account data are processed and stored in the United States by our infrastructure providers. If you use the App from another country, your information may be transferred to and processed in the United States and other countries where those providers operate, which may have different data-protection laws than your own. We do not currently appoint a separate EU or UK representative. Your employer’s configuration may also affect who inside the company can view workplace records.

13. Changes to this Policy

We may update this Privacy Policy from time to time, for example when App features, permissions, or processors change, or when law or Google Play requirements require clearer disclosures. We will revise the “Last updated” date (and the effective date when we publish a new version) on this page. For material changes, we may provide additional notice in the App or by other reasonable means. Continued use of the App after an update means you acknowledge the revised Policy, except where applicable law requires a different approach.

14. Contact us

Questions about this Privacy Policy, MyHopLog’s privacy practices for the mobile App, or a deletion request:

• Privacy: privacy@myhoplog.com
• Other inquiries: john@myhoplog.com

If your question is about employer-held workplace records (shifts, miles, HR decisions), please also contact your company administrator. MyHopLog may need your employer’s involvement to resolve company-data requests that are not a full company-account deletion.