Privacy Policy

1. Core Architectural Privacy Principle — Customer Data Remains Local

B-52 Original Edition is a self-hosted Execution Management System (EMS) designed to operate on infrastructure controlled and administered by the customer, including private Linux servers and cloud Virtual Private Servers (VPS).

Under the standard customer-controlled deployment model, trading execution, exchange credentials, and authoritative execution records remain within the customer's designated operating environment.

1.1. Exchange Credentials and Financial Custody

B-52.io DOES NOT REQUIRE OR COLLECT CUSTOMER EXCHANGE API KEYS, PRIVATE SIGNING KEYS, EXCHANGE ACCOUNT PASSWORDS, OR WITHDRAWAL CREDENTIALS AS PART OF NORMAL TELEMETRY OR WEBSITE OPERATION.

Provider does not take custody of customer trading capital or operate B-52.io as a brokerage, exchange, or centralized trading authority.

Customer exchange credentials remain within the customer's designated execution environment during normal operation.

1.2. Local Execution Records

The authoritative local execution database, configuration files, individual trading instructions, and customer-developed trading strategies are not automatically uploaded to B-52.io as part of standard execution.

Any operational metadata transmitted through optional telemetry is governed separately by the restrictions in Section 2.3.

1.3. Voluntary Support Disclosures

Customers may voluntarily submit selected logs, diagnostic exports, or configuration excerpts when requesting authorized technical support.

Such submissions are separate from normal execution and telemetry processing.

Customers should remove passwords, API credentials, private signing keys, and other unnecessary sensitive information before submitting diagnostic materials.

Provider will process voluntarily submitted materials for the authorized support purpose and according to applicable data-protection requirements.

2. Information We Collect

We seek to limit information collection to what is reasonably necessary for website operation, security, Private Evaluation requests, technical communications, optional customer observability, and services actually provided.

2.1. Information You Provide Directly

Private Evaluation Requests

When you submit a Private Evaluation request, we may collect:

• Name, alias, or preferred identification.
• Email address and contact information.
• Preferred messaging handle, if voluntarily provided.
• General trading or technical experience.
• Information about your intended evaluation requirements.
• Other details you voluntarily provide through the application or subsequent correspondence.

This information is used to evaluate requests, communicate with applicants, and arrange authorized demonstrations or evaluations.

Submission of a Private Evaluation request does not itself establish a commercial licensing relationship.

Private Evaluation Access

Private Evaluations are conducted on Provider-operated infrastructure using Provider-controlled Binance Futures Demo/Testnet accounts. Evaluation participants are not required to provide exchange API keys, exchange account credentials, or trading capital.

When SSH evaluation access is granted, the evaluation infrastructure may collect and process:

• SSH public keys supplied for authorized access.
• Authentication and security records, including originating IP addresses, login timestamps, and authentication outcomes, to the extent these records are generated.
• Session or command activity only where such monitoring is enabled in the evaluation environment and disclosed to participants.

This information is used to provide and secure evaluation access, prevent abuse, and support evaluation participants. The scope of any session monitoring will be disclosed before such monitoring is used.

Support and Communications

When you contact Provider, we may retain your correspondence, contact details, technical descriptions, and information voluntarily provided to resolve your inquiry.

Future Customer and Licensing Records

If commercial licensing or customer account services are introduced, we may collect the information necessary to administer those services, including customer identification, billing contact details, license identifiers, subscription status, and relevant support records.

Such information will be collected only when the corresponding services are offered and applicable privacy notices and contractual arrangements are in place.

Future Payment Processing

If B-52 introduces paid subscriptions or licensing transactions, payments may be processed through designated third-party payment providers.

The applicable payment arrangements, data categories, and service providers will be disclosed when those services are introduced.

Provider does not require website visitors or Private Evaluation applicants to provide payment-card information merely to access public documentation or fleet demonstrations.

2.2. Website, Security, and Technical Information

Server and Security Records

When visitors access B-52.io, the website and its infrastructure or security providers may process technical information, including:

• IP addresses and network connection information.
• Browser and device characteristics.
• Requested pages and referring addresses.
• Request timestamps and technical response information.
• Security, diagnostic, and abuse-prevention events.

Such records support website availability, security monitoring, troubleshooting, and protection against unauthorized access or malicious activity.

Cookies, Browser Storage, and Analytics

