1. What this notice covers
Cookies are small pieces of information stored by a website. Similar technologies include local storage, native app keychain or keystore storage, caches, push identifiers and software libraries that store or access device information. This notice covers the public website and mobile app, including customers, tradespeople and landlords or holiday-home owners. Information about people appearing in uploads is covered by our Privacy Notice.
2. Our website
The website is hosted by Netlify and includes enquiry, waitlist, tradesperson-interest and job-interest forms. Hosting receives technical request information and submitted forms are processed through Netlify. Website forms are separate from the mobile app's area-availability waitlist.
With your prior marketing consent, the website uses the Meta Pixel to measure Facebook and Instagram advertising. Meta Platforms Ireland Limited receives advertising-measurement information. The Pixel loads only where a valid marketing choice has been saved as accepted; it does not load before that choice, on a rejected visit or on the /open app-link route. If you withdraw after previously accepting, future events stop and accessible Meta cookies are removed where possible, as explained in section 4. The mobile apps do not currently use Meta advertising or tracking technologies. A separate project is assessing Meta App Events for a future app release. If that changes, we will update this notice before app tracking begins. Necessary hosting, forms, authentication, payment security, diagnostics and requested map/location services are separate operational processing described in this notice. This does not mean third-party services use no cookies or device storage.
Meta Platforms Ireland Limited and WeeJobs are joint controllers for the collection and transmission of Pixel data, while Meta is a separate controller for its own later processing under its own privacy policy.
The Meta Pixel can set the first-party _fbp cookie, a browser identifier used to measure advertising, for up to 90 days. Where a landing URL contains a Facebook click identifier (fbclid), it can also set _fbc to associate that click with website activity, for up to 90 days. Meta's request handling receives technical information such as your IP address, browser information and the page URL, including permitted campaign parameters (utm_*) and fbclid. Other query parameters and URL fragments are removed before the Pixel loads.
We send fixed event names: PageView for page visits, AppStoreClick and GooglePlayClick for official store links, and Lead after a successful website form submission reaches its matching confirmation page. We do not send form contents, names, email addresses, phone numbers, addresses or job text to Meta, and do not use advanced matching or automatic event configuration. This does not make the technical information and browser identifiers anonymous.
We use first-party local storage to remember your accepted or rejected choice, its UTC ISO 8601 timestamp and the consent-policy version for up to 180 days. This consent record is separate from Meta's cookies and lets us apply your choice. If the record is missing, invalid, expired or for an older consent policy, the Pixel remains off until you accept again.
If you follow an Apple, Google, Stripe or other third-party link, that service can operate its own browser storage under its notice and controls. Browser settings can clear or restrict cookies and storage, which can affect sign-in or form behaviour.
3. Our mobile app
- Supabase login session and Expo SecureStore: keeps authentication and session tokens in native keychain or keystore storage. Sign out or request account deletion to manage the session.
- Local app preferences and AsyncStorage: stores selected onboarding area, notification settings and AI disclosure or withdrawal choices across app visits until changed or cleared. Withdraw AI permission in Privacy settings. Provider retention and device cache lifetimes are separate.
- Mapbox: provides maps and processes map, device and request information on map use. Its mobile SDK includes telemetry. See Mapbox's telemetry information for its controls.
- Expo notifications, Apple APNs and Google FCM: register delivery identifiers and deliver push messages according to device notification permission. App and device notification settings provide controls; push tokens and provider delivery records have separate lifetimes.
- Expo/EAS Update: checks for and downloads app updates using runtime, operating-system and randomised download information. No separate optional-update consent toggle is established in the app.
- Sentry: reports crashes, errors and technical context. Default personal-information attachment and logs are disabled, but error or breadcrumb context can still contain identifiers. No separate diagnostic-consent toggle is established in the app.
- Stripe and payment services: support payment entry and payment security or fraud prevention during relevant flows. Provider identifiers, usage and security records have separate lifetimes.
- Apple or Google sign-in and system browser: support the sign-in method selected. Provider-domain cookies and identifiers follow provider terms.
- Image and document pickers, caches and web content: handle selected files and linked content when used. Permission withdrawal does not erase previously uploaded material.
4. Separate choices and controls
Device permission for camera, photos, notifications or location controls access to those device features. It does not automatically authorise every vendor use or other storage technology. The AI-disclosure choice is per account and versioned; server permission is checked before estimates are processed. Availability or launch email choices are separate from push and AI choices.
SDK diagnostics, map telemetry, payment and update collection support the operational services described above. This notice does not establish that every runtime technology or future website technology has been inventoried. Optional website advertising measurement relies on consent. You can reject it and keep using the website, or change or withdraw your choice through Cookie settings in the footer. Withdrawal stops future Meta events and removes accessible Meta cookies, including _fbp and _fbc, where possible. It does not erase information already received by Meta. You can also contact privacy@weejobs.net.
You can clear browser storage, change device permissions and use available app or vendor settings. Clearing local preferences can remove remembered choices without erasing backend consent history or provider records. For an erasure or other privacy request, contact privacy@weejobs.net.
5. Contact
Questions about website or app storage and similar technologies can be sent to privacy@weejobs.net. See the Privacy Notice for suppliers, international processing, retention and rights.