Privacy Policy

How we protect and handle your personal information

Last updated: October 8, 2026

At Radar AI, we take your privacy seriously. This privacy policy describes how we collect, use, and protect your personal information when you use our intelligent email alert system for school management.

Google API Limited Use Disclosure

The 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.

We Never Sell Your Data

Radar AI does not sell, rent, or trade customer service data. Data obtained from Google APIs (Gmail and Google Calendar), data received via WhatsApp (phone numbers, message content, images, and PDFs), and account details are used to provide the Radar AI service, not for advertising. With your separate Advertising consent, we share limited browser campaign-measurement events with Meta as described below.

Information We Collect

When you use Radar AI, we collect the following information:

  • Your Gmail account information (email address)
  • Access to your Gmail messages, including subject lines, sender information, and message content. Depending on the scan mode you choose, this is either limited to senders you have designated, or covers your full inbox so Radar can identify school-related emails automatically.
  • Your phone number for WhatsApp alert delivery
  • Email addresses you designate for monitoring (school communication sources), if you choose the "I'll pick the senders" scan mode
  • Inbound WhatsApp content you send to Radar's WhatsApp number: text messages, images, PDFs, and forwarded links. We store this content (sender phone number, message body, media attachments) so we can process it and reply to you. When you send a link, we fetch the page and extract its readable text so our AI can understand what you forwarded.
  • Google Calendar metadata (when you connect calendar sync): the calendar id you choose to sync to, the Google event ids of entries Radar has created on your behalf, and the sync status of each entry. We do not read other events from your calendar.

How We Use Your Information

We use the collected information to:

  • Monitor your specified school email sources for important communications
  • Analyze email content using AI to identify deadlines, events, and action items
  • Generate personalized action reports and summaries
  • Send timely WhatsApp alerts about important school matters
  • Process content you send to Radar's WhatsApp number — your text, images, PDFs and the readable text fetched from any links you forward — through our AI to extract events and deadlines, and reply to you on WhatsApp with a summary of what we found.
  • Create and update events on your Google Calendar, when you have connected calendar sync, so that Radar action cards show up alongside your other commitments. Radar only writes the events it has created; it does not modify or delete other events on your calendar.
  • Provide, maintain, and improve the Radar AI service for you as an authenticated user. Email content obtained from Gmail is used solely to deliver this service to you — it is never used to train or improve AI models, for advertising, or for any secondary purpose beyond providing the service.

How We Share Google User Data

Data obtained from Google APIs is shared with third parties only as strictly necessary to provide the Radar AI service, as described below. No Google user data is shared with advertising platforms, analytics providers, or any other third party not listed here.

Gmail — AI Providers

When Radar scans your Gmail, the body text of relevant emails is sent to Google Gemini (with OpenAI and Anthropic as automatic fallbacks) solely to extract school events, deadlines, and action items for your personal dashboard. No email content is retained by us beyond what is needed to display your events, and no email content is shared with any other party.

Shared with: Google Gemini (primary), with OpenAI or Anthropic as automatic fallbacks  ·  Purpose: School event extraction for your personal use only  ·  No other parties receive Gmail data.

Google Calendar — Write-Only Access

When you connect Google Calendar sync, Radar uses write-only access to create events on your calendar on your behalf. Radar reads no calendar content or metadata from your calendar; the only identifiers stored are the Google event IDs that Google returns when Radar writes events, so that Radar can update or track the entries it created. No calendar data is shared with any third party — not with AI providers, not with Twilio, and not with any advertising or analytics platform.

Shared with: Nobody  ·  Purpose: Writing Radar-generated events to your calendar only

What Is Never Shared

Google user data (Gmail content or Calendar metadata) is never shared with our messaging, payment, or invoicing providers, advertising platforms, analytics providers, or any other third party not listed above. It is never used for advertising targeting, sold to data brokers, or used to train or improve AI models.

Data Security

We implement industry-standard security measures to protect your personal information from unauthorized access, disclosure, alteration, or destruction. Your data is encrypted in transit and at rest. We use secure authentication protocols and regularly update our security practices.

Third-Party Services

We integrate with the following trusted services:

  • Google Services: We use Google's OAuth 2.0 for authentication, the Gmail API to read email content (from designated senders or your full inbox depending on your scan mode), and the Google Calendar API (calendar.events scope) to create and update Radar action cards on your calendar. Calendar writes are limited to events Radar itself has created — we do not read, modify, or delete other events on your calendar.
  • AI Providers: We use Google Gemini as our primary AI provider, with OpenAI and Anthropic as automatic fallbacks, for email analysis and event extraction. Email content shared with these providers is used solely to extract events for your personal dashboard and is subject to each provider's data processing terms.
  • A WhatsApp and SMS messaging provider: For delivering alerts and notifications to your phone, and for receiving messages, images, PDFs, and links you send to Radar's WhatsApp number. Media you send is downloaded over an authenticated connection so we can process it. This provider does not receive any Google user data.
  • A payment processor: For handling subscriptions and billing when you sign up for a paid plan. Payment details are handled directly by the processor — Radar does not store your card information.
  • An invoicing provider: For generating receipts and invoices for your subscription payments. Only your billing details and payment records are shared with this provider.

