Privacy Policy

Last updated: 2026-10-17

Supaplan ("Supaplan", "we", "us", or "our") respects your privacy. This Privacy Policy explains how we collect, use, store, and protect personal data when you use the Supaplan mobile application (iOS and Android) and related web-based features used for scheduling and sharing events and Supaplan's messaging-channel features, such as the Supaplan Telegram bot (together, the "Service").

This Policy applies globally, including users in the European Union (EU) and European Economic Area (EEA).

If you have any questions, contact us at [email protected].

1. Scope of This Policy

This Policy applies to:

The Supaplan mobile app
Supaplan web pages used for event sharing and scheduling
Supaplan's messaging-channel features, such as the Supaplan Telegram bot
Communications with Supaplan support

It does not apply to the independent processing by third-party services you may access via Supaplan, including Telegram, WhatsApp and the calendar providers you connect.

2. Personal Data We Collect

2.1 Data You Provide

Account information (name, email address, authentication identifiers)
Preferences and settings
Communications with customer support
Content you intentionally enter into the app (for example notes or requests)
When you link a messaging channel (Telegram or WhatsApp), the account identifier and the profile details that channel provides (for Telegram: username, first name and language setting)
When you upload an image, video, or file to the assistant, the attachment bytes (or a browser-compatible image derivative), filename, MIME type, and size. We retain these in our preview store to show your attachment preview and support the assistant action you requested, with access limited to your authenticated account. For image and PDF attachments, uploaded files (including original uploads and unvalidated or rejected files) and OCR text are also processed and retained as part of assistant execution traces in Langfuse until account erasure.

2.2 Contacts and Calendar Data (Opt-In Only)

With your explicit consent, Supaplan may access:

Contacts (names, email addresses, phone numbers)
Calendar events, availability, and related scheduling metadata

Purpose

This data is used strictly to provide core, user-visible functionality, including:

Scheduling and coordination
Availability checks
Creating, updating, and managing events
Sharing event information with selected participants

Important Commitments

Contacts and calendar data are never sold
Never used for advertising or marketing purposes
Never shared with data brokers or resellers
Never used to train, fine-tune, or improve generalized AI or machine learning models
Used only to provide the features you explicitly enable and use

You may revoke access at any time through your device settings or within the app.

2.3 Connected Telegram Account (Opt-In Only)

If you connect your Telegram account, Supaplan can read messages from the conversation in which you ask it to, only when you mention the Supaplan bot there and never in the background (see §5). This includes messages written by other participants in that conversation. The text of those messages is not stored by Supaplan (see §7).

The login session that lets Supaplan access your Telegram account is stored encrypted (see §10). You can disconnect your Telegram account at any time within the app.

3. Automatically Collected Data

We may collect:

Device and log data (IP address, operating system, app version)
Approximate location (derived from IP address)
Usage analytics (feature usage, performance metrics, crash reports)

This data is used for security, reliability, and service improvement.

3.1 Product Analytics on the Calendar App

