DRAFT for review. This policy hasn't been adopted or legally reviewed yet.

Privacy policy

Instant Appointments & Tickets, by FourCore. Last updated 30 October 2026.

Who this covers

Instant Appointments & Tickets is a Shopify app made by FourCore. Stores install it to sell appointments, classes, stays and event tickets. This policy explains what the app does with personal data.

The store you bought from decides how your booking is used, and its own privacy policy applies too. We process your details for that store, to run its bookings. If you have a request about your data, it's usually quickest to contact the store directly.

What we process

We don't collect shipping or billing addresses, and we don't take card details. Payments happen in Shopify's checkout.

Why we process it

We don't sell personal data, and FourCore doesn't use it to advertise. A store that connects its own Meta Pixel or Google Analytics can use its booking events to measure its own ads (see “Tools a store connects”).

Who else handles it

These companies run parts of the app for us:

Tools a store connects

A store can choose to send booking events to its own tools: Klaviyo, Zapier, Make, n8n, its own webhook address or our API. These events can include the customer's name, email and phone number. Nothing is sent unless the store connects the tool. That store is then responsible for how the tool uses the data.

A store can also connect its own Meta Pixel or Google Analytics, using its own keys. Meta then receives booking events (the service, value and whether a booking was confirmed, moved or cancelled) with the customer's email, phone and name in hashed form. Google receives the same events with no name, email or phone. If you've unsubscribed from a store's follow-up emails, your bookings aren't sent. Steps before a booking, such as viewing the booking widget or choosing a time, are only sent if you've allowed marketing or analytics on that store: Meta gets your browser's user agent, the page address and the Meta cookies already on your browser, and Google gets the Google Analytics ID already on your browser. We don't keep those details. Meta and Google use this data under that store's agreements with them, and the store is responsible for it, including asking for any consent its region requires.

A store can connect its own WhatsApp Business number. If you tick the box to get booking updates on WhatsApp, Meta (WhatsApp) receives your phone number and the message: your name, the service, its date and time, and a link to manage your booking. Without that box ticked, or once you unsubscribe from the store's emails or reply STOP on WhatsApp, nothing is sent there. We keep whether you agreed, your number, and whether each message was delivered and read. The store's access to its WhatsApp account is encrypted in our database and forgotten when it disconnects WhatsApp or uninstalls the app.

A store or its team members can connect a Google Calendar. Then Google receives each booking as an event: the service, its time, and your name, email, phone and notes, plus you as a guest if the store chose to invite customers. The app reads that calendar's busy times to stop double bookings, and reads changes to its own booking events to move or cancel the booking. It keeps no other calendar details. Its use of Google data follows Google's API Services User Data Policy, including the Limited Use requirements. The access is encrypted in our database and revoked when the calendar is disconnected or the app is uninstalled.

A store can connect Zoom. Then each online booking gets a Zoom meeting named after the service and your name, at the booking's time, and its link is sent to you. Zoom handles the meeting under its own privacy policy. The store's Zoom access is encrypted in our database and revoked when it disconnects Zoom or uninstalls the app.

Storefront and cookies

The booking widgets count views and selections per product, with nothing that identifies a person. They remember your 12 or 24-hour clock choice and short-lived cart notices in your browser's storage. The app sets no advertising or tracking cookies. If a store connects Meta or Google and you've allowed it, the widgets read the cookies those companies' own tags already set, to send the steps described above. The staff portal uses one sign-in cookie, for team members only.

How long we keep it

Automatic removal of older customer details is built but not turned on yet. The proposed periods are 24 months after a booking ends for customer details, and 12 months for email logs and waitlists.

Your choices and rights

You can ask the store you bought from to see or delete your data. Through Shopify, the store can send us that request, and we then send it what we hold, or remove your details. When a store uninstalls the app, Shopify asks us to delete that store's data and we do.

A store's booking emails can include a link to manage your booking.

Security

Connections to the app and its database use encrypted connections (HTTPS and TLS). Our hosting providers state that they encrypt stored data: see Neon's and Resend's security pages. Access to customer details inside the app is recorded, and the store can see that log.

Contact

Questions about this policy or your data: support@fourcore.dev.

We'll update this page if what we do changes.