Skip to content
PlanTrackAnalyze

PlanTrackAnalyze Privacy Policy

DRSOLID LLC

Effective date: 16 October 2026

This policy explains how DRSOLID LLC ("DrSolid", "we", "us" or "our") handles information in connection with PlanTrackAnalyze. It covers our website, available app editions, supporting online services, approved direct downloads, sharing features and customer communications (together, the "Service"). A reference to an edition, feature or distribution channel applies only when it is actually offered and used.

Research and commercial statistics. As explained in Section 6, DrSolid may analyze lawfully held information for research, market research, statistics, benchmarking, product development, pricing analysis and marketing. Public or commercially supplied statistical results will not name customers or identify them through individual records. Section 6 explains how we distinguish identifiable source information from genuinely anonymized results.

Privacy and account deletion. Contact support@plantrackanalyze.com. You do not need to install the app or sign in to make an outside-app request. Section 11 explains account deletion, including the separate in-app route.

1. DrSolid, Fleet operators and the people covered

1.1 Company contact. DrSolid is a Wyoming limited liability company. Our business correspondence address is DRSOLID LLC, 2106 House Ave, Suite 498, Cheyenne, Wyoming 82001-3737, United States. Direct Service, privacy, complaint and deletion correspondence to the Company at support@plantrackanalyze.com.

1.2 People covered. This policy applies to account holders, people managing or using a Fleet, people carrying or operating a Tracked Phone, individuals recorded in Fleet information, sharing recipients, support correspondents and website visitors. Personal information includes information that identifies or can reasonably be linked to an individual; a device identifier or movement record may be personal information even without a person's name.

1.3 Company personnel. DrSolid acts through authorized members, managers, officers, employees, developers, contractors, agents, advisers, technology licensors and service providers. Those persons may handle information in their authorized roles for the purposes described here. This policy describes DrSolid's information handling; it does not make an individual acting for DrSolid a separate contracting supplier or a personal guarantor of the Service. The Terms and Conditions address the contractual relationship and applicable protections.

1.4 Fleet decisions. A "Fleet" is the account workspace that holds connected phones, vehicles and operational information. Its owner or authorized administrator (the "Fleet operator") decides which phones to connect, what to record and enter, how assignments are made and who receives shared access. The Fleet operator is responsible for the authority, notices and permissions required for its monitoring, instructions and use of information.

1.5 Processing roles. DrSolid generally handles customer-directed Fleet information on the Fleet operator's behalf where the law treats DrSolid as a processor or service provider. DrSolid determines the purposes of its own account administration, security, legal compliance, business communications and any independently undertaken research described in Section 6. The applicable role depends on the actual activity and law. The Terms' applicable processing appendix governs processing on the Customer's behalf; Section 6 addresses separately described research.

2. Information we handle and its sources

2.1 Accounts and access. Google sign-in supplies an account identifier, email address and available profile information, such as a display name or profile image. We handle Firebase identifiers, Fleet identities, roles, account status, pairing invitations, device principals, access credentials or tokens, authorization decisions, and relevant acceptance or permission records. Google sign-in does not give PlanTrackAnalyze your Google password or access to your Gmail messages or contact list.

2.2 Fleet and business information. We handle information that you, your Fleet operator or other authorized users enter or upload: business and customer details; operator information; trucks, vehicles and Phone Cards; phone numbers and labels supplied in those records; Sites, addresses and geofence areas; Plans, Actions, schedules, assignments and guidance; settings, rates, prices, costs and other supported operational fields. These records can concern people who do not hold a PlanTrackAnalyze account.

2.3 Location and movement. An enabled Tracked Phone records precise location, timestamps, accelerometer motion and available sample information such as accuracy, altitude, speed, direction and location-provider status. The Service processes these inputs into live positions, routes, stops and moves, activity estimates, history, Site timelines, distances and planned-versus-actual results. Records can be associated with a Fleet, phone, assigned truck, operator, Site or Action. Location histories can reveal information about a person's movements and visits.

2.4 Phones, equipment and recording status. We handle app-scoped device-recognition and installation identifiers, device model and manufacturer, app and operating-system information, pairing and session records, notification tokens, battery and charging status, storage availability, connectivity and recording-health information. Account, pairing and technical records can be processed before recording is started. A phone number entered into a Phone Card is distinct from reading a device's contact list or call history.

