Privacy policy
Slipmint is an HTML-to-PDF API that is in development. The only thing you can sign up for is the launch waitlist (section 6). Free API keys go out by invite to waitlist members, through one-time claim links (section 6a). This policy describes what the service does today, and it will be reviewed before any public launch.
1. Documents you send
- The HTML, JSON
dataand asset URLs you send toPOST /v1/pdfare processed transiently to produce your PDF. The PDF is streamed back in the HTTP response withCache-Control: no-store. - Slipmint doesn't retain documents: nothing is written to a database, object storage or a persistent disk.
- The API runs on Cloudflare Workers, which process requests in memory. Rendering happens on Google Cloud Run in us-central1 (Iowa, USA). The renderer (open-source Gotenberg/Chromium) writes per-request working files (your HTML and the output PDF) to Cloud Run's in-memory filesystem, and they're removed when the request finishes. Cloud Run's filesystem doesn't persist beyond the instance (Cloud Run container contract).
2. Data we store
- For each API key: a SHA-256 hash of the key (never the key itself), a short key ID, a label, the plan and limits, and created/revoked timestamps.
- A document count per key per calendar month, used for quotas and (later) billing.
- This data is stored in Cloudflare D1.
3. Logs
- Slipmint doesn't log request bodies, rendered documents or API keys.
- Our hosting providers record standard request metadata such as time, IP address, user agent, path, status code and latency: Cloudflare for the API, and Google Cloud for the renderer.
- Cloudflare (API): Workers Logs (observability) is turned off for this Worker, and we don't use Logpush or Tail Workers, so we don't keep per-request API logs. If we ever turn Workers Logs on, Cloudflare's free plan keeps them for 3 days (Cloudflare docs). Cloudflare also processes request data to run and secure its network under its own privacy policy.
- Google Cloud (renderer): Cloud Logging's default retention is 30 days (Google Cloud docs).
4. Service providers (subprocessors)
- Cloudflare, Inc.: API hosting (Workers, global network) and the D1 database.
- Google LLC: PDF rendering on Google Cloud Run, region us-central1 (USA).
Data is therefore processed in the United States and at Cloudflare edge locations.
5. Remote assets and security
- If your HTML or
logo_urlreferences public URLs (images, fonts, stylesheets), the renderer fetches them from the Google Cloud network while rendering. - Requests that reference private, loopback, link-local or cloud-metadata addresses are rejected where detected; the renderer blocks private IPs at fetch time.
- Report security issues: digitalpromohub.support+slipmint@gmail.com.
6. This website and the waitlist
The site sets no cookies and has no analytics or tracking scripts.
If you join the waitlist on the home page:
- What's stored: your email address, the time you joined (UTC), where you joined from (for example "landing"), and the exact consent wording you agreed to (with its version tag). We also store a SHA-256 hash of a one-time deletion token. The token itself is shown only to you. All of this is kept in Cloudflare D1 (the same database as API keys).
- Abuse protection: to rate-limit signups we keep a keyed hash of your IP address (HMAC-SHA256 with a secret key; for IPv6, of your /64 network) and an hourly counter. An hourly cleanup job deletes it once the hour is over. Your raw IP address isn't stored.
- How long: until we send the launch invite, or 12 months after you joined, whichever comes first. We delete the list after the invite is sent, and an automatic hourly cleanup job deletes any entry older than 12 months.
- Emails: joining requires ticking the consent box, and you'll get one launch invite. There's no newsletter, and we don't share or sell the list. Nothing is sent automatically when you join.
- How to delete it: use the personal deletion link shown right after you join, or email digitalpromohub.support+slipmint@gmail.com from the address you signed up with, and we'll delete it.
6a. Free API key claim links
Free API keys go out by invite, to waitlist members and occasionally to people we invite directly. We send you a personal one-time link by hand from our support inbox. The site itself sends no emails.
- What's stored: a SHA-256 hash of the link's secret token (the token itself isn't kept), when the link was created and when it expires, when it was used, the ID of the key it created, and a short internal label. If you were invited from the waitlist, we also store a keyed hash of your email address (HMAC-SHA256 with a secret key) so we don't send you two links. Your email address itself isn't stored with the link. All of this is kept in Cloudflare D1.
- Expiry: the link works once and expires 7 days after it's created. An hourly cleanup job deletes unused links once they've expired. The record of a used link is kept as long as the key it created exists.
- Your key: using the link creates a free-plan key (50 documents per month) and shows it to you once. As with every key, we store only a SHA-256 hash of it (see section 7), so we can't show it again. If you lose it, email us for a new link.
- Abuse protection: to rate-limit claim-link visits and key claims we keep a keyed hash of your IP address (HMAC-SHA256 with a secret key; for IPv6, of your /64 network) and an hourly counter. The hourly cleanup job deletes it once the hour is over. Your raw IP address isn't stored.
- Deletion: email digitalpromohub.support+slipmint@gmail.com and we'll revoke your key and delete its key record and claim record. Deleting your waitlist entry with its deletion link doesn't remove a claim link or a key.
7. Retention and deletion
- Key records and monthly counters are kept while the key exists, and for billing records once paid plans launch.
- Keys can be revoked immediately. For deletion or privacy requests, email digitalpromohub.support+slipmint@gmail.com.
8. Changes
This is a pre-launch draft. Material changes will be posted on this page with a new date.