Skip to content
LeaguebornGet my recap

Product data boundaries

Read-only should be specific.

A public Sleeper lookup, saved league coverage, product analytics, and a public share receipt have different data consequences. This page names those differences directly.

Direct answer: Leagueborn never asks for a Sleeper password and cannot write to a Sleeper league. Saving coverage requires a Leagueborn sign-in; creating a share receipt makes that receipt public to anyone with its URL.

From lookup to storage

What changes when you save?

A preview reads provider-exposed data so you can choose a league. It does not create persistent Leagueborn coverage. Saving is an authenticated import with normalized product records.

01 / Public preview

Read-only provider lookup

A public Sleeper username can return account display details and available league data. The lookup does not use a Sleeper password or authorize changes to the provider league.

02 / Saved coverage

Authenticated normalized records

After sign-in and selection, Leagueborn can store account and membership references, seasons, franchises, rosters, matchups, scores, transactions, drafts, picks, and derived league records.

03 / Public share

A receipt anyone with the link can open

An authenticated member can deliberately create a share asset. The rendered receipt can expose league or team labels, recap text, and final-score evidence included in that asset.

Product analytics

The app records bounded events.

Current product analytics use an anonymous browser identifier to connect basic events without placing the raw identifier into the product-events table.

What the event path does

  • Creates a random anonymous identifier in browser storage.
  • Hashes that identifier before database persistence.
  • Stores the event name, path, bounded properties, and time.
  • Does not store raw IP addresses in the product-events table.

What this statement does not claim

It does not promise that browsers, hosting, network, database, authentication, or upstream Sleeper infrastructure produce no operational logs. Those systems can process normal request and account data outside the product-events table.

Public-by-link is not private. Create or send a share receipt only when the league labels and recap evidence rendered there are appropriate for anyone who receives the URL.

Questions, answered

Who can do what?

The important split is between reading public provider data, saving authenticated coverage, and explicitly publishing a share.

Does Leagueborn collect my Sleeper password?
Leagueborn never asks for a Sleeper password and cannot change Sleeper league settings.
Does signing in grant Sleeper write access?
No. Leagueborn sign-in controls access to saved Leagueborn coverage. The Sleeper integration remains read-only and cannot change league settings, rosters, lineups, members, or scores.
Does read-only mean Leagueborn stores nothing?
No. Read-only describes the boundary with Sleeper. A preview does not create saved coverage, but an authenticated import can store normalized copies needed for recaps and history.
Can everyone see a league after it is saved?
Saved coverage is an authenticated product surface. A separate share receipt becomes public-by-link only when an authorized member creates it.
Is a share link confidential?
No. Anyone who obtains its unguessable URL can open the public receipt. The URL reduces accidental discovery; it is not an access-control credential.

Bring your own league

Preview before you decide to save.

Use the read-only Sleeper lookup first. A Leagueborn account is required only when you choose ongoing league coverage.
Get my latest recap Read the sample