Skip to content

Rallly is an open-source scheduling and collaboration tool designed to make organizing events and meetings easier.

📝 Disclose data protection and Google Calendar use in the privacy policy (#3394)

Luke Vella78d11db1d145
diff --git a/apps/landing/src/app/[locale]/(main)/privacy-policy/page.tsx b/apps/landing/src/app/[locale]/(main)/privacy-policy/page.tsx
index 3e88425a0..c07c76404 100644
--- a/apps/landing/src/app/[locale]/(main)/privacy-policy/page.tsx
+++ b/apps/landing/src/app/[locale]/(main)/privacy-policy/page.tsx
@@ -9,7 +9,7 @@ export default async function PrivacyPolicy() {
cacheLife("max");
return (
<Section>
- <LegalPageLayout title="Privacy policy" lastUpdated="2026-09-27">
+ <LegalPageLayout title="Privacy policy" lastUpdated="2026-09-29">
<p>
At rallly.co, we take your privacy seriously. This privacy policy
explains how we collect, use, and disclose your personal data, and
@@ -108,6 +108,15 @@ export default async function PrivacyPolicy() {
profile picture to create and identify your account.
</p>
+ <p>
+ If you connect Google Calendar, Rallly reads the list of calendars in
+ your Google account, with each calendar&apos;s name, time zone and
+ whether you can add events to it, so you can see and choose your
+ calendars in your settings. We store that list for as long as the
+ calendar is connected. Rallly does not read, create or change events
+ in your calendars through this connection.
+ </p>
+
<p>
If you connect Google Meet, Rallly uses the permission to create Meet
meeting spaces (<code>meetings.space.created</code>) only to create a
@@ -120,24 +129,30 @@ export default async function PrivacyPolicy() {
</p>
<p>
- When you connect, Google also shares your Google account id, email
- address and basic profile (name and profile picture). We do not store
- your name or profile picture. We store your Google account id and
- email address to identify the connection and show which account is
- connected, and the OAuth tokens Google issues, encrypted at rest, so
- Rallly can create meetings without asking you to sign in each time. We
- use this data only to identify the connected account and to create
- meetings for you as the organizer. We do not sell Google user data,
- use it for advertising, use it to train AI models, or share it with
- third parties except as needed to provide the service.
+ When you connect Google Calendar or Google Meet, Google also shares
+ your Google account id, email address and basic profile (name and
+ profile picture). We do not store your name or profile picture. We
+ store your Google account id and email address to identify the
+ connection and show which account is connected, and the OAuth tokens
+ Google issues, encrypted as described in{" "}
+ <a href="#data-protection">How we protect your data</a>, so Rallly can
+ act for you without asking you to sign in each time. If you connect
+ the same Google account for both, the two connections share one set of
+ tokens. We use this data only to identify the connected account, to
+ show your calendars and to create meetings for you as the organizer.
+ We do not sell Google user data, use it for advertising, use it to
+ train AI models, or share it with third parties except as needed to
+ provide the service.
</p>
<p>
- When you disconnect Google Meet in your settings, we delete the stored
- account details and tokens. When you delete your Rallly account, we
- delete them along with your events, including the details of meetings
- Rallly created. You can also revoke Rallly&apos;s access at any time
- at{" "}
+ When you disconnect Google Calendar in your settings, we delete the
+ connection and the list of calendars we stored. When you disconnect
+ Google Meet, we delete the connection, and we delete the stored tokens
+ unless your Google Calendar connection on the same Google account
+ still uses them. When you delete your Rallly account, we delete all of
+ it along with your events, including the details of meetings Rallly
+ created. You can also revoke Rallly&apos;s access at any time at{" "}
<a href="https://myaccount.google.com/permissions">
myaccount.google.com/permissions
</a>
@@ -232,6 +247,39 @@ export default async function PrivacyPolicy() {
Meetings Rallly already created stay in your Microsoft account.
</p>
+ <h2 id="data-protection">How we protect your data</h2>
+
+ <p>
+ We use the following measures to keep your data, including the data we
+ receive from Google, Zoom and Microsoft, confidential and secure:
+ </p>
+
+ <ul>
+ <li>
+ Encryption in transit: all traffic to rallly.co, and between our
+ servers and the service providers listed below, is encrypted with
+ TLS (HTTPS).
+ </li>
+ <li>
+ Encryption of access tokens: the OAuth access and refresh tokens
+ that Google, Zoom and Microsoft issue when you connect an account
+ are encrypted with AES-256-GCM by our application before they are
+ written to the database. The encryption key is kept separately from
+ the database, so a copy of the database alone does not reveal the
+ tokens.
+ </li>
+ <li>
+ Encryption at rest: our database and its backups are hosted by Neon,
+ which encrypts all stored data at rest.
+ </li>
+ <li>
+ Restricted access: access to our production systems and data is
+ limited to the people who need it to operate and support the
+ service, and data from connected accounts is used only for the
+ purposes described in this policy.
+ </li>
+ </ul>
+
<h2>Content moderation</h2>
<p>