Privacy Policy

Effective and last updated: 20 October 2026

This policy explains how Cloudmeter — AI Auto Trading handles information through the website cloudmeter.in and its Android app, package in.cloudmeter.andriod. It covers the closed-testing experience and the separate administrator trading console.

1. Who is responsible and how to contact us

Cloudmeter operates the AI Auto Trading service described here. For privacy questions, access or correction requests, and deletion requests, contact the app operator at mail2ganesh.cse@gmail.com. Include “Cloudmeter privacy request” in the subject. Do not send broker passwords, API secrets, access tokens, TOTP codes, or sensitive trading documents by email.

2. Information we handle

Sign-in and service security

We process the username and password entered to authenticate an account. The server stores salted password hashes rather than plaintext app passwords. It maintains a signed session cookie and server-side session information, including a browser/user-agent fingerprint, expiry and anti-forgery token. IP addresses, request times, browser/user-agent information, login failures and technical errors may be processed in server/security logs and login throttling.

Broker connections and financial information — administrator access

When the administrator connects an authorised broker account, the service processes the broker identifiers and credentials needed for that connection, authentication/request tokens and a one-time authentication code where required. Broker/API secrets are held in private server configuration, not embedded in the Android app. Zerodha access tokens may be saved in a restricted server file to restore an unexpired historical-data session; saving a token does not extend the broker’s expiry.

The administrator console may retrieve broker profile details, usable balance, margins, holdings, positions, orders, executions and profit/loss information. Trading preferences, confirmed fills, performance snapshots, position-management records and decision observations may be saved on the server to operate and audit the configured service. These private account functions are not available to read-only testers.

Market research, app use and notifications

The service retrieves and saves market prices, index candles, instrument information, public news context and research observations. If the administrator enables trade email alerts, the notification system processes the configured recipient email address and order details such as instrument, side, quantity, buy/sell price, reason and profit/loss where available. Read-only testers cannot enable or trigger these alerts.

If you contact support, we receive the email address and information you choose to provide. The current app does not provide public account registration; tester access is provisioned by the operator.

3. Why we use information

• Authenticate users, enforce administrator/tester permissions, prevent abuse and keep sessions secure.
• Display requested market history and research, and provide authorised account and performance views.
• Maintain broker connections and, only for an authorised administrator using enabled trading controls, operate configured orders and exit management.
• Maintain records for troubleshooting, reconciliation and strategy research, and deliver configured notifications.
• Respond to support, privacy and deletion requests.

Research archives contain observations and rule-based comparisons. They are not a promise of profit or evidence that a live-trained model controls orders.

4. Cookies, Android permissions and tracking

The website and Android WebView use an essential first-party session cookie. The WebView permits first-party cookies and website storage so the authenticated website can function; third-party cookies are disabled. The current Android app requests internet access. It does not request access to contacts, SMS, camera, microphone or GPS/precise location. Network IP addresses may still be processed for service operation and security.

The current Android build contains no advertising or third-party analytics SDK, and Cloudmeter does not use an advertising identifier or sell personal information. Broker login pages opened in your external browser are governed by that browser’s cookie settings and the broker’s policy.

5. Service providers and sharing

Information is shared only as needed to provide the functions described here, with the administrator’s configured providers, or when disclosure is required by applicable law:

• Google Cloud: hosts the application server and operational data.
• Angel One and Zerodha: receive the authentication and API requests needed for the broker services the administrator connects. Angel One can receive authorised order requests; the current Zerodha integration supplies historical/market data.
• Configured email services, including Gmail relay: process the administrator’s notification recipients and email contents when alerts are enabled.
• Google Play, Android and your browser: distribute/run the app and may process installation, device, security or diagnostic information under their own policies.
• Market/news providers: receive requests for public market/news information and necessary network metadata. Tester app passwords are not included in those requests.

Authorised operators can access server records to maintain and support the service. We do not make personal brokerage information public or give community testers access to it. External providers apply their own policies, retention and account controls. Processing locations depend on the hosting and providers used and may be outside your country.

6. Storage, security and retention

Connections to Cloudmeter use HTTPS. App passwords are hashed, session cookies are HTTP-only, and sensitive server credential files have restricted access permissions. These controls reduce risk but do not make any service immune to unauthorised access. Do not share an administrator login with testers.

• App sessions expire after the configured session lifetime (currently up to eight hours); signing out invalidates that session. Removing or rotating the tester credential file invalidates existing tester sessions.
• Broker session validity is controlled by the broker. Saved historical-data tokens can be restored only while valid and are invalidated/removed when rejected or expired.
• The index archive retains approximately 90 days of saved candles. Detailed decision/research observations are generally kept for 30 days, with daily summaries retained for 90 days; these cleanup windows apply when the relevant collection/cleanup runs.
• Trading, performance, position-management, notification records and operational logs do not currently all have a scheduled automatic deletion period. They remain until operational cleanup or an approved deletion request removes them, subject to any applicable retention needs.
• Copies in backups or delivered email may remain separately until those copies are removed or replaced. Broker, Google Play and other provider records have their own retention rules.

7. Access, correction and deletion

To request access to, correction of, or deletion of information held by Cloudmeter, email mail2ganesh.cse@gmail.com with the app name and your login username or contact email. We may request reasonable information to verify that the request is yours. Deletion and account disabling are handled manually; there is no self-service account creation or deletion feature in the current closed test.

If you use the shared community tester login, do not submit personal information through it. You can request information associated with your own support interactions; you cannot request another person’s private records. The operator can disable or rotate the shared tester credential.

Removing the Android app removes its local app data but does not delete server records or close broker positions. Turning trading OFF also does not close positions. Stop automated trading and resolve outstanding broker activity before requesting removal of an administrator account’s operational data. Some records may need to be retained for security, disputes or legal obligations; we explain applicable limits when responding. To remove information held directly by a broker or Google, contact that provider.

8. Children and changes to this policy

Cloudmeter is intended for adults and is not directed to children under 18. If you believe a child has provided personal information to Cloudmeter, contact us to request review and removal.

We may update this policy as the service changes. The latest version will remain at this public URL, with an updated date. Material changes to data handling will be reflected in the service’s disclosures.