YOUR WORK STAYS YOURS

Privacy

This policy describes how Orgbit handles information for its website, desktop licensing, and account services. For account and privacy requests, contact Orgbit at support@orgbit.app.

Local workspace

Orgbit stores workspace content locally. Salesforce CLI manages Salesforce authentication. The licensing service does not receive Salesforce credentials, org contents, recipes, queries, Apex code, or results. Operations you request can connect to Salesforce and your chosen recipe sources.

Account and licensing information

We use your email address, account ID, purchase and refund records, update coverage, and activated computer records to provide the product. Activation records include a device public key, computer name, operating system, and activation date. New purchases use Polar license keys without an Orgbit account. You can remove computers in Manage license. Your key is sent securely for validation and stored encrypted in the desktop app’s system-backed secure storage; the website does not persist it.

Service providers

Cloudflare hosts the website, account service, database, and downloads. Resend delivers verification emails. Polar acts as merchant of record for new purchases and receives billing information you provide at checkout. Its handling of payment data is described in the Polar privacy policy. Existing Lemon Squeezy test purchases continue to use Lemon Squeezy for license validation and receipt access. OpenPanel is self-hosted by Orgbit for product analytics. Orgbit does not store complete card details. Better Auth is the authentication software running in our service.

Product analytics

The public landing page uses our self-hosted OpenPanel instance for page views and predefined actions. Free CTA clicks, installer-link clicks, installer requests and app starts are separate measurements; a download request is not an installation. We do not record account-page or desktop replays. Automatic outbound URL capture and public-page replay are paused pending privacy review.

When enabled in desktop Preferences, Orgbit sends predefined product-action events with app version, platform and Free/Paid status. First start, first successful org connection and later-day return signals use local flags; no persistent install or session identifier is transmitted. Cohort retention remains disabled pending a separate privacy review. Events exclude Salesforce IDs and records, org names, usernames, URLs, queries, recipes, emails, license keys, credentials, payment details and issue reports.

Optional server analytics count checkout creation/errors and verified settled purchases, with durable retry deduplication. Payment and license records are kept separately to provide the purchased product. Website choices are available in the footer; Do Not Track and Global Privacy Control also disable optional analytics. A preference cookie carries this choice to downloads. Analytics providers may process request metadata such as IP address and user agent; we do not use it as a persistent installation identity or claim that remaining traffic is verified human.

With optional analytics allowed, a 30-minute cookie keeps predefined campaign and suspected-scanner labels across site navigation; it contains no person or device identifier. Existing checkout references may be kept separately for up to seven days without another checkout, solely to revoke optional checkout events when you opt out. They are never sent to analytics or used for retention. Opt-out clears campaign labels and asks the server to revoke known pending checkouts in this browser. A failed request is visibly marked for retry. Clearing these references or using another browser can prevent revocation of an earlier checkout; server analytics remains disabled pending review of this limitation and retention policy.

Cookies, security, and communications

Legacy account pages use necessary session cookies. The purchase page keeps a checkout request identifier in session storage to prevent duplicate checkout creation. We process request information, including IP addresses, to secure the service and limit abuse. Verification codes expire quickly and are stored as hashes. We send account and purchase-related messages; Orgbit does not use advertising analytics.

Retention and deletion

We retain account and entitlement records to support perpetual licenses, recovery, and billing. Expired sign-in and activation records are cleaned up automatically. Billing records may need to be retained for legal or accounting obligations. Request account deletion from account settings or through support. Deleting an account does not delete local files on your computer.

Optional reports

Issue reports are separate from licensing. Reports and attachments are sent only when you submit them after reviewing their contents.

Your choices

Manage license lets you review purchases and remove computers using your key. Existing legacy accounts also support email changes, session management, and deletion requests. Eligible activated desktop releases continue working offline; license refresh checks can update coverage or discover revocation when connected. Contact the seller’s published support address to request access or correction of account information.