Effective: September 15, 2026
Calemander LLC (“Calemander”, “we”, “us”) provides scheduling software at calemander.com. This policy describes what we collect, why, and how it is handled. Questions: support@calemander.com.
Calemander's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google Calendar data is used solely to show your availability and to create, update, and cancel calendar events for your bookings. It is not sold, not used for advertising, and not read by humans except with your permission or for security purposes.
We do not sell personal data. These companies help us run Calemander, and each gets only what its job needs. Some are always involved; others only see your data if you connect or choose them.
| Provider | What they do for us | Data they handle | When |
|---|---|---|---|
| Cloudflare | Hosting, databases, file storage (including visit photos), the bot check on forms, backup email route | Everything we store, IP addresses, request logs | Always |
| Emailit | Sends our booking and account emails | Recipient name, email address, booking details | Always |
| Stripe | Our subscription billing, and payments for hosts with a connected Stripe account | Owner name and email address; attendee email address and payment status. Card numbers go to Stripe, never to us | Billing always; payments only if you connect Stripe |
| Telnyx | Text-message reminders, and a backup route for our email | Phone number and message text (name, time, link); recipient name, email address and booking details when the backup email route is used | Texting only if you turn it on; email backup always |
| Square | Payments and saved cards | Attendee name, email address, payment status; cards are entered on Square's own form | Only if you connect it |
| Calendar sync, Meet links, Google sign-in, Google Fonts on booking pages | Busy times, events with the attendee's email address, your sign-in email address, visitor IP address when a font loads | Only if you connect or choose it | |
| Microsoft | Outlook calendar sync, Teams links | Busy times, events with the attendee's email address | Only if you connect it |
| Zoom | Creates the meeting for each booking | Meeting title (event and attendee name), time | Only if you connect it |
| Your CalDAV provider (iCloud, Fastmail, others) | Calendar sync | Busy times, events | Only if you connect it |
| Resend | Email from your own domain | Recipient name, email address, booking details | Only if your domain is verified with Resend |
| Clio | Writes your bookings to your firm’s Clio calendar and contact list | Client name, email address, optional phone number, the appointment time and the event type's name, and the meeting link. We send no answers to your booking questions | Only if your firm connects it |
| LawPay (8am) | Card payments for law firms | Attendee name, email address, payment status; cards are entered on LawPay's own form | Only if you connect it |
| Jitsi Meet (8x8) | Video room | Nothing from us; the call runs on their servers | Only if you choose it |
Tools you connect yourself (Google Analytics, Slack, Zapier, your own webhooks, an AI assistant through our MCP connector) receive booking data on your instructions. They work for you, not for us, and you can disconnect them at any time.
Our operations dashboards see counts and internal IDs only, never names, email addresses, or phone numbers.
If we add a provider that every workspace uses, we email workspace owners before it goes live and note the change here.
On calemander.com — our marketing pages, documentation, signup and the dashboard — we measure how the site is used with Google Analytics, loaded through Cloudflare Zaraz. Zaraz sends this from Cloudflare's network rather than from your browser, so Google runs no script on our pages. We record which pages are viewed and a small set of product events, such as a signup being started or a booking link being copied. We do not send your name, your email address, your workspace name, or anything you type.
This does not run on booking pages, and it does not run on a workspace's own booking domain. Someone booking an appointment is your customer, not ours, and our analytics never sees them.
Calemander integrates with Clio Manage and with Clio Identity (“Sign in with Clio”). Both are optional, both are turned on by your firm, and neither is on until an administrator at the firm authorises it.
What we send to Clio. When a booking is confirmed on an event type your firm has switched on, we create or find a contact for the person who booked and put the appointment on the responsible lawyer’s Clio calendar. That means the client’s name, email address and, if they gave one, their phone number; the appointment’s start and end time; the name of the event type; and the video meeting link if there is one. We also attach the booking’s own reference to the calendar entry, so we can find the same entry again instead of creating a second one. If the booking is rescheduled we move that entry, and if it is cancelled we delete it.
The optional time entry. Your firm can additionally turn on a time entry. With it on, when a consultation has ended we write one time entry to Clio for the responsible lawyer, carrying the appointment’s duration, the name of the event type and the client’s name, and marked non-billable if your firm has said consultations are free. It is off unless your firm turns it on, and turning it off stops any further entries.
What we do not send. We do not send the answers your clients give to your booking questions. We do not write notes, we do not create matters, and we write no documents and no bills. Whether Clio emails your client about the appointment is a switch your firm controls, and it is off unless you turn it on.
What we keep from Clio. Identifiers, and not contents. What we store is a Clio contact id next to an email address, a Clio calendar entry id next to a booking, a Clio time entry id where one was written, the Clio calendar and the Clio user id for each of your members, the Clio user id of whoever authorised the connection, your firm’s name, the Clio region you connected, our own record of the permissions we registered with Clio, and the access credentials themselves, which are encrypted. Separately, so that a second person at your firm joins the workspace you already have rather than a new one, we keep your firm’s Clio account identifier and, for anyone who signs in with Clio, the identifier Clio uses for that person. Names, matter numbers, note text and anything else your firm keeps in Clio are not copied into Calemander. We never read your Clio calendar to work out your availability — that comes from the calendars you connect directly, such as Google or Outlook — so the information only ever travels from us to Clio.
Sign in with Clio. If you sign in that way, Clio tells us your first name, last name, email address and an identifier for your Clio account, and we use those to create or recognise your Calemander account. The first time anyone at your firm signs in this way, the sign-in continues straight into a Clio Manage authorisation, on Clio’s own consent screen, so that the workspace we set up is your firm’s and appointments have somewhere to go. You can decline that screen and still be signed in — nothing is connected unless you approve it. If you do approve it, the Clio Manage connection belongs to the workspace, and everything above about what we send and what we keep applies to it.
You are in control of the connection. An administrator can disconnect Clio in Calemander at any time: we tell Clio to revoke the authorisation and we remove the connection and the tokens we hold for it. You can also revoke our access from inside Clio, which stops the flow at once and leaves Calemander showing that the connection needs reconnecting until someone disconnects or reconnects it here. Appointments already written to your Clio calendar stay there either way, because they are your firm’s records and removing them is not ours to do. Your Clio data itself remains governed by your own agreement with Clio.
Support is ours. If the integration misbehaves, ask us at support@calemander.com. We will not send you to Clio for a problem with our integration.
LawPay (operated by 8am) is one of the payment providers a host can connect. As with Stripe and Square, the money moves between the person booking and your own merchant account; you are the merchant of record and we are not. Card details are entered in LawPay’s own fields and never reach Calemander. What we store is the payment status and LawPay’s reference identifiers, plus your connection’s credentials, which are encrypted.
LawPay accounts include trust accounts, and which account a paid event type deposits into is a choice only your firm can make — we offer no default and will not save an event type until you have chosen. Because LawPay allows one refund per trust deposit, Calemander stops you issuing a second refund against a booking that has already been refunded. That is a convenience so the platform does not help you break a rule by accident. It is not legal or compliance advice, it does not make us responsible for your trust accounting, and your obligations under your state bar’s rules remain entirely yours.
Booking and account data is retained while your workspace is active. Disconnecting a calendar removes its stored credentials immediately. To delete your workspace and its data, or to request an export, email support@calemander.com — we honor deletion requests within 30 days.
A workspace can also set its own retention period for the answers people give on its booking forms: 30, 90 or 365 days after the appointment ends. This is off unless the workspace turns it on, and the workspace decides it, not us. When it is on we delete those answers and the copies we hold of them, keeping only the questions and the date the answers were deleted. What has already been sent — confirmation and reminder emails, text messages, and calendar invitations — is not recalled, because those copies are in inboxes and calendars we do not control. Deleted answers cannot be restored.
We will update this page when our practices change; material changes will be announced to workspace owners by email.