Privacy Policy

Last updated: 16 November 2026

Precheckly is operated by Charyx Labs, a sole proprietorship registered in India ("we", "us"). This policy explains what personal data we handle when you use the Precheckly website, web app, API, browser extension, MCP server, n8n node and HighLevel Marketplace app (the "Service"): what we collect, why, who else processes it, how long we keep it and your rights. Questions go to [email protected].

In short

  • The SMS calculator and the extension's counts run on your device. Nothing you type there is sent to us unless you click a button that needs our server.
  • We do not sell personal data or show ads.
  • We count visits with Cloudflare Web Analytics, which sets no cookies. Microsoft Clarity records how visitors use the public pages, except visitors in Europe and browsers that send Global Privacy Control. It never records the dashboard, and it never receives what you type into the free tools.
  • The messages, phone numbers and records our customers put into the Service belong to them. We process them only to run the Service for them.
  • When AI features are on, message text is sent to Anthropic to get the result. Workspace owners can turn AI off.

Who is responsible for your data

  • Our own data. For account, billing, support and website data, we decide how it is used, so we are the controller.
  • Our customers' data. Messages, contact phone numbers, consent and opt-out records and message history that a customer puts into the Service belong to that customer. We process them on the customer's behalf as a processor, under section 9 of the Terms of Service. If you received messages from one of our customers, contact that business about your data. We will help them answer you.

What we collect and why

Your account

  • Your name, email address and password. We store the password only as a salted scrypt hash.
  • If you sign in with Google: Google tells us your name, your email address and that Google has verified it. We never receive your Google password or access to anything else in your Google account. An account first created this way has no password until you set one with "Forgot your password?".
  • Your workspace and team: the workspace name, sub-accounts, the people you invite (their email address), and roles.
  • How you get started: when you signed up and signed in (with a password or Google), which steps of the getting-started guide you saw, finished or skipped, and when we showed you a plan offer and what you chose. We use it to improve the guide and the offers. It holds no message content.
  • How you found us: when you create an account, we keep the website that sent you on that visit (its domain only, such as google.com), the first page you opened, and any campaign tags in the link (utm_source, utm_medium and utm_campaign). If the link came from an ad, we keep which ad network it was, never its click ID. Nothing is stored in your browser for this, and we keep it only if you create an account. After you sign up, we ask once how you found us; answering is optional. We use both to learn which channels bring customers.
  • Sign-in sessions, with the browser type that started each session. API keys are stored only as hashes and shown once; we record when each key was last used.
  • Your plan and billing status. Dodo Payments or HighLevel takes the payment and holds your card details; we receive only the plan, status and their customer reference.
  • AppSumo codes: when you redeem one, we keep a fingerprint of the code (not the code itself), the workspace, who redeemed it and when, so each code works once.
  • Emails you send to our support address.

We use this to provide the Service and support (our contract with you), keep it secure and prevent abuse (our legitimate interests), and keep the records tax and accounting law requires (legal obligation).

Content you put into the Service

