Trust & legal
What happens if you leave
You are about to print something permanent. Before you do, you should know what we do if you stop buying, what you can take with you, how long we keep it, and what a code on a shelf says afterwards. We would rather publish it than be asked in an audit.
Your printed codes keep verifying
A label you have paid for keeps answering. Stop buying credits and you stop making new labels — the ones already on shelves go on verifying, because the credit was spent when the code was made.
We will not turn a label on a shelf into a suspect one to settle an invoice. A buyer holding your genuine product and getting anything other than a clean answer concludes they were cheated, and that lands on you and on them. It is not a lever we are willing to pull.
| State | What a scan says today | After you stop buying credits |
|---|---|---|
| Activated, within its count | GENUINE | GENUINE |
| Activated, count used up | SCANNED BEFORE | SCANNED BEFORE |
| Batch recalled by the brand | RECALLED | RECALLED — a recall outlives the contract |
| Never activated, or never issued | We can't verify this code | We can't verify this code — the two stay indistinguishable |
What does lapse, and when
15 days after a subscription ends, platform access stops: the dashboard, exports, new batches, message sending and reward payouts. The promise above is about the verdict a buyer sees; it is not a promise about the console.
So take the exports below before those 15 days are up. Nothing about the codes already printed changes on that day.
What you can export, and when
Any time, not only on the way out. Self-serve, not a support ticket — for everything marked available. Three are not built yet, and this page says which rather than describing a roadmap in the present tense.
| Export | What is in it | Today |
|---|---|---|
| Serial registry | Every label generated for your brand: label number, code, batch, product and the URL it encodes. | The print file. Downloadable by your partner until the batch is activated; afterwards platform-admin only and audited, because it becomes a list of live codes. Ask us and we produce it. |
| Warranty registrations | Serial, purchase date, shop, pincode, registered-on, term, expiry, masked phone. | Available today, masked and audited. |
| Rewards | A payout statement per month, and the TDS file per financial year with PANs, for your finance team. | Available today. Wallet balances and held claims are on screen, not yet a file. |
| Activation status | Per batch: its state and the date of each, the label range, the verification limit, the lot number. | On screen. No export yet. |
| Scan history | Every scan: code, batch, product, verdict, time in IST, approximate place. No raw IPs. | On the dashboard. No export yet — it needs to be a background job like the print files. |
| Fake reports | Reports against your brand: code, status, date, city and the photo. | On the dashboard. No export yet. |
What we do not have: a single “export everything” button. The full list of files is on getting your data out.
How long we keep it
These windows run daily, automatically, whether or not anyone asks. They describe a job that is already running.
| Data | What happens | When |
|---|---|---|
| A scan's IP address | Truncated to the network prefix | 30 days after the scan |
| A scan's browser string | Reduced to a family, such as "Chrome on Android" | 90 days |
| A scan's device token | Cleared | 400 days |
| The scan row itself | Kept. It is your data and it is the product, and by then it holds nothing personal. | — |
| A fake report's phone number | Erased | 90 days |
| A print file, after the batch is activated | Purged | 30 days after activation |
| A closed member's profile | Erased. The phone number stays on the financial record tax law requires. | On close |
Your own domain
Not available yet. When it is, here is the part nobody else will tell you:
A printed code carries its URL inside it. The QR on a shelf encodes https://<domain>/s/<code> and that string is ink. Changing your domain changes the batches you generate after the change. It cannot change a label already on a shelf, and any vendor who tells you otherwise is describing a redirect that they control.
So the honest version of “bring your own domain” is: your domain from this batch onwards, and our domain answering for the ones already printed, for as long as those labels exist.
If your printer changes, or stops
Your brand, your products, your batches and every code already printed belong to your brand, not to the printer's account. Changing printers means we re-point your brand to the new account. Codes on shelves are untouched, and your scan history, dashboards and warranty registrations come with you.
If the partner who prints for you lapses, your codes keep verifying and your brand may be taken over by us directly. Credits are the one thing that does not move: they were bought by the printer, from us, in their name.
If AVRA is the one that goes away
The fair version of this question is not “will you fail” — it is “what would we be left holding”. Your codes are opaque strings in a Postgres database. They are not derived from anything proprietary and there is no format only we can read. The serial registry, the batch states and the scan history are the three things another platform would need to keep your labels answering.
What we do not have today is an automatic, external copy of that in your hands. It is on the list below.
Still undecided
Listed in public on 18 Sep 2026. Each one moves up the page when it is decided.
- How long a departed brand's scan history, warranty registrations and member records are kept, and the deadline for deleting them on request.
- A brand-facing serial-registry export that works after activation and leaves the hidden codes out.
- Whether "your own domain" is built, or removed from this page.
- How a brand moves between printers: who starts it, what notice the outgoing printer gets, and what happens to credits bought for that brand.
- A quarterly registry export deposited with you, so you are never waiting on us.
Ask us anything on this page: connect@avrascan.com.
Print one batch and scan it yourself.
The fastest way to judge this is a sheet of real labels and a phone.
Trust, made visible.
connect@avrascan.com · +91 91737 47583 · Navacara Infotech, Ahmedabad, Gujarat, India