Skip to main content

Privacy

Privacy and data use

A factual summary of the information currently handled by this project.

Updated 2026-07-24

Information collected

  • A waitlist email address when a visitor requests the community launch notice.
  • Provider survey responses, work contact details, source links, and optional uploaded files.
  • Limited technical request data processed by hosting and security systems.
  • Error-reporting configuration exists for Sentry, but current production receipt has not been verified. Performance tracing and session replay are not part of the approved measurement system.
  • When aggregate measurement is enabled, one of seven fixed reading or search-outcome signals is sent to a same-origin endpoint. Payloads contain only approved broad groups or outcomes; they contain no search text, page path, referrer, account, visitor ID, cookie, or saved item.

Public account registration and sign-in are currently disabled. The project does not use advertising, session replay, user profiles, or third-party behavioral analytics scripts.

Information kept on this device

Saved reading stores only the paths of saved public pages and the time each page was saved in this browser's local storage. The list is not linked to an account, sent to the project, or synced between devices. Aggregate measurement may report only that a non-empty saved list was viewed or that an item was selected; it never sends the item, path, timestamp, count, save action, or removal action. Removing the items or clearing this site's browser data deletes the local list.

How information is used

  • Waitlist emails are used for the requested launch notice.
  • Provider submissions are held for verification, editorial review, and approved publication.
  • Technical data is used to operate, secure, and diagnose the service.
  • Aggregate counters are used for a monthly, page-query-free comparison of public discovery and broad useful-reading signals. They are not used to identify people, reconstruct sessions, rank content, or infer individual medical interests.

Service providers

The project uses Vercel for hosting, Neon for application data, Sanity for editorial records, Jotform for provider questionnaires, Resend for transactional email, and Sentry for minimized error reporting. Articles may also contain YouTube or Vimeo embeds; loading an embedded player can allow that provider to receive technical request data under its own privacy terms. These services may process data in countries other than the visitor's or respondent's country.

For an aggregate signal, Vercel processes the request before application validation and Neon processes the dimensioned counter update. Production collection remains disabled unless request-specific technical records and deleted-data residuals for this workflow can be bounded to 30 calendar days.

Retention and requests

Waitlist records are retained until the requested notice is sent or deletion is requested. Provider submissions are retained while the related record is reviewed or displayed. Rejected or unused provider submissions are scheduled for deletion within 90 days after review completion.

Aggregate measurement counters keep the current partial month plus 13 completed months. A daily maintenance job applies the cutoff with a deletion service level of 48 hours. Because no visitor or event identifier is stored, the project cannot locate or delete one person's contribution; requests can instead concern the complete aggregate dataset, retention pruning, or provider technical records.

To request access, correction, or deletion, email editorial@limblengtheninglibrary.org. Verification may be required before a request is completed.