PROVF Privacy Policy and App Purpose
This page identifies PROVF, describes its purpose, and explains how PROVF accesses, uses, stores, and protects user-selected files and related Google user data. Last updated: May 17, 2026.
1. PROVF app identity
PROVF is an application that lets users choose files, read those selected files, and save them to the PROVF platform for storage and later use by the user. PROVF does not represent itself as a Google product and does not use Google branding in its app name.
2. App purpose
Purpose of PROVF:
- Allow a user to intentionally select a file from the user's device, cloud storage, or an authorized Google account.
- Read the file selected by the user so the file can be uploaded, stored, displayed, managed, processed, or retrieved through PROVF.
- Save a copy of the selected file and related metadata on the PROVF platform under the user's account or session.
- Maintain an operational record of file upload, storage, retrieval, and deletion activity for security, reliability, and support.
PROVF only needs access to files that the user selects or authorizes. The core purpose is file reading and platform storage, not advertising, data brokerage, or unrelated profiling.
3. User consent and file selection
- PROVF acts only after the user selects a file, starts an upload, or grants account-level authorization through a supported sign-in or file picker flow.
- When Google authorization is used, PROVF requests only the permissions needed to identify the user and access the files the user chooses to provide.
- PROVF does not intentionally access, read, or copy files that the user has not selected or authorized.
- The user may decide not to provide a file. In that case, PROVF will not read or store that file.
- Any permission screen, upload screen, or file picker should clearly connect the requested access to PROVF's file storage purpose.
4. Information PROVF accesses
Depending on how the user uses PROVF, the app may access the following information:
- Selected file contents: the actual contents of files the user chooses to upload or import.
- Selected file metadata: file name, file type, MIME type, file size, source location, timestamps, and technical identifiers needed to process the file.
- Account information: basic sign-in information such as user ID, email address, and display name when needed for authentication, account association, or support.
- Usage and system data: upload status, processing status, error logs, access logs, device/browser details, and security events.
PROVF uses this information to provide the file storage service requested by the user and to keep the platform reliable and secure.
5. Google user data
Google account and file data
- If the user signs in with Google, PROVF may receive basic profile information needed for authentication and account association.
- If the user chooses a file from Google Drive or another Google-provided file source, PROVF reads the selected file and its associated metadata only for the purpose described on this page.
- PROVF stores the selected Google file content on the PROVF platform when the user chooses to upload, import, or save that file.
- PROVF does not use Google user data to serve ads, sell data, build unrelated profiles, or train unrelated machine learning models.
Scope of access
PROVF's Google data access is limited to the minimum data needed for sign-in, user-authorized file selection, file reading, and platform storage. The user remains in control of which files are selected for PROVF.
Revocation
Users can revoke Google account permissions through their Google Account security settings. Revocation may stop future imports from Google, but it does not automatically delete files already saved to PROVF unless the user also requests deletion from PROVF.
6. Use of selected files
Primary use: PROVF reads selected files so they can be saved on the PROVF platform and made available to the user inside PROVF.
Operational use: PROVF may inspect file type, file size, upload status, and technical metadata to validate uploads, prevent abuse, provide previews, restore access, troubleshoot errors, and protect the service.
Support use: PROVF may use logs and file metadata to respond to support requests. Human access to file contents should be limited to cases where the user requests support, legal compliance requires it, or security review is necessary.
7. Platform storage
When a user chooses to save a file through PROVF, the file is stored on the PROVF platform. Stored data may include the file contents, file name, file type, file size, upload time, owner or account identifier, and processing status.
Storage location: PROVF may use managed hosting, databases, object storage, backup systems, and security monitoring tools to provide the service. Stored files remain associated with the user's PROVF account or session unless deleted under the deletion process described below.
Access control: PROVF is designed so that stored files are available to the user who saved them and to authorized systems needed to operate the platform.
8. Privacy policy
This Privacy Policy applies specifically to PROVF. It explains what PROVF does with information obtained from users, including Google user data and files selected by the user.
Policy commitments
- PROVF collects and processes only the information needed to provide the file reading and storage functions requested by the user.
- PROVF discloses that selected files are read and stored on the PROVF platform.
- PROVF keeps this policy current when its data practices materially change.
- PROVF's published use of Google user data is limited to the practices described in this policy.
This page is intended to serve as the PROVF privacy policy and app purpose disclosure for users and for app verification review.
9. Sharing and disclosure
PROVF does not sell user files, Google user data, or account data. PROVF does not share selected file contents with third parties for advertising or unrelated marketing.
PROVF may share or process data only in the following limited situations:
- With service providers that host, store, secure, monitor, or operate the PROVF platform under appropriate confidentiality and security obligations.
- When the user requests an action that requires sharing, export, transfer, or support.
- When required to comply with applicable law, legal process, security obligations, or abuse prevention.
- As part of a business transfer, only if the receiving party continues to protect the data consistently with this policy.
10. Limited use commitments
PROVF's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements, where applicable.
PROVF will not
- Use Google user data for unrelated advertising.
- Sell Google user data or selected file contents.
- Use selected Google file contents for unrelated profiling.
- Read files from a Google account unless the user selected or authorized the relevant files.
PROVF may
- Read selected files to complete the upload or import requested by the user.
- Store selected files on the PROVF platform.
- Use file metadata and operational logs for reliability, security, debugging, and support.
- Comply with valid legal, safety, or security requirements.
11. User controls
Users have practical controls over how PROVF receives and stores their files:
- Choose which files to upload or import into PROVF.
- Decline to provide a file or stop an upload when the interface allows it.
- Delete files from PROVF where deletion controls are available.
- Request assistance or deletion by contacting PROVF support.
- Revoke Google permissions from the user's Google Account settings.
Some operational records may remain for security, audit, backup, legal, or abuse-prevention purposes for a limited period after a file is deleted from active storage.
12. Retention and deletion
PROVF retains selected files and related metadata for as long as needed to provide the platform storage service, maintain the user's account, comply with legal obligations, resolve disputes, prevent abuse, and keep backup or audit records.
Deletion requests: when a user deletes a file or requests deletion, PROVF will remove the file from active storage within a reasonable time unless retention is required for legal, security, or operational reasons.
Backups: copies in backups or disaster-recovery systems may remain until those backups expire or are overwritten under PROVF's normal backup cycle.
13. Security measures
PROVF uses administrative, technical, and organizational safeguards designed to protect selected files and account data. These safeguards may include encrypted transport, access controls, authentication controls, logging, monitoring, backups, and separation of production access responsibilities.
No online service can guarantee absolute security. PROVF works to reduce risk by limiting access, collecting only relevant data, and using operational controls appropriate for file storage services.
14. Legal and compliance
PROVF may retain, access, or disclose information when necessary to comply with applicable law, enforce terms, respond to lawful requests, protect users, protect the platform, or investigate suspected misuse.
Users are responsible for ensuring that they have the right to upload, import, and store the files they choose to provide to PROVF. Users should not upload files that they are not allowed to store or process through PROVF.
15. Intended users
PROVF is intended for users who can lawfully choose, upload, import, and store files through the platform. PROVF is not directed to children under the age required by applicable law for independent use of online services.
If PROVF becomes aware that it has collected information from a child in a manner that requires parental consent and such consent has not been provided, PROVF will take appropriate steps to delete or limit that information.
16. Data categories
PROVF's data categories can be summarized as follows:
| Category |
Examples |
Purpose |
| User-selected files |
Documents, images, PDFs, archives, or other files chosen by the user |
Read and store the files on the PROVF platform |
| File metadata |
Name, type, size, timestamps, source identifiers |
Upload handling, indexing, retrieval, security, and support |
| Account data |
User ID, email address, display name, authentication records |
Sign-in, account association, access control, and support |
| Operational logs |
Upload events, errors, access logs, device/browser details |
Reliability, security, debugging, and abuse prevention |
17. Processing surface
User chooses a file
PROVF reads the selected file
PROVF uploads or imports the selected file
PROVF stores the selected file on the PROVF platform
User manages, retrieves, or deletes the stored file
Any API, import process, or upload process connected to Google data should match this flow and should not request broader access than PROVF needs for the user-selected file operation.
18. User-facing notices
- The app name PROVF should be shown consistently on the home page, consent screen, support materials, and privacy policy.
- The user interface should make clear that selected files will be read and saved to the PROVF platform.
- The privacy policy should remain easy to find from the PROVF home page and from the Google OAuth consent screen configuration.
- Upload or import controls should accurately describe what will happen before the user provides a file.
- Deletion, permission revocation, and support contact options should be available where practical.
19. Policy accuracy
PROVF should keep this page aligned with actual product behavior. If PROVF changes what data it accesses, how it uses selected files, where it stores files, or how it shares data, this page should be updated before or at the time the changed practice begins.
For review purposes, the key disclosure is that PROVF reads files selected by the user and stores those files on the PROVF platform.
20. Operational commitments
- Keep PROVF's app name, logo, home page, privacy policy, and consent-screen details consistent.
- Limit requested Google scopes to those needed for user-selected file reading and storage.
- Protect stored files with appropriate access controls and operational monitoring.
- Provide a reasonable path for deletion requests and account support.
- Keep this privacy policy available to users without requiring login.
21. Risk controls
Primary privacy risks include accidental upload of unintended files, excessive authorization scope, unauthorized access to stored files, unclear retention expectations, and mismatch between policy text and product behavior.
PROVF reduces these risks by relying on user-selected files, limiting access to the stated purpose, using access controls, documenting storage and deletion practices, and keeping the policy current with the app's real behavior.
22. Summary
PROVF is a file reading and storage application. Its purpose is to let users select files, allow PROVF to read those selected files, and save them to the PROVF platform. PROVF's privacy policy discloses the access, use, storage, sharing, retention, deletion, and security practices connected to those files and related Google user data.
Appendix: contact and updates
Contact for privacy questions, deletion requests, or app review questions: pdx.error@gmail.com.
Policy updates
PROVF may update this policy when the app, storage process, Google authorization scope, or legal requirements change. The effective date at the top of this page should be updated whenever the policy materially changes.