Patten Labs

Privacy Policy

Last updated: September 30, 2026 ยท Ontario, Canada

1. Who we are

Patten Labs ("we", "us") in Ontario, Canada, provides Crew Card. This Privacy Policy describes personal information this application collects, stores, or sends, as implemented in this codebase. We do not claim that processing stays in Canada.

2. Account and sign-in

When you register or sign in, Crew Card uses Base44 authentication. The app stores and uses your email address, name (full_name or name), and role (admin or user). Registration also collects a password, which is submitted to Base44 auth and is not stored as a field on our User entity. You may sign in with Google. Email verification sends a one-time code to your email. Password reset sends a reset link to the email you enter.

When you accept these Terms in the app, we store tos_accepted_at (date and time) and tos_version (the terms version id) on your user record so we know you agreed, and which wording you agreed to.

3. Team and company records

Workers: display_name, user_email, phone, role (worker, crew_lead, or admin), pin_required, has_pin, active, invited_at, joined_at, and company_id. These identify who is on the crew, send invites, and control access.

Private worker fields (visible to account owners): phone, pay_rate, and a hashed PIN plus pin_fails and pin_locked_until used to verify and lock the PIN. The PIN itself is stored hashed, not as the digits you typed.

Company: name, timezone, currency, rounding_minutes, business_hours_start, business_hours_end, open_shift_threshold_hours, work_tags, pay_period_start, pay_period_days, trial_ends_at, subscription_status, stripe_customer_id, stripe_subscription_id, and subscription_period_end. These run the account, trial, and billing status.

4. Clients, jobs, and schedules

Clients: name, address and address parts (address_line1, address_line2, po_box, city, province, postal_code, country), contact_name, contact_phone, default_rate, color, lat, lng, notes, and active. Owners enter these so crews can find the site and so hours can be billed.

Jobs and job tasks: name, notes, status, and who completed a task (done_by_id, done_by_name, done_at).

Schedules and visits: name, frequency, weekday, start_date, crew_ids, crew_names, notes, due_date, visit status, and who marked a visit done.

5. Time records and location

Time entries store worker_id, worker_name, worker_email, client and job identifiers and names, crew_session_id, crew_lead_id, crew_lead_email, crew_names, status, clock_in, clock_out, break_minutes, duration_hours, work_summary, description, work_tags, entry_source, flags, reviewed, billing_status, billed_at, billed_by, invoice_reference, payroll_status, and payroll_period_label.

If the device allows it, clock-in and clock-out also store clock_in_lat, clock_in_lng, clock_in_accuracy, clock_out_lat, clock_out_lng, and clock_out_accuracy. If permission is denied or GPS fails, the entry stores clock_in_location_unavailable and/or clock_out_location_unavailable. Location is requested only at clock-in and clock-out, not continuously.

Crew sessions store the lead, client, worker ids and names, start, end, and work_summary. Audit logs store who changed a time-entry field, the old and new values, and a timestamp.

6. Payments

Owner subscriptions are processed by Stripe. Checkout sends the owner's email, the company name, and the company id to Stripe, and stores stripe_customer_id, stripe_subscription_id, subscription_status, and subscription_period_end on the company. Card numbers are handled by Stripe; this application does not store a full card number.

7. Email

The app sends email through Base44's SendEmail integration: a welcome email when a worker first joins, a welcome email when an owner creates a company, an invite when an owner adds a worker email, and copies of contact-form messages and in-app suggestions to users with the admin role. Sign-in also uses Base44 auth emails for one-time codes and password-reset links. This repository does not name the email vendor behind that integration.

8. Help, contact, and suggestions

The public Contact page collects name, email, and message, stores them on a Suggestion record (from_name, from_email, text, status), and emails admin users.

Signed-in users can submit a suggestion (text plus their name and email) the same way.

The in-app help "Ask" feature sends your question (up to 300 characters) and the in-app manual to Base44's InvokeLLM integration and returns an answer. This repository does not name the underlying model provider. We do not know whether that provider keeps the question or uses it for training.

9. Maps and address lookup

When an owner types an address, the app may send that text to Photon (photon.komoot.io) for autocomplete and to OpenStreetMap Nominatim for geocoding, then store lat and lng on the client. The owner map loads map tiles from Esri ArcGIS.

10. Browser storage

The app stores a signed-in worker snapshot (id, display_name, role, email, whether a PIN is required) in localStorage as ft_me, plus theme (ft_theme), tutorial and add-to-home flags, and whether the help panel is open. Base44 auth tokens are stored in localStorage (base44_access_token and token). PIN unlock is kept in memory for the session. This repository does not set advertising cookies. A sidebar cookie exists in an unused UI kit file and is not used by Crew Card screens.

11. Uploads, advertising, and analytics

This application does not provide file or photo upload. We found no advertising SDK and no named analytics vendor (such as Google Analytics) in application source. The Base44 Vite plugin has an analyticsTracker option enabled; this repository does not show what that option collects or where it sends data.

12. Who can see information

Account owners can see team, time, client, and billing records for their company. Workers see their own hours and the client details needed to do the job. Stripe receives billing information described above. Address text may be sent to Photon and Nominatim. Help questions may be sent to Base44 InvokeLLM. Emails are sent through Base44 SendEmail. Google receives information needed if you choose Google sign-in. The app loads the Manrope font from Google Fonts (fonts.googleapis.com). We may also disclose information where required by law.

13. Retention

This repository does not implement an automated deletion or retention schedule for accounts or time records. Owners can edit or deactivate workers, edit entries, and delete sample (is_seed) data. Records otherwise remain while the service is used. If you want information deleted, contact us at the email below.

14. Access, correction, and complaints

You may request access to the personal information we hold about you, ask for corrections, or raise concerns by emailing info@patten-labs.com. If you are not satisfied with our response, you may contact the Office of the Privacy Commissioner of Canada (priv.gc.ca).

15. Changes

We may update this Privacy Policy. The current version is posted in the app.

16. Contact

Privacy questions: info@patten-labs.com. Patten Labs, Ontario, Canada. Last updated: September 30, 2026.