2.5 Fuel information. Fuel-related records may include equipment and sensor identifiers, vehicle or model descriptions, configuration, calibration, connection information, supported measurements, consumption estimates and user-entered costs. Collection from Bluetooth equipment depends on a supported, enabled feature, compatible equipment and the required permissions. A saved equipment description does not by itself mean that measurements are being collected or decoded.

2.6 Files, guidance and support. We receive messages and supported images, videos and other files you choose to submit. Guidance files form part of the relevant Fleet operation. In-app support and custom-feature requests also create a diagnostic Fleet snapshot, which can include a broad copy of Fleet documents, operational history, information about other people, and references to associated files. Submitted attachments and diagnostic copies are separate from the message text. You can use ordinary email for an inquiry that does not need a Fleet snapshot.

2.7 Purchases and financial records. App stores or other payment providers identified for an offer process payment. We receive available purchase references, verification tokens, product and order information, subscription and renewal state, capacity, price, currency, refunds, chargebacks, entitlement and related transaction records. We use these to connect a purchase with its Fleet and administer the business. Google Play does not provide DrSolid with the full payment-card details you give Google Play.

2.8 Maps, search, invitations and sharing. Map and address features send the relevant requests, address queries or coordinates to the map or geocoding provider. Invitations, installation-link/referrer information and sharing sessions can carry identifiers or tokens used to open the requested Fleet, pairing flow or shared view. We handle sharing grants, scope, expiry, redemption and access/security records, and generated export or file-access information.

2.9 Technical and website information. The Service, devices and providers handle request times, IP addresses, browser or device details, page or resource requests, authentication events, errors and delivery/security logs. Website content and images may be supplied through hosting or content-management providers. Administrative website tools have their own authenticated activity; using an ordinary public page does not itself create a Fleet or purchase a subscription.

2.10 Sources and relevance. Information comes from you, the device, the Fleet operator and authorized users, selected recipients, sign-in and payment providers, and providers involved in a Service function. We may link relevant records, including across devices within a Fleet, to carry out the purposes below. Do not submit passwords, private keys, unrelated sensitive documents or information you are not authorized to provide.

3. Recording, background operation and controls

3.1 Separate Tracked Phone operation. Using the manager workspace does not automatically enable that installation for background Fleet recording. A phone must be connected as a Tracked Phone, its operator must receive the applicable recording disclosure and give the required agreement and permissions, and recording must be enabled and authorized. This does not prevent the account, map-request and technical processing needed for other functions.

3.2 Automatic and background operation. After the Tracked Phone operator agrees and grants the required permissions, recording may start automatically when its Phone Card has subscription access and is selected by the manager. Enabled location and motion collection can continue while the screen is off or the app is not visible. An enabled session can resume after a supported interruption, renewed authorization, restored location availability or an allowed restart. The operating system can restrict operation or require the app to be reopened. The enabled recording session is identified through its ongoing notification and in-app state.

3.3 Stop and remote changes. The Tracked Phone's Stop control stops new recording and remains stopped until the operator starts it again. Location, accelerometer and configured Fuel collection use the same tracking Start/Stop. You can change the relevant operating-system permissions. A manager can deactivate a Phone Card, but an offline phone applies the change when it receives it; a remote change is not an instantaneous offline stop mechanism.

3.4 Existing evidence. Stopping recording does not delete information already collected. Existing evidence can remain locally and may upload or finish processing afterward. Successful upload does not necessarily remove the local copy. Device loss, app-data clearing, storage pressure, permissions and operating-system behavior can affect information and availability.

3.5 Permission choices. Location, notifications, Bluetooth and media access have separate purposes. A denied or withdrawn permission can prevent the function that needs it. Accepting the Terms or reading this policy does not replace a required operating-system permission or a separate in-app disclosure and consent. Additional uses requiring a separate choice are subject to that choice.

4. Service operation and business purposes

4.1 Supplying the Service. We use relevant information to authenticate and authorize accounts; establish and manage Fleets and pairing; provide planning, recording, history, fuel, analysis, guidance, sharing and exports; connect assignments and results; verify subscriptions; allocate capacity; and answer requests.

