TechDashers Privacy Policy

This Privacy Policy describes how we collect, use, share, and retain personal information when you use the TechDashers mobile applications, websites, and related services (the “Platform”). It should be read with the Platform Terms of Service (the “Terms”) and the Acceptable Use Policy. Technicians are also subject to the Independent Contractor Agreement.

We do not sell your personal information for money. We share information as described in Section 6 to operate the marketplace.

#1. Scope; Controller; d/b/a

(a) Controller. NexGen PC Logic, LLC d/b/a TechDashers is the business that determines the purposes and means of processing personal information described in this Policy, except where a third party (such as Stripe or Agora) processes data as an independent controller under its own policy.

(b) Who this covers. This Policy applies to Clients, Technicians, website visitors, and support correspondents. It does not apply to a Technician’s own processing of Client data on the Client’s machine during a TechDash, except that Technicians are contractually restricted as described in the Terms, AUP, and ICA.

(c) Service geography. The Platform currently focuses on Central Florida service operations. We may collect information from Users located elsewhere in the United States who create accounts or visit our websites.

(d) Definitions. Capitalized terms not defined here have the meaning in the Terms.

#2. Categories of Personal Information We Collect

Depending on your role and features you use, we may collect:

(a) Identity and contact. Name, email address, phone number, account role (Client or Technician), technician public code, profile photo, bio, skills, certifications listed on a public profile, languages, and city.

(b) Authentication. Email/password credentials (stored by our auth provider), Google OAuth identifiers, Sign in with Apple identifiers, session tokens, and multi-factor or step-up authentication status.

(c) Addresses. Saved addresses (recipient name, phone, street, city, state, postal code, country, delivery instructions), latitude/longitude, address-validation results, and whether an address is a Client location or Technician workbench.

(d) Service and device information you provide. Ticket title and description, service type, device type, model number, photos and attachments, meeting instructions, and notes.

(e) Location. Client GPS and reverse-geocoded city when you request on-site matching or update a profile location; Technician last-active coordinates when Online for dispatch; En Route coordinates associated with a ticket; location-history records used for dispatch and audit; and, when a Technician accepts an on-site request with Extended Reach, the distance from the Technician’s reported location to the service address at acceptance, used to set the travel reimbursement.

(f) Communications. In-app chat text, image attachments, support-ticket messages, call lifecycle metadata (started, answered, missed, completed, duration), notification preferences, and push-notification device tokens.

(g) Payments. Stripe customer ID, default payment-method token (not the full PAN), Connect account ID and payout-capability flags for Technicians, transaction amounts, escrow/hold status, invoice and receipt data, tips, coupons, and Florida tax amounts and county used for tax calculation.

(h) Hardware and custody. Hardware Quotes and orders, shipping snapshots, barcodes or scanned identifiers used for custody verification, intake photos stored in our custody bucket, and supplier or catalog identifiers (for example, ASIN or vendor order IDs).

(i) Technician verification documents. Documents you upload (driver license, insurance, certifications, licenses, degrees) stored in restricted buckets and accessed via signed URLs for review. We do not collect Social Security numbers, ITINs, or EINs in the TechDashers application database; tax identity for payouts is collected by Stripe Connect under Stripe’s policies.

(j) Vetting and safety. Onboarding status, vetting-quiz status, background-check status (for example, passed/pending), account status, dormancy flags, blocks, reports, and dispute records (which may include name, email, phone, and a compiled audit manifest).

(k) Reviews and reputation. Star ratings, written reviews, and related ticket identifiers. Technician rating totals are calculated by our systems from reviews.

(l) Job records and availability. A timestamped record of each ticket’s events (for example: request created, offers and alerts sent, claims and releases with the reason given, acknowledgment, arrival, diagnosis start, quotes sent, approved, or declined, completion, cancellation and who cancelled, refunds, disputes, reviews, and tips), and, for Technicians, when they go online and offline for on-demand work. We use these records to dispatch, pay, provide support, resolve disputes, prevent fraud, measure service quality (for example, response and completion times), and improve the Platform. They are not shown to other users.

(m) Device and log data. IP address, user agent, app version, OS, crash-adjacent diagnostics we may collect through the OS or host, and terms-acceptance records (agreement version, timestamp, IP address, user agent).

