Contact the Valdar support team
One address · We reply within 1–2 business daysEverything reaches one address: [email protected]. There is no ticket portal, no chat widget and no phone queue. The same small team that builds the app and writes this site reads the inbox, in English or Russian.
That has one advantage and one cost. The advantage is that a report about a misidentified card reaches the person who can go and look at why it was misidentified. The cost is that a message arriving without enough detail to reproduce the problem needs a round trip before anything can be checked, and a round trip is a day. Most of this page is about avoiding that round trip.
App support
Scanning that misses, a card identified as the wrong parallel, sync, crashes, feature requests. Include your device model and app version — it is the difference between a same-day answer and a week.
Email supportBilling
Subscription questions and refunds. Payments are processed by Apple and Google, never here, so a refund is issued by the store that took the money — this inbox can tell you which route yours needs.
Email billingPrivacy and data
Access, export, correction, objection or deletion, under GDPR, CCPA/CPRA or the equivalent where you live. The privacy policy sets out what exists to be exported; requests are answered within 30 days.
Data requestCorrections, reuse and press
A figure that is wrong, a link that has died, a dataset you want to build on, or a question from a publication. Corrections are credited; the data is open and most reuse needs no permission at all.
Email usWhat to include so the first reply is the useful one
A support message is either reproducible or it is a conversation. Five facts turn almost any report into something that can be checked the same day: the device, the operating system version, the app version printed on the Settings screen, what the card actually was, and what the app said about it.
The last two carry more weight than they look. “The value is wrong” cannot be checked by anyone. “1989 Upper Deck #1, raw, the app showed 32 dollars and the sold listings I found were 70 to 95” can be, because it names the card, the condition assumed and the comparison being made. A screenshot carries the first half of that and almost never the second.
| If you are writing about | Send | So that |
|---|---|---|
| A card the scanner did not recognise | The photograph you scanned, plus the year, set, player and card number as printed | the failure is reproduced against the same image rather than against a better one |
| A value that looks wrong | The card as the app identified it, and two or three sold listings you found | the gap is checked against the comparison you actually made |
| A grade estimate that looks wrong | The photographs, and the grade the card came back at if it has since been slabbed | an estimate is compared with an outcome instead of with an impression |
| A crash, or a screen that will not load | Device model, OS version, app version from the Settings screen, and the last thing you did | the crash log is matched to a build and to a step |
| A subscription or a refund | Which store you bought through, and the date of the charge | the reply points at the right refund route first time |
| A privacy, export or deletion request | The account email, or the device the collection sits on | the right data is found and removed rather than guessed at |
| An error in a published figure | The URL, the row or field name, and the figure you believe is correct | the correction can be checked against the source the same day |
| Reuse, press or a partnership | What you want to publish, where, and by when | the answer is a yes or a no rather than a request for more detail |
Attachments are welcome, and the photograph you actually scanned is worth more than a better one taken afterwards. When recognition fails it is usually the photograph that failed, and a clean replacement shot removes the evidence.
What this inbox can answer, and what it cannot
Vast Flow, LLP publishes this site and builds the Valdar app. It is a software studio: not a grading company, not a card shop, not an auction house and not a certified appraiser. Three kinds of request arrive here regularly that it cannot honestly serve, and saying so is faster than a polite non-answer three days later.
The first is a valuation of one specific card by email. Nobody can value a card they cannot see, and a valuation that would stand up needs the right set, the right parallel, the right condition and sold listings from the right window. That work is what the app does with the card in front of it, and what the sold-comps calculator does with the listings you have already found. A reply typed into an email would be a guess wearing a signature.
The second is a grading opinion. Only PSA, BGS, SGC, CGC and TAG issue grades, and nothing published here is issued, endorsed or recognised by any of them. What can be answered without seeing the card is the one grading input that is a measurement rather than a judgement: the centering calculator takes four border measurements and reports the highest grade each company’s published tolerance allows. Corners, edges and surface are opinions formed under magnification, and an email cannot form one.
The third is a sale. Nothing is bought, sold, consigned or brokered here, and no commission is taken on any transaction anywhere. The question behind most of those messages — where should this card be sold — is answered by the where-to-sell calculator, which compares seven routes to cash on the same card, net of every fee and of the waiting.
| The question | Answered by email | Where the answer actually is |
|---|---|---|
| “What is this card worth?” | No | The app, or the sold-comps calculator — a valuation needs the card in front of something that can see it |
| “What grade would this get?” | No | The centering calculator measures the one part of a grade that is a measurement |
| “Will you buy, sell or consign this?” | No | Nothing is bought or sold here; the where-to-sell calculator compares seven routes |
| “Is this a rookie card?” | No | The rookie card checker answers it from the convention for that sport and year |
| “The app identified a card wrongly” | Yes | — |
| “A figure on this site is wrong” | Yes | — |
| “May I republish your data?” | Usually no permission is needed | CC BY 4.0 — attribution is the whole requirement |
| “I want a refund” | Partly | The store that took the payment issues it; this inbox can point you at the route |
Found an error in a published figure?
Corrections are welcome and they are credited in the reply. Every reference figure on this site is a transcription of something a third party published, carried with the date it was read and a link to the page it came from, which means two different things can be wrong: the transcription, or the source moving underneath it. The second is far more common. Grading companies revise their standards, marketplaces reprice their fees, and the transcription sits there looking authoritative until somebody checks.
What makes a correction actionable is the address of the number. A calculator result needs the inputs you typed. A
reference table needs the page and the row. A JSON field needs the endpoint, the field name and the
as_of date carried in the envelope. With that, a correction takes minutes; without it, it takes a
round trip. The reference layer was last read on 2026-09-11 and cites 8 primary sources,
every one of them linked rather than copied, so the live page is always the thing to check first.
| Where you found it | Quote this | What it is |
|---|---|---|
| A calculator result | The tool URL and the numbers you typed | Computed in your browser from your inputs, by one shared arithmetic module |
| A reference table on a tool page | The tool URL and the row | A transcription of a published source, carried with the date it was read |
| A field in the JSON API | The endpoint, the field name, and the as_of date in the envelope | The same transcription, machine-readable |
| A figure or a chart | The page URL and the first line of the caption | Drawn from the table on the same page, never from numbers typed under it |
| A scouting report | The URL and the sentence | Editorial, written and signed |
| Something the app said | The card, the screen, and the app version | A model output, which is why the photograph matters more than the description |
When a correction lands, it changes in one place. The reference values live in a single data module that the pages, the 7 open datasets and the machine endpoints all read, so a corrected figure moves through the web pages, the JSON and anything built on it together. That is the entire reason the numbers are not typed into the markup, and it is why a correction is worth sending rather than working around.
Dead outbound links are the same class of report and the least glamorous one. Every published tolerance, fee schedule and population report on this site links to the publisher’s own page rather than to a copy of it, which is honest and also fragile: those pages get reorganised. If a source link lands on a 404, that is a real defect and it gets repointed.
Reusing what is published here
The datasets are published under CC BY 4.0. Most reuse therefore needs no permission at all: copy them, republish them, build a product on them, charge money for that product. The only requirement is attribution — a credit naming Sports Card Radar, with a link back to the page or the endpoint the data came from. That link is the entire price, and it is the reason the licence is there.
Three things sit outside the licence and do need an email. Using the Valdar name or logo in a way that suggests a partnership, a sponsorship or an endorsement is the first, because attribution and endorsement are different claims and only one of them is granted by a licence. The second is the editorial text of the scouting reports and the tool pages, which is written rather than transcribed and is not under CC BY. The third is any arrangement that needs something a licence cannot give: a guarantee of uptime, a promise that a field name will not change, or a dated snapshot held still for a citation.
There is no rate limit on the API today and no key to apply for. If you are pulling it at volume, cache it — the reference data changes when a grading company revises a scale, which is not often, and the API page documents how each dataset moves. The terms set out the rest, including the one condition that matters more than volume: do not present the data as endorsed by, or sourced from, any of the companies it describes.
Press and partnerships
Card shops, breakers, content creators and anyone working with market data are all welcome to write. What makes a press request fast is the same thing that makes a support request fast: the publication, the deadline, and what you actually need — a quote, a screenshot at a particular size, a figure from the open data, or a look at how a number was computed. Logos, app screenshots and the reference figures can all be supplied at print resolution.
Partnership proposals get a straight answer rather than a slow one. The test applied to them is narrow: does this help somebody price or protect a collection, and can it be published without claiming something that is not true. Anything that would require presenting an estimate as a valuation, or an affiliation that does not exist, is a no on the first reply.
Billing, refunds and subscriptions
Subscriptions are sold and billed by Apple and Google, not by this site, and that is why a refund cannot be issued from here. Cancellation is handled in your App Store or Google Play account settings, and deleting the app does not cancel a subscription — the two are separate actions and only the second one stops the billing. If you are not sure which store took the payment, the receipt in your email will say. The terms of service set out the renewal and refund position in full.
Privacy requests and deletion
Requests to access, export, correct, object to or delete personal data are answered within 30 days, and they go to the same address. It helps to name the account email or the device the collection sits on, because that is what identifies the data to be acted on. The privacy policy sets out what is collected on each surface, which is worth reading first: the free calculators on this site transmit nothing at all, so there is genuinely nothing on that side to export.
Who you are writing to
Vast Flow, LLP is the legal entity behind both the app and this site, and it is the entity named in the privacy policy, in the terms, and in the App Store and Google Play listings. Who publishes this explains what the studio does, what it does not claim to be, and how a number gets onto a page here.
Correspondence is by email. Where a request genuinely requires a postal address of record — a formal notice, a rights request under a regime that demands one — say so in the first message and it will be supplied. For everything else, [email protected] is the whole contact surface, and it is read by people who can actually change the thing you are writing about.