Privacy Policy
Last updated: 10 August 2026
Summary
Schedule 1 Lab is operated by a sole trader registered in France. Full publisher details are on the legal notice. This policy explains what we collect, why, and what you can do about it.
Short version: the tools work without an account and without us knowing who you are. If you create an account, we store your email address and whatever you choose to save. We show ads, and those ads use cookies.
Who is responsible
The data controller is the publisher of Schedule 1 Lab, identified in full on the legal notice.
For anything in this policy, write to hello@schedule1-lab.com.
What we collect
If you only use the tools
Nothing that identifies you. The calculators, the optimizer, the effect finder, the grow planner and the blueprint editor all run without an account.
We do collect anonymous usage statistics: pages viewed, time spent on a page, approximate country, referring site, device type. We also count which buttons get used - for example, how many people open the Discord from a given page. These are aggregated and cannot be traced back to an individual.
This measurement sets no cookie, stores no identifier that outlives your tab, never keeps your IP address, and sends nothing to a third party. That is why it runs without asking: it falls under the exemption for strictly statistical audience measurement. The consent banner covers advertising and Google Analytics, which are a different matter.
If you create an account
- Your email address, used to sign you in and to contact you about your account
- A hashed password, which means we cannot read it
- Anything you save: recipes, blueprints, notes, production chains
- Anything you publish to the community: shared recipes, shared blueprints, team posts
If you contact us
Whatever you put in your message, and the address you send it from.
The feedback button also sends the page you were on, your browser and device type, the Discord handle if you fill it in, and your account name if you are signed in - enough to reproduce a bug and to answer you. It goes to a private Discord channel, not to the database.
Advertising
We show ads through Google AdSense. Ad providers may set cookies and use identifiers to measure and personalise advertising. See “Cookies and advertising” below.
Why we collect it, and on what legal basis
| What | Why | Legal basis (GDPR Article 6) |
|---|---|---|
| Account email and password | Run your account, let you sign in | Performance of a contract |
| Saved recipes and blueprints | Provide the feature you asked for | Performance of a contract |
| Community submissions | Publish what you chose to publish | Performance of a contract |
| Anonymous usage statistics | Understand which tools get used and fix what breaks | Legitimate interest |
| Anonymous interaction counts | See which links and buttons actually get used | Legitimate interest |
| Advertising cookies | Fund the site | Consent |
| Support messages | Answer you | Legitimate interest |
You can withdraw consent for advertising cookies at any time through the cookie settings link in the footer.
Who else processes your data
We use a small number of service providers. They process data on our behalf and are bound by contract.
| Provider | What for | Where |
|---|---|---|
| Vercel Inc. | Hosting and delivery of the website | United States |
| Neon Inc. | Database hosting | United States (AWS us-east-1, N. Virginia) |
| Google Ireland Limited (Google Analytics) | Anonymous usage statistics | Ireland, with transfers to the United States |
| Resend Inc. | Account and transactional emails | United States |
| Google Ireland Limited (Google AdSense) | Serving advertising | Ireland, with transfers to the United States |
Where a provider is outside the European Economic Area, transfers rely on the European Commission's Standard Contractual Clauses or an adequacy decision.
We do not sell your data. We do not share it with anyone not listed above.
Cookies and advertising
Essential cookies keep you signed in and remember your preferences. The site does not work properly without them, so they are set without asking.
Advertising cookies are set by our ad provider to measure and personalise ads. If you are in the European Economic Area, the United Kingdom or Switzerland, we ask for your consent before any of these are set, and you can change your mind at any time through the cookie settings link in the footer.
Analytics are aggregated and do not identify you individually.
Our ad provider may use its own cookies and technologies. Google's handling of that data is covered by its own policy: policies.google.com/technologies/partner-sites
How long we keep it
- Account data: as long as your account exists, then deleted within 30 days of closure
- Saved recipes and blueprints: same as your account
- Published community content: stays public until you unpublish it or close your account
- Anonymous statistics: 14 months
- Support messages: 12 months after the exchange ends
Your rights
Under the GDPR you can ask us to:
- give you a copy of the data we hold about you
- correct anything inaccurate
- delete your account and everything attached to it
- export your saved data in a portable format
- stop processing your data on legitimate interest grounds
- withdraw a consent you previously gave
Write to hello@schedule1-lab.com. We answer within one month.
If you are not satisfied with our answer, you can complain to the CNIL, the French data protection authority, at cnil.fr.
Age
Schedule I is rated for mature audiences. Schedule 1 Lab is not directed at children, and we do not knowingly collect data from anyone under 16 years old. If you believe a child has created an account, write to hello@schedule1-lab.com and we will remove it.
Security
Passwords are hashed and never stored in readable form. The site is served over HTTPS. Access to the database is restricted and authenticated.
No system is perfect. If you find a vulnerability, please report it to hello@schedule1-lab.com before disclosing it publicly.
Changes
If this policy changes in a way that affects you, we will say so on the site. The date at the top always reflects the current version.