Skip to content
Workspace

Legal

Privacy policy.

What ship.page (Bitgate, Inc.) stores, why, and for how long. The short version: we run an ephemeral hosting service, not an ad network — we collect the minimum needed to operate and bill.

Last updated
On this page

What we store

  • Drop content and metadata. The files you deploy, plus the drop's slug, timestamps, file count, owner (if authed), and expiry. Anonymous deploys are not tied to any identity.
  • Account data (only if you sign in): your sign-in identity (Google, Apple, or GitHub) via Firebase — a Firebase user ID, your email address, and an internal account ID.
  • Password protection. Protected drops store a salted password hash, not the password. Unlocking sets an essential, host-only browser session cookie valid for 12 hours; it is not used for analytics or cross-drop tracking. Passwords are not included in API responses or telemetry.
  • API keys. Stored only as a SHA-256 hash plus a short display prefix. We cannot recover a lost key.
  • Email preferences. Per-category opt-in/out flags for your account.
  • Billing state. Payments are processed by Stripe; we never see or store card numbers. We store only your plan status, keyed by account ID.
  • Drop visit telemetry. When someone views a drop, we record server-side: the slug, the path, the referring site's hostname, and the visitor's country. No IP addresses, tracking cookies, user accounts, or third-party analytics scripts are recorded or added for this telemetry. Retained 90 days, then deleted.
  • MCP/API telemetry. Which API/MCP methods were called, client name and version, and whether the call was authenticated. No payloads, keys, or IPs. Retained 90 days.
  • Marketing-site analytics. The ship.page website itself uses Google Analytics and Simple Analytics. This applies to ship.page only — drops never load our analytics or any third-party script from us.

CSS to Tailwind converter and browser extension

  • What we receive. The converter on ship.page receives the address you enter. The browser extension only works on the tab where you click it: it sends that page's address, title and window width, plus a snapshot of the page as your browser shows it (its HTML, styles, images and anything typed into forms, except password and payment fields).
  • How long we keep it. A snapshot is deleted as soon as its conversion finishes or fails. Converted pages and their before and after screenshots are kept for 24 hours so you can review and export them, then deleted. Nothing is published unless you deploy it yourself.
  • Bot checks. Conversions without an account are checked with Cloudflare Turnstile, loaded from ship.page inside the extension's panel. The check runs for each conversion and is usually invisible.
  • Connecting your account. Signing in from the extension creates an API key for it. The extension keeps the key in its own browser storage, and we store it hashed like any other API key. Disconnecting the extension deletes the key; you can also revoke it from the dashboard.
  • What the extension doesn't do. It only reads a page when you ask it to convert that page, doesn't run in the background on other sites, doesn't read your browsing history and contains no ads or third-party analytics. Its requests include the browser name and extension version, which we count to see which browsers people use.

Tailwind to CSS converter

  • What we receive. The address you enter. We load that public page to convert it.
  • Naming classes. To give the CSS classes readable names, we send the page title and address plus short excerpts of the page (tag names, nearby headings, the first words of element text, ARIA roles and labels, and CSS declarations) to OpenAI through OpenRouter. No account details are sent.
  • How long we keep it. The converted page and its two screenshots are kept for 24 hours so you can review and export them, then deleted. Nothing is published unless you deploy it yourself.
  • Exports. Each export is recorded against your account to count your free exports for the month.
  • Bot checks. Conversions are checked with Cloudflare Turnstile. The check runs for each conversion and is usually invisible.

What we never do

We do not sell data, run ads, fingerprint visitors, or track people across drops. We do not inject anything into drops on a Pro account. For other drops viewed in a browser, we display a small badge that loads nothing from our servers, sets no cookies, and runs no analytics. If a visitor closes the badge, it stores a flag in sessionStorage so it stays closed for that session. Clicking the badge goes through ship.page, which records the click (which drop, which badge style, and the visitor's country; kept 90 days) and sets a first-party ship.page cookie for 30 days, so we can see whether that visit led to a new drop, an account, or a Pro checkout. Drop URLs may be checked against automated threat lists (such as Google Safe Browsing) to detect abuse like phishing and malware; drop content is never used for advertising or profiling.

Who processes the data

  • Cloudflare — edge hosting and file storage (drops are served from Cloudflare's network, which keeps its own standard edge logs), plus page rendering and Turnstile bot checks for the CSS to Tailwind and Tailwind to CSS converters;
  • OVH — database hosting, located in the EU;
  • Stripe — payment processing;
  • OpenAI, through OpenRouter: naming CSS classes for the Tailwind to CSS converter, from short page excerpts;
  • Google (Firebase) — sign-in for accounts;
  • Google Analytics and Simple Analytics — marketing-site analytics only.

Retention

Anonymous-drop rows and files are deleted after expiry plus the 30-day private recovery window. Owned expired files are retained for 90 days. Visit and API telemetry are deleted after 90 days. CSS to Tailwind and Tailwind to CSS conversions are deleted after 24 hours, and extension page snapshots as soon as their conversion ends. Account data is kept until you ask us to delete it. Removed (451) drops stay removed.

Your rights

You can request access to, correction of, export of, or deletion of your personal data at any time — email bart@bitgate.com from the address on your account. Deleting your account removes your API keys and paid drops. You can also revoke API keys yourself from the dashboard at any time.

Security

All traffic is TLS-encrypted, API keys are stored hashed, and drops are isolated from each other on separate subdomains. Report security issues to abuse@bitgate.com.

Changes

We may update this policy as the service evolves; the "last updated" date below tracks that. Material changes will be called out on this page.

Bitgate, Inc.Terms of service