Privacy Policy

Compress.My is operated by FileMesh, 1178 Broadway, New York, NY 10001. It estimates potentially eligible Google Drive candidate data and, only after you approve a run, processes supported files. This policy explains the information the service needs and avoids absolute promises about security or deletion.

Information we process

• Your Google account name, email address, authorization tokens, and service-session information.
• The pre-run estimate reads Google storage quota and limited Drive metadata: file size, extension, and whether a file is owned, shared, trashed, and editable. It does not request file names, identifiers, or folder paths.
• After you start a run, the service also uses the identifiers, names, and folder relationships needed to process and report on files included automatically in the authorized run, up to the allowance you selected.
• File content only after you start a compression run, so the service can download, process, validate, and upload supported files.
• Operational records such as job progress, errors, security logs, support messages, and basic product analytics.
• Checkout and payment status from our payment provider. Compress.My does not receive your full card number.

How we use information

We use this information to authenticate you, estimate potentially eligible candidate data, apply the allowance you selected, run requested compression jobs, verify payment before a paid run starts, show results, prevent abuse, diagnose failures, and provide support.

Why Google requests full Drive access

Google's full Drive permission is required because an approved run must read each included file and update that same Drive file in place after validating that the compressed output is readable and smaller. Before you approve a run, the estimate uses storage quota and limited file metadata rather than file content. File content is accessed only after you start a run. You can revoke access at any time in your Google account settings.

Google API Limited Use

Compress.My's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

File processing and retention

The initial estimate is based on quota and limited Drive metadata. If that scan reaches its time limit, the interface labels the result as a fallback based on total Drive usage. A compression run requires temporary access to file content and may use isolated temporary working storage, which is cleaned after processing. Unsupported files are skipped. Account records, file metadata, job state, payment references, and diagnostic logs may be retained when needed to operate, secure, and support the service. For a current retention period or a deletion request, contact FileMesh support.

Service providers and international processing

Data may be handled by Google, cloud infrastructure, payment, monitoring, and analytics providers that help us operate Compress.My. Processing may occur outside your country under the safeguards available from those providers and applicable law.

Checkout is provided by Polar, which acts as merchant of record for paid purchases and handles card data, sales tax or VAT, receipts, and payment and refund processing. Compress.My receives purchase status and transaction references rather than your full card number.

Security

We use transport encryption and technical access controls intended to protect data. No online service can promise perfect security. If you believe your account or data is at risk, revoke Compress.My access in your Google account and contact us.

Your choices

You can stop before starting a run, revoke Google access from your Google account settings, clear your local browser session by signing out, and request access to or deletion of personal data where applicable.

Analytics and browser storage

Compress.My uses essential browser storage for session, checkout-return, and wizard state. Google Analytics is disabled unless you choose “Allow analytics” in the on-site analytics settings. If enabled, Google Analytics may process page and product events, a browser client identifier, session information, approximate location, and browser or device information. You can reopen Analytics settings to withdraw that choice; essential storage remains necessary for sign-in and checkout return flows.

Changes and contact

We may update this policy and will change the effective date above. For privacy questions, access requests, or deletion requests, contact FileMesh support at support@filemesh.io.