Skip to content
littleworks

Explore the documentation

Meet LittleworksA little backend for what you’re building on Shopify.Littleworks or your own appWhat it takes to give a Shopify feature a backend: with Littleworks, or with a custom app you build and run yourself.Connect to LittleworksChoose the CLI, a plugin, or a remote MCP connection.CLIConnect from your terminal with Shopify approval and no manual tokens.Claude pluginThe Littleworks MCP connection and agent guidance in one package.OpenAI pluginThe Littleworks MCP connection and agent guidance in one package.MCP with OAuthConnect a compatible client directly, without a marketplace plugin.Build with an agentThe operating guide for agents building on Shopify with Littleworks.Write a workA JavaScript handler, a small manifest, and a version you test and then publish.Keep secretsEncrypted credentials, shared across your store’s works.Call external servicesMake public HTTPS API requests from a work using http.fetch().Store dataDocument collections with a small API, scoped automatically to the work that uses them.Call ShopifyCall Shopify’s Admin and Storefront GraphQL APIs with credentials held by Littleworks.Store filesKeep uploads such as artwork and photos in the merchant’s Shopify Files, uploaded by the browser straight to Shopify.Expose an endpointConnect an existing frontend to a work through a small JSON API.Customer access and invitationsRequire a signed-in shopper or a narrow, expiring invitation before a work runs.RecipesUseful things to build for your store, with the backend already taken care of.Product reviewsCollect customer reviews, verify purchases, and publish approved content directly into your Shopify theme.Customer wishlistsGive signed-in customers a persistent list of products they can revisit across devices.Customer quote requestsCollect a customer’s products, quantities, and requirements without turning a request into an order.Back-in-stock alertsCollect confirmed signups on sold-out variants, email them through your own provider when stock returns, and see every signup and send in your admin.Transactional emailSend email from your works through your own provider, never twice for the same thing, and see what was sent and what failed.Build a merchant pageDescribe your records and what merchants do with them; Littleworks renders a native Shopify admin page.Run works on their ownRun a work when something happens in the store, on a schedule, or from a Shopify Flow workflow.Run background jobsQueue runs for later or in the background: fan out to thousands of customers, import in pages, follow up days later, and retry what fails.MCP tool referenceTools to inspect, deploy, run, and organize the backend for a connected store.Usage and allowancesSee what your works use, how much capacity remains, and when allowances reset.Inspect and troubleshootFind the relevant run, understand the failure, and make the next change deliberately.Limits and securityThe current runtime boundaries, data isolation model, and execution allowances.
Shopify admin
Littleworks · Policies

Privacy policy

What Littleworks processes, why it is needed, and the controls available to you.

Effective September 26, 2026

Who operates Littleworks

Littleworks is operated by Benjamin David Kovacs (“Littleworks,” “we,” or “us”). This policy covers littleworks.app, our Shopify app, hosted works, and agent connections through our plugins, MCP server, and CLI. Contact admin@littleworks.app about privacy or this policy.

Merchants decide what their works do and what information they collect. When a merchant uses Littleworks to process customer information, we process that information to provide the infrastructure they configure. If you are a customer of a store, contact that merchant first about its use of your information; we can help the merchant handle a verified request.

Information we process

  • Store and connection information: store name, myshopify.com domain, internal store identifier, approved Shopify scopes, installation status, encrypted Shopify access credentials, and connection records. Connection records include the agent application, approving Shopify user identifier, redirect addresses, authorization status, and timestamps. Agent tokens are stored as hashes where used for verification; temporary authorization material may be encrypted during the connection flow.
  • Store secrets: names, timestamps, and encrypted values you provide for external services. Each store has one set of secrets, and every work in the store can read these values in test and real runs. Values are not returned by settings or agent metadata tools; an agent with deployment access can nevertheless write code that reads or exposes them.
  • Customer access and invitations: Shopify-signed customer identifiers used to verify storefront requests, and derived identifiers used for rate limits and duplicate-request protection. Basic run metadata uses a keyed hash of the customer identifier. Invitation records contain a token hash, encrypted action claims chosen by the issuing work, target work/version, expiration, and use status. The raw invitation token is returned to the issuer for delivery, not saved in the invitation record.
  • Code and configuration: JavaScript source, work names and titles, descriptions, input schemas, permissions, deployment versions, draft/published/paused status and current version, preview URL tokens, and draft/published admin view definitions.
  • Documents and Shopify information: data that works read, create, update, or delete. Depending on the code and granted Shopify scopes, this can include product and order information, customer identifiers, contact details, or other store/customer information the merchant chooses to process.
  • Execution information: work and version identifiers, run identifiers, whether a run was a test run, timestamps, status, duration, request origin category, operation counts, error codes, bounded logs and detailed errors, and external-request hostname, method, status, and duration. External-request diagnostics omit headers, bodies, paths, and query values. Inputs and outputs are processed to run the code and return results; they are not automatically saved as complete run payloads. A work may explicitly store or log some of that information.
  • Website and security information: network and request information needed to deliver and protect the service, such as IP addresses, request paths, browser information, and rate-limit signals. Our hosting provider processes this information; application rate limits use derived identifiers where applicable.
  • Support correspondence: your email address, message, and any information you choose to send when requesting help.

How we use information

We use this information to authenticate store and agent access, run and version works, store merchant-selected data, make permitted Shopify requests, return results, provide diagnostics and support, enforce usage limits, investigate abuse, and comply with applicable obligations. The app does not need your Shopify password. Do not place credentials, payment-card data, government identifiers, health information, or other unnecessary sensitive information in source code, documents, logs, or support messages.

