1. What information is collected
When you submit the evaluation form, the current flow stores limited metadata related to the request. That may include the selected card brand, entered amount, currency, input mode, whether supporting fields were provided, masked last four digits when available, locale, timestamp, and form version details.
2. What is not retained in the current flow
The current implementation is designed not to retain full card codes, brand PIN values, CVV values, or uploaded card images as part of the Firebase submission record. The image upload flow is handled as an in-session processing step rather than a retained file archive.
3. How the information is used
The limited metadata is used to support the submission workflow, issue a reference ID, and preserve a minimal record of the request. It is also used to understand which evaluation path was selected. If operator notifications are enabled for workflow monitoring, those notifications are limited to the same reduced metadata rather than full submitted card details.
4. Analytics and technical logging
The current static frontend does not include a dedicated third-party analytics script. Basic technical hosting or platform logs may still exist as part of Firebase infrastructure operations. If product analytics are added in the future, this policy should be updated before or when they are introduced.
5. Security
The site is intended to be served over HTTPS through Firebase Hosting. That helps protect data in transit. No system can promise zero risk, so users should still avoid submitting more information than necessary and should rely on official issuer channels for final confirmation.
6. Contact
If you have privacy questions, contact support@card-verify.com. We typically respond within 24 to 48 hours.