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 aren't tied to an account, but if you give an email for the claim link, we store it with the drop. Every deploy, redeploy and append also records the uploader's IP address and the location and network it maps to, the user agent, the other request headers (never passwords, API keys or cookies) and Cloudflare's details about the request, so we can investigate abuse.
- 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, the visitor's country and device type, any utm_source, utm_medium, utm_campaign or ref tags in the link, and a visitor hash that changes daily and per drop (a one-way hash of the IP address and browser, used to count unique visitors). 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 Clicktag. This applies to ship.page only — drops never load our analytics or any third-party script from us.
Forms on drops
- What we store. When a visitor sends a form on a drop that belongs to an account, we store the response for the drop's owner: the field names and what the visitor entered, the page and form it came from, the time, the visitor's country, the referring site, and the same daily visitor hash as visit telemetry. We don't store IP addresses; we only use them to rate-limit responses. For a file field we keep the file name, not the file. Forms with a password or payment card field are never saved.
- Who can read it. Only the drop's owner, in their dashboard and in the alert emails we send them. An alert can carry the whole response, with reply-to set to the email address the visitor entered. We use responses only to deliver them to the owner and to filter spam and abuse.
- The forms script. When a form only shows its own thank-you message and sends nothing, the page can also get a small script, served from the drop's own address, that copies what the visitor sends through that form. It reads a form only when it's sent, loads nothing from anyone else and runs no analytics. The owner's test link from the dashboard sets a cookie on that page for 10 minutes, so their own test responses are marked as tests.
- Deleting it. The owner can delete any response. Responses are kept until the owner deletes them or their account is deleted; responses marked as spam are deleted after 30 days. Sent a form on someone's drop and want your response gone? Ask the drop's owner, or email info@bitgate.com with the drop's address.
ship.page in ChatGPT
- What we receive. The files of each page ChatGPT publishes for you, and the images you attach in the chat for that page, which we download from OpenAI's file links to publish them.
- Your ChatGPT identity. OpenAI sends an anonymized user ID with each request. We store only a one-way hash of it next to the pages you publish, so ChatGPT can list, update and take down your pages, and we use it to rate-limit requests. We never receive your name, email address or conversation.
- Usage records. Plugin calls are logged like other MCP calls (see MCP/API telemetry above), without page contents or your ID.
- Keeping a page. Pages published from ChatGPT aren't tied to a ship.page account until you choose Keep it online and sign in. Taking a page down takes it offline; we keep its files but no longer serve them.
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 unless the owner turns on the forms script. 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, and a page with a form that needs it also gets the forms script described above. 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;
- Postmark: sending email, including form response alerts to drop owners;
- 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 Clicktag — marketing-site analytics only.
Retention
Drops and their files are not deleted: an expired drop stops being served and a drop you delete or take down goes offline, but their files and records are kept. So are the deploy records described above. Visit and API telemetry are deleted after 90 days. Form responses are kept until the drop's owner deletes them or their account is deleted, and responses marked as spam are deleted after 30 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 info@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.