Wantok Chat

Privacy Policy

This policy covers Wantok Chat and Wantok Transport. It describes verified backend processing and identifies implementation details that are not yet confirmed. It is not a guarantee of security, permanent deletion or legal compliance.

1. Responsible individual and scope

Wantok Chat is operated by Japhet Moses Kapak using the Jstaroma Technologies project/business brand. Jstaroma Technologies is not currently registered or incorporated as a company. "We" and "our" refer to that responsible individual.

The Android application is Wantok Chat, package identifier com.wantok.chat, built with Flutter. This notice covers app accounts, communications, community and transport features, and related support and administration. It does not replace the hosting website's own legal documents.

Contact [email protected] for support and privacy requests. This policy explains processing; it is not blanket consent. Feature availability and collection depend on the released app, choices and permissions.

2. Accounts and profiles

We process account identifiers, sign-in/account information and profile information you provide. Depending on the features you use, these can include email address, name, username, province, profile photo, description and account timestamps.

Supabase supports authentication and database storage, including information needed to establish and secure sessions. Do not send passwords or one-time codes to support.

Other users can see profile information relevant to the feature, such as a sender, group member or operator identity. Do not place identity documents, financial details or another person's confidential information in a public profile. Exact sign-in methods and optional/required fields can vary by release; no universal identity or age-verification claim is made.

3. Messages, media and groups

Wantok stores message content and conversation/account identifiers, timestamps and relevant message state to provide communications. Supported media can include images, files, voice notes and other attachments. Group details, membership/roles, connections, reports and blocking/privacy preferences also support these features.

Recipients and group members can copy or retain content outside Wantok. Discoverable profiles/groups have a different audience from a private conversation. Hiding or removing content from a screen does not prove permanent deletion from every device or backend copy.

The backend currently includes public chat-media storage. A publicly retrievable media URL may allow someone who obtains it to access the file without joining the conversation. Do not assume all attachments are restricted by conversation membership. The released app's precise media-delivery paths have not yet been fully verified.

4. Calls, notifications and technical data

LiveKit supports audio/video calling. Calling involves participant/session identifiers and network/connection information; microphone and camera permissions are needed for corresponding media. The backend also has call and call-join records.

Production recording settings, detailed call-log retention and encryption configuration have not yet been verified. This policy does not state that calls are never recorded or that they are end-to-end encrypted. Other participants can independently record or retain communications.

The app and infrastructure providers can process network addresses, request times, device/operating-system details, app versions, errors and security events in providing the service. The exact diagnostic collection enabled in the released app remains unverified.

Device notification tokens are represented in the backend. Firebase is configured, but the active production Firebase services, push payload contents and lock-screen exposure have not yet been confirmed. Configuration alone does not establish that Firebase Analytics, Crashlytics or Performance collection is enabled.

5. Location and optional features

Earlier app disclosures described People Nearby, Google sign-in and translation. Their current production behavior, location precision/background use, contact-book access and translation provider have not yet been verified. This policy does not claim that these features collect no data or that every planned feature is active.

Where location or another optional feature is offered, review the feature explanation, recipient visibility and device-permission request before using it. Do not assume precise location is hidden from every recipient. Device permission is not a substitute for other permissions required by law.

Active third-party data flows must be reflected in the policy as they are verified. We do not make a blanket "no tracking", "no contacts access" or "no analytics" promise based on incomplete app evidence.

6. Operator information and documents

Transport applications include operator/account identifiers, business/display name, contact phone, province, operating area, description, status, review note and registration/review/update times. Vehicle records include registration number, vehicle type, passenger capacity, name, color, description, status and visibility/registration-vehicle flags. Routes, stops and fares support route management.

Private backend storage buckets exist for transport registration documents and business photos. Exact document requirements, released upload channels, reviewer access and document retention have not yet been verified. Private bucket settings alone do not prove that every upload or signed-URL endpoint is correctly authorized.

Use designated application channels for requested documents. Do not send unrelated personal information or another person's documents without authority, or place registration documents in public profiles or ordinary chat.

Published business numbers and passenger-visible vehicle/trip information can be viewed and copied outside Wantok. A business number may still identify an individual. Provide only a number you are authorized to publish; exact audience and visibility controls depend on the released feature and are not yet fully verified.

7. Trips, reservations and transport messages

Trip records include operator/vehicle references, origin/destination, province, departure date/time and timezone, pickup details, intermediate stops, information, capacity, fares, status and timestamps.

Reservations include a reference, passenger account reference, trip and boarding/alighting stops, seat quantity, fare per seat, status and timestamps. One reservation can cover multiple passengers; the verified schema records a seat quantity rather than a separate identity for every passenger.

Booking notices and passenger/operator chat-contact links support journey communications. Relevant trip/booking information may be available to the operator or passenger to arrange travel. The exact released display and any additional passenger-contact collection have not yet been verified.

Cancellations affect availability and statistics. Recorded fares are not proof of payment. No payment-card, payment-processing or settlement collection is asserted here without verified implementation.

Transport-message deletion is not verified. A trip ending, expiring, being cancelled or becoming hidden does not establish that associated messages are erased. No five-day deletion promise is made.

8. Purposes and permissions

Where applicable law requires a legal ground, it must match the activity: provision of a requested service/contract, an appropriately balanced lawful operational or security interest, a specific legal duty or valid consent where required. This policy does not create a legal ground itself. Acceptance of Terms is not consent for unrelated optional tracking or disclosure.

9. Who can see information

