1. Scope and data controller
This policy applies to orbi.gg, the Orbi app, affiliate.orbi.gg, our account and trading services, Discord and Telegram bots, and related support. It covers visits, account creation, AI requests, bot graphs, wallet features, referrals, subscriptions and integrations you choose to use.
P.A. Energy Limited, a company in Cyprus, operates Orbi and is the controller responsible for the personal data described here. Contact us at [email protected] for privacy questions or rights requests. The website, app and affiliate portal use shared account services; a product name change does not create a separate account or erase existing records.
AI assistance and automated trading can have real financial consequences. Orbi does not guarantee profits or protection from loss. Read the trading-risk section of our Terms.
2. Information we collect
Accounts and authentication
We process your name, username, email address, profile picture where supplied, account identifiers, role, active plan, account dates and session records. Google sign-in and supported email/password flows use Firebase Authentication. Direct password sign-in sends your password over HTTPS to our authentication API for verification; passwords retained by that API are stored as one-way hashes, not readable values. We also process hashed refresh token identifiers, expiry, revocation and session activity. Google may provide basic profile information; signing in with Google does not give Orbi access to your mailbox.
Trading and research
We process bot names and status, node graphs and sharing codes, selected wallets, signal sources, execution mode, symbols, positions, orders, prices, timestamps, trading limits, balances, profit and loss, and related performance, market and error records. This can concern live or simulated activity. Public token and wallet data can become personal data when linked to your account or an identifiable person.
Public trader profiles
Accounts with a username have a public Orbi profile by default. Anyone can view your username, profile picture, public bio, completed Solana paper and live trades, and performance calculated from those trades. Paper and live results are shown separately. Your email address, private wallet details, account balances, bot settings and AI conversations are not included. Do not put private information in your public bio. Profiles are hidden when account deletion begins.
Signals and connected channels
Discord, Telegram and other supported connections can involve account, server or channel identifiers, names, delivery settings, message content, delivery status and error records. A signal or message is shared with the platform and recipients you select. Channel members may view, copy or redistribute it. Connect only destinations you are authorized to manage.
Referrals and affiliates
Affiliate accounts can include your name, email, traffic sources, approval status, referral or promo code, payout details, commission records, and tax or identity information where required. Referral activity can include codes, landing URLs, referring domains, timestamps, technical request information, resulting accounts or subscriptions, transaction values, and validation, refund or fraud status. Historical prerelease records may include an email, signup date, campaign and discount entitlement.
Billing, support and technical data
We process plan, billing interval, payment method, status, transaction identifiers, amount, currency, relevant tax or billing details and limited information returned by Stripe or NOWPayments. When enabled, Stripe hosts card checkout; Orbi does not store full card numbers. Crypto payment records can include addresses, networks and transaction signatures. New card and crypto purchases are currently paused, but existing subscription and accounting records remain relevant.
Support requests can include your contact details, messages, attachments and support history. Our servers and infrastructure providers may process IP addresses, timestamps, browser or app version, operating system, request logs, security events and diagnostics to deliver the service and investigate abuse or failures.
2.1. Discord and Telegram bot data
This policy covers Orbi’s Discord and Telegram bots, including their connection flows, commands, research workflows and notifications. We use platform data to verify your connection, authorize commands, run your configured workflows, deliver responses and investigate delivery or security problems—not to sell platform data, target advertising or train AI models on platform messages.
Information received and stored
- Discord: your numeric Discord user ID, linked Orbi account, selected server and channel IDs and names, connection permissions, command names and registration IDs, interaction IDs, command arguments and timestamps. A short-lived OAuth credential verifies your identity during connection; it is not kept as an ongoing user access token. Temporary interaction credentials are used to reply.
- Telegram: your numeric user/private chat ID, username if supplied by Telegram, account-link confirmation, message IDs, commands and their text arguments, and connection and delivery timestamps. The current bot accepts commands in the confirmed private chat, not group conversations. Text sent directly to the bot reaches our service; do not send unrelated sensitive information.
- Workflows and delivery: saved drafts and published configurations, selected destinations, watched keywords, schedules, public research inputs and results, pending digest items, run history, delivery state and errors, and deduplication or rate-limit records. Infrastructure may also record the technical request and security information described above.
Command-only Discord connections do not require message-content access. Where community moderation is explicitly enabled, Orbi processes message text, source message/member/channel IDs, role information, edits and timestamps to apply your configured rules and verify moderation authority. This requires Discord’s Message Content intent and appropriate channel permissions; the bot does not request Administrator or bulk member-list access and cannot read private DMs between members. Linking either platform does not grant access to your mailbox, phone contacts, unrelated private chats, passwords or wallet signing keys. Research commands do not give another member access to your Orbi account or private trading history.
Recipients and service providers
Discord or Telegram receives the replies and notifications sent through its service. Accepted Discord command results and scheduled or watched-source notifications are visible to everyone who can view the selected channel. Permission/input errors can remain private. Moderator alerts include a bounded message excerpt and action result in your selected moderator channel. Own-trade alerts contain the selected confirmed fill information, not wallet keys or unrelated account balances. Telegram replies go to the linked private chat. Recipients may copy messages. Public-data providers receive the token address or search query needed for a lookup, and our hosting and database providers process records to operate the service. Research-workflow commands are not sent to an AI model; optional Orbi AI features are described separately below.
The platforms also process information under their own policies: Discord Privacy Policy and Telegram Privacy Policy. Orbi cannot erase recipients’ copies or records held independently by those platforms.
Retention, disconnecting and deletion requests
Connection details are kept while linked. Disconnecting removes the active link and cancels pending deliveries to that destination; historical delivery records can remain temporarily. Saved workflow configuration remains until deleted, and retired Discord command bindings may remain to prevent another account taking over a registration. Routine cleanup removes finished workflow runs and completed notification records after seven days; active runs and pending digests can remain until resolved or cancelled. Temporary Discord reply credentials are encrypted in stored runs and cleared when the run reaches a terminal delivery state. Restricted backups and lawful retention exceptions are described in Retention and deletion.
Use Orbi’s connection controls or Telegram’s /stop to disconnect, and My Bots → Bot workflows to pause or delete a workflow. Disconnecting is not a request to delete all saved workflow or historical data. To request access, correction or deletion of your bot data, email [email protected] with the subject “Bot privacy request”, the platform and your user ID or username. If you have an Orbi account, include its email; you do not need one to make a request. We verify authority without asking for passwords, tokens or seed phrases, delete platform data no longer needed unless law requires retention, and explain any exception. Account deletion does not itself remove every saved workflow or command binding; contact us for removal of remaining bot records. Platform removal does not erase already delivered messages.
3. Information stored on your device
The website stores account session tokens and basic account information in browser storage so you can stay signed in. Firebase may also persist authentication state locally. Signing out clears the website account session; clearing site data can remove saved sign-in state. The app and website can show the same account profile and active plan.
In production desktop builds, the refresh token used to restore your session is stored in your operating system’s credential vault and short-lived access tokens are held in memory. App settings, conversation history and character preferences can remain in local storage. Uninstalling the app may not remove every credential or downloaded file; sign out and use your device’s data controls where needed.
Affiliate and friend-referral links may save a first-touch code in local storage for up to 30 days. Friend-referral storage can be cleared sooner after successful use. Referral visits may send the code, landing URL, referring domain and request information to our API. Avoid putting sensitive data in referral URLs. Clearing browser storage does not remove a referral already recorded on your account or payment. Pending checkout choices are kept in session storage to continue after sign-in; this does not authorize a payment.
The affiliate portal also uses browser storage for sessions and relevant preferences. The public website currently has no third-party advertising or behavioral advertising trackers. Hosting and security providers may use their own essential technologies.
We use first-party website analytics to understand visits, signup and checkout completion, coarse scroll milestones, plan choices, and FAQ engagement. A random tab identifier is kept in session storage and expires after 30 minutes of inactivity. We do not collect form values, full URLs, recordings, or phone-motion data for these reports. Server milestones can link a journey to a pseudonymous account identifier to confirm setup and live payments. Journey details are retained for up to 30 days, subject to a storage cap; anonymous daily counts are retained for 90 days. The website honors Do Not Track and Global Privacy Control for this tracking. Clearing site storage removes the local identifier. An answer remaining visible is measured as engagement, not proof that it was read.
On supported phones, device-orientation events move Orbi’s eyes. This data is used in memory on your device and is not stored or sent to our servers. The effect does not request camera, microphone or location access. Inter is served with the website rather than requested from Google Fonts.
4. AI conversations and ongoing tasks
Optional chat diagnostics can be enabled in Agents settings. They retain redacted user messages, public assistant replies and findings for up to seven days for owner-only reliability review. They exclude private reasoning and raw tool payloads. Redaction is best-effort; never send credentials or seed phrases. Turning sharing off deletes diagnostic copies, not your saved chats or ongoing task checkpoints. These logs do not automatically train a model. Other accounts are not opted in on your behalf.
AI requests include the instructions and conversation context you provide, selected model, relevant graphs or research data, tool results and proposed actions. Conversation history is saved in your desktop workspace’s local storage. Context needed to respond or continue a task is sent through our authenticated API to the AI provider, currently OpenAI. An ongoing task can involve repeated requests while it runs.
Our service asks the provider not to retain responses as saved response history. This does not mean that no data is retained for security, abuse prevention, caching or legal purposes. Provider processing follows its applicable terms and privacy practices. Do not include unrelated sensitive personal data, passwords or seed phrases in an AI conversation.
We record model usage and allowance information to operate the feature and enforce plan limits. Stopping a task does not undo completed actions or erase information already sent to a provider. Deleting local conversation history does not itself delete relevant account, usage, trading or third-party records.
5. Wallets and connected trading access
Wallet features process addresses, networks, balances, positions, orders, deposits, withdrawals, transaction signatures, permissions and execution records. Public blockchain addresses and transactions can be visible to anyone and may be linked to your identity.
Orbi-hosted wallets use signing keys stored encrypted on our servers. The service accesses those keys to sign authorized transactions. Other wallet or venue connections may use provider tokens, credentials or permissions, depending on the integration. Signing access differs from reading a public address; review the wallet type and permissions before transferring funds or enabling trading. Use dedicated connection controls rather than sending secrets through email, support channels or AI prompts.
Removing a connection does not undo an on-chain transaction or erase public blockchain records. Account deletion stops agents and new entries, requests closure of server-managed open trades, and waits for unresolved orders and transfers before completing. Device-managed live positions must be closed in the app first. Market exits incur normal fees and slippage and may be unavailable; deletion remains pending if settlement cannot be verified.
Account deletion does not withdraw or destroy funds. Your assigned wallet and its encrypted signing records are retained in our database, with normal account access removed. Withdraw first if you need immediate access. Recovery after deletion requires support and identity verification; creating another account does not transfer the retained wallet to it.
6. How we use information
- Create, authenticate, secure and administer accounts and shared profiles.
- Deliver AI assistance, bot graphs, research, wallets, trading, signals, analytics and updates you request.
- Manage plan entitlements, usage allowances, subscriptions, billing and support.
- Attribute referrals, validate commissions, prevent abuse and process eligible affiliate payouts.
- Honor relevant existing prerelease and discount entitlements.
- Diagnose failures, maintain reliability and investigate fraud or unauthorized access.
- Send necessary account, security, billing and policy notices.
- Meet legal obligations, enforce our Terms and establish or defend legal claims.
We do not sell personal data or use account, trading or AI conversation data for third-party targeted advertising. Optional marketing, if offered, is separate from necessary service messages and follows applicable consent and opt-out requirements.
7. Legal bases for processing
Where a legal basis is required, the purpose of the processing determines the basis:
- Contract: account access and the AI, trading, billing or connected features you request.
- Legitimate interests: securing Orbi, preventing abuse, resolving support issues and maintaining reliability, balanced against your rights.
- Legal obligations: required accounting, tax, consumer, security or regulatory records and lawful requests.
- Consent: optional processing that legally requires it; you can withdraw consent prospectively.
Essential account information is necessary to create and secure an account. Optional AI requests and integrations remain your choice. Withholding data needed for a feature can prevent it from working.
9. Retention and deletion
We retain data while needed for the purposes described here. Account records support an active account; retention after closure depends on unresolved billing, disputes, security investigations, legal obligations and backup needs. Individual refresh tokens expire after up to 30 days unless rotated or revoked earlier. Token expiry does not automatically erase the associated account or security record.
Trading history, graphs and task records support your workspace, historical dashboards and investigations. AI usage records support allowance accounting and dispute resolution. Support, payment, commission and tax records may remain for applicable statutory or claims periods. Referral records support attribution windows, fraud checks and commission disputes. Historical prerelease records support remaining entitlements, duplicate-use checks and related support or recordkeeping duties.
You can request account deletion from the website footer or the app’s Account settings. After the safety checks finish, your active bot graphs, Orbi chats and tasks, preferences, profile and sessions are removed. Trade records and collected market research remain in Aegis; retained trading, custody, billing and security records are restricted rather than restored as a new account’s workspace. Recurring subscription renewal is stopped.
Local conversations and settings remain until removed using available app or browser controls. Backups may contain records until replaced or removed, with access restricted to recovery and other necessary purposes. Provider retention is separate, and public blockchain records cannot be erased by Orbi. Contact us to ask what we retain and why, or to request deletion subject to any lawful retention exception.
10. International data transfers
Our infrastructure includes servers in Amsterdam, while authentication, AI, payment, security and other providers may process data elsewhere. Your information can therefore be processed outside your country. Where required, transfers must rely on an applicable adequacy decision, contractual safeguards or another lawful mechanism. Contact us for information about safeguards relevant to your data and how to obtain a copy where applicable.
11. Security
Measures include HTTPS in production, one-way password hashing, hashed server-side refresh tokens, session expiry and revocation, access controls, rate limits, protected server records, operating-system storage for desktop refresh tokens, and encrypted signing keys for hosted wallets. Encryption of a hosted signing key does not mean only you can use it: authorized service processes must access it to carry out activity.
No system is completely secure. Protect your device, email, password, recovery methods and connected accounts, and report suspected compromise promptly. Do not send passwords, private keys, seed phrases or exchange credentials to our email or public support channels.
12. Your privacy rights and choices
Depending on applicable law, you may request access, correction, erasure, restriction or portability of personal data, object to processing, withdraw consent, or complain about a decision. Withdrawal of consent does not affect processing lawfully completed beforehand. You may object to processing based on legitimate interests and ask about the balancing of those interests against your rights.
Email [email protected] with your request and account email. We may verify identity and authority without asking for passwords or seed phrases, and respond within the period required by law. We explain any refusal or lawful retention exception. A deletion request may need to account for open positions, accessible wallet funds and records that law requires us to keep.
You may complain to the data-protection authority competent for your circumstances, including the Cyprus Commissioner for Personal Data Protection. The European Data Protection Board’s guidance explains EU privacy rights and how to exercise them.
13. Automated strategies and AI decisions
Bot graphs evaluate market data and configured conditions; AI models interpret the context you provide to propose or perform supported actions. Enabled trading automation can affect your assets and lose money. Review approvals, configure limits, monitor tasks and use the available stop or permission-revocation controls. Producing a strategy does not mean Orbi has assessed whether it is suitable for your circumstances.
We also use automated checks for account access, plan allowances, referrals and security. If a decision significantly affects you or you believe a restriction is wrong, contact us to request an explanation, challenge it or ask for human review where applicable law provides that right. Nothing here removes protections that apply to solely automated decisions with legal or similarly significant effects.
14. Age limits
Orbi is intended for people aged 18 or older. We do not knowingly collect children’s personal data. Contact us if you believe a child supplied data so we can investigate and remove it where appropriate.
15. Changes to this policy
We may update this policy as the product, providers or law change. The revised page will show a new last-updated date, with additional notice of material changes where required.
16. Contact us
P.A. Energy Limited, Cyprus, is responsible for this policy. Send privacy questions and rights requests to [email protected]. Mark your message “Privacy request”. General product help is also available through Orbi support. Do not include passwords, seed phrases, private keys or exchange credentials in either channel.