Privacy Notice

Effective August 31, 2026

LogicHauler LLC operates LogicHauler for adults in the United States. This notice explains the information used by the software, website, account services, Teams features, support system, and prepared billing integrations. Contact [email protected] with privacy or data-rights questions. Our mailing address is 3007 THORNCREST DR, ORANGE PARK, FL 32065.

Local-first file processing

LogicHauler's supported file workflows are centered on files, folders, photos, or storage locations that you select or grant the app access to. Desktop and mobile processing occurs on your device for supported operations. A paired transfer can send selected content across a local network to a trusted paired device. The account control plane is not designed to routinely upload or store the private payloads of selected files.

Local-first does not mean that LogicHauler uses no network services. Account, Teams, support, entitlement, billing-provider, update, and security functions can communicate with services described below.

Information we process

Depending on the features you use, we may process:

• Account and authentication information, such as email address, account identifier, display name, authentication state, and security-related account events.
• Preferences, including product-update opt-in, security-notice preference, and optional receipt-summary sync choice.
• Device-link metadata, such as an opaque device identifier, platform, user-selected label, and link or revocation state. Account links do not provide cloud browsing of local files and are separate from local cryptographic pairing trust.
• Optional receipt-summary metadata that you choose to sync. The control plane is designed to exclude local paths, filenames, file contents, content hashes, pairing secrets, device fingerprints, local IP addresses, and card data from those summaries.
• Teams metadata, such as organization and project names, membership and role records, seat and entitlement facts, opaque checkpoint records, invitations, and privacy-minimized audit facts.
• Support information, such as name, email address, request category, subject, message, optional project information, update opt-in, status, and creation time. Do not submit passwords, tokens, private keys, card numbers, pairing secrets, private file contents, or raw logs.
• Billing and entitlement facts if a purchase channel is activated, such as provider, provider-side identifiers or hashes, plan, status, price and currency facts, paid-through period, cancellation state, and provider event results. LogicHauler does not implement storage of full card numbers in its control-plane schema.
• Website request and anti-abuse information processed by infrastructure and Cloudflare Turnstile, which can include network, browser, device, challenge, and security signals under the provider's practices.

Why we use information

We use information to authenticate accounts, provide requested features, maintain preferences and device links, verify entitlements, support Teams collaboration, receive and manage support requests, investigate security or abuse, comply with law, maintain service integrity, and communicate about requested services. Promotional or launch-update email is separate and requires the explicit update opt-in represented by the product.

Service providers and recipients

Source-proven integrations include:

• Supabase for authentication, database-backed account and Teams metadata, Edge Functions, support requests, and related control-plane operations.
• Stripe for prepared direct Web billing, subscription, provider-event, cancellation, and refund-reconciliation functions. Public Web commerce is currently off.
• Apple and Google Play for conditional mobile purchase, subscription management, provider verification, and entitlement state when those channels are activated.
• Resend for optional service-email delivery and internal notification when configured. A support submission does not currently promise a submitter confirmation email.
• Cloudflare for Turnstile anti-abuse checks. Repository materials describe Cloudflare Pages preparation but do not prove a production hosting deployment.

Providers may process information for their own security, fraud prevention, legal, account, and operational purposes under their terms. We may also disclose information when required by law, to protect rights and safety, in a business transaction subject to appropriate safeguards, or with your direction.

Retention

We retain information only as reasonably needed for the purposes described, service integrity, dispute handling, security, accounting, and legal obligations. The current implementation does not establish one universal retention period. Different records and providers have different lifecycles. We do not state an exact deletion deadline that the implementation cannot prove.

Account deletion and local data

Authenticated users can initiate account deletion in the Web, desktop, and mobile applications. The Web account area also provides an external mechanism that does not require reinstalling the mobile app. Organization owners must transfer or close owned organizations before deletion can proceed. The server deletes identified account metadata and requests deletion of the authentication user when the operation succeeds. Technical, integrity, provider, legal, security, fraud-prevention, accounting, or dispute records may be retained where reasonably necessary or required.

Account deletion does not delete files or receipts stored only on your devices and does not revoke separate local cryptographic pairing trust. Manage those items on the relevant device. Deleting an account also does not by itself cancel an Apple, Google Play, or other provider subscription.

See the Account Deletion policy for the operational steps.

Choices and requests

You can update available preferences in the product, decline promotional updates, request an account metadata export, initiate account deletion, and contact [email protected] about access, correction, deletion, or other applicable rights. We may need to verify the request and may deny or limit it where law permits. Rights and procedures vary by jurisdiction.

Security

We use technical and organizational measures intended to reduce risk, including server authorization boundaries, scoped control-plane data, integrity checks, and privacy-safe diagnostic rules in supported workflows. No system is perfectly secure. Report suspected vulnerabilities to [email protected] and follow the Security Reporting policy.

Children

LogicHauler is a general-audience product for people age 18 or older. It is not directed to children. Do not create an account or submit personal information if you are under 18.

United States service and changes

The initial public launch territory is the United States. Service providers may process information in locations described by their terms and configurations. If we materially change this notice, we will publish a new effective date and provide additional notice when required.

Contact

Privacy and data-rights contact: [email protected]

General support: [email protected]

Postal address: LogicHauler LLC, 3007 THORNCREST DR, ORANGE PARK, FL 32065

Data and Local Processing Summary

Selected-file payload boundary

• Desktop workflows use files, folders, or approved local roots selected by the user.
• Mobile workflows use app-accessible data and explicit Files, Photos, document-picker, or Android system-picker grants.
• Supported inspection, organization, conversion, receipt, and storage-analysis work runs on the selected device.
• A local-network transfer sends selected content only to an authenticated paired session. Transport and feature limits are described by the current product, not by a universal encryption or compatibility claim.
• Managed converters create separate outputs and preserve source files for supported profiles. Converter availability, integrity, licensing, format, and fidelity limits still apply.

Network control-plane boundary

LogicHauler uses a network control plane for account authentication, profile and preference metadata, opaque account-device links, optional data-minimized receipt summaries, entitlements and provider billing facts, Teams organization metadata, support requests, and authorized operations.

The canonical control-plane schema is designed not to store local paths, filenames, private file payloads, content hashes from local files, local IP addresses, pairing material, device fingerprints, or card data in its core account tables. This boundary does not mean that no data leaves a device. Information intentionally submitted to support, entered as Teams names, used for account authentication, or sent to a purchase provider is network data.

Receipts and recovery

Local receipts can record operation identifiers, file-related facts, outcomes, and timestamps needed for review. Optional cloud receipt summaries are deliberately narrower and do not contain the private file payload. A receipt is technical history, not identity or ownership proof. Recovery is conditional on operation type, current state, available source data, and validation checks. It is not universal or guaranteed.

Account deletion separation

Account deletion acts on account and control-plane data through the server request pipeline. It does not delete local files, local-only receipts, or separate cryptographic pairing trust on a user's devices. Provider, security, accounting, legal, fraud-prevention, or dispute records may follow separate retention duties.

For details, see the Privacy Notice, Account Deletion policy, and Third-Party Notices.