Clear explanations of local storage, feedback and beta limitations.
Event dates, cell names, culture vessels and passages are stored in your browser using LocalStorage and IndexedDB. Without signing in, all schedules remain browser-local. Optional account-based synchronization is available in beta for signed-in users. The first cloud save or load is a deliberate action, and full real-device testing is still in progress.
People who choose to sign in use Supabase email verification and user-isolated cloud storage. Authentication uses an email address; the backend restricts calendar data access to its owner. Database isolation has been tested; real-device sign-in and cross-device syncing are undergoing final checks. Keep local JSON backups.
Browser data can be erased or lost with a device. Export JSON backups regularly. Push notifications are not guaranteed when the app is closed; use secondary reminders for critical work.
Once secure online intake is activated, role, field, feedback text and any voluntarily provided reply email are stored in a Cloudflare database. Cloudflare Turnstile is used to reduce automated abuse. When online intake is unconfigured, your feedback is not submitted.
The hosting provider may process standard technical access logs. Research-domain photographs load from Pexels, and the laboratory background photo loads from Unsplash. Those image providers receive asset requests. Photographs are illustrative and do not depict the user's own results.
BenchCadence is an experimental scheduling aid, not an ELN, clinical record system, laboratory SOP, safety management system or audit record. Never enter patient/participant identifiers, passwords or confidential unpublished research data.