Cloudpanel policies
Privacy policy
Effective date: November 22, 2026
This policy explains how Cloudpanel at manager.servicesparrow.xyz handles information when you use its domain, DNS, hosting, and email management features. This deployment is operated by its portal administrator, referred to here as the operator.
1. Information we process
- Portal account details, password hashes, and signed session information used to authenticate access.
- Connected Cloudflare account details, API credentials, domains, DNS records, SSL/TLS settings, groups, and workflow configuration and execution history.
- cPanel server addresses, usernames, API tokens, mailbox addresses, and mailbox passwords or Google app passwords you choose to save.
- For connected Google accounts: your verified email address, authorization tokens, mailbox folders or labels, message headers, read status, message content, and attachments needed for the mail features you use.
- Basic operational information such as IP addresses, request paths, timestamps, and errors that may appear in web server or infrastructure logs.
2. How information is used
Information is used to authenticate users, display and manage connected services, list and read mail, send messages and replies when requested, update read status, show folder and unread counts, provide new-mail notifications, run requested workflows, and maintain and secure the service. Connecting an account allows the portal to check mail automatically while the mail workspace is open.
We do not sell personal information, use mailbox content for advertising, or use Google user data to train generalized artificial intelligence or machine-learning models.
3. Google account access and Limited Use
Google sign-in requests your email identity and mail access so that the portal can read and send messages and show mailbox folders and status. The Gmail mail scope permits broad mailbox access; the portal uses that access for its user-facing email features. OAuth access and refresh tokens allow authorized access without storing your normal Google password. If you choose the app-password method, the app password is saved instead.
Cloudpanel's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Google user data is not shared with advertising platforms, data brokers, or lenders. Human access to Google user data is limited to your explicit permission, necessary security investigations, or legal obligations, as permitted by that policy.
4. Storage and security
Saved mailbox credentials, Google client secrets, and OAuth tokens are encrypted at rest on the deployment server. Cloudflare credentials are held in the server environment; portal passwords are stored as hashes. Server administrators control the hosting environment, storage, encryption keys, and any backups. Encryption does not prevent an authorized server administrator from accessing data needed to operate the portal.
Connections to this public portal use HTTPS, and mailbox connections use TLS with certificate verification. Message bodies and attachments are fetched from the connected provider when needed; the application does not maintain a permanent local mailbox archive. Downloaded attachments, provider-side mail, infrastructure logs, and any administrator-managed backups may have separate retention. No security measure can guarantee absolute protection.
Encrypted backups and mail caching
Mailbox lists are cached in server memory for up to 60 seconds and opened message bodies for up to five minutes. Refresh bypasses the list cache. These caches are bounded and cleared on restart. Google Drive authorization is optional and separate from Gmail. When you create a backup, portal settings, saved credentials, groups, and workflows are encrypted with your chosen passphrase before upload to the selected Google Drive account. Manual backup passphrases are not retained. When you enable hourly automatic backups, the active backup passphrase or generated recovery key is retained in the encrypted server credential store so backups can run unattended; authenticated portal users can download the active recovery key. Disabling the schedule clears the retained key, and existing backups require the original key for recovery. Backups remain in that Drive until you delete them; disconnecting does not delete existing backups. Mail messages are excluded.
Additional mailbox providers and delivery tests
Google Workspace uses the same user-authorized Google mail access as Gmail. Proton connections use either a generated SMTP token for sending or generated Bridge credentials and an optional public TLS certificate for inbox access. These saved credentials are encrypted in the portal credential store.
When you explicitly send an address test, the selected mail provider receives the recipient address and a fixed test message containing a one-time receipt link. The recipient can confirm receipt without signing in. The link expires after 24 hours; opening the page alone does not confirm receipt. The portal keeps up to 100 test records containing sender and recipient addresses, message identifiers, dates, status and confirmation-token hashes. Test metadata and provider credentials are included in encrypted portal backups. Checks may inspect recent sender delivery reports and the matching message in a connected recipient Inbox or Spam folder; they do not prove the identity of the person using the address.
Transactional email integrations
When you connect Maileroo, the portal stores its API Management key and domain Sending Keys encrypted in the credential store. Requested domain management and verification checks exchange domain names and DNS values with Maileroo. Sending a transactional message shares the sender, recipients, subject, and message content with Maileroo and the recipients. To addresses are visible to the other To recipients. The portal disables open and click tracking on messages sent through this integration. The portal can generate domain Sending Keys automatically when your Management key permits it, reuse an existing Cloudpanel key, and save it encrypted. Saved integration settings are included in your encrypted portal backups.
5. Providers and disclosures
The portal exchanges information with Google, Cloudflare, your configured cPanel and mail servers, and the hosting infrastructure as necessary to deliver the features you request. Sending mail shares the message and addressing information with the mail provider, intended recipients, and their mail systems. Each provider operates under its own terms and privacy practices.
Information may also be disclosed when required by law or when necessary to investigate abuse or protect the service, subject to applicable law and Google's Limited Use requirements where Google user data is involved.
6. Cookies, browser storage, and notifications
A session cookie keeps you signed in. A short-lived authorization cookie protects the Google connection flow. Browser local storage remembers notification preferences and mailbox notification cursors so old messages do not trigger repeated alerts. The application does not include advertising trackers or third-party analytics. Web servers may still record operational request logs.
Desktop notifications are optional and require browser permission. Automatic mail checks and notifications run while the workspace is open. You can disable notifications in the portal or browser and clear cookies and local storage in your browser settings.
7. Retention, disconnecting, and deletion
Connection details and settings are kept until you disconnect or remove them, or the operator deletes them. Disconnecting a mailbox removes its saved local connection and credentials; it does not delete messages held by Google or your hosting provider. Shared Google OAuth application settings remain until the operator changes or removes them. Domain groups and workflow history are stored separately from mail connections.
You can revoke Google OAuth access in your Google Account connections, or revoke an app password in Google Account security settings. To remove remaining portal data, shared settings, logs, or backups, contact the operator. Logs and backups follow the operator's maintenance and retention practices; deletion of active connection data does not automatically erase historical backups or provider-side records.
8. Your choices and contact
You may decline to connect an account, disconnect it later, revoke provider permissions, turn off desktop notifications, or ask the operator about access, correction, or deletion of information held by this deployment. The operator may need to verify your authority over the relevant account before carrying out a request.
For questions, privacy requests, or reports of unauthorized access, contact the administrator who provided your portal access through your existing support channel.
9. Changes to this policy
Updates will be posted on this page with a revised effective date. Review the policy when connecting new services or using new features. See also our Terms of service.