B-52.io may use cookies, browser storage, or comparable technologies where necessary for security, authentication, session management, or website functionality.

Website hosting, delivery, and security providers may process technical visit information where their services are enabled.

B-52.io uses Google Analytics 4, a web analytics service provided by Google, to understand how the website is used. The Google tag loaded by B-52.io may set cookies or similar browser identifiers and sends information to Google, including:

• The pages visited, their addresses (including any query-string parameters in the address), and the referring page or website.
• Approximate location derived from the visitor's IP address.
• Device, operating-system, and browser characteristics.
• The date, time, and duration of visits.
• Interactions with the website, including page views, views of the Live Demonstration and Private Evaluation pages, the successful submission of a Private Evaluation request, and the automatic interaction events (such as scrolling and form interactions) collected under the website's Google Analytics configuration.

Provider uses this information to measure website traffic and usage, to understand how visitors reach and use the website, to assess how many Private Evaluation requests are submitted, and to improve the website's content and performance.

The contents of Private Evaluation applications (including names, email addresses, organization names, and intended-use descriptions) and customer or demonstration fleet telemetry are not sent to Google Analytics. A successful submission is recorded only as an event, without applicant information.

Google acts as a service provider in relation to this measurement, and its handling of information is governed by its own terms and privacy documentation. Visitors may limit this measurement through browser privacy settings, content-blocking tools, or the opt-out tools Google provides.

Before introducing any analytics tool beyond Google Analytics 4, Provider will identify the relevant data processing, disclose the applicable services and information categories, and implement any notices, consent choices, or preference controls required by law. Google Analytics 4 is the analytics service active at public launch.

Provider will not treat acceptance of essential website functionality as automatic consent to optional tracking where separate consent is legally required.

No Sale of Personal Information

PROVIDER DOES NOT SELL OR RENT VISITORS' OR CUSTOMERS' PERSONAL INFORMATION TO THIRD-PARTY ADVERTISERS OR DATA BROKERS.

Any disclosure to operational service providers remains subject to Section 4 of this Policy.

2.3. Customer Fleet Telemetry — Strictly Private, Read-Only Observability

B-52.io may publicly display approved operational telemetry from Provider-operated demonstration aircraft for product demonstration, technical evaluation, and informational purposes.

Such demonstration telemetry is separate from customer-operated instances.

CUSTOMER-OPERATED FLEET TELEMETRY SHALL NEVER BE PUBLICLY DISPLAYED, DISCLOSED, OR MADE ACCESSIBLE ON B-52.io UNDER ANY CIRCUMSTANCES, REGARDLESS OF CUSTOMER CONSENT.

Customer fleet telemetry may be transmitted to and displayed exclusively within the customer's private, authenticated B-52.io account, ONLY WITH THE CUSTOMER'S PRIOR, EXPLICIT, AFFIRMATIVE OPT-IN FOR PERSONAL DISPLAY.

ALL CUSTOMER-AUTHORIZED TELEMETRY IS STRICTLY READ-ONLY AND FOR OBSERVABILITY PURPOSES ONLY.

B-52.io has no authority or capability to initiate trading lifecycles, submit, modify, or cancel exchange orders, manage positions, change execution parameters, or otherwise control customer-operated B-52 instances.

Customer-authorized telemetry remains private and inaccessible to other customers and the general public.

Authorization for personal telemetry display does not authorize trading control or public disclosure.

Customer telemetry processing is limited to the operational information necessary for the authorized observability functions, subject to the applicable telemetry contract, privacy protections, and access controls.

2.4. Telemetry Authorization and Withdrawal

Private customer telemetry is optional.

Enabling an execution instance or using B-52 Original Edition does not automatically authorize transmission of customer telemetry to B-52.io.

Customers must provide separate, affirmative authorization before customer telemetry is enabled for personal display.

Customers may withdraw authorization for private telemetry through the applicable configuration or authorization process.

Withdrawal will end the authorized collection and display of future telemetry for that purpose, subject to the technical operation of the relevant service. Previously retained data will be handled in accordance with applicable deletion rights, retention obligations, and this Policy.

Disabling outbound telemetry does not necessarily erase records previously transmitted to B-52.io. Customers may request deletion of eligible retained information under Section 6.

3. How and Why We Use Information

Provider processes information only for specified, legitimate purposes connected with the operation of B-52.io and applicable services.

