[{"_1":2,"_78":-5,"_79":-5},"loaderData",{"_3":4},"routes/category.$slug",{"_5":6,"_58":67,"_69":27,"_70":27,"_71":47,"_72":73,"_74":75,"_76":-7,"_77":-7},"posts",[7],{"_8":9,"_10":11,"_12":13,"_14":15,"_16":17,"_18":19,"_20":21,"_22":23,"_24":25,"_26":27,"_28":9,"_29":30,"_31":32,"_33":34,"_35":36,"_37":38,"_39":40,"_41":42,"_43":44,"_58":59},"id",25,"slug","share-period-data-privately-clinician-ready-summaries","title","Share Period Data Privately: Clinician‑Ready Summaries","excerpt","Turn your menstrual logs into a private, clinician-ready one-page summary. Learn what to include/redact, remove metadata, choose file formats, and send securely—plus copy-paste templates.","content","

Yes — you can share period data with a doctor privately. Create a one-page, clinician-focused summary that lists key dates, averages, symptoms, medications/contraception, and a one-line request. Export it as a sanitized, flattened PDF (or a minimal CSV if specifically requested), remove metadata, encrypt or password-protect the file, and send it via the clinic’s secure portal or an agreed secure channel.

\n\n

Why a privacy-first clinician summary matters

Sharing raw app exports can reveal more than your cycles: hidden metadata, device or analytics IDs, GPS coordinates on images, and revision history can travel with a file. Recent reporting and legal rulings (including high-profile femtech privacy cases) show period data is sensitive and sometimes mishandled, which is why a privacy-first approach matters.

Clinicians prefer concise, structured menstrual histories — treat cycles like a vital sign. A one-page summary focuses on what clinicians need while keeping everything else private. Framing sharing as a controlled, consented choice lets you support care without an all-or-nothing tradeoff.

\n\n

What clinicians typically want (one-page checklist)

Identifiers & context: name, DOB, contact, and reason for sharing (e.g., “irregular cycles, 6 months”).
Quick summary: average cycle length (+ range), average bleed length, and main symptom(s).
Timeline snippet: start dates for the last 6 cycles (explicit dates).
Key numbers: shortest and longest cycle in period reviewed; days of heavy flow; missed periods.
Symptoms by phase: cramps, mood changes, migraines, ovulation signs with cycle-day timing.
Reproductive & medical context: meds, contraception, pregnancy/fertility attempts, diagnoses, surgeries, family history.
One-line goal: clear request for the visit (testing, diagnosis, fertility planning).

\n\n\n

\"Close-up — Photo by Karolina Grabowska www.kaboompics.com on Pexels

\n\n\n\n

How to draft your clinician-ready one-page summary (step-by-step)

Step A — write a plain-language, single-page summary using exact dates. Clinicians like dates (YYYY-MM-DD) rather than “last month.” Keep sentences short and use headings and bullets so the clinician can scan quickly.

Create a header: Name / DOB / contact and one-line reason for sharing.
Quick stats: average cycle ± range; average bleed length; shortest/longest cycle.
Timeline: last 6 cycle start dates listed on one line or a short column.
Symptoms & timing: bullet list linking symptom to cycle day or phase (e.g., “Severe cramps, days −1 to +2”).
Context: meds, contraception, known diagnoses, surgeries, pregnancies.
Goal: one-line request (e.g., “Please evaluate for PCOS and advise testing options.”)

Formatting tips:

Use bold headings and short bullets for scanability.
Include a tiny timeline snippet for the last 6 cycles (comma-separated dates).
If you need to supply more detail, prepare an extended version but send the concise page first.

\n\n

Exporting only the data you mean to share

Step B — export minimal data. Avoid sharing full app backups or JSON exports that include analytics and internal IDs. Instead:

Copy your one-page summary into a fresh document and export that file (this avoids hidden history from the source app).
If the clinician requests raw logs (temperatures, ovulation test positives), export a small CSV with only the relevant columns and date range.
Choose PDF for summaries; choose CSV only when asked for numeric logs. Avoid sharing raw JSON or full backups unless explicitly requested and redacted.

\n\n

Remove hidden metadata and redact safely

Step C — strip metadata and redact properly. Hidden content can include author name, device IDs, timestamps, comments, and revision history. Visual cover-ups (black boxes drawn over text) are not true redaction and can fail.

Practical steps:

Use a PDF sanitizer or redaction tool (Adobe Acrobat Pro’s “Sanitize document / Redact” is a reliable option) to remove hidden content and permanently redact text.
For images, strip EXIF/GPS data before embedding or sharing. Many image editors and EXIF removers let you remove location metadata.
Prefer client-side metadata removers when possible (verify the tool actually runs in your browser or on your device), and avoid unknown cloud services that keep copies.
Verify redaction: re-open the file and try to copy/paste redacted content — it should not be retrievable.

\n\n\n\n

Choose a secure file format and protect it

Steps D & E — choose format and protect the file. For most clinicians a flattened PDF is ideal: printable, non-editable, and supports true redaction and encryption.

PDF: Save or export the one-page summary as PDF, sanitize/redact, then encrypt with AES-256 password protection.
CSV: Use only when clinician asks for raw logs (e.g., basal temperatures). Trim to necessary columns and date range before exporting.
Encryption: Password-protect the PDF (AES-256) or use an encrypted ZIP. Share the password by phone or a separate secure message channel — never in the same email as the file.

Tools: Adobe Acrobat (offline Pro preferred), trusted local ZIP utilities, or verified client-side encryptors. Avoid unknown online services that process files server-side unless you confirm their privacy policy.

\n\n\n

\n\n\n\n

Secure transmission: safest ways to send your summary

Step F — pick a secure channel. Rank-ordered options:

Clinic/EHR patient portal: Best — file is placed inside the clinical record and stays on the practice’s secure system.
Clinic secure upload / HIPAA-compliant file transfer: Many clinics use services like Klara or Paubox. Confirm with the clinic first.
Encrypted/passworded PDF via email: Acceptable if the clinic requests it; deliver the password by phone or separate message.
Messaging apps: Use only if the clinician explicitly agrees and documents patient preference. Recognize provider BAAs and platform limits.

What to ask the clinic:

How will this file be stored and who can access it?
Will you add the file to my chart or keep it in external storage?
Do you prefer a portal upload or a password-protected PDF sent by email?

\n\n

What to redact (practical redaction checklist)

Remove device/analytics IDs, software names, and revision histories.
Strip or remove GPS/EXIF data from photos before attaching.
Delete or redact non-clinical personal notes (partner/sexual history unless clinically relevant).
Avoid sharing contact or account usernames linked to third parties.
Verify redaction by opening the sanitized file and attempting simple searches or copy/paste of removed text.

\n\n

Export format pros & cons (quick reference)

PDF — Pros: printable, redaction-supported, can be encrypted. Cons: larger files; if not sanitized, hidden metadata may remain.
CSV — Pros: useful for numeric analysis (temps, cycle-day flags). Cons: can include metadata, timestamps, and IDs — trim before sending.
JSON / App backup — Pros: machine-readable, complete. Cons: contains internal metadata and analytics; avoid unless requested and fully redacted.

\n\n

Two copy-paste templates: Clinician and Partner

Clinician template (paste into portal or email)

Subject: Menstrual summary for appointment — [Your name, DOB]

Hi Dr. [Name] / Clinic team,

I’m sharing a one-page summary of my menstrual cycles for the past 6 cycles to support our upcoming visit. Quick highlights:

Concern / reason: [e.g., irregular cycles / heavy bleeding / TTC / severe cramps]
Average cycle (last 6): [e.g., 34 days; range 25–42]
Average bleed length: [e.g., 6 days]
Notable symptoms: [e.g., severe cramps day −1 to 2; mood swings luteal days −7 to −1]
Relevant meds/conditions: [e.g., combined OCP stopped 6 months ago; PCOS diagnosed 2024]
Files attached: One-page PDF summary (sanitized & password-protected). Password sent by phone.

My question for the visit: [e.g., “Could we evaluate for PCOS and discuss testing?”]

Thank you,

[Your name, DOB, phone]

\n\n

Partner template (short, privacy-minded)

Hey [Name],

Typical cycle length: [e.g., 30–35 days]
Period length: [e.g., 5–7 days]
Days with cramps/low energy: [e.g., day −1 through day 2]
What helps: [e.g., heat pack, ibuprofen, rest]

Please don’t forward this without asking me first.

\n\n

Exact intake phrasing for forms and portal messages

Use this short intake line for a portal “reason for visit” or message box:

“Sharing a 1‑page menstrual summary and recent cycle dates for evaluation of [irregular periods / PCOS / fertility timing / heavy bleeding / severe cramps]. Please review the attached PDF (last 6 cycles). I’m happy to discuss details in the visit.”

Optional privacy preference line:

“Privacy preference: Please do not share this file outside my care team without my explicit consent. I have provided a redacted summary rather than a full app backup.”

\n\n

Short checklist of free, privacy-focused tools

Local editing: Pages (Mac), Word (offline) — edit and save locally to avoid cloud sync.
PDF sanitization & redaction: Adobe Acrobat Pro (offline) — use Sanitize/Redact. Online tools like MetaClean, LuxPDF, MetadataFinder can strip metadata if they confirm client-side processing.
Password/encryption: Adobe’s password protect, trusted ZIP utilities (7-Zip) for AES encryption; share passwords separately.
EXIF removal: Phone settings to remove location, or EXIF strippers before attaching images.
CSV editing: Spreadsheet apps (offline) — create minimal CSVs with only requested columns.
Final send: Clinic/EHR portal preferred; otherwise, password-protected PDF + password sent by phone.

\n\n

Framing sharing as consented and reversible

Before you send, ask how the clinic will store the file and who will see it. Request chart upload rather than external storage when possible. Document that you voluntarily shared a sanitized summary and keep a local redacted copy for your records.

Remember: you can offer more information in-person if needed. Sharing is a choice you control — start small, and expand only if clinically helpful.

\n\n

Quick examples: clinician-ready summary (PCOS, TTC, first-period)

Example 1 — PCOS concern (mini summary)

Name/DOB: Alex R., 1994-06-12 | Reason: Irregular cycles, concerns for PCOS

Average cycle (last 6): 38 days; range 28–62
Average bleed: 6 days; heavy flow days 2–3
Last 6 start dates: 2025-06-01, 2025-04-24, 2025-03-16, 2025-02-06, 2024-12-30, 2024-11-20
Symptoms: Acne and irregular periods for 2+ years; mild hirsutism; occasional ovulation pain
Meds/History: No hormonal contraceptives; BMI 31; family history of diabetes
Goal: Please evaluate for PCOS and advise on testing (US/androgen labs).

\n\n

Example 2 — Trying to conceive (TTC)

Name/DOB: Jamie S., 1990-02-18 | Reason: Timing for conception

Average cycle (last 6): 29 days; range 27–31
Last 6 start dates: 2025-06-05, 2025-05-07, 2025-04-08, 2025-03-10, 2025-02-09, 2025-01-11
Symptoms: Positive ovulation test on cycle day 13 for 3 cycles; BBT shift noted mid-luteal
Meds/History: Prenatal vitamin; no contraception past year
Goal: Advice on timing and whether any fertility testing is recommended.

\n\n

Final checklist before you send (one-minute review)

Is this a single, concise page with header and one-line goal?
Did I remove metadata and redact non-essential notes?
Is the file flattened (PDF) and password-protected if not using a portal?
Have I confirmed the clinic’s preferred upload method?
Will I send the password by phone or a separate message?
Did I keep a local redacted copy and note the sharing in my records?

You are in control: sharing can be narrow, reversible, and focused on care.

\n\n

References and further reading

ACOG — Menstruation as a vital sign (clinical guidance)
MSD Manuals — Gynecologic evaluation and menstrual history elements
Adobe Help — PDF redaction and sanitization guidance
Recent investigative reporting on femtech privacy and legal rulings (summary coverage)
Client-side metadata tools (MetaClean, LuxPDF, MetadataFinder) — verify privacy claims before use

\n\n

Conclusion

Sharing period data with a doctor doesn’t mean sacrificing privacy. A short, clinician-focused one-page summary, properly sanitized and sent through a secure channel, gives clinicians what they need while keeping your broader data private. If you’d like, I can draft a printable one-page template (concise and extended) you can paste your dates into.

","contentPlain","Yes — you can share period data with a doctor privately. Create a one-page, clinician-focused summary that lists key dates, averages, symptoms, medications/contraception, and a one-line request. Export it as a sanitized, flattened PDF (or a minimal CSV if specifically requested), remove metadata, encrypt or password-protect the file, and send it via the clinic’s secure portal or an agreed secure channel.\n\nWhy a privacy-first clinician summary matters\nSharing raw app exports can reveal more than your cycles: hidden metadata, device or analytics IDs, GPS coordinates on images, and revision history can travel with a file. Recent reporting and legal rulings (including high-profile femtech privacy cases) show period data is sensitive and sometimes mishandled, which is why a privacy-first approach matters.\nClinicians prefer concise, structured menstrual histories — treat cycles like a vital sign. A one-page summary focuses on what clinicians need while keeping everything else private. Framing sharing as a controlled, consented choice lets you support care without an all-or-nothing tradeoff.\n\nWhat clinicians typically want (one-page checklist)\n\n Identifiers & context: name, DOB, contact, and reason for sharing (e.g., “irregular cycles, 6 months”).\n Quick summary: average cycle length (+ range), average bleed length, and main symptom(s).\n Timeline snippet: start dates for the last 6 cycles (explicit dates).\n Key numbers: shortest and longest cycle in period reviewed; days of heavy flow; missed periods.\n Symptoms by phase: cramps, mood changes, migraines, ovulation signs with cycle-day timing.\n Reproductive & medical context: meds, contraception, pregnancy/fertility attempts, diagnoses, surgeries, family history.\n One-line goal: clear request for the visit (testing, diagnosis, fertility planning).\n\n\n\n\n \n Photo by Karolina Grabowska www.kaboompics.com on Pexels\n\n\n\n\nHow to draft your clinician-ready one-page summary (step-by-step)\nStep A — write a plain-language, single-page summary using exact dates. Clinicians like dates (YYYY-MM-DD) rather than “last month.” Keep sentences short and use headings and bullets so the clinician can scan quickly.\n\n Create a header: Name / DOB / contact and one-line reason for sharing.\n Quick stats: average cycle ± range; average bleed length; shortest/longest cycle.\n Timeline: last 6 cycle start dates listed on one line or a short column.\n Symptoms & timing: bullet list linking symptom to cycle day or phase (e.g., “Severe cramps, days −1 to +2”).\n Context: meds, contraception, known diagnoses, surgeries, pregnancies.\n Goal: one-line request (e.g., “Please evaluate for PCOS and advise testing options.”)\n\nFormatting tips:\n\n Use bold headings and short bullets for scanability.\n Include a tiny timeline snippet for the last 6 cycles (comma-separated dates).\n If you need to supply more detail, prepare an extended version but send the concise page first.\n\n\nExporting only the data you mean to share\nStep B — export minimal data. Avoid sharing full app backups or JSON exports that include analytics and internal IDs. Instead:\n\n Copy your one-page summary into a fresh document and export that file (this avoids hidden history from the source app).\n If the clinician requests raw logs (temperatures, ovulation test positives), export a small CSV with only the relevant columns and date range.\n Choose PDF for summaries; choose CSV only when asked for numeric logs. Avoid sharing raw JSON or full backups unless explicitly requested and redacted.\n\n\nRemove hidden metadata and redact safely\nStep C — strip metadata and redact properly. Hidden content can include author name, device IDs, timestamps, comments, and revision history. Visual cover-ups (black boxes drawn over text) are not true redaction and can fail.\nPractical steps:\n\n Use a PDF sanitizer or redaction tool (Adobe Acrobat Pro’s “Sanitize document / Redact” is a reliable option) to remove hidden content and permanently redact text.\n For images, strip EXIF/GPS data before embedding or sharing. Many image editors and EXIF removers let you remove location metadata.\n Prefer client-side metadata removers when possible (verify the tool actually runs in your browser or on your device), and avoid unknown cloud services that keep copies.\n Verify redaction: re-open the file and try to copy/paste redacted content — it should not be retrievable.\n\n\n\n \n \n Turn your cycle logs into a private, clinician-ready summary\n Use the app’s cycle-tracking and journaling to assemble the key dates and symptoms, then export a focused one-page summary you can sanitize and share. Try the free 7-day trial to create and export a clinician-friendly PDF.\n \n Try App Free\n \n \n \n \n\n\nChoose a secure file format and protect it\nSteps D & E — choose format and protect the file. For most clinicians a flattened PDF is ideal: printable, non-editable, and supports true redaction and encryption.\n\n PDF: Save or export the one-page summary as PDF, sanitize/redact, then encrypt with AES-256 password protection.\n CSV: Use only when clinician asks for raw logs (e.g., basal temperatures). Trim to necessary columns and date range before exporting.\n Encryption: Password-protect the PDF (AES-256) or use an encrypted ZIP. Share the password by phone or a separate secure message channel — never in the same email as the file.\n\nTools: Adobe Acrobat (offline Pro preferred), trusted local ZIP utilities, or verified client-side encryptors. Avoid unknown online services that process files server-side unless you confirm their privacy policy.\n\n\n\n \n Photo by Mingyang LIU on Pexels\n\n\n\n\nSecure transmission: safest ways to send your summary\nStep F — pick a secure channel. Rank-ordered options:\n\n Clinic/EHR patient portal: Best — file is placed inside the clinical record and stays on the practice’s secure system.\n Clinic secure upload / HIPAA-compliant file transfer: Many clinics use services like Klara or Paubox. Confirm with the clinic first.\n Encrypted/passworded PDF via email: Acceptable if the clinic requests it; deliver the password by phone or separate message.\n Messaging apps: Use only if the clinician explicitly agrees and documents patient preference. Recognize provider BAAs and platform limits.\n\nWhat to ask the clinic:\n\n How will this file be stored and who can access it?\n Will you add the file to my chart or keep it in external storage?\n Do you prefer a portal upload or a password-protected PDF sent by email?\n\n\nWhat to redact (practical redaction checklist)\n\n Remove device/analytics IDs, software names, and revision histories.\n Strip or remove GPS/EXIF data from photos before attaching.\n Delete or redact non-clinical personal notes (partner/sexual history unless clinically relevant).\n Avoid sharing contact or account usernames linked to third parties.\n Verify redaction by opening the sanitized file and attempting simple searches or copy/paste of removed text.\n\n\nExport format pros & cons (quick reference)\n\n PDF — Pros: printable, redaction-supported, can be encrypted. Cons: larger files; if not sanitized, hidden metadata may remain.\n CSV — Pros: useful for numeric analysis (temps, cycle-day flags). Cons: can include metadata, timestamps, and IDs — trim before sending.\n JSON / App backup — Pros: machine-readable, complete. Cons: contains internal metadata and analytics; avoid unless requested and fully redacted.\n\n\nTwo copy-paste templates: Clinician and Partner\nClinician template (paste into portal or email)\nSubject: Menstrual summary for appointment — [Your name, DOB]\nHi Dr. [Name] / Clinic team,\nI’m sharing a one-page summary of my menstrual cycles for the past 6 cycles to support our upcoming visit. Quick highlights:\n\n Concern / reason: [e.g., irregular cycles / heavy bleeding / TTC / severe cramps]\n Average cycle (last 6): [e.g., 34 days; range 25–42]\n Average bleed length: [e.g., 6 days]\n Notable symptoms: [e.g., severe cramps day −1 to 2; mood swings luteal days −7 to −1]\n Relevant meds/conditions: [e.g., combined OCP stopped 6 months ago; PCOS diagnosed 2024]\n Files attached: One-page PDF summary (sanitized & password-protected). Password sent by phone.\n\nMy question for the visit: [e.g., “Could we evaluate for PCOS and discuss testing?”]\nThank you,\n[Your name, DOB, phone]\n\nPartner template (short, privacy-minded)\nHey [Name],\n\n Typical cycle length: [e.g., 30–35 days]\n Period length: [e.g., 5–7 days]\n Days with cramps/low energy: [e.g., day −1 through day 2]\n What helps: [e.g., heat pack, ibuprofen, rest]\n\nPlease don’t forward this without asking me first.\n\nExact intake phrasing for forms and portal messages\nUse this short intake line for a portal “reason for visit” or message box:\n“Sharing a 1‑page menstrual summary and recent cycle dates for evaluation of [irregular periods / PCOS / fertility timing / heavy bleeding / severe cramps]. Please review the attached PDF (last 6 cycles). I’m happy to discuss details in the visit.”\nOptional privacy preference line:\n“Privacy preference: Please do not share this file outside my care team without my explicit consent. I have provided a redacted summary rather than a full app backup.”\n\nShort checklist of free, privacy-focused tools\n\n Local editing: Pages (Mac), Word (offline) — edit and save locally to avoid cloud sync.\n PDF sanitization & redaction: Adobe Acrobat Pro (offline) — use Sanitize/Redact. Online tools like MetaClean, LuxPDF, MetadataFinder can strip metadata if they confirm client-side processing.\n Password/encryption: Adobe’s password protect, trusted ZIP utilities (7-Zip) for AES encryption; share passwords separately.\n EXIF removal: Phone settings to remove location, or EXIF strippers before attaching images.\n CSV editing: Spreadsheet apps (offline) — create minimal CSVs with only requested columns.\n Final send: Clinic/EHR portal preferred; otherwise, password-protected PDF + password sent by phone.\n\n\nFraming sharing as consented and reversible\nBefore you send, ask how the clinic will store the file and who will see it. Request chart upload rather than external storage when possible. Document that you voluntarily shared a sanitized summary and keep a local redacted copy for your records.\nRemember: you can offer more information in-person if needed. Sharing is a choice you control — start small, and expand only if clinically helpful.\n\nQuick examples: clinician-ready summary (PCOS, TTC, first-period)\nExample 1 — PCOS concern (mini summary)\nName/DOB: Alex R., 1994-06-12 | Reason: Irregular cycles, concerns for PCOS\n\n Average cycle (last 6): 38 days; range 28–62\n Average bleed: 6 days; heavy flow days 2–3\n Last 6 start dates: 2025-06-01, 2025-04-24, 2025-03-16, 2025-02-06, 2024-12-30, 2024-11-20\n Symptoms: Acne and irregular periods for 2+ years; mild hirsutism; occasional ovulation pain\n Meds/History: No hormonal contraceptives; BMI 31; family history of diabetes\n Goal: Please evaluate for PCOS and advise on testing (US/androgen labs).\n\n\nExample 2 — Trying to conceive (TTC)\nName/DOB: Jamie S., 1990-02-18 | Reason: Timing for conception\n\n Average cycle (last 6): 29 days; range 27–31\n Last 6 start dates: 2025-06-05, 2025-05-07, 2025-04-08, 2025-03-10, 2025-02-09, 2025-01-11\n Symptoms: Positive ovulation test on cycle day 13 for 3 cycles; BBT shift noted mid-luteal\n Meds/History: Prenatal vitamin; no contraception past year\n Goal: Advice on timing and whether any fertility testing is recommended.\n\n\nFinal checklist before you send (one-minute review)\n\n Is this a single, concise page with header and one-line goal?\n Did I remove metadata and redact non-essential notes?\n Is the file flattened (PDF) and password-protected if not using a portal?\n Have I confirmed the clinic’s preferred upload method?\n Will I send the password by phone or a separate message?\n Did I keep a local redacted copy and note the sharing in my records?\n\nYou are in control: sharing can be narrow, reversible, and focused on care.\n\nReferences and further reading\n\n ACOG — Menstruation as a vital sign (clinical guidance)\n MSD Manuals — Gynecologic evaluation and menstrual history elements\n Adobe Help — PDF redaction and sanitization guidance\n Recent investigative reporting on femtech privacy and legal rulings (summary coverage)\n Client-side metadata tools (MetaClean, LuxPDF, MetadataFinder) — verify privacy claims before use\n\n\nConclusion\nSharing period data with a doctor doesn’t mean sacrificing privacy. A short, clinician-focused one-page summary, properly sanitized and sent through a secure channel, gives clinicians what they need while keeping your broader data private. If you’d like, I can draft a printable one-page template (concise and extended) you can paste your dates into.","metaTitle","Share Period Data with Doctor — Private Clinician Summary","metaDescription","A privacy-first, step-by-step guide to turning menstrual logs into a one-page, clinician-ready summary: what to include, redact, export formats, and secure sending.","ogImageUrl","https://images.pexels.com/photos/7691972/pexels-photo-7691972.jpeg?auto=compress&cs=tinysrgb&fit=crop&h=627&w=1200","authorId",1,"categoryId","status","published","publishedAt",["D",1770183273347],"updatedAt",["D",1770183273347],"createdAt",["D",1770183273347],"readingTimeMinutes",10,"isFeatured",false,"viewCount",0,"author",{"_8":27,"_10":45,"_46":47,"_48":49,"_50":-5,"_51":-5,"_52":-5,"_53":-5,"_54":-5,"_55":-5,"_35":56,"_33":57},"lunara","name","Lunara","bio","Hi, I'm Lunara. I was tired of wellness \n tools that felt like chores, or worse, like they were judging me. \n \n I believe your body already knows what it needs. My job is just to \n help you listen. Whether you're tracking your cycle, building a \n morning routine, or simply trying to understand why Tuesdays feel \n harder than Mondays — I'm here to be a quiet companion, not a \n demanding coach. \n \n I care deeply about your privacy. Your data stays yours. I'll never \n sell it, never train AI on your personal moments, and I'll always give\n you a way out if you need one. Some things are just between you and \n your journal. \n \n When I'm not thinking about cycle phases and habit streaks, you'll \n find me advocating for women's health literacy, learning about the \n science of rest, and reminding people that \"good enough\" is actually \n good enough. \n \n I'm so glad you're here. 🌙 ","avatarUrl","jobTitle","company","twitterHandle","linkedinUrl","websiteUrl",["D",1770042392705],["D",1770042392705],"category",{"_8":9,"_10":60,"_46":61,"_62":-5,"_20":63,"_22":64,"_65":-5,"_35":66},"privacy-practical-wellness","Privacy & Practical Wellness","description","Privacy & Practical Wellness | Blog","Articles about privacy & practical wellness","parentId",["D",1770183273345],{"_8":9,"_10":60,"_46":61,"_62":-5,"_20":63,"_22":64,"_65":-5,"_35":68},["D",1770183273345],"currentPage","totalPages","siteName","siteUrl","https:/getlunaraapp.com","canonicalUrl","https://getlunaraapp.com/category/privacy-practical-wellness","prevUrl","nextUrl","actionData","errors"]