RuboCal

Privacy policy

Effective November 17, 2026

RuboCal is a scheduling service operated by Rubotic ("we", "us"). A host signs in, connects their calendars and shares booking links. A guest uses one of those links to book a time with a host. This page says what we collect from each, what we do with it, and how to have it removed.

We do not sell personal information, show ads, or use analytics or advertising trackers.

What we collect from hosts

  • Your account. When you sign in with Google, our sign-in provider (Firebase Authentication) receives your name, email address and profile picture. We keep your name and email address with the handle, time zone, photo link, welcome message and brand color you choose.
  • Your setup. The booking links, intake questions, working hours and webhook addresses you create.
  • Your calendars. For each calendar you connect: its name and color, and the start and end times of the events on it, which is how we know when you are busy. See the next two sections for exactly what is read.

Google user data

Connecting Google Calendar is optional and separate from signing in. When you connect it, RuboCal asks Google for permission to:

  • See your email address, so we know which Google account was connected.
  • See the list of your calendars, so you can choose which ones count toward your busy time and which one bookings are written to.
  • View and edit events on your calendars. We read events to work out when you are busy, and we create, update and delete the events for bookings made through RuboCal, including their Google Meet links and the invitation to the guest.

When reading your calendar we ask Google only for each event's times, its status, whether it marks you as busy, and the email addresses and replies on its guest list, which we use for one thing: an invitation you declined does not block your time. We do not request event titles, descriptions or locations, we do not store guest lists, and nothing about your events is sent to a guest except which start times are open.

We store the start and end times of your busy periods, refreshed regularly, and the access and refresh tokens Google issues, encrypted. The only events we change are the ones RuboCal created for your bookings.

We use Google user data only to provide these features. We do not use it for advertising, we do not sell it, we do not use it to develop or train AI or machine-learning models, and no person at Rubotic reads it unless you ask us to for support, it is needed for security, or the law requires it. It is shared only with the service providers listed below, who process it on our behalf.

RuboCal'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.

Disconnecting a Google account in Calendars deletes its tokens from RuboCal and asks Google to revoke the permission. You can also remove RuboCal at any time from your Google Account's connections page.

Other calendars

You can add a calendar by its feed address (an .ics URL from iCloud, Outlook and others). We store that address encrypted, download the feed regularly, and keep only the busy times worked out from it. Feeds are read-only: we never write to them.

What we collect from guests

  • What you enter when booking: your name, email address, time zone, any notes, a phone number if the host asks for one, and your answers to the host's questions.
  • How you arrived: the page that sent you and any campaign tags (UTM parameters) in the link, when present.
  • The booking itself: the time, its status, and any reschedule or cancellation, with the reason if you give one.

This goes to the host you are booking with: in their RuboCal inbox, in emails to them, on the event in their calendar, and to any systems they have connected (webhooks, or a page they send you to after booking, which receives your name and email address). The host decides what to do with it from there; ask them about their own practices.

We email you the confirmation, reminders and any changes to your booking. We do not add you to a mailing list.

Technical data, cookies and storage

  • IP addresses are used to limit abuse of the booking pages. We keep them only as one-way hashes in short-lived counters. Our hosting provider also keeps standard request logs.
  • Sign-in is kept in your browser's storage by Firebase Authentication. Connecting Google Calendar sets one cookie for a few minutes to complete the connection safely.
  • Your theme preference (light or dark) is saved in your browser.
  • Some booking pages may show a Cloudflare Turnstile check to keep bots out, which is run by Cloudflare under its own privacy policy.

There are no advertising or cross-site tracking cookies.

Who processes it for us

  • Google (Firebase and Google Cloud): hosting, the database, sign-in, and the Google Calendar and Meet features.
  • Cloudflare: domain name service, and Turnstile where it is switched on.
  • An email delivery provider, to send booking emails.

We may also disclose information when the law requires it, or to protect the service and the people using it.

How long we keep it

Host accounts, booking links and bookings are kept until the host deletes them or asks us to. Calendar busy times are replaced each time they are refreshed and removed when the calendar is disconnected. Abuse-prevention counters expire within hours.

Your choices

  • Guests can cancel or reschedule from the link in their confirmation email.
  • Hosts can edit or remove links, calendars and webhooks in the app at any time.
  • Anyone can ask for a copy of their information, a correction, or its deletion (including a whole host account) by writing to privacy@rubocal.com. If you are a guest, we may involve the host you booked with, since the booking is also their record.

Children

RuboCal is not directed at children under 13, and we do not knowingly collect their information.

Changes

If this policy changes, the new version is posted here with a new effective date.

Contact