Privacy policy
Updated
What this covers
This policy covers the StillBooked marketing website, diagnosis-call request form, and iOS and Android apps, and the text messages StillBooked sends to people who call a shop that uses it. The section "Texts to a shop's callers" covers those messages, and the mobile app sections below describe account and sample-workspace handling.
Information you give us
When you request a diagnosis call, we collect what you type into the form: your name, business name, mobile number, email, the kind of shop you run, the booking tools you use, and your answers about missed calls. We don't collect anything from that form that you didn't type.
How we use it
We use the form information to schedule and prepare for your diagnosis call and to follow up about it. We don't add you to a newsletter or a drip sequence because you filled out the form.
Text message consent
By submitting the form you agree that we may text the mobile number you provided to schedule the call. Message frequency is limited to scheduling. Reply STOP to any message to opt out, and standard carrier rates may apply.
Texts to a shop's callers
When you call a shop that uses StillBooked and the call is not answered, StillBooked can text you for the shop. To do that we store the number you called from, the time and status of the call, and the texts in the conversation. Your number and the message text are encrypted in storage, and the call is not recorded. People the shop has added to its workspace can read the conversation, and when you reply, the shop's owner can get a text with the start of your message and the last four digits of your number. The providers we use to deliver texts and host and monitor the service receive what they need to do that. We do not sell your mobile number or share it with third parties or affiliates for marketing or promotional purposes. The shop sets how long conversations are kept. When that period ends, we clear your number and messages from our own records and delete the call and message records 30 days later. We keep a record of a STOP so the opt-out holds, and activity logs that hold no phone number or message text. Twilio, the messaging service that delivers the texts, keeps its own logs under its own policy. Reply STOP to any text to opt out.
Sharing and selling
We do not sell your information. For website and diagnosis-call information, we share it only with the service providers we use to run the site, store form submissions, and send email and text messages, and only so they can do those jobs for us. If you choose to pick a time on the confirmation screen, we send your name and email to Cal.com, the scheduling service, so the calendar can book your call. That only happens when you pick a time. If you don't, nothing is sent to Cal.com. The mobile app sections below describe account and enabled-feature transfers and providers' separate handling.
How long we keep it
We keep diagnosis-call requests for as long as it's useful to follow up, and we'll delete yours if you ask.
Cookies and analytics
If you allow analytics, Google Analytics uses cookies to measure page visits, navigation clicks, and successfully stored diagnosis requests. We send page paths and broad traffic-source categories, not your name, contact details, or form answers. Google also receives technical connection information when the analytics script loads. We do not enable advertising personalization. Your preference is saved in this browser; change it using Analytics preferences in the footer. Declining stops further analytics events but does not erase data already collected.
Contact
Questions about this policy or your information: hello@stillbooked.app. Mail: 11-11 Productions, 30 N Gould St, Ste 9081, Sheridan, WY 82801.
Scope and contact
This section covers the StillBooked iOS and Android apps and the account or shop settings pages they direct you to. It covers real account access, shop discovery, appointments, customer and shop conversations, business settings, and payment or notification features where available. The website and diagnosis-call sections of this policy describe their separate uses and retention. Separate SMS notices describe text-message programs.
StillBooked is operated by 11-11 Productions. Our mailing address is 30 N Gould St, Ste 9081, Sheridan, WY 82801. For privacy questions or help with account deletion, email hello@stillbooked.app. StillBooked is intended for adults aged 18 and over.
We do not sell or rent information from StillBooked accounts or share it for third-party advertising. The transfers needed to operate the app and its enabled features are described below. Payment, identity and delivery providers also handle information under their own applicable privacy notices.
Account and business information
Clerk handles account creation, sign-in and any required verification. Clerk receives your email, password or offered verification code. The app's own records and logs do not store your password or verification codes. Clerk also handles technical authentication information. This can include your IP address, client or device identifiers, sign-in activity, and approximate city or country derived from the IP address. When its diagnostic logging is enabled, Clerk can also receive technical logs about the identity software.
StillBooked stores account identifiers, email, language preferences and any supplied name or profile-image reference. Customer signup does not require a personal name or phone number. Business setup uses the shop or location name, owner contact phone, timezone, booking system and business settings. Account roles and shop memberships control access to personal and business records.
Convex hosts application records and stored listing images. Vercel hosts StillBooked's website and settings pages. Approved directory listings can show the shop's description, images, services, prices and supplied city or state. The directory uses location information supplied for the shop; its form does not request the device's GPS location. Photo management can open StillBooked's website settings.
The app and its identity software keep some information on your device, including sign-in state, preferences and a sign-out preference. Signing out does not delete your account or request deletion of its records.
Searches, appointments and conversations
Directory searches send your search text to StillBooked's backend to retrieve results, including while you type. There is no saved-search history feature. This does not promise that related service logs or caches disappear when the search ends.
Appointments include the chosen shop, service, staff and time, booking or payment status, and relevant provider references. The customer and authorized shop participants can access their appointment records. An external booking service handles information under its own terms when you follow its booking link.
Conversations store message text, sender information and timestamps. The authorized customer and shop participants can read them. These messages are not end-to-end encrypted. Reporting records the conversation and a report category; blocking records the relationship and restricts access. These controls do not promise an assigned human moderator or a response time.
Sample workspaces
Sample customer and business workspaces use fictional accounts and records. Their booking, message, payment, notification, review and deletion actions are simulations. They do not make real bookings, send customer messages, charge a card, contact a review service or delete a real account.
Sample records and drafts stay in temporary app state rather than being saved to your real account. Exiting the sample session discards that state. Do not enter real customer information there. This description concerns sample actions; the app can still contain identity, payment or notification software used by its real-account features.
Payments and subscriptions, where available
If your version and shop offer native appointment checkout, Square's embedded interface collects card number, expiration, security code and postal or ZIP code, then creates a one-time payment token. The interface can also return limited card details, such as brand, last four digits, expiry, postal code and card type. StillBooked uses the token to request payment and stores booking, amount, payment or refund status, and provider references for transaction handling and recovery. Its application records do not store the full card number or security code.
Square's payment software can also handle device or installation identifiers and interactions with the card interface, including cancellation. Its iOS payment software declares payment information, user and device identifiers, card-interface interactions and crash data. Payment information and crash data are declared for app functionality; user identifiers for functionality and analytics; device identifiers and interactions for analytics. These declarations are separate from StillBooked's own error-reporting controls. See Square's privacy notice for its broader handling. Cancelling card entry or disabling a payment feature does not itself erase information already handled by a provider.
When store subscriptions are offered, Apple or Google processes the purchase. StillBooked uses subscription status, account bindings and provider transaction or recovery references to verify access and resolve uncertain transactions. Deleting a StillBooked account does not cancel a store subscription. Manage it through Apple or Google.
Notifications and technical services
If you turn on app notifications, the app requests permission and can register your installation. StillBooked records the installation identifier, delivery token, language and signed-in account or session. Registration can occur even while notification delivery is unavailable; enabling permission does not guarantee that updates will be sent.
Expo, Apple Push Notification service and Firebase Cloud Messaging handle registration or delivery. This can involve their own installation identifiers and token records. Updates sent through this feature use a generic notice and app destination rather than the conversation's message body. See Expo's explanation and Firebase's privacy information.
Confirmed app cleanup revokes the installation's StillBooked delivery registration and removes active token ownership. Registration history and provider identifiers can remain. App and operating-system controls affect notification display or future use; they do not promise immediate deletion of every provider token or identifier.
Authentication and hosting services receive technical request, connection and event information to provide and protect their services. Convex logs can go to Axiom when that integration is configured. If StillBooked's optional Sentry error reporting is enabled, the app sends limited diagnostic information and excludes error-message text, account or contact details, screenshots, replay and breadcrumbs from that reporting path. These app controls do not describe every embedded provider's separate handling. Website analytics choices govern website analytics separately.
Retention and deletion
We keep information while it is needed for the account, conversation, listing, appointment, transaction, subscription or support request you use. Retained information needs a specific purpose and an end trigger. Roshawn Franklin checks the support inbox and deletion-request queue each business day and reviews records retained after deletion each month. A review schedule is not a promise that all records disappear within that period.
For bookings, payments and subscriptions, the criteria include unfinished settlement, refunds, recovery, disputes and any specifically identified record requirement. For safety records, they include the particular report or restriction still being handled. Listing images remain while used by the listing or a documented claim. Support records remain while the case or a specific dispute or deletion-proof need is open. We keep minimal deletion evidence while unfinished provider handling or applicable backup copies could restore deleted information.
You can request deletion from the app's Account screen or through StillBooked account deletion. The website explains how to submit a signed-in request; email hello@stillbooked.app if you need help. End active shop memberships and transfer ownership where needed before requesting deletion. We check membership again before completion. Acceptance of a request disables customer access and starts the process; it does not mean deletion has finished.
Account deletion has application and provider steps. Profile and contact information, conversation content and StillBooked notification records need separate handling from retained appointment, transaction, subscription, safety and deletion records. We distinguish a request being accepted from completed cleanup, identify the specific records still retained and explain remaining steps when we respond.
Some account identifiers, preferences, timestamps and history can remain before their cleanup or review is finished. Appointments, financial or subscription records, provider mappings, reports and deletion records also need review. Removing all of these records is not automatic. We assess the specific retained information against the criteria above; you can ask which records remain and how your request is progressing. A retained record needs its own reason and handling, rather than a blanket indefinite hold.
Identity deletion at Clerk, provider copies, service logs and backups need separate handling. Application cleanup does not establish immediate erasure from every provider or backup. Provider retention can differ from StillBooked's records. We track incomplete steps separately. Account deletion does not automatically cancel appointments, issue refunds or cancel subscriptions.
Security and requests
StillBooked uses authenticated account and shop permissions and HTTPS for its application requests. Shared conversation participants and authorized business members can still access the records described above. Contact hello@stillbooked.app with questions about access, correction, retained records or deletion. Support mail passes through Cloudflare forwarding to our Gmail inbox. Do not send passwords, verification codes or full payment-card information.