Current website data practices
Current source inspection found no client analytics SDK, advertising tracker, checkout, authentication flow, form submission, or browser-storage use. The current marketing website therefore does not intentionally collect account-registration or payment data through its interface.
Hosting infrastructure may still process ordinary request, device, browser, network, security, and diagnostic information needed to deliver and protect the website. The current public source does not identify the hosting operator’s complete log fields, locations, or retention settings, so this notice does not invent them.
No client-side mechanism for selling personal information, targeted advertising, or unrelated profiling was observed in the current website source. Any material change to those practices would require an updated notice and applicable controls before use.
Data categories for future features
If accounts, support, subscriptions, or integrations are activated, the operator may need to process only the information required for the feature a person requests. The actual data map and notice must be confirmed before collection begins.
- Profile and contact details, authentication records, and account preferences.
- Subscription status, price, tax, renewal, cancellation, refund, and payment-provider records; full payment credentials should remain with an appropriate payment provider.
- Connected-service identifiers, permissions, and connection status for brokers, MT5, messaging services, or other requested integrations.
- Portfolio, trade, journal, screenshot, tag, configuration, and automation records selected or generated by the user.
- Support communications plus security, device, network, diagnostic, and feature-usage records.
Purposes and data minimisation
Future processing should be limited to providing requested features, securing and troubleshooting the service, communicating with users, administering subscriptions, complying with applicable obligations, and improving reliability. Only data reasonably needed for a stated purpose should be collected, and materially different use requires an updated notice and any required legal basis or choice.
Service providers, integrations, and legal requirements
Information may be shared with infrastructure, security, support, communications, payment, broker, trading-platform, messaging, or other providers only when needed for an activated feature or legal obligation. Connected third parties process information under their own terms and privacy practices where they act independently.
The final production notice must identify or accurately categorise actual recipients and distinguish processors or service providers from independent recipients. Information may also need to be preserved or disclosed when applicable law validly requires it.
Retention, security, and international processing
Retention should be based on the purpose for which information is used, account status, support and security needs, legal obligations, dispute requirements, and technically reasonable backup deletion. No fixed retention period is claimed until the real systems and obligations are documented.
Reasonable technical and organisational safeguards should match the sensitivity and risk of the information, but no storage or transmission method can be guaranteed completely secure. This notice does not claim a certification that has not been verified.
Hosting and service providers may process information in more than one country. Before future personal-data features launch, actual processing locations and any required international-transfer safeguards must be documented; this notice does not claim that transfers never occur.
Location-dependent privacy rights
Depending on location and applicable law, a person may have rights to information or access, correction, deletion, portability, restriction, objection, consent withdrawal, an opt-out of certain sale, sharing, advertising, or profiling practices, and complaint to an appropriate authority where applicable. Exceptions and verification requirements may apply.
The current website does not currently publish a functioning rights-request channel because it does not identify a verified data controller or business contact. A suitable channel, identity-verification process, and response procedure must be published before account, support, payment, or integration data is collected.
Mandatory rights and notice changes
Nothing in this notice limits privacy or consumer rights that applicable law does not allow to be limited. Location-specific rights and duties apply only where their legal conditions are met.
Review and update this notice before material changes to operator identity, contact channels, analytics, cookies, advertising, accounts, support, payments, integrations, recipients, retention, processing locations, or security practices.
Questions about this document
Use these published paths for general questions about this document, the community, or Kinetic features. Support does not identify a registered operator or public address and is not a formal legal-notice or privacy-rights channel. No response time is promised.
- telegramKinetic Fx IndonesiaOpen community discussion and resources that may be available to participants.
- telegramKYRA Community ChatCommunity discussion focused on KYRA tools and their intended workflows.
- emailsupport@kineticfamily.idWebsite, product, privacy, and community-access questions without a promised response time.