(n) Local device data we do not upload as biometric templates. Biometric unlock is optional and performed by your device (for example, Face ID). We store an opt-in preference and may store refresh tokens in the device secure storage. We do not collect or store your facial geometry or fingerprint templates on Company servers.

(o) Information we do not collect in-app. Date of birth (except as a third-party screener may collect directly), government tax ID numbers in our application database, children’s accounts, or Agora/Getscreen session recordings.

(p) Account standing and claims. Account standing records (reports about you or that you make, strikes, your responses and appeals, staff decisions, and restrictions); an audit log of staff actions on accounts; damage-claim records under the Service Guarantee and the photos and files uploaded with them; and chat-filter flags, including the original text of masked messages, kept for staff review.

(q) Phone verification and text messages. Whether and when your phone number was verified, and the type of number (for example, mobile or internet-based) where our communications provider reports it. If you use job alerts by text or call: your alert settings (channels, alert types, and hours), records of your consent and opt-outs (the wording you agreed to, when, and any STOP reply), and a record of the texts and calls we send you, such as the time and delivery status.

#3. Sources of Personal Information

We collect information:

• From you, when you register, book, chat, call, upload documents, pay, review, dispute, or contact support;
• From your device, including OS permissions you grant (location, camera, microphone, photos, notifications, Face ID);
• From the other party to a TechDash, for example messages they send you;
• From service providers, including Stripe (payment status), address-validation and shipping providers, Agora (call connectivity, not media archives), Getscreen (session provisioning metadata such as invite codes and connection URLs stored on the ticket), email and push vendors, communications providers that send our text messages and calls (delivery status, opt-out replies, and the type of phone number), and background-check vendors that return a status to us;
• From catalogs and suppliers, when a Technician searches parts or we procure hardware; and
• Automatically, through application logs and essential cookies or local storage on the website.

#4. Cookies, SDKs, and Tracking Technologies

(a) Mobile application. The TechDashers apps use device identifiers, secure storage, and third-party SDKs required to operate (including Stripe, Agora, maps, our backend SDK, and, on Android, Google Firebase Cloud Messaging to deliver push notifications). We do not currently integrate consumer analytics suites such as Firebase Analytics, Mixpanel, Amplitude, or Sentry in the application dependency list.

(b) Website. Our websites may use essential cookies or local storage for login, security, and load balancing, and functional cookies to remember preferences. Disabling cookies may prevent login or booking. We also use Google Analytics on techdashers.com to understand how visitors find and use the website: pages viewed, how they arrived (for example, a search or a link), approximate location from the IP address, device and browser, and actions such as tapping an app store link or submitting an application. Google Analytics uses cookies. We turn off Google’s advertising features, and we do not send your name, email, phone number, or application details to Google. You can opt out with Google’s browser add-on at https://tools.google.com/dlpage/gaoptout. If you join the coverage waitlist on techdashers.com, we keep your email, city, and the kind of help you need, only to tell you when we serve your area; you can ask us to remove it at any time.

(c) No sale via advertising pixels. We do not currently operate a cross-context behavioral advertising pixel program on the core app. If that changes, we will update this Policy.

(d) OS permissions. iOS and Android will prompt for Location (When In Use), Camera, Microphone, Photo Library, Notifications, and (on iOS) Face ID as needed. On Android, while a Technician is online for on-demand work or en route, and during a call, the app runs with a visible ongoing notification. You may deny permissions; some features will not work.

#5. How We Use Personal Information

We use personal information to:

• create and secure accounts, including terms-acceptance audit trails;
• match Clients and Technicians, schedule TechDashes, and display ETAs;
• provide chat, push notifications, email receipts, and incoming-call ringing;
• use your phone number to verify your account (with a one-time code sent by text message or read in an automated call), help prevent fraud and fake or duplicate accounts, send the text messages and calls described in Section 15(f), and help Clients and Technicians coordinate a TechDash;
• provision Getscreen invite codes and Agora tokens for an eligible ticket;
• process Authorization Holds, captures, refunds, Hardware Quotes, tips, and Technician payouts;
• calculate Florida sales tax and maintain tax records;
• perform Spot Audits, fraud prevention, Rate Card enforcement, and AUP enforcement;
• enforce the Terms and AUP through account standing (reports, strikes, responses, appeals, and restrictions), and decide Service Guarantee damage claims;
• operate in-app disputes, including compiling chat transcripts and payment history;
• verify Technicians, review credentials and insurance, and record background-check status;
• if a Technician elects Platform Coverage (when offered), enroll the Technician with the insurance provider, report covered TechDashes, support claims, and deduct any premium the Technician authorizes;
• improve safety, quality, and Platform reliability, including aggregated metrics;
• comply with law, card-network rules, tax, and lawful requests; and
• communicate service updates and, where permitted, limited service-related announcements.

