Effective date: October 16, 2026.
Copper Heron Labs LLC operates Card Exhibit. Card Exhibit helps you scan, organize, search, and display a sports card collection. This policy explains how the app handles information.
Saved collection storage
Card Exhibit stores your saved card details, confirmed card photos, Favorites, custom collection memberships, and app preferences locally on your device. The app does not currently include an account login, cloud-sync service, advertising identifiers, or in-app analytics.
After a card has been saved, you can browse, search, edit, and display your collection without an internet connection. Saved records remain until you delete them or remove the app’s data. Device or iCloud backup settings may create additional copies under Apple’s applicable policies.
Camera, local label reading, and optional online correction
Card Exhibit uses the camera when you choose to scan. The current version reads visible slab-label text on your iPhone using Apple Vision. Label reading, manual cropping, editing, and saving do not require photo uploads. Results may be incomplete or incorrect; review every field before saving.
Camera permission does not authorize uploads. Optional automatic corner detection and perspective correction send the captured photo securely to our service hosted by Render. The photo may include the background and visible certification information. The app explains this separately and remembers your choice across restarts. It checks your saved permission before each upload, without repeatedly prompting you. With permission, uploads may begin after capture, before review. Turn uploads off in More → Privacy & Support to continue local label reading, manual cropping, editing, and saving. This stops future uploads but cannot recall information already sent.
The current version has no Identify or cloud-OCR recognition fallback. Your saved collection is local. Captures/cache copies can remain until app/operating-system cleanup; no fixed deletion interval or secure erasure is promised.
Earlier app versions
Earlier versions sent scan images to CardVault Identify and label crops to OCR.space. Identify has closed; Card Exhibit’s backend now blocks upstream Identify calls. Our backend no longer forwards images to Identify or OCR.space. Older installed versions may still send label requests to our backend when uploads are allowed, but receive no automatic label text; details remain available for manual entry. Stopping future uploads does not delete historical copies held by providers. The sections below distinguish legacy providers from current optional correction.
Hidden owner diagnostics
Owner diagnostics are hidden behind a passcode and disabled on a fresh launch. When enabled, they temporarily hold the latest label-reading text, image-area coordinates, suggested fields, and limited error details on the device. They remain available during normal navigation and temporary backgrounding within the same app session. Disabling diagnostics or selecting lock and clear removes this information. Nothing is automatically uploaded; the owner can choose to copy it locally or send it to support.
Motion guidance
While the scanner is open, Card Exhibit may use your device’s motion sensors to show a level-guidance indicator. This helps you hold the phone level while photographing a card. Motion data is used locally for that display, is not saved to your collection, and is not sent to the scan backend or processing providers. The level indicator is optional guidance and does not prevent a scan if sensor access is unavailable.
What the backend handles
Our service processes uploads without maintaining a permanent collection database or image library. The reviewed application code does not intentionally save photos or label-reading results after processing. Temporary files may be used while handling an upload. This describes the application code, not a guarantee about every infrastructure copy.
Service logs can contain timestamps, network addresses, requested endpoints, response status, and request identifiers. When timing logging is enabled, logs can also contain processing durations and limited error information. The reviewed application logging code is designed to exclude photos, label text, card details, and API keys. Network addresses may also be used temporarily to limit excessive requests.
The currently selected backend region is Oregon (US West). Render documents seven-day dashboard log retention for the confirmed Hobby workspace. That is not a promise that every copy, manual export, backup or other provider record is deleted in seven days.
Render and other infrastructure providers may have their own operational, security, and access logs. Their logging, retention, and processing practices are separate from Card Exhibit’s application code. See the provider links below for available information.
Third-party processing providers
Card Exhibit uses third parties for online scanning features. Their practices are governed by their own terms and privacy policies, and may change.
- Render hosts the Card Exhibit scan backend. Render receives network requests and scan uploads needed to operate that backend. Render Privacy and Render Logging.
- CardVault Identify (historical processing) previously received scan images. Its still-accessible policy describes retaining images and request logs to operate and improve the service, with possible aggregated or anonymized information after account deletion. The operator has confirmed closure; the published policy does not establish what historical information is currently retained or when it will be deleted. Our live backend blocks further Identify calls. CardVault Identify Privacy Policy.
- OCR.space (historical processing) previously received focused slab-label image crops from the Card Exhibit backend for OCR. Our backend no longer forwards images to this provider. OCR.space publishes that cloud-OCR uploads are deleted after processing and API-access IP addresses are retained for one month. OCR.space Privacy Policy.
These published provider practices are distinct from storage of your collection on your phone. Card Exhibit does not offer a universal provider deletion deadline, an assurance that providers never retain or use information to improve their services, or a promise that all processing occurs in one location. Contact us for privacy or provider-deletion requests. We can handle requests concerning information we control and coordinate with a provider when required; a local card deletion alone does not delete information held by providers.
Diagnostics and network information
Using online scanning sends ordinary network information, such as an IP address and request metadata, to the Render-hosted backend as part of delivering the request. Earlier versions sent provider requests from the backend without forwarding the phone’s client-IP header. Our backend no longer sends images to Identify or OCR.space. Providers and infrastructure operators may still collect network information associated with their own services under their own practices. The backend uses a non-secret request ID to correlate a scan request with limited service diagnostics. It does not create user accounts or link scans to an account profile.
Support communications
When you email support@copperheronlabs.com, Copper Heron Labs LLC receives your email address, message, and any attachments you choose to send so that we can respond to your request. Support email is provided through GoDaddy. Please avoid sending card photos, certification numbers, backup archives, or other sensitive information unless it is necessary for your support request.
You can send privacy or deletion requests to the same address. Copies held by our email provider or in backups are subject to the provider’s practices. We do not promise a fixed deletion deadline for those copies.
We keep support messages while your request is open. We review resolved conversations monthly and normally delete messages and attachments under our control within four months of the last support exchange. We may retain necessary information longer for a specific legal obligation or active dispute. You can request earlier deletion at support@copperheronlabs.com. Copies in provider backups or recovery systems follow the provider’s retention practices.
Deleting cards and backups
You can delete a saved card from Card Details. This removes its local collection record and attempts to delete its app-managed saved image. If file cleanup fails, an unreferenced local image can remain; temporary capture/cache files are separate. Local deletion does not guarantee secure erasure and does not remove:
- a backup archive you previously exported;
- copies stored in iCloud Drive, device backups, or another location you chose through iOS Files; or
- information that Render, CardVault Identify, OCR.space, or another provider may retain under its own practices.
Card Exhibit offers a user-controlled collection export. An export can contain saved cards, photos, Favorites, custom collections, and memberships. You choose where to save it through the iOS share sheet. If you choose iCloud Drive, Apple stores that exported backup under your Apple account and subject to Apple’s applicable terms and privacy practices. Card Exhibit does not upload recovery archives for you.
Keep exported archives in a location you control and protect them appropriately. Archives are unencrypted and contain saved photo bytes, not a separate original camera capture. Creating an export or dismissing the share sheet does not prove the archive was saved outside the app: verify the Files destination before confirming. Import adds missing records while keeping existing saved cards and images; it can recover archived cards deleted after a previous import, and repeated imports do not duplicate surviving cards. It does not remove previously exported copies.
Contact us
For questions about Card Exhibit, to withdraw consent, or to request access, correction or deletion of information we control, contact support@copperheronlabs.com. You can also withdraw future photo-upload consent in More → Privacy & Support without deleting your collection.
Changes to this policy
We will update the date on this page when the policy changes. Material changes to photo-upload purposes or recipients will be reflected in the app’s disclosure and permission flow before the new processing occurs.