RB
Reviewboard MagazinePrivacy policy

Reviewboard Privacy Policy

Reviewboard Magazine provides Product Signal, account, membership, mobile scanner, coupon wallet, member offer, and paid-member Scan Challenge services.

Information we collect

We collect account email, authentication/session data, scan inputs such as barcode, VIN, product query, ZIP, optional location when provided, Product Signal results, subscription status, coupon claims, support/contact messages, support message status, and operational logs needed to run the service. Full VINs, free-form scan inputs, and precise coordinates are encrypted in a private operational record. A VIN is never displayed on a public page or placed in a public URL. The Android app also registers a random installation ID and may report app version/build, Android version, device manufacturer/model, locale, install source, and bounded events such as app open, login, scan, subscription, and security events.

Reviewboard does not collect advertising IDs, permanent hardware identifiers, contact lists, background location, or cross-app tracking data.

Location

With foreground permission, the Android app keeps only the latest usable location in memory while the app is open and attaches it only to a relevant scan or deal request. Reviewboard never collects a background location trail. If permission is denied or location is unavailable, Reviewboard uses ZIP/manual context instead. Request-linked precise coordinates are removed after 30 days.

How we use it

We use this information to return product and vehicle intelligence, improve the product graph, provide regional and online member offers, process subscriptions, issue and validate coupons, prevent abuse, store and handle support/correction/privacy/merchant inquiries, track support status, and operate the service.

Public catalog

Public Product Signal pages show product and decoded vehicle intelligence only. Full VINs, customer names, account identities, and individual shopping histories are not displayed in the public catalog. Private VIN records are masked by default and available only to the owner through audited administrative actions.

First-party analytics

Reviewboard uses local, first-party analytics to understand aggregate traffic, app reliability, content use, searches, and scan outcomes. Analytics do not contain VINs, barcodes, precise coordinates, ZIP codes, email addresses, tokens, camera data, or free-form search text. We do not use advertising IDs, cross-site identity, or browser fingerprinting. Global Privacy Control and the opt-out below disable browser event collection immediately.

Coupons and merchants

When a member claims an offer, Reviewboard may create a signed coupon token or register payload. Redemption checks may share only the coupon information needed for validation, merchant scope, expiry, and anti-replay protection.

Payments

Android in-app membership checkout is handled by Google Play Billing. Website-origin membership checkout is handled by Stripe. Reviewboard stores subscription status and provider references needed to unlock account access, but does not store full card numbers.

Scan Challenge

The Scan Challenge is opt-in. Reviewboard records the account, rules version, acceptance time, active paid-membership status, eligible scan entry, item snapshot, and drawing/audit state. Public winner listings use a generated privacy-safe handle rather than an email address or legal name. If a selected entrant submits a claim, Reviewboard collects the recipient name, shipping address, and optional phone number solely for eligibility review and fulfillment. Shipping details are encrypted at rest, restricted to authenticated promotion administrators, and never displayed on the public Winners page.

Data sharing

Reviewboard may use product, vehicle, image, sentiment, email, billing, and infrastructure providers to deliver Product Signal and account services. We do not sell customer names or individual shopping histories as public catalog content.

Choices

Contact

Use the Contact Us form for privacy questions or correction requests.

Request facts and precise coordinates are retained for 30 days; crash/error detail for 90 days; detailed activity, full VINs, and other detailed scan inputs for 180 days; and non-identifying daily aggregates for 36 months. Administrative and security audit records are retained for two years. An app heartbeat shows only when an installation was last seen; Reviewboard cannot reliably know whether an app is currently installed.

Last updated: August 16, 2026.