Pirate Pete Collector Privacy Policy

Last updated: October 13, 2026

 

This policy explains how Pirate Pete CCG handles information in the Pirate Pete Collector app and its connected account, Trading, tournament and lookup services. It describes the current iOS, Android, macOS and Windows apps; platform-specific practices are identified below. Shopping, payments and cookies on the separate Pirate Pete CCG website, and services you open in an external browser or another app, have their own privacy practices.

 

You can browse and manage a local collection without an account. Online features send the information needed for those features. Optional usage sharing is off by default and is separate from account services, notifications and crash diagnostics. We do not sell app user data or use it for third-party advertising tracking.

 

Request account deletion

To request deletion of your Pirate Pete Collector account and associated account data without reinstalling the app, email cole@piratepeteccg.com with the subject “Collector account deletion” and the email address used for your Collector account. We may verify account ownership before acting. Do not send your password or verification codes. The Deletion and retention section below explains what is removed and what may remain.

 

Information stored on your device

Collector stores local collection quantities and conditions, decks, graded-card records and custom photos, tournament records, valuation history and preferences in app storage. These records are not all automatically uploaded when you sign in. Pirates voyages and Bank records are kept locally and excluded from Collector account synchronization and Collector file backups.

 

Files you export or share go to the location or recipient you choose. Your device's own backup settings and any cloud storage or mail service you choose have separate controls. Removing an account does not erase local collections or copies of exported files.

 

Accounts and private collection sync

If you create or use an account, Google Firebase Authentication processes your email address and password for sign-in, email verification and password recovery. Our account service uses your verified email, Firebase user identifier and its own account identifier. The app also creates a device identifier and uses session and operation identifiers to protect access and coordinate changes. Authentication services process connection and security information, such as IP addresses and app/device metadata.

 

When you link collections for account sync, our service stores up to three collection names, card identifiers, Owned quantities by condition, and the revisions and operation information needed to synchronize and restore those records. This is a collection-sync feature, not a backup of every local app feature. Account Trading and tournament saves use their own data flows below. Account sign-in and account service requests use HTTPS. On Windows, saved account recovery material is encrypted using Windows Data Protection; the app does not save your password. This protection is separate from collection files and backups you choose to export.

 

Trading and notifications

Trading uses your account and participant identifiers, nickname, optional contact handle, participation setting, and the Trade and Wanted cards you publish with their quantities and conditions. Matching traders can see the profile and card details needed to arrange a trade. Offers store the participating traders, selected cards, optional messages, status and history.

 

On supported platforms, push notifications use Google Firebase Cloud Messaging, Apple push delivery on iOS, and our notification service. These services use installation or device tokens and app configuration information to route messages. A token may be created or recorded even when visible alerts are disabled. Permission to display alerts and the app's alert setting control delivery behavior; they do not erase every identifier already held by notification services. Notification identifiers are used for app functionality, not advertising tracking.

 

You can change your published Trading information in the app. On platforms with push support, you can also change alert settings and control notification permission in your device Settings. Push notifications are not available in the current Windows app; use the Trade Inbox to check offers and replies.

 

Tournaments and spectator pages

Local tournament information stays in app storage unless you save it to your account, export it or publish a spectator view. Private account saves can include event and player names and identifiers, date and venue, notes, deck references, check-in, pairings, standings and results. They can also contain recorded entry fees, paid status and amounts, draft costs, prize amounts and store credit. These are records you enter; the app does not collect payment-card or bank credentials for them.

 

If you publish a spectator page, viewers can see the event details, player names, pairings, standings and results selected for that public view. The public view excludes private payment, prize and notes fields. Share only information you are authorized to publish. Removing a public page cannot retrieve copies or screenshots already made by viewers.

 

Community content rules

Keep Trading profiles, contact text, offer messages and public tournament content appropriate for a collecting community. Do not post harassment, threats, hateful or sexually explicit content, content exploiting children, scams, spam, or another person’s private information without permission. Publish only content you have the right to share. Use Report content or Contact Support to flag a concern; Trading also offers Block trader. We may remove or disable content and restrict accounts that violate these rules. Contact cole@piratepeteccg.com about a report or moderation decision.

 

Reporting content and blocking

You can report Trading or public tournament content and block another trader or tournament host. A report stores your reason, the relevant profile, offer or public tournament content, record identifiers and timestamps. Account Trading reports also identify the reporting and reported participants. Public tournament reports identify the event and its account publisher; the report form does not require you to sign in. Reports may contain quoted messages or names needed to explain the issue. Avoid adding unrelated personal information.

 

Reports, evidence and moderation decisions are kept separately from ordinary account records. Authorized operators can review reports and restrict content or publishers; actions record the operator and time. Submitting a report does not automatically remove content. These records and restrictions are not automatically erased when an account is deleted or when a report is reviewed.

 

Trading blocks are saved for your account so they can apply across your devices. A tournament host block on a spectator page uses a persistent, randomly generated browser cookie. Our service stores a hash of that browser identifier and the blocked publisher identifier to hide that host's events in the same browser. It does not link this viewer cookie to your app account or use it for advertising. You can unblock the host using the page's control; clearing the cookie resets the browser preference but does not itself delete previously stored server block records.

 

Camera, photos, scanner and graded cards

The app uses your camera or chosen photos when you scan cards or graded-card barcodes, add a custom graded-card photo, or attach report evidence. It does not upload your entire photo library.

 

The card scanner performs local reading and catalog matching. When you scan with a game selected and online assistance is available, an uncertain match may automatically send a processed image, recognized text and card/game hints to our scanner service to help identify the card. This is part of using the scanner and is separate from optional usage sharing. The scanner service processes those inputs to return matches; service-operation and connection information may also be processed to keep the service reliable and prevent abuse.

 

On Android, local scanner features use Google ML Kit. Its SDK separately sends device and app details, installation identifiers, feature events, and performance/error metrics to Google for diagnostics and SDK usage analysis. This technical collection is separate from optional app usage sharing and from the processed image or recognized text our scanner service may receive for online assistance, as described above.

 

Custom graded-card photos are saved in local app storage. A certificate lookup sends the selected grading company and certificate number to our lookup service and, when needed, the relevant grading provider. It does not send your custom graded-card photo. Lookup results may include provider-hosted card images.

 

Market lookups, reports and quote requests

When you request an eBay market lookup, our service receives the card, set and game terms and applicable grade or other card details, and may query eBay. Certificate and market results may be cached so repeated requests can be served efficiently. These requests also involve ordinary network information, such as the IP address used to connect.

 

A catalog report sends the selected card details, issue type, correction or notes, app version and any evidence image you choose to attach. We retain reports and evidence so staff can investigate and correct the catalog. Please avoid including unrelated personal information.

 

A quote request prepares your selected card quantities and estimated values for an email attachment or share action. Your mail or sharing app lets you choose whether and where to send it. If you send it or contact support, the recipient receives the message, attachment and sender/contact information supplied by that service. Sending a quote or support message is separate from account sync and usage sharing.

 

Optional usage sharing with Google Analytics

Optional app usage sharing through Google Analytics is not available in the current Android, macOS and Windows apps and remains disabled on those platforms. Android ML Kit technical collection is described in the scanner section above.

 

On iOS, you can choose whether to share app usage through Google Analytics for Firebase. Optional usage sharing is off by default and can be enabled only in App options → Privacy & Data → Share usage analytics. There is no startup consent popup or request to track you across other companies’ apps and websites. The updated iOS 2.0.7 release resets choices from earlier test builds to off; you can make a fresh choice in Settings. Turning sharing on or off does not change access to app features. Account services, notifications and separate crash diagnostics continue under the practices described in this policy.

 

When enabled, reports use a resettable app-instance identifier and basic app and device information. They include app lifecycle/session activity, relevant notification interactions, fixed public game and feature categories, setup milestones, broad sync outcomes and rounded operation times. Google can derive approximate geography from your connection's IP address; the app does not request GPS location for Analytics.

 

The app does not set an Analytics account/user ID or send your email, collection names or contents, private card records, search terms, notes, messages, files, photos or raw error text as custom usage events. Advertising identifier collection, advertising consent, ad personalization and automatic screen reporting are disabled. The app-instance identifier still distinguishes an installation, so these reports are not described as fully anonymous.

 

Turning sharing off stops collection, clears queued custom usage observations and resets the local Analytics identity. It does not delete reports already delivered to Google. Read more about how Google uses information from apps that use its services.

 

Crash and reliability diagnostics

Sentry crash and error reporting is disabled in the current Android, macOS and Windows apps. This does not disable the separate Android ML Kit technical collection described above.

 

The configured iOS app uses Sentry for crash, app-hang and filtered error diagnostics to help us fix failures. Diagnostics are separate from the Share usage analytics choice. Reports include technical information such as the app build, OS/device characteristics, fixed error categories and crash stack information.

 

The iOS app filters Sentry reports before sending them to remove account and device identifiers, request details, private content and raw error messages. Our Sentry project is configured to prevent new stored IP addresses and remove inferred user-location fields. The current configuration disables session replay, screenshots, view-hierarchy capture, automatic breadcrumbs, session tracking, tracing and profiling. These controls do not retroactively erase older reports. Network services still need to process connection information to receive requests.

 

Service providers and sharing

We use service providers to operate accounts, hosting and data storage, notifications, requested lookups, diagnostics and optional Analytics. These include Google Firebase, Google ML Kit for Android scanning, Google Analytics and Sentry on iOS as described above, Apple push services on iOS, and the relevant card-market or grading service when you request a lookup. Staff access submitted reports and support messages to respond and maintain the service. Trading participants and public tournament viewers receive the information described above.

 

Providers process information under their terms and privacy policies and may operate outside your country. See Firebase privacy and security information and Sentry's privacy policy. We may also disclose information when required to comply with law or to protect the service and its users.

 

Deletion and retention

You can request account deletion from the app's Account area. The deletion flow closes account Trading and tournament access, removes active cloud collection and account records, and deletes the associated Firebase sign-in identity.

 

Some records remain after deletion. Shared trade-offer history retains card lines, participant and audit identifiers, timestamps and status, while offer messages and active profile contact details are cleared. Limited closed-account, tournament/public-code ownership and deletion-completion records remain to prevent old devices or requests from reopening deleted data. These retained records are not all anonymous.

 

Account deletion does not erase local app records, device or file backups, exports, other people's copies, separate catalog/support and moderation submissions, or Analytics and diagnostic reports already sent. Notification-provider identifiers also have their own lifecycle. Uninstalling the app alone does not delete your account.

 

Retention varies by record and provider; we do not apply one fixed deletion period to all information. Catalog reports and evidence remain available for correction and support. Moderation reports, relevant evidence, operator decisions and restriction records remain for handling abuse and protecting the service; they have no automatic time-based deletion in the current system. Lookup results use caches, and operational or backup records can remain after active records are removed. Firebase currently states that authentication information is removed from its live and backup systems within 180 days after deletion of the associated user; notification installation identifiers follow a separate deletion process. For help deleting information outside the in-app account flow, contact us with enough detail to identify the record. We may need to verify ownership before acting.

 

Your choices and contact

You can use local features without an account, choose what to sync or publish, turn optional usage sharing off, manage camera/photo/notification permissions in device Settings, and choose the recipients of exports and messages. The app is not directed to children under 13.

 

For privacy questions, support or deletion help, contact Pirate Pete CCG at cole@piratepeteccg.com. We will update this page when our practices change.