Your data stays on your site.

01Who we are

Calendar by J6 Venture ("the plugin", "we", "us") is a WordPress booking plugin published by J6 Venture. It gives a website owner ("the operator") a booking page where their invitees pick a time for a meeting, and it connects to the operator's Google Calendar or Microsoft Outlook to read availability and place events.

In data-protection terms the operator is the controller of the bookings taken on their site. The plugin is the tool they use; J6 Venture builds and maintains that tool.

02Two editions, one policy

The plugin ships in two editions that differ only in how the calendar connection is authorised. What each touches is otherwise identical.

• Self-hosted. Runs entirely on the operator's own WordPress site, using OAuth credentials the operator creates in their own Google Cloud or Microsoft Azure account. No J6 Venture server is involved at any point.
• Connect (managed). The operator connects Google or Outlook in one click. The sign-in handshake is brokered by a stateless J6 Venture Cloudflare Worker that holds only the application's own secret. The broker stores no user data and no tokens; the resulting access is handed straight to the operator's own site.

03What data we access

From the connected calendar account (the operator)

• Basic profile: name, email address and profile picture, used to label the booking page and identify the connected account.
• Calendar free/busy times, used to work out which slots to offer.
• Permission to create, update and cancel the specific calendar events that bookings generate, including the online-meeting link on each.

From invitees (the people booking)

• The name and email they enter, the time they choose, and any answers to booking questions the operator has set.
• This is stored in the operator's own WordPress database and used to create the booking, send confirmations and reminders, and place the calendar event.

04Google user data

When an operator connects Google, the plugin requests only the scopes it needs to schedule: their basic profile (openid, email, profile) and Google Calendar access (calendar.events and calendar.freebusy) to read availability and manage the events bookings create, including the Google Meet link on each. It requests no access to Gmail, Drive, Contacts or any other Google service.

Google Calendar tokens obtained during connection are stored on the operator's own site (see Where data is stored) and used solely to keep the calendar in sync. They are removed when the operator disconnects or uninstalls.

05Microsoft user data

When an operator connects Microsoft Outlook, the plugin requests only: their basic profile (User.Read, openid, email, profile), calendar access (Calendars.ReadWrite) to read availability and manage booking events, online-meeting access (OnlineMeetings.ReadWrite) to attach a Microsoft Teams link, and offline_access so the connection can refresh without repeated sign-in. It requests no access to Outlook mail, files or any other Microsoft service.

Microsoft tokens are stored on the operator's own site and used only to keep the calendar in sync. They are removed on disconnect or uninstall.

06What we never access

• We never read or send email on your behalf. No Gmail and no Outlook mail scopes are requested.
• We never touch files, documents, contact lists, or any calendar or account beyond what scheduling requires.
• We build no advertising profiles and run no third-party trackers on the booking page beyond any analytics the operator chooses to switch on.

07Where data is stored

Bookings & answers

In the operator's own WordPress database, on the operator's own hosting. J6 Venture does not receive a copy.

Calendar tokens

On the operator's own site, held against the connected host record and used only to sync the calendar.

Connect broker

Stateless. It brokers the one-time sign-in and stores no tokens and no user data.

Calendar providers

The events themselves live in the operator's Google or Microsoft calendar, governed by Google's and Microsoft's own privacy policies.

Infrastructure

The J6 Connect service runs on Cloudflare's serverless platform (Cloudflare Workers), which processes the sign-in request in transit only and stores nothing. See Cloudflare's privacy policy.

08Sharing & selling

We do not sell personal data, and we do not share it with third parties for their own purposes. Data moves only where it must to perform the scheduling the operator and invitee asked for, namely to Google or Microsoft to place the calendar event, or where the law requires it. Confirmation and reminder emails are sent through the operator's own WordPress mail setup.

09Retention & deletion

• Calendar tokens are deleted from your WordPress site immediately when a host disconnects their calendar or is removed from your team, and are dropped entirely if you uninstall the plugin with “remove all data” enabled.
• The J6 Connect service is stateless and retains no tokens or calendar data at any time.
• Booking records stay in the operator's database until the operator deletes them. An invitee who wants a booking removed should contact the operator whose page they booked on, or reach us at the address below and we will route the request.

10Security

Connections use OAuth 2.0, so the plugin never sees or stores a calendar-account password. Tokens are held on the operator's own site and transmitted over encrypted (HTTPS) connections. The Connect broker holds only the application secret and keeps no user data. No method of storage or transmission is perfectly secure, but we design to request the least access necessary and to keep sensitive material off J6 Venture servers entirely.

11Your rights

Depending on where you live, you may have the right to access, correct, export or delete personal data held about you, and to withdraw a connection at any time. Operators can act on these directly from their WordPress dashboard, which includes built-in GDPR export and erase. Invitees can exercise them through the operator, or by contacting us to be routed to the right operator.

12Contact

Questions about this policy, or about data handled by Calendar by J6 Venture:

If we make material changes to this policy we will update the date at the top of this page and, where appropriate, note the change here.