Community privacy, safety and launch conditions

Contact and reporting

No corrections, privacy, removal, safety-report or appeal email is currently verified. Do not send medical records or emergency information. A replacement route must be selected, delivery-tested and assigned to a responsible moderator before submissions reopen. No response time can currently be promised.

Public pseudonymity is not anonymity

Public contributions use a chosen display name and date. Accounts are identified to the service by a site-specific signed-in identifier; hosting and sign-in providers process normal account and request information. Moderators and the author can see pending text; it is not intended to become public before approval. Separate sites keep separate community records. MyWise does not accept health entries or store a patient record.

Consent and other people

At launch, consent must expressly cover public publication after moderation. Do not post another person’s story, identifiable details, clinical records, allegations or images. Unnamed details can still identify someone. Consent from another person does not guarantee that publication is suitable.

Minors and guardians

No submissions by or about minors are being accepted. A guardian-consent, age-assurance and safeguarding procedure has not been approved. Do not submit on a child’s behalf. Any future guardian pathway requires separate approval and the child’s interests and assent where appropriate.

Medication advice, allegations and promotion

Future moderation must decline dose-change instructions, unsafe medical claims, requests for individual prescriptions, commercial promotion, harassment and identifiable allegations. A moderator may ask for a safer revision or decline publication. A community post does not replace clinical advice.

Distress and urgent disclosures

The community is not monitored continuously and must not be used for urgent help. In an emergency in Australia call 000; elsewhere use the local emergency number. Before launch, a written escalation procedure, designated moderator and backup must cover distress, threats, privacy breaches and unsafe advice.

Reports, appeals and moderator absence

Before reopening, publish a staffed response window and a backup contact, test reporting and appeal delivery, and define escalation, temporary removal and review of disputed decisions. If moderation coverage is unavailable, submissions and publication must remain paused. Do not assume a sent email has been received or acted on.

Withdrawal and retention

Existing signed-in contributors have a My submissions withdrawal control. The current implementation removes the stored public text and display name, but retains the author identifier, kind, timestamps and consent metadata. There is no implemented automatic expiry. This is not a claim of complete deletion or a verified backup-retention period. A retention schedule and deletion workflow require approval and testing before new submissions. Copies, screenshots, search caches or reposts made elsewhere may remain after removal here.

Launch verification required

Test sign-in, consent, isolation, moderation, reports, appeals, withdrawal, email receipt and retention using an authorised test account and fictional text before making these workflows available.