Privacy policy

1. Who and what this covers

This policy describes the More in Frame Chrome extension and its shared score service, operated by the independent More in Frame developer. More in Frame is a personal project, not a Google or YouTube product. It does not cover YouTube TV itself or other services you visit.

2. Information kept on your device

The extension reads the program titles, page links and player state needed to build and control your multiview. When you import open tabs, it reads titles and URLs of eligible YouTube TV tabs, not your general browser history.

• Local storage: saved sources and their labels, saved lineups, the most recent lineup, layout choice, update timestamps, and score preferences such as league selection, favorite games and spoiler delay.
• Session storage and memory: workspace tab and document identifiers, internal authorization tokens, audio state, pane sizes, temporarily matched game airings and recent public score snapshots.

These records support playback controls, restoring your last lineup and displaying scores. The extension does not use Chrome sync storage or upload these records to the score service. Local data is accessible to someone with access to your Chrome profile; it is not an encrypted vault.

3. What leaves your browser

YouTube TV

Opening the guide, entering a search or loading a program contacts YouTube TV directly through its own pages and players. Google receives those interactions and its ordinary account, cookie and network information under the Google Privacy Policy. More in Frame does not ask for, extract or store your YouTube TV password or authentication cookies. It does not record or upload the video or audio you watch.

Shared scores

While scores are shown, the extension requests a common public scoreboard over HTTPS from a service hosted by Supabase. The request contains no lineup, program URL, search text, favorite selection or user account identifier. It omits cookies and the referring page URL. League and favorite filters are applied in your browser, not sent to the score service.

Supabase and its infrastructure providers necessarily receive network information such as your IP address, request time, endpoint and HTTP metadata. They may process operational and security logs to deliver and protect the service. See the Supabase Privacy Policy. The API host is djxoottwxpgvjmpnyoft.supabase.co; its root address is not a public website.

Score providers

The server obtains public schedules and scores from BALLDONTLIE and, where enabled, NCAA community and SportsPuff feeds. Those provider requests originate from the server. The application does not forward your IP address, browser headers, lineup or favorites to them. The server cache contains public sports data and refresh-control metadata, not a viewer profile.

Optional bug reports and feedback

The Feedback button prepares a local report for you to review. Nothing is submitted automatically. Choosing Email report sends the displayed report to the developer through the existing Wayfind feedback endpoint at www.getwayfind.com/api/notify-feedback, hosted on Vercel and delivered by Resend. These services process the report and ordinary connection metadata to deliver the email. The recipient is fixed on the server; no email-service credentials are included in the extension. Email-service acceptance does not guarantee inbox delivery. Copy and download remain available instead of emailing.

Reports contain your description, extension versions, basic browser and player state, ticker settings and timestamps, and recent score-request outcomes. Public game scores for the selected leagues are included only if you select that option. Large reports trim older detail to fit the existing mailer; the displayed report is the one sent. Reports exclude account details, credentials, page URLs, watched program titles, saved lineups and video captures. Review your description before sharing it. Reports are labeled More in Frame (formerly YTTV Grid) even though the shared email template is Wayfind-branded.

For troubleshooting, up to 20 recent score-fetch outcomes are kept in extension session storage; exports exclude entries older than four hours. Up to 30 recent ticker events are kept in workspace memory. These records use timestamps, HTTP status codes and fixed outcome labels, not raw network responses or error messages. They are not sent to an analytics service. Email attempt identifiers and times, but not report contents, are kept in session storage for duplicate/rate-limit checks; checks disregard entries older than an hour. Emailed reports remain in the developer's inbox until deleted; there is no automatic inbox deletion guarantee. A downloaded copy remains on your device until you delete it. See Resend’s Privacy Policy and Vercel’s Privacy Notice.

Public policy website

The public copy of this policy is hosted on Vercel. Opening that website sends Vercel ordinary connection information, including your IP address, requested page and browser metadata, so it can deliver and protect the page. The policy website has no analytics scripts, forms, advertising or application cookies, and does not contact YouTube TV or the score service. We do not maintain a separate visitor-log archive. Vercel may retain infrastructure and security information under its applicable policies; we do not promise a fixed deletion period for those records. See Vercel’s Privacy Notice. Reading the bundled policy inside the extension does not contact Vercel.

4. Permissions and limited use

Storage access saves settings and lineups. Optional access to tv.youtube.com and script execution enable the guide, player controls and tab import. Access to the packaged score-service host enables score requests. This build does not request access to all websites, browser history, cookies, microphone or camera, and it does not run in incognito.

The extension uses information obtained through these permissions only to provide the features described here. It does not sell that information, use it for targeted advertising, or send it to an analytics service.

5. Retention

Saved sources, lineups, the last lineup and preferences remain in local extension storage until removed or the extension is uninstalled. Session storage is cleared when Chrome clears the extension session; in-memory state also ends when its workspace closes. Cached public scores are replaced as updates arrive; hiding scores does not erase already cached snapshots.

The score-service application does not create viewer accounts, store visitor IP addresses in its database, or write custom visitor request logs. Its database holds a shared public scoreboard cache and refresh-control metadata, which may persist until replaced or removed.

Supabase automatically records operational request and function information. For the Free plan used by this beta, Supabase publishes one day of API and database log retention. This describes the standard project log window, not a promise that every infrastructure or security record is deleted within 24 hours. Supabase may retain other information for security, legal or operational purposes under its own policies. We do not add a separate visitor-log archive or analytics service. If the hosting plan or logging setup changes, this policy must be updated accordingly.

6. Your choices and deletion

• Stop score requests: hide scores using the Scores control or score settings in the extension. Requests already received by the server cannot be recalled.
• Manage saved information: open Edit lineup, then Saved sources & lineups to remove saved entries. Removing a playing pane is not the same as deleting its saved source or the last remembered lineup.
• Delete all extension-local information: remove More in Frame from Chrome’s Manage Extensions page. This does not delete your YouTube TV account, Google activity or service-provider logs.
• Revoke access: change More in Frame’s site access in Chrome’s extension settings or uninstall it. Without YouTube TV access, the multiview cannot operate.

7. Security and changes

The extension uses HTTPS for service requests, validates incoming data, and limits stored-data access to trusted extension contexts. Provider API keys are held by the server, not distributed to viewers. No system is risk-free. Material changes to data handling will be reflected in this policy and, where appropriate, in the product before new uses begin.

8. Privacy questions

Contact Adam at adam@getwayfind.com for privacy questions or requests about More in Frame. If your request concerns an emailed bug report, include its approximate date so it can be located; do not send passwords or account credentials.