#6. How We Share Personal Information (Processors and Assignees)

We share personal information as follows:

(a) Assigned Technicians and Clients. To complete a TechDash, we share necessary contact, service, and (after assignment) street-location details with the other party. Unclaimed / pool Technicians see city-level location and masked contact, not street address. Directory search returns distance without exposing raw coordinates or street addresses.

(b) Service providers (processors or similar).

(c) Professional advisors and authorities. We may share information with lawyers, insurers and claims administrators (including any Platform Coverage provider, as needed for a covered claim), accountants, and with law enforcement or regulators when required or when we believe in good faith that disclosure is necessary to protect safety or rights.

(d) Corporate transactions. We may transfer information in connection with a merger, financing, or sale of assets.

(e) With your direction. For example, if you ask us to send a receipt to an additional email.

(f) No unrestricted public listing of Client home addresses. Technician public share pages show Technician profile information you elect to make public, not Client addresses.

(g) Account standing and damage claims. Account standing and claim records described in Section 2(p) are seen by TechDashers staff. For a damage claim, the other party to the claim sees the claim, the Technician’s response, and the decision. Strike details are shown only to the person they are about.

(h) Mobile phone numbers and text-message consent. We do not sell, rent, or share mobile phone numbers or text-message opt-in data and consent with third parties or affiliates for their marketing or promotional purposes. Text-message opt-in data and consent are shared only with the communications service providers that send our text messages and calls on our behalf, or when the law requires it; they are not part of any other sharing described in this Section 6.

We require service providers to use information only to perform services for us or as required by law, except where they are independent controllers (notably Stripe, Apple, Google, Agora, and Getscreen for data they process under their own terms).

#7. Location Information

(a) Why we collect it. Location enables radius matching, fraud/safety audits, En Route maps, and Live Activities.

(b) Technician Online pings. While a Technician is toggled available for on-demand dispatch, we periodically capture location for Haversine matching within selected radii (illustratively 5–30 miles), and record the Technician’s location when they accept a request to confirm they are within range and to set any Extended Reach amount. Clients browsing technicians see only an approximate whole-mile distance from the Technician’s work address, never the Technician’s live location.

(c) En Route. During an active En Route status, higher-frequency location may be associated with the ticket so the Client can see progress. Background location on iOS is used for this operational purpose when the Technician has granted the relevant permission; on Android, location is updated while the Technician is online or en route with a visible ongoing notification. It is not used for unrelated advertising.

(d) Client location. Creating an on-site ticket or updating a Client profile location may store coordinates and city.

(e) History. We may retain location-history records (for example, Technician on-demand pings, Client profile updates, ticket creation) for dispatch accuracy, safety, and audits.

(f) Control. You may disable OS location permissions. Doing so will degrade or disable on-site matching, En Route tracking, and related features.

#8. Payments (Stripe; Apple Pay; Google Pay)

(a) Stripe. Card numbers are entered into Stripe-controlled fields. TechDashers stores Stripe identifiers and transaction metadata. Stripe’s privacy policy governs Stripe’s processing: https://stripe.com/privacy.

(b) Apple Pay. If you use Apple Pay, Apple and Stripe process wallet data under their policies. Apple Pay does not make Apple the seller of TechDash services.

(c) Google Pay. If you use Google Pay, Google and Stripe process wallet data under their policies. Google Pay does not make Google the seller of TechDash services.

(d) Technician payouts. Connect onboarding collects tax and identity information on Stripe’s platform. We receive Connect account status (for example, whether charges and payouts are enabled) necessary to permit claiming jobs.

(e) PCI. Payment-card data is handled in accordance with Stripe’s PCI-DSS responsibilities. We are not a card vault.

#9. Remote Sessions (Getscreen) and Real-Time Communications (Agora)

(a) Getscreen. When a remote session is provisioned, we store an invite code and connection URL on the ticket. Getscreen processes the remote-desktop stream. TechDashers does not record Getscreen sessions (no session video, keystroke logs, or remote-desktop archives on our servers).

