1. Scope and data controller
This policy explains how CloudyDream collects, uses, stores, protects, and deletes information when providing its website, customer accounts, and cloud infrastructure services. Linking Google and authorizing Google Drive are optional and occur only after the user's action and consent.
2. Information collected outside Google
The information collected depends on the features you use. CloudyDream collects only what is needed to provide, secure, and support its services.
- Account and identity information: mobile number, phone-ownership verification result, protected national identifier, name, family name, and optional email address.
- Service and billing information: selected services, resources, orders, invoices, payments, and records required for support.
- Technical and security information: IP address, request time, session identifier, browser or device type, sign-in events, errors, and logs required for security and troubleshooting.
- Content you provide, such as support messages, SSH public keys, and data you choose to process or store through a service.
3. Google User Data and requested access
CloudyDream uses OpenID Connect scopes openid, email, and profile for sign-in and account linking, and only the https://www.googleapis.com/auth/drive.file scope for Drive features. Drive access is requested separately and incrementally and is not required to use Google sign-in.
CloudyDream cannot view, search, or enumerate your whole Google Drive. Only files you explicitly choose with Google Picker can be read or downloaded, and CloudyDream policy keeps each original file read-only.
The drive.file scope is used to read files the user explicitly selects with Google Picker and to create and manage copies or outputs that CloudyDream creates in its dedicated folder. Selecting an original does not grant write access in the CloudyDream interface: the original always remains read-only, and editing is available only on a copy created by CloudyDream at the user's request.
After the first Drive authorization, the CloudyDream backend idempotently finds or creates the dedicated CloudyDream folder, stores its actual Google folder ID for that account, and creates new outputs there by default.
- Google Login: the Google account's unique identifier (sub), verified email address, and, when provided, given and family names. This data is used to identify the Google account, securely link it to the mobile-based CloudyDream account, and support later sign-ins.
- Google Drive explicit file selection: identifiers, metadata, and content of only the selected files for reading or download, without enumerating the whole Drive or modifying or deleting an original.
- Google Drive with drive.file: creating, opening, updating, saving, and managing files created by CloudyDream or specifically made available to the app by the user; write operations are limited to these authorized files.
- Authorization data: granted scopes, authorization time, connection status, and an encrypted refresh token. A short-lived access token is used only for required Google API calls and is not stored permanently.
- Write controls: before every create, update, rename, move, or delete operation, the backend checks the account identity, recorded file grant, live Drive metadata, and parent chain. Forged IDs, manipulated parents, cross-account access, and invalid requests are rejected fail-closed.
- An authorized deletion moves the file to Trash by default; permanent deletion is not performed. Drive audit events record the account, file ID, action, timestamp, request ID, result, and destination, but never file content, access tokens, or refresh tokens.
4. How information is used
Information is used only to provide features the user can see and activate in the CloudyDream interface, authenticate the user, perform user-requested actions, maintain security, prevent abuse, provide support and billing, and comply with legal obligations.
5. Storage and retention
The Google identifier and email are retained while the Google account remains linked. The Drive refresh token is encrypted and retained only until access is revoked or the connection is deleted. The CloudyDream folder ID and file grants are retained only while Drive remains connected to enforce that account's access policy. Drive content is not turned into a permanent database or general dataset; its processing is limited to the user-requested operation unless the user explicitly asks to store an output in a CloudyDream service.
Billing, contractual, security, and technical-event records are retained only as needed to provide services, resolve disputes, prevent fraud, or meet legal obligations. When no longer needed, data is deleted or de-identified, and backup copies expire through the secure backup lifecycle.
6. Sharing and human access
CloudyDream does not sell or rent Google User Data and does not provide it to data brokers, advertising networks, or third parties for advertising, retargeting, creditworthiness, or marketing. Data is processed with Google to perform OAuth and Drive API operations and with essential infrastructure or security providers only to the minimum necessary and under confidentiality obligations.
Employees and contractors are not permitted to read Google content unless the user gives explicit, documented consent for a specific support request, access is necessary to investigate a security incident, or access is legally required. Any other transfer occurs only with user consent or where expressly required by law.
7. Google Limited Use commitment
CloudyDream'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. Google User Data is used only to provide or improve prominent, user-facing features requested by the user.
- Google User Data is not used or transferred for advertising, personalized advertising, or retargeting.
- Google User Data is not used or transferred for sale, data brokerage, creditworthiness, or lending.
- Google User Data is not used to build, train, or improve a general-purpose artificial intelligence or machine-learning model.
CloudyDream'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.
8. User controls, deletion, and revocation
At any time, the user can disconnect Google Login from the CloudyDream profile or revoke Drive access from Resources → Google Drive in the Notebook. Revoking Drive triggers an attempt to revoke the grant with Google, invalidates runtime bindings, and removes the stored refresh token, folder ID, file grants, and local connection cache. Disconnecting Google Login first performs the same Drive cleanup and does not delete the primary mobile-based CloudyDream account.
You can also remove CloudyDream directly from your Google Account connections page. To request access, correction, a copy, or deletion of Google User Data and other account data, email info@cloudydream.ir from your account email. After identity verification, deletable data will be erased; records that must be retained for legal, security, or billing purposes remain restricted and protected only for the required period.
9. Data security
CloudyDream uses HTTPS, least-privilege access controls, isolated execution environments, security logging, secret protection, and server-side encryption of refresh tokens. Tokens, passwords, and secrets are not exposed in the user interface, public logs, or source repositories. No internet system is absolutely secure; material incidents are investigated and notified as required by applicable obligations.
10. Cookies and technical data
The site uses cookies and local storage that are necessary for sign-in sessions, request-forgery protection, security, and preferences such as language and theme. Technical data is processed for operation, diagnostics, and abuse prevention and is not sold or used for behavioral advertising.
11. Policy changes and contact
If the way Google User Data is accessed or used changes, this policy will be updated before the new use begins, and fresh consent will be requested where required. The version and effective date appear at the top of this page. Send privacy questions, requests, and complaints to info@cloudydream.ir.