SmartCoupon — Privacy Policy

Last updated: 5 September 2026

SmartCoupon is a tool for shopkeepers. This policy describes what the app collects, why, and how to get rid of it. It is deliberately short, because the app deliberately collects very little.

Who is responsible

SmartCoupon is operated by AxionX Digital, Ahmedabad, Gujarat, India, which is the data controller for the information described here.

Contact: softwarebelieve@gmail.com

Write to that address for any question about this policy, to request a copy of your data, or to have it deleted.

What is collected, and why

Your sign-in identifier — a phone number or an email address. Used only to sign you in and to keep you signed in. Stored by our authentication provider (Supabase). Without it there is no account.

Your shop details — name, language, country, category, and the phone number you choose to print on your cards. The name and phone number appear on the vouchers you send, because that is the point of them. The language and country decide which script and currency the app uses.

Your offers and redemptions — the offers you create, the codes issued against them, and each redemption's amount, time, outlet and staff name. This is the shop's own trading record. It is what the console shows you and what settles an argument at the counter.

Staff names you enter. So a receipt says who took the redemption. Staff do not have accounts and are not tracked.

A device identifier for your phone. On Android this is the system's ANDROID_ID, which is unique to the combination of your handset, this app and your user profile — it is not the advertising identifier and cannot be used to recognise you in any other app.

Two things use it, and nothing else does. It counts the free monthly allowance per handset rather than per login, because an email address costs nothing to invent and the free tier would otherwise be a suggestion. And it stops one person being both ends of a referral: a phone may be referred once.

It is stored against your shop and deleted with it.

Your shop's logo, if you set one. Optional, and most shops never do. The picture is uploaded so that it comes back when you reinstall the app or sign in on the shop's second phone. It is stored in a public bucket — the same picture is printed on every voucher you broadcast, so there is nothing in it to keep secret, and a private URL would only add a token that expires at the worst moment. It is deleted when you remove the logo or delete the shop.

A subscription receipt, if you subscribe. The purchase token Google Play issues, so the plan can be verified with Google and restored on a new phone. We never see a card number: the payment happens inside Google Play and the app is never told anything about it.

A notification token, only if you turn notifications on. A token issued by Google's messaging service that identifies your handset for the purpose of delivering a message to it, stored with your shop's language so the message arrives in it. It is not an advertising identifier, is not used to recognise you anywhere else, and is deleted when you turn notifications off, when Google reports the handset is gone, or when you delete your shop.

We send exactly two things: a referral reward you have earned, and a warning that an offer of yours stops working tomorrow. Nothing is marketing.

A record of when you open the app. The date you opened it on, and the time you were last seen — nothing about what you did while you were there. It answers one question we cannot otherwise answer, which is whether the product is worth coming back to. It is deleted with your shop.

If you are a customer, not a shopkeeper

Most people who meet SmartCoupon never install it. They tap a link a shop sent them on WhatsApp and get a code. This is what that collects.

A phone number, only if you type one. The field is optional and says so. Its only purpose is to give you the same code back if you open the link again, instead of issuing you a second one. It is stored against that one voucher, is visible only to the shop that issued it, and is deleted when that shop deletes its data. Leave it blank and you still get a code.

Your network address, hashed, for a few hours. To stop one machine draining a shop's offer, the page counts requests per address per offer. The address is put through a one-way hash with the offer's identity and only the result is stored, so the table holds a counter under a key nobody can read back to an address. Rows older than two hours are deleted on a schedule.

Counts, with nothing in them about you. How many people opened an offer and how many claimed it, per day, per offer. There is no visitor identity of any kind — no cookie, no device identifier, no fingerprint — and no timestamp finer than the day, so a single person is not a row in it and cannot be reconstructed from it.

Nothing else. No account, no tracking, no advertising, and no third-party script of any kind on that page.

What is not collected

Analytics and crash reporting

The app uses Google Firebase Analytics and Crashlytics, and only for understanding whether the product works: how far a new shop gets in setup, which offer types are used, and — most of all — which of the redemption verdicts cashiers actually hit, because that tells us which wording confuses people at a counter.

What is sent is deliberately narrow:

What is never sent: your shop name, your phone number, your address, staff names, voucher codes, customer phone numbers, or any photograph. This is enforced in code by an allow-list of permitted parameters and covered by an automated test, not by convention.

Crashlytics receives stack traces when the app fails, so the failure can be fixed. Those contain no shop or customer data.

If Firebase is not configured for a given build, none of this runs at all.

Permissions

Camera — used only to scan a voucher's QR code at your counter. Nothing is recorded or uploaded; the camera is read to find a code and closed. The permission is optional: a shop can type codes by hand and never grant it.

Notifications — asked for only at the moment you switch notifications on in Settings, never on first launch, and never as a condition of using anything. Refusing costs you nothing else in the app. You can switch them off again in Settings, or in your phone's own settings, and both work.

Where the data lives

In a Supabase project (PostgreSQL) operated by the controller named above. Access is restricted by row-level security so a shop can read only its own rows. Traffic is encrypted in transit.

How long it is kept

For as long as the shop exists, and then for up to 30 days after you delete it — see below.

Deleting your data

In the app: Settings → Delete my shop.

Two things happen, at different speeds, and both are deliberate:

That 30-day window exists so a shop deleted by mistake can be restored on request, and so a dispute or a report of abuse raised just before deletion can still be investigated. During it the records are not used for anything else and are not visible in any app. After it, they are gone and cannot be recovered by us or by you.

If you want the records destroyed sooner than 30 days, email the contact address above and say so; we will action it and confirm.

To request deletion without using the app, email the contact address from the address the account uses. Requests are actioned within 30 days.

Children

The app is for business use and is not directed at children.

Changes

Material changes will be noted here with a new date at the top.