We process this for the customer whose workspace it is:

  • Message templates and the messages you check, with merge-field values.
  • Recipient phone numbers, time zones and states sent with checks. In gate decisions and the audit trail, phone numbers are stored as keyed hashes. The full message body is stored only if the workspace turns that setting on, and then only for 30 days.
  • Consent and opt-out records: the phone number or email address, the source, the wording shown, and any evidence you add, such as a form address, IP address or browser type.
  • Replies from connected integrations, checked for opt-out requests.
  • Message history for audits. An uploaded CSV file is processed in memory and not saved. A pull from HighLevel or Twilio reads up to 93 days of messages. Audit reports keep up to 10 example messages for 30 days, then mask them. For a pull, the report also keeps how many texts were delivered, undelivered and failed, which phone system or app sent them, and the provider's error messages with phone numbers, times and request IDs removed. A pull also reads the replies in the same period, to count opt-out requests, texts sent to people after they opted out, and replies such as "who is this" or "wrong number". Only those counts are kept, never the replies or who sent them. A pull from HighLevel adds the location's latest email check to the report, as described below.
  • Delivery of the texts in connected accounts. Once a day we read the outbound texts of each HighLevel location or Twilio account you connect, for the days not yet read, to count how many were delivered, undelivered and failed. We keep those daily counts, the last four digits of the numbers the texts were sent from, and the provider's error messages with phone numbers, times and request IDs removed. The messages themselves are not stored. A workspace owner can turn the daily check off in settings.
  • Delivery of the emails in connected HighLevel locations. The same daily check counts the emails sent on each of the last 14 days and looks up a sample of them to see how many were delivered, opened and failed. To do that it reads those emails, looks up the public DNS records of the domains they were sent from, and checks whether a few of them carry an unsubscribe link and a postal address. We keep only the counts, the sending domains and the results of those checks. No recipient, subject or body is stored.
  • Contacts from a HighLevel sync. When you run a sync, we read the location's contacts: phone number, name, tags, Do Not Disturb status and the date added. Do Not Disturb contacts become opt-out records, and contacts with the tags you name become consent records. The sync also counts how many email addresses HighLevel marks invalid and why it stopped emailing contacts (an unsubscribe, a bounce or a spam complaint); only those counts are kept. The contacts with no consent on record are kept as a list you can download (phone number, name, tags, date added and HighLevel contact ID) for the workspace's audit retention period, 30 days unless you change it, then deleted. On plans with the consent ledger, we also check each location connected with a token that can read contacts once a day, and add its new Do Not Disturb contacts to your opt-out list.
  • Contact lists you check before a send. The uploaded file is processed in memory and not saved; only the counts are recorded.
  • A2P registration details and sample messages, email domains, short links with a click count (we do not record who clicked), alert recipients and Slack webhook addresses.
  • Credentials for the Twilio and HighLevel accounts you connect, stored encrypted.

The free tools

  • The SMS calculator runs in your browser and sends nothing to us.
  • The email checker sends the domain you enter (and any DKIM selectors or sending IP) to our server, which looks up public DNS records. Nothing is stored.
  • The A2P sample checker sends the business name and sample messages you enter to our server for automated checks. Nothing is stored, and no AI is used.
  • On these pages, the tools' inputs and results are masked in your browser, so Microsoft Clarity never receives what you type or what the tools show you. See Website analytics.
  • A shared audit report can be opened by anyone with its link until the customer stops sharing it. The page loads the workspace's logo from the address the customer set.

The browser extension

  • The extension counts characters, encoding, segments and cost on your device. It reads the text of the message box you are typing in only to do that, and it does not collect your browsing history or other page content.
  • Nothing you type leaves your browser unless you click Check wording, Shorten, Make link or Save. Then only that message, link or segment count goes to our API, under your account.
  • If you connect an account, the extension keeps the API address, your API key and your plan status in the browser's extension storage on that device. While connected, it rechecks your plan status (your key, never message text) when you start typing, at most every 10 minutes. Your rate and number type settings sync through your browser account.
  • It runs on app.gohighlevel.com and on the sites you turn on yourself.
  • The use of information received from the Precheckly browser extension will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

The MCP server and n8n node

They pass your requests to our API with your API key, store nothing, and log only errors.