4.2 Supporting operations. These activities include hosting, copying, organization, indexing, synchronization, caching, replication, backups where used, diagnostic snapshots, logging, testing, troubleshooting, correction, migration, restoration attempts, maintenance, security, fraud and misuse prevention, and improvement of Service functionality, reliability and performance. Both automated processing and authorized human access may be involved. A separate approval is not requested for each ordinary action within the authorized scope; additional permission is obtained where required.

4.3 Business administration. Relevant records support customer communication, financial reporting and verification, accounting, audit, pricing and demand analysis, professional advice, investment or business discussions, legal compliance, dispute handling, and establishing, exercising or defending rights. The recipient arrangements in Section 5 and the research and marketing provisions in Sections 6 and 7 apply.

4.4 Applicable legal bases. Where a legal basis is required, we rely on the appropriate basis for the activity: contractual necessity for a requested service supplied to the individual; legal obligations for mandatory records or disclosures; appropriately assessed legitimate interests for activities such as security, technical support, business administration and compatible improvement; and consent where required for location or other sensitive-data handling, a secondary use, marketing or optional website technologies. Fleet processing on another organization's behalf follows its lawful instructions and the applicable processing arrangement. Contractual permission does not substitute for another person's required consent.

4.5 Automated results. Automated processes calculate outputs and apply access, entitlement, capacity and security rules. Results can be incomplete or incorrect. They are not a certification of an individual's conduct, work, costs or entitlement under an employment arrangement. Direct suspected Service errors to DrSolid and questions about a Fleet operator's employment or operational decision to that operator. Applicable rights concerning significant automated decisions can be exercised through Section 11.

5. Recipients and authorized access

5.1 Fleet users and selected recipients. The Fleet owner and authorized users receive information within their access. Sharing can provide selected live, historical, planning or guidance information to recipients chosen by the Fleet operator. A person with a usable invitation, bearer link or shared session may be able to access its permitted content; a recipient label is not identity verification. Keep access links private. Revocation limits future authorized Service access but cannot recall an independently downloaded copy and may not invalidate an already issued short-lived file URL before it expires.

5.2 Providers and personnel. We use Google services for identity, Firebase/Google Cloud storage and processing, messaging, Maps/Places, invitation scanning and Google Play commerce. Website delivery, security, content management and email routing may involve Cloudflare, Sanity and the relevant email provider. Authorized personnel, developers and technology licensors may receive or access information for the technical, operational, support, research, financial and administrative activities described in this policy. Access follows the relevant authorization and service, confidentiality, security and data-processing arrangements. Providers retained to process information for us must provide the protections required for that processing. Some providers separately determine their own processing, such as payment administration and account security, under their own terms.

5.3 Financial and professional recipients. Relevant information may be provided to members, managers, technology licensors, auditors, accountants, legal and other professional advisers, prospective investors, financiers and purchasers for accounting, verification, advice, financing, valuation or business discussions. Information supplied is appropriate to the purpose; identifying details are removed or limited when unnecessary. A financial-reporting purpose does not authorize handing a recipient unrestricted Fleet access or unrelated location histories.

5.4 Legal and protective recipients. We may disclose information to authorities, courts, advisers or other appropriate recipients where required by law or valid legal process, or where reasonably necessary and lawful to investigate misuse, protect the Service or people, enforce terms, or establish, exercise or defend rights.

5.5 Transactions and succession. Relevant account, subscription, Fleet, history, file and support information may be disclosed or transferred in connection with a proposed or completed investment, reorganization, financing, merger, sale or transfer of the Service or its customer operation, including to a technology licensor or successor operator. Due-diligence disclosures use appropriate restrictions. A receiving operator must have lawful authority and the required privacy responsibilities. We provide notice and obtain consent where required; an operational transfer does not itself authorize an unrelated new data use.

5.6 Other requested disclosures. We may disclose information when you use a function that requires the disclosure, instruct us to do so within your authority, or provide another valid permission. Section 6 separately addresses non-identifying research and commercial results.

6. Research, market research, statistics and commercial results

6.1 Authorized purposes. DrSolid may use lawfully held Service information to conduct research and market research; draw statistical conclusions; measure patterns, demand and performance; develop and improve products and services; benchmark operations; analyze costs and pricing; and prepare commercial reports, demonstrations and marketing materials. These activities may benefit DrSolid commercially and are not limited to resolving a support request for the contributing customer.