Please review each service's privacy policy for more information on how they handle your data.

Cookies & Tracking

We use cookies to make Radar AI work and, with your permission, to understand how it's used. Below is a summary of the cookies we set or may set in future.

Always On

Essential / Functional

  • Cookie name: session (Flask session cookie, which also carries CSRF state)
  • Purpose: Keeps you logged in, secures your session, and protects form submissions against cross-site request forgery (CSRF). It also retains first-touch signup campaign context, including a fixed approved landing-page label, through sign-in and checkout. Retaining this context does not send an analytics or advertising event without the relevant preference. Required for the service to function.
  • Duration: Up to 7 days
  • Can be disabled: No — disabling this cookie will prevent you from using Radar AI
Consent Required

Analytics

  • Cookie name: Set by analytics provider when enabled (e.g. _ga, _gid)
  • Purpose: Help us understand how users navigate the app so we can improve it. No personal data is sold. Analytics cookies operate entirely independently of Google API data — data obtained from Gmail or Google Calendar is never used for analytics.
  • Custom event providers: Google Analytics and, when enabled for the published app, Replit-hosted analytics. Radar sends custom campaign-page, signup, plan-selection, checkout and trial events only with Analytics consent. Event properties use fixed categories, a fixed landing-page variant label and aggregate counts, not names, emails, phone numbers, payment identifiers or message content. The first approved campaign page seen before signup is retained as signup attribution without replacing existing campaign-source attribution. Visits by existing accounts do not reattribute those accounts. Replit's automatically collected pageviews are controlled separately in Publishing settings.
  • Duration: Up to 2 years
  • Can be disabled: Yes — via Cookie Preferences
Consent Required

Advertising

  • Providers: Google Ads and Meta (Facebook/Instagram). After Advertising consent, the standard Meta Pixel may set first-party advertising cookies such as _fbp and _fbc to help match website visits and trial activations to ads. Google Ads may also set advertising cookies.
  • Purpose: With Advertising consent (independently of Analytics consent), Meta receives PageView events for selected public marketing pages and a StartTrial event for a confirmed, authorized trial activation. The trial event contains an opaque event identifier, zero value, and the plan currency — not the refundable mandate charge or subscription price. Meta also receives normal browser connection information, such as IP address and browser information, and may associate events with a Meta account under its own policies.
  • Privacy safeguards: Meta receives approved public-page URLs (including the Search Editorial campaign page), safe campaign/ad-click parameters, a fixed landing-page variant label, and safe referrer information. Consented Google ad-click identifiers may be retained in the session through signup and returned to the legitimate checkout confirmation for campaign measurement; withdrawing Advertising consent clears this stored transport context. These identifiers are not custom analytics event properties. Unknown query parameters and fragments are removed before Meta loads, and private pages suppress outgoing referrers. We do not send names, email addresses, phone numbers, account IDs, private URLs, Gmail content, Calendar data, or WhatsApp content to Meta. Automatic advanced matching and automatic event detection are not enabled. Private dashboards, admin pages, OAuth callbacks, billing receipts, email/calendar views, and shared-link pages are excluded. Trial measurement uses a clean confirmation page without billing or account details.
  • Duration: Google Ads cookies may last up to 1 year. Meta _fbp and _fbc cookies typically last up to 90 days; availability and duration depend on Meta's policies and browser restrictions.
  • Can be disabled: Yes — via Cookie Preferences

Turning Advertising off revokes Pixel consent and stops further Meta events. It cannot recall events already sent or unload a script already downloaded; you can clear existing cookies in your browser. Learn more in Meta's Privacy Policy.

You can update your cookie choices at any time from the Cookie Preferences panel, or by clearing cookies in your browser settings (Settings → Privacy & Security → Clear browsing data).

Your Rights

You have the right to:

  • Access, correct, or delete your personal information
  • Withdraw your consent at any time by logging out and revoking access
  • Request a copy of your data or its deletion
  • Opt out of WhatsApp notifications while maintaining email monitoring
  • Control which email addresses are monitored
  • Stop sending content to Radar's WhatsApp number at any time — simply stop messaging it. You can also ask us to delete previously sent inbound messages by contacting us.
  • Revoke Radar's access to your Google Calendar at any time, either by disconnecting the integration in your Radar settings or by removing Radar from your Google account permissions. After revocation, Radar will stop creating or updating calendar events; events Radar previously created on your calendar are left in place so they don't disappear from your schedule, and you can delete them yourself in Google Calendar at any time.

Data Retention

We retain your personal information only as long as necessary to provide our services and fulfill the purposes outlined in this policy. Email content is processed in real-time and stored temporarily for analysis. You can request deletion of your data at any time.

Changes to This Policy

We may update this privacy policy from time to time to reflect changes in our practices or legal requirements. We will notify you of any significant changes by posting the new privacy policy on this page and updating the "Last updated" date.

Contact Us

If you have any questions about this privacy policy or our data practices, please contact us: