Your payout file stays in your browser.
Effective November 11, 2026. This page explains what DeliverPayout stores, what it never receives, and what changes if you create an account or allow advertising cookies.
- On the free tier, driver files and payout data are processed in your browser, not sent to DeliverPayout.
- There is no account and no server-side copy of your dataset unless you choose to create one.
- If you subscribe, we store your account details and payment status — never your card number.
- DeliverPayout uses no analytics and sets no tracking cookies of its own.
- Google AdSense may use advertising cookies if you accept advertising.
- You can clear your data or change your consent choice at any time.
1. Who this policy covers
This policy describes how DeliverPayout (“DeliverPayout”, “we”, “us”) handles information when you use the website at https://deliverpayout.com and the payout review tool available on it. DeliverPayout is the controller of the limited information described below.
2. The driver data you import
When you choose a CSV, XLSX, or TSV file, it is read by JavaScript running in your browser. The parsed rows are normalized and shown in the dashboard. They are not transmitted to a DeliverPayout server, and we do not have a copy of the file, the driver names, or the payment values.
The normalized dataset is saved in your browser's local storage so the dashboard can be restored when you return. This storage is specific to your browser and device. Clearing site data, using a private window, or using the “Remove dataset” control in the dashboard deletes it. If a dataset is too large for the available local storage quota, it is kept only for the current tab and is not saved for a later visit; the app tells you when that happens.
3. What DeliverPayout stores in your browser
DeliverPayout uses browser local storage — not server-side profiles — for the following:
- deliverpayout.dataset.v1: the normalized dataset from your most recent import, including driver names, external IDs, earnings, orders, distance, hours, tips, ratings, completion rates, vehicle type, any contact columns you mapped (email or phone), and the cash/prior-payment settlement amounts you enter. Stored locally until you remove it or clear site data.
- deliverpayout.history.v1: up to five replaced reports, so you can restore an earlier dataset. Snapshots keep driver names and amounts but strip the original source rows and clear payment confirmations. Removed by “Remove dataset” or site-data controls.
- deliverpayout_custom_platform_presets: the column mappings you choose to save for future imports. Header names only — no driver rows or amounts.
- deliverpayout.prefs.v1: your distance unit and display density preference.
- deliverpayout.consent.v1: your cookie and advertising choice, so the banner does not ask again on every page.
These values are stored on your device and are not sent to us. You can remove them through your browser's site-data controls or through the “Remove dataset” control in the dashboard.
4. Accounts, payments, and cloud storage
The free tier needs no account. If you start a trial or subscribe, we create an account so the plan can follow you between devices. In that case we store your email address, an organisation name if you provide one, the plan status, trial and renewal dates, and the identifier your payment provider assigns to the subscription.
Payments are handled by Dodo Payments, which acts as the merchant of record. Card details are entered with Dodo Payments and are never transmitted to or stored by DeliverPayout. We receive the outcome of a payment — paid, failed, refunded — and the billing country, not the card number.
If you use cloud save, the payout runs you choose to save are stored in our database so they can sync between your devices. That data is yours: you can delete individual runs or your whole account from the app, and you can export it first. Data you never save to the cloud stays in your browser.
5. Advertising and Google AdSense
The free tier is supported by advertising on selected public pages: the home page, the how-it-works page, and the guides. We do not display advertising in the dashboard, the import flow, on legal pages, or anywhere on a paid plan.
Advertising is provided by Google AdSense. The AdSense script is not loaded unless you make a choice that allows advertising cookies. If you choose “Essential only” or dismiss the banner into essential mode, the AdSense script is not loaded and you may see a labelled placeholder instead of an ad.
When advertising is allowed, Google and its partners may use cookies, local storage, and device identifiers to serve and measure ads, including personalised ads, and may process information such as your IP address, approximate location, browser, and the pages you view. This processing is governed by Google's own policies. See How Google uses information from sites that use its services.
If required in your region, we request consent before loading advertising scripts. You can change your choice at any time using the cookie and advertising settings. You can also manage personalised advertising through Google Ad Settings and manage cookies in your browser settings.
6. What we do not use
DeliverPayout does not run third-party analytics, session recording, heatmaps, advertising pixels of its own, or cross-site tracking. Fonts are bundled with the application rather than loaded from a font CDN. The app does not sell personal information.
7. Hosting, processors, and technical logs
Like any website, the hosting provider that delivers DeliverPayout may process standard technical data — such as an IP address, request time, requested URL, and user agent — to serve the page and protect the service. Those logs are controlled by the hosting provider and are not used by DeliverPayout to identify individual visitors.
Where you create an account, we use a small number of processors to run the paid service: a managed database and authentication provider for account data and saved runs, a transactional email provider for sign-in links and receipts, and Dodo Payments for payments. Each processes only what it needs for that purpose. Our hosting provider and database may process data outside your country; where required, they rely on appropriate transfer safeguards.
8. Legal bases and your rights
Where the GDPR or UK GDPR applies, we rely on your consent for advertising cookies, on the performance of our contract with you for account and billing data, and on our legitimate interest in operating a secure, functional website for essential technical processing. You have the right to access, correct, delete, restrict, or object to the processing of personal data, and to withdraw consent at any time.
Because DeliverPayout does not receive your imported dataset unless you save it to the cloud, we cannot access, correct, or delete local data for you — it is under your control in your browser. For any other request, including deleting an account, contact hello@deliverpayout.com. You also have the right to complain to your local data protection authority.
9. Children
DeliverPayout is a business tool intended for adults. It is not directed to children under 16, and we do not knowingly collect personal information from children.
10. Changes to this policy
If this policy changes materially, the effective date above will be updated. Continued use of the site after a change means you accept the updated policy. If you have an account, we will email you about material changes; otherwise this page is the notice.
11. Contact
Questions about this policy or your data: hello@deliverpayout.com.