Website and technical data

  • Cookies: one essential cookie, sid, keeps you signed in for up to 30 days. On the public pages, Microsoft Clarity sets analytics cookies of its own, described below. No advertising cookies are set.
  • Third-party scripts: every page loads Cloudflare's Web Analytics script, and the public pages load Microsoft Clarity's. The site loads no third-party fonts.
  • Directory badges: the footer of the public pages shows badges from directories that list Precheckly, such as DailyLaunch. Each badge image loads from that directory's own site when you scroll to it, so the directory receives your IP address and browser details, as any website does. The badges run no scripts and set no cookies of ours.
  • How-to videos: the "How it works" buttons in the dashboard and the tour on the home page play our videos from YouTube, in its privacy-enhanced mode (youtube-nocookie.com). Nothing loads from YouTube until you press one. Once the player opens, Google receives your IP address and browser details, and the player may store its own data in your browser. YouTube says a video watched this way is not used to personalise your YouTube browsing. Google handles this data under the Google Privacy Policy.
  • Browser storage: the web app remembers the workspace you last opened (workspaceId). A service worker caches the public pages so the calculator works offline. It never caches the dashboard, sign-in pages or shared reports.
  • Request logs: our servers and hosting providers log each request's IP address, time, address and browser type for security and troubleshooting, and keep the logs for up to 30 days. Some addresses include what was looked up, such as a contact's phone number or email address.
  • Abuse limits: to rate-limit requests, the server counts requests per IP address in memory only. It never writes these counts to disk.

Website analytics

  • Cloudflare Web Analytics counts page views, the sites visitors come from, countries, browsers and page speed. It sets no cookies and uses no identifier to follow you.
  • Microsoft Clarity records how visitors use the public pages, so we can see what confuses people and fix it. It records clicks, scrolling, mouse movement, the pages viewed, the device and browser, and an approximate location from the IP address. It also notes when someone uses a free tool or follows a link to sign up, without anything they typed. Visitors are never identified to Clarity.

Clarity is limited in these ways:

  • Where it runs: only on the public pages (the home page, pricing, the free tools, the rule changelog and these policies), never in the dashboard, the sign-in pages or shared reports. Following a link from a public page into those pages loads a fresh page without Clarity.
  • What it never receives: the free tools' inputs and results are masked in your browser. Microsoft says masked content is never uploaded. Clarity also masks every form field.
  • Who is never recorded: visitors in the European Economic Area, the UK and Switzerland, and browsers that send Global Privacy Control. For them, the site does not load Clarity.
  • Cookies: Clarity sets _clck, which keeps a pseudonymous Clarity user ID and preferences, and _clsk, which joins page views into one recording. The site tells Clarity that advertising storage is denied, and Microsoft writes its advertising cookies, such as MUID, only when that storage is granted. See Microsoft's list of Clarity cookies and its consent guide.
  • Microsoft's role: Microsoft handles Clarity data as an independent controller, under the Microsoft Privacy Statement.
  • To opt out: turn on Global Privacy Control in your browser and we will not load Clarity, or block clarity.ms with a content blocker.

AI features

When AI features are on (the default for new workspaces), we send content to Anthropic:

  • message templates, with merge fields not filled in, during gate checks and use-case checks;
  • the filled-in message, when you ask for a shorter version;
  • inbound replies (without the phone number) that may be opt-out requests;
  • A2P registration details;
  • email subject lines with the first 2,000 characters of the body.

Anthropic returns the result and processes the content as our service provider. Under its commercial terms, it does not train its models on this content. We cache AI results for up to 30 days so the same text is not sent twice. A workspace owner can turn AI features off in settings.

Who else processes data

We use these providers (our subprocessors) to run the Service:

  • Railway, which hosts the app and the database, in the United States.
  • Cloudflare, for website hosting, DNS, visit statistics without cookies, and forwarding email sent to our addresses, on its global network.
  • Resend, which sends our service emails (a welcome email when you sign up, invitations, password resets, alerts, weekly delivery summaries), in the United States.
  • Anthropic, for AI features, in the United States.

Payment providers and the services you connect handle data under their own terms:

  • Dodo Payments sells our plans as merchant of record. It is responsible for payment data under its own privacy policy.
  • HighLevel bills Marketplace installs, and exchanges data with us for the HighLevel features you connect. With a Private Integration token, we read only what the permissions you gave it allow: message history for audits, and contacts for a sync.
  • Twilio is used only when you connect your Twilio account; we read message history from it for audits.
  • Slack is used only when you send alerts to a Slack webhook.

