PLAIN-LANGUAGE PRIVACY

Your curiosity.
Your choices.

Optional micro-conversion counts

From the October 19, 2026 analytics upgrade, choosing “Allow counts” permits first-party page-attempt measurement on participating pages, including the resource library, sticker form and Peer Reviewer. Earlier counting choices are reset so you can choose again. Reading, searching, quizzes and forms work if you skip. Turn counts off using the same page controls. A browser Global Privacy Control or Do Not Track signal disables the new counter.

A new random reference is held in page memory for each page visit. It links milestones within that page only: page open, 30 visible seconds, resource/download/kit links, share or print actions, search used or no results, and quiz/form starts, save attempts, confirmed success screens or failure screens. The reference changes on navigation, reload, a new Toronto date or a testing-label change. It is not a persistent visitor identifier and is not linked to form receipts, names, accounts or other pages. Repeated milestones and request retries do not add another milestone within the same page attempt.

The new table stores only that reference, Toronto date, approved page path, measurement release, approved channel label from the current URL, testing label and reached milestones. It does not store search terms, chosen topics, quiz answers or scores, initials, form fields, comments, mailing details, IP addresses, full URLs, referrers or device fingerprints. Hosting providers may process standard security/request information. Channel labels are unverified and are not carried to other pages. Unlabelled traffic is called unattributed.

The owner sees aggregate reports and exports. Page-attempt records expire after 90 days and are removed on the next analytics access; there is no automatic deletion job while the system is unused. Switching counts off prevents new sends but cannot recall an already-sent request. No previous behaviour is backfilled when you opt in. Counts cover only participating visitors and may include automated or mislabelled activity. They cannot prove unique people, resource receipt, learning, mailing, health benefits or stigma reduction.

Optional sticker-linked visit counts

From October 28, 2026, new sticker links ending in /safety?src=sticker use the same optional first-party page-attempt counter above, with the approved channel label “sticker.” No extra counter, cookie, persistent visitor identifier or advertising service is added. The safety card and emergency guidance open without allowing counts. Only opted-in visits are recorded; Global Privacy Control and Do Not Track disable this counter. The private owner report separates self-labelled testing and shows today separately from completed days.

These are sticker-linked page visits, not physical QR scans or unique people. Reloads can count again, and the link can be shared or typed. Repeated requests within the same page attempt do not inflate its count. Existing printed codes and older records cannot be labelled retroactively. The same 90-day page-attempt retention and data limits above apply.

Optional campaign counts

If you choose “Allow counts,” this campaign counts page visits and actions such as opening a clue, copying the starter or clicking to ChatGPT. Counts are grouped by date, campaign placement and action. We do not put names, email addresses, chat messages or personal profiles in these counts. Your preference is kept in this browser tab’s session storage. You can turn counting off on the page.

These counts cover participating visitors and may include repeat visits or automated traffic. A click to ChatGPT does not tell TRDP what you typed or whether DOPE opened. ChatGPT has its own privacy practices.

Optional safety-card counts

Since September 26, 2026, the safety card sends usage events only if you choose “Allow counts.” Reading, emergency links, sharing and pledging work if you skip. The same session preference applies to participating campaign pages. You can turn counting off on the card. Its aggregate table stores a date, action type and count, without names or messages. Activity means card opens, sharing actions, pledge taps or official-guidance clicks—not unique people, confirmed message delivery or health outcomes. Older safety-card counts were collected without this opt-in choice and remain in the totals until they leave the displayed date range.

Optional website feedback

The resource feedback form requests no name, email or sign-in. Each question is optional. Submitting requires permission for TRDP to store and privately review the answers you choose to provide for website improvement. Please leave out names, contact details, personal health information and other people’s private details. It is not an emergency or clinical contact.

The form stores optional answers about learning, usefulness and respectful experience, optional comment, chosen review time, private owner review status and action notes, selected resource, site-release version, form version, a self-declared testing label, random receipt and submission timestamp. It does not store an account identity or IP address in its feedback table. Hosting providers may process standard request and security information. We do not promise complete anonymity.

Only the configured TRDP owner can review or export feedback. Submitting does not give permission to publish your comment or use it as a public testimonial. Records expire 90 days after submission and are deleted when the feedback system is next accessed. To request earlier deletion, email the contact below with your receipt. If you lose it, we may be unable to identify your response. An optional invitation may appear near the end of a visit. It never blocks leaving and does not send answers automatically. If you choose the testing-browser setting, this browser remembers it in local storage until you switch it off or clear site data. It labels new feedback and supported resource activity as testing but does not exclude native analytics. This browser tab remembers dismissal until it is closed; this preference is not sent to TRDP. Invitation displays are not tracked; responses are voluntary and do not represent every visitor.