6.2 Examples and inputs. Analyses may concern average or typical speed and travel time on a road or within an area; stopping, activity or Site-duration patterns; fuel consumption by area, road conditions, truck make, model, configuration or other relevant vehicle characteristics; distances and operational efficiency; prices, rates, costs and market trends; and relationships between planning inputs and observed results. Inputs may include customer-entered rates and costs, device and vehicle evidence, usage and transaction information, and other lawfully usable information. We may combine suitable contributions from more than one Fleet and with other lawful datasets. A calculation is undertaken only where the required inputs are available; these examples do not promise a particular report or measurement feature.

6.3 Internal analysis and anonymization. Preparing statistics may require authorized analysis of identifiable or coded source information, including comparing records over time and producing derived measures. That source processing remains subject to this policy, applicable processing-role restrictions and the required legal basis, notices and permissions. Where DrSolid determines an independent research purpose, it takes the corresponding responsibility for that processing rather than treating the customer as responsible for DrSolid's independent decision. Information subject to a restriction on independent use or cross-customer combination is excluded unless the permitted basis for the proposed processing has been established.

6.4 Non-identifying external results. Before research results are published, supplied commercially or used in public marketing, they must be genuinely anonymized or aggregated so that neither an individual nor a contributing customer or Fleet is reasonably identifiable in the intended context. We do not include customer names, account identifiers, identifying vehicle details, raw individual location histories or identifiable customer-specific prices in those outputs. Removing names alone is insufficient. Depending on the information, preparation may require combining observations, generalizing locations or dates, using ranges, removing unusual or small-group results, or withholding a result that remains identifiable. Data that can still reasonably be linked back remains protected information, not anonymous information.

6.5 Use and commercial rights. DrSolid may retain, combine, use, publish, distribute, license or sell qualifying anonymized datasets, statistical conclusions, benchmarks and reports, and use them in marketing, product development and commercial decisions, without identifying the contributing customers. Appropriate results may be made available to customers, partners, research organizations or other commercial recipients. No payment, royalty, revenue share or separate approval is owed to a customer merely because its information contributed to those qualifying outputs, except under a separate express agreement or applicable law. Independent third-party data and intellectual-property restrictions remain applicable.

6.6 Re-identification and ongoing use. We maintain information represented as anonymized in non-identifying form, do not attempt to re-identify it except for a legally permitted effectiveness assessment, and require recipients of nonpublic anonymized datasets not to attempt re-identification. Qualifying anonymous results may continue to be used after an account closes or its source records are deleted, because they no longer identify or remain linked to that account. Records that remain identifiable do not acquire indefinite retention merely by being called research.

6.7 Required choices and limits. Acceptance of the Terms records the customer's contractual authorization for the purposes above. Where a law or platform requires separate consent for the underlying source processing, we obtain it before that processing and provide the required withdrawal route. Declining consent for a genuinely optional research use does not remove access to unrelated paid functions. We do not sell personal or sensitive app-user data or disclose identifiable location or motion histories for advertising or data brokerage. Commercial use of qualifying anonymized results is distinct from such a sale.

7. Communications and marketing

7.1 Service communications. We use appropriate contact and delivery information for account, security, subscription, service-change, legal and support messages. These are distinct from optional promotional communications.

7.2 Company marketing. Where lawful, DrSolid may use appropriate account or business contact information and non-sensitive commercial interactions to communicate relevant products, offers, updates, surveys and feedback invitations. We obtain marketing consent when required and provide the applicable unsubscribe or other opt-out route. Marketing may draw on the anonymized market insights described in Section 6. We do not use identifiable location histories, motion histories or complete support snapshots to construct advertising audiences.

7.3 Marketing disclosures. We do not sell personal information or share it for cross-context behavioral advertising under the practices described here. Providing your contact details to another business for its independent marketing requires the applicable notice and lawful permission; this policy is not, by itself, that permission. We do not present a named customer, identifiable testimonial or customer logo as an endorsement without authorization.

7.4 Choices. Follow the unsubscribe instructions or email support@plantrackanalyze.com with "Marketing preference" in the subject. We may keep limited suppression records to respect the choice. Opting out of marketing does not prevent necessary Service communications or use of qualifying non-identifying statistics.

