What we hold, and why
Privacy Policy
Last updated November 1, 2026 · Applies to chalkcrm.com and app.chalkcrm.com
Chalk holds the records a service business runs on: its customers, its quotes, its jobs, its money. This page says exactly what we store, who else touches it, how long it stays, and the things we will not do with it. It is written to be checked, not skimmed past.
Are you the customer of a business that uses Chalk? A painter, landscaper or cleaner probably sent you a quote, an invoice or a text through us. That business decides what to collect about you and why. We only hold it for them. Contact them first, and see section 11.
Contents
- Two roles, and which one we are in
- What we collect
- What we never collect
- How we use it
- Who else processes it
- ChalkBot and AI
- Messaging, carriers and consent
- Cookies and tracking
- How long we keep it
- How we protect it
- If you are somebody's customer
- Your rights and choices
- California and other state rights
- People outside the United States
- Children
- Changes to this policy
- How to reach us
1 Two roles, and which one we are in
Chalk handles information in two different capacities, and it matters which:
- For the business that subscribes, we are the controller of its account: who signed up, the email and phone on the account, what was paid, how the software was used. We decide how that is handled and this policy governs it.
- For everything that business puts into Chalk about its own customers, we are a processor, or in California terms a service provider. The business decides what to collect and why; we hold and process it on their instructions, under our User Agreement, and for no purpose of our own.
2 What we collect
| Category | What it includes | Where it comes from |
|---|---|---|
| Account | Business name, address, phone, email, industry, hours, logo and branding, plus each user's name, email, phone, role and permissions. | Entered by the business at signup or in Settings. |
| Credentials | A password hash, PIN hash, two factor codes and device trust records. Never the password or PIN itself. | Created when a user sets one. |
| Business records | Customers and their contacts and property addresses, leads, quotes, line items and measurements, jobs, visits, schedules, invoices, payments, expenses, timesheets, payouts, notes and tags. | Entered or generated by the business as it works. |
| Files | Photos of work and property, receipts, documents, and signatures drawn by a customer approving a quote. | Uploaded by the business, or captured from its customer. |
| Communications | The text messages and emails sent through Chalk and their delivery status, including inbound replies. | Sent and received through the app. |
| ChalkBot | What people ask ChalkBot and what it answers, things it has been told to remember, the photos and voice notes added to a chat with their date and place, and short descriptions of those photos. | Created when someone in the business uses ChalkBot. See section 6. |
| Payment metadata | Stripe customer, account, charge and payout identifiers, amounts, the last four digits and brand of a card, and payment status. | Returned to us by Stripe. Card numbers never reach Chalk. |
| Registration details | Legal entity type, EIN, address and website supplied for carrier messaging registration. | Entered by the business when it registers a text number. |
| Technical | IP address, browser and device type, timestamps, pages and endpoints requested, errors, and an audit trail of who changed what inside an account. | Generated automatically when the software is used. |
3 What we never collect
- Card numbers. Payment details are entered on Stripe's own pages and go straight to Stripe. Chalk stores only Stripe's reference tokens.
- Bank login credentials. Bank details for payouts are held by Stripe under the business's own Stripe account.
- Location. Chalk does not follow crews or devices through the day. When a phone allows it, Chalk asks for its location at three moments: when someone clocks in, when they come back from a break, and when they tap On my way. Chalk keeps only the latest spot for each person and shows it on the calendar map, for 12 hours, to people who can see everyone's calendar. It is not saved with their hours. When a photo is added to a job, a visit or a ChalkBot chat, Chalk keeps the time and place the camera saved in it, or asks the phone for its location at that moment, so the photo can be matched to the work. Addresses are geocoded so they can be shown on a map.
- Advertising profiles. There are no advertising trackers, no data brokers, and no cross site profiling anywhere in Chalk or on this website.
4 How we use it
- To run the software: show a business its own records, send the quotes, invoices, reminders and receipts it asks us to send, take payments through Stripe, and keep the schedule.
- To bill: take subscription payments, apply seats and taxes, and keep the records that go with them.
- To support: answer questions and investigate faults. Staff access to a business's records is limited to what a specific problem requires.
- To keep it safe: detect and prevent abuse, fraud, unauthorised access and messaging violations, and to enforce our agreement.
- To improve it: understand which features are used and where the software fails, using aggregated and de-identified information wherever that will do.
- To comply with law: respond to lawful requests, keep tax and transaction records, and meet carrier and payment network obligations.
We do not sell personal information, and we do not share it for cross context behavioural advertising. We do not use a business's customer records to market to those customers ourselves. We do not train AI models on a business's records, for that business or for anyone else.
5 Who else processes it
Chalk is built on other people's infrastructure, and each of these sees a defined slice of information in order to do its job. This is the full list as of the date at the top of this page.
| Provider | What it does | What it sees |
|---|---|---|
| Cloudflare | Hosting, database, file storage, network security, and cookieless visit counts for this website | Everything stored in Chalk, at rest in its database and object storage, and every request in transit |
| Google Analytics | Aggregated usage counts for this website (www.chalkcrm.com) only | Pages visited, the site that linked there, browser and device type, and a cookie that tells one browser from another. Not used on the app. See section 8. |
| Stripe | Subscription billing and customer card payments | Payer name, email, amounts, card details entered on Stripe's pages, and the business's own identity and bank details |
| Telnyx | The built in text number, and carrier registration | Phone numbers, message contents and delivery status, plus the business details filed for registration |
| The Campaign Registry and mobile carriers | Approving a business to send text messages in the United States | The registration details described in section 2 |
| Resend | Sending email | Recipient address, subject and message content |
| United States Census Bureau geocoder, and Photon (run by Komoot) | Turning a street address into map coordinates, and suggesting addresses as one is typed | The address text only, with no customer name attached |
| OpenStreetMap | Map images behind the schedule map | Which map tiles were needed, which reveals the area being viewed. Our server fetches them, so OpenStreetMap does not see your browser or device |
| OSRM public route server | Estimating drive time between two stops | Two sets of map coordinates, with no name or address attached |
| United States National Weather Service | The weather forecast on the schedule and in ChalkBot's answers | Map coordinates of the business or a job site, with no name attached |
| OpenRouter | Passing ChalkBot's requests to the company that runs the AI model | What ChalkBot sends for a task, described in section 6 |
| AI model hosts reached through OpenRouter | Running the AI model that writes ChalkBot's answers, drafts and photo descriptions | The same as OpenRouter. Who they are, where they are, and what they keep is in section 6 |
| Browser push services (for example Apple, Google or Mozilla) | Delivering notifications to a device that turned them on | A device address and when a notification was sent. The notification itself is encrypted so only the device can read it |
A business can also connect optional services of its own. When it does, Chalk sends them only what that connection is for, and what they do with it is governed by the business's relationship with them:
- Quo: texts sent from the business's own Quo number, with the phone numbers and message contents.
- QuickBooks, by Intuit: customer names, email addresses and phone numbers, invoices, payments and expenses, to keep the business's books in step.
- A webhook address it chooses, such as Zapier: lead updates, including the customer's name, phone number and email address.
- Meta (Facebook), through Meta Conversions: only once the business turns it on, and only for leads that came from the business's own Facebook lead form. Chalk sends Meta's own lead id, which step the lead reached (estimate booked, quote approved, paid) and when, and what a paid job came to. To help Meta match the lead it already has, the customer's email address, phone number, name, city, state and zip code go too, but only scrambled (hashed) in Chalk first, never as readable text. Meta uses this to measure and aim the business's lead ads. Leads that did not come from Facebook are never sent.
We also disclose information when:
- The law requires it, or a valid legal process compels it. Where we may lawfully tell the business first, we will.
- It is needed to investigate fraud, abuse or a security incident, or to protect somebody's safety.
- Chalk is sold, merged or reorganised, in which case the information moves with the business and this policy continues to apply until replaced with notice.
6 ChalkBot and AI
ChalkBot is the assistant built into Chalk. It comes with the AI plan and the free trial. To answer a question, write a draft or read a photo, it sends information to an outside AI model. This section says what goes, who receives it, what they keep, and how to turn it off.
6.1 What ChalkBot sends
- The request: what a person types or says to ChalkBot, and the earlier messages in that chat.
- Shop details it works from: the business name, trade, address and hours, the price book, and staff names and roles.
- The records a task needs: for example a customer's name, phone numbers, email addresses and property addresses, their quotes, jobs, visits, invoices and payments, notes, and recent texts and emails with them.
- What it has been told to remember about the business or the person asking.
- Photos added to a chat, while photo reading is on. The photo file is sent to be described (again if the first try fails), and the file can include the time and place the camera saved in it. With photo reading off the photo itself is not sent, but ChalkBot is still told when it was taken and which of the business's properties it was taken near, if any.
- Incoming customer texts. While ChalkBot is on, a text from a customer is sent so ChalkBot can draft a reply, unless "Texting customers back" is set to off. A text asking to stop messages is never sent to be answered, though it can appear in the message history ChalkBot reads later.
- Routines the business sets up send the same kinds of information when they run.
Voice typing uses the speech recognition built into the browser or phone. Depending on the device, its maker (for example Google or Apple) may process the audio. Chalk receives only the words, which are then handled like typed text.
This information is sent only to produce the answer, draft or description that was asked for. It is not sold or used for advertising, and Chalk does not train AI models on it.
6.2 Who receives it
ChalkBot runs on DeepSeek V4 Flash, and reads photos with DeepSeek V4.1 Flash. These are openly published models that many hosting companies run. Chalk sends each request to OpenRouter, Inc., a United States company that passes it to one of those hosts.
Every request is marked zero data retention. That tells OpenRouter to use only hosts whose policy is to keep nothing: not the request, not the answer, not for any length of time. If none of those hosts is free, the request is not sent anywhere else; ChalkBot says it could not answer and nothing is changed.
- Chat replies are routed to Novita first, and to Azure (Microsoft) when it is slow.
- Everything else, and chat replies when those hosts are busy or down, may go to any host on OpenRouter's zero data retention list for the same model. That includes photo reading and background steps such as summing up a long chat. These hosts may be in the United States or in other countries, and the list changes over time. OpenRouter publishes it on its website.
6.3 What they keep
- OpenRouter stores prompts and replies only for customers who turn on prompt logging, and Chalk's OpenRouter account has prompt logging turned off. OpenRouter says it does not train on them. It keeps details about each request, such as its size and timing.
- The hosts that can receive ChalkBot's requests are, by OpenRouter's published data, hosts that keep no prompts or replies and do not train on them. Holding a request briefly in memory to answer it does not count as keeping it.
Inside Chalk, ChalkBot's chats, what it remembers and its photo descriptions are kept in the business's account like any other record, and are deleted with it. Anything ChalkBot remembers can be read and forgotten from the Memory panel in ChalkBot.
6.4 How to limit it or turn it off
The owner of the account can, on the ChalkBot page in Settings:
- Switch ChalkBot off. Its chats, routines and reply drafts stop, and nothing more is sent to an AI model for them. A ChalkBot Team helper has its own switch on the same page, and should be switched off too if it was turned on.
- Set "Texting customers back" to off, so incoming customer texts are not sent.
- Turn off photo reading, so photos are kept in Chalk but not sent to be described. Their date and nearest property are still shared, as described in section 6.1.
The owner also chooses which roles can use ChalkBot at all, under Team and permissions in Settings.
The Core plan does not include ChalkBot, so a business on Core sends nothing to an AI model. If you are a customer of a business that uses Chalk and do not want your messages read by ChalkBot, ask that business.
7 Messaging, carriers and consent
Text messages sent through Chalk go out from a number registered to the business that sent them, not from us. To make that possible, business registration details are filed with Telnyx, The Campaign Registry and the mobile carriers, and message contents pass through those carriers to reach a handset.
Mobile numbers and consent are never sold, rented or shared for anyone else's marketing. Consent a customer gives to one business is used only by that business, and is not shared with third parties or affiliates for their own marketing. It is not passed to any other business using Chalk.
Message contents and delivery records are kept in the sending business's account so it has a history of what was sent. Standard message and data rates may apply to recipients. Anyone can stop messages from a business by replying STOP, and should contact that business directly with any other request.
7.1 Your opt-in, and what happens to it
This is the part US carriers require to be stated plainly, and it is the page our customers' carrier registrations point at:
We will not share your opt-in to an SMS campaign with any third party for purposes unrelated to providing you with the services of that campaign. Your mobile number and your consent are never sold, rented, or passed to anyone else's marketing, to affiliates, or to any other business using Chalk.
The one place your number does go is the technical path a text has to take: our messaging carrier and the mobile networks, which is the only way a message reaches a handset. They handle it to deliver the message, not to market to you. What the messages contain, how often they come and how to stop them is set out in the messaging programme description.
8 Cookies and tracking
The app uses a small number of strictly necessary cookies and nothing else. There are no advertising cookies, no pixels and no analytics on app.chalkcrm.com, the customer portal, or any signed-in screen.
To count visits, this website (www.chalkcrm.com) uses Cloudflare Web Analytics. It is cookieless: it sets no cookies, stores nothing on your device and does not follow you from site to site. It collects no personal data. What we see is a tally of page views, which pages were visited, the site that linked there, and the type of browser and device, never who you are. Cloudflare, already our host, runs it.
This website also uses Google Analytics 4. It tells us which public pages are visited,
roughly where the visit came from, and what kind of browser and device. That is
aggregated usage data, not a profile of you, and it is not used to advertise. It does
not run on the app, the customer portal, or anything behind a sign-in. Google
Analytics sets first-party cookies named _ga and
_ga_YQL4K7SMGH so it can tell one browser from another across visits,
typically for up to two years. You can refuse those cookies in your browser, or
install Google's
opt-out add-on.
Google's own policy is at
policies.google.com/privacy.
| Cookie | Purpose | Lifetime |
|---|---|---|
chalk_session | Keeps you signed in. Http only. | Up to the length of the session you chose |
chalk_trust | Remembers a device you confirmed, so it is not asked for a code every time. | 30, 60 or 90 days, as the shop sets it |
chalk_device | Marks a shared shop device as enrolled, so the crew PIN pad can appear on it. | Until removed |
chalk_team | Set when a business's staff use the app, so their own looks at a customer's quote or invoice are not counted as the customer opening it. A random value that does not sign anyone in, and only counts while that sign-in lasts. Http only, sent to chalkcrm.com addresses. | 30 days, or until you sign out |
The app also uses your browser's local storage, under names beginning
chalk_, to remember preferences such as your chosen view and theme, and
to hold work typed while offline until it can be saved.
That stays on your device. If you turn on notifications, your browser's push service
holds a subscription identifier so a message can reach you.
9 How long we keep it
- While the account is open: business records are kept until the business deletes them. Chalk deliberately archives rather than deletes anything money has touched, so history stays intact.
- Backups: a nightly copy of each account is written to encrypted storage and kept for about fourteen days, then overwritten in the ordinary course.
- If the owner closes the account: it stops working at once and any text number is released, but the records are kept for 90 days so the owner can sign in to download them or reopen the account. After the 90 days they are deleted permanently, and copies inside backups age out within roughly fourteen days. The closing screen also offers a full download first.
- If a subscription ends or lapses, or a free trial ends with no plan: the account stops working but the data is kept, so a business that comes back finds its records where it left them. For 90 days after that day, the owner can still sign in to download all of its records, as spreadsheets or as one file; photos and documents are not in that download, and the owner can write to us for them. After the 90 days the data is still kept, and the owner can write to us for a copy. The same applies if we close an account, except an account we close for cause: nobody can sign in to it, its data is kept, and the owner can write to us about a copy.
- What outlives the account: billing and tax records we are required to keep, and a short note that an account existed and was closed, which contains the business name and date and none of its customer records.
- Logs: technical and security logs are kept for a limited period, typically weeks rather than years.
10 How we protect it
- Encrypted in transit, and at rest in Cloudflare's database and object storage.
- Passwords and PINs are stored only as salted hashes. Session, invitation, reset and device tokens are stored hashed as well, so a copy of the database does not hand somebody a working key.
- Two factor sign in by emailed code when a new browser appears, with device trust so it is not asked for daily.
- Every request is fenced to a single business. Cross business access is tested automatically on every release.
- Roles and permissions limit what each person in a business can see, including price and financial visibility for field crews.
- Data exports deliberately exclude credentials and access tokens. Nightly backups also leave out password hashes, sessions and device records, but keep what a restore needs, such as the links already sent to customers and the connections to Stripe, texting and QuickBooks.
- A full audit trail records who changed what.
No system is perfectly secure, and we cannot guarantee that information will never be accessed improperly. If a breach affects a business's information we will notify it without undue delay and provide what we know, so it can meet its own notification obligations to its customers.
11 If you are somebody's customer
If a business sent you a quote, an invoice, a receipt or a text through Chalk, that business chose to collect your information and decides what happens to it. We hold it on their behalf and we do not use it for anything of our own.
- To see, correct or delete what a business holds about you, ask that business. They control it and they can act on it directly.
- To stop text messages, reply STOP to the message. To stop emails, use the unsubscribe link or reply and ask.
- When you open a quote or invoice link, the business can see when you opened it, the kind of device (phone, tablet or computer) and, if it was opened inside an app such as Facebook or Instagram, which app. We do not keep your IP address or your browser's details for this.
- Links to a quote, invoice or portal are unguessable web addresses so you do not need an account to open them. Treat one like a private link and do not forward it to anyone you would not show the document to.
- If you cannot reach the business, or believe it is misusing your information, write to us at info@chalkcrm.com and we will pass it on and help where we can. In most cases we must refer you to the business, because acting on its records without instruction is not ours to do.
12 Your rights and choices
If your business holds a Chalk account, you can at any time:
- Export everything as spreadsheets or as a full backup file, from Settings and Data.
- Correct anything in the account, including the business name, directly in Settings.
- Delete individual records, or close the account and have everything deleted 90 days later.
- Control notifications and choose which channels are used for what.
- Ask us for a copy of the account information we hold as controller, or for it to be corrected or deleted, by writing to us.
We do not discriminate against anyone for exercising a privacy right. We may need to verify a request, and we will respond within the time the applicable law allows.
13 California and other state rights
Residents of California and of other states with comprehensive privacy laws have rights to know, access, correct, delete, and to obtain a portable copy of personal information, and to appeal a refusal. Where we act as a service provider to a business, those requests should go to that business, and we will assist it.
In the twelve months before the date of this policy we collected the categories in section 2, for the purposes in section 4, and disclosed them for business purposes to the providers in section 5. We do not sell personal information, and we do not share it for cross context behavioural advertising, including of anyone under 16. We do not use or disclose sensitive personal information beyond what is necessary to provide the service. We offer no financial incentive in exchange for personal information. An authorised agent may make a request with proof of authorisation.
14 People outside the United States
Chalk is operated from the United States and built for businesses working in the United States, and information is processed there and on globally distributed infrastructure. If you use Chalk from elsewhere, you are sending information to the United States, where privacy law differs from your own.
When ChalkBot is used, what it sends may be processed by an AI model host based outside the United States, as set out in section 6.2. Those are hosts whose policy is to keep nothing.
If a business has obligations under the GDPR, UK GDPR or a similar regime, write to us and we will provide a data processing agreement covering our role as processor, including the standard contractual clauses where they are required.
15 Children
Chalk is a tool for businesses and is not directed at children. We do not knowingly collect information from anyone under 13, and accounts require users to be at least 18. If you believe a child's information reached us, write to us and we will remove it.
16 Changes to this policy
We will update this policy as Chalk changes, and the date at the top will change with it. If a change is material, we will give notice by email or in the app before it takes effect. Providers added to section 5 will appear here before they begin processing anything.
17 How to reach us
Chalk · info@chalkcrm.com · Duncan, South Carolina, United States. Privacy, security, data protection and deletion requests all go to that address, and a person reads it.
Read this alongside the User Agreement, which sets out each side's responsibilities.