Detailed privacy terms for a user-directed cleanup utility.
This Privacy Policy explains how Tidy Cloud collects, receives, stores, uses, protects, and discloses information when you use the service. Tidy Cloud is a utility product designed to help you review and clean up your own connected accounts. It is not an advertising or data-resale business, but it does store operational data required to run the service.
Last updated: April 1, 2026
1. Scope of this policy
This policy applies to Tidy Cloud's website, application interface, connected-service cleanup features, recurring cleanup features, public support paths, and related operational infrastructure. It covers information collected directly from you, through your use of the service, and from third-party services you connect.
2. What Tidy Cloud is and is not
Tidy Cloud is a cleanup utility. It is intended to help you filter, preview, review, organize, and perform user-directed actions in services such as Gmail and Google Drive. It is not intended to act as a data broker, advertising network, mailbox intelligence provider, or generalized training pipeline for unrelated machine-learning systems.
3. Information you provide directly
Depending on how you use the service, you may directly provide or confirm information such as your name, email address, legal acceptance, support or donation interactions, recipe names, cleanup rule settings, schedule settings, and account preferences.
4. Information we receive from connected accounts
When you connect a Google account or another supported service, Tidy Cloud may receive account-related and content-related data permitted by the scopes or permissions you approve. This may include account identifiers, mailbox counts, message preview data, labels, snippets, sender information, message metadata, file names, file sizes, storage totals, modified dates, owner information, and other metadata needed to render summaries, previews, and cleanup actions.
5. OAuth tokens, sessions, and access credentials
Tidy Cloud stores operational authentication data required to keep your account connected and functional. This may include access tokens, refresh tokens, token expiry values, OAuth provider account identifiers, scopes, session records, and related authentication state. These records are used to authenticate requests, refresh expired access, and perform the cleanup actions you ask the service to run.
Tidy Cloud is designed to retain these credentials only for service operation and not for unrelated commercial use.
6. Other operational data we store
Tidy Cloud may store operational product data including cleanup history, selected message or file identifiers for reversible actions, saved recipes, recurring schedules, feature entitlements, error states, support-related state, legal acceptance timestamps and versions, and system records needed to keep the service consistent and recoverable.
7. How we use information
Tidy Cloud may use information to:
- authenticate users and maintain active sessions;
- connect to third-party services you authorize;
- show summaries, counts, previews, filters, and review flows;
- perform actions you explicitly instruct the service to perform;
- save recipes, recurring schedules, and cleanup history;
- refresh expired access where refresh tokens allow it;
- monitor reliability, security, abuse, and operational health;
- process voluntary support or donation payments through payment providers; and
- measure general site or product usage where analytics are enabled.
8. Google user data limitations
Tidy Cloud is intended to use Google user data only to provide and improve the user-facing cleanup features you request. Tidy Cloud is not intended to use Google user data for advertising, resale, data brokerage, profile enrichment, or unrelated commercial exploitation.
Tidy Cloud is also not intended to use data received from Google Workspace APIs to develop, improve, or train generalized artificial intelligence or machine learning models for unrelated purposes.
9. Analytics, logs, and diagnostics
Tidy Cloud may use analytics, logs, and diagnostics to understand traffic, detect failures, troubleshoot issues, improve stability, and protect the service. These tools may collect technical information such as page visits, session behavior, request timing, environment metadata, and coarse product interaction data. They are not intended to be used to resell or commercially mine your connected content.
10. Payment and donation processors
If support payments or donations are enabled, payment information is typically processed by a third-party payment processor such as Stripe. Tidy Cloud may receive limited transaction-related information needed to confirm or reconcile support activity, but payment card information is generally handled under the payment processor's own systems and policies.
11. How cleanup actions relate to your data
Tidy Cloud is designed to execute user-directed utility actions such as moving content to Trash, applying labels, archiving messages, or performing comparable organizational actions in connected services. The service is not designed to independently decide what to delete. The user remains responsible for the instructions given to the product.
12. Trash, restore, retention, and provider-side behavior
Where supported, Tidy Cloud generally sends content to Trash rather than permanently deleting it immediately. However, restoration windows, permanent deletion timing, retention behavior, storage calculations, and provider-side recovery rules are controlled by the connected service and its own terms and technical systems. Tidy Cloud does not control those third-party policies.
13. Sharing and disclosure
Tidy Cloud may share or expose information only in the limited circumstances necessary to operate the service, comply with law, protect rights, detect abuse, process payments, host infrastructure, maintain databases, provide analytics, or support connected service operations. Tidy Cloud is not intended to sell your connected data to data brokers or advertisers.
14. Third-party providers and subprocessors
Tidy Cloud depends on third-party services such as hosting providers, database providers, analytics providers, payment processors, authentication providers, and connected platform APIs. Those providers may process data on Tidy Cloud's behalf or as independent controllers under their own terms and privacy practices.
15. Data retention and deletion timing
Tidy Cloud may retain operational records for as long as reasonably needed to maintain service continuity, preserve cleanup history, support recurring schedules, investigate failures or abuse, meet legal obligations, or protect the service. Tidy Cloud may not yet provide a complete self-serve deletion workflow for every stored record.
16. Security measures and limitations
Tidy Cloud is intended to use reasonable administrative, organizational, and technical safeguards to protect credentials, sessions, stored operational data, and connected account access. No online system can guarantee absolute security, and you understand that internet transmission, cloud storage, and third-party services involve residual risk.
17. International transfers
Your information may be stored or processed in countries other than the one in which you live, depending on the service infrastructure and providers used by Tidy Cloud.
18. Children and minors
Tidy Cloud is not directed to children under 13 and should not be used by anyone who is not legally authorized to use the service and consent to the applicable terms in their jurisdiction.
19. Your choices and controls
You control whether to connect accounts, which scopes to approve, what cleanup rules to create, whether to schedule recurring actions, whether to provide support payments, and whether to revoke connected-service access from the provider side. You may revoke Tidy Cloud's Google access through your Google account permissions.
20. Changes to this policy
Tidy Cloud may update this Privacy Policy from time to time. If the product's data access, storage, analytics, token handling, payment handling, or service model materially changes, the revised policy should reflect those changes.