Privacy Policy

1. What the app receives

• Account and sign-in data: name, email, optional profile image, password-account data, email-verification state and records, sessions, and the optional IP-address and user-agent fields on session records.
• Profile and preference data: resident/helper role information, profile and helper details, helper service area, and home-island preference. If a phone-verification record exists, it includes a phone number and verification state. The app's current SMS adapter is unavailable, so a new verification attempt cannot currently deliver a code or create a new verification record. Helper profiles can also include work photos and their labels or captions.
• Marketplace data: job descriptions, categories, timing, service area, island, neighborhood, access notes, recurring and scheduled-job records, approximate and exact location fields, job photos and captions, bids and bid notes, participant messages and optional message images, completion records, reviews and ratings, blocks, and job reports.
• Job payment-tracking data: whether a job's payment is pending or marked complete, and an optional receipt reference. These are marketplace recordkeeping fields; this notice does not describe payment-card handling.
• Contact and pilot feedback submissions: the public contact route stores a name, email, message, and timestamp. The pilot-feedback form uses that same contact/submission path and includes the form responses in the message.

The current app does not describe a profile or verification state as a license, identity check, background check, or insurance verification.

2. How information is used

KōkuaLocal uses these records to create accounts and profiles, authenticate members, support email verification, expose the phone-verification flow used by bidding, help residents and helpers discover and coordinate jobs, deliver participant messages, process bids, send bid and message notifications, record completion and recurring work, display reviews and ratings, support blocking and report moderation, and receive contact or pilot feedback. Phone verification is currently unavailable because the SMS adapter is not connected.

After the contact route stores a submission, it attempts to record it in the dashboard submission flow. If that platform recording path does not record the submission or fails, the configured company inbox can receive a best-effort notification. Neither path is a promise of delivery or a response time.

3. Who can see information

The app uses different projections for anonymous visitors, public profiles, and authenticated participants. An anonymous open-job listing can show selected job details such as the description, category, service area, island, neighborhood, timing, schedule, photos, and an approximate location. It does not return the exact job location in that public projection.

Public helper and resident profiles can show selected profile fields, names and images, email-verification status, helper work photos, job details, and public reviews or ratings. These projections do not make every account or marketplace field public.

• Exact job-location details are available to the person who posted the job and to the accepted helper for an accepted or completed job when the existing accepted-bid rule allows it.
• Participant messages, including optional message images, stay within the existing participant access checks.
• Blocks, bids, reports, and other member actions are handled by their existing authenticated and moderation checks rather than by the public job projection.

4. Photos, maps, email, and browser storage

• Uploaded profile, job, helper-work, and message photos use the configured Polsia R2 proxy. The resulting URLs are stored and displayed by the relevant marketplace flows.
• Map components load map tiles from OpenStreetMap.
• Email verification and marketplace notifications use the installed email proxy.
• The job-discovery island preference can be stored in browser local storage. For a signed-in member, the preference is also stored in the app database.
• If the deploy sets POLSIA_ANALYTICS_SLUG, the framework visitor beacon creates or reuses the local-storage visitor id polsia_vid and sends a page-load request to the Polsia beacon endpoint, using the configured API base when one is provided. This behavior is conditional on that deployment setting.

This notice does not turn those implementation references into a complete provider or subprocessor disclosure and does not specify their storage duration, processing location, or transfer mechanism.

5. Member controls

Depending on the member role and job state, members can edit profile information, profile and job photos, helper-work photos, and the home-island preference; sign out; submit or withdraw applicable bids; coordinate schedules and recurring arrangements; complete jobs; review or rate completed work; block or unblock another participant; and submit a job report. The app applies participant checks to job, message, and exact location access.

The current app does not provide self-service account deletion, a data-export flow, a privacy-request workflow, or a published retention schedule. No verified public privacy contact destination or request workflow is published in the current app.

6. Demonstration content

Demonstration content may contain fictional, display-only residents, helpers, jobs, bids, and reviews. It is separate from live member accounts and marketplace activity and is not a real person, transaction, endorsement, or historical record.

7. Details not specified by the current app

The current app does not specify the legal operator or address, an effective or last-updated date, legal bases, retention periods, an account deletion or closure process, a privacy-rights request process, cookie or analytics preference and opt-out behavior, a complete provider or subprocessor disclosure, processing locations or cross-border transfer terms, or a response-time commitment. It also does not specify practices about sale or rental of data, advertising, biometrics, background checks, insurance, or payment-card handling.

Those details require confirmation before they can be stated as commitments in this notice.