Privacy Policy

1. Scope

This policy applies to the Multibot desktop application, mobile web application, website, support interactions, and connected account services.

2. Information we process

We process account identifiers and verified email information, subscription state, support communications, device and app-version information, account-scoped profiles and settings, session summaries, checklist records, remote-host status, command receipts, and security or diagnostic events needed to operate and protect the service.

3. Sensitive local information

Proxy credentials, rotating desktop refresh tokens, game-session credentials, cookies, and browser-control details are not intended for cloud synchronization. Desktop refresh and proxy secrets are stored through macOS Keychain, Windows Credential Manager, or a Linux Secret Service keyring. Mobile authentication is managed by Clerk rather than stored in Multibot-owned browser storage.

4. Service providers

Clerk provides identity, account recovery, and authentication security. Stripe provides checkout, subscription billing, payment-method management, invoicing, and fraud controls. Convex provides authenticated application data and remote-command coordination. Hosting, update distribution, and error-delivery providers may process limited technical information necessary to deliver the service.

Sentry receives error reports from the Multibot apps and backend. A report describes what failed, such as the feature, site, step, source location, app version, operating system and a random install identifier. It never includes sign-ins, cookies, balances, email addresses or other account details, and IP addresses are not stored.

5. How information is used

Information is used to authenticate accounts, confirm paid or complimentary access, synchronize requested settings and records, operate remote control, provide support, prevent abuse, diagnose reliability problems, secure accounts, comply with legal obligations, and improve product performance.

6. Sharing

Multibot does not sell personal information. Information is shared with service providers only as needed to operate the service, respond to valid legal requests, protect users and the service, complete a business transaction, or when you direct us to share it.

7. Retention

Account and subscription records are retained while an account is active and as reasonably necessary for billing, security, dispute resolution, legal compliance, and backup integrity. Operational checkout records are pruned after seven days and processed webhook records after ninety days under the current service configuration. Local data remains on your device until removed through the app or operating system.

8. Security

Multibot uses short-lived authenticated sessions, encrypted transport, account-scoped authorization, restricted renderer access, signed billing events, secret redaction, operating-system credential storage, bounded remote-command leases, and verified software-update artifacts. No system can guarantee absolute security.

9. Your choices

You may update account factors through Clerk, update payment methods or cancel through Stripe's billing portal, remove local profiles, and request access to or deletion of applicable account data through support. Some records may be retained when required for fraud prevention, billing, legal compliance, or dispute handling.

You can turn off error reports in Account & security on desktop or in Settings in the mobile app.

10. Children

Multibot is not directed to children. Users must be at least eighteen and meet any higher age requirement that applies where they live or use supported third-party services.

11. Changes

Material changes will be reflected by an updated effective date and, when appropriate, an in-product or account notice.

12. Contact

Privacy and data requests may be submitted through the Multibot support page.

Referral program

When you follow a referral link, we use a first-party cookie lasting up to 30 days to remember the referral. We record account attribution, qualifying payment references, reward and payout history, accepted terms, and security review signals. We compare protected payment fingerprints and masked bank details to help detect abuse. Referrers see an opaque referral label, reward amount, and status, not the referred customer’s name, email, or payment details. Stripe collects bank and verification information through its hosted forms; Multibot stores Stripe references and minimal masked details. Financial and fraud-prevention records may need to be retained after an account is closed. Contact support for privacy requests.