Privacy, Local Data & Optional Sync

1. The desktop application

Coding works without an internet connection. Automatic update checks contact GitHub at startup and periodically while the app is open; you can turn them off in Settings. Sign-in, session renewal and collaboration contact the configured service when those features are used.

Excluded from collaboration sync

Transcript files and full text
Quote fields and passage text
Original filenames and folder paths
Analytic and coding memo fields
Full project database and backups
Interview dates and diagnosis fields

Collaboration sync · HTTPS / WSS

Shared when collaboration is enabled

Study and participant labels
Code names, hierarchy and colors
Definitions, criteria and examples
Coded spans: IDs and character offsets
Coder names and memberships
Content hashes and revision metadata

Codebook text syncs as written, including any copied quotes. Exports and backups can leave your device through sharing or synced folders.

Stored credential files remain on this computer. Authentication uses credential values with the configured sign-in service.

Data boundary field disclosure

Category	Synced when collaboration is active	Excluded from collaboration sync
Account & Access	Account email, auth metadata, study membership, coder display name, device sync state	Stored credential files, local application preferences, working folder paths. Credential values are used with the auth service.
Study Identity	Study title, de-identified participant IDs, interview IDs, segment counts, content hashes	Raw transcript files, full transcript text, original filenames, interview dates, diagnosis fields
Codebook	Code IDs, code names, definitions, inclusion criteria, exclusion criteria, examples, hierarchy, color	None (codebook text syncs word-for-word so teams share definitions; author them de-identified)
Coding	Coder attribution, segment IDs, code IDs, character start/end offsets, timestamps	Verbatim quote text, coding memos, analytic memos, reflective notes
Output & Diagnostics	Nothing automatically	Exported reports, local SQLite databases, backup files, crash logs

Read docs/PRIVACY-AND-PERMISSIONS.md on GitHub →Read docs/IT-DEPLOYMENT.md on GitHub →

2. This website (fleuron.study)

We count page visits with Cloudflare Web Analytics, which uses no cookies and no cross-site tracking. It records the page visited, the referrer, and basic browser, device and load-performance facts. We run no Google Analytics, Plausible, PostHog, advertising trackers, or tracking pixels. Fonts, scripts, styles and images are served from this domain, except the Cloudflare analytics beacon. Cloudflare hosts the site and processes requests; its network error reporting can send browser reports about connection failures. The theme choice is stored locally in your browser. Download and support links take you to GitHub, which operates under its own policies.

Visit counts, no cross-site tracking: We count page visits with Cloudflare Web Analytics. It sets no cookies and does not track you across sites; it records the page visited, the referrer, and basic browser, device and load-performance facts. We run no Google Analytics, Plausible, PostHog, advertising trackers, or tracking pixels.
Theme storage: The theme toggle stores your choice in browser local storage. We do not add tracking cookies.
No forms or inputs: We collect no emails, names, newsletters, or visitor submissions.
Page assets: Fonts, styles, scripts and images are served from this domain, except the Cloudflare analytics beacon (static.cloudflareinsights.com). Cloudflare can separately receive browser network-error reports. Read Cloudflare’s explanation.
What checks cover: Our asset-reference check scans generated HTML and CSS for externally hosted resources, allowing only the analytics beacon above. It does not prove the absence of every runtime request or hosting-layer report.