<?xml version="1.0" encoding="utf-8"?>
<resources>
    <!--
      The launcher label. The brand is "Privacy:Period Tracker" (BRAND_GUIDE.md
      §10); the launcher gets the short form, because a long label is truncated
      on most home screens anyway.

      Worth a decision rather than a default: §32's optional incognito launcher
      uses app_incognito_name instead, because a neutral icon under this label
      would still identify the app. The default label is the brand.
    -->
    <string name="app_name">Privacy: Period</string>
    <string name="app_full_name">Privacy: Period Tracker</string>
    <string name="app_tagline">Know your cycle. Protect your privacy.</string>
    <string name="app_incognito_name">Daybook</string>

    <string name="tab_today">Today</string>
    <string name="tab_calendar">Calendar</string>
    <string name="tab_insights">Insights</string>
    <string name="tab_settings">Settings</string>

    <!-- The back arrow on every screen that is not a tab. One string, one meaning. -->
    <string name="action_back">Back</string>

    <!--
      One copy, read by every surface that shows a fertility estimate.

      §18 scopes this line to "near fertility features and in About", and it was
      a literal in two screens before Settings needed a third. Two copies of a
      safety disclaimer is how two versions of a promise come to exist — the
      failure DOC_TRUST_MAP.md exists to prevent, in code rather than prose.

      Notifications deliberately do NOT carry it: a long sentence about
      fertility on a lock screen is the leak the discreet copy exists to avoid.
    -->
    <!--
      §4's promise, in one place because it is made in two.

      Onboarding shows it once, before the user has entered anything; Settings
      shows it beside Export and Delete, where it stops being a marketing line
      and becomes a statement they can hold the product to. A second literal is
      how two versions of a promise come to exist — the same failure the
      fertility disclaimer below is one copy for.

      **The wording is load-bearing and narrower than it could be.** It says we
      never SELL your data. It deliberately does NOT claim that no third party
      ever processes anything, because Play Billing and an ad SDK eventually
      will, and a promise the implementation cannot keep is worse than a
      narrower one that holds. Do not "strengthen" it. docs/security/SECURITY.md
      records the same wording and the same reason.
    -->
    <string name="privacy_promise_title">Your cycle belongs to you.</string>
    <string name="privacy_promise_body">We will never sell your personal or health data.\n\nYour period history and fertility information are private. We don\'t sell them to advertisers, data brokers, or third parties.</string>

    <string name="fertility_disclaimer">Fertility and ovulation dates are estimates based on cycle history and are not intended to be used as contraception or as a medical diagnosis.</string>
</resources>
