RedemptionBase
Bottle Redemption Center Management Software
Legal terms version RB-Legal-1.0 · Effective September 17, 2026

Privacy & Data Notice

Local-first by design. RedemptionBase is designed so the center's working operational database remains on the center's own device during ordinary use.

1. Operational data stored locally

Depending on the features Customer uses, local RedemptionBase data may include customer transaction counts and amounts, drop-off identifiers, account and fundraiser names, balances and history, employee names and PINs, hourly rates and time records, drawer records, sorting and pickup records, reimbursement records, settings, official registry files loaded by the Customer, and backup/recovery information.

2. What ordinary app use sends to Licensor

RedemptionBase does not automatically upload the center's transaction database, employee records, account records, sorting records, pickup records, or drawer records to Licensor during ordinary local use.

On supported devices, Customer may optionally select a folder for automatic external safety backups. RedemptionBase writes those backup files to the folder selected by Customer; it does not transmit them to Licensor. If Customer selects a folder managed by a third-party synchronization service such as OneDrive or Google Drive, that service may copy the files according to Customer's own account settings and the third party's terms.

When Customer opens the hosted app, checks for updates, downloads Software files, or visits the website, ordinary server logs may record technical information such as IP address, browser or user-agent information, requested file paths, and date/time.

3. Purchase and license records

The purchase process may collect and retain information reasonably necessary to complete the sale and maintain a license record, such as purchaser name, business or center name, email address, order/license identifier, purchase date, amount, and the legal-terms version accepted. Payment-card information may be handled by the payment processor used at checkout rather than by RedemptionBase directly.

4. Support files

If Customer sends Licensor a backup, export, screenshot, or other file for support, Licensor may temporarily possess the information in that file. Licensor will use it only as reasonably necessary for the requested support, security, troubleshooting, protection of the Software, or legal obligations. Customer should not send a full backup unless it is reasonably necessary.

5. Backup sensitivity

Full backups may contain confidential business, customer, account, and employee information, including readable employee and owner PIN information. Customer is responsible for protecting backup files and exported reports.

6. Data sale and advertising

Licensor does not sell Customer operational data to advertisers. If the website later uses analytics, payment, hosting, or support providers, those providers may process limited information needed to provide their services under their own applicable terms and privacy practices.

7. Security

Licensor uses reasonable measures appropriate to the Software and information Licensor actually possesses, but no device, browser, storage method, network, website, or transfer can be guaranteed perfectly secure. Customer is responsible for securing local devices, browser profiles, backups, credentials, and recovery information.

8. Customer control of local data

Because operational data is primarily stored locally, Customer controls normal retention, backup, export, and deletion of that data. Uninstalling the app may not by itself erase browser/site data or exported backup files.

9. Legal and security disclosures

Licensor may disclose information Licensor actually possesses when reasonably necessary to comply with law or legal process, protect rights or security, investigate fraud or abuse, or respond to a security incident.

10. Changes to this notice

If a future feature materially changes whether the center's operational database is transmitted to or centrally stored by Licensor, the change should be clearly disclosed before or when that feature is enabled.