Privacy Policy
Last updated: 2026-10-12 · Version 4
This notice covers LogiShell websites, the LogiShell store, account services and clients. Operator details: LogiShell LTD, registered in England and Wales, company no. 17040399. Registered office: 2nd Floor College House, 17 King Edwards Road, Ruislip, London, HA4 7AE, United Kingdom. For privacy questions and rights requests, contact hello@logishell.com.
1. Our role
We act as controller for account administration, website enquiries, service security, billing and our own product operations. Where an organisation directs how personal data in its workspace is processed, it may be the controller and LogiShell may act as its processor. Contact your workspace administrator for those instructions and contact us to discuss a data processing agreement before entrusting data that requires one. This notice is not a signed data processing agreement.
When you buy a plan or a hosted server, the sale is made by Paddle as merchant of record (see section 4). Paddle is an independent controller of the data it needs to take payment, issue invoices, calculate tax and prevent fraud, under its own privacy notice.
2. Information and sources
| Information | Source and purpose |
|---|---|
| Account details | Email, name, avatar, identity-provider identifiers and connected wallet addresses supplied by you or your chosen sign-in provider; used to authenticate and manage your account |
| Workspace content | Files, graphs, messages, prompts, outputs, attachments and related metadata that you upload, sync, share or submit for processing |
| Connected resources | Device identifiers, presence, permissions, integration configuration and credentials needed for features you enable |
| Hosted servers | Server identifiers, addresses, specification, region, status and the content you place on a server you rent through the Service; used to provision, bill and operate the server |
| Operational records | IP address, browser/client information, timestamps, request and security records needed to deliver and protect the Service |
| Usage and billing | Model/resource usage, charges, plan and entitlement status, payment provider references (customer and transaction identifiers), invoices and payment status needed for billing, limits and accounting. We do not receive or store your card number |
| Communications | Support requests, feedback, reports about store listings, and the email address and preferences you submit for product updates |
| Optional telemetry | Allowlisted diagnostic and feature-use events when you enable the corresponding setting; these event fields exclude file, prompt and terminal contents |
| Error and crash reports | When you enable Diagnostics, a client that fails sends the error message, stack trace, the module and route where it happened, the app version and the operating system. Reports are grouped by the shape of the error and counted, so a repeated fault is one record, not thousands. Before a report leaves the device, web and file addresses are cut back to their path, home directories become ~, and anything shaped like an email address, an API key or a bearer token is replaced with a label. A stack trace can still quote the code around a failure, so this stays off until you turn it on. Without Diagnostics, a client sends only the module, the error code, the app version and a count: no message, no stack, no route (see the next row) |
| Service counters | Counts of how many browsers or clients reach a step (opened the app, saw the sign-in screen, signed in, opened a project, asked the assistant) and of the shape of errors (module and code). These counts carry no identifier: no account, no device or browser id, no IP address and no country are stored with them, and nothing is written to your device for them. They tell us how many, never who, and are kept whether or not you enable the optional settings above |
Local resources are not all automatically uploaded merely because you install a client. What leaves a device depends on the sync, assistant, sharing and execution features you use. Do not put secrets or unrelated personal data in feedback or support messages. Network requests may carry technical identifiers even when a telemetry event contains no content; “content-free” does not mean every part of processing is anonymous.
The store at store.logishell.com can be browsed without an account. It keeps ordinary server logs (IP address, request, time) for security and capacity for a short period, and one value in your browser’s local storage so the “add to LogiShell” button can bring you back to the card you chose. It sets no cookies and uses no analytics.
3. Purposes and legal bases
Where UK GDPR or EU GDPR applies, we rely on:
- Contract: creating and operating accounts, carrying out requested processing, delivering paid plans, hosted servers and usage credits, and responding to service requests.
- Legitimate interests: protecting accounts and infrastructure, preventing abuse and payment fraud, maintaining reliability (including the identifier-free service counters described in section 2), handling business enquiries and reports about store listings, and establishing or defending claims. We consider the impact on individuals; you can object to processing on this basis.
- Legal obligations: accounting, tax, valid legal demands, consumer-protection record keeping and other applicable duties.
- Consent: optional diagnostics (including automatic error and crash reports), optional product analytics, and product-update emails you request. These choices are separate from accepting the Terms. Refusing or withdrawing them does not prevent core service use.
Optional diagnostics and analytics start off for new choices in every region. Change them in Settings → Privacy. Withdrawal affects future consent-based processing and does not invalidate earlier lawful processing. Essential security and billing records continue on their separate legal bases. Ask us to stop product-update emails at hello@logishell.com; accepting the Terms alone does not subscribe you.
4. Who receives information
We disclose information only as needed for the relevant purpose:
- Infrastructure providers, including Cloudflare, deliver hosting, edge services, storage, network security (including the Turnstile anti-bot check on public forms), transactional email and real-time communications (calls) used by the Service. Our websites load fonts and scripts from our own domains, not from third-party font or analytics networks.
- Paddle (Paddle.com Market Ltd, United Kingdom, and its affiliates) is the merchant of record for plans and hosted servers. It receives your name, email, billing country and payment details directly at checkout, and sends us the plan, status and references we need to grant your entitlement. Paddle's privacy notice is at paddle.com/legal/privacy.
- Hosting providers supply the machines behind hosted servers you rent: data-centre operators in the European Union (such as Hetzner Online GmbH, Germany and Finland) and in the United States and other regions (such as Vultr), as named when you order. They process the server's technical data and the content you place on it to run the machine.
- Where usage credits are sold, the payment provider named at purchase processes the payment; we receive the amount, status and a reference.
- The AI provider selected for your request, such as Anthropic, OpenAI or Google, receives the prompts, context and attachments submitted to that model. Local models and user-configured endpoints have different processing paths. Review the provider and endpoint before sending confidential data; provider retention and policies depend on that provider and your account arrangement.
- Identity providers such as Google, GitHub or Apple process sign-in requests when you choose them. Connected services and plugins receive information within the access you grant.
- Public blockchain networks and your own wallet provider receive the transaction data needed for wallet functions you use, such as a payment to a developer in the store. Transactions on a public network are visible to anyone and cannot be erased by us.
- Developers of store listings receive reports about their listing that we forward, without your contact details unless you include them, and payments you choose to send them directly.
- Workspace members, administrators and link recipients receive information you share with them. Publicly published information can be copied by others.
- Authorised support personnel, professional advisers and authorities may receive information where necessary for support, compliance, security or legal claims. In a business reorganisation, information may transfer subject to applicable data-protection requirements.
We do not sell personal data, do not share it for cross-context behavioural advertising, and do not use advertising trackers on the landing page or the store. The list above describes recipients by function; it is not a representation that every optional integration is a contracted subprocessor. Business customers can request details of the providers and contractual arrangements relevant to their deployment at hello@logishell.com.
5. International processing
Infrastructure and external providers may process data outside your country, including in the United States. The applicable locations depend on the feature and provider selected; a hosted server lives in the region you choose at order. Where regulated transfers require safeguards, the relevant transfer must be covered by an applicable adequacy decision or contractual safeguards such as EU Standard Contractual Clauses and the UK Addendum or IDTA. Contact hello@logishell.com for the safeguards and a copy of relevant information for your deployment. This notice does not itself establish a transfer agreement or promise that data remains in a single jurisdiction.
6. Storage, encryption and security
Access controls and encryption protect information, but no system can guarantee absolute security. Workspace access restrictions are different from end-to-end encryption. Only features explicitly identified as client-side encrypted provide that specific property. We may still process associated ownership, size, timestamps and access metadata. We cannot recover encryption keys we do not hold. Once you decrypt content and send it to a provider or recipient, their processing applies.
Keep credentials and recovery methods secure. Contact hello@logishell.com about a suspected security issue. Do not send passwords or recovery phrases in a report.
7. Retention and deletion
We keep personal data only as needed for its purpose and applicable obligations. Retention depends on the record and feature:
| Category | Retention criteria |
|---|---|
| Account and hosted content | While your account or requested workspace storage is active; following a deletion request, subject to shared-workspace obligations, recovery copies and legal exceptions |
| Hosted server content | While the server is paid for, then through the stated grace period after cancellation (at least 7 days); deleted afterwards and not recoverable |
| Security and operational records | For the period needed to investigate incidents, prevent abuse and maintain reliability; longer where a specific incident or legal claim requires preservation |
| Optional telemetry and consent records | Telemetry for the relevant diagnostic or measurement purpose; consent and withdrawal records as needed to demonstrate and honour your choice |
| Error and crash reports | While the fault is being investigated and for a limited period after a fix ships, so a regression can be recognised as the same fault; records are grouped by error shape rather than by session |
| Billing and accounting | For applicable statutory accounting/tax periods (normally six years in the UK) and resolution of payment disputes |
| Support, reports and updates | Until the enquiry or report is resolved or subscription withdrawn, with limited records where needed to honour opt-outs, show how a report was handled, or resolve disputes |
| Device storage | Until expiry, replacement or removal by you as explained in the Cookie Policy |
A deletion request is not a promise that every system or backup is erased instantly. We will explain any lawful retention exception and applicable timing when handling your request. Local copies on your devices and copies retained by independent recipients require separate removal. Public blockchain records, if you use those functions, cannot be erased by us.
8. Your rights
Depending on applicable law, you may request access, correction, deletion, restriction, portability, object to legitimate-interest processing, and withdraw consent. Email hello@logishell.com from your account address where possible, stating what you need. We may request proportionate verification and clarification. We normally respond within one month under UK/EU GDPR; if a lawful extension applies, we will explain it within that period. Requests are normally free.
You may complain to the UK Information Commissioner or your local data-protection authority, including in the EEA. You do not need to contact us first. For organisational content, we may refer the request to the controller and assist them. We cannot export readable content where we possess only ciphertext and no decryption key.
Residents of US states with privacy laws (such as California) have the rights described above to the extent those laws apply, exercised through the same address. We do not sell personal information or share it for targeted advertising, and we do not use sensitive personal information for purposes other than providing the Service. We will not discriminate against you for exercising a right. You may appoint an authorised agent; we will verify the request with you.
9. Cookies and similar technologies
Read our Cookie Policy for session/security cookies, browser storage, durations and controls. Optional analytics consent is separate from essential sign-in storage. Clearing browser storage does not withdraw the server-side telemetry choice for an account: change that choice in Settings → Privacy.
10. Children and automated decisions
The Service is intended for people aged 16 or older, subject to any higher local eligibility requirements. Contact us if you believe a child has provided data contrary to these requirements. The Service provides automation tools; customers are responsible for the decisions they configure and their duties to affected individuals. We do not make decisions with legal or similarly significant effects on you by solely automated means, except fraud and abuse controls applied by payment and infrastructure providers, which you can challenge by contacting us. Contact us for information or to challenge an account restriction affecting you.
11. Changes and contact
We publish dated versions and bring material changes to account holders’ attention through the Service or other appropriate communication. A new consent-based purpose requires a new choice before that processing starts. Contact: hello@logishell.com.