Privacy policy

1. Operator and contact

EvidenceReview is a personal-use application operated privately, not a publicly available data-processing service. Questions about this policy, data handling or removal of locally stored information can be sent to [email protected].

2. Google data accessed

With account-holder consent, EvidenceReview uses the Google Drive API permission https://www.googleapis.com/auth/drive.readonly (view and download files). The permission can permit access to all files in the authorised account, but the application is operated with bounded source selection and acquisition controls.

Depending on the specific authorised task, the application may obtain account identifiers (including the email address and a Google Drive account/permission identifier); selected file IDs, names, locations, types, sizes, timestamps, versions and available checksums; and the bytes of expressly selected files. It also records technical timestamps, integrity results and provenance needed to document acquisition.

The current Google integration does not request Google Drive write or delete permissions, Gmail mailbox access or Google Photos access.

3. Purposes and use

This data is used to confirm the authorised Google account; identify and select relevant source files; download and preserve selected copies; verify data integrity; and maintain locally controlled source, acquisition and audit records. The app does not use Google user data for advertising, profiling for advertisers or resale.

Use of information received from Google APIs is intended to adhere to the Google API Services User Data Policy, including its Limited Use requirements. Google user data is not used to develop or train general-purpose artificial-intelligence or machine-learning models.

4. Storage and security

Downloaded files, selected metadata and acquisition records are retained in the operator's controlled local Windows environment. Google OAuth credentials are managed separately from evidence files; account refresh credentials are stored using the current-user Windows credential mechanism. Access to Google's API uses encrypted HTTPS connections, and local preservation includes integrity and no-overwrite checks.

This public website does not receive Google OAuth tokens, host private Drive files or provide access to the local preserved file collection.

5. Sharing and external processing

Google user data is not sold, published on this website or shared with advertisers. Downloading a file does not by itself send it to an external AI service or third-party reviewer. Any separately authorised onward processing or disclosure, for example to an instructed professional adviser or an approved processing service, must be limited to the applicable purpose and lawful instructions, with appropriate safeguards and applicable Google data-use restrictions. This is not a blanket permission to share Google data.

6. Retention, revocation and deletion

Locally preserved materials and provenance records may be kept for as long as required for the operator's legitimate review, preservation and record-keeping purposes, subject to applicable legal restrictions. They are not automatically deleted when the Google OAuth permission expires or is revoked.

An account holder can revoke future Google Drive access through their Google Account's third-party connections settings. For enquiries about retained local copies or deletion, contact [email protected]. Removal requests will be assessed against applicable preservation and legal obligations.

7. This website

The informational pages at bunneyhub.co.uk contain no account-registration forms, file-upload functionality, advertising scripts or optional visitor analytics installed by the site operator. The hosting provider, Cloudflare, may process ordinary technical request and security information needed to deliver and protect the website, under its own applicable terms and privacy practices.

8. Policy updates

Material changes to the application's access, data uses or third-party sharing arrangements will require an appropriate update to this public policy before the changed practice is relied on. The effective date above identifies this version.