WorkLatchSign in

WorkLatch Privacy Policy

Effective Date: August 31, 2026

Last Updated: August 31, 2026

WorkLatch, a Maryland sole proprietorship (“WorkLatch,” “we,” “us,” or “our”), provides software and telecommunications-enabled tools that help participating service businesses manage certain missed-call, customer-care, intake, and job-request workflows.

This Privacy Policy explains how WorkLatch collects, uses, processes, discloses, and retains personal information when you use or interact with WorkLatch.

1. WorkLatch’s Role

When a Business Customer uses WorkLatch to collect information from its callers or prospective customers, WorkLatch generally processes that job-request information to provide the WorkLatch Service for that Business Customer.

Business Customers determine why they need information concerning their customers’ service requests and remain responsible for their own use of that information.

WorkLatch may separately process certain information for its own legitimate purposes, including:

  • operating and securing WorkLatch;
  • fraud and abuse prevention;
  • Call Defense;
  • telecommunications and messaging compliance;
  • maintaining consent and opt-out evidence;
  • billing and account administration;
  • troubleshooting and service reliability;
  • enforcing agreements and policies;
  • resolving disputes;
  • complying with law; and
  • protecting WorkLatch, Business Customers, Callers, service providers, and others.

WorkLatch is not necessarily acting in the same legal privacy role for every category of information or processing activity.

2. Business Customer and Authorized User Information

WorkLatch may collect or process:

  • profile or display name;
  • email address;
  • account identifiers and status;
  • authentication and session information;
  • business name;
  • configured ZIP/postal service areas;
  • selected industry or custom industry name;
  • service offerings;
  • business configuration;
  • custom questions or intake configuration;
  • membership role such as OWNER, ADMIN, or MEMBER;
  • membership status; and
  • account authorization information.

WorkLatch does not currently collect an account-user telephone number through its standard signup/onboarding flow.

WorkLatch does not currently maintain a standard first-party Business Customer address or website field in its application database.

3. Billing Information

WorkLatch may retain:

  • Stripe customer identifiers;
  • Stripe subscription identifiers;
  • Stripe price identifiers;
  • subscription status;
  • billing-period information;
  • cancellation or grace-state information;
  • invoice identifiers;
  • payment-success or payment-failure timestamps; and
  • related Stripe event metadata.

WorkLatch does not currently receive or store full payment-card numbers, CVVs, or bank-account credentials entered through Stripe-hosted payment interfaces.

Stripe handles sensitive payment credentials through its own payment systems.

4. Call and Telecommunications Information

WorkLatch may process or retain:

  • Caller telephone number;
  • WorkLatch/business-assigned telephone number;
  • Business Customer identifier;
  • call timestamps;
  • call duration where available;
  • provider call identifiers;
  • provider webhook or event identifiers;
  • call status and outcome;
  • Call Defense outcome and reasons;
  • Rescue eligibility or outcome;
  • human-verification state;
  • Press-1 consent state;
  • Rescue session or Activation identifiers;
  • SMS provider identifiers;
  • SMS direction, category, and status;
  • STOP, START, UNSTOP, HELP, or related interactions;
  • business-specific suppression records; and
  • security, rate-limit, velocity, and abuse-prevention information.

5. No Rescue-Call Recording or Transcription

WorkLatch’s current Rescue voice flow does not record Caller audio and does not create a transcript of the Rescue call.

WorkLatch processes telecommunications events, state information, and DTMF/Gather interaction information instead.

If recording or transcription is introduced later, WorkLatch will separately evaluate the applicable product, legal, consent, and privacy requirements before using that functionality.

6. One-Time Rescue SMS Consent

For the current Rescue flow, an eligible Caller must complete the applicable verification and consent step before WorkLatch sends the automatic Rescue Link SMS.

A valid Press-1 interaction is intended to provide consent to receive one Rescue Link SMS associated with that specific call and specific Business Customer.

That consent is not intended to enroll the Caller in recurring WorkLatch messaging, a general WorkLatch consumer list, promotional or marketing messaging, unrelated offers, or messages from unrelated WorkLatch Business Customers.

7. SMS and Mobile Information — No Marketing Sale or Sharing

WorkLatch does not sell or share mobile information, telephone numbers, SMS opt-in information, or SMS consent information with third parties for those third parties’ promotional or marketing purposes.

WorkLatch may permit necessary service providers to process telephone numbers, consent status, opt-out status, and related information where necessary to provide, route, secure, maintain, or administer the WorkLatch messaging service.

Such providers may include telecommunications platforms, carriers, hosting and infrastructure providers, and other vendors necessary to operate the messaging interaction.

Operational processing by these providers is different from selling or sharing mobile information for unrelated promotional or marketing purposes.

8. Rescue Intake Information

