ActBook is booking software for live entertainers and event businesses. It is a product of
eDetroit LLC, 29035 Five Mile Rd, Livonia, MI 48154, USA (“ActBook,” “we,”
“us”). This policy explains what information we collect, how we use it, who handles it for us, and the
choices you have. It covers the ActBook app at actbook.app, our website at
actbookapp.com, and the websites and booking pages ActBook hosts for its
customers.
1. Who this covers
Customers — the performers and businesses that have an ActBook account, and the staff
they invite.
Our customers’ clients and contacts — people who book, sign, pay or get messages
through a customer’s ActBook pages, and people a customer keeps records about or writes to. For this
information the customer decides what is collected and why; we process it for them as their service provider. If
you are a client and want to see, correct or delete your information, ask the performer or company you dealt
with, or write to us and we will pass it on.
Visitors to our website and people who chat with us or email support.
2. Information we collect
Account and profile. Name, email, phone, business name and address, the kind of act you run,
login details (passwords are stored only as salted hashes), and each user’s role.
Business data you enter or import. Clients and their contacts, bookings, event dates and
places, quotes, contracts, signatures, waivers, invoices, payments recorded, notes, documents and photos you
upload, calendar entries, your website content, and your outreach campaigns and prospect lists.
Information from your clients. What a client types into your booking, inquiry, waiver,
review or sign-up forms; their e-signature with the date, time, IP address and browser; and their replies to
your emails and texts.
Payments. Card details are entered on Stripe’s pages and handled by
Stripe. ActBook never receives or stores full card numbers. We keep payment records (amount,
date, status) and a reference to the Stripe transaction.
Messages. Emails and texts sent through ActBook, their delivery status (delivered, bounced,
opted out), and replies. If you forward a mailbox into ActBook or connect one for outreach, we store the
messages that arrive there so they can be shown in your inbox and matched to clients.
Connected accounts. If you connect Google, Apple, Zoom or Microsoft, we access the data
described in sections 5 to 8, and nothing more.
Support. What you write to support or in the chat on our site or in the app. Chat from our
public website also records the visitor’s IP address to prevent abuse.
Technical data. IP address, browser type, and the cookies described in section 14. We
also record which features are used (for example “opened Settings”), not what you type into
them.
Sign-up source. If you arrive from a link or an ad, we note the campaign it came from.
Business contact directory. We keep a directory of organisations that book entertainment
(schools, libraries, fairs and similar) with business contact details gathered from public sources, which
customers can use for outreach. To be removed from it, email us.
3. How we use information
To run ActBook for you: bookings, calendars, contracts, invoices, payments, your website and your
outreach.
To send email and text messages on a customer’s behalf to that customer’s own clients and
prospects: confirmations, contracts, payment links, reminders, thank-yous, review requests and campaigns.
To process subscription payments, and deposits and balance payments, through Stripe.
To sync gigs with your Google or Apple calendar, and to create Zoom or Google Meet links, if you connect
them.
To provide support, keep the service secure, prevent abuse and fraud, and meet legal obligations.
To understand which features are used so we can improve the product.
To email you about your account (receipts, security notices, changes to the service) and, during setup,
tips for getting started.
We do not sell personal information, and we do not use it for advertising.
4. Who handles data for us
We share data only with the companies needed to run the service, each under its own privacy and security
terms. Some are used only if you turn on the feature.
All data stored in ActBook; the name and address on a sending domain you buy (kept private in public registration records)
Stripe
Subscription billing; deposits and balance payments through your own connected Stripe account
Card and billing details entered on Stripe’s pages; email; amounts; a booking reference
Twilio
Sending and receiving text messages
Mobile numbers and message text
OpenAI
AI features (section 9)
The text or images the feature works on
Google
Calendar sync and Meet links (opt-in); sending email from your Gmail or Workspace address (opt-in); maps, distance and place lookups
Calendar events for your gigs; emails you send; addresses and place searches
Microsoft
Sending and reading mail in an Outlook or Microsoft 365 mailbox you connect; hosting sending mailboxes we set up for you
Emails you send and receive in that mailbox
Apple (iCloud)
Two-way calendar sync over CalDAV (opt-in)
Calendar events for your gigs
Zoom
Creating video-meeting links for discovery calls (opt-in)
Meeting topic and time
Cloudflare
Bot check (Turnstile) on sign-up, chat and some public forms
Browser and network signals from the visitor
Bouncer
Checking that an email address exists before outreach is sent to it
The email address being checked
TD SYNNEX
Licences for the Microsoft 365 mailboxes we set up for you
The licence order only
Backblaze
Off-site copy of our backups
Backups, encrypted by us before upload
Website analytics run on software we host ourselves (section 14), so no analytics company receives your
data. If you connect an AI assistant or automation tool to your account through our API, that tool receives the
data you allow it to request.
We may also disclose information if the law requires it, or to protect the rights, safety and security of
ActBook, our customers or others. If ActBook is ever sold or merged, your information may pass to the new owner,
and we will tell you first.
5. Google user data (Calendar & email integrations)
Connecting Google Calendar is optional. If you connect it, you grant ActBook access to your Google Calendar
through Google’s OAuth consent screen. Specifically:
What we access: your Google account email address (to label the connection), and read/write access to your Google Calendar events (scope https://www.googleapis.com/auth/calendar.events).
How we use it: solely to (a) create, update and remove events in your Google Calendar that correspond to your ActBook bookings, and (b) display your calendar alongside your gigs. We do not use Google data for any other purpose.
Storage: we store an encrypted Google refresh token and short-lived access token so syncing can run in the background, plus a mapping between your ActBook bookings and the Google events we created. You can revoke this at any time (Section 12).
Sharing: we do not share, transfer, or sell your Google data to anyone, and we do not use it for advertising or to train any machine-learning/AI models.
Connecting a Gmail / Google Workspace mailbox to send outreach is also optional. If you connect one:
What we access: your Google account email address (to label the connection), and permission to send email on your behalf (scope https://www.googleapis.com/auth/gmail.send). We request no read access to your mailbox.
How we use it: solely to send the outreach and follow-up emails you compose and schedule in ActBook, from your connected address. We do not read, store, or analyze the contents of your mailbox, and we do not use Google data for any other purpose.
Storage: we store an encrypted Google refresh token and short-lived access token so your scheduled sends can run in the background. You can revoke this at any time (Section 12).
Sharing: we do not share, transfer, or sell your Google data to anyone, and we do not use it for advertising or to train any machine-learning/AI models.
Limited Use disclosure. ActBook’s use and transfer of information received from Google APIs
to any other app will adhere to the
Google API Services User Data Policy,
including the Limited Use requirements.
6. Apple iCloud Calendar data (two-way calendar sync)
Connecting Apple Calendar is optional. Apple does not offer an OAuth sign-in for calendars, so you connect by
creating an app-specific password for ActBook at appleid.apple.com and entering it with your Apple
ID email. ActBook never asks for, sees or stores your regular Apple ID password. Specifically:
What we access: over Apple’s CalDAV service (caldav.icloud.com), the list of
your iCloud calendars (names and colours), read/write access to the calendar you choose for your gigs (by default a
new “ActBook gigs” calendar we create), and read access to the events (title, start and end time) in the
calendars you choose to count as busy, for the next 90 days.
How we use it: solely to (a) create, update and remove events in your chosen iCloud calendar that
correspond to your ActBook bookings, and (b) treat your chosen calendars’ events as busy time — showing
them on your ActBook calendar and keeping those times free on your discovery-call and booking pages. Events you mark
as free, cancelled events and invitations you declined are ignored.
Storage: your Apple ID email, the app-specific password encrypted at rest, the
addresses of your iCloud calendar home and chosen calendars, a mapping between your ActBook bookings and the iCloud
events we created, and the start/end time and title of upcoming busy events (refreshed every 15 minutes, and removed
when they pass or are deleted in iCloud).
Sharing: we do not share, transfer, or sell your iCloud data to anyone, do not send it to any
AI/ML service, and do not use it for advertising or to train any machine-learning/AI models.
Deletion: disconnect at any time from the Calendar page in ActBook (Calendars) or the guided
calendar setup — we delete the stored password, calendar addresses, event mapping and busy events — or
revoke the app-specific password at appleid.apple.com, which stops all access immediately. Gigs already written to
your iCloud calendar stay there until you delete them (or the “ActBook gigs” calendar) in iCloud.
7. Zoom user data (video meeting integration)
Connecting Zoom is optional. If you connect it, you authorize ActBook through Zoom’s OAuth consent screen to
create meetings on your behalf. Specifically:
What we access: permission to create, read and delete meetings on your Zoom account (scopes meeting:write:meeting, meeting:read:meeting, meeting:delete:meeting), and your Zoom user identifier and email (to label the connection and manage the meetings we create).
How we use it: solely to generate a unique Zoom meeting link when a prospect books a discovery call through your ActBook scheduling page, and to update or cancel that meeting if the booking changes. We do not use Zoom data for any other purpose.
Storage: we store an encrypted Zoom refresh token (so links can be created in the background) and your Zoom user id/email. We do not record, store, or access the contents of any Zoom meeting.
Sharing: we do not share, transfer, or sell your Zoom data to anyone, and we do not use it for advertising or to train any machine-learning/AI models.
Deletion: you can disconnect Zoom at any time from the Meetings page in ActBook, or uninstall ActBook from the Zoom App Marketplace. On disconnect or uninstall we delete the stored Zoom tokens and identifiers; uninstalling also triggers Zoom’s deauthorization notification, which we honor automatically.
8. Microsoft mailbox data (sending email)
Connecting an Outlook or Microsoft 365 mailbox is optional. If you connect one through Microsoft’s
sign-in screen:
What we access: your account email address, permission to send mail from that mailbox, and
permission to read it (scopes SMTP.Send and IMAP.AccessAsUser.All).
How we use it: to send the outreach and follow-up emails you schedule in ActBook from your
address, and to read incoming mail so we can spot replies and bounces — stopping a sequence when someone
answers, and showing the reply in ActBook.
Storage: an encrypted refresh token, and the messages we match to your clients,
prospects and campaigns.
Sharing: we do not sell or share your mailbox data, and we do not use it for advertising or
to train AI models. If you turn on AI reply sorting (section 9), the subject and opening lines of an
outreach reply are sent to OpenAI to classify it.
Deletion: disconnect the mailbox at any time in ActBook (Email accounts), or remove
ActBook’s access in your Microsoft account. On disconnect we delete the stored token.
If ActBook sets up sending mailboxes for you on a domain you buy or connect, those mailboxes are hosted in
Microsoft 365 and ActBook sends and reads mail in them for the same purposes.
9. AI features
ActBook’s AI features are powered by OpenAI, through OpenAI’s API. What each one
sends:
The in-app assistant (optional, enabled per account). It works with your own ActBook
business data — your bookings, clients, quotes, invoices and the like — and only the records in
your own account. What you ask it, and the records it looks up to answer, are sent to OpenAI.
Support chat. The chat on our website and in the app is answered first by an AI assistant,
and a person takes over when needed. Your chat messages are sent to OpenAI.
Setup help. If you give us your website address when you sign up, we read the public pages
and send their text and images to OpenAI to draft your profile, packages and booking page. Drafting outreach
emails sends the description of your act.
Reply sorting (optional). If you turn it on, the subject and opening lines of replies to
your outreach are sent to OpenAI to label them (interested, not interested, unsubscribe).
Google and Zoom data are never sent to it: information obtained through the Google Calendar,
the Gmail / Google Workspace sending integration, or Zoom — calendar events, availability, OAuth tokens,
your Google/Zoom account email, or the Gmail mailbox you connected to send from (which we access with the send-only
gmail.send scope and therefore cannot read) — is never transmitted to OpenAI or
any other AI/ML service, in raw, aggregated, or derived form. Those integrations are fully isolated from the AI
features. The same is true of Apple iCloud calendar data.
No model training on your data: we do not use your data — and in particular never use any
Google or Zoom user data — to create, train, or improve any foundational or generalized machine-learning/AI
model. Requests are made through OpenAI’s API, under which, per OpenAI’s API data-usage policy, submitted
data is not used to train OpenAI’s models.
AI can be wrong. Check what it writes before you rely on it.
10. Text messages
ActBook sends text messages for its customers to their own clients about a booking (program name:
“ActBook Booking Notifications”). A mobile number you give to receive booking texts is used only to
send messages about your own booking and to show your replies to the performer or company you booked.
Mobile information and SMS consent are never shared with third parties or affiliates for marketing or
promotional purposes. Text messages are delivered through our messaging provider, Twilio. Reply
STOP at any time to opt out, or HELP for help. Details:
Text Message Program and the Terms.
11. How long we keep data
While your account is active: we keep your data so the service works.
After you cancel: we keep the account’s data for at least 30 days so you can export it
or come back. After that we may delete it, and we delete it within 30 days of a written request. An account
admin can download the account’s data at any time.
Unfinished sign-ups: deleted automatically — if the email was never confirmed, 3 days
after you started or after the last link we emailed you, whichever is later; 7 days after it was confirmed if it
was. We may email up to two reminders about an unfinished sign-up. Each one has a link that stops them and can
delete what you entered right away.
Connected accounts: Google, Zoom and Microsoft tokens and Apple app-specific passwords are
kept only while the connection is active, and deleted when you disconnect or the account is deleted.
Backups: encrypted backups are kept on a rolling schedule and expire within 12 months.
Deleted data stays in those backups until they expire, and is not restored except to recover from a
failure.
Records we must keep: billing and tax records, and opt-out lists (so we do not message
someone who asked us to stop), are kept as long as the law or that purpose requires.
12. Your choices & rights
Disconnect Google Calendar at any time from the Calendar page in ActBook, or revoke ActBook’s access directly at myaccount.google.com/permissions. On disconnect we delete the stored tokens and stop syncing.
Disconnect Apple Calendar at any time from the Calendar page in ActBook, or revoke the app-specific password at appleid.apple.com (Sign-In and Security → App-Specific Passwords). On disconnect we delete the stored password and calendar data and stop syncing.
Disconnect Zoom at any time from the Meetings page in ActBook, or uninstall ActBook from the Zoom App Marketplace. On disconnect or uninstall we delete the stored Zoom tokens and identifiers.
Disconnect a mailbox at any time from Email accounts in ActBook.
Access, correct, export or delete your data. Customers can edit or remove most data in the
app and download a full export. For anything else, email
support@actbook.app and we will act on it within 30 days.
We do not treat anyone differently for using these rights.
Stop emails and texts. Every outreach email and newsletter sent through ActBook has an
unsubscribe link. Reply STOP to any text.
Account closure. When an account is deleted we delete or de-identify its personal data,
except where we are required to keep it (section 11).
13. Security
Data is sent over TLS (HTTPS).
The database and our servers’ disks are encrypted at rest. Uploaded files are stored in Amazon S3.
Passwords are stored as salted hashes. Sensitive secrets — including Google, Zoom and Microsoft
refresh tokens, Apple app-specific passwords and mailbox passwords — are encrypted at rest.
Each customer’s data is kept logically separate, and access to internal APIs is authenticated and
scoped.
Backups are taken nightly and a copy is kept off-site, encrypted before it leaves our server.
No system is perfectly secure. If we learn of a breach that affects your information, we will tell you as the
law requires.
14. Cookies and analytics
Necessary cookies. A session cookie keeps you signed in, and security cookies protect forms.
We also set a cookie, kept for up to 90 days, noting which link or campaign brought you to sign-up.
Bot check. Sign-up, chat and some public forms use Cloudflare Turnstile to tell people from
bots. Cloudflare may set its own cookie for that check.
Analytics. We measure traffic on our website and sign-up pages with Umami, open-source
analytics that we host ourselves. It sets no cookies and builds no profile of you. It records page visited,
referring site, browser, operating system, device type and country. It is not shared with anyone.
We do not use advertising or cross-site tracking cookies.
15. Where data is processed
ActBook is run from the United States and data is stored on servers in the United States. If you use ActBook
from another country, your information is transferred to and processed in the United States.
16. Children
ActBook is a business tool. It is not directed to children under 13 and we do not knowingly collect personal
information from them. Customers who serve families may record a child’s first name or age for an event
(for example on a birthday booking or a waiver signed by a parent); that information belongs to the customer and
is handled as described in section 1.
17. Changes to this policy
We may update this policy. If a change is material we will tell customers by email or in the app, and we will
update the date at the top.
18. Contact us
Questions or requests about privacy:
eDetroit LLC · 29035 Five Mile Rd, Livonia, MI 48154, USA support@actbook.app