Dingo Dispatch
Latest dispatch

Dingo Dispatch · Policy draft

Privacy Policy

This working draft describes the information requests and handling visible in the current Dingo Dispatch app. Details that the code and available research do not establish are called out for owner confirmation below.

Draft — owner review required

This wording is not approved policy or legal advice. The owner must review and confirm the open details before publication as final terms.

Information the current forms request

The newsletter form asks for your email address and requires an unchecked-by-default affirmative consent box before it can be submitted. The account sign-up form asks for your name, email address and password. Creating an account does not itself select the separate newsletter consent box.

For a newsletter signup, the app records the email address, consent time and subscription state, and creates a token used by the one-click unsubscribe link. The account system handles the information entered in its sign-up form.

How the app uses that information

The current newsletter flow uses the submitted address to create or update a newsletter subscription, send a welcome email and deliver newsletter issues to active subscribers. It also records the signup for an owner notification through the configured submission or email service.

The account form passes its name, email and password to the installed account service to create an account. The app does not treat account creation as newsletter consent.

Newsletter preferences

Newsletter enrollment requires your express choice. Each newsletter email includes a one-click unsubscribe link that works without signing in. Using it marks the newsletter subscription inactive. That action changes the newsletter preference; it is not, by itself, a request to delete an account or all information held about you.

Services and technical information

The current app stores newsletter records in its database and uses the installed Better Auth, Polsia email and Polsia submission services for account and email workflows. The code also includes an optional page-view beacon: when configured for a deployment, it stores a random visitor identifier in browser local storage and sends the identifier with a configured site slug to the beacon service.

The available app information does not establish the hosting locations, full provider or subprocessor list, data-transfer destinations, retention periods, or the exact information recorded by hosting logs. The owner must confirm these details before approving this policy.

Access, correction, deletion and questions

Proposed request route: contact dingo-dispatch@polsia.app to ask about information associated with your address or request access to, correction of, or deletion of that information. The owner must confirm that this inbox is monitored for privacy requests and document the identity checks, response process, applicable retention exceptions and complaint-handling steps before publication.

Owner confirmation required before publication

The available app information does not establish the following details. They remain open questions for owner review, not statements of current policy:

  • The responsible legal entity, its contact details and which privacy laws apply.
  • Whether analytics or other cookies, browser storage, server logs or diagnostics are enabled, and the data and retention involved.
  • The complete provider and subprocessor list, hosting regions and any overseas disclosures.
  • Retention and deletion schedules for account and newsletter records, plus access and correction procedures.
  • How privacy complaints are reviewed and escalated, and the security and incident-response practices that may be described.
  • Whether the service is intended for children or handles any sensitive information.
Terms draftBack to Dingo Dispatch
PrivacyTerms