ClientPing Privacy Policy
Effective date: October 5, 2026
This policy explains what personal information Foxsoft LLC, doing business as ClientPing ("Company," "we," "us" or "our"), collects, where it comes from, how we use it, who receives it, and the choices you have. "ClientPing" is the name of our product. The "Service" means the ClientPing website, software, applications, integrations and related services.
1. Who we are
Foxsoft LLC, doing business as ClientPing 515 West 41st Street #1169 Sioux Falls, SD 57105 United States
Email: support@clientping.com Privacy line (voicemail): (833) 429-4744
ClientPing is a service for law firms in the United States. A firm connects its Google, Microsoft (Outlook, Office 365, Hotmail) or Clio account. ClientPing then reads the firm's appointments, sends the firm's clients reminders and other messages by text and email, processes their text-message replies, and updates the firm's calendar.
2. Our two roles
For most information in this policy, we decide why and how it's used. That covers people who create or use a ClientPing account, visitors to clientping.com, people who contact us, and the law firms and lawyers we contact about ClientPing.
"Client Data" means information that a firm or a person acting on its behalf submits to the Service, that the Service receives from the firm's connected calendar or practice-management accounts, or that a person provides through the firm's booking pages or messages, including appointment details, contact information, booking descriptions, message content, delivery information and messaging-consent records. Client Data excludes information we process for our own account administration, billing, website analytics and marketing purposes, as described in this policy.
For Client Data, we act as the firm's service provider (sometimes called a processor). We process Client Data to provide, secure and support the Service for that firm, following the firm's settings and our Terms of Service. The firm decides who gets messages and what they say.
If you're a client of a law firm that uses ClientPing, please send privacy questions and requests to the firm. If you contact us instead, we'll help identify the right firm and assist as required by applicable law and our agreement with the firm. You can reply STOP to stop texts and use the unsubscribe controls for the types of email described in section 10.
3. Information we collect
Account holders
When a firm signs up and uses ClientPing, we collect:
- name, email address, business name, phone number and time zone;
- a password, which we store only as a one-way hash;
- an encrypted two-factor authentication secret and encrypted recovery codes, if you turn on two-factor sign-in;
- an optional profile photo and booking-page logos you upload;
- your settings: reminder rules and message templates, booking pages and availability, notification email addresses, and the phone number you want calls forwarded to;
- billing details: your plan, trial and subscription dates, your Stripe customer ID, and your card's brand and last four digits. Stripe collects the full card number directly; it never reaches our servers;
- a record of each free trial, with the account's email address, Stripe customer and subscription IDs and the trial dates, so each firm gets only one trial;
- the ClientPing phone number we provide for your firm and its carrier registration status;
- support messages you send us, including through the in-app help form;
- how you found us: when you register, we save the Google Analytics client ID from your browser, plus the first page you landed on, the referring website and any campaign (UTM) tags from a first-party cookie (see section 9). A separate session cookie,
cp, can hold a campaign code from a home-page link; we include that code in internal registration alerts; - session records including IP addresses and browser information, password-reset records, and records of staff use of our account-impersonation tool.
If you contact us through our privacy request line, we collect the voicemail you leave, recording and call identifiers, the length of the message and when it arrived. Vonage, which runs the line, receives your caller ID with the call and shows it to us in its call logs; we don't store it in our database. Vonage records and stores the voicemail itself (section 6).
Client Data we process for firms
Depending on which features a firm turns on, ClientPing processes:
- appointments from the calendars the firm activates: title, description, start and end time, location, and the attendee names, email addresses and phone numbers in the appointment. ClientPing looks for phone numbers and email addresses in the appointment text. For a booking page, ClientPing also checks busy times on the linked calendar;
- from Clio: calendar entries, the matter client's primary phone number, and Clio contacts if contact sync is on;
- contacts the firm syncs from Google, Microsoft or Clio, imports from a CSV file or enters by hand: names, job titles, company names, phone numbers and email addresses;
- details people enter on a firm's public booking page: name, phone number, optional email address, a required free-text description, their selected appointment and the time zone used for the booking. We store booking details and send them to the firm's connected calendar provider;
- messages: the text and email messages ClientPing sends for the firm, the replies clients send back, delivery status, the phone numbers and times involved, and messages firm staff send from the ClientPing inbox;
- consent records: when someone texts STOP or START, we keep the keyword, the time and the numbers involved, plus any contacts the firm blocks and any email addresses that have unsubscribed.
If a firm enables call forwarding, Vonage connects calls to the forwarding number selected by the firm. Otherwise callers are told to send a text. We do not record those calls to firms' ClientPing numbers. Our separate toll-free privacy request line records the voicemail you choose to leave, and Vonage's record of the call includes your caller ID and call times, so we can receive and respond to your request.
Website visitors
When you visit clientping.com, we and Google collect:
- through Google Analytics 4 on our public pages: pages viewed, clicks on sign-up and pricing links, the referring website's origin, device and browser information, approximate location and similar usage data. The page URLs we report can include filtered campaign parameters and advertising click identifiers such as gclid and fbclid. We filter other query parameters and use rules intended to reduce the inclusion of personal information;
- a first-touch cookie that records your landing page, referring site and campaign tags;
- on the registration page, information Google reCAPTCHA collects about your browser and device. We also send Google the challenge-response token and your IP address to verify the challenge. reCAPTCHA is covered by the Google Privacy Policy and Terms of Service;
- server and application logs that include IP addresses, pages requested, times and browser type.
When you register or subscribe, we look up the country of your IP address in a DB-IP database stored on our own server, so your IP address isn't sent to DB-IP. We may keep IP addresses that are linked to repeated or blocked sign-up attempts. Sign-up country checks use IP Geolocation by DB-IP, licensed under CC BY 4.0.
Law firms and lawyers we contact
We may email law firms about ClientPing. For that, we collect business contact information about firms and the lawyers and staff who work there, such as name, firm name, role, business email address, business phone number, office address and website. It comes from public business listings and directories (gathered for us by a data-collection service), firm websites, services that find and verify business email addresses, and our own earlier records. We keep a record of the emails we send, the replies we receive and the people who ask us to stop.
We use this information to contact firms about ClientPing. Before every send, we check the address against our suppression and opt-out lists. To stop these emails, reply asking us to stop, use the unsubscribe link in the email, or write to support@clientping.com. An opt-out applies to every product of Foxsoft LLC, not only ClientPing, and we keep opted-out addresses on a suppression list so we don't email them again.
4. Connected Google, Microsoft and Clio accounts
When a firm connects a calendar, it signs in with the provider and grants ClientPing access. We store encrypted access and refresh tokens, together with the provider account identifier and connection details needed to maintain the connection.
| Provider | Access we request | What ClientPing does with it |
|---|---|---|
| View and edit calendars and events; your Google account email address; read-only access to contacts | Reads appointments in the calendars you activate; writes status words such as "REMINDED:", "CONFIRMED" or "DECLINED" to event titles and a status note to event descriptions; creates events for bookings and moves events for reschedules; reads contacts if you turn on contact sync | |
| Microsoft | Sign-in and basic profile; read and write calendars; read contacts; ongoing access while you're away | The same as Google |
| Clio | Calendars and calendar entries; matters (the client's primary phone number); contacts; your Clio user name | The same as Google, plus finding the matter client's phone number for an appointment |
Calendar updates depend on your enabled features and settings. Provider capabilities differ; for example, booking an appointment does not add an email attendee through the Clio integration. Disabling reminders for a calendar does not disable a separate active booking page or its calendar-availability checks.
ClientPing's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In plain terms, for data from Google, Microsoft and Clio alike:
- We use it only to provide and improve the ClientPing features you see and turn on: reminders, reply handling, calendar updates, booking, rescheduling and contact sync.
- We transfer this data only as necessary to provide or improve the user-facing features you use and with your consent (for example, a client's phone number and the reminder text go to Vonage so the text can be delivered), as necessary for security purposes such as investigating abuse, or to comply with applicable law. We may also transfer it as part of a merger, acquisition or sale of our business, but only after obtaining your explicit prior consent to that transfer.
- We don't use it for advertising, we don't sell it, and we don't give it to data brokers or information resellers.
- We don't use it to decide anyone's creditworthiness or for lending.
- We don't use it to develop, improve or train generalized artificial intelligence or machine learning models.
- We do not allow people to read this data unless you affirmatively agree to our viewing specific data, access is necessary for security purposes such as investigating abuse, access is necessary to comply with applicable law, or the data is aggregated and used for internal operations in accordance with the Google API Services User Data Policy's Limited Use requirements. For the last exception, the data must be anonymized and aggregated, must not permit identification of an individual user, and our use must comply with applicable privacy and other legal requirements.
You can cut off ClientPing's access at any time in your Google Account permissions, your Microsoft account's app permissions page, or Clio's connected-apps settings. Revocation prevents further provider access once the provider makes it effective. It does not itself delete data already held by ClientPing or recall messages already queued or sent. To stop reminders as well, disable the calendar's reminders in ClientPing and contact support if needed.
Removing a calendar inside ClientPing deletes its synced appointments, reminder rules and other records linked to that calendar in our primary database. It does not delete all information about those clients: account-level contacts, consent records, inbox conversation summaries and uploaded logos may remain. It also does not disconnect the provider account or erase events at the provider. Revoke access at the provider to disconnect it, or contact support about removing the connection. Sections 11 and 12 explain retention and deletion.
5. How we use information
We use personal information to:
- provide ClientPing: sync calendars and contacts, send reminders and other messages, process replies, update calendars, run booking pages, show conversations in the inbox, forward calls, and email firms when a client replies or books;
- run billing, free trials and plan limits;
- send verification, password-reset, registration, subscription and other account emails, and a separate scheduled series of onboarding, trial and reactivation emails that you can unsubscribe from;
- answer support requests and keep accounts secure. Authorized staff can view an account as its owner sees it, using a tool that ends each session within 60 minutes and logs it. Staff open a firm's account, or view its calendar or contact data, only with the firm's permission for the specific request, or for security, abuse or legal reasons. Section 4 sets further limits for data received from connected Google, Microsoft and Clio accounts;
- keep ClientPing secure: block spam sign-ups with reCAPTCHA and IP checks, limit ClientPing to US businesses, rate-limit requests and investigate abuse;
- measure website use and selected account milestones, such as a first calendar connection, first reminder and subscription start, and measure whether any Google Ads advertising we run leads to sign-ups and subscriptions (section 8). Server events use our internal numeric user ID and, when available, your Google Analytics client ID; otherwise we generate a client identifier from our numeric user ID. These server events can be sent even if your browser does not accept Analytics cookies. Our event code does not intentionally include names, email addresses or phone numbers;
- alert our team about registrations, subscription changes, support access and operational problems. Depending on the alert, this includes account-holder and staff names and email addresses, account IDs, plan information and the firm's ClientPing phone number;
- contact law firms about ClientPing (section 3);
- comply with the law, enforce our terms and protect our rights.
We don't use Client Data to market ClientPing, and we never contact a firm's clients for our own purposes.
6. Who we share information with
We don't sell personal information. We disclose it only as described here.
Service providers. We use the following companies to provide hosting, communications, payments, analytics and other functions. The information they receive and their roles depend on the function. Some may also process information under their own privacy policies.
- DigitalOcean hosts our servers and database in the United States.
- Amazon Web Services stores our encrypted nightly database backups in the United States.
- Vonage sends and receives text messages, provides firms' phone numbers, forwards calls and handles carrier (10DLC) registration. It receives phone numbers and message content.
- SendGrid (Twilio) delivers our outbound email, including reminder emails to clients and notifications to firms.
- Stripe processes payments. Our billing pages load Stripe's payment form from Stripe, which receives your browser's request information. See the Stripe Privacy Policy.
- Google provides Google Analytics (linked to Google Ads for conversion measurement, as described in section 8), reCAPTCHA and Google Workspace, which we use for our business email and support inbox.
- Telegram carries the internal alerts described in section 5, including alerts when authorized staff use account impersonation.
- jsDelivr delivers some scripts and styles to browsers. Requests to these resources disclose network and browser request information to the content-delivery provider.
- For our outreach to law firms (section 3), a data-collection service gathers public business listings and directories, other services find and verify business email addresses, and an email-outreach service sends our emails and records replies and opt-outs.
- Vonage operates our toll-free privacy request line and records and stores the voicemails callers leave. Vonage deletes each recording 30 days after it's made. We don't download the recordings. We store call identifiers, message length and arrival time, but not your caller ID, and send a notification with those details through SendGrid to our Google Workspace support inbox, so we can listen to the voicemail in Vonage and handle the request.
Mobile carriers. Carriers receive the phone numbers and content of the texts they deliver.
The law firm. The firm controls its Client Data and can see it in its account.
Calendar and practice-management providers. When a firm connects Google, Microsoft or Clio, we send booking and status updates back to that account.
Legal and safety reasons. We may disclose information if the law requires it, to respond to valid legal process, or to protect the rights, property or safety of the Company, our customers or others.
Business transfers. Information may transfer as part of a merger, acquisition or sale of our business, subject to this policy. Data received from connected Google, Microsoft and Clio accounts may transfer in such a transaction only after we obtain your explicit prior consent, as explained in section 4. The recipient must handle the information consistently with this policy. Section 4's restrictions also apply to the other disclosures described in this section.
With consent. We share information in other ways only with your permission.
The additional restrictions on mobile information and text-messaging consent data in section 7 apply to all sharing described in this section.
7. Text messages (SMS)
Firms use ClientPing to text their own clients from a dedicated phone number. The firm is responsible for getting each client's consent before ClientPing texts them.
No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text-messaging opt-in data and consent are used only to operate the messaging program, honor messaging choices and meet legal requirements. We disclose this information only to the firm responsible for the program, service providers that help operate and support it, and recipients to whom disclosure is required by law; we do not disclose it for any other party's marketing or promotional use.
If you get texts from a firm through ClientPing:
- Reply STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT, OPTOUT or REVOKE to stop texts from that firm's ClientPing account. The opt-out applies across numbers in that account, but not to other firms' accounts. We attempt one confirmation when your opt-out status changes; delivery is subject to carrier availability.
- Reply START, UNSTOP or SUBSCRIBE to opt back in for that account. This does not override a separate block placed by the firm.
- Reply HELP or INFO for help, or email support@clientping.com. You may still receive a help reply that you request after opting out.
- Message frequency varies. Message and data rates may apply.
We keep records of opt-outs and opt-ins so we can honor them and show that we did.
8. No sale and no targeted advertising
We don't sell personal information, and we don't share it for cross-context behavioral advertising (targeted ads based on activity across other companies' sites).
We use Google Analytics to measure website use and selected account milestones. Our Google Analytics property is linked to Google Ads so we can measure whether any advertising we run leads to sign-ups and account activity. In our Analytics settings, Google signals is off, ads personalization is off for the Google Ads link, and sharing Analytics data with other Google products and services is off. Our Analytics page tag also tells Google not to use the data for Google signals or ad personalization. You can use Google's Analytics opt-out browser add-on to limit browser-based Analytics collection. It does not control account-milestone events sent directly from our servers.
Because we don't sell personal information or share it for cross-context behavioral advertising, we do not currently use Global Privacy Control signals to change those practices. We do not respond to browser Do Not Track signals.
9. Cookies
ClientPing uses a small number of cookies:
| Cookie | Purpose | How long it lasts |
|---|---|---|
| Sign-in session | Keeps you signed in. Required. | Browser cookie lasts up to 2 hours from when it is set, or 30 days with Remember me. Server sessions also expire after the corresponding period of inactivity, and our daily cleanup deletes expired session records. |
| Calendar-connection check | Protects the Google, Microsoft or Clio connection step from forgery. Required. | Up to 10 minutes; normally removed when the callback is handled. |
cp_ft (first touch) |
Remembers how you first reached our site (landing page, referring site, campaign tags) so we can credit it if you sign up. | 90 days |
cp |
Remembers a campaign code supplied in a home-page link and includes it in internal registration alerts. | Session cookie, subject to the browser's session-restoration behavior. |
_ga, _ga_* (Google Analytics) |
Measures visits to public pages. Our Analytics tag is not loaded inside the signed-in app. Existing cookies may still accompany requests to our site. | Set and refreshed by Google Analytics according to its configuration. |
| Google reCAPTCHA | Tells people from bots on the registration page. | Set by Google |
You can block or delete cookies in your browser settings. If you block the sign-in cookie, you won't be able to use the app.
10. Your choices about email and texts
Account emails. Our scheduled onboarding, trial and reactivation email series includes an unsubscribe link that stops that series for your account. This control does not stop separate registration and subscription welcome emails, password resets, billing notices or account alerts.
Our outreach to law firms. Follow the opt-out instructions in the email or write to support@clientping.com.
Reminder emails from a firm. Rule-generated client emails, including reminders and review requests, include an unsubscribe link. Confirming that unsubscribe stops those emails to that address across all firms using ClientPing. It does not stop account, security, support or firm-notification emails, and account-holder onboarding emails have a separate unsubscribe control. If an unsubscribe link no longer works, contact support@clientping.com.
Texts from a firm. Reply STOP. See section 7.
11. How long we keep information
- Account information, settings, Client Data and message history are kept while the account exists. ClientPing doesn't automatically delete older appointments or messages from an active account.
- Removing a calendar deletes the records described in section 4; it does not erase every related client record or copy.
- Text-message consent events and opt-out status are kept while the account exists. When the account is deleted, we keep a minimized copy of each client's opt-out status record for 4 years from the deletion, including the recorded opt-out keyword and dates and any subsequent opt-in date. We do not retain the complete history of STOP and START messages after deletion. Email unsubscribes are kept as long as we send email.
- Billing records are kept while the account exists. After deletion, a subscription record is kept until both its last update (or its creation, if it was never updated) and any end date are more than 7 years old. A settled record of a subscription we started or cancelled during the deletion is kept until both its last update and any resolution date are more than 7 years old. Unresolved billing records are kept until they're resolved.
- We keep staff-access logs for 2 years from when the access was logged, including while an account remains open. Phone-number purchase and release records and our records of analytics events already reported are kept while the account exists; after deletion, each is kept until 2 years from the date the record was created, subject to the unresolved-record exceptions in section 12.
- Sign-in session records are deleted by our daily cleanup once the session has expired: 2 hours after the last activity, or 30 days with Remember me.
- Web-server logs, which record IP addresses, the pages requested and times, are rotated daily and kept for 14 days. Application logs in our server's system journal are kept for 90 days.
- Our records of privacy-line voicemails (recording and call identifiers, message length and arrival time) are deleted 2 years after the voicemail arrived. Vonage deletes the recording itself 30 days after it's made (section 6).
- Records of repeated or blocked sign-up attempts, including IP addresses, are deleted 2 years after they were last updated. An IP address on our active block list is kept while the block is in force.
- Support email, including the voicemail notifications in our support inbox, is deleted 2 years after the last message in the thread. We clear the support inbox by hand once a month, so a thread can stay up to about a month past that date.
- Under our Analytics data-retention settings, Google keeps event-level Google Analytics data for 2 months and user-level data for 14 months. These settings don't affect aggregated reports.
- Our nightly database backups are encrypted before upload and stored with Amazon Web Services in the United States (Ohio region). We configure S3 lifecycle rules to expire these uploaded backups after 90 days. On our server, each successful backup run keeps only the three newest compressed database dumps and deletes older ones. These local dumps can be read only by the server's administrator account, but they aren't separately encrypted. A failed run can leave an extra or incomplete copy on the server. We're alerted when a run fails, we remove leftover copies when we fix the failure, and we check for them once a month. Backups can contain information removed from the live database. If we ever restore a backup, reminders and other messages stay off (the service is in maintenance) until the account deletions, text-message opt-outs and email unsubscribes made since that backup was taken are re-applied, from the live database where it survives, otherwise from our text provider's message records and our support records. During that time we still receive texts and apply opt-outs as they arrive, and the only texts we send are the automatic replies to a text someone has just sent us, such as an opt-out confirmation; the firm still gets its usual email about each text it receives. If the database itself is lost, email unsubscribes made after the most recent nightly backup may not be recoverable, so a person may need to unsubscribe again. We honor every repeat request.
- Contact information about law firms and lawyers we contact (section 3) is kept until you opt out or we stop contacting your firm. We keep a suppression record of opted-out email addresses so we don't contact you again.
- After an account is deleted, the records described in section 12 are kept for the periods stated there and then deleted.
12. Deleting an account and its data
Account deletion is handled by our support team; there's no delete button in the app. Cancelling a subscription doesn't delete your account or its data.
To request deletion, email support@clientping.com or leave a voicemail on our privacy line at (833) 429-4744. We'll confirm the request by sending a one-time code to the email address on the account, and we'll go ahead once you reply with that code from that address. A code is good for 7 days. We'll never ask for your password, card details or identity documents. If you can no longer receive email at the account address, we won't delete the account until we can confirm the request another way.
When we delete an account, we:
- sign out every session, block sign-in and stop all sending from the account;
- cancel any live subscription immediately. Cancelling doesn't by itself refund unused time or cancel amounts already owed;
- release the account's ClientPing phone numbers to our phone provider, after which a carrier may reassign them. If a number can't be released right away, for example during a provider outage or a transfer dispute, we delete the account and release the number later;
- remove the account's queued text messages;
- delete the account's settings, calendar connections and stored calendar tokens, appointments, reminder rules, booking pages, contacts, text messages and conversations, uploaded images, API tokens, sessions and email preferences from our database and file storage.
If a payment-provider or phone-provider problem interrupts the process, the account stays locked and nothing is sent from it until we finish. We reply in the same email thread when deletion is complete.
Deleting our calendar tokens doesn't revoke ClientPing's authorization at Google, Microsoft or Clio. You can remove it in your account settings with each provider.
What we keep after deletion
We retain the records below after account deletion. Each period runs from the date or dates the table states (for billing records, that includes the record's last update), so a record already older than its period when the account is deleted is removed at the next daily cleanup. Our daily cleanup removes eligible database records after those periods end; a processing backlog can delay removal. Unresolved billing obligations and records of numbers that may still be rented are kept until resolved and their applicable retention period has ended. Provider-held records, support correspondence and backups follow the separate retention schedules described here.
| Record | What it contains | Why we keep it | How long |
|---|---|---|---|
| Billing history | Our records: plan, subscription status and dates, and Stripe customer, subscription and price IDs, including records of any subscription started during the deletion and then cancelled, with the last Stripe error. Amounts, invoices and payment details (name, email address, card brand and last four digits) are held by Stripe as our payment processor, under its own policies. | Tax and accounting | Subscriptions: until both the last update (or creation) and any end date are more than 7 years old. Other settled billing records: until both the last update and any resolution are more than 7 years old. Unresolved records: until resolved |
| Deletion record | Internal account IDs, our support ticket reference, the staff member who ran the deletion, counts of what was removed, the Stripe subscription IDs we cancelled, internal IDs of the phone-number records released and any note on a step that was skipped or stopped. Email addresses and phone numbers are removed from it | Proof that we deleted the account at your request | 7 years from the deletion |
| Text-message opt-out records | For each client with an opt-out status record when the account is deleted: their phone number, the ClientPing number recorded for the opt-out, the recorded opt-out keyword and date, and any subsequent opt-in date. This is a minimized status record, not the complete consent-event history; START-only events without an opt-out record are not archived. | Showing that opt-outs were honored | 4 years from the deletion |
| Email unsubscribes | Email addresses that unsubscribed from reminder emails. Our email provider also keeps its own suppression list. | Making sure we don't email those addresses again | As long as we send email |
| Free-trial record | The account's email address, Stripe customer and subscription IDs and the trial dates | Making sure a deleted firm can't take a second free trial | As long as we offer free trials |
| Phone-number records | Numbers bought and released for the account, with status and dates | Making sure no number is left rented | 2 years from when the record was created |
| Staff-access log | Which staff account opened the account and when, with the staff member's IP address and browser | Security audit | 2 years from the logged access |
| Analytics IDs | Internal account ID and the names of milestone events already reported | Stopping the same event from being reported twice | 2 years from the event |
| Support email thread | Your deletion request and our replies | Evidence of the verified request | 2 years from the last message |
Copies held outside our database aren't removed by this process and are kept under the retention settings of the services that hold them: message records at Vonage, Google Analytics data, email-delivery records at SendGrid, our internal alert messages and our support mailbox. Backups are covered in section 11; a backup made before deletion still contains the account until that backup is deleted. If we restore one, we re-apply the deletion before we use the restored data.
Some logos and profile photos that were replaced or detached before this deletion process was introduced can't be matched to an account and may remain in our file storage. If our phone provider delivers a text to a released number after deletion, we may record it without linking it to any account.
If you're a firm's client and want your information deleted, ask the firm. Deleting an inbox conversation removes its inbox entry but does not erase the underlying SMS history. Deleting a contact does not erase appointments, messages or copies at the firm's calendar provider, and contact sync may import the contact again. The firm can contact support about information that cannot be erased through these controls.
13. Security
We protect personal information with measures that include:
- encryption in transit (HTTPS) for our website and app;
- passwords stored only as bcrypt hashes;
- calendar access tokens encrypted at rest with AES-256-GCM;
- optional two-factor sign-in;
- nightly database-backup uploads to Amazon Web Services encrypted with AES-256 before upload and stored with server-side encryption; other backup copies are described in section 11;
- authorized staff can use a time-limited, logged account-impersonation tool;
- links to text conversations that are signed, tied to one conversation and expire after 7 days.
No system is perfectly secure, and we can't guarantee that information will never be accessed without permission. If a breach affects your personal information, we'll notify you and the authorities as the law requires.
14. United States only; children
The Service is available only to businesses in the United States and its territories. We use IP-country checks to restrict registration, but these checks may be unavailable or unable to determine a location. We accept payment cards only when the issuer-country information identifies the United States or an accepted US territory. Our servers and database are in the United States. Some of our service providers, such as Telegram, may process information in other countries.
ClientPing isn't meant for children, and account holders must be at least 18. We don't knowingly collect personal information from children for our own purposes. Information about a firm's clients is Client Data, controlled by the firm.
15. Your privacy rights
Depending on where you live and which laws apply, you may have rights to know about, access, correct or delete personal information, and to exercise those rights without discrimination. To make a request, email support@clientping.com or call our privacy line at (833) 429-4744 and leave a voicemail. Where a state law gives you a right to appeal our decision, reply to our decision to appeal, and we'll explain the process and its deadline.
For Client Data controlled by a firm, send your request to that firm. If you contact us, we'll help identify the firm and assist as our agreement with the firm and applicable law require.
California
This section applies to California residents and adds to the rest of this policy. It covers personal information we handle for our own purposes. It doesn't cover Client Data we process for a firm as its service provider; the firm's own privacy notice covers that.
In the 12 months before the effective date of this policy, we collected the following categories of personal information. Section 5 explains why we use it, and sections 11 and 12 explain how long we keep it.
| Category | Examples | Where it comes from | Disclosed for business purposes to |
|---|---|---|---|
| Identifiers | Name, email address, phone number, office address, IP address, account ID, Google Analytics client ID | You; your browser or device; for law firms we contact, public business listings and directories, firm websites, email-finding and verification services, and our own earlier records | Hosting and backup providers (DigitalOcean, Amazon Web Services), Vonage, SendGrid, Stripe, Google (Analytics, reCAPTCHA, Workspace), Telegram (internal alerts), our outreach data-collection, verification and sending services |
| Customer records | Business name, billing details, card brand and last four digits | You; Stripe | Stripe; hosting and backup providers |
| Commercial information | Plan, free-trial and subscription history | You; Stripe | Stripe; hosting and backup providers; Google Analytics (subscription start); Telegram (internal alerts) |
| Internet or other network activity | Pages viewed, clicks, referring site, campaign tags, ad click IDs, use of the app, server logs | Your browser or device; our servers | Google (Analytics and Google Ads conversion measurement); hosting and backup providers; jsDelivr (request information) |
| Approximate location | Country or city estimated from an IP address | Your IP address | Google Analytics |
| Communications | Support messages and emails you send us; privacy-line voicemails, from October 5, 2026, when we introduced the privacy voicemail line (we collected none before that date); replies to our outreach emails | You | Google Workspace; Vonage (privacy-line recordings and call metadata); SendGrid (in-app support messages and privacy-line voicemail notifications); our outreach email service; hosting and backup providers |
| Professional information | Firm name and role | You; for law firms we contact, the sources listed above | Hosting and backup providers; our outreach data-collection, verification and sending services |
| Sensitive personal information | Account sign-in details (your email address with a password we store only as a hash) and two-factor secrets | You | Hosting and backup providers |
We do not sell personal information or share it for cross-context behavioral advertising. In the 12 months before this policy's effective date, we ran no Google Ads campaigns and our Google Ads account held no audience lists built from visits to our website or app, so we did not sell personal information or share it for cross-context behavioral advertising during that period. Google signals stayed off, and we turned off ads personalization for our Google Ads link on October 5, 2026. We have no actual knowledge of selling or sharing personal information of anyone under 16. If our practices change to include sale or sharing, we will update this policy and provide the required opt-out before doing so.
We use sensitive personal information only to sign you in, keep accounts secure and provide the Service. California law doesn't give a right to limit those uses, so we don't offer one.
If you're a California resident, you have the right to:
- know what personal information we've collected about you, where it came from, why we use it and who we've disclosed it to, and get a copy of the specific pieces;
- ask us to delete personal information we collected from you, subject to the exceptions the law allows, such as the records described in section 12;
- ask us to correct inaccurate personal information. Account holders can correct most account details in the app's settings;
- opt out of the sale or sharing of personal information. We don't sell or share it, as explained above;
- not be discriminated against for using these rights. We won't deny you the Service, charge you a different price or give you a lower level of service because you made a request.
To make a request, email support@clientping.com, or call our toll-free privacy line at (833) 429-4744 and leave a voicemail. Tell us which right you want to use and how to reach you.
We need to verify a request before acting on it. If you have a ClientPing account, we'll send a one-time code to the account's email address and ask you to reply with it from that address. If you don't have an account, for example if we contacted you about ClientPing, we'll send a code to the email address we hold for you, or ask for details that match what we hold. If you leave a voicemail, we'll contact you to verify the request in one of these ways. We'll never ask for your password. We use information you give us for verification only to verify the request. If we can't verify it, we'll tell you why.
Someone you authorize can make a request for you. We'll ask the agent for your signed permission, and we may ask you to verify your identity with us directly or to confirm that you gave the agent permission. This doesn't apply if the agent holds a power of attorney under California Probate Code sections 4000 to 4465.
We'll confirm that we received your request within 10 business days and respond within 45 calendar days of receiving it. If we need more time, we may extend that once by up to 45 more days; we'll tell you within the first 45 days and explain why.
The owner of ClientPing monitors support@clientping.com and the privacy line, including during absences, so these deadlines are met.
16. Changes to this policy
We'll post any change on this page with a new effective date. If a change is material, we'll email account holders before it takes effect. Before we use personal information we already hold in a materially different way, we'll get any consent the law requires.
17. Contact us
Questions about this policy or a privacy request:
support@clientping.com Privacy line (voicemail): (833) 429-4744 Foxsoft LLC, doing business as ClientPing, 515 West 41st Street #1169, Sioux Falls, SD 57105