Privacy Policy

1. Who this applies to

Three groups of people meet the App, and this policy covers all of them:

• Administrators — the monday.com admins who install the App, connect a board, and manage the settings.
• Hosts — the people in your monday.com account who publish a booking page and connect their Google Calendar or Microsoft 365 (Outlook) calendar.
• Guests — the people outside your account who open a booking page and book a meeting. Guests never need an account with us or with monday.com.

It also covers visitors to this website. It does not cover monday.com, Google, or Microsoft themselves — each has its own privacy policy that governs the data in your account there.

2. Our principles

• Least data. We ask for the narrowest calendar access that lets us find free time and add a meeting. Your other events are used only to find when you are busy, and are never shown to guests.
• Your board is the record. Every booking is written to your own monday.com board. We keep our own copy only so the page can show availability, so a guest can reschedule or cancel, and so a failed board write can be retried.
• No advertising, no resale, no AI training. Ever.
• Deleted when you leave. Uninstalling the App removes your calendar access immediately, and your data is deleted within 10 days (Section 10).

3. Definitions

• “Customer”, “you” — the organisation whose monday.com account the App is installed on.
• “Booking page” — a public page at meet.pluginpro.io where a guest picks a time. Personal pages belong to one host; team pages offer a time with any available host.
• “Booking” — one meeting a guest has booked: who, when, which meeting type, and the answers to any questions the Customer added to the form.
• “Calendar credential” — the OAuth token a host grants us to read their free/busy time and add the meeting to their calendar.
• “Personal data” — any information relating to an identified or identifiable person, as defined in the GDPR and similar laws.

4. Our role (controller & processor)

For the bookings, guest details, host details and settings the App processes for you, you are the controller and we are the processor: we process that data on your instructions, as set by how you configure the App and this policy. For the small amount of data we need to run the service itself — the record that your account installed the App, support messages you send us, and the technical logs of this website — we are the controller.

5. Information we process

The table lists every category of data the App handles and whether it is stored. Where we say stored, the data lives in our database on Railway (Section 8). Where we say read, not stored, the App looks at it in the moment and keeps nothing.

Category	Examples	Source	Stored by the App?
Installation record	Your monday.com account id and name, the workspace and board the App writes to, and the ids of the admins who installed or authorized it	monday.com OAuth	Stored
monday.com access token	The token that lets the App write bookings to your board and read your account's member list	monday.com OAuth	Stored, encrypted with AES-256-GCM; never logged, never sent to the browser
Hosts	Each host's monday.com user id, name, email address, profile photo and time zone, their working hours, and which meeting types they offer	monday.com (member list), Google (the photo of a host who connects Google Calendar) and the host's own settings in the App	Stored
Calendar credentials	The Google or Microsoft OAuth tokens a host grants so we can read free/busy time and add the meeting	Google / Microsoft OAuth	Stored, encrypted with AES-256-GCM; never logged, never sent to the browser
Calendar free/busy time	Whether a host is free or busy at a given time	Google Calendar / Microsoft Graph API	Read, not stored (except the copy of Google Calendar events in the next row)
Copy of Google Calendar events	For hosts who connect Google Calendar: their events for the next 3 months — start and end time, title, description and location, but not the attendees. The booking engine keeps this copy so booking pages load fast. It uses it only to find busy times and never shows it to guests	Google Calendar API	Stored; each event is deleted within a day after it ends, and all of them when the host disconnects their calendar
Guest details	The guest's name, email address, time zone, anything they typed in the notes field, and their answers to any extra questions the Customer added to the booking form	The guest, on the booking page	Stored, as part of the booking
Bookings	Meeting type, start and end time, the host, the guest details above, the video-meeting link, and the booking's status (upcoming, rescheduled, cancelled)	Created by the App when a guest books	Stored, and written to your monday.com board
Board link	The id of the monday.com item each booking was written to, so a reschedule or cancellation updates the same item	Generated by the App	Stored
Configuration	Meeting types, questions on the booking form, your logo and brand colours, team-page settings, and which board columns bookings map to	Set by the Administrator in the App	Stored
Usage counts	The number of bookings per month and the number of hosts, used to apply the free plan's limits	Generated by the App	Stored
Operational log	A short log of what the App did — booking ids, board item ids, and error codes. It never records guest details, calendar contents or tokens	Generated by the App	Stored for 65 days (Section 10)
Support communications	The contact details and contents of messages you send us	You	Kept only as long as needed to handle your request

