TypeLLM is run by Vectify AI Limited, a company registered in England and Wales (number 14827188) at 2nd Floor, College House, 17 King Edwards Road, Ruislip, London, HA4 7AE, United Kingdom. We are the controller of the personal data described here.
What we collect
- Your account. Your email address, when you signed up, and the access code or invite you used.
- Signing in. Sign-in links work once and expire after 15 minutes. We record the IP address each link was requested from, to limit how many can be sent. If you sign in with GitHub, see Signing in with GitHub below. A session lasts 30 days.
- API keys. We keep a hash of each key, never the key itself, with its name and first few characters. The playground's own key is kept encrypted, so the playground can make calls for you.
- Usage. For each API call: when it ran, its status, how long it took and its token counts. This is what we bill.
- Billing. Payments go through Stripe. We keep your Stripe customer ID, your balance and your transactions. Card details go to Stripe, not to us.
- Messages. What you send through the contact or early-access forms: your email address, name, company and message.
- Analytics. How the site is used, such as pages visited and features used, with browser and device details, linked to your account once you sign in.
The content of your calls
The context, questions and images you send, and the answers and thinking that come back, pass through our servers to be answered. We don't store them and don't use them to train models. When a call fails, our logs may keep a short error message about it.
Who processes it
- Vercel hosts this website.
- Neon hosts our database.
- Google Cloud runs the API's gateway and load balancer, which keeps request logs with IP addresses, without request bodies.
- RunPod runs the GPU servers that answer calls; your calls pass through them.
- Resend sends sign-in links and the newsletter, and delivers contact messages.
- Stripe handles payments.
- PostHog provides our product analytics.
- GitHub confirms your email address, if you sign in with it.
Signing in with GitHub
- What we access. When you choose “Continue with GitHub”, we ask GitHub only for the
user:emailscope and read only your verified primary email address. We do not read your repositories or any other GitHub data. - How we use it. To sign you in: we find the TypeLLM account with that email address, or create one, and open a session. The address is then your account's email address, used as any account's is: to identify your account, for messages about the service and your billing, and for the newsletter, which you can unsubscribe from.
- How we store it. Your email address is stored with your account in our database, hosted by Neon. The access token GitHub gives us is used once, to read your email address, and then discarded: we never store it, and we cannot use it to reach your GitHub account later.
- Who we share it with. No one, except the providers listed under Who processes it, which run the service for us, and where the law requires it. We do not sell it, do not use it for advertising, and do not use it to develop, improve or train AI or machine learning models.
- How long we keep it, and deleting it. While your account is open. To delete your account and its data, contact us from your account's email address; we keep only the records the law requires, such as payments. You can also remove TypeLLM's access at any time on GitHub, under Settings, Applications.
Why we use it
To provide the service you signed up for: your account, your keys, answering your calls and billing them. To keep it secure and within its limits, such as limiting sign-in links, which is in our legitimate interest, as is improving the site. To keep the records the law requires, such as payments. And to reply when you write to us.
Newsletter
Once you have signed in, we may email you news about TypeLLM, such as new features. Every such email has a link to unsubscribe, which stops them at once; it does not affect your account or your sign-in links.
Where it is processed
Most of these providers process data in the United States. Where data leaves the UK, we rely on the safeguards the law provides for it, such as the UK's adequacy regulations or standard contractual clauses.
How long we keep it
Your account, keys and usage while your account is open. Payment records as long as the law requires for accounting. Messages as long as we need them to reply and follow up.
Cookies
tl_session keeps you signed in, for up to 30 days. tl_invite carries an invite code through sign-in, for up to a day. tl_oauth protects a sign-in with GitHub from forgery, for up to 10 minutes. ph_…_posthog is for analytics, for up to a year. We use no advertising cookies.
Your rights
You can revoke your API keys at any time from the dashboard. You can also ask for a copy of your data, and ask us to correct it, delete it, restrict or object to how we use it, or move it elsewhere; contact us from your account's email address. We keep records the law requires, such as payments. If you are unhappy with how we handle your data, you can complain to the UK Information Commissioner's Office (ico.org.uk).
Changes
If this page changes, its date above changes with it.