Privacy Policy.
Effective November 4, 2026. What we collect, why, and how to request deletion.
1. What we collect
If you submit a review: we save your rating, review text, optional first name and use stage, any customer-reported feedback or giveaway relationship, the order and account it belongs to, your publication permission, revisions, and moderation history. Reviews are anonymous publicly unless you choose a first name. We publish only the exact version you permitted after moderation. Public reviews do not show your email, account or order identifiers, or private moderation notes. You can edit or withdraw a review in Order History. An edit removes the prior public version until the new version is checked; withdrawal removes it from our public review page and rating counts. Review records and moderation evidence remain while your account exists and are removed when that account is deleted. Copies already made by other people or search engines may remain outside our control.
When you buy a tape: your email address, the
ballistic and turret inputs you enter (rifle, cartridge, bullet,
velocity, turret specs, conditions), any customer-supplied turret correction
table and its revision history, your order details, and the
generated PDF file. If you arrived from one of our ads, the ad's
campaign parameters (the utm_* values and, when
present, Google's gclid ad-click identifier) are saved
with the order so we can measure which campaigns lead to purchases.
We also save when the campaign was first recorded and your Advertising
preference at checkout, including whether Global Privacy Control blocks
that purpose. If no campaign label is present, we may save a general
Facebook or Instagram source from an ad-click parameter or referring
domain. We do not save Facebook's raw click identifier or the full
referring address with your order. A social source alone does not
identify a particular ad. Valid campaign source, medium, and name are
also attached to your Stripe Checkout Session and payment record.
Customer-supplied turret correction tables are used to generate and maintain the product you ordered. If you separately opt in, DialWRX may also compare live-fire verified values with the associated technical load inputs to test and improve its ballistic calculations. That choice is off by default and is not required to purchase or update a tape. Before using opted-in data for calculation improvement, we separate it from your name, email, account, and order details.
If you create an account: your email, an optional display name, and a password (stored as a secure hash, so we never see it).
When you contact us: whatever you include in your message, plus your name and email so we can reply. Our website's contact form is processed and stored by Netlify Forms.
When you report a problem in the app: we store your description, the part of the builder or order history you were using, basic browser and screen-size details, and the related order number when you report from a purchased tape. We also store your account email, the order's checkout email, or an optional reply email you enter in the builder. Troubleshooting details can include your selected data source and units, supplied-row count, and a validation category. We do not automatically attach your pasted table or ballistics values. Owner alert emails contain a report reference and category, not your description or contact details.
When you request a free PDF: your email address and request details are saved so we can deliver it and retry if needed. The setup guide, demo preview, and drop chart are sent through Resend. You can confirm separately in that email to join our occasional tips and updates list. Requesting a PDF does not confirm that subscription. Every such email has an unsubscribe link. Unsubscribing from updates does not affect paid-order delivery.
When a dealer builds a tape: we store the dealer organization, location, staff account, and tape inputs. A customer email supplied for delivery is sent to our email provider but is not copied into the permanent licensing ledger or dealer report.
If you use Locate me: after your browser asks for permission, your coordinates pass through DialWRX only long enough to request ground elevation from the U.S. Geological Survey. If that point service is unavailable, DialWRX requests the corresponding map tile from Mapzen Terrain Tiles on AWS and accepts it only when the tile identifies USGS 3DEP/NED as its source. DialWRX does not store or log your coordinates or attach them to your order.
For abuse prevention: the app keeps a keyed one-way hash of the requesting IP address with request timestamps for the active one-minute or 24-hour protection window. An hourly retention job removes expired entries; the raw address is not stored in that table.
For first-party usage measurement: our public marketing pages count page views and clicks into the tape builder. The tape builder records page views, meaningful builder interactions, successful interactive previews, and sample download starts. Our four public free tools also count page views, interactions, successful calculations, accepted PDF email requests, download starts, visits to the tape builder, and issues. Flight path and hit probability also record aggregate counts of displayed results, failures, and feature use, including playback, timeline scrubbing, camera views, condition comparisons, target changes, and model adjustments. These newer counters cover the public hit probability calculator and tools used with purchased tapes. They store only the day, tool, public or saved-tape surface, event label, and count. They do not store entered load data, account or order IDs, or visitor hashes. Signed-in access is verified for saved-tape events, but identity is not included in these counters. We also record the campaign source, medium, and campaign name when those values are present. To estimate daily visitors without a browser tracking ID, the app stores a keyed one-way hash of the requesting IP address that changes each day. The raw address, form values, email, account ID, full URL, browser details, and ad-click identifiers are not stored in these usage tables. Email-request counts do not confirm delivery or a subscription to marketing updates. Current-visit campaign counts are separate from the first campaign saved with a purchase.
If you allow Google Analytics: Google Analytics 4 helps us see which public pages people visit and which campaigns bring them here. It also measures completed builder steps, preview outcomes, and general issue categories so we can find where people get stuck. We send page addresses without query strings or URL fragments, the referring site's domain, and limited campaign labels. We do not send form entries, email addresses, account or order IDs, checkout or edit tokens, or private download links. Google says its standard Analytics collection includes approximate location and browser and device information. See Google's Analytics data collection documentation for more detail.
If you allow Advertising: Meta Pixel helps us measure Facebook and Instagram ads and reach interested visitors. It receives public page addresses, including allowed campaign and ad-click parameters, and the limited builder and free-PDF events we send. Meta also receives browser and network information such as your IP address, referring page, and its cookie identifiers. Meta may associate that activity with your Facebook or Instagram account and use it for ad measurement and audiences. We do not enable automatic advanced matching or automatic event collection, and we do not send your email address, form entries, ballistic inputs, account or order IDs, checkout or edit tokens, or private download links. See Meta's Privacy Policy and Cookie Policy.
What we don't collect: we never see or store your card number. Payment goes directly to Stripe. We do not enable Google advertising features or sell customer lists. Optional Advertising does share the visit data described above with Meta.
2. Who processes it
We use a small set of service providers to run DialWRX, each receiving only what they need:
- Stripe: payment processing (your card details go to Stripe, not us)
- Supabase: account authentication, order database, and private file storage
- Resend: delivers paid-order and requested free-PDF emails
- Netlify and Fly.io: host the website and the tape builder. Netlify also processes contact-form submissions and gives us aggregate, cookieless traffic counts from server logs.
- Google Analytics: measures visits and limited usage only after you allow analytics; read Google's Privacy Policy
- Meta: receives visit and event data for ad measurement and audiences only after you allow Advertising; read Meta's Privacy Policy
- U.S. Geological Survey: receives coordinates only when you choose Locate me, and normally returns the elevation for that location
- AWS Open Data: Mapzen Terrain Tiles receives an approximate map-tile identifier, rather than your exact coordinates, only when the USGS point service is unavailable
Fallback terrain data: Mapzen Terrain Tiles, accessed July 13, 2026 from the AWS Registry of Open Data. U.S. 3DEP/NED data courtesy of the U.S. Geological Survey.
3. Cookies and local storage
If you sign in, your browser stores a session token so you stay
signed in. The tape builder keeps your cart and your checkout email
in your browser's own storage. The first recorded campaign, including
a gclid when present, is remembered for up to 30 days in
browser storage and a first-party cookie shared by dialwrx.com and
app.dialwrx.com. This lets a later return visit retain that campaign.
The cookie contains campaign labels and dates, not a unique visitor
ID. A general social source may be replaced by the first specific
campaign label. Later campaigns do not overwrite that label or extend
its 30-day window. This measurement stays with DialWRX and our payment
records and does not enable Google Analytics or Meta Pixel. The cart
is cleared after the server validates the returned order. Your checkout
email is retained to prefill a future order until you clear this site's
browser data. For
marketing-site traffic volume we use Netlify's server-side analytics,
which counts visits from request logs without cookies or scripts in your
browser. The tape builder sends the first-party usage events described
above to DialWRX without setting its own analytics cookie or persistent
browser tracking ID.
A private feature-test link may set a strictly necessary, HttpOnly cookie that unlocks that test in the tape builder. It contains a signed random capability and expiration time, not your name, email address, or shooting data. It expires when the link expires, no later than 30 days after it is created.
Google Analytics and Meta Pixel stay off until you allow their
respective purposes in our Privacy choices banner. Allow all permits
both; Reject all permits neither. Manage choices lets you allow
Analytics or Advertising separately. We save those preferences in
one cookie for up to 180 days, shared by the website and tape builder.
An earlier Analytics-only choice does not allow Meta; we ask again
when offering Advertising. If you allow Analytics, Google may
set identifier cookies that also expire after 180 days. You can change
your choices at any time with the Privacy choices control on public
pages, including this privacy page. Declining
a purpose stops its future measurement and removes that provider's
identifier cookies from this site. Meta may set _fbp and
_fbc cookies when Advertising is allowed. Meta controls
their normal expiry as described in its Cookie Policy. A browser's
Global Privacy Control signal keeps Advertising off, even if you
choose Allow all.
Browser privacy signals: the older Do Not Track (DNT) setting does not automatically change your choices on DialWRX. Google Analytics and Meta Pixel still require your separate permissions. Global Privacy Control (GPC) is different: we honor it by keeping Advertising off. After you opt in to their respective purposes, Google and Meta may collect information about your activity over time and across other websites that use their services.
Both tags are limited to public marketing pages and normal use of the consumer builder. They are not loaded on sign-in, account, order, message-confirmation, administrator, or dealer pages. They are also not loaded when the builder is handling a paid order, an edit link, or dealer mode. Meta also stays off when a referring address could expose a private path or URL parameters. Google advertising features stay disabled even when you allow Meta Advertising.
4. How long we keep it
Account data, saved tapes, and customer turret correction table revisions stay as long as your account exists. Optional calculation-improvement consent is stored with the applicable turret correction table revision so we can honor the choice that accompanied it. Order records are retained for financial and tax compliance. Guest-order emails are kept with the order record. App usage records are retained for 90 days. Their daily visitor hash changes at Mountain Time midnight, so the analytics table does not carry one persistent identifier from day to day. The consent preference and Google Analytics identifier cookies described above expire after no more than 180 days under our browser configuration.
Completed free-PDF delivery jobs are removed after 30 days. Unconfirmed signup records are removed after 90 days if no delivery is pending. Confirmed email-list addresses stay until you unsubscribe or ask us to delete them. We retain an unsubscribe record to prevent unwanted updates; you can ask us to delete that record too. Problem reports are kept as long as needed to investigate the issue, respond, and recognize repeated failures. You can ask us to remove one.
5. Deleting your data
Account holders can delete their account from the account page at any time. Deletion permanently removes your profile, login, and stored personal tape files. We remove your account link and email from retained DialWRX order records. Payment records held by Stripe and records needed for financial or legal compliance may remain. Dealer-organization records and files belong to the organization and are not removed by deleting an individual staff account. Guests or anyone else wanting data removed can email info@dialwrx.com and we'll handle it within 30 days.
Email updates are managed separately from accounts. Deleting an account does not automatically unsubscribe or delete an email-list signup. Use an email's unsubscribe link to stop updates, or email us to request deletion of the signup record as well.
6. Your rights
Wherever you live, you can ask us what data we hold about you, ask for a copy, ask us to correct it, or ask us to delete it. Email info@dialwrx.com for any of these. We don't sell customer lists. You can decline Analytics and Advertising at any time through Privacy choices on public pages, including this privacy page. Declining Advertising opts out of sharing visits with Meta for ad measurement and audiences. Your tracking choices do not affect the builder, checkout, or delivery of a requested PDF. You can also ask us to stop using previously opted-in trajectory data for future calculation-improvement work.
These request options are available to all customers. Additional rights under privacy laws depend on where you live and whether those laws apply to DialWRX.
7. Not for kids
DialWRX is a product for firearm owners and is not directed at anyone under 18. We don't knowingly collect data from minors. If you believe a child has given us personal information, contact info@dialwrx.com so we can investigate and remove it as appropriate.
8. Changes
November 4, 2026: we added customer reviews with separate publication permission and moderation. We also added aggregate activity counts for flight path and hit probability, including the tools used with purchased tapes.
October 17, 2026: we clarified the limited unit and validation details included in problem reports and order linking from paid tape editors.
October 13, 2026: we added in-app problem reports and explained the limited troubleshooting details stored with them.
October 12, 2026: we added a separate, optional consent choice for using de-identified live-fire trajectory data to improve ballistic calculations.
October 6, 2026: we clarified contact-form processing, browser privacy signals, third-party tracking, and what account deletion does and does not remove.
October 4, 2026: we added opt-in Meta Pixel measurement and a shared Privacy choices banner with separate Analytics and Advertising preferences. Previous Analytics permission does not authorize Meta. Automatic advanced matching and automatic event collection remain off. Google Analytics, added October 3, remains opt-in with Google advertising features disabled. If this policy changes materially again, we'll update the effective date above and note the change here.
9. Contact
Privacy questions: info@dialwrx.com.