We do not intentionally collect special categories of personal data (health, biometric, racial, political or similar), and we ask that you do not add booking-form questions that request such data.

6. Calendar & booking data — what the App reads and writes

The App asks each platform for the least access that does the job:

• Google Calendar — calendar.readonly to read the host's events and free/busy time, calendar.events to add, update and remove the meeting the guest booked, and userinfo.profile to show the host's Google profile photo on their booking page. When a meeting type uses Google Meet, the meeting link is created on the host's own Google account as part of that event. We do not request access to Gmail, Drive, Contacts, or any other Google service.
• Microsoft 365 / Outlook — Calendars.Read and Calendars.ReadWrite to read free/busy time and add, update and remove the booked meeting; User.Read to identify the connected account; and offline_access so the connection keeps working without asking the host to sign in again. When a meeting type uses Microsoft Teams, Outlook creates the Teams link on the host's own account as part of that event; the App asks for no separate Teams permission.
• monday.com — the App reads your account's member list so hosts can be picked, creates and reads the Meetings board it writes to, creates and updates items on that board, adds a webhook to each Meetings board it uses so a change made on the board can be reflected back, sends monday.com notifications to admins and hosts, and adds short updates to booking items. It reads workspace names so the board goes in the workspace you chose. To find a Meetings board made from the App's template, it reads board column titles, never items: until the App has a Meetings board (for example when an admin first authorizes), the column titles of up to 100 boards in your account; and when the App is opened on a board or dashboard, the names and column titles of up to 50 boards in that workspace. It does not read the items of any other board.

What crosses between the platforms:

• To your monday.com board — every booking, as one item: guest name and email, time, meeting type, host, video link, status, and the answers to your form's questions, mapped to the columns you chose. A reschedule or cancellation updates the same item.
• To the host's calendar — the booked meeting, with the guest as an attendee, so it blocks the host's time and the guest gets the invitation.
• To the guest — a confirmation email with a calendar file and the video link, sent from bookings@send.pluginpro.io, with replies going to the host's own monday.com email address. Hosts are not emailed by us; their calendar invitation is the notification.

Content the App has written into monday.com or a calendar stays there under that platform's own retention. Deleting a booking in the App does not delete the board item or the calendar event, and the other way round.

7. Why we process it & legal bases

• To run the booking pages you publish — showing a guest when a host is free, recording the booking, adding it to the calendar, writing it to your board, and emailing the guest a confirmation. Legal basis: performance of a contract; and, where we act as processor, the controller's instructions.
• To let a guest manage their booking — reschedule or cancel from the link in their confirmation. Legal basis: performance of a contract with the Customer; the guest's own request.
• To authenticate with monday.com, Google and Microsoft on your behalf using the stored tokens. Legal basis: performance of a contract.
• To apply your plan's limits — counting bookings and hosts. Legal basis: performance of a contract.
• To operate, secure, troubleshoot and improve the service, including keeping the operational log, retrying a failed board write, and preventing abuse of public booking pages. Legal basis: legitimate interests.
• To provide support. Legal basis: performance of a contract / legitimate interests.
• To comply with legal obligations where applicable. Legal basis: legal obligation.

Where we rely on legitimate interests, we have weighed them against your rights and freedoms. We do not use your data for advertising or to train AI models, and we do not sell or “share” it for cross-context behavioural advertising as those terms are defined under applicable law.

8. Who else touches it — sub-processors

