Redeemind stores vouchers, settings, and local display preferences only in the browser. Vouchers and settings are preferably synchronized through the browser-provided storage.sync. If sync is unavailable or the quota has been reached, Redeemind uses storage.local.

There is no Redeemind server, no analytics, no tracking, no advertising, and no network transmission of data. The browser may transfer storage.sync data to the user’s sync account in accordance with its own account settings and privacy terms. As a result, the data remains either local or in the user’s browser sync.

The data remains in the browser: in storage.local or, optionally, in the browser-provided storage.sync. Redeemind does not operate its own servers and does not use tracking. The security of browser sync depends on the respective browser account: in Chrome, on the Google account and optionally on an enabled sync passphrase; in Firefox, on the Mozilla account.

Optionally, voucher codes can be encrypted locally with a master password. PBKDF2 and AES-GCM are used for this purpose. The master password is not stored; if it is lost, the encrypted codes cannot be recovered. The “Local only” option disables browser sync and keeps the data exclusively in the local browser storage.

The content script reads the current HTTP or HTTPS page to detect the domain, checkout hints, and optional voucher field heuristics. It does not send page content to Redeemind. Only vouchers that have already been stored locally and are relevant for display are used within the extension.