Privacy policy

Meetingboard is the meeting booking service at app.meetingboard.io and on the meetings. addresses of Frederike Falke's brands (for example meetings.nxtconnect.ai or meetings.pinpulse.io). It is operated by FalkeLabs LLC, New York, USA. This page says which personal data the service handles, why, and with whom it is shared. Questions and requests: hi@falkelabs.ai.

When you book a meeting

To book, you give your name, your email address and the time you chose, and, if you want to, a phone number, notes, answers to the meeting's questions and the email addresses of further guests. Your time zone is taken from your browser. We use this to:

• save the booking and put the meeting into the host's calendar, which also sends you the calendar invitation;
• send you and the host the confirmation, a reminder, and emails when the meeting is moved or cancelled;
• let you move or cancel the meeting with the private link in those emails;
• tell the team about the booking in our own systems: the brand's back office (the Brand Hub) and an internal Slack channel.

We do not sell these data, do not use them for advertising, and do not set tracking cookies on the booking pages.

If you have an account (hosts)

Accounts exist only for the people who take meetings; there is no public sign-up. For them we store the name, the email address, working hours, a one-time sign-in code while it is valid, and the secret of the authenticator app used for the second sign-in step (encrypted). A sign-in sets a cookie that lasts at most 12 hours.

Google calendar data

A host can connect a Google calendar. The service then asks Google for two permissions:

• See the calendar's events (calendar.readonly): to know when the host is busy, so that the booking pages only offer free times. For each event in the next 90 days the service keeps its start and end, its title, whether it is all-day, its place and whether it blocks time.
• Create and change events (calendar.events): to put a booked meeting into the host's calendar with a Google Meet link and the guest invited, and to move or remove it when the guest moves or cancels.

The keys that give the service this access are stored encrypted. The copied events are used only to work out free times and are deleted when the calendar is disconnected. When the dashboard assistant looks for free times, it receives the free times only, not the events. Google calendar data are not sold, not used for advertising, not used to train AI models, and not shared with anyone except as needed to run the features described here.

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

A host can disconnect a calendar in the dashboard at any time, or remove the service's access in the Google account at myaccount.google.com/permissions. Microsoft calendars are handled the same way.

Who else handles the data

The service runs on providers that process the data on our behalf:

• Vercel (hosting) and Supabase (database), in the USA;
• Resend (sending email) and Upstash (scheduled tasks such as reminders);
• Google and Microsoft, for the calendars that hosts connect;
• Slack, for internal messages about bookings and about problems with the service;
• Anthropic, for the assistant in the hosts' dashboard, which works with bookings, brands and meeting types; Anthropic does not use these data to train its models.

How long we keep data

Bookings are kept as long as they are needed for the business relationship and for our records, and are deleted on request where the law allows it. Copied calendar events are only kept for the coming 90 days and go when the calendar is disconnected. Sign-in codes expire after 10 minutes.

Your rights

You can ask which data we hold about you, have them corrected or deleted, object to their use, or receive a copy. If you are in the European Union or the United Kingdom, these rights come from the GDPR, and you may also complain to a data protection authority. Write to hi@falkelabs.ai.

Changes

When this policy changes, the new version is published on this page with a new date.