Draft for attorney review. This is not legal advice and it is not a finished policy.
Privacy Policy (draft)
Draft for attorney review. This is not legal advice and it is not a finished policy. TailgateLog has not had this text reviewed by counsel.
Who we are
TailgateLog is a record-keeping service for California construction safety meetings. The operator of this site is the company that hosts TailgateLog. Contact sales@tailgatelog.com for privacy questions.
What we collect
Account data: name, email, password (stored as a hash or by the auth provider), role, and language.
Company data: company name, city, trade, CSLB license number and class if you enter them, and a short IIPP cover note if you enter one.
Crew and job data: crew names, job names, addresses, ZIP codes, and coordinates used to read weather.
Meeting data: the talk, the date, notes, corrective actions, who signed, and signature images.
Incident data: what you type in a report, optional photos, and an optional phone location if the person filing the report turns that on.
Billing data: if Stripe is configured, Stripe stores the card. TailgateLog stores the Stripe customer id, the subscription status, and the plan. We do not store full card numbers.
Technical data: the auth session cookie, and provider logs from hosting, email, or SMS if those are turned on.
How we use it
We use this data to run the log, show the right language, send reminders you turned on, read heat and smoke for a job, and bill the company plan. We do not sell personal information.
Who else sees it
People in your company see what their role allows. A foreman sees their crew. Owners and admins see the company.
Processors, when configured: Supabase for accounts and file storage, Stripe for payment, and the email or SMS provider for reminders. Weather readings come from public forecast services. Those services receive the job location, not the crew roster.
An inspector or a general contractor sees a packet only if someone in the company exports it and hands it over.
How long it stays
Meetings are not deleted by the product when a plan changes or a subscription is canceled. Keep exports for your own retention rules. Title 8 section 3203 requires training documentation for at least one year. You can ask sales@tailgatelog.com to close a company account. Closing an account is a manual request until an in-app delete exists.
Security
Access is limited by role. The database policies use the auth app metadata, not a field the user can edit in the browser. No method of transmission is perfectly secure.
Children
TailgateLog is a workplace tool. It is not directed at children.
California
This draft does not claim a particular exemption under the CCPA or CPRA. Ask counsel before you rely on it.
Changes
When this draft is replaced by a reviewed policy, the date at the top of that policy will change. The copy on this page is the current draft.