What Shipcel keeps, and what it doesn’t

Your apps and their data live in your own Cloudflare account. Shipcel keeps what it needs to sign you in and act for you, counts visitors without cookies, and sells nothing.

Where your data lives

Shipcel is a control panel. The apps you deploy, with their databases, files and logs, live in your own Cloudflare account, under Cloudflare’s terms, not with Shipcel. This page is about the little that shipcel.com itself keeps.

What Shipcel keeps about you

When you sign in with GitHub, Shipcel stores your GitHub user ID and username, and when you joined. It stores no email address and no password: there is no password.

Your workspaces and projects, and a record of each deployment: names, versions, addresses, what Shipcel did and whether it worked.
The GitHub and Cloudflare access you grant, as tokens encrypted with a key held only by shipcel.com, used only to do what you ask: read the repositories you connect, create and deploy Workers, databases and storage in the account you choose, and read your apps’ analytics, logs and plan.
API tokens and CLI sign-in codes as hashes, never in the clear. The shipcel command keeps its token in ~/.config/shipcel/config.json on your computer, readable only by you.
Webhooks you add: their address, and each delivery’s payload, which names the deployment and its outcome.
Invitations: the GitHub username you invite and the role.
Secrets you set for an app go straight to Cloudflare. Shipcel keeps no copy, and never shows them again.

Cookies

The dashboard sets one cookie, __Host-cloudcel_session, which keeps you signed in; signing out removes it. During a GitHub sign-in a second cookie, cloudcel_github_return, remembers for an hour which page to return you to. The public site sets no cookies. There are no advertising or third-party cookies.

How visitors are counted

shipcel.com uses PostHog, cookieless: nothing is stored in your browser, and PostHog counts visitors by a hash of your address and browser that changes every day, so it can’t follow you from one day to the next. Its requests go to shipcel.com/ingest, which forwards them to PostHog in the United States with your address and without your cookies.

On the public site it records the pages viewed and clicks. In the dashboard no PostHog script runs at all: Shipcel’s own code sends which pages are opened and a few named events, such as a project being created, with the framework chosen and nothing that identifies you. Blocking shipcel.com/ingest in your browser stops it, and the site works the same.

Server logs

shipcel.com runs on Cloudflare, which keeps its request logs (your address, the page requested, the status) for up to 7 days. Shipcel reads them only to find faults and abuse.

Nobody buys your data, and nobody else sees it. Shipcel talks to GitHub and Cloudflare with the access you granted, to do what you asked; to PostHog as above; and to the webhook addresses you configure. Shipcel shows no advertising.

Your control

Disconnect GitHub or Cloudflare under Connections: the tokens are erased at once.
Delete a project: Shipcel’s records go; the app and its data stay in your Cloudflare account.
Revoke an API token under API & CLI.
To delete your account and everything Shipcel keeps about you, email info@shipcel.com from the GitHub account you signed in with. Your Cloudflare account is untouched.

A Shipcel you run yourself

This page describes shipcel.com. Someone who runs Shipcel on their own account is its operator and holds that data themselves; their copy sends no analytics unless they set a PostHog key.

Questions

Write to info@shipcel.com. This page was last changed on 28 October 2026, and changes to it are recorded in Shipcel’s repository.