[{"_1":2,"_81":-5,"_82":-5},"loaderData",{"_3":4},"routes/tag.$slug",{"_5":6,"_66":67,"_72":26,"_73":26,"_74":46,"_75":76,"_77":78,"_79":-7,"_80":-7},"posts",[7],{"_8":9,"_10":11,"_12":13,"_14":15,"_16":17,"_18":19,"_20":13,"_21":22,"_23":24,"_25":26,"_27":9,"_28":29,"_30":31,"_32":33,"_34":35,"_36":37,"_38":39,"_40":41,"_42":43,"_57":58},"id",11,"slug","12-point-privacy-audit-period-tracker","title","12-Point Privacy Audit for Your Period-Tracking App","excerpt","A one‑sitting, non‑technical 12‑step privacy audit for period‑tracking apps—check permissions, export/delete old data, secure widgets, and build gentle habits to keep your menstrual data private.","content","

Introduction

Your period app contains some of your most personal data — and a few quick checks can dramatically lower who sees it. In one sitting (about 60–120 minutes) you can run a 12‑point privacy audit: review the app’s privacy label and hosting, tighten iPhone permissions, disable trackers, export or delete old data, secure your device, and build simple widget and backup habits to reduce real‑world risks.

This article walks you step‑by‑step through quick checks, settings and permissions, data‑control actions, non‑technical security checks, and gentle habit and journaling prompts. It also links to recent 2024–2025 research and legal context so you’ll know why each action matters.

\n\n

Why a privacy audit matters right now

Cycle‑tracking data is highly valuable to advertisers and can cause real harms when mishandled. A June 2025 report from the University of Cambridge and the Minderoo Centre described menstrual data as a “gold mine” for marketers and warned of safety risks from wide data sharing. At the same time, 2025 legal actions (reported by outlets like The Verge) show courts are taking non‑consensual collection seriously.

Academic reviews (JMIR and others) repeatedly find apps often request more permissions than needed and have inconsistent data‑minimization or retention practices. For you, that can mean targeted ads, uncomfortable disclosures on a shared device, or—rare but real—data vulnerable to legal requests or misuse.

\n\n

How to use this guide: one sitting, practical steps

Each of the 12 steps below takes about 5–30 minutes. You can complete the whole audit in one focused session (60–120 minutes) or split it across two coffee breaks. No technical tools required — all tasks are doable on an iPhone with basic settings and the app itself.

By the end you’ll have clearer permissions, fewer trackers, a plan for exports/deletions, and a short journaling prompt to help turn this into a habit.

\n\n

Quick reality check: what apps often share and why it matters

Period apps commonly collect:

Health details (cycle dates, symptoms, pregnancy attempts)
Identifiers (email, device IDs, advertising IDs)
Analytics and crash logs sent to third parties
Location, timestamps, and usage metadata

Advertisers and data brokers can combine these signals to infer sensitive states (like pregnancy) and target ads or offers. The Cambridge/Minderoo work and related studies show this data can be repackaged, resold, or combined with other sources to create detailed profiles.

Non‑obvious harms include discrimination, subpoenas or legal requests for historic logs, and stalking. The “intimate harms” framework from legal scholarship (2024) reminds us that privacy harms are not just financial — they can affect safety, reputation, and autonomy.

\n\n

The 12‑Point Privacy Audit (quick checklist)

This audit groups action into: Quick checks, Settings & permissions, Data control, Non‑technical security, and Everyday habits. Each step below explains what to do, why it matters, and the real‑life risk it reduces. Use the mini‑checklist at the end to copy and run the audit now.

\n\n

Quick checks (steps 1–2)

\n Step 1 — Check the app’s App Store privacy label and privacy page\n
How: Open the app’s App Store page and tap the Privacy section, or open the app’s privacy policy from its settings or website. Note categories listed: Health, Identifiers, Analytics, Advertising.
\n
Why: App Store labels and the privacy page reveal first‑order data flows and whether the app shares with ad networks or brokers. Many apps still list analytics or ad categories alongside health data.
\n
Real‑life risk: Unexpected sharing can lead to targeted ads or profiling connected to reproductive events.
\n
\n Step 2 — Find where your data is stored/processed\n
How: Search the privacy policy for words like “data storage,” “GDPR,” “EU,” “Germany,” or named cloud providers (AWS, Google Cloud). Note the data controller’s country and any cross‑border transfer language.
\n
Why: Jurisdiction affects your rights. EU/Germany hosting often comes with stronger deletion and access rights; US‑based storage can mean different legal exposures.
\n
Real‑life risk: Data stored in weaker jurisdictions may be easier for third parties or legal processes to access.
\n

\n\n\n

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

\n\n\n\n

Settings & permissions (steps 3–5)

\n Step 3 — Review iPhone app permissions\n
How: Go to Settings → [App Name]. Check Location, Health, Photos, Notifications, and Background App Refresh. Revoke non‑essential items and turn off Background App Refresh if you don’t need real‑time sync.
\n
Why: Permissions leak metadata — location plus timestamps can reveal clinic visits or routines. Notifications and widgets can show sensitive content on a lock screen.
\n
Real‑life risk: Accidental exposure on shared phones; third parties using timestamps to infer private events.
\n
\n Step 4 — Check Health app integrations and third‑party connections\n
How: Open Health → Data Access & Devices and revoke apps you don’t want syncing. In the app, look for “Connected services” and disconnect calendars, Google, Fitbit, or other integrations you didn’t intentionally enable.
\n
Why: Connected services multiply storage points and potential leaks.
\n
Real‑life risk: Calendar or fitness integrations could unintentionally broadcast sensitive entries or metadata across accounts.
\n
\n Step 5 — Turn off analytics/advertising tracking\n
How: In the app settings look for “Share analytics,” “Personalized ads,” or similar toggles and disable them. Also check iOS Settings → Privacy → Tracking and disable “Allow Apps to Request to Track.”
\n
Why: Many apps send usage and event data to analytics or ad networks. Opting out reduces the chance that cycle signals are included in ad‑targeting pools.
\n
Real‑life risk: More specific ad targeting or resale of sensitive events.
\n

\n\n

Data control & account actions (steps 6–7)

\n Step 6 — Export and delete old data\n
How: Use the app’s export tool (often in Settings → Privacy / Account). Expect CSV or JSON formats. Before deleting, verify the export opens correctly and store it in an encrypted folder or secure location if you need a copy.
\n
Why: Exporting gives you control and makes it safe to remove historic logs from a service you no longer trust.
\n
Real‑life risk: Long‑retained histories can be subpoenaed or sold later; exporting lets you limit live exposure.
\n
\n Step 7 — Read retention & deletion policy and make a deletion request\n
How: Search the privacy policy for “retention,” “delete,” or “data controller.” Use the provided privacy contact or in‑app support to request deletion. Save confirmation emails or request IDs as proof.
\n
Why: Policies vary; keeping records of your request protects you if data is later found to remain in backups.
\n
Real‑life risk: Unclear deletion policies mean data may persist in backups or be transferred to third parties.
\n

\n\n

Non‑technical security checks (steps 8–9)

\n Step 8 — Secure your device & lock screen\n
How: Set a strong passcode, enable Face/Touch ID, and change Notifications → Show Previews to “When Unlocked” or “Never.” Consider enabling “Erase Data” after several failed attempts if you prefer.
\n
Why: Anyone with brief physical access to your phone can read widgets or notifications if the lock screen shows details.
\n
Real‑life risk: Roommates or friends seeing cycle status on a locked screen; casual exposure when leaving your phone on a shared table.
\n
\n Step 9 — Enable two‑factor authentication (2FA)\n
How: Turn on 2FA in the app (if offered) and enable 2FA on the email account linked to the app. Prefer authenticator apps (e.g., Authy, Google Authenticator) or hardware keys over SMS when possible.
\n
Why: 2FA prevents account takeovers that could expose long histories or allow someone to impersonate you in support requests.
\n
Real‑life risk: Unauthorized access, doxxing, or harassment from compromised accounts.
\n

\n\n

Everyday habits & translations of findings (steps 10–12)

\n Step 10 — Widget and home‑screen hygiene\n
Habit: Prefer minimal widgets that show non‑specific info (e.g., “Cycle: day 12”), or disable widgets that reveal details. If the app offers private‑by‑default widgets, use them.
\n
Why: Widgets are handy but can reveal sensitive states at a glance to anyone nearby.
\n
Real‑life risk: Accidental disclosure on shared desks, on public transport, or in group settings.
\n
\n Step 11 — Backup policy habit\n
Habit: Check whether the app data is included in iCloud backups. If you prefer fewer copies, consider encrypted local backups or exclude the app from cloud backups. Schedule a quarterly review.
\n
Why: Backups create multiple copies of your data across accounts and devices, increasing exposure.
\n
Real‑life risk: More copies mean higher chance of access through synced accounts or legal requests.
\n
\n Step 12 — Journal & reflection prompt\n
Habit: Write a short private journal entry after auditing. Template: “What I changed today: ___ . How that felt: ___ . Next small step: ___.” Optional prompt: “What did I learn about my digital boundaries today?”
\n
Why: Journaling reinforces behaviour change without fear; it’s a gentle way to record choices and plan next steps.
\n
Real‑life benefit: Keeps you from slipping back into unsafe defaults and builds a sustainable privacy routine.
\n

\n\n\n

\"A — Photo by Lisa from Pexels on Pexels

\n\n\n\n

Feature highlight: how an app can make privacy easy

\n\n\n

Linking audit findings to real‑life risks

Shared devices / roommates: Widgets and lock‑screen previews can reveal cycle status. Fixes: hide previews, limit widgets, and secure device (Steps 3, 8, 10).

Targeted ads / commercial profiling: Third‑party analytics and ad sharing power precise targeting. Fixes: disable analytics/ads in app and system tracking (Step 5) and prefer apps that don’t share with ad networks (Step 1).

Legal / subpoenas: Historic records can be requested in legal processes. Fixes: export what you need and request deletion; choose apps with clear retention policies or local‑first storage if you need stronger protection (Steps 6–7).

Stalking / cyberstalking: Location and timestamps combined with logs can be dangerous. Fixes: revoke location access, disconnect calendar/fusion integrations, harden device access (Steps 3, 4, 8).

\n\n

Practical recommendations when choosing or switching apps

Look for explicit local‑first options or end‑to‑end encrypted cloud sync when available.
Prefer apps with clear retention and deletion policies and an easy export tool.
Avoid apps that automatically share with ad networks; find transparency about third‑party partners.
If you need multi‑device sync (e.g., TTC), choose providers that name their data jurisdiction and support E2EE where possible.
Keep logs minimal: only record what you truly need; store sensitive notes in a separate encrypted journal.

\n\n

Quick starter checklist you can copy (do this now)

Check app privacy label & policy — 5 minutes.
Revoke non‑essential permissions & hide lock‑screen previews — 5–10 minutes.
Disable analytics/ads and disconnect third‑party services — 10 minutes.
Export & delete old data you don’t want stored — 15–30 minutes.
Set a monthly 5‑minute reminder to review widget and backup settings + write a short privacy journal entry — 5 minutes.

Bookmark this checklist and repeat the audit every 3–6 months, or after major app updates.

\n\n

Resources, studies, and where to learn more

University of Cambridge / Minderoo Centre, June 2025: report on cycle‑tracking data risks and governance recommendations.
The Verge, 2025: coverage of a jury ruling on collection of menstrual data (legal context).
JMIR, 2024: studies on user behaviors and app quality in menstrual tracking.
Computer Law & Security Review, 2024: “Intimate harms” framework — why privacy harms go beyond breaches.
App privacy scoring and research from 2023–2024 showing over‑permissioning in many apps.

Plain‑language guides: look up GDPR data deletion rights and templates for data access/deletion requests in your jurisdiction. Save or print the checklist and set a calendar reminder to repeat this audit.

\n\n

Closing and gentle journaling prompt

Small habits protect your choices without fear. A short, regular privacy check keeps defaults working for you rather than against you.

Journaling prompt (3–5 lines): “Today I checked: ___ . One change that mattered: ___ . My next small step: ___.” Schedule a 5‑minute monthly privacy check and you’ll quickly turn this into a sustainable routine.

If you’d like a printable audit, in‑app microcopy for widgets, or a one‑page checklist, I can draft those next.

\n","contentPlain","Introduction\nYour period app contains some of your most personal data — and a few quick checks can dramatically lower who sees it. In one sitting (about 60–120 minutes) you can run a 12‑point privacy audit: review the app’s privacy label and hosting, tighten iPhone permissions, disable trackers, export or delete old data, secure your device, and build simple widget and backup habits to reduce real‑world risks.\nThis article walks you step‑by‑step through quick checks, settings and permissions, data‑control actions, non‑technical security checks, and gentle habit and journaling prompts. It also links to recent 2024–2025 research and legal context so you’ll know why each action matters.\n\nWhy a privacy audit matters right now\nCycle‑tracking data is highly valuable to advertisers and can cause real harms when mishandled. A June 2025 report from the University of Cambridge and the Minderoo Centre described menstrual data as a “gold mine” for marketers and warned of safety risks from wide data sharing. At the same time, 2025 legal actions (reported by outlets like The Verge) show courts are taking non‑consensual collection seriously.\nAcademic reviews (JMIR and others) repeatedly find apps often request more permissions than needed and have inconsistent data‑minimization or retention practices. For you, that can mean targeted ads, uncomfortable disclosures on a shared device, or—rare but real—data vulnerable to legal requests or misuse.\n\nHow to use this guide: one sitting, practical steps\nEach of the 12 steps below takes about 5–30 minutes. You can complete the whole audit in one focused session (60–120 minutes) or split it across two coffee breaks. No technical tools required — all tasks are doable on an iPhone with basic settings and the app itself.\nBy the end you’ll have clearer permissions, fewer trackers, a plan for exports/deletions, and a short journaling prompt to help turn this into a habit.\n\nQuick reality check: what apps often share and why it matters\nPeriod apps commonly collect:\n\n Health details (cycle dates, symptoms, pregnancy attempts)\n Identifiers (email, device IDs, advertising IDs)\n Analytics and crash logs sent to third parties\n Location, timestamps, and usage metadata\n\nAdvertisers and data brokers can combine these signals to infer sensitive states (like pregnancy) and target ads or offers. The Cambridge/Minderoo work and related studies show this data can be repackaged, resold, or combined with other sources to create detailed profiles.\nNon‑obvious harms include discrimination, subpoenas or legal requests for historic logs, and stalking. The “intimate harms” framework from legal scholarship (2024) reminds us that privacy harms are not just financial — they can affect safety, reputation, and autonomy.\n\nThe 12‑Point Privacy Audit (quick checklist)\nThis audit groups action into: Quick checks, Settings & permissions, Data control, Non‑technical security, and Everyday habits. Each step below explains what to do, why it matters, and the real‑life risk it reduces. Use the mini‑checklist at the end to copy and run the audit now.\n\nQuick checks (steps 1–2)\n\n \n Step 1 — Check the app’s App Store privacy label and privacy page\n How: Open the app’s App Store page and tap the Privacy section, or open the app’s privacy policy from its settings or website. Note categories listed: Health, Identifiers, Analytics, Advertising.\n Why: App Store labels and the privacy page reveal first‑order data flows and whether the app shares with ad networks or brokers. Many apps still list analytics or ad categories alongside health data.\n Real‑life risk: Unexpected sharing can lead to targeted ads or profiling connected to reproductive events.\n \n \n Step 2 — Find where your data is stored/processed\n How: Search the privacy policy for words like “data storage,” “GDPR,” “EU,” “Germany,” or named cloud providers (AWS, Google Cloud). Note the data controller’s country and any cross‑border transfer language.\n Why: Jurisdiction affects your rights. EU/Germany hosting often comes with stronger deletion and access rights; US‑based storage can mean different legal exposures.\n Real‑life risk: Data stored in weaker jurisdictions may be easier for third parties or legal processes to access.\n \n\n\n\n\n \n Photo by Karolina Grabowska www.kaboompics.com on Pexels\n\n\n\n\nSettings & permissions (steps 3–5)\n\n \n Step 3 — Review iPhone app permissions\n How: Go to Settings → [App Name]. Check Location, Health, Photos, Notifications, and Background App Refresh. Revoke non‑essential items and turn off Background App Refresh if you don’t need real‑time sync.\n Why: Permissions leak metadata — location plus timestamps can reveal clinic visits or routines. Notifications and widgets can show sensitive content on a lock screen.\n Real‑life risk: Accidental exposure on shared phones; third parties using timestamps to infer private events.\n \n \n Step 4 — Check Health app integrations and third‑party connections\n How: Open Health → Data Access & Devices and revoke apps you don’t want syncing. In the app, look for “Connected services” and disconnect calendars, Google, Fitbit, or other integrations you didn’t intentionally enable.\n Why: Connected services multiply storage points and potential leaks.\n Real‑life risk: Calendar or fitness integrations could unintentionally broadcast sensitive entries or metadata across accounts.\n \n \n Step 5 — Turn off analytics/advertising tracking\n How: In the app settings look for “Share analytics,” “Personalized ads,” or similar toggles and disable them. Also check iOS Settings → Privacy → Tracking and disable “Allow Apps to Request to Track.”\n Why: Many apps send usage and event data to analytics or ad networks. Opting out reduces the chance that cycle signals are included in ad‑targeting pools.\n Real‑life risk: More specific ad targeting or resale of sensitive events.\n \n\n\nData control & account actions (steps 6–7)\n\n \n Step 6 — Export and delete old data\n How: Use the app’s export tool (often in Settings → Privacy / Account). Expect CSV or JSON formats. Before deleting, verify the export opens correctly and store it in an encrypted folder or secure location if you need a copy.\n Why: Exporting gives you control and makes it safe to remove historic logs from a service you no longer trust.\n Real‑life risk: Long‑retained histories can be subpoenaed or sold later; exporting lets you limit live exposure.\n \n \n Step 7 — Read retention & deletion policy and make a deletion request\n How: Search the privacy policy for “retention,” “delete,” or “data controller.” Use the provided privacy contact or in‑app support to request deletion. Save confirmation emails or request IDs as proof.\n Why: Policies vary; keeping records of your request protects you if data is later found to remain in backups.\n Real‑life risk: Unclear deletion policies mean data may persist in backups or be transferred to third parties.\n \n\n\nNon‑technical security checks (steps 8–9)\n\n \n Step 8 — Secure your device & lock screen\n How: Set a strong passcode, enable Face/Touch ID, and change Notifications → Show Previews to “When Unlocked” or “Never.” Consider enabling “Erase Data” after several failed attempts if you prefer.\n Why: Anyone with brief physical access to your phone can read widgets or notifications if the lock screen shows details.\n Real‑life risk: Roommates or friends seeing cycle status on a locked screen; casual exposure when leaving your phone on a shared table.\n \n \n Step 9 — Enable two‑factor authentication (2FA)\n How: Turn on 2FA in the app (if offered) and enable 2FA on the email account linked to the app. Prefer authenticator apps (e.g., Authy, Google Authenticator) or hardware keys over SMS when possible.\n Why: 2FA prevents account takeovers that could expose long histories or allow someone to impersonate you in support requests.\n Real‑life risk: Unauthorized access, doxxing, or harassment from compromised accounts.\n \n\n\nEveryday habits & translations of findings (steps 10–12)\n\n \n Step 10 — Widget and home‑screen hygiene\n Habit: Prefer minimal widgets that show non‑specific info (e.g., “Cycle: day 12”), or disable widgets that reveal details. If the app offers private‑by‑default widgets, use them.\n Why: Widgets are handy but can reveal sensitive states at a glance to anyone nearby.\n Real‑life risk: Accidental disclosure on shared desks, on public transport, or in group settings.\n \n \n Step 11 — Backup policy habit\n Habit: Check whether the app data is included in iCloud backups. If you prefer fewer copies, consider encrypted local backups or exclude the app from cloud backups. Schedule a quarterly review.\n Why: Backups create multiple copies of your data across accounts and devices, increasing exposure.\n Real‑life risk: More copies mean higher chance of access through synced accounts or legal requests.\n \n \n Step 12 — Journal & reflection prompt\n Habit: Write a short private journal entry after auditing. Template: “What I changed today: ___ . How that felt: ___ . Next small step: ___.” Optional prompt: “What did I learn about my digital boundaries today?”\n Why: Journaling reinforces behaviour change without fear; it’s a gentle way to record choices and plan next steps.\n Real‑life benefit: Keeps you from slipping back into unsafe defaults and builds a sustainable privacy routine.\n \n\n\n\n\n \n Photo by Lisa from Pexels on Pexels\n\n\n\n\nFeature highlight: how an app can make privacy easy\n\n \n \n Privacy‑friendly defaults and easy export/delete make audits painless\n Tools that default to private widgets, GDPR‑hosted data, and simple export & deletion options reduce friction for doing this audit and keeping your data safe. Use a free trial to test private widgets, journaling, and one‑tap export/delete before committing.\n \n Try App Free\nn \n \n \n \n\n\nLinking audit findings to real‑life risks\nShared devices / roommates: Widgets and lock‑screen previews can reveal cycle status. Fixes: hide previews, limit widgets, and secure device (Steps 3, 8, 10).\nTargeted ads / commercial profiling: Third‑party analytics and ad sharing power precise targeting. Fixes: disable analytics/ads in app and system tracking (Step 5) and prefer apps that don’t share with ad networks (Step 1).\nLegal / subpoenas: Historic records can be requested in legal processes. Fixes: export what you need and request deletion; choose apps with clear retention policies or local‑first storage if you need stronger protection (Steps 6–7).\nStalking / cyberstalking: Location and timestamps combined with logs can be dangerous. Fixes: revoke location access, disconnect calendar/fusion integrations, harden device access (Steps 3, 4, 8).\n\nPractical recommendations when choosing or switching apps\n\n Look for explicit local‑first options or end‑to‑end encrypted cloud sync when available.\n Prefer apps with clear retention and deletion policies and an easy export tool.\n Avoid apps that automatically share with ad networks; find transparency about third‑party partners.\n If you need multi‑device sync (e.g., TTC), choose providers that name their data jurisdiction and support E2EE where possible.\n Keep logs minimal: only record what you truly need; store sensitive notes in a separate encrypted journal.\n\n\nQuick starter checklist you can copy (do this now)\n\n Check app privacy label & policy — 5 minutes.\n Revoke non‑essential permissions & hide lock‑screen previews — 5–10 minutes.\n Disable analytics/ads and disconnect third‑party services — 10 minutes.\n Export & delete old data you don’t want stored — 15–30 minutes.\n Set a monthly 5‑minute reminder to review widget and backup settings + write a short privacy journal entry — 5 minutes.\n\nBookmark this checklist and repeat the audit every 3–6 months, or after major app updates.\n\nResources, studies, and where to learn more\n\n University of Cambridge / Minderoo Centre, June 2025: report on cycle‑tracking data risks and governance recommendations.\n The Verge, 2025: coverage of a jury ruling on collection of menstrual data (legal context).\n JMIR, 2024: studies on user behaviors and app quality in menstrual tracking.\n Computer Law & Security Review, 2024: “Intimate harms” framework — why privacy harms go beyond breaches.\n App privacy scoring and research from 2023–2024 showing over‑permissioning in many apps.\n\nPlain‑language guides: look up GDPR data deletion rights and templates for data access/deletion requests in your jurisdiction. Save or print the checklist and set a calendar reminder to repeat this audit.\n\nClosing and gentle journaling prompt\nSmall habits protect your choices without fear. A short, regular privacy check keeps defaults working for you rather than against you.\nJournaling prompt (3–5 lines): “Today I checked: ___ . One change that mattered: ___ . My next small step: ___.” Schedule a 5‑minute monthly privacy check and you’ll quickly turn this into a sustainable routine.\nIf you’d like a printable audit, in‑app microcopy for widgets, or a one‑page checklist, I can draft those next.\n","metaTitle","metaDescription","A practical 12-step privacy audit for period‑tracking apps: quick checks, settings fixes, and gentle journaling prompts to protect your menstrual data now.","ogImageUrl","https://images.pexels.com/photos/6473738/pexels-photo-6473738.jpeg?auto=compress&cs=tinysrgb&fit=crop&h=627&w=1200","authorId",1,"categoryId","status","published","publishedAt",["D",1770096333690],"updatedAt",["D",1770096333691],"createdAt",["D",1770096333691],"readingTimeMinutes",10,"isFeatured",false,"viewCount",0,"author",{"_8":26,"_10":44,"_45":46,"_47":48,"_49":-5,"_50":-5,"_51":-5,"_52":-5,"_53":-5,"_54":-5,"_34":55,"_32":56},"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":59,"_45":60,"_61":-5,"_20":62,"_21":63,"_64":-5,"_34":65},"privacy-app-safety-period-tracking-guides","Privacy & App Safety / Period Tracking Guides","description","Privacy & App Safety / Period Tracking Guides | Blog","Articles about privacy & app safety / period tracking guides","parentId",["D",1770096333688],"tag",{"_8":68,"_10":69,"_45":70,"_34":71},41,"app-privacy-audit","app privacy audit",["D",1770096333704],"currentPage","totalPages","siteName","siteUrl","https:/getlunaraapp.com","canonicalUrl","https://getlunaraapp.com/tag/app-privacy-audit","prevUrl","nextUrl","actionData","errors"]