(b) Agora. We mint time-limited publisher tokens so ticket participants (and, in limited cases, authorized support staff) can join a voice/video channel named for the ticket. TechDashers does not retain call audio or video. We do retain call metadata as described in Section 2(f).

(c) Sensitive material. Clients should close sensitive documents and accounts before sharing a screen or granting control. See Terms Sections 14 and 23.

(d) Provider policies. Getscreen and Agora process communications data under their terms and privacy policies.

#10. Chat, Photos, Attachments, and Dispute Manifests

(a) Storage. Ticket chat, direct conversation messages, and image attachments are stored in our database and object storage (including a ticket-attachments bucket).

(b) Retention. We do not currently operate an automated chat-purge timer. Messages generally persist until the parent ticket or conversation is deleted or the account is anonymized under Section 14, subject to legal holds.

(c) Disputes. If you open a job dispute, we may compile a complete chat transcript, quotes, payment events, timeline, and device/OS details into a dispute manifest for investigation.

(d) Reports. Safety or abuse reports may attach a recent subset of messages (illustratively, the last twenty).

(e) Camera. Camera and photo-library access is used for issue photos, custody verification, chat images, and optional video during calls you enable—not to populate a Company recording archive.

(f) Automatic chat filtering. In-app chat is automatically filtered. Profanity and off-platform contact or payment details (phone numbers, email addresses, payment apps) are masked. When a message is masked, we keep its original text for staff review, and it may open a case for staff review. Nothing gives a strike automatically; a person reviews every case.

#11. Biometrics, Device Security, and the Profile Photo Check

(a) Local unlock. If you enable biometric login, your device authenticates you using Face ID, Touch ID, or the platform equivalent. Biometric templates remain on the device and are not sent to TechDashers servers.

(b) What we store. We may store a preference that biometric unlock is enabled and hold encrypted session or refresh material in OS-backed secure storage.

(c) Illinois and similar laws. Because we do not collect biometric identifiers as defined under statutes such as the Illinois Biometric Information Privacy Act, those statutes generally do not apply to our server-side processing. If we ever collect biometric identifiers, we will provide a separate written policy and consent first.

(d) Profile photo check. When a Technician chooses a profile photo, the app checks on the device that the photo shows one clear face (using Apple’s Vision framework on iOS or Google ML Kit on Android). This check only detects that a face is present and its size in the photo; it does not identify anyone, does not create a face template, and its result is not sent to us. Only the photo you choose to upload is sent.

#12. Background Checks and Technician Verification

(a) Status, not a public consumer report. We record onboarding, vetting, and background-check status to gate dispatch. Marketing that Technicians are “background-checked” refers to this gate.

(b) Vendor. Screening may be performed by Checkr or another consumer-reporting agency. That vendor may collect SSN, date of birth, and other identifiers directly under its FCRA notices and authorization. We do not store SSN in the TechDashers app schema.

(c) Documents. Identity, insurance, and credential files are stored in restricted storage for compliance review. They are not shown on the public Technician directory. We may confirm a Technician’s coverage with the insurer or agent named on the certificate.

(d) Discretion. We may deny, suspend, or deactivate a Technician based on screening or risk evaluation as described in the ICA and Terms.

#13. Retention; Florida Tax Records; Hardware Order Anonymization

We retain information only as long as needed for the purposes in Section 5, including:

• Account data, while the account is active and for a reasonable period thereafter;
• Tickets, chat, quotes, and payment records, for the life of the service relationship plus the period needed for disputes, accounting, fraud prevention, and tax;
• Florida tax and hardware orders. Hardware-order records are retained for the minimum period required by Florida law for sales-tax audit (generally at least three (3) years, and longer if a period is open or we are advised to retain). Account deletion does not hard-delete hardware-order tax records; we anonymize personal fields where feasible while preserving legally required transactional data;
• Terms-acceptance logs, for the duration of the legal relationship plus limitation periods;
• Location history, for dispatch, safety, and audit for a period we determine is reasonably necessary;
• Phone verification and text-message records (Section 2(q)), for the life of the account plus the period needed to show consent and to handle disputes and legal claims;
• Dispute manifests, for the limitation period applicable to the dispute; and
• Account standing, staff audit-log, damage-claim, and chat-filter records (Section 2(p)), for the life of the account plus the period needed for disputes and legal claims. Strikes stop counting after six (6) months, but the record is kept.

