Clasp

Clasp privacy policy

This privacy notice explains how Clasp handles account, field-service, mobile app, and ChatGPT plugin information.

Updated October 23, 2026

Who is responsible

Clasp provides this service. Your service business controls the customer and work records in its workspace; Clasp processes those records to provide the service. Contact your workspace owner for requests about their records, or use the Clasp support page for operator assistance.

The Android and iPhone app

The mobile app downloads the workspace records your account may access, including customer and lead contact details, service addresses, jobs, visits, conversations, estimates, and invoices. It stores these records and your pending changes in encrypted storage on your phone so you can work offline. Authentication credentials are stored using the device's protected credential storage. Saved changes are sent to Clasp when the app reconnects; message delivery and other online actions remain subject to your workspace permissions and configuration.

Signing out clears the app's saved workspace from that phone; it does not delete your account or the workspace's server records. Synchronize changes you want to keep before signing out. Offline copies can remain on a disconnected device until the app reconnects and processes an access change or the local app data is cleared.

If you enable notifications, the app can schedule local visit reminders and register a push token, a generated installation identifier, your account and workspace identifiers, and the device platform with Clasp. Where remote notifications are configured, delivery uses Expo and the Android or Apple push service. Notification text is generic; open the authenticated app to see the related workspace records. You can turn notifications off in the app or your device settings. Optional biometric checks use the operating system; Clasp does not receive your fingerprint or face data.

This mobile version does not import your phone's contacts, read your personal SMS inbox, collect GPS location, or upload photos and documents. Conversation records belong to your Clasp workspace and are synchronized from its configured messaging service.

Information processed

Clasp processes account and authentication information, workspace membership, customer names and contact details, service addresses, requests, estimates, jobs, visits, files, invoices, payment references, and operational or security records needed by the features you use. Payment-card entry is handled by Stripe components; the plugin does not request card numbers, passwords, or verification codes.

The ChatGPT connection

When you authorize Clasp in ChatGPT, requested tool arguments pass from OpenAI to Clasp and authorized results return to OpenAI for use in your conversation. Results can contain customer contact details, work descriptions, schedule information, amounts, statuses, and record identifiers needed for follow-up actions. Customer creation accepts a US service address; contact updates accept only the supported fields. Clasp does not receive unrelated conversation history through these tools.

Why we use information

We use information to authenticate access, operate your workspace, perform your requested lookups or customer changes, prevent duplicate or conflicting changes, detect misuse, and troubleshoot service problems. Lookup security records include the user, company, connected client, record category, and time; customer changes also generate audit and retry records.

Providers and sharing

Vercel hosts the service and connector, and Supabase provides sign-in and secure data storage. OpenAI processes plugin requests and returned results under the terms and privacy controls applicable to your ChatGPT account. Configured email and payment features use Resend and Stripe respectively. Configured SMS features use Telnyx to process message content, phone numbers, and delivery information. Mobile push delivery, when enabled and configured, uses Expo, Google Firebase Cloud Messaging, and Apple Push Notification service. Clasp may disclose information where required by law or necessary to protect the service and its users.

When a workspace administrator connects Thumbtack, Thumbtack provides Clasp with the authorized businesses, webhook configuration, associate phone-number registrations, OAuth credentials, and new-lead events needed for the connection. Clasp sends Thumbtack the selected business's Clasp webhook address and authentication, phone numbers the administrator chooses to register for lead communications, test requests, and disconnect requests. Disconnecting stops future partner intake but does not delete customer or request records already saved in the Clasp workspace.

Retention

Workspace records remain available while the workspace uses the service, unless an authorized deletion is completed. Security, audit, and change receipts may remain for access control, dispute handling, or legal recordkeeping. Deletion timing depends on the request scope, legal holds, required retained evidence, and the backup rotation in use; disconnecting ChatGPT is not a deletion request. Ask the workspace owner or operator for the retention and deletion schedule applicable to your workspace.

Your choices

You can review and correct permitted records, disconnect the ChatGPT integration, and ask your workspace owner or Clasp operator for access, export, restriction, or deletion. We may need to verify your authority before acting. Previously returned information in ChatGPT is governed by your OpenAI account controls; deleting a Clasp record does not automatically delete a conversation.

To request deletion of your Clasp account and associated personal data, follow the account deletion instructions. This request is separate from signing out, uninstalling the app, or removing a workspace member. Business records controlled by your service company and records subject to legal or security retention may need separate handling; request-specific retention details are provided during review.

Cookies and security

Clasp uses session and authentication mechanisms to maintain sign-in and apply access controls. Only authorized company records are available through the connector. Avoid including unnecessary sensitive information in free-text fields. No security measure guarantees absolute protection.

Optional support chat

When available, website support chat is provided through Crisp. We load that service only after you choose to open chat. Crisp receives the messages and contact information you choose to provide and connection information needed to operate the chat. The Clasp integration does not automatically attach your workspace records, customer information, or private page links. Chat is separate from your Clasp sign-in.

Avoid sending passwords, verification codes, payment details, or private customer links. See Crisp's privacy policy for its handling of chat data. You can email team@clasp.pro instead of opening chat.

Contact

Email team@clasp.pro for Clasp support and privacy requests.

For privacy, account, or security questions, visit the support page. Service customers should first contact the business identified in their workspace or customer portal.