Recipients depend on the feature: communication/group participants; viewers of profiles, discoverable groups or published transport information; operators/passengers needing journey information; authorized support, safety and administrative personnel; infrastructure/feature providers; and recipients you authorize.

Limited disclosures to professional advisers or competent authorities may be necessary on a lawful basis. Requests must be evaluated rather than treated as automatically valid. Public business information is different from private application material; registration documents are not intended as public trip attachments.

No advertising or data-sale integration was identified in the reviewed website/backend integration, but the app SDKs and all business practices have not been fully verified. This is not a service-wide "no sale" or "no advertising sharing" guarantee.

10. Administration and analytics

The Jstaroma portal uses separately authenticated administrator accounts and server-side authorization. It is not a public analytics feed. Aggregates include usage, operator registrations, trips, reservation counts, seats, route popularity and occupancy. Cancelled reservations are excluded from occupied-seat calculations under backend rules.

Operator management includes necessary business/contact, review, vehicle and route details. The reviewed dashboard responses do not expose passenger account identities, private registration-document links or payment-card data. Small aggregate counts can still identify people in context.

Operator decisions and trip moderation record administrator identifiers, affected record identifiers, status changes, reasons and times for accountability and dispute/safety handling. Decisions can affect live trips and reservations. These verified administrative analytics must not be confused with unverified Firebase Analytics collection.

11. Providers and international processing

Supabase provides authentication, database, storage and server-side administration infrastructure. LiveKit supports calling. Firebase is configured, but its active production services remain unverified; Google sign-in, notifications, Analytics, Crashlytics and Performance must not be treated as interchangeable.

Cloudflare/GitHub and website resource CDNs deliver public policy/website pages. Website delivery includes observed Cloudflare performance telemetry. This does not mean those website providers receive every app message.

Actual database, storage, backup, calling and diagnostic processing regions have not yet been confirmed. Providers may process information outside Papua New Guinea; PNG-only storage is not promised. Applicable transfer safeguards and notices must reflect the actual arrangement. Active translation, email and any payment-provider processing also require verification before specific claims can be made.

12. Security and limitations

The reviewed administrator integration uses HTTPS, authenticated server checks, administrator membership authorization, restricted administrative function execution, validated response fields and atomic transport-decision auditing. Privileged database credentials remain server-side in that integration.

Transport registration-document and business-photo buckets are private with restrictive direct-client policies. Public avatar, group-avatar and chat-media storage has different exposure. Not every app endpoint, signed URL or upload path has been audited.

No system guarantees prevention of all unauthorized access or disclosure. No security certification, end-to-end-encryption or permanent-erasure guarantee is made. Protect your account/device and avoid sharing unnecessary sensitive information.

13. Retention

Specific retention periods and automated deletion schedules have not yet been verified. This applies to accounts/authentication logs, messages/media, call diagnostics, applications/documents, trips/reservations, decision audits, safety/support records and provider backups. No fixed number of days is promised.

Retention should be limited by the record's purpose, the service relationship, a specific legal requirement and proportionate safety, security, fraud or dispute needs. These criteria do not justify retaining everything indefinitely. Contact us for the current handling of a particular record or deletion request.

Trip expiry, hidden content or a temporary interface is not proof of deletion from storage, recipients, logs or backups. Provider backup rotation and restoration behavior remain unverified.

14. Account and operator-profile deletion

Send account-deletion requests to [email protected]. We may require proportionate account-ownership verification. Do not send passwords, one-time codes or unnecessary identity documents.

Earlier guidance describes Settings > Delete account. The released control and its complete backend effects have not yet been verified. Contact support if an option is unavailable or you need confirmation of what was removed.

Operator-profile removal is separate from full Wantok account deletion. Its availability and effects on documents, approval history, public trips, reservations and communications require verification. Neither operation should be assumed to erase all records or other users' copies instantly.

Limited retention may be required for a specific legal duty or justified safety, fraud or dispute purpose. Applicable exceptions and handling should be explained for the request. A deletion request does not automatically cancel an imminent journey or refund a payment; use the relevant cancellation/support process too.

15. Choices and privacy requests

Use available profile, privacy, notification, blocking/reporting, group and device-permission controls. Exact controls and any export feature depend on the released implementation; no unverified settings path or export capability is guaranteed here.

Depending on applicable law, you may request access, correction, deletion, a copy, restriction, objection or withdrawal of consent for processing based on consent. Legal exceptions and others' rights may limit a request. You may contact a competent regulator or seek another available remedy.

Email [email protected] with relevant account details and the action requested, not credentials. We will apply appropriate verification and applicable response requirements. Withdrawing device permission does not automatically erase earlier server records; withdrawing consent does not make earlier lawful processing unlawful.

16. Children and safety

Wantok is an adult-only service for people aged 18 or older. This does not guarantee that information about a minor is never received, especially in safety reports.

If we learn of an underage account or potential child exploitation, we assess the report, restrict access where appropriate and handle information in accordance with applicable safety/legal duties. Relevant evidence may need preservation or lawful disclosure. Use reporting tools or support without redistributing illegal material. In immediate danger, contact appropriate local emergency services.

17. Changes and contact

Updates will carry a version and effective date. Material changes will receive an appropriate service notice, with additional consent or other steps where required. The canonical website version is identified in our policy version record.

Responsible individual: Japhet Moses Kapak, using the Jstaroma Technologies brand. Support, safety and privacy contact: [email protected]. See the Wantok Chat Terms of Use.