Privacy
last updated 2026-08-10 · canivibecodeit.com, run by Rob Hallam, sole trader, UK
What we store, and why
- Digest emails. If you sign up for the weekly digest (or check the box at account signup), we store your email address and where you signed up from. Sending goes through Resend, our email provider, which holds a mirror of the list. Every email has a one-click unsubscribe. Unsubscribing actually works.
- Accounts. Sign-in is Google or GitHub only; we never see or store a password. We keep what the provider hands us (email, name, avatar, and the OAuth tokens that make sign-in work), your stack (the list of apps you saved), and per session the IP address and browser it was created from, which is standard session-security bookkeeping. Sessions expire after 7 days; everything else lives until you delete it.
- Votes. "I replaced this" clicks are counted with a short-lived rate-limit key based on your IP. No account needed, no profile built.
- Sponsors. If you buy a sponsor slot we store the card details you give us: company name, tagline, link, logo, and a contact email. Payment runs entirely through Stripe; we never see your card number.
- Analytics. First-party PostHog (EU region), proxied through our own domain. We count pageviews and clicks to see what's working. No third-party ad trackers, no cross-site anything.
What we don't do
- No selling or renting your data. Ever, to anyone.
- No merging you into other mailing lists.
- No pre-checked consent boxes.
Deleting your data
Delete your account on /account: it wipes your stack, removes your email from the digest list (including the Resend mirror), and deletes the account rows. There is no soft-delete and no exit survey. For anything else (a stray digest signup, a sponsor record), email [email protected] and a human (Rob) will delete it.
The formal bit
Legal bases under UK GDPR: consent for the digest (the unchecked box you tick), contract for accounts and sponsor purchases (we can't provide the thing without the data), and legitimate interest for rate limiting and first-party analytics. Data lives with our processors (Railway for the database, Resend for email, Stripe for payments, PostHog EU for analytics). If you think we've handled your data badly, email us first and a human will fix it; you also have the right to complain to the ICO at ico.org.uk.
Later features
If you post content here in the future (build attempts, product claims, that sort of thing), it will be public by design and tied to your account name. We'll say so on the surface where you post it, before you post it.
Terms live at /terms.