Version: 2026-10-27
Last revised: October 27, 2026
This Privacy Policy explains the personal data processed in connection with Flipr.Cloud subscription software, its website, dashboard and supported integrations (the "Services"). In this Policy, "Flipr.Cloud", "we", "us" and "our" refer to the provision of the Services under the Flipr.Cloud name.
The Policy describes the information involved, its purposes, recipients, retention and your applicable rights. It is an information notice. Reading this Policy, using the Services or accepting the Terms of Service does not constitute blanket consent to every processing activity or to optional marketing or tracking.
Flipr.Cloud determines the purposes and means of processing associated with administering accounts and subscriptions, operating and securing the Services, and handling support and privacy requests.
For questions about this processing or to exercise your rights, contact legal@flipr.cloud.
Connected exchanges and other services may process information for their own purposes under their own privacy notices. Their responsibility is distinct from the responsibility for processing carried out in connection with Flipr.Cloud. The fact that you configure software instructions does not, by itself, determine the data protection role of each participant.
Depending on the features you use, the following information is processed:
| Category | Information involved |
|---|---|
| Account and profile | Email address, first and last name, country, account identifier, password hash, verification status, authentication information and account settings. |
| Exchange connections | API keys, secrets, required passphrases, exchange and account labels, connection settings and technical connection status. |
| Instructions and automation | Webhook messages, commands submitted through supported interfaces, parameters and conditions, execution records, monitoring information and diagnostics. |
| Exchange information | Balances, positions, orders, transaction identifiers, statuses and API responses obtained through connected accounts. |
| Subscriptions and payments | Plan and billing-period details, payment and renewal status, customer and transaction references, payment-related choices and records used to reconcile payments. Where you pay in crypto-assets, these may include payment addresses and public blockchain transaction references. |
| Notifications and support | Notification preferences, enabled Telegram connection details, message identifiers, support correspondence and the content of messages exchanged through enabled functions. |
| Security and usage | IP addresses, login events, browser or device information, website usage, errors and records of suspected abuse or technical incidents. Security records may include limited samples of requests associated with an incident. |
Information is obtained from you, the integrations you enable, connected exchanges, payment providers and operation of the Services. Website tools may also collect information as described in section 13.
Providing the account and connection information necessary for a requested feature is a condition of using that feature. Without it, the corresponding functionality may not be available. Do not include unnecessary personal information, information about unrelated third parties, wallet recovery phrases or other third-party secrets in webhook messages or support requests.
Exchange API credentials are confidential authentication information. API keys, secrets and required passphrases are encrypted before storage in the application database.
Authorised server processes use these credentials to authenticate connections to the exchanges you select, process configured instructions, retrieve account and order information, monitor enabled features, reconcile responses, display a key preview and perform connection checks and maintenance. Authentication information required by an exchange is communicated to that exchange through the connection.
Exchange API credentials are different from the private keys of a blockchain wallet. Encryption protects stored credentials but does not prevent the authorised application from using them to perform enabled functions.
Removing a saved connection in Flipr.Cloud and revoking a key at an exchange are different actions. Revocation at the exchange invalidates the credential according to that exchange's rules. Neither action reverses completed activity, and removing a connection does not itself cancel orders or close positions held at the exchange. Removing or revoking a key may interrupt monitoring and automated protective actions.
The legal basis depends on the purpose of the processing:
You may withdraw consent without affecting processing that lawfully took place before withdrawal. Withdrawing optional consent does not by itself end processing necessary to provide the contracted Services or meet a separate applicable legal obligation. The website tools currently used are described in section 13.
Information is used to operate accounts, connect to exchanges, apply your configured commands and display the resulting activity. This includes technical calculations, checks, monitoring and subsequent requests associated with enabled automation.
Account and payment information is used to provide the selected plan, apply service limits, reconcile payments, administer renewals and address billing questions. Support information is used to respond to requests, understand reported problems and maintain a record of the assistance provided.
Security, diagnostic and usage information helps identify unauthorised activity, investigate failures, understand use of the website and improve the operation and performance of the Services. The applicable basis depends on the particular purpose, as described in section 5.
Personal information is not sold. Information does not become anonymous merely because a name has been removed; information that can still be linked to an individual remains subject to the applicable data protection rules.
Information is communicated to the recipients needed for the functions involved:
| Recipient | Purpose and information involved |
|---|---|
| Exchanges connected by you | Authentication information and the requests needed to operate the connection, including configured commands and requests for account, order or position information. |
| Hosting and infrastructure providers | Hosting, connectivity, storage, backups, service operation and security. Information involved depends on the infrastructure function. |
| Resend | Delivery of service emails, including recipient addresses and message content such as verification, account, subscription and operational notifications. |
| Stripe | Subscription checkout, recurring payments and payment administration. Information exchanged includes account email, customer and subscription references, selected plan and payment status. Payment details are submitted through Stripe's payment interface. |
| Telegram | Enabled messaging, notification, support and command functions. Information may include connection and chat identifiers, message content and related trading or diagnostic information. |
| Google Analytics | Website usage measurement, including information associated with visits and interactions. |
| Cookiebot | Presentation and administration of cookie-related information and choices. |
Access within the Services is associated with operational, support or security responsibilities. Support messages should not contain credentials that are unnecessary to resolve the request.
Providers may act on instructions for some activities and for their own purposes for others. Exchanges and services with which you have a separate relationship may use information under their own terms and privacy notices.
Information may also be disclosed where required by applicable law or a valid request from a competent authority, or where lawfully necessary to establish, exercise or defend legal claims. Any such disclosure remains subject to the applicable requirements.
The Services use regional infrastructure in Europe, Japan and Singapore. Account and service information may be processed or replicated across regions for the operation of the Services and their integrations.
Connected exchanges and other service providers may process information in additional countries, depending on the provider and the functions you use. Those countries may have different data protection laws.
The legal basis for processing personal data and the requirements applicable to an international transfer are separate matters. Acceptance of the Terms or this Policy is not a substitute for a transfer mechanism required by applicable law.
You may contact legal@flipr.cloud to request information about the locations and transfer arrangements relevant to your data, including any applicable safeguards and how to obtain information about them.
Retention differs by record category. The following periods and criteria do not create a single retention period for every copy or type of information:
| Record category | Retention period or criteria |
|---|---|
| Account and profile information | Used while the account exists. When closure or erasure is requested, the relevant considerations include completing that request, outstanding account matters and any specific obligation or legal claim requiring continued retention. Cancelling a subscription does not itself delete the account. |
| Saved API connections | Retained to support the connection until it is removed. Connections that remain suspended for subscription-related reasons may be removed after at least 14 days. Removal from Flipr.Cloud does not revoke the key at the exchange. |
| Operational webhook execution history | Subject to scheduled cleanup for records older than 30 days. Cleanup timing and technical failures can affect the exact removal time. This history is not a permanent archive of exchange transactions. |
| Other activity and diagnostic records | Retention depends on the record's use for service operation, investigation of a reported failure, reconciliation or a specific dispute. The webhook-history cleanup period does not apply automatically to these separate records. |
| Security-event audit records | Currently have no scheduled deletion date and are maintained as an audit trail for detecting and investigating abuse and security incidents. This does not remove applicable rights or the requirement to justify continued retention. |
| Subscription and payment records | Retention depends on administration of the subscription, reconciliation, payment disputes and applicable accounting or tax requirements. Some transaction records are maintained separately from the account and may remain after account deletion for those purposes. Records held by a payment provider are also subject to that provider's arrangements. |
| Support messages | Retention depends on resolving and following up the request, maintaining relevant support history and addressing related complaints or disputes. |
| Backup and replicated information | Deletion from an operational record does not necessarily occur at the same time in every replica or backup. Retention and removal depend on the particular copy, its recovery purpose and the handling of the relevant deletion request. |
A specific legal obligation or an unresolved legal claim may require relevant information to be retained after normal operational use ends. Continued retention must relate to the applicable purpose; it does not authorise unrestricted use for unrelated purposes.
Account deletion and cancellation of recurring subscription payments are separate actions. Deleting data held in connection with Flipr.Cloud does not itself erase records held independently by an exchange, payment provider or messaging service. Transactions recorded on a public blockchain remain subject to the operation of that blockchain.
You may request information about retention or exercise applicable erasure rights using the contact details in section 12.
Security measures include authentication controls, restrictions on access, monitoring and protection of credentials. Exchange API keys, secrets and required passphrases are encrypted before storage in the application database. Account passwords are stored as hashes. Encrypted connections are used for website access and communication with supported external services.
These measures do not mean that all application data is encrypted at field level. Operational records and support message content may be stored as readable text accessible to authorised application functions and personnel who require access for their responsibilities.
No method of transmission or storage can guarantee absolute security. Security incidents affecting personal data are subject to the notification and other obligations imposed by applicable law.
Keep login, webhook and exchange credentials confidential. Enter API credentials through the designated connection interface rather than sending them in email or support messages.
Create a dedicated exchange API key with only the read and trading permissions required for the features you use. Do not enable withdrawals, external transfers or other unnecessary permissions. Apply exchange IP restrictions where available and use the security features offered by your exchange and account.
If you suspect that credentials have been compromised, contact support@flipr.cloud and take appropriate steps at the exchange, including revoking affected keys where necessary. Verify outstanding orders and positions directly with the exchange when changing or stopping a connection.
Your security responsibilities do not remove the responsibilities applicable to the processing of your personal data by Flipr.Cloud.
Subject to the conditions of applicable law, you may:
Contact legal@flipr.cloud to exercise these rights. Information reasonably necessary to verify your identity may be requested. Do not send passwords, API secrets or wallet recovery phrases as proof of identity.
We normally respond within one month of receiving a request. Where an extension is permitted because of the complexity or number of requests, we will explain the reasons and the extension within that first month. If a request cannot be fulfilled in whole or in part, the response will explain the applicable grounds and available remedies.
You may lodge a complaint with the competent data protection supervisory authority, including in the place of your habitual residence, work or the alleged infringement. Nothing in this Policy requires you to contact Flipr.Cloud before exercising a right to complain to an authority or seek a judicial remedy.
The website uses authentication cookies to maintain login sessions and related browser storage for application settings. Blocking or deleting necessary cookies can prevent login or interrupt account functionality.
The website also uses Google Analytics to measure visits and interactions and integrates Cookiebot to present cookie-related information and choices. These external tools may receive browser, device, usage and connection information.
Some pages request fonts from Google Fonts, which involves a connection from your browser to the external font service. Payment and other enabled third-party interfaces may also use their own browser technologies under their privacy notices.
You can use your browser settings to manage or remove cookies and restrict external requests. Cookie choices available through the website are separate from accepting the Terms of Service. Browser controls and a privacy notice do not replace any consent required by applicable law.
The Services are intended for people aged at least 18, subject to the eligibility requirements in the Terms of Service. Do not create an account if you do not meet those requirements.
If you believe that a child has provided personal information through the Services, contact legal@flipr.cloud. Relevant information will be assessed and handled in accordance with applicable requirements, including restriction or deletion where appropriate.
Your use of an exchange, payment provider or messaging service is also subject to that service's terms and privacy notice. A provider may hold information independently of the copy processed through Flipr.Cloud, and a request to Flipr.Cloud does not itself direct that provider to erase its own records.
Review the notices of the services you choose to connect and use their privacy contact channels for processing they control. This separation does not exclude responsibility for disclosures or other processing carried out in connection with Flipr.Cloud.
This Policy may be updated to reflect changes in the Services, processing activities or applicable requirements. The revised document will identify its version and revision date.
Material changes will be communicated by email or a prominent notice within the Services. A notice of change does not substitute for any consent or other requirement that applies to a new purpose. Changes do not remove rights relating to earlier processing.
Flipr.Cloud is subscription-based software. Personal data processed to operate the software includes coded commands received from the external platforms on which you operate your strategies, together with account and exchange information needed to perform the corresponding software operations.
Commands submitted through other supported interfaces follow the same predefined technical rules. Those rules may generate API requests automatically when conditions specified in a command are met, without a separate confirmation for each request or an investment decision by Flipr.Cloud.
Your trading decisions and relationship with the exchange remain distinct from the responsibility for personal data processed under this Policy. Permission to use an exchange connection is not blanket consent for unrelated uses of your personal data.
Flipr.Cloud
Privacy inquiries and rights requests: legal@flipr.cloud
Technical and account support: support@flipr.cloud
Website: https://flipr.cloud
End of Privacy Policy
For privacy inquiries, contact: legal@flipr.cloud