UpShore privacy
Updated October 9, 2026 · Applies to the website and current Fire TV / Android TV prototype.
UpShore combines calendars you choose into a family display. You can sign in with Google and explicitly attach an existing family calendar to your account. Anyone with your private editor link can edit that family calendar. Keep it within your household.
Google sign-in
Google provides your stable Google account identifier, verified email address when available and display name. We request only basic sign-in information, not Google Calendar access. Your Google password, Google access token, refresh token and original private editor link are not stored in your UpShore identity record. An explicit private-calendar proof is required before attaching a calendar; an email match does not grant calendar ownership.
Identity details, calendar ownership records, sign-in flow records and sessions are encrypted in private Cloudflare R2 storage. Identity indexes use keyed digests; session and flow lookup keys use random-token digests. A Secure, HttpOnly, same-site cookie keeps you signed in for up to 24 hours, without automatic extension. Sign-in flows expire after 10 minutes. Expired records authorize nothing; physical removal may happen later during maintenance. Signing out of all browsers revokes browser sessions at their next authorization check. Requests already authorized and in progress may finish.
Deleting family data revokes access to that calendar, while minimal ownership and revocation records prevent old access from being reassigned or restored. Google identity removal and ownership transfers are currently handled by support, rather than a self-service account deletion button. Contact support without sending credentials or private calendar links. Google handles recovery of your Google account.
Roku sign-in
Google Firebase Authentication processes your Roku email and password. Website setup verifies that the Firebase Google identity matches your existing UpShore Google identity before linking Roku access. Matching email addresses alone do not grant calendar ownership. When you sign in on Roku, your email and password pass over HTTPS through UpShore on Cloudflare to Firebase. UpShore does not save that password or Firebase sign-in tokens. Encrypted access records bind your Firebase user identifier to your existing UpShore identity and calendars.
Roku receives a separate display-only device token, not Apple credentials or calendar editor access. Changing or removing Roku access through UpShore revokes existing Roku grants at their next authorization check. Removing Roku access does not delete your Firebase account. Changes made directly in Firebase are not automatically reflected in already-issued TV grants; use UpShore’s removal controls to revoke them. Contact support for identity deletion.
Information used by the service
- Family display settings: names, colors, icons, birthdays, weather location, event filters and any background photo you choose to save.
- Calendar connection information: subscription links, selected calendars, and iCloud calendar names, descriptions and addresses discovered from Apple. If you choose to keep iCloud connected, we store your Apple Account email and app-specific password as an encrypted connection.
- Calendar events and optional calendar wallpaper images. Connected TVs retrieve events from your selected providers and keep local copies so the display can work through connection failures. TVs supporting the editor preview send a limited date range of event titles, times, source identifiers, weather, display icons and an optional picture of their calendar to your private family editor. Events from registered calendars can remain in that preview data even when you hide them, so you can preview changes before saving. The existing private wallpaper-sharing feature can store a picture of the day's events on our service.
- Private access and pairing information. The server stores owner, invitation and device-token digests rather than the raw keys, together with the records needed to associate your devices with your family.
- Feedback you send and support emails. Trial feedback is available to the trial organizer for review.
- Technical network information processed by hosting services, including IP addresses used for request limits and security.
How information is used
We use this information to save your choices, connect the screens you authorize, retrieve and display selected calendars, provide weather, handle support and review feedback. UpShore's calendar integrations retrieve events; they do not create, edit or delete events in Apple or other source calendars.
The current product has no advertising, third-party analytics SDK, payment-card collection or automatic billing. Google account sign-in identifies you; it does not connect Google Calendar. Microsoft account sign-in is not implemented. Calendar subscription links from those providers can be added when available.
Providers and sharing
- Cloudflare hosts the website and service, stores server data in private R2 storage, processes technical requests and forwards support email.
- Google verifies your Google sign-in and provides the basic profile information described above. Its sign-in button image may also be loaded from Google.
- Firebase Authentication (Google) stores and verifies Roku authentication credentials and processes basic Google identity information when you link sign-in methods. No Firebase Analytics SDK is used.
- Apple provides iCloud Calendar access using the Apple Account email and app-specific password you enter. This is not an Apple OAuth sign-in.
- Open-Meteo receives location searches or coordinates to provide location matches and weather.
- Your calendar subscription providers receive requests from connected TVs when their feeds are refreshed.
- Gmail receives support messages sent to support@upshorecalendar.com.
These providers also process information under their own terms and policies. You control sharing of private links, screenshots, downloaded settings and wallpaper images with your relatives. Do not put passwords, app-specific passwords, subscription links or private editor links in feedback or support email.
Family view links and snapshots
Your editor can create separate view-only family links lasting 1, 7 or 30 days. Anyone with one can see the current authorized picture of your TV calendar until the link expires or you remove it. These links provide no calendar editing controls, saved provider credentials, subscription URLs or raw event records. Their random access tokens are returned once; encrypted server grants and token digests support expiry and removal. Link records are kept until replaced or removed through cleanup. Family deletion revokes these links and removes their active server records.
A calendar snapshot is a still image of the current editor view, which may include unsaved choices. Sharing opens your device's sharing controls when available, or downloads a PNG. You choose the recipient yourself. A copy already saved by someone cannot be erased by removing a live link.
The original personal TV prototype can obtain a private update link that expires after 24 hours. Its APK remains in private R2 storage and is served only through an owner-authorized expiring link. The prototype may contain that household's private calendar setup and must not be shared with another family. The APK does not use separate application-level storage encryption. Family deletion removes the matching hosted private update and its link records; expired link records may also be cleared when a new link is requested.
Storage and access
Family settings, subscription links contained in settings, remembered iCloud connections, feedback and TV editor-preview data are encrypted in server storage with family-bound authenticated encryption. The editor-preview image and icons are encrypted with that preview data; preview uploads do not contain provider passwords or subscription URLs. The separate calendar-wallpaper images are kept in private storage and protected by private read links; they do not have separate application-level encryption. Version 0.4.8 receives selected iCloud event data from UpShore over HTTPS rather than Apple credentials. UpShore reads selected calendars using the encrypted saved server connection. Successful migration removes legacy Apple credential storage from the app. Earlier versions may retain previously delivered credentials protected by Android Keystore. Revoke the app-specific password at Apple to invalidate those credentials. Calendar content remains in private TV storage for offline use. The browser holds preview events in memory while the editor is open and does not save them in localStorage. Browser remembering of a private link uses localStorage only when you choose it.
Separate families have separate settings, connections and paired devices. The legacy wallpaper-sharing feature remains separate from invited family owners. Server request observability is disabled in this deployment; hosting providers can still process operational and security information.
Retention, disconnecting and deletion
There is no scheduled expiry or routine automatic purge for family configurations in this beta. The service keeps one latest editor preview per family, replacing it when the TV sends a newer snapshot. Use the controls in your private editor to disconnect a remembered iCloud connection or delete the family's stored data. Disconnecting removes the saved server credential and disables that family's iCloud calendars; your private editor link and other calendar sources remain. Revoke the app-specific password in your Apple Account separately if you want Apple to stop accepting it.
Family deletion removes active family settings, saved connections, paired-device records, editor previews, feedback and owner-key records. For the original family it also removes its hosted wallpaper and setup images/pages and cancels unused invitations. Minimal digest-based revocation records and a deletion timestamp remain so old links and devices cannot restore deleted data and interrupted cleanup can be retried.
TV versions that support the deletion feature clear cached family data when they receive the service's authenticated deletion response. Older prototype versions may need their app data cleared manually. Offline devices cannot receive a deletion response until they reconnect. Deletion cannot remotely erase screenshots, downloaded settings, saved wallpapers or support emails already kept by other people. Hosting and email providers may retain operational records under their own policies; we do not promise a specific provider-backup deletion time.
Contact form
The contact page lets you submit a support message without opening a mail app. It stores the topic, subject, message, optional name, reply email and device details, submission time, and a random receipt reference. Messages are encrypted in private Cloudflare R2 storage and can be read only by the trial organizer through the support inbox. The form does not send an automatic email or notification. Messages are separate from family calendars, remain until the organizer removes them, and are not removed by deleting a family calendar. You can request removal using your receipt reference.
Contact
For privacy questions or trouble using deletion controls, use the contact form or email support@upshorecalendar.com. Do not send credentials or private access links. Automatic email-based account recovery is not available in this beta.
