RentalCar Backups — Privacy Policy

Last updated: 29 October 2026.

Operator and scope

This policy covers the private RentalCar Backups utility operated by Idan for Poland Rent a Car at poland-rent-car.com. Contact: idan.poland@gmail.com. It describes the backup utility, not all processing performed by the rental business or Google.

Information handled

Backup archives can contain the rental system's database and private uploaded documents: customer names and contact details, rental requests, quotes, bookings, supplier information, payment or reconciliation records, and information contained in vouchers. The precise contents depend on the source records. Database copies may also contain administrator account records and password hashes; they must be treated as confidential.

For Google Drive, the utility handles OAuth authorization tokens, backup file identifiers, names, sizes, timestamps, folder identifiers and file contents needed for upload, integrity checks and recovery. It requests no Gmail, contacts or calendar data. The intended Drive permission is drive.file, covering files created or explicitly authorized for this utility; it is not intended to browse unrelated personal Drive documents.

Purpose and use

Information is used only to create, store, check, retrieve, restore and manage business backups. Google user data is not sold, used for advertising or profiling, or used to train AI or machine-learning models. RentalCar Backups' use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Storage, security and recipients

The application runs on Render. Independent copies are intended for the operator's Google Drive, with encryption performed before upload. Encryption, automated uploads and restoration are still being configured as of the date above; this policy does not claim they are already operational. Google and Render provide the storage or hosting needed for these functions under their respective service terms. The operator and expressly authorized administrators may access backup data for maintenance or recovery. Backup data is not made public through these information pages.

Authorization tokens and encryption secrets must be kept outside public source code. Access to the Google account is controlled by the account owner. A separate recoverable copy of the encryption key is needed: losing it can make encrypted backups unreadable.

Retention and deletion

No automatic independent-backup retention schedule has yet been activated. Copies remain until deleted by the operator or a configured retention rule. The operator will record the retention schedule when automation is enabled and update this policy if the described practices change. Provider-managed database recovery and disk snapshots have their own retention rules, separate from independent Drive copies.

To stop future Drive access, revoke the utility in Google Account connections and disable its backup job. Revocation does not delete existing copies. Delete the utility's archives from Drive and empty the relevant trash to request their removal there; separately remove any downloaded or restored copies. Provider retention can affect final deletion timing. Requests about personal information, access, correction or deletion can be sent to the operator at the contact address above. A deleted source record may remain in older backups until those copies expire or are deleted; restored backups must be reconciled with applicable deletion requests.

Changes and further information

This policy will be updated if the utility's data use changes. New permissions require the account owner's authorization. See the Google API Services User Data Policy, Google Privacy Policy, application description and Terms of Use.