Privacy Policy

For every account we store:

• Email — your login and the address we send API keys and receipts to.
• Hashed password — managed by Supabase Auth; we never see the plaintext.
• API keys — your issued keys, stored in plaintext on our side so the dashboard can re-display and re-email them. v1 limitation; see the v2 plan in our docs.
• Subscription + payment records — Paystack transaction ids, plan id, period start/end, amount in Naira. We do not store card numbers; Paystack holds those.
• Usage metadata — for every request: timestamp, model id, prompt token count, completion token count, request id, the API key id used. No IP addresses are persisted beyond what the access log retains for 30 days.

By default we do not log the bodies of your prompts or the model responses. A future debugging feature may opt-in to a short-window content log; if/when that ships, this page will be updated and the toggle will live in your dashboard.

Data leaves our database only to the processors below, each governed by their own privacy terms:

• Supabase — authentication, session cookies, and the mirrored Postgres database. EU region hosting. See supabase.com/privacy.
• Paystack — payment processing, NGN-denominated charges, webhook delivery. Card data never reaches brewkeg. See paystack.com/privacy.
• Resend— transactional email (API key reveal, billing receipts). Message content is rendered server-side and sent via Resend’s HTTPS API. See resend.com/legal/privacy.
• Anthropic, OpenAI, Google — upstream model inference. Your prompts are forwarded over HTTPS to these providers under their standard API terms. We pass no identifying user metadata to them beyond what the API request itself requires.
• Fly.io / Vercel — hosting and edge runtime. Access logs retained for 30 days for abuse detection.
• Meta — if you opt in via our ads, the Meta Pixel and Conversions API receive a hashed email and event metadata for conversion attribution. The pixel is disabled by default in development.

We set a minimum set of cookies, all first-party:

• Supabase auth cookies — session management.
• brewkeg_minted_key — one-minute flash cookie that hands your freshly-minted API key from the signup action to the dashboard. httpOnly, sameSite=lax.
• brewkeg_signup_event — one-minute flash cookie carrying the Meta Pixel event id for browser + server dedup. JS-readable; no PII.

• Account, API keys, subscriptions: lifetime of account + 30 days after deletion.
• Usage metadata: rolling 90 days. After 90 days the row is deleted; aggregate rollups (total tokens per day, per plan) may be retained indefinitely in anonymized form.
• Financial records (Paystack transaction ids, plan amounts): retained for 7 years per Nigerian tax requirements.
• Access logs (IP, user agent): 30 days, then purged.

You can, from the dashboard or by emailing us:

• Access — request a JSON export of every row tied to your account (email, keys, subscriptions, usage events).
• Rectify— change your email or display name; we’ll update both Supabase and our mirror.
• Delete — close your account; we wipe the rows listed above within 30 days. Financial records stay per Nigerian law.
• Revoke — delete an individual API key. Revoked keys are kept as tombstones so we never re-issue the same prefix.

Email hi@brewkeg.dev for any of the above. We respond within 14 days.

brewkeg is not directed at children under 13. We do not knowingly collect data from children. If we discover we have, we delete it within 30 days.

Material changes get 14 days’ notice by email; non-material changes take effect on this page. Continued use after the effective date means you accept the new policy.

Data Protection questions: hi@brewkeg.dev. We respond within 14 days. Nigerian users may also escalate to the Nigeria Data Protection Commission (NDPC).

See also the Terms of Service.