Who receives information

  • Your connected AI provider or agent: when you authorize a connection, it can inspect source, versions, run details, and stored documents, and receive results from works it invokes. This may include customer information if your works process or store it. Document reads are not automatically redacted, and log redaction is best-effort. Only connect clients you intend to give this access to; their own privacy settings and policies govern what they retain or use.
  • External services selected by your works: http.fetch sends the URL, headers, credentials, and body specified by your code to the chosen public HTTPS service. Its response is processed and returned to the work. Test runs also reach real external services. You are responsible for choosing recipients and authorizing what your code sends.
  • Shopify: permitted requests and their variables are sent to Shopify, which returns the requested store data. Shopify also supplies store authentication and installation information.
  • Render: hosts the application and PostgreSQL database, processes permitted Shopify and external requests, and provides operational logs and database recovery.
  • Cloudflare: routes website and app traffic, provides network protection, executes works in isolated runtimes, and processes the input, results, and capability responses needed for execution. It also provides edge and runtime operational logs.
  • Email providers: Cloudflare Email Routing forwards support email to the operator’s Google-hosted mailbox. Those providers process message content and delivery information so we can respond.
  • Authorized recipients and required disclosures: information may be shared with people you authorize or where reasonably required to comply with law, address security incidents, or protect the service and affected users.

We do not sell personal information or provide it to advertising networks. Our app does not send stored data to an AI provider until your chosen client or configured work requests the relevant operation. If you publish an HTTP work, its callers can receive whatever data your code returns; the merchant is responsible for appropriate authorization and output handling.

How long information is kept

InformationCurrent retention
Run logs, detailed errors, and external-request diagnosticsVisible for seven days. A periodic cleanup removes expired log entries, external-request diagnostics, and detailed error content; basic run metadata remains.
Invitation records and encrypted claimsExpire after the duration chosen by the issuing work, up to seven days. Bounded periodic cleanup removes expired records and may take longer under load. Consumed invitations remain until that cleanup.
Hosted documents, source, versions, and basic run metadataKept to support your deployed works and their history until removed through supported controls or a verified deletion request. Documents can have an optional expiration timestamp: expired documents become unavailable immediately and are removed by bounded periodic cleanup, which may take longer under load. Source, versions, and basic run metadata have no automatic age-based deletion period. Deleting a work does not erase its saved versions, run history, or stored documents.
Store secretsEncrypted values are kept until replaced, deleted through Secrets settings, or removed following a verified deletion request. An in-progress run may still hold a value it already read. Uninstalling disables reads. Shopify’s subsequent shop deletion request removes these values from active application storage.
Connection recordsKept to operate and audit the connection until a verified deletion request. A connection grant expires after 90 days, and access tokens after one hour; expiry stops authorization but does not delete all associated records. Pending sign-in requests and expired access-token records are removed during subsequent client-registration cleanup.
Privacy requestsRequest details are encrypted while we handle the request. We remove the payload on completion and retain a minimal receipt for 90 days to avoid processing duplicate deliveries.
Browser authorization cookieExpires after ten minutes and is cleared when the authorization flow completes.
Hosting operational logsCloudflare Workers logs are retained for up to seven days. Render logs expire within 30 days, depending on the hosting plan. We do not intentionally log credentials, authorization query strings, or work inputs and outputs in these logs.
Database recovery copiesRender point-in-time recovery copies expire within seven days, depending on the hosting plan; Render logical exports expire after seven days. Private migration snapshots are kept while needed to validate a migration or restore, and removed manually afterward.
Support emailKept in the support mailbox while needed to resolve and follow up on the issue; there is currently no automatic mailbox deletion schedule. You may request deletion.

Disconnecting an agent revokes its future access; existing works can continue running. Uninstalling the Shopify app disables store access, clears the stored Shopify credentials, and revokes agent grants. Shopify normally sends a shop deletion request 48 hours after uninstall; we then remove that installation’s data from active application storage. A request received for an active or reinstalled shop is held for review to avoid deleting the current installation. Contact us if you need help with deletion.

Deletion from active application storage does not necessarily remove an earlier copy from provider recovery systems immediately. Such copies expire under the provider’s recovery retention. We may retain information when required by law or needed for a specific security or dispute matter and will explain any applicable restriction when handling your request.

Your controls and requests

  • Review works, saved source, data, runs, and agent connections in Littleworks inside Shopify.
  • Pause works to stop new execution, disconnect agents to stop future agent requests, or uninstall the app to disable its store access.
  • Use your connected agent to read, export, correct, or delete documents within your authorized scope. Back up information you need before deleting it.
  • Contact admin@littleworks.app to request access, export, correction, deletion, or help with a privacy concern. We verify that the requester is authorized for the store or information before acting. We handle requests in accordance with applicable law and explain any information we must retain.

Shopify customer data and deletion requests enter a tracked queue with a 30-day deadline. Because merchants choose their own document structure, we work with the merchant to identify relevant information across documents, code, views, invitations, and logs. We verify the scope before disclosing or deleting records and also review relevant support, export, and downstream copies.

Security and processing locations

We use encrypted connections, encrypted stored Shopify credentials and merchant-provided secrets, store-scoped authorization, sandboxed code execution, and access limits. No system or redaction method eliminates every risk. Test runs are not a sandbox: they use the store’s real Littleworks data, and permitted Shopify calls reach the real store.

Render, Cloudflare, Shopify, your selected AI provider, and our email providers may process information outside your country. Littleworks does not currently offer a selectable data-residency region. Each provider’s own terms and privacy policy also apply to its service.

Cookies and changes to this policy

Littleworks uses an essential, short-lived cookie to secure OAuth authorization. Shopify and your chosen AI client manage their own sign-in sessions. The public site does not currently use advertising cookies or a separate marketing analytics tracker.

We will update this page and its effective date when our practices change. If a change requires additional notice or consent, we will provide it as required. Contact us before connecting if anything in this policy is unclear.