These purposes include:

• Reviewing and responding to Private Evaluation applications.
• Communicating with prospective customers and evaluation participants.
• Arranging authorized technical demonstrations and SSH evaluation access.
• Providing technical information, assistance, and support.
• Maintaining website availability, performance, and security.
• Detecting abuse, preventing fraud, and investigating security incidents.
• Operating customer-authorized private, read-only telemetry services.
• Maintaining records required for lawful business administration.
• Administering future licensing or subscription services when introduced.
• Complying with applicable legal and regulatory obligations.

Lawful Grounds for Processing

Where applicable data-protection law requires a lawful basis, processing will be conducted under an appropriate basis for the specific purpose.

Depending on the circumstances and jurisdiction, this may include:

• The individual's informed consent.
• Processing necessary to respond to a requested evaluation or take steps toward an agreement.
• Performance of an applicable customer contract.
• Compliance with a legal obligation.
• Legitimate interests in operating, securing, and maintaining the website, where permitted by law.

Optional customer telemetry processing requires the express authorization described in Section 2, independently of other processing grounds that may apply.

Provider will not use Private Evaluation contact information for unrelated promotional communications without an appropriate lawful basis.

4. Information Sharing and Third-Party Service Providers

PROVIDER DOES NOT SELL, RENT, OR TRADE CUSTOMER PERSONAL INFORMATION.

We disclose information only where reasonably necessary for legitimate operational purposes or where required or permitted by applicable law.

4.1. Infrastructure and Operational Service Providers

Information may be processed by service providers responsible for:

• Website hosting, delivery, and network security.
• Transactional email and business communications.
• Website performance measurement and analytics (Google Analytics 4).
• Customer authentication and applicable private account services.
• Technical support infrastructure.
• Future billing or payment processing, when introduced.

Service providers will be subject to applicable contractual, confidentiality, and data-protection requirements appropriate to the services they perform.

Information shared with service providers is limited to what is reasonably necessary for the relevant service.

Such operational processing does not authorize the public disclosure of customer fleet telemetry.

4.2. Legal and Regulatory Disclosures

Provider may disclose information when required by applicable law, valid legal process, or a legally binding governmental or regulatory request.

Disclosure may also occur where legally permitted and reasonably necessary to investigate fraud, respond to security incidents, protect legal rights, or prevent unlawful activity.

4.3. Customer Fleet Confidentiality

Customer-operated fleet telemetry is not a public information service.

Any authorized processing by infrastructure providers for the purpose of delivering private telemetry does not grant those providers permission to publish, market, or independently expose customer fleet information.

Private customer telemetry shall not be made accessible through the public B-52.io fleet demonstration.

5. Data Retention, Security & Protection

5.1. Retention

Provider retains information only for as long as reasonably necessary for its disclosed purpose, subject to applicable legal requirements.

Retention depends on the category of information and its operational purpose:

• Private Evaluation Applications: Retained while the request is being assessed or the evaluation is arranged, and for reasonable follow-up after its conclusion. Continued retention depends on outstanding correspondence, support needs, or applicable legal requirements.
• SSH Access and Evaluation Security Records: Retained as needed to administer evaluation access, investigate authentication or security events, and address abuse or disputes. Retention may be longer where an incident remains under investigation.
• Support Communications: Retained while the inquiry is being handled and afterward only as needed for related support, security, or legal purposes.
• Website and Security Logs: Retained according to the operational need for troubleshooting, security monitoring, incident investigation, and the applicable infrastructure-provider log-retention settings.
• Customer-Authorized Telemetry: If private observability is offered, retained only as necessary for that service and subject to the customer's authorization, applicable withdrawal and deletion procedures, and legal retention requirements.
• Future Billing and Licensing Records: If commercial services are introduced, retained as necessary for customer administration and applicable tax, accounting, or legal requirements.

Applicable retention periods and technical deletion arrangements will be documented against the actual services and provider configurations before public launch or activation of the relevant feature. Where applicable law requires specific retention information, Provider will disclose the relevant periods or criteria used to determine them.

Information that is no longer required will be deleted, anonymized, or otherwise disposed of according to applicable legal and operational requirements.

5.2. Security Measures

Provider applies technical and organizational safeguards appropriate to the information processed, including encrypted website connections, authentication, access restrictions, and controls designed to prevent unauthorized disclosure or alteration.

