WarehousesCloud
Back to the website
Updated 6 November 2026

Privacy policy

How the current Warehouses Cloud application stores and uses account, company, and file data.

Information in your workspace

Clerk manages sign-in credentials, primary-email verification, and authentication sessions. Warehouses Cloud stores your account name and email, company memberships and roles, and a mapping from the verified Clerk identity to your internal workspace user ID. For older workspace accounts, the existing salted password hash is retained for a one-time ownership check when linking that account to Clerk; subsequent sign-ins use Clerk.

Workspace data includes products, warehouses, stock quantities and movement history, supplier and customer details, purchase and sales records, invoices, and uploaded files. Only enter information that you are authorized to use for your company.

Storage and use

Cloudflare Workers handles application requests. Company records, identity mappings, current-company selection, and file metadata are stored in Cloudflare D1. Uploaded file contents are stored in a private Cloudflare R2 bucket. Clerk handles authentication; Cloudflare retains the business records and the membership checks used for workspace operations, file access, and reports.

The browser stores your selected theme locally and your language preference for the current browser session. Business records and uploaded file contents are stored on the server, not in those preference settings.

Company access

Requests for records and files check the signed-in account and its current company membership. Members can access the companies they are authorized to join. Roles determine whether they can read or change records, files, company settings, and team access.

Company owners and administrators control team access. Share invitation codes only with the intended teammate and tell your company administrator when access should be removed.

Sessions and preferences

Clerk manages authentication cookies, session expiry, and sign-out. Each workspace API request requires a Clerk session token verified by Cloudflare Workers and an active company membership. A stored current-company selection does not authenticate a request on its own. Session duration follows the Clerk configuration.

Theme and language preferences do not grant access to company data. You can clear browser preferences independently of your server-side records.

Keeping, updating, and removing data

Business records and files do not have an automatic expiry in the current application. Authorized members can update records or delete records that are not required by linked data. Stock movement history is retained as an immutable ledger.

A successful file deletion removes the active stored object and its application record. Removing a Clerk account does not automatically remove historical company records or files. To request a correction or discuss removal of company information, contact the owner or administrator of your workspace. Some changes require preserving historical references.

Service providers and changes

Clerk provides identity, sign-in, email-verification, and authentication-session services. Cloudflare provides the hosting, database, and file-storage infrastructure. Your company is responsible for the information it enters and for any additional notices required for its use of the workspace.

This page describes the current product. It should be updated when payment, analytics, or other data-processing services are added or changed.