LEGAL

PRIVACY POLICY

Effective date: November 2, 2026

PlumeClue is operated by Lucholli Game Studios ("PlumeClue," "we," "us," or "our"). This Privacy Policy explains the information handled when you use the PlumeClue iOS app and related services.

Information We Collect

Account and profile information

We collect your email address, birder alias, internal user identifier, sign-in provider information, profile settings, and limited account-status information. If you use Sign in with Apple, Apple provides us with an account identifier and, depending on your choices, your name or email address. We do not receive your Apple ID password.

Content and gameplay information

We collect content you create or submit, including bird photos, sighting titles, clues, species answers (common, scientific, and family names), guesses, scores, rankings, stakeout memberships, comments and discussion, follows, blocks, reports, beta feedback and optional screenshots, private Life List observations, counts, dates, notes, optional locations, imported history, Flashcard progress, and related gameplay activity. Private stakeout activity is available to the people participating in that stakeout as the game requires. Public cases and their related results may be visible to other PlumeClue users.

Photos and camera

PlumeClue accesses only the photos you select or images you capture for a sighting. We do not scan your entire photo library. Uploaded images are processed to create a game-ready display copy and to remove unnecessary embedded metadata, including EXIF and GPS metadata, before that copy is shown in gameplay.

Safety information

We collect content reports, moderation decisions, block relationships, and limited security and audit records used to protect users and enforce our rules.

Notifications, widgets, and Live Activities

If you enable notifications or Live Activities, we use Apple's delivery tokens and your preferences to provide Case alerts and countdowns. Home Screen widgets use a limited on-device cache of active Daily Cases and display photos. This cache does not contain your sign-in credentials, private observations, or exact coordinates.

Optional crash reports and usage data

In app versions offering these controls, Share Crash Reports and Share Usage Data are separate optional choices under Profile > Safety & Privacy. Both start off on this device. You can change either choice at any time without losing app features.

If you enable crash reports, Google Firebase Crashlytics receives crash stacks and limited technical diagnostics, such as app version, device and operating-system details, installation identifiers used by the service, and fixed error categories. We do not attach your PlumeClue account identifier, email, alias, photos, answers, notes, or exact locations to those reports. Google Analytics and advertising measurement are not enabled for this integration.

If you enable usage data, TelemetryDeck receives a limited set of feature-use events, such as opening the app or Daily screen, completing onboarding, publishing a Case, submitting a guess, starting or answering Flashcards, and purchase or Restore outcomes. Events contain the app version/build, a random session identifier and a hashed random installation identifier. This identifier is separate from your PlumeClue login. No photo, species answer, notes, email, alias, private location or Case identifier is sent as an event field. We send these events on a best-effort basis without storing an offline event history.

Turning sharing off stops new submissions and cancels pending usage requests. Turning off crash sharing also asks Crashlytics to delete unsent reports. Reports already delivered cannot be recalled through the switch. Network providers receive ordinary connection information, such as an IP address, when a request reaches them.

Optional location and Apple Maps

PlumeClue does not track your background location. When you choose Use My Current Location, we request location access to place a private sighting pin. If you choose Use My Current Area in Explore, we use an approximate search centre to find reported birds, without background tracking. You can instead search for a place, tap a map, enter coordinates or leave location blank. Apple Maps processes map displays, place searches and geographic lookups. These requests can include the search terms, selected place or coordinates needed for that feature.

Birds Reported Around Here sends an approximate search centre, distance, selected month and year window to GBIF. Place searches use Apple Maps. The comparison with your Life List happens on your device; we do not send your Life List or PlumeClue account identity to GBIF. Public search results are cached on your device for up to 24 hours. They show historical observation reports, not a prediction of which birds you will see.

We store the sighting location you choose with your private Life List record. Exact pins are not shown on public Cases or profiles. State and county summaries can use saved regions or regions found from a pin. You control whether supported exports include exact coordinates; enabling Include Exact Coordinates puts those locations into the file you choose to share. Exported place names can also reveal where a sighting occurred.

Life List imports and exports

You can import an eBird CSV that you select into your private PlumeClue account. An import can contain species, dates, counts, place names, notes and coordinates. An eBird-format export or Observation Archive creates a file for you to review and share; PlumeClue does not automatically submit it to eBird. Sending a file to another service is your choice and that service's policy then applies.

Subscriptions

Apple processes subscription payments. We receive the signed transaction information needed to validate Plus, expiration, revocation and Family Sharing, including product and transaction identifiers, purchase status and an app account token. We link eligible access to your PlumeClue account. We do not receive your card number or Apple Account password. Signing into a different PlumeClue login does not automatically move a subscription or merge private records.

Safety checks for shared content

In app versions with shared-content safety checks, we ask for your permission before sending the text or photo being shared to OpenAI. These checks cover Case photos and manually entered bird names, avatars, display names, Stakeout names, Case Talk messages and submitted guesses. We send the submission needed for the check, not your sign-in credentials, account identifier, private observation history or exact sighting coordinates. A photo or text can itself contain identifying information, so please avoid including it in shared content.

Private Life List photos and notes are excluded from these checks. You can withdraw safety-check permission under Profile > Safety & Privacy; sharing through safety-enabled features requires screening. Withdrawing permission does not delete content already shared or recall a completed check.

Automated flags may hold a submission for moderator review. A flag does not automatically ban your account or prove wrongdoing. Authorized moderators may inspect held shared content and record a decision. You can edit a held submission or contact support with its review reference. An avatar that fails screening is not published; choose another image or contact support if you believe the result is mistaken. Routine safety-review records and decisions are removed after 30 days by a daily cleanup; original account content and separate reports follow the retention rules below.

We use OpenAI's moderation API for content safety, not AI species-answer scoring. Species-answer matching uses PlumeClue's catalog and accepted aliases. OpenAI's published data controls state that API submissions are not used for model training by default and list no application-state or abuse-monitoring retention for the moderation endpoint; see OpenAI's current data controls and exceptions.

How We Use Information

How Information Is Shared

We share information only as needed to provide and protect PlumeClue, when you direct us to share it through the game, or when required by law. Our service providers include:

These providers may process information for us under their own service terms and privacy commitments. We do not sell personal information and do not use personal information for cross-context behavioral advertising.

Retention and Account Deletion

We retain information while your account is active and as reasonably needed for gameplay integrity, safety, fraud prevention, legal compliance, dispute resolution, product improvement, and backups. Feedback may be retained after account deletion without its account link or birder alias. Some completed-game or audit records may be anonymized or retained where necessary to preserve other players' history or meet legal and security obligations. Backup copies may expire on their normal schedule.

Delete your account in the app: account deletion is available inside the PlumeClue app under Profile > Safety & Privacy > Delete Account. If you cannot access the app, contact [email protected].

Your Choices and Rights

You can update your alias, manage notification preferences, revoke notification or camera or location access in iOS Settings, choose crash/usage sharing, control exact coordinates in supported exports, report content, block other users, and delete your account. Depending on where you live, you may also have rights to request access, correction, deletion, or a copy of certain personal information. Contact [email protected] to make a request. We may need to verify your identity before completing it.

Children's Privacy

PlumeClue is intended for people age 13 and older and is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided information, contact us so we can act.

Security

We use technical and organizational safeguards designed to protect information, including encrypted connections, access controls, private media storage, and database authorization rules. No system is perfectly secure. Report a suspected security issue to [email protected].

Changes to This Policy

We may update this policy as PlumeClue evolves. We will update the effective date above and provide additional notice when required by law.

Contact

Lucholli Game Studios
Privacy: [email protected]
Support: [email protected]