Privacy Policy
Updated 13 October 2026
This page explains what BinBack collects during the pilot, why it is needed, and how users can ask for their information to be changed or removed.
Who is responsible
BinBack is operated by BAGGOIT LTD, the controller responsible for personal information used by this service. For privacy requests, contact [email protected] or use our Support page.
1. What we collect
When you use BinBack, we may collect your name, email address, account role, QR token, scans, bottle or can photos, reward activity, voucher activity, collection-point activity, precise or approximate location when you allow it during a return, and basic app analytics.
We also process messages and appeal notes you send, sign-in and passkey records, browser identifiers used for app analytics, and push subscription details if you enable notifications. Hosting and security services process connection information such as IP addresses and request logs. If a phone number is provided for an account or support, it is personal information too.
Photos are used as evidence for the return process. They help operators verify that the submitted container is real and help BinBack reduce fraud during the pilot.
2. Why we use it
We use this information to run the recycling reward pilot, keep your pending and confirmed balance accurate, operate collection sessions, issue rewards, investigate mistakes, improve the product catalogue, and detect suspicious activity.
3. Photos and evidence
Users may be asked to upload a live photo of the empty container. Evidence photos may be visible to authorised operators or admins when they need to verify a return, review a dispute, or check a fraud signal.
Please avoid including faces, private documents, addresses, bank cards, or unrelated personal information in container photos.
If you save a scan draft, its photo and details are stored in this browser on this device, for your account. Drafts expire after 24 hours and are removed when you submit successfully, delete the draft, or sign out. Saving a draft does not upload it or release a reward.
4. Fraud and safety checks
BinBack may use automated risk signals such as repeated barcodes, repeated photos, unusual volumes, new-account activity, and operator confirmation patterns. These checks help protect the pilot and keep rewards fair.
A flagged return may be reviewed before a reward is confirmed.
5. Rewards and vouchers
Reward and voucher history is kept so users, admins, and partner venues can confirm whether a reward has been issued, used, expired, cancelled, or rejected.
6. Who can access data
Access is limited to the user, authorised BinBack admins, operators who need to process returns, and approved partner venues where voucher validation is needed.
Our technical providers also process information needed to deliver the service: Railway hosts the application and database; Cloudflare provides website security and private object storage for evidence and encrypted backups; Resend delivers account emails when used. Your browser or phone provider delivers notifications you choose to enable.
The Android app uses Google Code Scanner. Barcode image processing is on the device, but Google documents collection of scanner usage, diagnostic information and device identifiers. See Google’s scanner data disclosure. This is separate from photos you choose to submit as return evidence.
7. Your choices
Optional browser usage analytics is off until you enable it in Privacy choices. If enabled, page and installation events use a browser identifier and may be linked to your signed-in account. You can turn it off at any time; this stops new browser usage events and removes the identifier from this device. Previously collected information can be included in a privacy request. Account, return, reward and security records needed to operate the service continue to be processed.
You can request account and personal-data deletion at /delete-account in the app or browser. Requests are processed within 30 days, with completion confirmed using your account email. We delete personal data that we are not legally required to retain and explain any retained records in the completion confirmation.
Camera access is used for barcode scanning and container photos. Location is requested while using the return flow; the app does not request background location. Native barcode scanning runs on the device. A decoded code is used in the return flow; scanner video is not uploaded by the native scanner.
Phone notifications are optional. If you enable them, BinBack stores this browser's push subscription and delivery status to send account updates through your browser provider. Lock-screen messages contain no balance, evidence photo, name or voucher code. You can turn notifications off on the Notifications page or in your phone settings.
8. Retention and backups
Account and return records are used while providing your account, verifying returns and resolving rewards or disputes. A deletion request is reviewed manually; submitting the request does not instantly erase your information. We explain any specific records that must be retained and the reason when completing your request.
Encrypted recovery backups are checked daily. Recognised backup sets older than 30 days are removed after a new backup has passed recovery checks. Failed jobs or storage errors can delay this cleanup. Deleting a live record does not immediately remove its older backup copies. Backup retention is separate from the retention of live account and accounting records.
9. Privacy requests
You can ask us to access or correct your information, erase it, restrict its use, or provide a portable copy where applicable. You can object to processing based on legitimate interests. Where processing relies on consent, you can withdraw it. Rights depend on the circumstances and applicable law.
If you are unhappy with our response, you can complain to the UK Information Commissioner’s Office.
10. Contact
For privacy questions, see the support contact details on our Support page.