When information is no longer required, we delete or de-identify it, except for backup copies that rotate out in the ordinary course.

#14. Account Deletion and the 14-Day Safety Window

(a) Self-service. You may request deletion in the app (account settings). We log you out and set the account to a deletion-requested status.

(b) Fourteen-day window. There is a fourteen (14) day safety window during which the account cannot be used to log in. We may use this period to complete open tickets, payments, and fraud review.

(c) After the window. Personal profile fields are deleted or anonymized. Active service history is anonymized rather than displayed as your identity. Hardware-order tax records are handled under Section 13.

(d) No self-serve data export. The app does not currently offer a one-tap download of all personal data. You may request a copy of personal information we hold by emailing support@techdashers.com from your account email. We will respond within a reasonable period, and in any event as required by applicable law.

(e) Residual copies. Encrypted backups, logs, and legal holds may persist for a limited time.

#15. Your Privacy Rights (US / Florida; California notice if applicable)

(a) All Users. You may access and update certain profile fields in-app, request deletion as in Section 14, and request a copy of personal information via the emails in Section 20.

(b) Florida. We comply with applicable Florida law, including the Florida Information Protection Act’s data-security and breach-notice obligations. If Florida or other state consumer-privacy statutes apply to a particular request, we will honor legally required rights to know, delete, or correct, subject to exceptions (including security, tax, and fraud).

(c) California (CCPA/CPRA) notice. We do not have actual knowledge that we sell or share personal information of consumers under 16. If you are a California resident, you may have the right to: know/access; delete; correct; opt out of “sale” or “sharing” as those terms are defined (we do not sell for money; some third-party SDK disclosures may be “sharing” if we later enable cross-context advertising—we do not currently); and non-discrimination. Submit requests to support@techdashers.com. We will verify using your account email and reasonable additional checks. You may use an authorized agent as permitted by law.

(d) Authenticated requests. We will not fulfill requests that we cannot verify, or that would unreasonably risk another User’s privacy or our security.

(e) Do Not Track. Our websites do not currently respond to browser DNT signals.

(f) Text messages and calls. We send account and security texts, such as a verification code you ask for and important account notices. Job alerts by text message and automated call are optional, and you can turn them off in the app at any time (Profile › Urgent alerts). Reply STOP to any of our texts to stop receiving texts, or HELP for help. We do not send marketing texts. Message and data rates may apply. The full terms are in Section 3(g) of the Terms.

#16. Children’s Privacy (no under-18 accounts)

The Platform is not directed to children under 18, and we do not knowingly collect personal information from children. We do not create COPPA-regulated child accounts. If we learn that a minor has created an account, we will terminate it and delete or anonymize associated personal information, subject to legal retention.

#17. Security

We use administrative, technical, and physical safeguards appropriate to the nature of the data, including encryption in transit (TLS), access-controlled storage buckets, row-level security on our database, Stripe-hosted card collection, and device secure storage for session material. No method of transmission or storage is 100% secure. You are responsible for your device, passwords, and for not sharing remote-session invite codes except with your assigned Technician.

Remote-desktop and live-call security also depend on Getscreen, Agora, and your network.

#18. International Users

The Platform is operated from the United States. If you access it from outside the United States, you understand that your information will be processed in the United States, which may have different data-protection rules than your country. We do not currently target the EU/UK public as a marketplace of establishment; if that changes, we will update this Policy and provide required transfer mechanisms.

#19. Changes to this Policy

We may update this Policy from time to time. The “Last Updated” date and version number (currently 1.0) control. Material changes will be noticed by in-app prompt, email, or posting at the Public URL. Continued use after the effective date constitutes acceptance where permitted by law.

#20. Contact Us

For privacy questions, deletion or access requests, or this Policy:

NexGen PC Logic, LLC d/b/a TechDashers
Privacy and support: support@techdashers.com
Technician operations: tech@techdashers.com
Website: https://techdashers.com

Principal operations: Orange County, Florida.

Mailing address for privacy notices: request the then-current registered-agent or mailing address from support@techdashers.com with subject “Privacy Notice Address,” or use the Company’s registered agent as on file with the Florida Division of Corporations.

To report a suspected data incident, email support@techdashers.com with “Security Incident” in the subject line.

© 2026 NexGen PC Logic, LLC. All rights reserved. TechDashers is a d/b/a of NexGen PC Logic, LLC. This document is provided for operational deployment after licensed Florida counsel review.