We use Sentry to diagnose failures and improve reliability. Reports can include an internal account identifier, app and operating-system versions, device information, operation identifiers, error stacks and workflow timings. We exclude receipt images, packing videos, authentication credentials, verification codes and email bodies from these reports. For the mobile app, limited, masked session replay may be used in preview testing; camera and sign-in surfaces are excluded. On our website, masked session replay can also help diagnose interface errors. Contact hello@biteback.ai with questions about these diagnostics.
We advertise Biteback on Meta (Facebook and Instagram). We do not show any advertising in our apps or on our website, and we do not sell your information. To learn which of our campaigns work, we measure conversions in three ways. None of them uses your device's advertising identifier, and we never ask the apps to track you across other companies' apps or websites.
Account conversions sent from our servers. When an account is created or becomes active (its first order with evidence within 7 days of sign-up), our servers send that event to Meta through Meta's Conversions API. This happens whether you signed up on the website or in an app. We send the event name, its time and a hashed (SHA-256) account identifier. We do not send your name, email address, phone number, order details, receipts or videos. When the event comes from our website, we may also include the browser details Meta uses to match it to a visit from one of our ads, such as your browser's user agent and Meta's cookie identifiers. Meta uses this information to report on and improve the delivery of our campaigns. Our legal basis is our legitimate interest in measuring our marketing. Internal, test and app-review accounts are never sent.
iPhone and iPad installs. Our iOS app uses Apple's SKAdNetwork and AdAttributionKit. If you install the app after seeing one of our ads, Apple sends Meta, and a copy to us, an anonymous report of the campaign and a coarse progress value: whether an account was created, a first order was recorded, evidence was uploaded, or the account became active. These reports contain no information that identifies you or your device, and Apple delays and limits them to protect your privacy.
Android installs. When our Android app first opens, it reads the referral information Google Play recorded for the install. If you installed the app from one of our Meta ads, this includes Meta's campaign details. After you sign in, we store this with your account so we can tell which campaigns bring new accounts. We do not send it to Meta.
How to opt out. To stop us sending your account's conversions to Meta, sign in at biteback.ai/dashboard/privacy and choose Stop sharing with Meta. Your choice applies to your account on every device, including the apps, and also stops anything not yet sent. You can change it at any time on the same page, or email privacy-policy@biteback.ai and we will do it for you. Opting out does not affect how Biteback works for you.
On our website, the Meta Pixel loads only if you accept it in the privacy banner.