Privacy

Dueplans is run by Canvas Tech Solutions. This page describes everything the site collects and why. Questions or requests: [SUPPORT EMAIL — pending decision D-8].

The short version

• The plan generator collects nothing. Your five answers are processed in your browser and are never sent anywhere or stored.
• We don’t know your due date, your city, or anything else about your plan — there is no plan data on our side at all.
• If you buy a plan, payment runs through Stripe; we receive a record of the purchase (email, amount, date), never your card details.
• If you leave your email for rule-change updates, we store it for that single purpose, as described under the form.
• Visit analytics on the marketing pages runs only if you allow it.
• Our server keeps access logs for 14 days.

The plan generator — zero data collection

The generator at /plan/ makes no network requests while you use it. Your answers stay in your browser’s memory, are never transmitted to us or to anyone else, and aren’t stored in browser storage. Closing the tab erases them. The page carries no analytics, no cookies and no tracking scripts — this is enforced by the page’s security policy, not just promised.

Purchases

Buying runs on Stripe’s hosted checkout. Stripe receives your payment and email address and processes them under its own privacy policy. We receive from Stripe a record of the purchase (email address, amount, date) and use it only for receipts, refunds and support.

Update emails

If you submit the update form, we store the email you enter, the address of the page you signed up from, and basic technical details (time, IP, browser, browser language, and the referring page if your browser sends one) — solely to send you rule-change updates for Dueplans and to protect the form from abuse. Submissions are checked by Google reCAPTCHA Enterprise. This mirrors the disclosure shown under the form itself; if the form’s wording and this page ever disagree, the form’s wording is what we do. [Keep in lockstep with any future form-copy change — and this paragraph assumes the D-10 keep-branch wording; if D-10 removes the band, delete this section.]

Visit analytics (marketing pages only)

The marketing pages offer optional, consent-gated visit analytics (self-hosted Plausible). Before you answer, each view is counted as one anonymous row. If you allow analytics, the consent banner describes exactly what is collected and for how long; your choice is stored in your browser only — no cookies. Declining analytics never limits the product. The plan generator page carries no analytics at all. [Aligns with the certified consent notice; if the notice is revised, update this section in the same operation.]

Server access logs

Our web server records standard access logs — the page requested, your IP address and your browser’s user agent — kept for 14 days, used only for security and troubleshooting.

Where things live

[HOSTING FACTS — verify before publish; do not guess. The marketing site and the signup backend run on infrastructure operated by [HOSTING OPERATOR] in [DATACENTRE LOCATION]; the signup database is PostgreSQL. As of this page’s drafting the operator (OVHcloud, per the build plan’s estate) is known but the datacentre location is NOT verified — the engineer or site-frontend-agent confirms the facts, the user approves the wording.]

What we don’t do

• No advertising trackers or ad pixels.
• No selling or sharing of your data.
• No cross-site tracking.
• No medical or health data — we never ask for it.

Retention summary

• Access logs: 14 days.
• Purchase records: kept as long as needed for tax and dispute purposes. [Period to be set — legal review.]
• Update emails: until you unsubscribe or ask us to delete them.
• Analytics records: per the consent notice (browser ID up to 30 days; detailed visit records up to 90 days; your privacy choice up to 180 days; summary counts up to 13 months).

Access and deletion

Ask what data is connected to you, or ask us to delete it: [SUPPORT EMAIL]. We use a basic verification step before acting on a request.

Changes

We’ll post changes on this page with a new date; material changes get highlighted.