ArcheryNow Privacy Policy

Last updated: May 1, 2026

Language: This is an English translation for convenience. If there is any conflict with the Japanese Privacy Policy, the Japanese text prevails regarding governing law (Japan) and related interpretations.

ArcheryNow (the “App”) respects your privacy. This policy explains what we handle and how. The text is published on GitHub Pages. See also the Terms of Service.

This document is a draft aligned with the implementation and is not legal advice.

1. Scope

This policy applies to data handling for the iOS App. Paid purchases: see Terms of Service.

2. Information we process

2.1 Primarily on your device

Stored on your device and, with Pro and iCloud, in your Apple iCloud container. We do not aggregate these on our own servers:

Uninstalling or deleting data may remove local copies. iCloud follows Apple.

2.2 Third-party services

(1) RevenueCat / Apple (billing) — purchase status, restore; data may include purchase info, pseudonymous app user ID, device/OS info. See RevenueCat Privacy. Payments are processed by Apple.

(2) iCloud (Pro) — database/backup JSON sync per Apple’s terms.

(3) GitHub Issues — feedback and requests; content and public profile data processed by GitHub, Inc. (GitHub Privacy Statement).

(4) On-device AI (where available) — coach summaries/responses on-device; we do not send conversation content to our servers. Apple’s policies apply to platform AI logging.

(5) Google AdMob / Google User Messaging Platform (ads and consent) — used to show ads, manage consent, protect ad delivery, and measure ad performance. Google may process data such as the advertising identifier (IDFA, if allowed through ATT), device information, IP address, ad impressions/clicks, app usage signals, and consent status. See Google Privacy Policy and Google advertising technologies.

In the EEA, UK, Switzerland, and other regions where consent is required, the App uses Google User Messaging Platform to show privacy messages and controls ad requests according to the user’s choices. If ATT permission is denied, the App does not use IDFA for tracking. Where shown, the in-app privacy options entry lets you revisit ad consent choices.

2.3 Tracking

Because the App uses Google AdMob, advertising identifiers and usage data may be used for ad delivery and measurement depending on your consent and iOS ATT permission. If personalized ads are not permitted, non-personalized ads and aggregated measurement such as SKAdNetwork may still be used.

3. Purposes

Provide the App (logging, stats, export, Pro), verify purchases and prevent abuse, show ads according to consent choices, support users, improve quality, and comply with law. No unrelated use.

4. Retention

Device/iCloud data until you delete or uninstall. RevenueCat/Apple/GitHub/Google: their policies. Issues: GitHub retention rules.

5. Sharing, disclosure, international transfers

We do not sell personal information. Google AdMob personalized ads may be considered sharing for cross-context behavioral advertising under some laws. We may disclose when required by law, to protect life/body/property, or as described for Apple/RevenueCat/GitHub/Google processing.

Foreign recipients (reference under Japanese law): Vendors may have servers outside Japan (e.g. U.S.). Their policies describe safeguards (contracts, certification schemes, etc.). If you do not want such processing, you may be unable to use billing, rewarded-ad unlocks, or GitHub-based contact.

6. Children

The App is not directed at children under 13, and we do not knowingly collect their personal information. Parents may use OS parental controls. Contact us via GitHub Issues for child-related privacy questions.

7. Rights (Japan)

Under Japanese law you may request access, correction, deletion, etc. No public email — use GitHub Issues or methods we specify. We may verify identity.

8. EEA and UK (GDPR)

If you use the App from the EEA or UK, you may have rights including access, rectification, erasure, restriction, portability, objection, withdraw consent, and complaint to a supervisory authority. Legal bases may include contract, legitimate interests (security/improvement), or consent for ads where required. International transfers may occur to Apple/RevenueCat/GitHub/Google as described. Requests via GitHub Issues where possible; we may ask for verification.

9. California (CCPA/CPRA)

California residents may have rights to know, delete, opt out of sale/sharing (we do not sell personal information), limit certain sensitive processing, and non-discrimination. AdMob personalized ads may be considered sharing where applicable; choices are provided through consent messages, OS settings, or in-app privacy options where available. Requests via GitHub Issues; authorized agents may need verification.

10. app-ads.txt

We publish app-ads.txt at the root of the developer website for AdMob authorized sellers. The App Store Connect developer website URL should match the domain where app-ads.txt is hosted.

11. GitHub Pages and cookies

Hosted on GitHub Pages. We do not intend to set first-party cookies; github.io / GitHub infrastructure may still process technical data or cookies.

12. Security

We take reasonable measures to protect personal information. No method of transmission is 100% secure.

13. Changes

We may update this policy; updates take effect when posted on GitHub Pages. We will try to notify you of material changes via the App or store notes.

14. Contact

GitHub Issues or App Store developer support.

Operator name/address: We do not publish a legal name or street address in this policy or the README by policy. Seek professional advice if you must publish such information under applicable law.

This policy is interpreted under the laws of Japan.