Depending on the Business Customer’s configuration and the Caller’s choices, Rescue intake information may include:

  • requested service;
  • job or problem description;
  • answers to intake questions;
  • urgency;
  • timing or scheduling information;
  • ZIP code;
  • street address;
  • city;
  • state;
  • additional service-location details;
  • preferred contact information;
  • photos;
  • videos; and
  • other information deliberately submitted concerning the service request.

9. Location Information

WorkLatch’s current V1 Rescue intake may collect typed service-location information.

WorkLatch does not currently request browser/device GPS or device-based precise geolocation through the V1 Rescue intake.

WorkLatch does not currently perform geocoding as part of the V1 Rescue intake.

10. Job Packets and Access

A completed Rescue intake may become a job packet associated with the specific Business Customer the Caller contacted.

Authorized active members of that Business Customer’s account may access its job packets.

A job packet belonging to one Business Customer is not made available through WorkLatch to an unrelated Business Customer.

Caller-uploaded photos and videos are intended to be private rather than public social content.

Authorized WorkLatch personnel may access information where reasonably necessary for service operation, support, troubleshooting, security, fraud or abuse investigation, legal or regulatory compliance, or protection of WorkLatch and others.

11. Technical and Security Information

The public Rescue intake may use a request IP address transiently for abuse prevention and rate limiting.

WorkLatch’s current public-intake design does not persist the Caller’s raw IP address in the intake database for that purpose.

Instead, WorkLatch may derive and retain a pseudonymized HMAC-based identifier for security or rate-limit enforcement.

Vercel, Supabase, or other infrastructure providers may still process ordinary network information such as IP addresses, request headers, or browser information as technically necessary to transmit, host, secure, or log internet requests.

12. Rescue Tokens

WorkLatch does not intentionally persist the plaintext Rescue bearer token in its application database.

WorkLatch may retain token digests or cryptographic representations necessary to validate or manage Rescue access.

The current Rescue Link design places the secret token in the browser fragment rather than the ordinary URL path or query string.

13. Intake and Upload Metadata

WorkLatch may process:

  • intake or session identifiers;
  • timestamps;
  • upload filename or display metadata;
  • MIME/content type;
  • file size;
  • private storage object identifiers;
  • upload or validation state;
  • security and rate-limit state; and
  • operational or error information necessary to maintain the Service.

WorkLatch does not currently maintain a dedicated persistent device-fingerprint profile for Rescue users.

14. Cookies and Similar Technologies

WorkLatch currently uses technically necessary cookies or similar browser storage for authenticated Service functionality.

For example, Supabase authentication uses session information to maintain and refresh authenticated access.

WorkLatch does not claim that its website uses no cookies.

WorkLatch has not currently identified implementation of Google Analytics, Meta Pixel, TikTok Pixel, Microsoft Clarity, PostHog, advertising-retargeting pixels, or similar advertising trackers.

