[{"_1":2,"_83":-5,"_84":-5},"loaderData",{"_3":4},"routes/tag.$slug",{"_5":6,"_68":69,"_74":27,"_75":27,"_76":48,"_77":78,"_79":80,"_81":-7,"_82":-7},"posts",[7],{"_8":9,"_10":11,"_12":13,"_14":15,"_16":17,"_18":19,"_20":21,"_22":23,"_24":25,"_26":27,"_28":29,"_30":31,"_32":33,"_34":35,"_36":37,"_38":39,"_40":41,"_42":43,"_44":45,"_59":60},"id",30,"slug","export-secure-period-tracker-data-6-step-guide","title","Export & Secure Your Period Tracker Data: 6-Step Guide","excerpt","A practical, privacy-first 6-step guide to export your period-tracker data: export from iPhone or app, audit for PII/metadata, securely archive or transfer, delete what you don’t need, and feel empowered.","content","

Introduction

Export period tracker data securely means: export from the app or Apple Health, inspect the file for PII and hidden metadata, remove or redact sensitive fields, encrypt and archive only what you need, transfer locally or via end-to-end encrypted channels, and permanently delete any unnecessary copies. With growing scrutiny of femtech privacy (three top apps had ~250 million downloads in 2024), taking a privacy-first approach protects you from profiling, unwanted sharing, and unwanted exposure.

This post walks you through a calm, 6-step how‑to: quick iPhone export, automated exports, an advanced local path, an export-audit checklist, safe transfer and archiving tips, filename conventions, secure deletion steps, and gentle journaling prompts so the process feels empowering, not scary.

\n\n

Why exporting your period data matters—and privacy risks to know

Your menstrual data often includes intimate details: period dates and flow, symptoms, sexual activity, contraception, ovulation test results, and private journal notes. That makes it sensitive data; researchers and consumer advocates have flagged femtech apps for sharing or retaining this kind of information in ways users may not expect.

Recent academic and public reports (Cambridge, UCL, King’s College) have highlighted that many apps share data with advertisers or third parties, and that deletion flows can be unclear. In the EU/UK, health and sex‑life data are treated as sensitive under GDPR, which gives you rights to portability and deletion—but these rights vary by region.

What can go wrong: exported files with names, emails, or hidden metadata (EXIF in photos, device IDs) can be used for profiling, targeted advertising, or even re‑identification. The good news: using portability rights and a few practical steps reduces risk without making the process stressful.

\n\n

Before you start: a short privacy checklist to prepare

Decide what to keep. Minimize exported fields: dates, flow, basic symptoms—skip names, emails, or full profile data when possible.
Choose temporary storage. Prefer your personal device (local Files, desktop) over third‑party cloud for the initial export.
Check app settings. Look for built-in Export or Request Data options before using third‑party tools.
Know formats and encryption basics. Exports are often ZIP/XML from Apple Health; converters produce CSV/JSON. Have an AES‑256 capable tool ready (7‑Zip, macOS disk image) if you’ll encrypt.

\n\n

Step 1 — Simple: Quick iPhone export (best for most users)

This path is ideal if your cycle app syncs with Apple Health or you only need a quick, local export.

Open Health → tap your profile (top right) → Export All Health Data. This creates a .zip containing export.xml. (Apple Support documents this process.)
Choose Save to Files locally or AirDrop it to your own Mac/iPhone. Avoid emailing the file.
Unzip locally and inspect export.xml. Look for obvious PII: name, email, userId, or profile notes. If you see attachments (photos, audio), note them for metadata checks.
If you prefer CSV/JSON for review, use a trusted converter locally (applehealth2csv or HealthExport run on your device). Prefer local tools that don’t upload your file to a remote server.

When to use this path: you want a quick, mostly local export with minimal risk and no third‑party servers involved.

\n\n\n

\"Close-up — Photo by Tima Miroshnichenko on Pexels

\n\n\n\n

Step 2 — Intermediate: Automated or scheduled exports

Automations are useful if you want regular backups or trend exports, but they need careful configuration.

Tools to consider: Health Auto Export, HealthExport, exporthealth.app. They can schedule exports and route them to a destination.
Configure carefully: select only the menstrual and symptom fields you need, set a secure destination, and avoid sending raw CSV to unencrypted cloud folders.
Retention policy: set automatic pruning—e.g., keep only the last 6–12 months—and schedule an audit frequency (quarterly recommended).
Risk reduction: prefer local automations (shortcuts that save to your device) or E2EE services. If the tool requires remote servers, read its privacy policy and prefer open‑source or reputable vendors.

\n\n

Step 3 — Advanced: Local conversion and selective exports (for power users)

For full control at the field level, use local CLI tools and small scripts to convert and sanitize exports.

Use applehealth2csv or similar local tools to convert Apple Health XML into CSV/JSON while selecting only the types you need (menstrualFlow, symptoms, notes).
Script redaction: filter out columns like userId, email, deviceId, and remove account metadata automatically during conversion.
Validate the output by sampling rows and checking headers. Import the sanitized CSV into another app only if it supports minimal imports and you’ve confirmed its privacy policy.
When to use: you want complete control, automated sanitization, or are moving large datasets between services you trust.

\n\n

How to audit exported files for PII and hidden metadata

Opening and carefully scanning exports is the best defense. Use simple tools and a checklist-style approach.

Open the file: view the first 20 and last 20 lines of CSV/JSON/XML. Search headers for columns like name, email, phone, userId, or accountId.
Search for attachments: look for image or audio references in the XML or CSV. If present, list those files separately.
Check metadata: for photos/audio, run an EXIF viewer (ExifMeta, ExifTool). Look for GPS coordinates, device timestamps, or camera software fields that could identify you.
Hidden logs and analytics: list the ZIP contents before sharing—some exports include auxiliary logs or analytics files. Remove anything not needed.
Practical redaction: in a spreadsheet, delete columns with PII, export as plain CSV or JSON (this usually strips document properties), and remove attachments before archiving.

Tools that help: ExifTool/ExifMeta for photo metadata, any text editor or spreadsheet for CSV/JSON inspection, and command-line zip list commands to check archive contents.

\n\n

Step 4 — Remove, minimize, and sanitize before you store

Follow the minimalism principle: only keep fields that serve your goal (e.g., spotting cycle length changes).

Drop profile and account fields. Keep essentials: date, flow, symptoms, mood tag.
Journals: search text for names, addresses, partner info, or other identifying details. Either redact those phrases or export journals separately if you need them.
Strip metadata from images and documents before including them. On phone, use a metadata‑stripper app; on desktop, use ExifTool or export as plain images without location.
Save a minimized file and use a clear filename (see conventions below). Keep a copy only if it helps a specific goal like sharing with a provider.

\n\n

Step 5 — Securely archive and transfer: encryption, local transfers, and cloud choices

Encrypt before storing. Prefer local transfers when moving files between your own devices.

Encryption: create an AES‑256 encrypted ZIP/7z or a macOS encrypted disk image. Use a strong, memorable passphrase and store it in your password manager.
Local transfers: AirDrop to your own devices, USB drive, or secure local network copy. Avoid email or insecure links for sensitive files.
Cloud storage: if you use cloud, prefer end‑to‑end encrypted vaults (e.g., paid services with zero‑knowledge encryption) or encrypt locally before uploading.
Importing to another app: verify the app’s import method and privacy policy. Import only minimal fields and prefer apps that explicitly support secure imports.

\n\n\n\n

Step 6 — Permanently delete what you don’t need (and verify deletion)

Deleting data thoroughly requires action in several places.

Delete from the source app: use its delete-account or delete-data flow. Request a confirmation email or screenshot when possible.
Wipe local copies: securely delete files, empty the trash, and remove versions. On macOS and Windows, empty the Trash/Recycle Bin and remove backups (Time Machine snapshots or cloud versions).
Remove cloud copies: delete uploads and clear the cloud provider’s Bin/Trash and any historical versions.
Keep a minimal audit note (no PII): e.g., “export cycles_min deleted on 2025-02-09 from iPhone and iCloud.” Store that note separately from sensitive files.
Legal note: deletion timing and guarantees vary by app and region. Save any deletion confirmation from the app or request written confirmation if needed.

\n\n\n

\n\n\n\n

Filename conventions and versioning for privacy-first archives

Good filenames make audits and deletions simple while protecting privacy.

Do: use neutral names and date stamps. Example: wellbeing-export-2025-02-09_min.csv.
Don’t: include names, emails, or account IDs in filenames. Avoid things like emma_smith_cycles_2025.csv.
Use suffixes for clarity: _min for minimized exports, _full for complete exports, and include the ISO date for versioning.
Quick rules: neutral title + ISO date + suffix. Example: cycles-2025-02-09_min.csv. This helps you find and delete specific files later without revealing identity in the filename.

\n\n

Downloadable export-audit checklist (compact & printable)

Use this short checklist as you work through an export. Save or print it separately from your exports.

Export source & date noted (app or Apple Health) — yes/no
File format checked (XML/CSV/JSON) and previewed — yes/no
PII columns removed (names, emails, phone, account IDs) — yes/no
Attachments checked; EXIF stripped if present — yes/no
Journal entries scanned and sensitive text redacted — yes/no
File archived encrypted (method noted) — yes/no
Original copies securely deleted (device + cloud) — yes/no
Import target privacy reviewed (if sharing/importing) — yes/no

\n\n

Gentle journaling prompts to make exporting feel empowering

Take a moment before or after exporting. These short prompts help you center your intention and reduce anxiety.

What do I want to learn from my cycle data? (patterns, mood, energy)
Which three data fields feel important to keep for my wellness goals?
What privacy boundaries do I want to set around this data?
How will I use this archive—personal reference, provider visit, or research?
One kind thing I’ll do for myself after this: (tea, walk, call a friend)

\n\n

Quick tools & resources (where to export, convert, audit, and encrypt)

Apple Health — built-in export (XML/ZIP).
HealthExport / Health Auto Export — selective export and automation (use cautiously, prefer E2EE or local-only options).
applehealth2csv (GitHub) — local open-source converter for power users.
ExifMeta / ExifTool — view and remove EXIF from photos and attachments.
7‑Zip, macOS encrypted disk images — create AES‑256 encrypted archives.
Authoritative reads: Cambridge Minderoo report and UCL/KCL research on femtech privacy; Apple Support on Health export; ICO guidance on portability and deletion.

\n\n

Legal & safety caveats — what this guide doesn’t promise

Platform and regional differences matter: iOS and Android have different export flows, and GDPR rights apply in the EU/UK but differ elsewhere. This guide explains risk reduction steps—not absolute guarantees. Always check the app’s privacy policy, request deletion or portability under local laws, and save any confirmations you receive.

\n\n

Wrap-up: a calm checklist to finish

Quick recap of the 6 steps:

Prepare: decide what to keep and where to store temporarily.
Simple export: iPhone → Health export → local preview.
Intermediate: set up scheduled exports with minimal fields and retention.
Advanced: convert locally and script field-level redaction.
Archive & transfer: encrypt, prefer AirDrop/USB, or E2EE cloud.
Delete: wipe originals, clear cloud Trash, and keep a minimal audit note.

Taking control of your cycle data is an act of agency. Move at your own pace, use the journaling prompts to stay centered, and keep privacy-first habits so your logs help you—without exposing you. If you’d like, download the printable checklist or try App’s built-in export and PII-removal tools to make an export feel calm and safe.

\n\n

Conclusion

Exporting your period-tracker data securely is doable and empowering with simple habits: minimize what you save, audit exports for PII and metadata, encrypt archives, prefer local transfers or E2EE, and delete what isn’t needed. Use the checklist and journaling prompts to keep the process gentle—you're in control of your data and how it's used.

","contentPlain","Introduction\nExport period tracker data securely means: export from the app or Apple Health, inspect the file for PII and hidden metadata, remove or redact sensitive fields, encrypt and archive only what you need, transfer locally or via end-to-end encrypted channels, and permanently delete any unnecessary copies. With growing scrutiny of femtech privacy (three top apps had ~250 million downloads in 2024), taking a privacy-first approach protects you from profiling, unwanted sharing, and unwanted exposure.\nThis post walks you through a calm, 6-step how‑to: quick iPhone export, automated exports, an advanced local path, an export-audit checklist, safe transfer and archiving tips, filename conventions, secure deletion steps, and gentle journaling prompts so the process feels empowering, not scary.\n\nWhy exporting your period data matters—and privacy risks to know\nYour menstrual data often includes intimate details: period dates and flow, symptoms, sexual activity, contraception, ovulation test results, and private journal notes. That makes it sensitive data; researchers and consumer advocates have flagged femtech apps for sharing or retaining this kind of information in ways users may not expect.\nRecent academic and public reports (Cambridge, UCL, King’s College) have highlighted that many apps share data with advertisers or third parties, and that deletion flows can be unclear. In the EU/UK, health and sex‑life data are treated as sensitive under GDPR, which gives you rights to portability and deletion—but these rights vary by region.\nWhat can go wrong: exported files with names, emails, or hidden metadata (EXIF in photos, device IDs) can be used for profiling, targeted advertising, or even re‑identification. The good news: using portability rights and a few practical steps reduces risk without making the process stressful.\n\nBefore you start: a short privacy checklist to prepare\n\n Decide what to keep. Minimize exported fields: dates, flow, basic symptoms—skip names, emails, or full profile data when possible.\n Choose temporary storage. Prefer your personal device (local Files, desktop) over third‑party cloud for the initial export.\n Check app settings. Look for built-in Export or Request Data options before using third‑party tools.\n Know formats and encryption basics. Exports are often ZIP/XML from Apple Health; converters produce CSV/JSON. Have an AES‑256 capable tool ready (7‑Zip, macOS disk image) if you’ll encrypt.\n\n\nStep 1 — Simple: Quick iPhone export (best for most users)\nThis path is ideal if your cycle app syncs with Apple Health or you only need a quick, local export.\n\n Open Health → tap your profile (top right) → Export All Health Data. This creates a .zip containing export.xml. (Apple Support documents this process.)\n Choose Save to Files locally or AirDrop it to your own Mac/iPhone. Avoid emailing the file.\n Unzip locally and inspect export.xml. Look for obvious PII: name, email, userId, or profile notes. If you see attachments (photos, audio), note them for metadata checks.\n If you prefer CSV/JSON for review, use a trusted converter locally (applehealth2csv or HealthExport run on your device). Prefer local tools that don’t upload your file to a remote server.\n\nWhen to use this path: you want a quick, mostly local export with minimal risk and no third‑party servers involved.\n\n\n\n \n Photo by Tima Miroshnichenko on Pexels\n\n\n\n\nStep 2 — Intermediate: Automated or scheduled exports\nAutomations are useful if you want regular backups or trend exports, but they need careful configuration.\n\n Tools to consider: Health Auto Export, HealthExport, exporthealth.app. They can schedule exports and route them to a destination.\n Configure carefully: select only the menstrual and symptom fields you need, set a secure destination, and avoid sending raw CSV to unencrypted cloud folders.\n Retention policy: set automatic pruning—e.g., keep only the last 6–12 months—and schedule an audit frequency (quarterly recommended).\n Risk reduction: prefer local automations (shortcuts that save to your device) or E2EE services. If the tool requires remote servers, read its privacy policy and prefer open‑source or reputable vendors.\n\n\nStep 3 — Advanced: Local conversion and selective exports (for power users)\nFor full control at the field level, use local CLI tools and small scripts to convert and sanitize exports.\n\n Use applehealth2csv or similar local tools to convert Apple Health XML into CSV/JSON while selecting only the types you need (menstrualFlow, symptoms, notes).\n Script redaction: filter out columns like userId, email, deviceId, and remove account metadata automatically during conversion.\n Validate the output by sampling rows and checking headers. Import the sanitized CSV into another app only if it supports minimal imports and you’ve confirmed its privacy policy.\n When to use: you want complete control, automated sanitization, or are moving large datasets between services you trust.\n\n\nHow to audit exported files for PII and hidden metadata\nOpening and carefully scanning exports is the best defense. Use simple tools and a checklist-style approach.\n\n Open the file: view the first 20 and last 20 lines of CSV/JSON/XML. Search headers for columns like name, email, phone, userId, or accountId.\n Search for attachments: look for image or audio references in the XML or CSV. If present, list those files separately.\n Check metadata: for photos/audio, run an EXIF viewer (ExifMeta, ExifTool). Look for GPS coordinates, device timestamps, or camera software fields that could identify you.\n Hidden logs and analytics: list the ZIP contents before sharing—some exports include auxiliary logs or analytics files. Remove anything not needed.\n Practical redaction: in a spreadsheet, delete columns with PII, export as plain CSV or JSON (this usually strips document properties), and remove attachments before archiving.\n\nTools that help: ExifTool/ExifMeta for photo metadata, any text editor or spreadsheet for CSV/JSON inspection, and command-line zip list commands to check archive contents.\n\nStep 4 — Remove, minimize, and sanitize before you store\nFollow the minimalism principle: only keep fields that serve your goal (e.g., spotting cycle length changes).\n\n Drop profile and account fields. Keep essentials: date, flow, symptoms, mood tag.\n Journals: search text for names, addresses, partner info, or other identifying details. Either redact those phrases or export journals separately if you need them.\n Strip metadata from images and documents before including them. On phone, use a metadata‑stripper app; on desktop, use ExifTool or export as plain images without location.\n Save a minimized file and use a clear filename (see conventions below). Keep a copy only if it helps a specific goal like sharing with a provider.\n\n\nStep 5 — Securely archive and transfer: encryption, local transfers, and cloud choices\nEncrypt before storing. Prefer local transfers when moving files between your own devices.\n\n Encryption: create an AES‑256 encrypted ZIP/7z or a macOS encrypted disk image. Use a strong, memorable passphrase and store it in your password manager.\n Local transfers: AirDrop to your own devices, USB drive, or secure local network copy. Avoid email or insecure links for sensitive files.\n Cloud storage: if you use cloud, prefer end‑to‑end encrypted vaults (e.g., paid services with zero‑knowledge encryption) or encrypt locally before uploading.\n Importing to another app: verify the app’s import method and privacy policy. Import only minimal fields and prefer apps that explicitly support secure imports.\n\n\n\n \n \n Export only what matters: App’s privacy-first export tools\n App can export menstrual fields by default, offer a one-tap PII removal step, and create an encrypted archive so you keep only what you need. All data is hosted under GDPR in Germany and not used to train AI models.\n \n Try App Free\n \n \n \n \n\n\nStep 6 — Permanently delete what you don’t need (and verify deletion)\nDeleting data thoroughly requires action in several places.\n\n Delete from the source app: use its delete-account or delete-data flow. Request a confirmation email or screenshot when possible.\n Wipe local copies: securely delete files, empty the trash, and remove versions. On macOS and Windows, empty the Trash/Recycle Bin and remove backups (Time Machine snapshots or cloud versions).\n Remove cloud copies: delete uploads and clear the cloud provider’s Bin/Trash and any historical versions.\n Keep a minimal audit note (no PII): e.g., “export cycles_min deleted on 2025-02-09 from iPhone and iCloud.” Store that note separately from sensitive files.\n Legal note: deletion timing and guarantees vary by app and region. Save any deletion confirmation from the app or request written confirmation if needed.\n\n\n\n\n \n Photo by Scott Webb on Pexels\n\n\n\n\nFilename conventions and versioning for privacy-first archives\nGood filenames make audits and deletions simple while protecting privacy.\n\n Do: use neutral names and date stamps. Example: wellbeing-export-2025-02-09_min.csv.\n Don’t: include names, emails, or account IDs in filenames. Avoid things like emma_smith_cycles_2025.csv.\n Use suffixes for clarity: _min for minimized exports, _full for complete exports, and include the ISO date for versioning.\n Quick rules: neutral title + ISO date + suffix. Example: cycles-2025-02-09_min.csv. This helps you find and delete specific files later without revealing identity in the filename.\n\n\nDownloadable export-audit checklist (compact & printable)\nUse this short checklist as you work through an export. Save or print it separately from your exports.\n\n Export source & date noted (app or Apple Health) — yes/no\n File format checked (XML/CSV/JSON) and previewed — yes/no\n PII columns removed (names, emails, phone, account IDs) — yes/no\n Attachments checked; EXIF stripped if present — yes/no\n Journal entries scanned and sensitive text redacted — yes/no\n File archived encrypted (method noted) — yes/no\n Original copies securely deleted (device + cloud) — yes/no\n Import target privacy reviewed (if sharing/importing) — yes/no\n\n\nGentle journaling prompts to make exporting feel empowering\nTake a moment before or after exporting. These short prompts help you center your intention and reduce anxiety.\n\n What do I want to learn from my cycle data? (patterns, mood, energy)\n Which three data fields feel important to keep for my wellness goals?\n What privacy boundaries do I want to set around this data?\n How will I use this archive—personal reference, provider visit, or research?\n One kind thing I’ll do for myself after this: (tea, walk, call a friend)\n\n\nQuick tools & resources (where to export, convert, audit, and encrypt)\n\n Apple Health — built-in export (XML/ZIP).\n HealthExport / Health Auto Export — selective export and automation (use cautiously, prefer E2EE or local-only options).\n applehealth2csv (GitHub) — local open-source converter for power users.\n ExifMeta / ExifTool — view and remove EXIF from photos and attachments.\n 7‑Zip, macOS encrypted disk images — create AES‑256 encrypted archives.\n Authoritative reads: Cambridge Minderoo report and UCL/KCL research on femtech privacy; Apple Support on Health export; ICO guidance on portability and deletion.\n\n\nLegal & safety caveats — what this guide doesn’t promise\nPlatform and regional differences matter: iOS and Android have different export flows, and GDPR rights apply in the EU/UK but differ elsewhere. This guide explains risk reduction steps—not absolute guarantees. Always check the app’s privacy policy, request deletion or portability under local laws, and save any confirmations you receive.\n\nWrap-up: a calm checklist to finish\nQuick recap of the 6 steps:\n\n Prepare: decide what to keep and where to store temporarily.\n Simple export: iPhone → Health export → local preview.\n Intermediate: set up scheduled exports with minimal fields and retention.\n Advanced: convert locally and script field-level redaction.\n Archive & transfer: encrypt, prefer AirDrop/USB, or E2EE cloud.\n Delete: wipe originals, clear cloud Trash, and keep a minimal audit note.\n\nTaking control of your cycle data is an act of agency. Move at your own pace, use the journaling prompts to stay centered, and keep privacy-first habits so your logs help you—without exposing you. If you’d like, download the printable checklist or try App’s built-in export and PII-removal tools to make an export feel calm and safe.\n\nConclusion\nExporting your period-tracker data securely is doable and empowering with simple habits: minimize what you save, audit exports for PII and metadata, encrypt archives, prefer local transfers or E2EE, and delete what isn’t needed. Use the checklist and journaling prompts to keep the process gentle—you're in control of your data and how it's used.","metaTitle","Export Period Tracker Data: 6-Step Privacy Guide","metaDescription","Learn how to securely export, audit, archive, transfer, and delete your menstrual-tracker data in 6 privacy-first steps—plus filename tips, a checklist, and calming promp","ogImageUrl","https://images.pexels.com/photos/6963098/pexels-photo-6963098.jpeg?auto=compress&cs=tinysrgb&fit=crop&h=627&w=1200","authorId",1,"categoryId",28,"status","published","publishedAt",["D",1770615018293],"updatedAt",["D",1770615018293],"createdAt",["D",1770615018293],"readingTimeMinutes",10,"isFeatured",false,"viewCount",0,"author",{"_8":27,"_10":46,"_47":48,"_49":50,"_51":-5,"_52":-5,"_53":-5,"_54":-5,"_55":-5,"_56":-5,"_36":57,"_34":58},"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":29,"_10":61,"_47":62,"_63":-5,"_20":64,"_22":65,"_66":-5,"_36":67},"privacy-cycle-care","Privacy & Cycle Care","description","Privacy & Cycle Care | Blog","Articles about privacy & cycle care","parentId",["D",1770615018291],"tag",{"_8":70,"_10":71,"_47":72,"_36":73},103,"gdpr-safe-apps","GDPR-safe apps",["D",1770615018306],"currentPage","totalPages","siteName","siteUrl","https:/getlunaraapp.com","canonicalUrl","https://getlunaraapp.com/tag/gdpr-safe-apps","prevUrl","nextUrl","actionData","errors"]