8. International processing and security

8.1 Locations. The primary application database and application storage are hosted in the United States. Authorized personnel and providers may access or process information in Australia and other countries in which they operate. Website delivery, content distribution, support and provider infrastructure can involve additional locations. Hosting in one country is not a promise of exclusive processing in that country.

8.2 Transfers. Where an international transfer requires safeguards, we use an applicable lawful mechanism, such as an adequacy arrangement or approved contractual safeguards with required supplementary measures. Relevant processing and provider terms also apply. Contact DrSolid for information about applicable safeguards and a copy where the law provides one, with lawful redactions. Acceptance of this policy does not waive required transfer protections.

8.3 Security and limitations. We use technical and organizational measures appropriate to the information and operation, including authenticated access, authorization rules and encrypted network transport where applicable. Authorized access may be needed to provide the Service; this is not a claim of end-to-end encryption against DrSolid or all its providers. No system can guarantee absolute security, uninterrupted availability or freedom from accidental loss, corruption, disclosure or error. We handle incidents and provide notices where required. Safeguard your accounts, devices and access links and report suspected unauthorized use promptly.

9. Retention and deletion of operational copies

9.1 Purpose-based retention. Retention varies by information and use. We retain information for periods reasonably needed for the disclosed service, operational, research, support, security, financial, contractual and legal purposes, subject to applicable requirements, valid requests and processing instructions. Relevant factors include account activity, ongoing history access, the purpose and sensitivity of the information, troubleshooting needs, payment reconciliation, possible or existing claims, and mandatory preservation duties. Retention is not a promise of permanent storage or recovery.

9.2 Categories. Account and Fleet records support the customer relationship, ongoing functions and retained history. Raw evidence and derived results may have different operational lives. Support communications, attachments and Fleet snapshots support diagnosis, follow-up and relevant claims. Technical records support delivery, fault analysis, security and misuse prevention. Financial and contractual records support administration, reporting, verification and legal requirements. Temporary and redundant working copies can have separate cleanup processes. We assess continued need rather than applying an unlimited retention rule to every category.

9.3 Subscription cancellation. Cancellation does not request account deletion. Account, Plan, vehicle, Site, settings and history records are kept for continuing access or a return to the Service, subject to ongoing lawful need, the applicable service arrangements and valid deletion requests. After subscription access ends, raw accelerometer recordings may be manually removed to manage storage costs; this particular cleanup does not delete other Fleet records or recorded location history. Recalculation requiring the removed raw files may no longer be possible. Resubscribing does not guarantee restoration of deleted information.

9.4 Copies and backups. Local-device evidence, support snapshots, generated exports, active records and provider recovery copies may be separate copies. Removing one does not necessarily remove all others immediately. Following a valid deletion request, relevant copies under our control or our processors' control are addressed through the deletion process. Where immediate removal from a protected backup or recovery system is not technically feasible, retained copies are restricted from ordinary use and expire or are deleted through the applicable process; required deletions are reapplied following restoration. No universal backup period or fixed recovery guarantee is created by this policy.

9.5 Retained exceptions and anonymous results. Necessary financial, security, fraud-prevention, dispute or legally required records may be retained for the justified purpose after account deletion. They are not retained for unrelated new use. Genuinely anonymized results described in Section 6 can be retained and used without an account-linked retention period. Use of anonymous results does not extend the permitted retention of identifiable source records or override an applicable deletion or withdrawal requirement.

10. Website technologies and external services

10.1 Delivery and administration. Hosting, security, content management, email routing, preferences and requested interactions can involve cookies or similar storage, technical logs and service-provider processing. Cloudflare and Sanity support the website functions for which they are used. The website's administrative Studio is distinct from ordinary public browsing and may involve separate login, administrative diagnostics and provider processing.

10.2 Optional tools. Where optional visitor analytics, marketing tools or embedded third-party content are introduced, we identify the relevant purposes and provide the consent and controls required before they operate. Ordinary browsing or acceptance of the Terms is not substituted for required permission. Browser storage controls can affect a function that depends on them. This policy does not assert that every technology mentioned is enabled on every page.

