Optional Meta ad measurement
When this feature is enabled, we ask before sending website activity to Meta. If you choose Allow measurement, we may send visit, search, useful-result, signup-start, completed-registration and first-card-save events with event time, a deduplication identifier, a public site URL, your IP address, browser user agent and an ad-click identifier when available. We do not send card identities, card prices, vault contents, email addresses, passwords or payment details through this integration.
We use these events to measure and improve our advertising. Meta may match events to its users and use them for ad personalization, measurement and improvements to its products under its privacy policy and Business Tools Terms. This is optional: declining does not affect your free account or the card-check service.
Use Ad privacy choices on the card-check, signup, login or privacy page to withdraw permission. Withdrawal stops future events from that browser and cancels its unsent events; it cannot recall events already sent. We honor Global Privacy Control and Do Not Track signals. The browser choice expires after 90 days. Matching data is cleared when permission is withdrawn or expires; consent and delivery audit records may be retained for accountability. Contact [email protected] about access or deletion.
What HaloVault is
HaloVault is a photo-first inventory workspace for cards, collectibles, shop stock, consignments, and related sale records.
The service is multi-tenant. Each vault belongs to a tenant, and user access is controlled through that tenant's memberships.
Your data and ownership
You own the inventory records, photos, notes, location labels, pricing work, certificates, exports, and other content you put in your vault.
We use that content to run HaloVault for you: storing it, organizing it, showing it to the people and public pages you choose, preparing exports, and powering features you use.
By uploading photos and other media, you grant HaloVault a license to host, display, and use them to operate, improve, promote, and market the service and its features — including public card pages, share links, the collection network, and marketplace tools. The full license is in the Terms of Service.
We do not sell your vault data.
AI-assisted identification
When you use card or binder scanning and identification features, HaloVault sends downscaled images or cropped portions of images of your collectibles to the paid Google Gemini Developer API to identify the collectible and extract information about it (for example, the player, set, card number, grading, or condition).
We limit what we send to what is needed for identification. We do not include your name, email, account identity, device identifier, or vault details in these requests — Google receives the compressed image derivative and an identification instruction only.
Under Google's paid-service terms, Google does not use the images, prompts, or responses from these requests to train or improve its products. Developer-owned request storage is disabled for the standard GenerateContent API used by HaloVault, so those requests are not stored in Google AI Studio logs. Google may still process or retain data for abuse monitoring, safety, legal, or security purposes as described in its current policies; HaloVault therefore does not claim contractual zero retention by Google. HaloVault does not store the outbound AI request or keep the image bytes in application logs.
Scene detection (finding objects in a wider photo) runs on HaloVault's own servers. Card and page identification is the feature that uses a third-party AI provider.
Nothing an AI suggests is saved to your inventory automatically — you review and confirm every item.
Photos and EXIF
HaloVault stores photos you upload or capture for inventory, intake, sales, insurance, and audit workflows.
Photos may include EXIF or similar metadata from the source device, such as timestamps, camera details, orientation, and sometimes location data if your device saved it.
We use photo metadata when it helps document items, preserve evidence, rotate images correctly, detect duplicates, or improve inventory workflows. You should remove sensitive metadata before upload if you do not want it stored in your vault.
Public share-link views
When someone opens a public share link you create for an item, HaloVault records a view for your vault analytics.
Each view may include the visitor's IP address, approximate location (city, region, country), ISP or network name, browser user agent, referrer URL, and timestamp.
This view history is available to your vault members on every plan, including free. It is not shown on the public page and is not sold.
First-party operational analytics
HaloVault records first-party operational analytics for dynamic site and API requests so we can monitor reliability, investigate errors and abuse, and understand product traffic.
These records may include the requested path and route, request method, response status and duration, timestamp, host, IP and forwarding information, browser user agent, a sanitized referrer scheme, host, and path, first-party visitor and browser-session identifiers, and the signed-in user when available. Referrer queries and fragments are removed.
HaloVault also records first-party page-view and visible engagement-time events so we can understand journeys, session duration, bounce rate, and signup conversion. If a link includes standard UTM campaign fields, we retain only the bounded utm_source, utm_medium, utm_campaign, utm_content, and utm_term values for attribution; unrelated query-string text is not retained.
These analytics records do not store request bodies, typed text, passwords, payment details, or the contents of a vault. Requests under the configured /static/ and raw /media/ prefixes are excluded from request logging.
Cardboard collection goals and catalog contributions
Cardboard stores the finite collection goals, checklist versions, missing-card requirements, and progress calculations you create. Exact inventory records remain inside your vault unless you separately make an item public or link-only.
Each goal lets you choose private, de-identified aggregate, or collector-network use. Private goals are excluded from Cardboard demand intelligence. Aggregate and network use require an explicit confirmation and may contribute non-identifying counts such as the type of goal, checklist target, completion level, and cards still needed.
Aggregate intelligence does not disclose your account, exact collection, storage location, serial numbers, or private budget. Reports suppress targets until enough different collectors share the same signal.
Checklist corrections and source suggestions are submitted only when you attest that HaloVault may review the evidence. Contributions remain reviewable and are not silently promoted into the published catalog.
Payments through Stripe
HaloVault uses Stripe for subscription checkout and seller-connected checkout where enabled.
Stripe processes payment card details, payment authentication, payouts, refunds, disputes, tax-related payment records, and fraud checks under Stripe's own terms and privacy policy.
HaloVault stores payment status, Stripe identifiers, order amounts, fee amounts, plan requests, and records needed to reconcile purchases. We do not store full payment card numbers.
Marketplace agreements and transaction evidence
When a vault owner activates selling, or a buyer makes an offer, places a bid, or starts checkout, HaloVault records the policy name, version and SHA-256 digest, the affirmations accepted, timestamp, account or submitted email, tenant, IP address, browser user agent, and the related marketplace context.
We retain these records for contract evidence, fraud prevention, marketplace safety, payment disputes, accounting, tax, and legal compliance. Deactivating selling does not erase acceptance or transaction records.
eBay and Discogs integrations
If you connect eBay, HaloVault may exchange listing, inventory, order, account-status, fulfillment, and token information with eBay so you can publish, update, withdraw, or reconcile listings.
If you use Discogs workflows, HaloVault may use release, marketplace, collection, wantlist, pricing, and catalog data needed to match records and prepare listings.
Connected marketplace data is used to provide the integration you enabled. You can disconnect integrations or ask us to remove stored integration tokens and related sync data.
Exports and deletion
You can export your inventory data from HaloVault in the product where exports are available, including CSV inventory exports.
You can ask us for a broader export or deletion of your account or tenant data by contacting [email protected].
Deletion removes active application records we control, subject to reasonable time for backups and subject to records we must keep for security, fraud prevention, legal compliance, payment reconciliation, tax, dispute, or accounting reasons.
Security and access
We use access controls, audit logs, and operational safeguards to keep tenant data separated and to limit access to people and systems that need it to run the service.
No internet service is perfectly secure. Tell us quickly if you believe your account, vault, share link, marketplace account, or payment flow has been compromised.
Contact
For privacy, export, deletion, marketplace data, or security questions, contact [email protected].