WalletPass — Privacy Policy

Last updated: 18 August 2026

WalletPass converts tickets, gift cards and codes into Apple Wallet passes. This policy describes exactly what the extension does with your data. It is written to match the code, not to describe an intention.

What stays on your device

The file you drop is never uploaded. PDFs are rendered and read in the extension itself; photos and screenshots are decoded there too. The original file is never transmitted anywhere and is not stored after you close the panel.

Barcode decoding also happens entirely on your device.

What is sent, and where

To build a pass, some information has to leave your device.

To our server (Supabase, hosted in Ireland):

the fields that appear on the pass — title, issuer, date, venue, seat, and similar — as shown to you before you press Create pass
the barcode payload, because it must be embedded in the pass itself
the colours sampled from your document
the logo image, when one was found

To our server and then to Google (Gemini), to work out which fields belong on the pass:

the text layer of the document, as a list of lines
a reduced-size image of the first page

The text layer can contain your name, seat number, order reference and any other text printed on the document. The barcode payload is never sent to Google.

Google processes this under the Gemini API terms. We use a paid tier, under which Google states that submitted data is not used to train their models.

What we store, and for how long

The generated pass file is stored so your phone can download it, and is deleted 15 minutes after it is created. The download link stops working at the same time.

Alongside it we keep a short record — a random token, the storage path, the pass type, timestamps and a download count — used only to serve that link and expire it.

We also record a counter per IP address, used solely to rate limit abuse. Each counter is deleted within two hours of the period it covers, and no record of which documents an address converted is kept.

We do not create accounts, set cookies, use analytics or advertising, track you across sites, or keep the contents of your documents after your pass has been built.

Who else is involved

Supabase — hosting, database and file storage
Google (Gemini API) — document analysis, as described above
Apple — passes are signed with an Apple Pass Type ID certificate. Apple is not sent your data by us; adding a pass to Wallet happens on your device.

Permissions the extension asks for

sidePanel — to show the WalletPass interface
downloads — to save a pass to your computer when you use the AirDrop fallback instead of the QR code
host access to our Supabase project — to build and fetch your pass

The extension does not request access to the pages you browse.

Your choices

You review every field before a pass is created, and can remove any of them. If you would rather nothing was sent for analysis, enter the details manually instead of dropping a file — manual entry does not contact Google.

Contact

Questions or deletion requests: tunepawapps@gmail.com

Because passes are deleted automatically within 15 minutes, there is usually nothing left to delete by the time you would ask.