Privacy and data

TossIt program interest

If you choose to save local program interest, we store your name, email, ZIP code or city and state, consent version and submission time. Authorized TossDock owners and managers use these requests for local launch review and permitted follow-up. For Mission alerts, we also store your cell phone number, whether you drive a truck, and affirmative text-message consent so we can alert you when a Mission is available in your zone and coordinate approved dumpster drop-off help. Message frequency varies. Message and data rates may apply. Reply STOP to opt out or HELP for help.

Records remain until an authorized owner removes them; no automatic deletion schedule is currently configured. To withdraw consent or request removal, contact team@tossdock.com with your email or receipt reference. Request protection stores short-lived keyed counters rather than your raw IP address in the program-interest record.

What this covers

Two applications, built by TossDock and operated with one qualified local operator per approved zone. Both are Beta: neither has been submitted to an app store, and a Beta build with no operator service connected says so on its own home screen rather than pretending to be connected.

Website and partnership inquiries

When you submit an inquiry, TossDock stores the contact and operating details you enter, your selected service, and campaign attribution supplied with the page link. Authorized commercial staff use these records to review fit and respond to your request. Abuse controls retain limited request metadata; inquiry details are not an advertising profile.

The receipt confirms storage. A scheduling link, if offered, opens the configured scheduling provider. A fixed inquiry retention period has not yet been adopted; request access, correction or deletion through support. Necessary correspondence and agreement records may be retained under the applicable business policy.

What TossIt collects

TossIt is the public application. It is a photo-first way to get approved access to a container already placed in the local operator’s network, to report litter, and to take part in verified Toss Force cleanup work.

What TossDock Pro collects

TossDock Pro is the operator application, used by an operator’s own dispatchers, drivers and owners. It collects no consumer photographs and no payment data at all.

Photographs, and what “evidence” means here

A photograph in TossIt is not a memory — it is the record a quote and a verification are built on. That is why the applications ask for specific ones: what you are getting rid of, the same spot afterwards, the cleaned area, the disposal, the receipt.

• Capture is prompted. The application asks for one photograph at a time and the camera is not used except at that moment. Nothing is recorded continuously or in the background.
• If camera access is denied, you can choose a photograph you already took instead. Only the photographs you pick are read.
• A photograph you submit is reviewed by a person at the local operator before it changes anything — an access decision, a Mission outcome, a reimbursement.
• The public Clean Zone map shows rounded pins only, at roughly a kilometre, and never the identity of whoever reported the site.

Location

You can decline location and type an address instead; distance to the nearest eligible container is shown before any price either way. There is no background-location feature in either application, which is why the permission that would allow one is on the refused list below.

Card details

Card details are entered inside Stripe’s own hosted payment fields and never reach TossIt, TossDock Pro or TossDock. What is kept is a reference to the payment, which is what makes a receipt and a refund possible. The local operator is the merchant of record on their own connected Stripe account.

Who else is involved

Both applications load some code and content from origins other than their own. This is the complete list, and it is the same list the applications’ Content-Security-Policy is generated from.

Permissions

TossIt asks for

TossDock Pro asks for

Neither application ever asks for

This list is enforced rather than intended: the script that writes the native permission files refuses to run if one of these turns up in a generated project, so a permission that reappears is something somebody has to explain rather than something that lands quietly in a build.

How long things are kept

On the phone itself, drafts and queued uploads are encrypted at rest under a key the device will not export, and they exist so that work done without a signal is not lost. No sign-in token and no raw card detail is written to ordinary browser storage.

Where a period is not stated above, it is because it is not settled: how long a local operator holds a completed record follows that operator’s own retention policy and any legal, tax, accounting, fraud, safety or dispute obligation that applies to it, and that wording is still subject to legal review. This page states what is known rather than a number that would have to be corrected later.

Deleting your account

Deleting your account removes your profile, your contact details, your saved drafts, and the photographs attached to submissions that have not been completed. It cannot be undone.

What may still be held afterwards, and on what basis — stated before you start rather than afterwards:

• Completed disposal records and their receipts may be retained by the local operator where a legal, tax, accounting, financial, fraud, safety or dispute obligation applies.
• Verified cleanup evidence attached to a completed Mission may be retained as the record that the work was done, including where a reimbursement or a sponsorship depended on it.
• The period anything is held for follows the local operator's retention policy and remains subject to legal review, so no fixed period is stated here.

Who these applications are for

Neither application carries user-to-user messaging, public user profiles, purchasable consumables or anything resembling gambling. Toss Force Missions carry a safety class, and a restricted Mission cannot be claimed by somebody who is not authorised for it. Anything a person submits is reviewed by the operator before it affects a decision.

Changes to this page

The date at the top changes when the content does. Because the rows here are generated from the same constants the applications render, a change to what an application collects shows up on this page in the same commit or fails the build — that is the point of writing it this way rather than maintaining a document alongside the code.

Questions about anything on this page go to support.