Customer-operated telemetry services, when made available, must enforce authenticated private access and separation between customer accounts.

NO INTERNET-CONNECTED SYSTEM OR ELECTRONIC STORAGE SYSTEM CAN BE GUARANTEED COMPLETELY SECURE.

Provider does not guarantee that security incidents, unauthorized access, or data loss can be eliminated under all circumstances.

5.3. Customer Responsibilities

Customers remain responsible for securing their own infrastructure, exchange API credentials, local execution databases, user accounts, and connected devices.

Access credentials for any B-52.io private account must be protected against unauthorized use.

Customers should promptly report suspected account compromise or unauthorized disclosure through the designated privacy or support contact.

6. International Processing & Your Privacy Rights

6.1. International Processing

B-52.io may serve visitors and customers located in multiple jurisdictions.

Personal information may be processed by Provider or its authorized service providers in locations outside the individual's country of residence. The locations and service providers involved depend on the website and services actually used.

Where international processing or transfer requires a recognized legal mechanism, contractual safeguards, notification, or other conditions, Provider will establish the applicable arrangements before carrying out the relevant processing. Where required by law, information about applicable transfer safeguards and how to obtain further details will be made available through the contact information in Section 8.

Providing information to B-52.io does not constitute a waiver of legally required protections for international data transfers.

6.2. Privacy Rights

Depending on applicable law and the circumstances of processing, individuals may have rights to:

• Access: Obtain information about personal data held or processed about them.
• Correction: Request correction of inaccurate or incomplete personal information.
• Deletion: Request erasure of eligible personal information, subject to applicable legal exceptions.
• Portability: Request a copy of eligible information in a portable format where legally required.
• Restriction or Objection: Restrict or object to certain processing activities where applicable law provides those rights.
• Withdraw Consent: Withdraw previously granted consent for processing that relies upon consent.
• Complaint: Lodge a complaint with an applicable data-protection or supervisory authority where that right exists.

Withdrawal of consent does not retroactively invalidate processing that was lawful before withdrawal.

Certain records may need to be retained to satisfy applicable legal, security, accounting, or dispute-resolution obligations.

6.3. Customer Telemetry Withdrawal

Customers may withdraw their authorization for private telemetry transmission and personal display.

WITHDRAWAL OF PRIVATE TELEMETRY AUTHORIZATION SHALL NEVER BE CONSTRUED AS REQUIRING OR PERMITTING PUBLIC DISCLOSURE OF CUSTOMER TELEMETRY.

Requests concerning previously retained customer telemetry will be handled under applicable data-protection rights and retention requirements.

6.4. Exercising Your Rights

To submit a privacy inquiry or request, contact Provider using the details in Section 8.

Provider may request reasonable verification of identity or authority before disclosing, modifying, or deleting information.

Requests will be considered and answered within the timeframes required by applicable law.

7. Changes, Effective Date & Authoritative Version

7.1. Changes to This Policy

Provider reserves the right to revise, amend, or update this Privacy Policy to reflect changes in applicable law, website functionality, service providers, security practices, or data-processing activities.

Where required by applicable law, material changes will be communicated through appropriate notification or consent procedures.

Publication of an updated Privacy Policy does not retroactively authorize processing that was not lawful when originally performed.

7.2. Effective Date

Revisions will become effective upon publication on B-52.io or on a later effective date specified in the updated Policy, subject to applicable legal requirements.

The "Last Updated" field will identify the applicable revision date.

7.3. Authoritative Version

THE CURRENT PRIVACY POLICY PUBLISHED ON THE OFFICIAL B-52.io WEBSITE CONSTITUTES THE AUTHORITATIVE PUBLIC VERSION OF PROVIDER'S PRIVACY DISCLOSURES.

Downloaded copies, archived editions, and third-party reproductions do not supersede the current published version for prospective processing.

Earlier versions remain relevant to processing carried out during the periods in which they were effective.

7.4. Preservation of Privacy Rights

No revision to this Policy overrides mandatory data-protection requirements or removes privacy rights that cannot lawfully be waived.

The privacy commitments prohibiting public disclosure of customer fleet telemetry remain governing principles of B-52.io's customer observability architecture.

8. Contact Information

For questions regarding this Privacy Policy, personal information, customer telemetry privacy, or applicable data-protection rights, contact:

Website: https://b-52.io

Email: contact@b-52.io