Grant data-management plan text

Copy this into a Data Management and Sharing Plan, then replace the PI name and any repository the FOA requires. It describes how runline stores working records — not a legal opinion.

Data Management and Sharing Plan — laboratory records in runline

1. Data types
Our lab records executable protocols, experiment-run notebooks (steps, reagent lots, notes), Quantify analysis sheets, and Diagnostics cases (symptoms, controls, ranked causes, and recovery steps). Optional literature search jobs store queries and paper identifiers we request. We do not treat runline as a genomic or clinical repository.

2. Related tools / software
Primary working copy: runline (https://runline.space), a runtime execution engine. Cloud persistence uses Supabase (authentication, Postgres, file storage). Optional processors (only when a feature is used): PostHog US for named product events after cookie consent (never under Global Privacy Control), Stripe for test-mode billing, Resend for transactional mail, and Google Gemini only when AI_TIER=paid. Full processor list: https://runline.space/privacy

3. Standards
Protocols and run records export as Markdown / JSON from the product (profile menu → Export my data, or GET /api/privacy/export). STAR Methods text can be generated from a run. We keep laboratory SOPs and journal-required metadata in the notebook fields our group already uses (strain, lot, instrument).

4. Preservation / access / reuse
Workspace content is retained until a lab member deletes the item or the account. Diagnostics cases may be purged earlier if the lab shortens retention. Shared open-access literature cache rows are not personal data. We can export JSON/Markdown for deposit in our institutional repository or a domain archive the FOA names. Unpublished science stays in the lab workspace; we do not grant public crawl of /share/ links via robots.txt.

5. Oversight
The PI (or named data steward) owns this plan. Access is lab-membership scoped (Row-Level Security). Invites are deliberate user actions only — we do not auto-email co-authors. Deletion requests aim to complete within 30 days after verification.

6. Limitations (do not delete)
This paste describes how runline stores our working records. It is not a substitute for institutional DMP templates, counsel, or repository deposit receipts required by the NOFO.