What we collect, what we do with it

Privacy Policy

Effective August 14, 2026 · Last updated August 14, 2026

Your hunt is private, not public social media. Hunt membership controls access to game data, and accepted evidence is designed to open to the group after the hunt ends rather than to the general internet.

Photos are game evidence. EyesPie stores submitted images, controlled evidence metadata, and related scoring/review records so the game can work.

Peer votes affect scores. EyesPie records the voter, selected photo owner, and the two 3-point awards so standings can update correctly.

We reduce common camera metadata. The client may read capture time for story metadata, then redraw/compress the image or strip common JPEG APP1 EXIF/XMP metadata so GPS and camera metadata are not intentionally retained in the stored file.

Stripe handles sensitive payment and payout credentials. EyesPie stores payment/payout status and provider identifiers, while full card and bank details are generally entered into Stripe-hosted flows.

1. Scope

This Privacy Policy explains how EyesPie handles personal information when you visit the website, create or use an account, join or host a hunt, submit photo evidence, participate in a peer-photo matchup, make or verify a wager-mode payment, set up a winner payout, view a shared album, or use related features.

This Policy does not govern information processed independently by third parties under their own policies, such as your bank, mobile carrier, Google account provider, Stripe, a venue, or another website you choose to visit.

2. Notice at collection

At or before collection, EyesPie may collect the categories below for the listed business/service purposes. The exact information depends on which features you use.

Category	Examples	Main purposes
Identifiers & account data	Name, email, phone number, profile image, Firebase UID, authentication provider	Sign-in, membership, security, account support
Game & activity data	Hunt membership, role, challenges, score, submissions, votes, vote point awards, standings, timestamps	Run the hunt, score play, prevent abuse, produce results
Photo evidence	Images, challenge association, controlled capture/upload metadata	Proof, host review, album, trip story, limited peer voting
Payment records	Checkout/session IDs, payment status, amount, refund/dispute state	Paid-entry eligibility, accounting, refunds, fraud prevention
Payout records	Stripe Connect account ID, onboarding/readiness state, transfer/payout status	Winner onboarding and prize delivery
Device & network data	IP address, browser/device details, logs, timestamps, errors, security events	Deliver, secure, troubleshoot, and improve the Service

EyesPie does not currently sell personal information for money or intentionally use hunt photos for third-party advertising. If those practices materially change, this Policy and any legally required notices or opt-out controls will be updated before the new use begins.

3. Information you provide or generate

Account information: display name, email, phone number when phone authentication is used, profile image, authentication identifiers, and account state.
Hunt information: hunt name, invite membership, host/player role, mode, Challenge configuration, start/end state, scores, completion counts, moderation decisions, and final results.
Evidence information: photos, Challenge associations, upload state, acceptance/rejection state, timestamps, and controlled object metadata.
Peer-vote information: which eligible matchup was shown, the choice submitted, skips, anti-repeat state, selected photo owner, the 3 points awarded to the voter, the 3 points awarded to the selected photo owner, and server records used to prevent self-voting or duplicate manipulation.
Payment and payout information: provider identifiers, transaction state, amount, refund/dispute information, payout readiness, transfer state, and related timestamps.
Communications: information you send when requesting support, contest review, payment help, privacy assistance, or image removal.

4. Sources of information

We receive information directly from you; from other members of the same hunt when they create or administer a hunt; automatically from your browser, device, and network; and from service providers such as Google Firebase / Google Cloud and Stripe when they return authentication, payment, payout, security, or operational information.

5. Photo evidence and photo metadata

Photo evidence is a core part of EyesPie. Before upload, the app may inspect a JPEG capture timestamp and preserve a controlled capture-time value for story metadata. The final Trip Story is remixed rather than chronological: accepted photos are shuffled, while top-voted photos can occupy prime-number positions. The client normally redraws/compresses the image into a new JPEG or strips common JPEG APP1 metadata. APP1 commonly contains EXIF/XMP fields, including GPS coordinates and camera details.

EyesPie is designed not to intentionally preserve GPS coordinates or full camera EXIF in the stored evidence file. Instead, the upload may include controlled metadata such as hunt ID, player ID/name, Challenge ID/name/category/points, capture timestamp, the source of that timestamp, and upload timestamp.

No metadata-removal technique is guaranteed to eliminate every possible proprietary or hidden field from every format. The app may reject formats it cannot process safely and may ask the user to upload a screenshot or smaller image instead.