Optional resource counts and learning pilot

Starting October 14, 2026, participating English resource pages can count resource opens, download-link clicks, kit-directory clicks, completed share/copy actions and print requests only after “Allow counts.” One action of each kind is counted per resource, link channel and testing label during the current page session; this is not a count of people or every click. The aggregate table stores Toronto date, resource path, site-release version, approved link-channel label, action, testing label and count. It stores no visitor identifier, full referrer, query string, IP address or account identity. Channel codes are self-labelled and do not verify where a visitor came from. Unattributed is not the same as direct traffic. These aggregate counts are retained for evaluation. Counts do not confirm printing, downloading, message delivery or learning. French resource activity is not covered by this October 14 aggregate counter; the separate micro-conversion counter above covers participating French pages.

The learning pilot works without saving scores. If you explicitly allow saving, a separate table stores a random attempt receipt, lesson version, self-declared testing label, before/after/later scores and timestamps. It requests no name, email or health history; it cannot verify unique people. Attempts expire after 90 days and are deleted on the next learning-system access. The receipt and completion date are kept in this browser’s local storage for a voluntary return after 7–14 days. There are no automatic reminders. “Forget this device receipt” removes the local copy; to request server deletion, email the contact below with your receipt. Do not share your receipt publicly. Hosting services may process standard request/security data. Independent review and validation are pending; results are not clinical qualifications, proof of lasting learning, causal impact or health outcomes.

The browser testing setting labels future resource counts and feedback; the learning pilot has its own visible testing checkbox. Existing campaign and safety counters skip newly labelled testing visits where supported. Earlier records cannot be retroactively identified, and native analytics still include traffic under the platform’s rules. Testing labels are self-declared, not identity verification.

Optional Peer Reviewer sessions

The community review offers three usability tasks in a 15-minute time box. You can skip, stop or leave without sending. At 12 minutes it moves to wrap-up; at 15 minutes no new tasks are offered. Your answers are never sent automatically or erased by the timer. Finishing or sending later can exceed the time box; elapsed time is recorded as reported by the browser, not verified task time. Task outcomes are self-reported, not an observed skills test or clinical approval.

Only after you confirm permission and press Send does this form store a random receipt, selected task pack, task outcomes and optional comments, overall optional comment, reported elapsed time, finish reason, optional device category, language, self-declared testing label, site/protocol versions and submission timestamp. No name, email, sign-in or health history is requested. Do not include other people’s private information. Hosting providers may process standard request/security data; complete anonymity is not promised.

The TRDP owner reads comments in a private inbox and receives summaries of new sessions in the configured daily ChatGPT report. Email and instant push are not enabled. Permission to review is not permission to publish a quote, testimonial or identifying detail. Draft answers stay only in the page’s memory and disappear on reload/close. Saved sessions expire after 90 days and are deleted the next time the peer-review system is accessed. Keep your receipt to request earlier deletion using the contact below. Removing a local page does not delete a saved review.

Optional sticker requests

The separate sticker form collects a mailing name and address with explicit permission. It is not linked to feedback. Only the TRDP owner can read it. The owner deletes the details after mailing; requests also expire after 90 days when the system is accessed. No mailing-list subscription or positive feedback is required. Keep your receipt to request earlier deletion.

Volunteer applications

The form asks for a chosen name, email, areas of interest, optional perspective, availability and participation needs, plus permission to review and contact you. Please do not include health histories or other people’s private details.

The TRDP founder reviews applications through a restricted owner area. Answers are used for recruitment and follow-up. Submitting does not subscribe you to a mailing list or permit public attribution. Application totals are counted separately without sending your answers to analytics.

Retention and hosting

Applications expire 90 days after their last review or status update. Expired applications are deleted the next time the application system is accessed. You may request earlier deletion. Aggregate counts contain no application answers and are kept for campaign evaluation.

The site runs on ChatGPT Sites using Cloudflare hosting and database services. Hosting providers may process standard request and security information to operate the service. TRDP does not use advertising pixels, browser fingerprinting or session replay in this campaign. We do not promise complete anonymity on the internet.

Contact and choices

Email therealdopeproject@gmail.com to ask about your application, correct it or request deletion. Do not email emergency information here; call 911 in Canada for an emergency.

Resource feedback privacy updated October 9, 2026. Sticker availability updated October 14, 2026. Other privacy sections last updated September 26, 2026.