Start with the contents, not the file format
A symptom diary may contain dates, health observations, medication names, locations and personal notes. A spreadsheet is not automatically private because it is stored in a file, and a paper copy can also be seen by people you did not intend. Consider the contents and where the record will go.
For a clinical visit, a one-page summary may be enough for the first conversation. Keep the full diary available if it is requested through the clinic’s normal process. Choose the smallest record that still explains your question clearly, rather than sharing an entire folder by default.
Five checks before sending
If the sharing settings are unclear, pause and confirm them with the service or the recipient. Do not paste your diary into an unrelated contact or waitlist form. A privacy-conscious checklist is a practical prompt; it is not a promise that any particular service is suitable for health data.
| Check | Question to answer |
|---|---|
| Contents | Have I reviewed every field and attachment? |
| Recipient | Am I using the correct person or clinic address? |
| Method | Does the clinic provide a preferred secure route? |
| Access | Who can view or edit this link or file? |
| Later access | What happens to the copy after it is received? |
Paper, files and links need different checks
For paper, consider who can see the copy while it is carried, printed or left at the appointment. For a file, check the destination and attached filename before sending. For a cloud link, review who has access and whether the recipient can download or pass on a copy. Confirm the actual settings in the service you use.
A download can create another copy beyond the original sharing link. Ask the recipient about its handling process if that matters to your decision. Do not assume that removing your local file or switching off a link deletes copies held elsewhere. Keep the explanation tied to the service’s documented behavior.
What is known about AirBloom today
AirBloom is in development. The existing public privacy notice covers early-access signup and its stated waitlist handling. It does not establish a complete specification for the future app’s collection, export, deletion, sharing, encryption or retention of health records. Those details need to be documented for the actual product before a product-specific privacy guide can describe them.
Do not submit symptoms, medication lists or a doctor report through the waitlist. Use the published contact or removal route for waitlist matters. The blank resources are offered to use independently; they do not require sharing a completed health record with this website.
Before using a future health app, read the policy and controls available for that released version. Ask what is collected, who receives it, how exports work and what deletion covers. Keep those questions separate from a marketing description or a screenshot of a planned feature.
Sources & further reading
This guide provides general education, not individual medical advice. It has not been clinically reviewed. Talk to a qualified clinician about persistent, new or worsening symptoms. Follow your local emergency guidance for urgent concerns.
Spotted an error? Tell the editorial team.
Your story, together.
AirBloom is in development for iOS and Android, bringing symptom records and existing routines into one place. Join the early-access waitlist.