Drafts stay in the browser
Current drafting tools are designed as browser aids. Visitors copy their own draft instead of submitting it to the site.
Privacy policy
Privacy comes before patient data collection.
The current public site is intentionally designed to avoid collecting sensitive patient information through public forms, accounts, story submissions, forums, or data-collecting tools.
Privacy guide
Why the site collects less by default.
The current drafting tools are meant to help visitors write and copy their own language without creating accounts, submitting stories, or storing private health details on the site.
Best first route
Use private drafting tools
The tools are designed to help you draft and copy text without submitting it to the site.
Current privacy posture
The site is primarily public education plus private browser-based drafting tools. Do not send private medical details through the website unless a secure form clearly explains consent, storage, review, and deletion rules.
If a feature collects data
If story submissions, contact forms, email-list forms, forum accounts, or data-collecting advocacy tools collect information, the site must define what is collected, why it is collected, how long it is kept, who can access it, and how users can request deletion.
Sensitive information warning
Avoid sending full medical records, Social Security numbers, account numbers, private insurance identifiers, prescription numbers, home addresses, or names of clinicians/pharmacies unless a secure process specifically requests and protects that information.
Third-party services
Analytics, ads, payment providers, email tools, guided drafting services, storage services, or forum services should be named in the privacy policy when they receive or process visitor information.
Privacy-first path
Useful patient tools should not force people to expose more than needed.
This site should stay helpful for people who are sick, rushed, elderly, or afraid of being judged. The privacy standard is simple: collect less, explain more, and keep current drafting tools under the user’s control.
Prepare before sharing
Use the tools to organize facts on your own device, then remove sensitive details that are not needed for the recipient.
Open tools →Keep first messages narrow
Source leads, collaboration ideas, or support questions should not include full records, account numbers, prescription numbers, addresses, or urgent medical requests.
Use contact router →Paid tools need extra controls
Saved packets, accounts, email delivery, and guided help belong behind clear retention, deletion, review, and consent rules.
Review safeguards →Details that should stay out by default
More detail is not always safer. Many first drafts and first contacts work better when unnecessary identifiers are removed.
- Avoid full medical records, full addresses, birth dates, prescription numbers, account numbers, and claim numbers unless a secure process specifically needs them.
- Do not post another person’s private medical details, clinician accusations, or identifying information in a public space.
- Keep payment and supporter account data separate from health-related drafts.
- Review any downloaded or copied packet before sending it through an outside channel.
Account privacy safeguards
Supporter access should collect the least information possible.
Accounts can make Supporter Tools easier to use, but only if they are narrow, transparent, and separated from sensitive medical facts. The account layer should handle access, receipts, usage limits, and optional saved work without turning payment into a medical record.
Free help stays usable
Public education pages and browser-based tools should remain available without forcing patients to create an account, upload records, or expose private health details.
Draft first, choose the channel
The safest workflow is still local preparation: draft, review, copy, print, and decide which outside office, portal, or agency channel should receive the final message.
Payment is not a medical file
Supporter billing should stay separate from diagnoses, prescriptions, records, claim numbers, pharmacy details, story drafts, and complaint packets.
Account safeguards patients should be able to see
A professional Supporter experience needs more than a login screen. These safeguards help patients understand what the account is for, what it is not for, and how private work stays under their control.
- clear sign-in purpose before an account is requested
- minimum profile fields for access, support, and security
- plain renewal, cancellation, and support-contact language
- separate handling for payment records and health-related drafts
- visible privacy warning before any draft is saved
- view, export, rename, and delete controls for saved packets
- written retention rules for any stored work
- abuse controls that do not expose private medical facts in ordinary logs
Data decisions that should stay plain
Users should understand what information is unnecessary, what may be needed for access, and what belongs only in a user-controlled saved-work feature.
Leave out by default
Full records, prescription numbers, addresses, account numbers, and unrelated names
These details should stay out of ordinary tools unless a secure, clearly explained workflow truly needs them. Most advocacy preparation does not require them.
Use only when needed
Email address, supporter status, fair-use counters, and basic account settings
These fields may be needed for access, receipts, cancellation, usage limits, abuse protection, and support. They should not become a hidden medical profile.
User-controlled
Saved packet titles, draft text, route category, timestamps, and user notes
Saved work should require a clear user action, a privacy warning, and controls to view, copy, export, rename, or delete the packet.
Promises that keep Supporter access from feeling risky
Trust improves when the site states what it will not do. These promises keep payment, saved packets, privacy, and sending choices separate.
Privacy should make Supporter Tools easier to trust.
Supporter access should clearly explain what stays free, what costs money, what is collected, what is not collected, and what the user controls.