Privacy Policy

1. Data processed

When an authorized backup runs, the utility reads the configured PREVISION PostgreSQL database and associated media from Supabase Storage. A backup may contain screenplay text, shots, preparation notes, media, account and project-access records, database structure, and identifiers linking these records.

The utility also processes backup generation identifiers, timestamps, sizes, checksums, verification results, and the file and folder identifiers required to manage its Google Drive copies. These are used for backup, integrity verification and recovery.

2. Local processing and encryption

Restic encrypts backup contents locally before an archive is transferred to Google Drive. The designated external destination is an encrypted drive. Recovery metadata accompanying the archive, such as its identifier, size, checksum and recovery instructions, is not itself encrypted and contains no backup passphrase or authentication token.

Local working files are different from encrypted archives. Database exports, downloaded media, a reusable media cache and decrypted verification files can exist in readable form on the Mac during processing. Working directories and credential files use restricted local permissions. The application does not itself encrypt every working file or promise secure erasure.

Temporary staging and verification directories are removed on normal completion. A crash or interruption can leave working files. Media caches, reports, interrupted generations and backup archives can remain for reuse or recovery. There is no automatic deletion of historical backup generations and no fixed retention period is promised.

3. Google authorization and Drive files

The desktop utility requests only the Google Drive OAuth scope https://www.googleapis.com/auth/drive.file. It can create and access application-managed backup files and folders, and files explicitly authorized for this application. It does not request permission to browse or manage all files in your Google Drive.

With this permission, the utility can upload encrypted archives and non-secret recovery metadata, read file metadata, and download its backup files for independent integrity checks and decryption on the Mac. Access is limited by Google authorization and by the configured backup destination.

The qualified transfer workflow does not synchronize, purge or automatically delete existing Drive backup generations. Copies are verified using hashes and independent readback. The current native test build keeps real backup execution disabled until its production prerequisites are qualified.

4. Authentication tokens and secrets

Google sign-in and consent take place through Google. The utility uses OAuth access and refresh tokens through rclone. Its local configuration file contains these tokens and the OAuth client configuration, and is stored separately from the application bundle and source repository, with permissions restricted to the local account.

This file is not protected by an application-managed encrypted credential vault. Protection also depends on the Mac account, device security and disk encryption. Backup passphrase material and database or Storage credentials are held in separate restricted local files. They are not included in the Google Drive backup package or displayed on this website.

Operational reports record stages, counts, identifiers, checksums and sanitized failure codes. They are designed to avoid recording tokens, passphrases or preparation content.

5. Service providers and sharing

The configured Supabase service supplies the source database and media. Google receives OAuth requests and the encrypted files and associated recovery metadata uploaded to the selected Drive account. Google processes that information under its own terms and privacy policy.

PREVISION Backup does not sell preparation data or Google user data, use it for advertising, or provide it to collaborators through a backup service. Backup data is used for the owner's backup, verification and recovery operations. The utility has no public registration service or operator-hosted backup account.

This information website is prepared for hosting on Cloudflare Pages. Once published, Cloudflare will process the network requests needed to serve it, which can include IP addresses and request metadata under its own policies. These pages contain no analytics scripts, advertising tools, tracking pixels, forms, cookies or external fonts.

6. Revocation, removal and retention

You can revoke Google access in your Google Account's third-party connections by selecting the authorization used by PREVISION Backup. Revocation prevents future authorized Drive operations after the change takes effect; it does not delete files already saved on Google Drive, the Mac or the external drive.

Backup copies and local credential files remain under the owner's control. Removing authorization, removing local credentials, and deleting backup files are separate actions. Historical generations are not automatically removed when authorization expires or is revoked.

For questions or a request concerning data handled by the utility, contact Koya Kamura at koyakamura@gmail.com. Do not send passwords, tokens or backup passphrases by email.

7. Changes and contact

This policy will be updated when the utility's data handling changes. The date at the top identifies this version.

Maintainer: Koya Kamura
Contact: koyakamura@gmail.com