Privacy Policy

Your data, by design

Last updated: 1 November 2026

i-Saves is built so that the platform can prove you qualify without ever learning who you are. This policy explains what verification touches, what leaves your device, and what is mathematically impossible for us to do with your data.

01Verification, not profiling

When you verify as a government servant or an enrolled student, i-Saves resolves your status against a ministry HR directory or campus SSO. The result stored is a pass/fail credential — your segment and tier — not your employment record or academic transcript. Merchants at the till receive only a yes/no token proving eligibility; they never see your name, ID number or history.

02What the Saves Pass holds

The Saves Pass carries your verified segment, a tier, and an expiry tied to your employment or enrolment. Its payment QR rotates on a short interval so a captured code cannot be replayed. The pass is designed to survive a phone change and to lapse automatically when your eligibility ends, so benefits never leak outside the group.

03Aggregates are de-identified by schema

The Aggregate Exchange publishes cohort-level demand signals — indices, elasticity bands, campaign-readiness scores. These are computed with k-anonymity floors (a minimum cohort size) and differential-privacy noise, and the output format contains a pii: null field by schema. We do not export, sell or make purchasable any individual profile, because the data we publish does not describe individuals.

04Consent and opt-out

Contributing to aggregates is optional. You can inspect which aggregates exist about your cohort and switch off contribution at any time. Turning it off never affects your ability to verify, pay, or receive segment discounts.

05Payments and settlement

iWallet transactions settle over national rails (DuitNow QR & ID, card networks and payroll deduction where your agency participates). Payment records required for settlement, anti-fraud and legal obligations are retained only as long as those obligations require, and are separated from the verification credential wherever the architecture allows.

06Pilot confidentiality

During private beta, participating ministries and campuses are named only with their consent. Aggregate pilot metrics are reported without identifying any individual member or any partner institution that has not agreed to be named.

07Contact and your rights

To exercise access, correction or deletion rights, or to ask how any field above is implemented, write to i-saves@antrex.app or use the Antrex contact desk at antrex.app/contact.