Family Check-In

Privacy Policy

Last updated: June 6, 2026

Information we collect

Family Check-In accesses your Google Calendar data solely to display events and chores on your Roku device. We collect:

• Google Calendar event data (titles, dates, descriptions)
• OAuth access tokens (stored locally on your Roku device)
• Device identifiers for authentication purposes

How we use your information

Your calendar data is used exclusively to:

• Display events and chores on your Roku TV
• Update chore completion status in Google Calendar
• Sync changes between your calendar and the Roku app

Data storage

All OAuth tokens and calendar selections are stored locally on your Roku device in the channel's registry. We do not store your calendar data or personal information on our servers. The only exception is optional diagnostic log reports, which you can send manually and which contain no personal information (see "Diagnostic log reports" below).

Data sharing and disclosure

We do not sell, rent, share, transfer, or otherwise disclose your Google user data to any third parties. Your Google Calendar data is accessed exclusively between the Family Check-In app on your Roku device and Google's own servers. No calendar data, OAuth tokens, or personal information passes through or is stored on our servers. The only external service that receives your data is Google, which you have explicitly authorized through the OAuth consent flow and whose use is governed by Google's Privacy Policy.

Third-party services

Family Check-In uses Google Calendar API to access your calendar data. Your use of Google services is subject to Google's Privacy Policy.

Data protection

We apply the following mechanisms to protect your data:

• Encrypted transport: All OAuth authorization and token exchange requests use HTTPS/TLS.
• OAuth 2.0: We use the industry-standard OAuth 2.0 protocol. Family Check-In never sees or stores your Google password.
• Local-only storage: OAuth access and refresh tokens are stored only in the Roku channel's local registry on your device. They are never transmitted to our servers.
• Minimal scope: We request only the Google Calendar scopes necessary to read and update calendar events for the app's functionality.

Data retention and deletion

Because we have no server-side storage, there is no Google user data to retain or delete on our end. All data is held locally on your Roku device:

• OAuth tokens persist in the Roku channel registry until you revoke access or uninstall the channel.
• Calendar data is fetched on demand and never cached beyond the current session.

To delete all stored data, you can:

• Revoke app access in your Google Account at myaccount.google.com/permissions, which invalidates all tokens immediately.
• Uninstall the Family Check-In channel from your Roku device, which removes all locally stored tokens and settings.

Google Calendar event data that you have created or modified remains in your Google account, under your control, and is not affected by uninstalling this app.

Diagnostic log reports (optional)

When you press "Send Logs" in Settings or on the subscription error screen, the app transmits a diagnostic report to our servers. This report contains: app version, device model type, and subscription flow events (API commands, status codes, timestamps). It does not include calendar data, event titles, Google OAuth tokens, or any personally identifiable information. Reports are used solely to diagnose technical issues and are deleted within 30 days. Sending a log report is always your choice — it only happens when you explicitly press the button.

Your rights

You can revoke Family Check-In's access to your Google Calendar at any time through your Google Account settings at myaccount.google.com/permissions.

Children's privacy

Family Check-In does not knowingly collect personal information from children. The app is designed for family use under parental supervision.

Changes to this policy

We may update this privacy policy from time to time. Changes will be posted on this page with an updated revision date.

Contact

For privacy questions or concerns, visit our support page.