10.3 External interactions. Following a store link, using Google sign-in, requesting Maps/Places content, opening an externally hosted file or contacting us through an email provider involves that provider's processing and terms. Google Maps features and content are subject to the Google Maps/Google Earth Additional Terms of Service and Google Privacy Policy. Third-party sites are not operated under this policy merely because we link to them. DrSolid's own disclosures and instructions to providers remain within the responsibilities applicable to those activities.

11. Account deletion and privacy requests

11.1 Outside the app. Email support@plantrackanalyze.com with the subject "Delete PlanTrackAnalyze account". Include the account email, Fleet identifier if known and enough information to identify the account and request. No app installation or login is required to initiate this request. Do not send your password, full payment-card number or unnecessary identity documents.

11.2 In the Android app. The Fleet owner opens Admin → Manage subscription in Google Play → Delete account and data → Review deletion request → Request permanent deletion, and confirms the identified account and Fleet. Checking the box or opening Google Play alone does not submit the request. A receipt confirms that the request was received, not that erasure is already complete. Requests are reviewed and fulfilled; the workflow is not a promise of instantaneous erasure.

11.3 Scope and subscription distinction. A confirmed whole-account request covers the associated account and Fleet, including Plans, Phone Cards, assignments, history, sharing permissions and uploaded files, subject to the limited justified exceptions in Section 9. Deletion is not merely deactivation. Cancel renewal separately through the payment platform; cancellation is not a prerequisite for submitting a deletion request. Deleting PlanTrackAnalyze does not delete the underlying Google or other provider account or the provider's independent payment records.

11.4 Verification and completion. We may verify identity, account authority and the scope of the request and coordinate with the relevant Fleet operator or provider. We handle requests within applicable legal and platform requirements, communicate expected processing and any justified extension or retention, and address relevant provider copies. Once information is deleted, recovery through the Service is not promised. Independently downloaded copies and devices outside our control may require action by their holders; we provide assistance where required.

11.5 Requests by affected individuals. A person whose information appears in a Fleet can contact its operator or DrSolid about their own information without having authority to delete the whole Fleet. Explain the relevant record and concern. We route or address the request according to the actual processing role and applicable requirements, without disclosing another person's protected information merely because a request is made.

11.6 Other applicable rights. Depending on the law that applies, you may have rights to know about or access processing, obtain a copy, correct information, request deletion, restrict or object to processing, obtain portability, withdraw consent, and challenge certain solely automated decisions. Applicable United States laws may also provide sale, targeted-advertising, sensitive-information or profiling choices and an appeal. We honor rights and legally required preference signals where applicable; listing a right does not extend every jurisdiction's procedures to every user. We explain any lawful refusal, charge or limitation and accommodate authorized representatives where required.

11.7 Consent, complaints and appeals. Use the relevant control or contact DrSolid to withdraw a consent or raise a privacy complaint. Withdrawal applies to future consent-based processing and does not invalidate earlier lawful activity. A necessary feature may cease to work when its required information or permission is withheld. Where an internal appeal is available, reply to the decision requesting review. You may complain to the competent authority, including the relevant United States authority, EEA supervisory authority, UK Information Commissioner's Office or Australian Office of the Australian Information Commissioner, as applicable. Required rights and non-discrimination protections remain available.

12. Responsible use and children

PlanTrackAnalyze provides planning and phone-based operational capabilities. It is not directed to children or offered as a child-tracking, stalking or covert-surveillance service. A customer must establish lawful authority for connecting and monitoring a phone, provide required notices, obtain required permissions, respect applicable workplace and off-duty restrictions, and control its selected recipients. Device ownership alone does not resolve every required permission.

We do not knowingly solicit children's information for marketing. Contact DrSolid about unauthorized information concerning a child or another person so that we can assess the circumstances and take the action required. Customers must satisfy applicable legal-capacity and distribution-channel requirements; the Terms describe their permitted use.

13. Changes and relationship to the Terms

We publish the effective date of this policy and update it as information handling changes. We provide the notice and obtain the additional permission required for a material change. A new publication does not retroactively authorize a use incompatible with the notice or permission governing previously collected information.

This policy explains information handling. The separately accepted Terms and Conditions address contractual permissions, responsibility for use, Service limitations and applicable liability protections. Neither document substitutes for a consent or disclosure specifically required for a feature. Direct inquiries to DRSOLID LLC — support@plantrackanalyze.com.