WhiteBeam
Privacy Policy
WhiteBeam for iPhone, iPad, macOS, and Windows is provided by Spaceport Consulting, LLC ("Spaceport," "WhiteBeam," "we," "us," or "our"). This Privacy Policy explains how the WhiteBeam applications and whitebeam.ai handle information.
WhiteBeam features vary by platform and release. A supported application may provide a private Local mode, a Cloud mode that connects to a configured WhiteBeam server, or both. This Policy covers both modes and applies to each described feature when that feature is available in a supported release. Describing a feature does not promise that it is available on every platform. This Policy does not cover an unrelated legacy product.
1. WhiteBeam's privacy model
Local mode
In Local mode, prompts, conversations, memories, attachments, imported content, repository content, and model inference remain on your device unless you intentionally use a feature that requires an external service or choose to export or share information. Local mode does not require a WhiteBeam account and does not use a WhiteBeam server for model inference, synchronization, or cloud fallback.
Cloud mode
Cloud mode connects to the WhiteBeam server you or your organization configures. Account information, prompts, conversations, attachments, memories, generated output, and feature requests used in Cloud mode are transmitted to and processed by that server. The server operator controls its deployment, users, storage, models, connected services, logs, backups, retention, and access policies.
When you use a Spaceport-operated WhiteBeam server, this Policy applies to Spaceport's processing. When you connect to a server operated by an employer, another organization, or another person, that operator's privacy notice and instructions also apply, and requests about information controlled by that operator should be directed to that operator.
The applications do not include WhiteBeam advertising or cross-app tracking. Local mode does not include WhiteBeam analytics or telemetry. A Cloud server may maintain operational, security, access, and audit records as described below or in the server operator's notice.
2. Information stored on your device
Depending on your platform, mode, and the features you use, WhiteBeam may store:
- Prompts, conversations, locally generated responses, drafts, titles, folders, tags, and application settings.
- Memories, preferences, local embeddings, source references, and other organizational information.
- Documents, PDFs, photos, camera captures, attachments, generated media, and other files you import or create.
- Library items, extracted text, metadata, visual observations, provenance, and relationships between retained items.
- Model availability, installation and activation state, subscription-entitlement state, and local diagnostic or recovery state.
- Source titles, links, and brief snippets associated with user-requested Search, Fetch, mapping, or location activity.
- For desktop Code features, local project and conversation records, selected-folder paths and access grants, repository metadata, bounded tool observations, change previews, and records of reviewed operations.
- For Cloud mode, the configured server address, application preferences, and protected session information needed to keep you signed in. The Windows client protects persisted Cloud session cookies with current-user Windows data protection.
WhiteBeam may temporarily index selected repository files in memory and create bounded scratch copies while preparing or validating reviewed changes. Original files and repositories remain in the locations you selected. WhiteBeam does not use local application content to train WhiteBeam or third-party models.
3. Information processed in Cloud mode
When you use Cloud mode, the configured server may process:
- Account, organization, authentication, session, legal-acceptance, subscription, role, and entitlement information.
- Prompts, conversations, responses, memories, files, attachments, repository context, generated media, source references, and feature settings you submit or create.
- Model selection, feature use, request status, token or resource usage, and content-free reliability or performance information needed to deliver and protect the service.
- Network, security, access, audit, and diagnostic information, including IP address, device or client type, request time, status, and identifiers needed to investigate misuse or failures.
- Information received from an external service that you or the server operator connects, such as GitHub, Brave Search, a mapping service, a model provider, or a payment provider.
A Spaceport-operated server uses this information to authenticate users, provide requested features, preserve server-authoritative content, administer entitlements, secure and troubleshoot the service, respond to requests, comply with law, and maintain business records. We do not use Cloud conversations, attachments, memories, or repository content to train WhiteBeam or third-party models.
4. When information leaves your device
Information can leave your device when you use Cloud mode, optional Search, Fetch, location or mapping features, App Store purchasing, Apple-hosted model delivery, GitHub, another provider integration, export or sharing, or the WhiteBeam Support form. Current iPhone, iPad and Mac releases send included Search requests through WhiteBeam’s hosted Search gateway. Other optional Local tools normally connect from your device to the selected service. Cloud requests may go through the configured server and are also subject to its operator’s configuration and notice. The Search gateway does not provide AI inference or synchronize your conversations.
WhiteBeam Search and the Search gateway
Search is optional. In current iPhone, iPad and Mac releases, eligible Mobile+ or WhiteBeam Pro access includes a Search allowance without a personal search-provider API key or separate search-provider subscription. The app shows usage and reset information. When Search is enabled and a request calls for online or current information, the app sends a bounded query through WhiteBeam’s gateway to Brave Search. WhiteBeam does not send every chat prompt to Search. Results are supplied to the on-device model; AI inference remains local.
To authorize included Search, the gateway receives Apple-signed subscription evidence and verifies entitlement with Apple. It processes the product and transaction information needed to verify access and issues a short-lived session token. Spaceport does not receive your Apple Account password or complete payment-card number. Usage is shared across devices associated with the same subscription; a keyed, pseudonymous identifier derived from the Apple original transaction identifier links the usage counters.
The gateway processes search queries and results in memory to deliver the requested service. Its usage database retains counters and pseudonymous identifiers, not raw Apple transaction identifiers, signed transactions, query text, result content, chat history, or raw client IP addresses. The gateway necessarily receives network connection information; short-lived rate-limit counters use keyed hashes of IP addresses. Access logging is disabled for the Search route. These controls do not mean the search provider or destination websites have zero retention.
If you request location-aware Search, a query may include a resolved city, region, place or address. Sharing location-derived place text requires the separate in-app control where offered, in addition to any operating-system permission needed to obtain your location. Current Apple clients do not send raw coordinates to the Search gateway or Brave. You may instead supply a place in your request.
Brave is an independent service and receives queries and ordinary gateway connection information under its own privacy practices. Its current notice describes query retention for up to 90 days for billing and troubleshooting, subject to legal obligations. Review the Brave Search API Privacy Notice and Brave Search API Terms of Use. Included Search does not require you to provide a Brave key or pay Brave separately. Provider retention and legal obligations are governed by its notice; WhiteBeam does not promise provider zero retention.
Some older or other-platform Local releases support a personal Brave key instead of included gateway Search. Where that option is offered, the app identifies it, protects the key using operating-system credential storage, and sends the query and key directly to Brave. Your own account, plan, fees and permitted use then apply separately. Cloud Search may use a key supplied by you or the configured server operator; that operator controls its credential storage and processing. These arrangements do not change the included Search entitlement described for current Apple releases.
Disable Search to stop future Search requests. Enabling Search authorizes relevant future queries until it is disabled; it does not enable Fetch automatically. Source titles, URLs, snippets and available date metadata may be saved locally with a conversation. Deleting local content does not delete gateway usage counters or information already retained by independent services. Cloud source retention depends on the configured server.
Fetch and destination websites
Fetch is optional and separately controlled. In current iPhone, iPad and Mac Local releases, enabled Fetch retrieves a requested public HTTPS page and may retrieve selected Search-result pages. With Fetch off, Search does not retrieve publisher pages from your device. Fetch connects from your device to the destination website and validated redirects; Cloud Fetch connects through the configured server. Those sites receive ordinary network information such as the connecting IP address, request headers, requested address and request time. Their own terms, logs and privacy practices apply.
Local Fetch blocks private-network destinations, checks redirects, applies platform-dependent response-size and context limits, and gives only bounded text excerpts to the model. Fetched page text is temporary model context; source metadata may be retained. These controls reduce technical risk but do not control what a destination website records. Secure Fetch does not use Brave unless you separately invoke Brave Search.
Location and Apple Maps
On supported mobile devices, WhiteBeam requests location only when it is relevant to a feature you invoke and after the operating system presents the applicable permission. Location may be used locally, sent to a configured Cloud server as part of a request, or used to obtain time, place, routing, or nearby-place information. Apple may receive request time, device and software information, search terms, interactions, and authorized location as described in Apple Maps & Privacy and Location Services & Privacy.
Location-derived text is included in Search only for a relevant location-aware request and with the separate place-sharing control where offered. Current Apple Search sends that text through WhiteBeam’s gateway to Brave; a direct-key client sends it to Brave. Ordinary prompts are not sent merely because location permission is available. You may revoke location permission through system settings or disable Search place sharing in the app. Revocation prevents future access or sharing but does not remove information already stored in a conversation or retained by Apple, the gateway, a configured server or another provider.
App Store purchases and subscriptions
Mobile+ and WhiteBeam Pro may be offered as purchases or auto-renewing subscriptions through Apple using the App Store and StoreKit on supported Apple platforms. Available products, billing periods, prices, trials or introductory offers, and included features are shown before purchase and may vary by product, platform, storefront, and release.
While a WhiteBeam Pro subscription remains active, it includes Mobile+ access on supported iPhone and iPad devices. WhiteBeam uses the applicable Apple product, transaction, and entitlement status to provide that cross-product access; Spaceport does not receive your Apple account password or complete payment-card number.
Apple processes these purchases and handles payment credentials and complete payment-card information. WhiteBeam receives the product and transaction information needed to validate purchases, restore access, determine renewal and entitlement status, provide the applicable Mobile+ or WhiteBeam Pro features, and respond to purchase-support requests. Spaceport does not receive your complete payment-card number from Apple.
You can manage or cancel an Apple subscription through your Apple account. Deleting WhiteBeam, WhiteBeam Pro, or locally stored application data does not cancel a subscription. Apple administers App Store billing, refunds, and its own transaction records under Apple's terms and privacy policies.
Access to a TestFlight beta, including a WhiteBeam Pro beta, is administered by Apple under TestFlight and does not by itself create a paid WhiteBeam subscription.
Model delivery
On supported Apple platforms, WhiteBeam uses Apple-managed asset delivery for local model packs. Apple may process device, account, network, download, transaction, integrity, and availability information under its terms and privacy policies. Model weights are application assets rather than user-created content and are kept in Apple-managed asset storage. WhiteBeam stores local installation and activation state; Apple-hosted model weights are not included in WhiteBeam's user-created Local backup.
On Windows, a Local release may obtain a model from a source identified before download in WhiteBeam's approved model catalog. The download host receives ordinary network and request information and applies its own terms and privacy practices. Model files remain separate from Local restore points.
GitHub authorization and repository content
GitHub integration is optional and requires a GitHub account. WhiteBeam accesses GitHub only after you initiate authorization and grant the requested permissions. The current macOS Local integration uses GitHub's device-authorization flow and requests repo, read:user, and workflow scopes. A different integration, where available, may request different access that is shown during authorization. GitHub receives the authorization request, account and session information, requested scopes, and ordinary device and network information under GitHub's terms and privacy practices.
Depending on the feature and action you request, WhiteBeam may process your GitHub login, display name, avatar address, repository names and settings, branches, commits, files, diffs, issues, pull requests, reviews, workflows, and related metadata. WhiteBeam may provide selected repository content to the active model, retain local working copies or bounded task history, and prepare proposed changes for your review.
In macOS Local mode, the GitHub token is stored in Apple Keychain and is not written to a repository, Git configuration, application preferences, conversation, or WhiteBeam server. In Cloud mode, the configured server may retain an authorization token in protected server-side credential storage so it can perform requested operations.
WhiteBeam reads local files only from folders you select through operating-system controls. Selecting or inspecting a local repository does not by itself send its files to GitHub. When you explicitly approve a remote operation, WhiteBeam may send repository coordinates, branch or commit content, issue or pull-request text, comments, reviews, or workflow instructions to GitHub. A change GitHub has accepted is not reversed when you disconnect WhiteBeam.
You can disconnect GitHub in WhiteBeam where that control is available and revoke WhiteBeam's authorization in your GitHub settings. Revocation prevents future access using that authorization but does not delete local repository copies, remove Cloud records, undo remote changes, or delete information already retained by GitHub. Review the GitHub General Privacy Statement and manage authorized applications through GitHub.
5. Permissions and consent
Depending on platform and feature, WhiteBeam may request location, camera, photos, files, selected-folder, local-network, or notification access. Desktop Code features receive access only to folders you select through operating-system controls. GitHub and Brave require separate authorization or credentials.
Permissions are requested in context. You can revoke system permissions in Apple Settings, macOS System Settings, Windows Settings, or other applicable operating-system controls. You can remove a selected workspace, disable Search or Fetch, remove a Brave key, disconnect GitHub, sign out of Cloud mode, or change the configured server. Revocation stops future use of that access but does not automatically delete local content, user-created backups or restore points, original files, remote changes, Cloud content, or information already retained by an external provider.
6. Website and Support information
The public WhiteBeam website provides product information and Support. It does not provide a marketing signup form.
If you submit a Support request, we receive the name, email address, subject, issue description, and optional screenshot you provide. Support may be used for technical, purchase, privacy, accessibility, legal-policy, misuse, or security questions. Do not submit passwords, API keys, access tokens, payment-card information, health records, government identifiers, or other information that is not needed for the request.
Support requests are stored as non-public WordPress administration records. Optional screenshots are placed in access-restricted storage rather than the public WordPress Media Library. Authorized administrators can review requests and download attachments. Permanently deleting a request also deletes its associated screenshot.
The website and its hosting or security infrastructure may process routine technical information such as IP address, browser type, requested page, timestamp, HTTP status, and security events. The origin web server's ordinary logs are generally retained for about 14 days. Records connected to an active security incident, dispute, or legal obligation may be retained longer when reasonably necessary.
To limit automated abuse, the Support form temporarily uses a one-way keyed representation of the submitting network address. The IP address is not stored with the Support request. The website stores your light or dark appearance choice locally in your browser. Public pages do not use WhiteBeam advertising or analytics cookies; authenticated WordPress administrators may receive operational session cookies.
7. How we use information
We use information to:
- Provide Local conversations, memories, Library, model, media, backup, restore, Code, repository, and selected-file features.
- Provide account, conversation, memory, attachment, model, media, and integration features through a Spaceport-operated Cloud server.
- Authenticate and perform Brave, GitHub, Fetch, mapping, or other provider operations that you request.
- Create, validate, restore, and maintain Local backups or restore points.
- Maintain application settings, local content, model availability, and subscription entitlements.
- Process and respond to Support, privacy, security, accessibility, abuse, and purchase questions.
- Operate, protect, debug, and maintain the website, Support system, and Spaceport-operated Cloud services.
- Prevent fraud, misuse, unauthorized access, and security incidents.
- Enforce applicable terms and comply with legal obligations.
We do not sell personal information. We do not share personal information for cross-context behavioral advertising or targeted advertising. We do not use Support submissions, Local content, or Cloud content to train AI models.
8. How information is disclosed
Information may be disclosed to:
- Services you invoke: Brave Search, GitHub, Apple Maps and location services, Apple App Store and StoreKit, Apple-managed model delivery, Windows model-download providers, configured Cloud servers, and public websites or redirect destinations used through Fetch.
- A server operator or organization administrator: when you connect to its WhiteBeam deployment or use an account it administers.
- Service providers: providers supporting Spaceport-operated hosting, storage, networking, security, backups, payments, communications, and administration, only as needed to provide and protect the applicable service.
- Legal and safety recipients: courts, regulators, law enforcement, or other parties when disclosure is required by law or reasonably necessary to protect rights, safety, security, and the integrity of WhiteBeam.
- A successor organization: as part of a merger, financing, reorganization, sale of assets, or similar transaction, subject to appropriate confidentiality and applicable law.
Providers processing personal information on Spaceport's behalf are permitted to use it only as needed to provide and protect the applicable service and are required to protect it consistently with this Policy and applicable law. For an integrated provider selected by Spaceport, we use applicable contracts, platform rules, and provider commitments to require or confirm protection of user information that is the same as or equivalent to the protection described in this Policy. Apple, Brave, GitHub, a server operator, and a model-download host may also act as independent providers; their privacy notices, account settings, and retention practices apply. A public website reached through user-directed Fetch is selected by the user rather than Spaceport, and Spaceport cannot verify that website's protections; review its privacy notice before directing a transfer.
In Local mode, we do not operate a WhiteBeam service that receives ordinary prompts, conversations, memories, imported files, selected repository contents, Brave keys, GitHub tokens, or local model outputs.
9. Retention and deletion
Local information and backups
Local application information remains on your device until you delete it through available controls, remove the Application and its applicable local data, restore a different backup, or it is otherwise removed by operating-system behavior. Deleting a conversation deletes its messages but may not delete an original Library item retained independently or shared with another conversation. Delete the Library item separately when you want to remove that retained copy.
Deleting a memory, Code project, workspace grant, Library item, or other local record removes the Application's associated record according to the available control. Removing a workspace grant stops WhiteBeam from reusing that grant but does not delete the selected repository or its files. Deleting WhiteBeam does not delete original files, repositories, exports, or backups outside its container.
On macOS, a user-created Local backup contains a snapshot of the local database and media vault at the destination you select. It may contain conversations, memories, attachments, Library media, Code records, selected-folder paths or grants, and related metadata. Provider credentials and model weights are not included. Spaceport does not receive or retain that backup. It remains until you delete it from the selected location.
On a supported Windows Local release, a restore point contains the local database and media vault under WhiteBeam's Local data directory. Model weights are excluded. No fixed automatic expiration applies unless the Application says otherwise. A restore point may retain deleted information until you separately remove it or the Local data directory. Uninstall behavior may vary by installer and operating-system settings.
Application data may also participate in an Apple device, iCloud, Windows, enterprise, or third-party computer backup depending on your settings. Deleting the Application or a local record may not immediately delete a copy already in a backup. The backup provider and the person controlling the backup determine its retention and deletion. Restoring a backup or restore point may reintroduce previously deleted information.
WhiteBeam may create temporary files, repository indexes, or scratch work while importing, capturing, processing, or preparing reviewed changes. The Application attempts to remove application-owned temporary material after completion, cancellation, background cleanup, recovery, or restart. Unexpected termination may delay cleanup. Apple-managed model assets remain subject to Apple's asset-management behavior and may be removed or downloaded again without deleting user-created content.
Cloud information
A configured Cloud server retains account and content records according to its operator's settings and notice. On a Spaceport-operated server, active account information and Cloud content remain until you delete them through available controls, the account is closed, or we complete a verified deletion request, subject to security, fraud-prevention, dispute, enforcement, and legal exceptions. We remove eligible active records without unreasonable delay after verified deletion. Deleted information may remain temporarily in backups until those copies are removed through Spaceport's documented backup-retention process.
Deleting Local information does not delete a separate Cloud copy. Deleting Cloud information does not delete a Local export, repository, backup, or restore point. If an organization controls your Cloud account, it may retain or delete information according to its policies and legal obligations.
Search gateway usage records
The gateway keeps pseudonymous usage and rate-limit counters for subscription allowances, abuse prevention and service operation, and prunes expired counter windows. Removing the app or a conversation does not reset a subscription’s shared allowance. These records do not include query text, result bodies or chat history. For a privacy or deletion request, contact WhiteBeam Support; limited records may need to remain where necessary for security, entitlement enforcement or legal obligations.
Credentials and external services
A locally stored Brave key or GitHub token remains in protected credential storage until you remove or disconnect it or operating-system behavior removes it. A provider may invalidate a credential without removing its local copy. A Cloud deployment retains configured credentials according to the server operator's controls. Removing a credential prevents future requests using it but does not delete the provider account or information already retained by the provider.
Support and website information
We retain a Support request and its attachment while the request is active and for up to 12 months after its last activity. We may retain it longer when reasonably necessary for security, fraud prevention, a dispute, enforcement, or a legal obligation. You may request earlier deletion, subject to those exceptions.
Routine origin-server logs are generally retained for about 14 days. Temporary abuse-prevention values expire automatically. Security incident records may be retained longer when reasonably necessary.
Third-party retention
Apple, Brave, GitHub, destination websites, configured server operators, and model-download providers control information they receive under their own retention practices. In particular, Brave currently states that Search API query records may be retained for a maximum of 90 days. Use the provider's account controls or contact it about information it holds.
10. Your choices, consent withdrawal, and privacy rights
Depending on the platform, mode, and feature, you can:
- View and delete conversations.
- Manage or delete memories, Library content, local media, Code projects, and other retained records where controls are available.
- Remove imported files or selected workspaces without deleting the original file or repository outside WhiteBeam.
- Delete macOS Local backups or Windows Local restore points from their storage location.
- Remove a Brave API key and disable Search.
- Disable Fetch.
- Disconnect GitHub and separately revoke WhiteBeam in your GitHub account settings.
- Revoke camera, photo, file, folder, local-network, notification, or location access through operating-system controls.
- Sign out of Cloud mode, change the configured server, delete available Cloud content, or ask the applicable server operator to close or delete an account.
- Manage or cancel a purchase or subscription through the store or account through which it was purchased.
- Export conversations or other records where WhiteBeam provides an export control.
- Remove local application information through available controls or by removing the Application and its applicable local data, subject to backups, restore points, and independently retained files or Library items.
Withdrawal applies to future processing. It does not undo an external action you previously approved, remove a prior Cloud or Local record automatically, or require an independent provider to delete information it may retain for security, billing, legal, or other permitted purposes. Use the provider's controls or contact it for information held in its systems.
Depending on where you live and whether a law applies to us, you may also have rights to request confirmation, access, correction, deletion, restriction, objection, or a portable copy of personal information we control and to learn about categories of recipients. WhiteBeam does not sell personal information, use it for targeted advertising, or profile users for decisions producing legal or similarly significant effects.
Submit a request through the WhiteBeam Support form. We may ask for information reasonably necessary to authenticate the request, such as the email address used for an account or Support submission. If another organization operates or administers your configured server, contact it first for server-held information. If we deny a request, you may appeal through the Support form with the subject "Privacy Appeal." We will provide further complaint information where required by law and will not discriminate against you for exercising a privacy right.
11. Security
WhiteBeam uses administrative and technical safeguards designed for the information it handles. Depending on platform and mode, examples include sandboxed local storage, protected operating-system credential storage, device-only Apple Keychain items, Windows data protection and Credential Manager, security-scoped selected-folder access, bounded temporary workspaces, verified model assets, encrypted network transport, access-controlled Cloud services, restricted Support records, non-public screenshot storage, and administrator access controls.
User-created backups and restore points are protected by the security of the destination, device, account, and backup system you select. A self-hosted or organization-operated server is protected according to its operator's configuration. No device, storage system, or transmission method can be guaranteed completely secure. Protect your devices, accounts, passcodes, credentials, repositories, backups, and configured servers.
12. Children
WhiteBeam is not intended for children under 13, and children under 13 may not use the Applications or submit Support requests. Users who are at least 13 but below the age of legal majority where they live must have permission from a parent or legal guardian. If you believe a child under 13 submitted personal information to Spaceport, use the Support form so we can investigate and delete it where appropriate.
13. United States availability and processing
This version of WhiteBeam is offered for an initial United States launch. Spaceport is based in Oregon. Apple, Brave, GitHub, configured server operators, website infrastructure providers, model-download hosts, and destination websites may process information in the United States or other locations under their own terms and privacy policies. Applicable consumer protections remain available where they cannot lawfully be limited.
14. Changes to this Policy
We may update this Policy when WhiteBeam's platforms, modes, features, providers, or legal obligations change. We will update the effective or last-updated date and version on this page. When appropriate, we may also provide notice in the Application or on the website. Prior published versions are archived.
15. Contact
Spaceport Consulting, LLC 4736 Royal Ave, Unit #17113 Eugene, Oregon 97402 United States
Submit privacy questions, rights requests, deletion requests, and appeals through the WhiteBeam Support form.
Review the WhiteBeam Terms of Service.