These are the services that process data for the App, each under its own data-protection obligations. The App does not integrate any analytics, advertising, error-tracking, marketing-email, or AI/large-language-model services.

Recipient	Role	What it processes
Railway (Railway Corp., United States)	Hosts the App's servers, the booking pages, the database and its backups, all in Railway's EU West region (Amsterdam, Netherlands)	Everything marked “stored” in Section 5, at rest and in transit
monday.com (monday.com Ltd.)	The platform holding your Meetings board; hosts the App's settings screen inside monday.com; the marketplace the App is sold through	Bookings the App writes to your board; your account's member list, which the App reads
Google (Google LLC)	Calendar provider for hosts who connect Google Calendar; creates Google Meet links	The host's free/busy time and the booked meeting, in the host's own Google account
Microsoft (Microsoft Corporation)	Calendar provider for hosts who connect Microsoft 365 / Outlook; creates Microsoft Teams links	The host's free/busy time and the booked meeting, in the host's own Microsoft account
Resend (Resend, Inc., United States)	Sends the guest's confirmation, reschedule and cancellation emails from its eu-west-1 region (Ireland)	The guest's email address and the email content: meeting time, host name, video link, calendar file

These are all the internet domains the App connects to, and why:

Domain	Used by	Why
api.monday.com	App backend	Read and write the Meetings board, read users and workspaces, send notifications and item updates (monday.com API)
auth.monday.com	App backend	monday.com sign-in (OAuth), token refresh and revocation
files.monday.com, cdn1.monday.com	App backend and the App's screens inside monday.com	Users' profile photos, shown in Settings; the App backend copies a host's monday photo to their booking page
lh3.googleusercontent.com	The guest's browser, on the booking page	The host's Google profile photo. When a host connects Google Calendar, it replaces their monday photo on their booking page
accounts.google.com	The host's browser, when connecting a calendar	Google sign-in screen, to connect Google Calendar
oauth2.googleapis.com	Booking engine	Google sign-in tokens: get, refresh and revoke
www.googleapis.com	Booking engine	Google Calendar: free/busy times, the booked event and the Google Meet link
fonts.googleapis.com, fonts.gstatic.com	The App's screens inside monday.com, and this website	Web fonts only; no cookies, no tracking
login.microsoftonline.com	The host's browser and the booking engine	Microsoft sign-in screen and tokens, to connect Outlook
graph.microsoft.com	Booking engine	Outlook calendar: free/busy times, the booked event and the Microsoft Teams link
smtp.resend.com	Booking engine	Send the guest's confirmation, reschedule and cancellation emails
api.github.com	App backend	Once a day, check the open-source booking engine for security fixes. No customer data is sent
backboard.railway.com	App backend	Every 15 minutes, copy our own service logs from Railway, our host, to our private storage on Railway, where they are kept for 65 days (Section 10). No customer data is sent
booking.pluginpro.io, meet.pluginpro.io	Our own servers, hosted on Railway	The App's backend and its screens inside monday.com (booking.pluginpro.io); the booking pages and the booking engine (meet.pluginpro.io)

The guest booking page loads everything from meet.pluginpro.io, with one exception: for a host who connected Google Calendar, the guest's browser loads the host's Google profile photo from lh3.googleusercontent.com. Like any image request, this gives Google the guest's IP address and browser type, but no booking data.

Google serves the web fonts used by this website and by the App's screens inside monday.com, and so receives the technical request data any web-font fetch involves — the IP address and browser type of the device loading the page. It receives no booking, calendar or account data through that, and sets no cookies. Cloudflare serves this website (pluginpro.io) and its DNS, and forwards our support mailbox. The App and the booking pages do not go through Cloudflare; their traffic goes directly to Railway.

We may also disclose data where reasonably necessary to comply with law or legal process, to enforce our terms, or to protect the rights, safety and security of our users, the public or the service. If we are ever involved in a merger, acquisition, financing or sale of assets, data may be transferred as part of that transaction, subject to this policy and applicable law.

