BULMAX ZIP STORAGE
Privacy policy
Effective date: October 4, 2026
Bulmax Zip Storage is a personal research utility operated by YNSScarSaiyan. It connects the owner’s Google Drive to the Bulmax Zip corpus and checkpoint pipeline. Questions and deletion requests can be sent to ynsscarsaiyan@gmail.com.
What the application accesses
The Google Drive permission used is drive.file: files and folders created by the application, or files explicitly opened or selected for it. The utility reads and writes owner-selected prepared corpus blocks, manifests, checkpoint state and recovery metadata. File names, identifiers, sizes and hashes are used to locate and verify those objects. It does not request Gmail, contacts, calendars, payment information, or unrestricted access to unrelated personal Drive files.
How the data is used
Prepared corpus files supply the owner’s Bulmax Zip model-training runs. Checkpoint files store and restore the learner’s state. Manifests, hashes and cursors verify transfers, identify prepared releases and prevent incorrect restarts. Corpus material collected from public dataset sources remains subject to those sources’ licenses and preparation rules.
Google account/profile information, OAuth tokens and unrelated personal Drive documents are not training examples. The utility does not scan the owner’s other Drive content. Data is not used for advertising, credit decisions or sale to data brokers.
Where data and credentials are stored
Corpus and checkpoint objects reside in the owner’s selected Google Drive folders. The trainer uses bounded memory buffers for corpus input rather than a local corpus cache. Local checkpoint files and recovery metadata reside in the owner’s isolated production folder.
OAuth credentials are held in the owner’s rclone configuration, outside the project source and public website. They are used to authenticate authorized Drive requests and are excluded from normal diagnostics. An owner-authorized remote preparation worker may process corpus data and upload it to Drive; worker access must be deliberately configured by the owner.
Transfers and public checkpoints
Google processes files stored in Drive. Cloudflare hosts this informational website. Files are transferred to the owner’s selected trainer or authorized preparation worker when needed for the requested workflow. The utility does not make Drive files public by default.
The project also supports an independently selected public Hugging Face checkpoint repository. Uploading there makes those checkpoint files public. It is a separate destination from Drive; the Drive transport does not automatically publish corpus files or credentials there.
Retention and deletion
The checkpoint retention tool keeps the newest two complete local checkpoints and five complete Drive checkpoints per run, plus snapshots pinned for active recovery. Older local checkpoints are eligible for removal only after matching remote verification. Interrupted uploads and recovery pins may retain additional files. Corpus files remain until the owner deletes them or selects a separate retention policy.
The owner can delete application files in Drive and remove local configuration and checkpoints. Access can be revoked through Google Account connections. Revocation stops new authenticated access; it does not itself delete previously stored files or copies.
This website
This static site has no account form, application database, advertising scripts or site analytics added by the operator. Cloudflare may process standard request information, such as IP addresses and security logs, to deliver and protect the site under its privacy policy.
Changes and contact
Material changes to access, use or destinations will be reflected in this policy. Contact ynsscarsaiyan@gmail.com with questions about the utility or its data handling.