EyesPie does not currently use facial recognition or biometric identity matching to identify people in submitted photos. Photos can nevertheless contain faces or other sensitive visual information, so participants should use judgment and respect other people’s privacy.

6. Authentication information

EyesPie uses Firebase Authentication and may support Google sign-in, email/password, and phone-number verification. Google or a telecommunications provider may separately process information when you use their authentication or messaging services. Phone sign-in can involve an anti-abuse reCAPTCHA or similar verification mechanism.

EyesPie stores or receives the account identifier and profile information needed to associate your activity with the correct player. Password handling and third-party identity-provider credentials are managed through Firebase or the relevant provider rather than stored in plain text by the EyesPie frontend.

7. Wager-mode payment information

Stripe may process eligible wager-mode entry payments. EyesPie may receive and store Checkout Session IDs, PaymentIntent IDs, customer or payment identifiers, amount, currency, payment state, refund/dispute/reversal state, reconciliation information, and timestamps.

Full card numbers and card security codes are generally entered into Stripe-hosted or Stripe-controlled payment interfaces and are not intentionally stored in the EyesPie application database.

8. Winner payout information and Stripe Connect

If a participant becomes eligible for a cash prize, EyesPie may use Stripe Connect for identity and payout onboarding. Stripe may ask the winner for legal name, date of birth, address, taxpayer information, government identification, bank/debit-card information, or other information required by Stripe, its financial partners, or applicable law.

EyesPie generally stores the Stripe connected-account identifier and high-level state needed to determine whether onboarding is complete and whether a transfer or payout is ready, pending, failed, restricted, or completed. EyesPie does not intentionally store the full bank-account or debit-card credentials entered into Stripe-hosted onboarding.

9. Automatically collected technical information and local storage

EyesPie and its infrastructure providers may process IP address, browser type, device/OS information, request timestamps, authentication/security events, network errors, function logs, crash/error data, performance information, and similar technical records needed to deliver and secure the Service.

The web app uses browser storage for functional state, which can include the preferred light/dark theme, the last-opened hunt identifier, and other short-lived interface state. Clearing browser/site data can remove these local preferences but does not automatically delete server-side account or hunt records.

10. How EyesPie uses information

Authenticate users and maintain private hunt membership.
Upload, store, process, review, and display photo Evidence.
Calculate server-authoritative scores, standings, completion counts, and final results.
Provide limited anonymized peer-photo matchups and award 3 points to the voter plus 3 points to the selected photo owner.
Process, verify, reconcile, refund, or investigate wager-mode payments.
Calculate prize previews and final prizes, determine payout readiness, and route eligible payouts.
Generate the shared end-of-hunt album and remixed Trip Story.
Detect duplicate submissions, abuse, unauthorized access, fraud, manipulation, payment disputes, and security incidents.
Troubleshoot, maintain, secure, test, and improve the Service.
Comply with legal obligations, enforce the Terms, and protect users, other people, the Service, and payment partners.

Personal information may be disclosed in the following circumstances:

Other members of your hunt: names, scores, standings, activity, and accepted photos according to the game’s visibility rules.
The Host: submitted Evidence and related game information needed to review and administer the hunt.
Service providers: Google Firebase / Google Cloud, Stripe, and other vendors that process information to host, secure, authenticate, communicate, collect payments, or deliver payouts.
Legal and safety disclosures: when reasonably necessary to comply with law, respond to valid legal process, investigate fraud or abuse, protect rights or safety, or enforce the Terms.
Business transactions: if the Service or its operator is involved in a merger, acquisition, financing, reorganization, bankruptcy, or sale of assets, information may be transferred subject to applicable law and appropriate protections.

EyesPie does not give advertisers a public feed of private hunt photos.

12. Who can see photos and hunt data

During a live hunt, Evidence is intended to remain restricted so ordinary players cannot simply browse the entire proof library and copy another player’s find. The submitting player can access their own Evidence, and the Host can review it.

Peer voting is a narrow live-hunt exception: the system may provide a hunt member temporary access to exactly the eligible images needed for a matchup between other players. The matchup is designed not to display the uploader’s name. A player should not be offered their own image as a choice. A completed vote awards 3 points to the voter and 3 points to the owner of the selected image, so the resulting score can affect standings.

