Who we are
Open Source Calendar is an online booking calendar for businesses, available at opensourcecalendar.com and its booking addresses. This policy explains what information the service handles, why, and the choices you have. Questions go to privacy@opensourcecalendar.com.
Open Source Calendar is also open-source software. If a business runs its own copy on its own servers, that business is responsible for it and this policy does not cover it.
Two kinds of people use the service
- Businesses that set up a booking page (and the agencies that set them up for clients).
- Customers who book an appointment with one of those businesses.
When you book with a business, that business decides what it asks for and what it does with your booking. We store and process your booking for the business, on its behalf. For questions about a particular business’s use of your details, contact that business; we will also help if you write to us.
Information we handle
When you book an appointment
- Your first and last name, and the email address and phone number you enter.
- Any note you add, and the service, date and time you choose.
- If you tick the box to receive text messages, a record of that permission: the wording you agreed to, the phone number and the time.
- The time zone your device uses, so times are shown correctly.
Each booking keeps a copy of the contact details entered for it, so the business can see who booked even if details change later.
When a business uses the service
- The business name, booking-page settings, services, prices, opening hours and days off.
- Logos and photos the business uploads.
- Customer and appointment records the business adds or edits.
- If the business connects Google Calendar: the Google account’s email address, the name and ID of the chosen calendar, and the sign-in tokens Google gives us (stored encrypted). See “Google Calendar” below.
When you join the waitlist
Your email address and the date you joined. Nothing else.
Technical information
To keep the service working and safe, our hosting provider Cloudflare processes your IP address and basic browser details when you load a page, and keeps short-lived technical logs. The booking page uses Cloudflare Turnstile to check that a booking comes from a person, not a bot; Turnstile works without advertising cookies.
How we use it
- To show booking pages, take bookings and stop two people booking the same time.
- To send booking emails: confirmations, changes, cancellations and reminders, to the customer and to the business.
- To let customers change or cancel their own booking from the private link in their email.
- To copy bookings into the business’s Google Calendar and block times it is busy, when the business turns that on.
- To send one email to waitlist members when hosted plans open.
- To keep the service secure, prevent abuse and fix problems.
We do not sell personal information, share it for advertising, or use it to build marketing profiles. We do not send marketing emails to a business’s customers.
Google Calendar
A business can connect its Google Calendar. When it does, Google asks the business to allow two things:
- See the list of its calendars, so it can choose which one to use.
- See and edit events on the chosen calendar. We read when events start and end, and whether they are marked busy, so those times can’t be booked. We store only those start and end times, not event titles, descriptions or guests. We also add, update and remove events for appointments made through the booking calendar; these events include the service, and the customer’s name, phone, email and note, so the business can see them in its own calendar.
Open Source Calendar’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular, we use Google data only to provide the calendar features the business turned on; we do not use it for advertising, do not sell it, do not use it to train AI or machine-learning models, and no person reads it except with the business’s permission, for security, or where the law requires.
A business can disconnect Google at any time from its settings. That deletes the stored tokens and busy times right away. Access can also be removed from the Google account at myaccount.google.com/permissions.
Who else handles the information
- Cloudflare hosts the service, stores its data, sends its emails and runs the Turnstile bot check.
- Google, only when a business connects Google Calendar, as described above.
- The business you booked with, which can see and manage your booking. A business can also connect its own software (for example a customer database) to receive booking details.
We may also disclose information if the law requires it, or to protect people or the service from harm or fraud.
How long we keep it
- Bookings and customer details stay until the business deletes them, or until a deletion request is handled.
- Records of sent emails and other background tasks are deleted after 30 days.
- Google tokens and busy times are deleted when the business disconnects Google.
- Waitlist addresses are kept until hosted plans open and we have sent the one email, or until you ask us to remove yours.
- Text-message permission records are kept after a deletion as proof that permission was given.
Your choices and rights
- Customers can ask for their details to be deleted from the manage link in any booking email. The business sees the request and deletes the details; this also removes them from bookings copied to Google Calendar. You can also write to us.
- Anyone can ask us for a copy of the information we hold about them, or ask us to correct or delete it, by emailing privacy@opensourcecalendar.com. We may need to check it’s really you, and we may pass a request to the business it concerns.
- Depending on where you live, you may have more rights under laws such as the GDPR or US state privacy laws. We will honor them.
Cookies and tracking
We do not use advertising or analytics cookies, and we do not track you across other websites. The owner screens keep a sign-in key in your browser for the current tab, and remember small display choices such as the calendar view.
Security
All traffic is encrypted. Google sign-in tokens are encrypted before they are stored. Customers’ manage links are signed so they can’t be guessed. No system is perfectly secure, but we work to protect your information and will tell affected people about a breach as the law requires.
Children
The service is meant for businesses and adults booking appointments. It is not directed at children under 13, and we do not knowingly collect their information.
Where the data is
Data is stored and processed by Cloudflare, which may handle it in the United States and other countries.
Changes
If we change this policy, we will update the date at the top. For important changes we will also tell businesses using the service.