Privacy Policy

Meta (Facebook)

Advertising measurement and conversion tracking via the browser pixel and the server-side Conversions API. Data sent: hashed email, an internal user id, Meta click identifiers, IP address, and user-agent. Consent category: marketing. Privacy policy: facebook.com/privacy/policy.

Stripe

Processes payments and subscriptions. Legal basis: performance of the contract. In addition, when you give marketing consent, Stripe acts as a pass-through for Meta ad-attribution signals: at checkout we store the Meta click identifiers, IP address, and user-agent in the Stripe payment object metadata, then read them back to enrich the conversion events sent to Meta. Stripe sets no new cookie in your browser for this. Privacy policy: stripe.com/privacy.

PostHog

Product analytics to understand how the app is used. Consent category: analytics. Privacy policy: posthog.com/privacy.

Clarity (Microsoft)

Session recording and heatmaps to spot and fix usability issues. Consent category: session recording. Privacy policy: privacy.microsoft.com/privacystatement.

Scopes requested

• https://www.googleapis.com/auth/calendar.readonly : read-only access to the user's Google Calendars and events, used only for the Calendar Import feature.
• https://www.googleapis.com/auth/calendar.app.created : access limited to a dedicated secondary calendar that SmartCookie itself creates. This scope grants no access to the user's other Google calendars or their events. It is used only for the Calendar Sync feature.

How we use Google user data (Calendar Import)

We use the read-only scope solely to read the user's existing calendar events when the user explicitly initiates the Calendar Import flow. Events are processed in-memory, grouped into proposed lesson series by our algorithm, and shown to the user for review. Only the lesson data the user explicitly confirms (lesson date, time, title, and attendee email or name) is persisted to SmartCookie's database. We do not poll Google Calendar in the background, set up webhooks, or sync continuously. We never read from, write to, modify, or delete events in the user's other Google calendars with this scope.

How we use Google user data (Calendar Sync)

When a teacher connects Calendar Sync, SmartCookie creates a dedicated "SmartCookie" secondary calendar in their Google account and one-way mirrors their SmartCookie sessions to it (creating, updating, and cancelling events as the teacher manages sessions in SmartCookie). At the teacher's option, SmartCookie may add a Google Meet link to those events. Enrolled students who have an email address are added as guests on the event; their name and email are shared with Google as event attendees so Google can deliver the invitation. We store only the integration status, the id of the calendar we created, event-mapping ids, and conference (Meet) link metadata. We do not read events from the user's calendars with this scope, and the sync is one-way: SmartCookie is always the source of truth.

Limited Use compliance

SmartCookie's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

• We do not transfer Google user data to third parties except as necessary to provide or improve the Calendar Import and Calendar Sync features, to comply with applicable law, or as part of a merger, acquisition, or sale of assets with notice to users.
• We do not use Google user data for serving advertisements, including retargeting or personalized advertising.
• We do not use Google user data to develop, improve, or train generalized or non-personalized AI/ML models.
• We do not allow humans to read Google user data, except: (a) with the user's affirmative consent for specific events, (b) where necessary for security purposes (e.g. investigating abuse), (c) to comply with applicable law, or (d) where data has been aggregated and anonymized.

Data retention

Raw Google Calendar event data is processed in-memory during the user-initiated import request and is not retained. Lessons that the user confirms during import are stored in SmartCookie's database as the user's lesson records and are retained for the duration of the user's account. The user may delete imported lessons at any time from within SmartCookie. For Calendar Sync, we retain only the integration status, the id of the dedicated calendar we created, event-mapping ids, and conference link metadata for the duration of the integration; this metadata is removed when the user disconnects the integration or deletes their account.

Data security

We apply security measures to protect the confidentiality of Google user data and all of your personal data. All data is transmitted over encrypted connections (HTTPS/TLS) and stored on hosting infrastructure that encrypts data at rest. Access to your data is restricted by authentication and authorization controls, so that only you, as the account owner, can access your imported calendar data. Google access tokens are stored securely, used solely for the Calendar Import and Calendar Sync features, and deleted when you revoke access. We follow the principle of least privilege, periodically review our security practices, and limit staff access to data as described in the Limited Use section above.

Revoking access

The user may revoke SmartCookie's access to their Google account at any time at myaccount.google.com/permissions. Revocation immediately disables the Calendar Import and Calendar Sync features but does not affect data already persisted from prior imports. Disconnecting Calendar Sync stops future syncing; events already created in the user's Google Calendar remain there until the user removes them in Google.