9. International data transfers

PluginPro is established in Poland (European Union). The App, the booking pages, the database and its backups are hosted on Railway in its EU West region (Amsterdam, Netherlands), and Resend sends email from its eu-west-1 region (Ireland). Railway and Resend are companies based in the United States, so staff of those providers may access data from outside the EEA, for example for support or security. Where that is an international transfer of personal data, we and our providers rely on appropriate safeguards — the European Commission's Standard Contractual Clauses and the UK International Data Transfer Addendum — to protect your data to a standard consistent with your home jurisdiction. Google and Microsoft process calendar data wherever the host's own account is hosted, under their own terms. Contact us for more information about these safeguards.

10. How long we keep it

• While the App is installed — bookings, hosts, configuration, tokens and usage counts are kept so the service works. The copy of a host's Google Calendar events (Section 5) reaches 3 months ahead; each event is deleted within a day after it ends, and all of them when the host disconnects their calendar.
• Logs — our app logs keep only ids, no personal data. We keep a copy for 65 days, then delete it. The database's own logs are not copied.
• When a host is removed — their booking pages are taken offline at once. Their meeting types and working hours are kept, so making them a host again brings the pages back. Their calendar connection stays until they press Disconnect on the Home tab, or until the App is uninstalled.
• When you uninstall — immediately, the App revokes its monday.com access, takes all your booking pages offline, stops calendar updates, revokes Google Calendar access and deletes every calendar connection (Google and Microsoft). The other records — bookings and guest details, hosts, meeting types, working hours, settings and the installation record — are kept for 1 to 2 days, so a reinstall within one day restores your setup, and are then deleted.
• Backups — each backup is deleted 7 to 8 days after it is made. So the last copy of your data is gone within 10 days of the uninstall.
• On request — email konrad@pluginpro.io and we delete or export your data at any time, without waiting for uninstall.

Items already on your monday.com board and events already on a host's calendar are yours, and stay there under those platforms' retention. We may retain limited information for longer where required to comply with legal obligations or to resolve disputes.

11. How we protect it

• Every OAuth token — monday.com, Google and Microsoft — is encrypted with AES-256-GCM before it is written to the database, is never logged, and is never sent to the browser.
• Data is isolated by monday.com account: every read and write is scoped to the installing account, and a host's calendar is read only for that host's own pages.
• The App's settings screen inside monday.com verifies the signed session monday.com issues for every request, and only account admins can change settings.
• The public booking page shows only what a guest needs: the host's name and photo, the meeting types offered, and free time slots. It never reveals the host's other events, email address, or calendar.
• All traffic uses HTTPS/TLS; the App's domains enforce it.
• The operational log records ids and error codes only — never guest details, calendar contents or tokens.
• Access to production systems is limited to the sole operator and protected by multi-factor authentication.

If we become aware of a personal-data breach affecting your information, we will investigate promptly and notify affected parties and authorities where and as required by law. No method of transmission or storage is completely secure, so while we work hard to protect your data, we cannot guarantee absolute security.

12. Your rights & choices

Depending on where you live, you may have the right to access, correct, delete, restrict or object to the processing of your personal data, to receive a copy in a portable format, and to withdraw consent where processing is based on consent. Guests: your booking confirmation carries links to reschedule or cancel; for anything else, contact the organisation you booked with — they control that data — or contact us and we will pass the request on and assist. Hosts: you can disconnect your calendar at any time with Disconnect on the App's Home tab, which deletes the credential. Administrators: you can remove hosts, delete meeting types, and uninstall the App from monday.com at any time. To exercise any other right, email konrad@pluginpro.io; we will respond within the time required by applicable law and may need to verify your identity first.

13. EEA & UK disclosures (GDPR)

The controller for the data we process on our own account is PluginPro, Konrad Kwiatkowski, Poland (contact in Section 20). Legal bases are listed in Section 7. Transfers outside the EEA and UK are described in Section 9. You have the right to lodge a complaint with a supervisory authority; in Poland that is the Prezes Urzędu Ochrony Danych Osobowych (uodo.gov.pl), and in the UK the Information Commissioner's Office (ico.org.uk). Where we act as your processor, we process personal data only on your documented instructions, keep it confidential, apply the security measures in Section 11, use only the sub-processors in Section 8, assist you with data-subject requests, and delete it as described in Section 10. Uninstalling the App is your instruction to delete.

14. California disclosures (CCPA/CPRA)

In the past twelve months we have collected the categories of personal information listed in Section 5, for the purposes in Section 7, and disclosed them to the service providers in Section 8. We do not sell personal information and do not share it for cross-context behavioural advertising, and we have no actual knowledge of selling or sharing the personal information of anyone under 16. California residents may request access to, deletion of, or correction of their personal information, and will not be discriminated against for doing so. Contact details are in Section 20. Where we act as a service provider to a Customer, we use personal information only to provide the App to that Customer.

15. Your responsibilities as the customer

You decide what your booking pages ask guests, who in your account becomes a host, and what your board columns hold. You are responsible for having a lawful basis for the guest data your pages collect, for telling guests how you will use it (a link to your own privacy notice on the booking form is a good idea), for not adding questions that request sensitive data, and for keeping your own records of bookings — your monday.com board is the system of record, not the App.

16. Automated decisions & “Do Not Track”

The App makes no decisions with legal or similarly significant effects about anyone. Team pages assign a booking to whichever host is free, in rotation — that is scheduling, not profiling. This website and the booking pages do not respond to browser “Do Not Track” signals because they do not track visitors across sites in the first place.

17. Children

The App is a business tool and is not directed at children. We do not knowingly collect personal data from anyone under 16. If you believe a child has provided us with personal data, contact us and we will delete it.

18. Cookies & technical storage

We use no tracking cookies. This website, the App and the booking pages run no analytics, ad or tracking scripts, and this website sets no cookies. The App's screens inside monday.com set no cookies; they use the session monday.com provides. The App uses only the cookies and browser storage it needs to work:

• While an admin authorizes the App — booking.pluginpro.io sets one cookie, pp_oauth_state. It is a security check for the monday.com sign-in. It is HttpOnly and Secure, and it expires after 10 minutes.
• On the booking page — meet.pluginpro.io uses short session cookies. They protect the booking form against fake requests (CSRF) and hold the time a guest picked, so two guests cannot book the same time. They are Secure and end when the browser closes. The sign-in system of the booking engine also sets two of these cookies on every booking page: __Secure-next-auth.csrf-token (a random security token) and __Secure-next-auth.callback-url (this site's address). Guests never sign in, and these two cookies hold no personal data.
• When a host connects a calendar — booking.pluginpro.io sets two cookies, pp_connect and pp_hop. They make sure the calendar is connected in the same browser that pressed Connect. They are HttpOnly and Secure, and they expire after 5 minutes. Then meet.pluginpro.io sets a sign-in cookie for that step. It is HttpOnly and Secure, and it ends 30 minutes after it was last used.
• Browser storage on the booking page — the booking page remembers the guest's time zone and 12-hour or 24-hour clock choice in the browser's local storage, so the next booking page shows times the same way. The sign-in system of the booking engine also keeps one technical entry there, nextauth.message, so that open tabs stay in step; it holds no personal data. This storage stays until the guest clears their browser data, and it is not used to track anyone.

These are all strictly necessary for the service, so we show no cookie banner and there is nothing to opt out of.

19. Changes to this policy

We may update this policy as the App or the law changes. The effective date at the top always shows the current version. For material changes we will give notice through the App or by email to the Administrator before they take effect. Continued use after the effective date means you accept the updated policy.

20. How to contact us

PluginPro · Konrad Kwiatkowski · Poland
konrad@pluginpro.io
We reply the same working day.

See also our Terms of Service, pricing and support.