After a hunt ends, accepted Evidence may become visible to the hunt’s members through the shared album and trip-story features. A private hunt is still a group-sharing environment; do not upload an image you are unwilling for the other participants to see after the game.

13. Data retention

EyesPie retains information for as long as reasonably necessary for the purposes described in this Policy, including operating active hunts, preserving the shared album/story, resolving Evidence disputes, reconciling payments, sending prizes, handling chargebacks, preventing fraud, securing accounts, maintaining backups, and meeting legal/accounting obligations.

Different records can require different retention periods. Payment, dispute, fraud, payout, tax, or legal records may need to be retained longer than ordinary interface state. Backup copies may persist for a limited period after primary records are deleted.

As the Service grows, EyesPie should publish more specific default retention schedules and self-service deletion controls where technically and legally appropriate.

14. Security

EyesPie uses measures intended to reduce risk, including authenticated access, Firebase Security Rules, restricted Storage paths, server-authoritative score and payment logic, immutable evidence objects, limited peer-vote access, secret management, provider-hosted payment/payout flows, and deployment/QA checks.

No system can guarantee perfect security. Users should use unique credentials, protect verification codes, keep devices secured, and promptly report suspected unauthorized access.

15. Your privacy choices and rights

Depending on where you live, you may have rights to request access to personal information, correction, deletion, portability, restriction, objection, or information about disclosures. Some rights are subject to exceptions, identity verification, fraud-prevention needs, payment/legal retention obligations, and the rights of other people.

You can also make practical choices by declining to join a particular hunt, skipping a Challenge, not uploading a photo, choosing friendly mode rather than wager mode, declining optional payout onboarding until a prize requires it, signing out, or clearing local browser data.

To make a privacy request, use privacy@eyespie.app. EyesPie may need to verify that the requester controls the account or is otherwise authorized to make the request.

16. California and other U.S. state privacy rights

Some U.S. state privacy laws provide qualifying residents rights such as knowing/accessing personal information, deletion, correction, portability, opting out of certain sales or sharing, limiting certain sensitive-data uses, and non-discrimination for exercising privacy rights. Whether a particular law applies to EyesPie depends on statutory thresholds, exemptions, and the operator’s activities.

EyesPie does not currently sell personal information for money and does not intentionally use private hunt data for cross-context behavioral advertising. If EyesPie begins a practice that legally constitutes a “sale,” “sharing,” or targeted advertising requiring an opt-out, the Service should provide the legally required notice and mechanism before or when that practice begins.

Authorized agents may submit requests where applicable law permits. EyesPie may require proof of authorization and may separately verify the consumer’s identity. Users will not be unlawfully discriminated against for exercising applicable privacy rights.

17. Children

EyesPie is not directed to children under 13, and wager mode is intended for legally eligible adults. We do not knowingly design the Service to collect personal information from children for participation in wager mode. If you believe a child has submitted personal information inappropriately, contact privacy@eyespie.app.

18. Non-consensual intimate images, unlawful images, and removal requests

Do not upload intimate or sexually explicit imagery of another person without that person’s consent, exploitative imagery, or illegal content. If you are depicted in content on EyesPie and believe it was shared without consent, violates your rights, or must be removed under applicable law, send a removal request to privacy@eyespie.app with enough information to locate the content and verify the request.

EyesPie may remove or restrict access to reported content while reviewing a request and may preserve limited records when reasonably necessary for safety, fraud prevention, legal compliance, or evidence of abuse. The operator should maintain a documented intake and response process for legally mandated image-removal requests.

19. International users and data transfers

EyesPie may rely on service providers that process information in the United States and other countries. If the Service is offered to users in jurisdictions with international-transfer requirements, the operator and its providers may need to use appropriate contractual or legal transfer mechanisms. Using the Service from another country does not by itself waive rights granted by applicable law.

20. Changes to this Policy

We may update this Policy as EyesPie changes. Material changes may be highlighted in the Service or presented before a feature that materially changes data use. The effective and last-updated dates identify the version currently published.

21. Privacy contact

Privacy questions and requests can be sent to privacy@eyespie.app.

Launch requirement: configure and actively monitor privacy@eyespie.app, and add the Service operator’s legal entity name and mailing address to this Policy before broad commercial rollout. The operator identity/address are intentionally not fabricated here.

This Policy is written to describe the current product implementation. Privacy obligations vary by jurisdiction and business size/activity; the operator should obtain jurisdiction-specific review as the public user base expands.