COOKIE POLICY
What this browser can remember when you use ScheduleFlowLab.
This policy explains cookies, local storage, session storage and similar technologies used for ScheduleFlowLab features, optional accounts, consent choices and advertising when enabled.
BROWSER TECHNOLOGIES
Cookies and local storage are not the same.
A cookie is a small record that a website or service can ask a browser to store and, depending on the cookie, send with later requests. Local storage keeps data in the browser and is not automatically attached to each web request. Session storage usually lasts only for a browser-tab session.
This policy uses browser storage as a broad description covering cookies, local storage, session storage and comparable client-side mechanisms. Deleting cookies alone may not remove local-storage data.
A schedule stored locally is different from a schedule deliberately saved to an optional cloud account. Read this policy with the Privacy Policy .
STORAGE CATEGORIES
Purpose is more reliable than a brittle list of key names.
Names and durations can change when a builder, WordPress component or provider is updated.
| Category | Mechanism | Purpose | Typical duration |
|---|---|---|---|
| Guest schedules and tool state | First-party local storage | Restores compatible entries, settings or templates in the same browser. | Until replaced, deleted or site/browser data is cleared. |
| Preferences and compatibility | Local or session storage | Remembers interface choices or migrates compatible data from an earlier tool version. | Session-based or persistent, depending on the feature. |
| Account authentication | Supabase session storage, cookies or local storage | Keeps a valid optional sign-in, refreshes the session and supports account security. | Until sign-out, expiry, revocation or site data is cleared. |
| WordPress, hosting and security | Cookies, logs or similar storage | Delivers pages, supports administration, protects the site and prevents abuse. | Varies by component, configuration and security need. |
| Consent choices | Cookie or local storage | Records choices made through an active privacy or advertising consent interface. | For the configured period or until the choice is changed. |
| Advertising and measurement—when enabled | Cookies, local storage and similar identifiers | Supports ad delivery, measurement, frequency controls, fraud prevention and permitted personalization. | Varies by provider, consent, configuration and applicable requirements. |
Your browser’s privacy or developer tools can show cookies and site storage for scheduleflowlab.org. Do not share authentication-token values or private schedule contents.
WHY STORAGE EXISTS
Storage supports requested functions and optional services.
Local continuity
Compatible autosave can restore guest work in the same browser after a refresh or return visit.
Account sessions
Authentication storage lets a valid optional session continue without entering credentials on every page.
Compatibility
Legacy keys can help an updated tool recover compatible data from an earlier local format.
Website operation
WordPress, hosting and security components may use storage to administer, deliver and protect the website.
THIRD-PARTY SERVICES
Connected services can use their own technologies.
Supabase
Optional authentication and cloud features can persist session information in the browser.
Privacy notice ↗Google sign-in
If selected, the browser communicates with Google, which may use cookies or similar technologies under its own settings.
Google cookies ↗Google advertising—when enabled
Google and approved vendors may use cookies or similar signals for ad delivery, measurement, fraud prevention, frequency controls and permitted personalization.
Advertising information ↗WordPress, hosting and security
Active components may set operational storage needed to deliver, administer or protect the website.
NON-ESSENTIAL TECHNOLOGIES
A clear choice is required where applicable.
When Google-served ads or another non-essential measurement service is active, applicable providers may read or write cookies, local storage or similar identifiers. Behavior depends on region, consent, account settings, configuration and provider rules.
Where prior consent is required, non-essential technologies should not activate until the visitor’s choice is collected. Google-served ads shown to visitors in the European Economic Area, United Kingdom or Switzerland require an appropriate Google-certified consent management platform integrated with the IAB Transparency and Consent Framework.
Functional storage used to provide a requested feature is described separately so it is not confused with optional advertising or measurement.
YOUR CONTROLS
Changing storage can change how the site works.
Use the displayed consent control
When available, use it to accept, reject or change the non-essential purposes managed by that control.
Clear site data
Removing cookies and local storage can sign you out and permanently delete schedules stored only in that browser profile.
Block browser storage
Browser restrictions can prevent autosave, session restoration or other storage-dependent functions from working.
Keep a backup first
When a tool offers CSV, JSON, calendar or another export, save needed work before clearing site data.
COOKIE OR STORAGE QUESTION
Send the page and browser context—never a stored token.
Use the Contact page or email contact@scheduleflowlab.org . This policy may change when tools, account features, providers or consent requirements change.