Microsoft receives website usage data through Clarity on the public pages and handles it as an independent controller (see Website analytics).

Google signs you in when you choose "Continue with Google" (see Your account), and plays our how-to videos through YouTube when you open one (see Website and technical data).

We may also disclose data when the law requires it, to protect the rights and safety of people or the Service, or to whoever takes over the Service, who must keep to this policy. We will update this list before we add a subprocessor.

International transfers

We operate from India, and our providers process data in the United States and other countries. When personal data from the European Economic Area, the UK or Switzerland goes to a country without an adequacy decision, we use the European Commission's Standard Contractual Clauses (with the UK Addendum for UK data), or the provider's certification under the EU-US Data Privacy Framework and its UK and Swiss extensions.

How long we keep data

These are the defaults. Workspace owners can change the audit trail periods in settings.

  • Account and workspace: while the account is open. To close an account, email [email protected] from the owner's address. We delete the workspace and its content within 30 days, except records the law requires us to keep, such as tax records. Copies in backups are deleted as the backups expire, within 30 days.
  • Sign-in sessions: 30 days. Password reset links: 1 hour.
  • Gate decisions: 395 days. A stored message body, if that setting is on, is kept for 30 days.
  • Audit trail: 395 days. Consent and opt-out events are kept for 5 years.
  • Audit reports: example messages are masked after 30 days.
  • Lists of contacts without consent, from a HighLevel sync: 30 days, the same setting as audit reports.
  • Daily delivery counts: 395 days.
  • Opt-out reviews: the reply text is cleared 30 days after a decision.
  • Cached AI results: 30 days.
  • Consent and opt-out records: while the workspace exists, because they are the customer's evidence of consent and opt-outs.
  • Templates, A2P checks, email domains, links and alerts: until you delete them, or the workspace is closed.
  • Request logs: up to 30 days. Support emails: as long as needed to handle the request, and no more than 2 years.
  • Microsoft Clarity recordings: Microsoft keeps them for 30 days. It keeps a sample, and any we mark as favourites, for up to 9 months. Heatmaps are available for up to 9 months.

Security

  • All traffic uses HTTPS, and the session cookie is HttpOnly and Secure.
  • Passwords are stored as scrypt hashes, and API keys and sign-in tokens as hashes.
  • Integration credentials and Slack webhooks are encrypted.
  • Phone numbers in gate decisions and the audit trail are stored as keyed hashes.
  • Only the operator has access to the production systems.

No system is perfectly secure. If we learn of a breach that affects your data, we will tell affected customers without undue delay and notify regulators where the law requires it. Please report security problems to [email protected].

Your rights

Depending on where you live, you can ask to access, correct or delete your personal data, to get a copy of it, or to restrict or object to how we use it. Where we rely on your consent, you can withdraw it.

  • EEA, UK and Switzerland: these rights come from the GDPR, the UK GDPR and Swiss law. You can also complain to your data protection authority.
  • California and other US states: you can ask what we hold and ask us to delete or correct it. We do not sell personal data or share it for cross-context behavioural advertising. The site tells Clarity that advertising storage is denied, and turning on Global Privacy Control stops the site from loading Clarity at all. We will not treat you differently for using your rights.
  • Canada: you can ask to access and correct your data, and complain to the Office of the Privacy Commissioner.
  • India: under the Digital Personal Data Protection Act you can ask to access, correct and erase your data, nominate someone to act for you, and raise a grievance. Send grievances to [email protected].

To make a request, email [email protected] from the address on your account. We may need to confirm your identity, and we aim to answer within 30 days. If your data sits in one of our customers' workspaces, we will pass your request to that customer and help them answer it.

Children

The Service is for businesses and people aged 18 or over. We do not knowingly collect data about children.

Changes to this policy

When we change this policy, we post the new version here with a new date. For material changes, we also email account owners.

Contact

Charyx Labs, India. Email: [email protected].