Privacy Policy

Effective date: May 3, 2026 · Last updated: May 31, 2026

This Privacy Policy describes how JordansCo ("we", "us", "our") collects, uses, and shares information when you use the PokeReplicas mobile application (the "App"). Questions: [email protected].

1. Information we collect

1.1 Information you provide

• Account information. When you sign in with Google or Apple, we receive your name and email from the identity provider. We never see your password. You may use Apple's Hide My Email relay to mask your address.
• Profile information. Your display name, country (two-letter code), and any optional profile details you set.
• Submitted content. Team titles, descriptions, Pokémon selections, metagame tags, regulation set and season labels, and screenshots you upload. Also includes comments and replies you post on team detail pages.
• Reports and block list. Reports you file against a team or comment, the list of other users you have blocked, and any message you send us through support.
• Community Guidelines acceptance. A timestamped record that you have accepted the Community Guidelines, captured the first time you post a comment.

1.2 Information collected automatically

• Device and diagnostic data. Crash reports and performance traces via Google Firebase Crashlytics, including device model, OS version, App version, and anonymized identifiers.
• Usage counters. Non-personal counters used to enforce rate limits (teams shared per day, comments per minute and per day).
• Advertising identifiers. Google AdMob may access device-level advertising identifiers (IDFA on iOS if you grant App Tracking Transparency permission, Android Advertising ID on Android). You can reset or limit these in your device settings.
• Push notification token. If you enable notifications, Firebase Cloud Messaging assigns an anonymous token we use to deliver alerts about replies to your comments and other activity on your content.

1.3 Purchases and subscriptions

• Purchase history. When you buy PokeReplicas Pro, we receive purchase and transaction information — the product purchased, purchase and renewal dates, and subscription status. We do not receive or store your payment card or bank details; those are handled solely by the Apple App Store or Google Play.
• App user ID. A pseudonymous identifier used to link your subscription entitlement to your install and restore it across your devices. We retain purchase records for as long as needed to provide the service and to meet legal and accounting obligations, after which they are deleted or anonymized.

1.4 Information we do NOT collect

We do not collect precise geolocation, contacts, calendar, microphone, or camera roll data outside of the screenshots you explicitly upload. We do not sell your personal information.

2. How we use information

We use information to authenticate users, store and display teams and comments, deliver reply notifications, respect your block list, enforce Community Guidelines and rate limits (including automated hiding of comments that receive three or more reports or that contain slurs targeting protected groups), diagnose crashes, display advertising, manage optional subscriptions and the ad-free entitlement, comply with legal obligations, and respond to lawful requests.

3. How we share information

• Publicly, by your choice. Teams and comments you submit are public by default and may include your display name and country flag.
• Service providers. We use Google Firebase (Authentication, Firestore, Cloud Storage, Cloud Messaging, Cloud Functions, Crashlytics), Google AdMob, and RevenueCat to process data on our behalf. RevenueCat handles subscription and entitlement processing; it receives your purchase history and a pseudonymous app user ID and acts as our processor (its privacy policy is at revenuecat.com/privacy). Apple and Google process the underlying transaction as the sellers of record.
• Legal reasons. We may disclose information if required by law or to protect rights, safety, and service integrity.
• Business transfers. If JordansCo is acquired or merged, your information may transfer as part of that transaction.

4. Authentication providers

Sign-in is handled by Google and Apple. We receive only the fields the provider agrees to share — typically name, email, and a stable provider user ID. We never see your Google or Apple password.

5. Advertising

The App displays ads served by Google AdMob. In some regions we request consent via Google's User Messaging Platform. On iOS 14.5 and later, Apple's App Tracking Transparency prompt governs whether AdMob may use device-level identifiers for personalized ads. You can reset your advertising identifier or opt out of personalized ads in your device settings.

6. Comments and moderation

Comments and replies you post are public and tied to your display name. Reports filed against a comment include the comment ID, your account ID as reporter, and a category label; reports are visible only to us, not to the reported user. Block lists are private to your account and are used to hide blocked users' content from your view and to suppress reply notifications from them. Comments that receive three or more reports are automatically hidden pending review. A soft profanity filter automatically hides comments containing slurs targeting protected groups; casual profanity is not filtered. Repeat or serious violations may result in account suspension.

7. Children

The App is not directed to children under 13, or the equivalent minimum age in your jurisdiction, and we do not knowingly collect personal information from them. If you believe a child has provided personal information, contact us and we will delete it.

8. Your rights

Depending on where you live, you may have the right to access, correct, delete, object to, or restrict certain processing of your personal information. You can delete your account in-app under Settings → Delete account, or by emailing [email protected]. Account deletion removes your profile record and releases your display name; public teams and comments you posted may remain but will be attributed to a deleted user.

9. Data retention

Account records are retained while your account is active. Upon deletion, we remove personally identifying fields from your profile record. Comments you posted may remain attributed to a deleted user; you can delete individual comments yourself before deleting your account. Crash and diagnostic logs are retained under Google's default Crashlytics retention. Rate-limit counters reset on a rolling daily basis.

10. Security

We use industry-standard measures to protect information in transit (TLS) and at rest (Firebase-managed encryption). No method of transmission or storage is 100% secure, and we cannot guarantee absolute security.

11. International transfers

Firebase, AdMob, and RevenueCat may process data in the United States and other countries. By using the App you consent to transfer of your information to jurisdictions that may have different data-protection laws than your own.

12. Changes to this policy

We may update this policy from time to time. Material changes will be announced in-app or by updating the effective date above. Continued use of the App after a change constitutes acceptance.

13. Contact

JordansCo
Email: [email protected]