VERDANTBLOOM

API privacy

As of 8 November 2026. This page covers the API at api.verdantbloom.bar: your account, your keys, your credit, and every request you send. The website privacy page covers the landing page and its forms.

1. The short version

We do not store or log what you write, or what the model writes back. Not the prompt, not the reply, not a summary, not a sample, not a hash of either. We keep what we need to run your account and charge your credit: who you are, which key, when, how many tokens, how long the GPU was busy, and what it cost.

2. Who

verdantbloom is operated by VerdantBloom LLC, a Pennsylvania limited liability company, 908 Henrietta Ave, Unit #2050, Huntingdon Valley, PA 19006. Contact: bloom@verdantbloom.bar.

3. What we never keep

  • The text of your requests: prompts, messages, system prompts, images or files you send.
  • The text of the replies, streamed or not.

Your request passes through our gateway to a rented GPU running kinfer, our own inference engine; the model answers, and the answer passes back. Nothing in that path writes the text down. That is enforced in code, not only promised: the GPU server is refused if it is started in any mode that would print or record text, and anyone who wants to change that must change this page first.

While a request is being answered, the GPU server keeps a working copy of the conversation in memory, and may keep a cache of it on its own disk so a follow-up request starts faster. That copy is only used to answer you. It is deleted when the server is shut down, which happens after 10 minutes without requests and at most 6 hours after it started.

4. What we keep, and why

WhatWhyHow long
Your email address, account id, level, and whether the account is activeTo log you in, run your level's limits, and write to you about your accountWhile the account exists
Your keys: name, first few characters, when made, when last used, when revoked. Never the key itself: only a one-way hash.To check a key on every request, and to show you your keysWhile the account exists
Each request's meter: time, key, model, tokens in and out, GPU busy and idle milliseconds, the charge, and whether it succeededTo charge your credit correctly and show you your usageAt least seven years (see 6)
Your credit: payments in, charges out, refundsIt is your creditAt least seven years
Daily request countersYour level's daily limitsPer day; old days are not used
Login links and sessions, as one-way hashes, with a salted hash of the network address that askedSo a link works once, and to slow down abuseLinks expire within the hour; sessions after 30 days

None of that contains text you wrote, apart from your email address and the names you give your keys.

5. Who else handles it

  • Stripe handles card payments. We get back that a payment happened, its amount and its reference. We never see or store your card number.
  • SendGrid (Twilio) delivers login links and account mail, so it handles your email address.
  • Vultr rents us the server the gateway, the account database and the website run on.
  • Cloudflare answers for our domain names.
  • RunPod and Vast.ai rent us the GPU servers the model runs on: for each start we take the cheapest suitable offer from either, under our price ceiling for that GPU size (a few models run on RunPod only). Your request and its reply travel to and from those servers. We do not store the text and we do not let them log it, but they operate the machines. We cannot promise what a hosting provider can technically see on its own hardware, and we will not pretend to.
  • Google Cloud Storage holds our usage records: counts, timings and costs per GPU server. No text, and no email addresses.

We do not sell any of it. We do not use it to train models. We run no analytics and no advertising on the API.

6. How long

Account, key and credit records last while your account exists. Billing records (meters, payments, refunds) are kept for at least seven years, because tax and accounting rules require us to be able to show them.

7. Your choices

Write to bloom@verdantbloom.bar from your account's address to see what we hold about you, correct it, or close your account. Closing revokes every key at once. Records we must keep for accounting stay, without anything you wrote, because we never had it.

8. When we would look

We cannot read your past requests, because we do not have them. If a key is reported for breaking the acceptable-use policy, we act on the report and the account's meter, not on its text. If the law requires us to hand over what we hold, what we hold is in section 4.

9. Age

The API is for people 18 or older.

10. Changes

If we ever change what is kept about requests, this page changes before the code does, and the date at the top changes with it. A change that would keep any text you write would be announced to account holders by email first.