Burn privacy policy

Effective date: April 13, 2026. This policy covers the Burn Android app and pay.burner.tel.

Burn is designed so that core use does not require traditional personal identity information. The Burn code is intended to be the main account reference, the website is not built around tracking, and Geo-Burn is designed to evaluate locally on-device rather than share your live location.

This policy applies to the Burn Android app and the related web experience hosted at pay.burner.tel, including voucher checkout and payment confirmation pages.

If a store listing, website, or in-app screen links to this page, this is the privacy policy that applies to that Burn experience unless a more specific notice is shown there.

Burn is designed so that normal use does not require your real name, email address, phone number, home address, or other traditional personal identity information.

The main account reference Burn uses is the 16-character Burn code. Subscription, voucher, recovery, and related account operations are designed to be tied primarily to that Burn code or derived account references rather than to your real-world identity.

On pay.burner.tel, Burn processes the minimum checkout data needed to create and confirm payment, issue vouchers, and show your voucher after payment. This can include invoice identifiers, voucher fulfillment records, payment status, and short-lived browser session identifiers during checkout.

Burn does not require personal identity details for normal app use, and the website is not designed around ad-tech, marketing profiles, or cross-site tracking.

Contacts access is used only for contact backup, restore, and sync features that you choose to enable. Burn is designed so contacts backups are stored in encrypted form rather than as readable plain contact data.

Location access is used only for location-based protection features such as geo-burn or geo-monitoring when those features are enabled. Geo-Burn uses the device's local location services and evaluates those rules on-device rather than sharing your live location with Burn or anyone else for that feature.

Camera access is used for QR scanning flows such as device linking. NFC access is used for supported recovery and device-authentication flows. Phone-state access is used for supported SIM-removal protection logic on compatible builds and devices.

Burn's website and checkout flow are not built around third-party analytics profiles, ad pixels, or cross-site tracking.

Short-lived browser storage or session identifiers may be used only to complete the active checkout flow, recover the voucher after payment, and protect against duplicate or broken fulfillment states.

We use information to operate the app and site, protect your device, enable the features you turn on, issue and redeem vouchers, confirm payments, sync eligible account state, provide customer support, prevent abuse, and diagnose service problems.

We do not sell personal information. We use data to provide and secure Burn, not to build a marketing or data-broker profile about you.

Burn uses service providers and infrastructure needed to operate the product. Depending on the feature, this can include backend hosting and database providers, realtime and messaging infrastructure, payment processors and payment infrastructure, app-distribution services, and web hosting providers.

We share information with those providers only as needed to operate the requested feature. For example, payment-related information is shared with payment infrastructure to create and confirm invoices, and support messages are processed through the support backend used by Burn.

If you choose an anonymous or pseudonymous payment method such as cryptocurrency, Burn is designed so checkout can be completed without asking you for traditional personal identity details. If you choose a card payment flow, payment information may be processed by the payment provider you use for that transaction.

We may also disclose information when required by law, to enforce our terms, or when reasonably necessary to investigate fraud, abuse, security incidents, or threats to users or the service.

Burn stores some data locally on your device so the app can function, including settings and feature state. Some service-side records may also be stored when needed for syncing, recovery, subscriptions, support, or voucher fulfillment, with the Burn code serving as the primary account reference.

Where Burn is designed to use encryption for sensitive flows, such as protected recovery material or contacts backup flows, it attempts to keep that information encrypted in transit and at rest according to the implemented feature design.

Contacts backups and related recovery material are designed so that restoration requires secrets associated with you, such as your Burn code together with recovery credentials like a PIN, device credential, or other recovery factors depending on the backup format. Burn is not intended to hold a plain readable copy that can simply be handed over as ordinary contact data.

We retain information for as long as needed to provide the feature you use, maintain security, resolve disputes, prevent abuse, and satisfy legal, tax, accounting, or operational requirements. Temporary browser-side identifiers used during checkout are intended only to complete the active purchase flow.

For normal use, Burn does not require you to create an account with your real name, email address, home address, or phone number.

Burn is designed so that the main server-side account reference is the Burn code. Outside of payment records created when a user chooses a card-based payment flow, Burn aims not to require personal identity information in order to use the core product.

If a lawful request is made for user information, the information Burn expects to have available is generally limited to service records tied to the Burn code and any transaction data generated by the payment method a user chose.

You can choose which optional features to enable, and many sensitive features only operate when you actively configure or turn them on. You can also deny or revoke app permissions through Android settings, subject to the feature impact that causes.

You may uninstall the app, stop using pay.burner.tel, and discontinue optional sync or support interactions at any time. If you need help with purchase records, support history, or other service-side data requests, contact Burn through the official support channel.

Burn is not directed to children under 13, and we do not intend to knowingly collect personal information from children under 13 through the app or checkout site.

Depending on the services used to operate Burn, your information may be processed in countries other than your own. Where that happens, we rely on the safeguards built into the service providers and operational setup we use.

We may update this policy from time to time. The version published at /privacy is the current version. Material changes will be reflected by updating the effective date on this page.