Skip to main content
Lab Grimoire
TW EN
Coffee

Lab Grimoire — Privacy Policy

Version: 2026-08-08 · Effective: 2026-08-08

1. Plain-language summary

2. Data we collect

Category Examples Purpose Retention
Account email, password hash (PBKDF2 600 000 iterations), display name, locale Authenticate and personalise Until account deletion
Tier and subscription tier, Polar customer & subscription IDs, period dates Gate paid features and bill correctly Until account deletion + 7 years for tax / audit
Quota counters day-bucketed download / API counts keyed by userId (auth) or hash(IP) (anonymous) Enforce per-tier and per-IP limits 48 hours rolling
Audit logs download_log, engine_load_log rows (timestamp, tool, format, fingerprint, IP, User-Agent, tier) Detect leaks, fraud, regression 18 months, then purged
Activity log admin-side actions and cron events Operational diagnosis 90 days
Telemetry aggregate counts of feature usage (no payload content) Product improvement 365 days

Automated enforcement of these retention windows is being rolled out; until it completes, older rows may persist beyond the stated window. Contact us to request early deletion. The "48 hours rolling" window for Quota counters is already enforced via KV TTL and is not subject to this caveat.

We do not collect:

3. Tool data

All analysis tools on this Service run in your browser. Values you paste or upload, including CSV, images, and FCS files, are not sent to our servers and are not stored by us.

Optional R-language cross-validation (WebR) also runs in the browser: R is compiled to WebAssembly, and your data is not transmitted off-device.

When a tool is used, we may record which tool and which action took place (for example, analysis started, result generated, or export). That record does not include your data content, numeric values, field names, or file names.

That event uses the same analytics pipeline as other site events. It therefore includes the page URL, a first-party session identifier, referrer, and UTM attribution parameters. The server also records IP address and User-Agent. When Google Analytics 4 is enabled, the same event is also sent to Google Analytics 4. See the Telemetry row in the table in section 2.

Because we do not retain your analysis inputs or outputs, there is no way to revisit a past analysis session from our side.

4. Cookies and local storage

We do not set third-party tracking cookies.

5. How we use your data

6. Sharing with third parties

Recipient Purpose Data shared
Cloudflare Hosting, edge compute, D1 database, KV, R2 storage All Service data is stored on Cloudflare infrastructure under our account
Polar Payment processing, invoicing Billing email, subscription status; no card data passes through us
Email provider (transactional) Send verification and notification emails Email address and message content
Google Analytics 4 Aggregate traffic and feature-usage analytics Event name, page URL, first-party session identifier, referrer, UTM parameters

We never share data with advertisers or data brokers.

7. Where data lives

Cloudflare's global edge network. Your D1 row may be served from regional replicas; we do not control replica geography precisely. If you require data residency in a specific jurisdiction, contact cyuh0817@gmail.com before subscribing.

8. Your rights

If you are in Taiwan, the EU/UK, or any jurisdiction with comparable rules, you have at minimum the right to:

Email cyuh0817@gmail.com to exercise any right. We will respond within 30 days.

9. Audit logs and the embedded fingerprint

Every CSV / PNG / report you download from a paid feature carries a fingerprint string of the form lg_<tier>_<hash> (anonymous downloads use lg_anon_<hash>). The fingerprint is a keyed hash of your account ID (or IP, for anonymous) and a timestamp. It is not reversible to your raw IP without our server-side secret.

We use the fingerprint to:

If you object to the fingerprint, please do not use the export feature.

10. Security

We disclose breaches affecting personal data to affected users without undue delay, and to competent authorities within statutory windows.

11. Research use only

All tools on this Service are for research and educational use only.

They are not medical devices, have not been approved by any regulatory authority, and must not be used for clinical diagnosis, treatment decisions, or patient care.

If you upload data derived from human subjects, you are solely responsible for obtaining ethics approval and any required consent, and for ensuring the data is de-identified before use.

You are solely responsible for judging and verifying the correctness and suitability of any statistical output.

12. Children

The Service is not directed at children under 13. We do not knowingly collect personal data from anyone under 13. If you believe a child has registered, contact us and we will delete the account.

13. AI crawlers

We permit selected AI search and retrieval crawlers to index public content. Which crawlers are allowed and which are refused is declared in labgrimoire.com/robots.txt and labgrimoire.com/llms.txt. Crawlable content contains no personal data: account pages, billing pages, and the admin interface are excluded from crawling and carry noindex.

14. Changes

This Policy may be revised; the version string in the front-matter changes when we do. Material changes will be announced on the site changelog at least 30 days before they take effect, except when a faster change is required to address a security or legal issue.

15. Contact

cyuh0817@gmail.com for any data-related question.


Lab Grimoire is a personal project operated by CYHsieh, not affiliated with any company. This document is provided as-is and is not legal advice.