The public Rescue intake at /r/* is currently designed without analytics or session replay.

Infrastructure providers may still generate ordinary hosting, performance, operational, network, or security logs.

15. How We Use Personal Information

WorkLatch may use personal information to:

  • create and administer accounts;
  • authenticate users;
  • maintain Business Customer configuration;
  • operate telecommunications;
  • determine Rescue eligibility;
  • perform verification and consent flows;
  • send authorized Rescue communications;
  • create Rescue sessions;
  • provide secure intake forms;
  • create job packets;
  • store and deliver uploaded media;
  • administer subscriptions;
  • maintain billing state;
  • operate Call Defense;
  • detect abuse or duplicates;
  • apply cooldowns or rate limits;
  • maintain suppression;
  • prevent fraud;
  • secure WorkLatch;
  • maintain consent and opt-out evidence;
  • answer support requests;
  • troubleshoot technical issues;
  • maintain reliability;
  • resolve disputes;
  • enforce agreements and policies; and
  • comply with law.

16. Deterministic and Automated Processing

WorkLatch may use deterministic or automated rules for Call Defense, eligibility checks, duplicate detection, cooldowns, rate limits, abuse prevention, suppression enforcement, usage controls, and other service-protection decisions.

WorkLatch’s current intelligence model relies on deterministic structured information, with structured customer answers serving as the authoritative source for job packets.

WorkLatch does not currently use Caller job packets, photos, videos, SMS content, or Business Customer data to train general-purpose AI or machine-learning models.

17. Service Providers

The current primary production-data providers identified by WorkLatch are:

Telnyx — telecommunications, voice, and SMS.

Stripe — subscription billing and payment processing.

Supabase — database, authentication, and private storage.

Vercel — hosting, application execution, CDN/edge functionality, and operational logs.

WorkLatch may change providers in the future where appropriate.

18. Legal, Security, and Compliance Disclosures

WorkLatch may disclose information where reasonably necessary and legally appropriate to:

  • comply with applicable law;
  • respond to valid legal process;
  • protect legal rights;
  • investigate fraud or security incidents;
  • enforce WorkLatch agreements or policies;
  • address telecommunications abuse;
  • protect Business Customers, Callers, service providers, or others;
  • cooperate with regulators or courts; or
  • cooperate with law enforcement where legally required or otherwise legally appropriate.

19. No Sale, Targeted Advertising, or General-Purpose AI Training

Under WorkLatch’s current business model:

  • WorkLatch does not sell or rent personal information;
  • WorkLatch does not share personal information with third parties for those third parties’ own promotional or marketing purposes;
  • WorkLatch does not use personal information for cross-context or targeted advertising; and
  • WorkLatch does not use Caller job packets, photos, videos, SMS content, or Business Customer data to train general-purpose AI/ML models.

20. Data Retention

WorkLatch does not currently apply one universal retention period to all categories of personal information.

WorkLatch retains information for as long as reasonably necessary for the purposes for which it was collected or processed, including:

  • service operation;
  • account and billing administration;
  • telecommunications consent or opt-out evidence;
  • fraud and abuse prevention;
  • security;
  • investigations;
  • dispute resolution;
  • agreement enforcement;
  • legal claims; and
  • legal or regulatory obligations.

Retention periods may vary depending on the data type and purpose.

Cancellation or termination does not necessarily cause immediate deletion.

WorkLatch does not promise indefinite storage or indefinite post-termination access.

21. Security

WorkLatch uses reasonable administrative, technical, and organizational measures intended to protect the Service and information processed through it.

Safeguards may include tenant isolation, authenticated access controls, private media storage, short-lived authorized media access, secure Rescue-token handling, cryptographic token representations, rate limits, abuse-prevention controls, and suppression controls.

No system or transmission method can be guaranteed completely secure.

WorkLatch does not currently claim SOC 2, ISO 27001, HIPAA certification, or another security/privacy certification unless expressly stated otherwise.

22. Uploaded Content

WorkLatch does not currently:

  • sell Caller media;
  • publish Caller media publicly;
  • use Caller media in advertising;
  • use Caller media for unrelated commercial purposes; or
  • use Caller media to train general-purpose AI/ML models.

WorkLatch does not currently claim every uploaded file is antivirus-scanned or certified safe.

23. Privacy Rights and Requests

Depending on applicable law, you may have rights concerning:

  • access;
  • correction;
  • deletion;
  • portability or a copy/export;
  • confirmation of processing;
  • information concerning certain disclosures; or
  • other rights provided by applicable law.

Privacy requests may be submitted through:

Email: support@worklatch.tech

Support: https://www.worklatch.tech/support

WorkLatch may take reasonable steps to verify the requester’s identity or authority.

Privacy rights are not necessarily absolute. WorkLatch may retain information where reasonably necessary or legally permitted for billing/accounting, telecommunications consent or opt-out evidence, security/fraud prevention, legal compliance, disputes, legal claims, agreement enforcement, or other lawful purposes.

Where applicable law provides an appeal right, appeals may be submitted through the same contact method and identified as an appeal.

24. Maryland Privacy Rights

Maryland law may provide qualifying consumers with privacy rights where the Maryland Online Data Privacy Act applies.

This section does not state that every provision of Maryland privacy law applies to every WorkLatch user or processing activity.

WorkLatch will honor applicable rights where required by law.

25. Children’s Privacy

WorkLatch is not directed to children under 13 and does not intentionally target children under 13.

WorkLatch does not currently age-gate all Callers using a Business Customer’s Rescue flow.

If WorkLatch learns that it has collected personal information from a child in circumstances where applicable law requires parental consent, deletion, or another action, WorkLatch will take appropriate steps as required by law.

26. Business Customer Responsibilities

Business Customers remain responsible for their own collection, use, disclosure, storage, and handling of information they receive through WorkLatch.

Business Customers may not use Rescue submissions as unauthorized lead lists, sell or resell Caller information, or automatically enroll a Caller in unrelated marketing merely because the Caller used WorkLatch.

27. Changes to This Privacy Policy

WorkLatch may update this Privacy Policy as the Service, technology, law, providers, or business practices change.

Material changes may receive reasonable notice where required.

Updates apply prospectively according to their stated effective date.

28. Contact WorkLatch

WorkLatch, a Maryland sole proprietorship

Email: support@worklatch.tech

Support: https://www.worklatch.tech/support

A public home or residential address is not listed in this Privacy Policy.

WorkLatch may provide identifying or address information privately to regulators, government agencies, telecommunications providers, payment processors, courts, or other parties where legally required.

Related Policies

Terms of Service:

https://www.worklatch.tech/terms

SMS/Messaging Terms:

https://www.worklatch.tech/sms-terms

Refund & Cancellation Policy:

https://www.worklatch.tech/refund-policy

Acceptable Use Policy:

https://www.worklatch.tech/acceptable-use

Support:

https://www.worklatch.tech/support