Privacy Policy
Version 2026-11-03.1 · Effective November 3, 2026
Forebot is operated by JeffCo Industries, LLC.
1. Who is responsible
JeffCo Industries, LLC ("we", "us") operates Forebot at forebot.cloud and is responsible for the information described here.
2. What we collect
- From Google, when you sign in: your email address, your name and your Google account identifier.
- About your account: when you created it, when you last used Forebot (recorded at most once an hour), which versions of our Terms and this Privacy Policy you accepted, and that you confirmed you are at least 18.
- Your workspace: the properties, jobs, field evidence, tasks, materials, equipment history, photos, documents and reports you add.
- If you start signing in with Google but do not confirm your age and accept our Terms and this Privacy Policy: Forebot creates no account and keeps nothing from your Google account except a one-way fingerprint (a SHA-256 hash) of your Google account identifier, the identifier Supabase gave that attempt, and when it happened. We keep these only to delete that attempt's sign-in record at Supabase and to check that the deletion finished.
- Request logs: our hosting provider records technical details of each request, such as its time, the path requested, the response status, your IP address and approximate location, and your browser's user agent. Forebot's own log lines add your account identifier. They never contain your email address, your sign-in tokens or your cookies.
3. How we use it
We use this information only to sign you in, to run your workspace, to keep Forebot secure, and to meet our legal obligations. We do not sell your information, we show no advertising, and Forebot has no third-party trackers or analytics.
4. Where it is kept
Forebot runs on Cloudflare: your account and workspace records are stored in Cloudflare's D1 database, and your photos and documents in Cloudflare's R2 storage. Sign-in runs through Supabase, which holds the profile details Google shares when you sign in (your email address, name, profile picture link and Google account identifier), your sign-in sessions, and a sign-in audit log that includes IP addresses. Google confirms your Google account when you choose to continue with Google. Our subprocessors page lists each of them and what they process.
5. Cookies
Forebot sets only the cookies that sign-in needs: your session cookies, and short-lived cookies that protect a sign-in while it is in progress. Page scripts cannot read them, and they are never used for advertising or analytics. Google and Supabase set their own cookies on their own sites while you sign in.
6. How long we keep it
We keep your account and workspace for as long as your account exists. When your account is deleted, we delete your workspace records, photos and documents, and your user record at Supabase. Request logs expire under our hosting provider's log retention.
7. Your choices
You can export a job's record from within Forebot. A full export of your workspace, and deletion of your account, are available on request until self-service tools for them are released. Requests go to the support address in the Contact section of this page.
8. Security
Forebot is served only over HTTPS. Your session cookies are HttpOnly, every request's session is verified with Supabase, and every record is scoped to the account that owns it.
9. Age
Forebot is not for anyone under 18. We do not knowingly keep information about anyone younger.
10. Changes to this policy
When this policy changes, we publish a new version with its effective date and ask you to accept it before you continue to use your account.
Contact
Our support and legal email addresses will be listed here as soon as their mail routing is live.