Dash Calc

Privacy Policy

Last updated: August 17, 2026

This Privacy Policy explains our policies on the collection, use, and disclosure of your information when you use our app, Dash Calc. We aim to keep your privacy secure and straightforward.

Data Collection and Usage

Dash Calc does not require an account and does not collect a user ID, device ID, advertising identifier, or other stable identifier. The information handled includes:

  1. Analytics: If you’ve enabled Share With App Developers in iOS  Privacy & Security settings, crash reports and basic usage information are shared with Apple. This is anonymous and helps improve the app.
  2. User Feedback: If you choose to send feedback from within the app, the email template will automatically include your device model and iOS version. You can review and edit this information before sending the email.
  3. Optional End-of-Trial Survey: If you choose to respond to the voluntary survey shown after a trial ends, Dash Calc sends your selected answer, any optional comment, locale, app version, build number, and distribution channel to a Cloudflare Worker. The submission also includes a random identifier generated for that submission; it exists only so that a retried send is stored once, and it is not a device or user identifier. If your download was attributed to one of our Apple Ads campaigns, the submission may also include the campaign details described under Apple Ads Campaign Measurement below. The server records when it receives the response and stores the response in Cloudflare D1. Email-address and phone-number patterns in comments are automatically redacted before storage. Please do not include personal information. The survey response fields are used only for analytics and product improvement; any attached campaign details are used only for aggregate measurement of our own Apple Ads campaigns. Neither is linked to your identity nor used for tracking. The survey Worker does not read or store IP-address headers.

Apple Ads Campaign Measurement

We advertise Dash Calc on the App Store using Apple Ads. If your download came from one of our ads, Dash Calc obtains a short-lived token from Apple’s AdServices framework and sends it directly to Apple’s AdServices API to retrieve an attribution record. The returned campaign record contains no user or device identifier. For those attributed downloads only, Dash Calc automatically reports up to four milestone events to our Cloudflare Worker so we can measure our advertising in aggregate:

  1. install_attributed — the app confirmed the download was attributed to one of our campaigns
  2. trial_started — a free trial began
  3. trial_expired — a free trial ended
  4. lifetime_purchased — the one-time lifetime unlock was purchased

Besides the milestone name and a static schema version, each event contains the campaign and ad-group identifiers of our own Apple Ads campaign, an optional keyword identifier, the claim type (whether the ad was tapped or viewed), the App Store placement where the ad appeared, the calendar week (a Monday date) in which the app was first opened, and at most one coarse bucket — a range for the number of calendar days between first open and trial start, a range for the number of days the app was used during the trial, or whether a purchase happened with no trial evidence, during the trial, or after it expired. No purchase amounts, receipts, or transaction identifiers are sent.

Each event also carries its own random identifier (a UUID). It exists only so that a retried delivery of the same event is stored exactly once. These identifiers are generated independently per event: the events from one installation do not share any identifier, and we do not create or store a stable key that joins them. Because events carry sparse campaign details and the server records a precise receipt time, events from the same installation could in principle be correlated probabilistically. We do not attempt such correlation, and we do not claim it is impossible.

These events are sent to and processed by Cloudflare (Workers and the D1 database). The server records a precise timestamp of when it receives each event. In Cloudflare D1, campaign measurement data — the milestone events and any campaign details attached to survey responses — is retained for 180 days and then deleted; for survey responses, the campaign details are cleared while the survey answer itself is kept. The automatic deletion does not cover CSV or downstream copies exported for analysis; those copies remain until manually deleted. We use this data solely to measure our own Apple Ads campaigns in aggregate. It is not linked to your identity and is not used to track you.

No Ads and No Third-Party Tracking

Dash Calc is ad-free: the app shows no advertising. We measure our own Apple Ads App Store campaigns in aggregate using only the events and campaign details described above, which contain no user ID, device ID, advertising identifier, or stable identifier shared across events. We do not track you across apps or websites owned by other companies, we do not use targeted advertising, and we do not sell your data or share it with data brokers.

Data Security

While we strive to use commercially acceptable measures to protect any data shared with us, no method of transmission or storage is 100% secure. However, our app is designed to minimize data handling and prioritize user privacy.

“As Is” Disclaimer

Dash Calc is provided on an “as is” basis without warranties of any kind, express or implied. We do not guarantee that the app will be error-free, uninterrupted, or that it will meet your expectations. Use of the app is at your own risk.

Changes to This Privacy Policy

We may update our Privacy Policy occasionally. Updates will be posted here, and the “Last updated” date at the top of this Privacy Policy will be revised.

Contact Us

If you have any questions about this Privacy Policy, please contact us at:

Email[email protected]