Privacy policy

Privacy comes before patient data collection.

Pain Care Rights minimizes sensitive data by default. Public drafting tools do not require an account. If someone creates a free account or sends a contact message, the site processes only the information needed for that feature plus limited security and abuse-prevention data.

Privacy guide

Why the site collects less by default.

Public drafting tools are designed to work without an account. Account access and the contact form use limited security controls, including Cloudflare Turnstile, to reduce automated abuse and preserve an investigation trail when an account is attacked or misused.

Best first route

Use private drafting tools

The tools are designed to help you draft and copy text without submitting it to the site.

Open tools
Collect less

Patient advocacy should not require unnecessary exposure.

Privacy matters because health records, prescription details, clinician names, addresses, and account numbers can create risk when they are shared without a secure reason.

Public drafts stay in the browser

Public drafting tools are designed as browser aids. Visitors can prepare and copy language without creating an account or submitting a medical record to the site.

Accounts use limited security logs

Free-account sign-in records a keyed hash of the network address, browser and device summary, authentication outcome, and Cloudflare request metadata when available so abuse can be investigated without storing the raw IP address.

Avoid unnecessary identifiers

Patients should not send full records, account numbers, prescription numbers, addresses, or identifying details unless a secure process clearly requires them.

Current privacy posture

The site is primarily public education plus browser-based drafting tools. Free accounts store only the saved work a member chooses to keep. The public contact form is for short non-urgent messages and does not accept attachments.

Account and abuse-prevention security logs

Account-code requests, account creation, successful sign-ins, rejected codes, blocked accounts, and rate-limit events can create a security record. That record may include a keyed hash of the network address, user-agent/browser family and version, operating-system and device class, language, timezone, platform and viewport supplied by the browser, referrer path, Cloudflare Ray ID/country/edge location when present, Vercel request ID, Turnstile result, and the authentication outcome. Raw IP addresses and MAC addresses are not stored. Security events are normally retained for 180 days and the configured period is limited to 30–365 days.

Contact form and Cloudflare Turnstile

The contact form sends the reply email, optional name or organization, selected reason, and message through the configured transactional email provider. Cloudflare Turnstile verifies that the submission is not automated. Limited browser and Cloudflare request details may be included with the message as an abuse reference. Do not use the contact form for medical records, prescription numbers, government identifiers, passwords, or urgent requests.

If a feature collects data

Any story submission, contact form, email-list form, forum account, member account, or data-collecting advocacy tool must explain what is collected, why it is collected, how long it is kept, who can access it, and how deletion works before a visitor shares sensitive details.

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

Cloudflare Turnstile processes anti-abuse verification data, and the configured transactional email provider processes one-time access codes, signup notices, and contact-form delivery. Other analytics, payment, storage, guided-drafting, or forum services should be named here before they receive or process visitor information.

Draft privately

Use the browser tools, then decide where the final message belongs.

The safer workflow is to draft, copy, review, remove private details, and send only through the proper outside channel when the patient chooses.

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.

Draft privately

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 →
Contact carefully

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 →
Supporter safeguards

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.