CARDREVIVE INSPECTOR

Privacy

Inspector uses your email address to create and secure your account. Supabase provides authentication and stores the link between your account and your billing customer record. Stripe handles payment details, billing names and addresses, any tax identifier you choose to provide, subscriptions and invoices. CardRevive does not receive or store your full card number.

Your inspection images

The workbench processes card images locally in your browser and does not send them to AI services. Loading a scan does not upload it to the cloud. Your current inspection images and notes autosave locally in this browser on this device. Choose Clear saved inspection to remove that local copy.

Saved card projects

For uploaded scans, you can choose Save to cloud in Cards. This stores the project name, card images, inspection notes, settings, checkpoints and explicitly attached evidence in private Supabase storage associated with your account. Load from cloud lets you reopen a saved card for editing on another device while signed in with an active Inspector subscription or an eligible trial offered at checkout. Camera sessions are not automatically saved as cloud card projects. A camera close-up or proof clip is included when you explicitly attach it to a scanned-card project and save that project.

Cloud saving is an explicit action, not background sync. Export a project to keep a separate file; importing one opens it locally until you choose to save it to the cloud. Delete a card in Cards to remove its cloud project. Clearing a local draft does not delete the cloud project, and deleting a cloud project does not remove copies you have already downloaded or saved locally.

Records after cancellation

Sign in to Saved records to download your full projects, delete records or revoke sharing, including after cancellation, a failed payment or a billing outage. This access has no cancellation countdown and lasts while your account and records exist. It does not allow new cloud saves, editing in the hosted workbench, publishing or new review invitations.

Cancellation does not automatically delete records or revoke existing customer links and named reviews. We do not currently apply automatic expiry to saved cloud projects or publish an account-wide storage allowance. This is not unlimited storage or a permanent backup guarantee. Keep independent downloads. Deleting a record ends its availability; deleting your account ends signed-in access. Contact support for account deletion or exceptional access help. See storage and browser limits.

Only one workbench tab at a time can save or clear the local draft. Other tabs can inspect and download without changing the saved copy. Download any unsaved work before closing the saving tab and reloading another one. If your browser cannot safely coordinate saving, autosave is disabled and the workbench shows a status message.

Download captures and reports to keep a separate copy. Private browsing, clearing browser data and browser storage limits can remove local work. On a shared device, clear saved inspections when finished.

Sharing and review

Publishing a customer report creates a separate customer copy that anyone with its link can view. It includes the card images, operator name, customer observations, annotations, reviewed areas and attached evidence. Workshop-only notes, checkpoints and recorded external grading outcomes are excluded. Evidence titles and clip bookmark labels are shared. Check the customer copy before sending its link.

Revoke the link to stop new access. Saving a new cloud revision or deleting its card also invalidates the publication. Previously issued download links can remain usable for up to 60 seconds, and downloaded copies cannot be recalled. A private card-ID QR label requires the card owner’s sign-in; it does not publish a report.

A second-person review gives the named, signed-in reviewer access to the full saved workshop project, including internal notes and checkpoints. Inspector does not automatically email the reviewer. Copy the review link when you are ready. Review access can be cancelled, and saving a new revision invalidates the previous review.

Images newly attached through the Evidence tool are re-encoded to remove embedded metadata. Uploaded scans, videos and media inside imported project files may retain embedded metadata, which is included when those media are published. Inspect or remove that metadata before sharing. Portable project files contain the full workshop record; use a customer PDF or selected evidence pack when workshop information should stay private.

Cookies and service records

Essential session cookies keep you signed in. The workbench saves camera and view preferences in your browser. Vercel hosts the website and may retain request logs for operation and security. Supabase and Stripe retain records needed to provide their services. Inspector does not include advertising trackers.

First-party workflow measurement

Optional first-party workflow measurement is off by default and requires explicit opt-in. It records categorical visits and workflow outcomes, the UTC date and pseudonymous browser or account identifiers, without card content, images, observations, filenames, names, email addresses or authentication tokens. Signed-in activity can be compared with subscription billing; an anonymous sample completion is not account activation. Events expire after 90 days and consent must be renewed after 90 days or when signing in or out. Disable all measurement and delete first-party events to remove this browser’s first-party sample events and the signed-in account’s usage events across browsers; projects and required billing records remain. Categorical support records contain the date, cause, time spent and a random entry identifier, with the same 90-day retention.

Public-page analytics and opt-out

Google Analytics and Vercel Web Analytics are enabled by default on known public pages. Disable them using the public-page notice or measurement preferences; existing opt-outs are preserved. This browser preference is independent of sign-in and first-party workflow consent. A one-year preference cookie and a local off choice remember your opt-out; re-enabling analytics or clearing browser storage can reset it.

These providers receive clean public page addresses, categorical pricing/signup interest or public sample completion, and browser/device information. They process the IP address used to contact them. Google uses host-only Inspector cookies for up to 90 days; Vercel uses no analytics cookies and says its visitor-session identifier expires after 24 hours. We disable advertising signals and enhanced measurement. Private routes, account identifiers, card/customer content, query strings and authentication links are excluded. Optional first-party workflow measurement remains off until you allow it.

Withdrawal stops future public-page collection and removes Inspector’s Google cookies in this browser. It does not automatically delete previously collected Google or Vercel data. Their retention and aggregate reporting are separate from our first-party 90-day deletion; Google aggregate reports can remain longer than its event-data retention window. Contact support for provider-data requests. We do not map Inspector accounts to provider visitor identifiers, which can prevent identifying an individual’s provider data for deletion.

Business records and service access

Other Inspector account holders cannot browse your private cloud projects. The server checks ownership before listing, downloading or deleting them. A customer link exposes its customer copy to anyone holding the link; a named review exposes the full workshop project to that reviewer. These are explicit exceptions to owner-only access.

Private storage does not mean that the service operator has no technical access. Privileged service credentials and provider administration can access stored records for service operation. Inspector has no customer-facing administrator access log. Do not treat Inspector accounts as separate organisations with their own administrators or as a promise of operational separation from CardRevive’s other activities. Ask support about your business confidentiality requirements before uploading sensitive records.

Questions or account deletion

Contact info@cardrevive.com.au for access, correction or deletion requests. Cancel any active subscription from Manage billing before requesting deletion. Billing records may need to be retained for legal and accounting obligations.