When you are signed in to the Supaplan calendar app (/cal/*), we use Mixpanel to record product-usage events such as page views and onboarding milestones.

Processor: Mixpanel, Inc. (United States), acting as our data processor. Cross-border transfers are covered by the EU Standard Contractual Clauses described in §8.
Residency: Mixpanel data is processed on Mixpanel's EU infrastructure (api-eu.mixpanel.com).
Identifier: Mixpanel events are tied to your Supaplan user ID. The Mixpanel People profile mirrors your Supaplan profile (email, first / last name, avatar URL, timezone, language, time-format preference, account-creation date) and your subscription state (plan tier — free / trial / paid — access flag, store, trial days remaining). We do not pass calendar event content, contact details, or message bodies to Mixpanel.
Scope: The Mixpanel SDK is not loaded on the marketing website, public booking pages, or pre-authentication screens — only after you sign in to the calendar app.
Storage: Mixpanel uses localStorage (not cookies) to persist its anonymous identifier and is reset when you sign out.
Retention: Event and People-profile data is retained for 5 years from the most recent event under Mixpanel's standard project policy. See §7 for what account deletion currently does and does not remove from Mixpanel.

Site-wide analytics (Google Analytics 4)

Across the Supaplan website we additionally load Google Analytics 4 to measure aggregate traffic. Details of the cookies it sets and how to opt out are in the Cookie Policy. The privacy-relevant facts:

Processor: Google Ireland Ltd. (EU) acting as joint controller with Google LLC (United States). Cross-border transfers are covered by the EU Standard Contractual Clauses described in §8.
Data: Pseudonymous client ID, page paths, referrer, device and browser metadata, and a truncated IP address. No Supaplan user identifier is sent to GA4.
Retention: GA4 event and user data retention in our property is set to 14 months; aggregated reports persist longer per Google's default reporting policy.
Scope: GA4 loads on all pages of the Supaplan website — including the authenticated calendar app, public booking pages, and shared-event pages — except on our internal staging environment, where it is disabled. Unlike Mixpanel, no Supaplan user identifier is passed to GA4.
Control: Analytics (both GA4 and Mixpanel) is on by default; a dismissible informational notice tells first-time visitors the site uses analytics, and signed-in users can stop it at any time through the account-level opt-out in Settings → Preferences, which disables GA at runtime, clears its cookies, and resets the Mixpanel identity. See the Cookie Policy for details.

We process personal data based on one or more of the following legal bases:

Performance of a contract (providing core functionality)
Consent (contacts, calendar access, notifications, connecting a messaging account)
Legitimate interests (security, fraud prevention, service reliability)
Legal obligations (compliance with applicable laws, regulations, court orders, subpoenas, or other legal processes; tax and accounting requirements; responding to law enforcement requests when required by law)

5. Use of AI and Automation

Supaplan uses automation and AI only to provide features that you actively and explicitly use, such as:

Scheduling suggestions
Time planning insights
Natural language interaction with your schedule

AI Data Handling Guarantees

AI features are user-initiated, in the app or in a messaging channel you connect (such as the Supaplan Telegram bot)
Personal data is processed only at the time of your request
We do not use your data to train, develop, or fine-tune generalized or third-party AI models
Data submitted during AI interactions is not retained for model training or improvement
All AI-initiated actions that modify your data (such as creating or updating events) require explicit user confirmation (human-in-the-loop)
AI processing is performed using Google Vertex AI with zero retention policy, ensuring that your data is not stored or retained by the AI service provider

AI is used solely to assist you in using the Service and does not operate autonomously on your data.

Telegram conversations (only if you connect your Telegram account): Supaplan reads recent messages (from the preceding 7 days, up to 1,000 text messages) from the conversation in which you ask Supaplan, only when you mention the Supaplan bot there, never in the background, including messages written by other participants, and sends them to Google Vertex AI to propose a calendar event. Nothing is created unless you confirm it. Supaplan does not store the text of those messages and does not send it to our assistant-trace, error-monitoring or logging services. How long Google keeps them is governed by Google's terms for that service, not by a commitment in this paragraph.

6. Payments

Payments are processed by the Apple App Store, the Google Play Store, or — for web subscriptions — RevenueCat Web Billing, which is powered by Stripe.

Supaplan does not collect, store, or process payment card information; card details are handled directly by these processors.

7. Data Retention

Personal data is retained for as long as your account is active
You may delete your account at any time directly within the app
After account deletion, the data you own — your account, calendars, notes, contacts, and the booking links, polls, and plans you created — is permanently deleted, except where retention is required by law, for the third-party processors described below (including assistant conversation history), or for a note or contact's AI-search copy as described below
Data you contributed to someone else's poll or plan is not deleted by your account deletion. If you responded to another user's poll or plan, the name, email, and any note, comment, or proposed option (a counter-proposed time, duration, or location) you submitted there are retained as that person's private record of the interaction; deleting your account severs the link to it but does not remove it. What appears on that item's public share link, if the owner has one active, is narrower and never includes your email or note: a poll's public link shows the participant's name, their vote on each option, and any comment they left, unless the poll owner has hidden participant responses, in which case nothing about participants is shown publicly; a plan's public link shows the participant's name, aggregate vote counts per option, and the value of any option they proposed, but never who cast which individual vote
A booking you make through someone else's scheduling link is their record, not yours. The name, email, phone, guests, and any note you provide when booking are stored against the link owner's account, because that is who the booking belongs to — deleting your own account does not touch it, since it was never tied to your account in the first place
An RSVP to someone else's shared event works the same way. The name and email you submit are written directly into that event on the organizer's calendar — outside our own database — because that is who the event belongs to; deleting your own account does not touch it
A note or contact's AI-search copy is not currently removed by account deletion. If a note or contact of yours was ever indexed to power AI-assisted search, a separate copy of its text — a note's full content, or a contact's name and details — is stored in our search index and can remain there indefinitely after you delete your account.
We do not retain personal data longer than necessary for the purposes described in this Policy

Payment, analytics, push-notification, error-monitoring, and assistant-history processors: Account deletion does not reach these processors the way it reaches our own database:

RevenueCat (subscription billing) retains your billing profile — email, display name, and other subscriber attributes we send it (such as an internal cross-tool identifier) — after account deletion; the profile itself is not deleted. Account deletion cancels only a Web Billing subscription; if you subscribed through the App Store or Play Store, deleting your account does not cancel it, and you will keep being charged until you cancel it directly in that store.
Mixpanel (analytics) is not currently asked to delete anything on account deletion, so your Mixpanel profile and event history are retained.
OneSignal (push notifications) is not purged by every deletion path: it is attempted only when deletion is started from the mobile app, on a best-effort basis that is not guaranteed to complete, and it is not attempted at all when you delete your account from the web — if you have used our mobile app, your OneSignal identity may remain there after deletion either way.
Sentry (error monitoring) is not purged on account deletion. Error reports captured while you used the app are keyed to your account identifier and are not erased or re-keyed when you delete your account.
Assistant conversation history (via Langfuse) has its deletion requested in the same request as your account deletion, for every account that has used the assistant at all. Langfuse removes that data asynchronously, and we do not wait to confirm it finished before your account deletion completes — so every such request is instead verified or finished by a manual follow-up step, with no automated retry and no fixed deadline guaranteed.

Assistant attachment previews and execution traces: Images, videos, and files uploaded to the assistant are retained in our preview store for up to 30 days to provide the preview and support the requested assistant action (or deleted earlier if you revoke the attachment or delete your account). For image and PDF attachments, uploaded files (including original uploads and rejected files) and OCR text are also retained within assistant execution traces in Langfuse and are scheduled for deletion upon account erasure as described above.

Telegram messages and connected Telegram accounts: Text read from your Telegram chats is used only to answer your request and is not stored by Supaplan. A draft event proposed from it, and any event you confirm, are kept like other assistant and calendar data. Messages you send directly to the Supaplan bot are handled like other assistant conversations, including the assistant conversation history described above. The login session for a connected Telegram account is stored encrypted until you disconnect it or delete your Supaplan account. When you disconnect, the session is revoked at Telegram and our stored copy is erased; if you delete your account without disconnecting first, our stored copy is deleted, but you should also end the session in Telegram's active-sessions settings.

Analytics retention windows:

Mixpanel event and profile data: 5 years from the most recent event (Mixpanel project default).
Google Analytics 4 event and user data: 14 months in our property; aggregated reports persist longer per Google's default reporting policy.

8. International Data Transfers

Your data may be processed in countries outside your country of residence. Where required, we rely on EU Standard Contractual Clauses (SCCs) or equivalent legal safeguards to protect your data.

The following processors involve a cross-border transfer to the United States, covered by the EU SCCs:

Mixpanel, Inc. — product analytics on the authenticated calendar app (see §3.1). EU residency endpoint, US-based processor.
Google LLC — Google Analytics 4 on the marketing site (see §3.1). EU sub-processor: Google Ireland Ltd.
Google LLC — Vertex AI for the AI features described in §5, with the documented zero-retention policy for prompts and outputs.
RevenueCat, Inc. — subscription billing (see §6, §7). US-based; SCCs relied on.
Stripe, Inc. — payment processing behind RevenueCat Web Billing (see §6). US-based; SCCs relied on.

When you message the Supaplan bot or connect your Telegram account, your messages also pass through Telegram under Telegram's own terms and privacy policy; Telegram is a third-party service (see §1), not a Supaplan processor.

Two further processors' transfer safeguards are not yet verified:

OneSignal (push notifications) is US-hosted, and its Data Processing Agreement and any EU-residency option are still under review — treat that transfer as unconfirmed pending that verification.
Langfuse (assistant conversation history / LLM observability, see §5 and §7) has a Data Processing Agreement and a data-residency location that are both still pending verification — treat that transfer as unconfirmed too.

9. Your Rights

You have the right to:

Access your personal data
Correct inaccurate data
Request deletion of your data (see §7 for what account deletion does and does not remove)
Restrict or object to processing
Request data portability
Withdraw consent at any time
Lodge a complaint with a supervisory authority

10. Security

We implement appropriate technical and organizational security measures to protect your data.

All service tokens and account credentials are stored encrypted using Google Cloud Key Management Service (KMS).

However, no method of transmission or storage is completely secure.

11. Changes to This Policy

We may update this Privacy Policy from time to time.

The most current version will always be available in the app and on our website.

12. Contact

📧 [email protected]