What we collect
- Sign-in: from Google, your email, name, profile picture URL and Google account ID; from GitHub, your primary verified email, name, avatar URL and GitHub user ID. We store your email, name, picture URL, the providers you linked with their account IDs, and when the account was created.
- Credits and usage: your balances, plan and billing period; for each model and UTC day, the credits charged, tokens and number of requests; credit grants and purchases. While a request runs we keep its request ID, model, token counts and cost.
- Payments: the Creem customer, subscription and order IDs, your plan, its status and period dates, and a record of each payment event Creem sends us. Card and billing details stay with Creem; we never receive them.
- Sign-in sessions: a session ID and a hash of the refresh token with its creation and expiry times. Tokens themselves are not stored on our servers.
Your code and questions
- Your indexes, Ask history and settings stay on your computer.
- When CtxE indexes a workspace, the text of code chunks is sent through our server to Voyage AI to compute embeddings, and symbols with their file paths are sent to TypeSafe to classify them.
- When you ask a question, the question and the code excerpts CtxE selects as evidence are sent through our server to the provider of the language model in use (OpenAI, DeepSeek, xAI, MiniMax or Xiaomi), and candidate excerpts to Voyage AI to rank them.
- Our servers pass this content to the provider and return the result; they do not store code, questions, prompts, embeddings or answers. For each request we record only the model, token counts and credits charged. Each provider processes the content under its own terms.
Why we use it
- To sign you in and keep you signed in.
- To run hosted requests, charge credits and show your usage and billing history.
- To sell plans and credit packs through Creem and apply the payments to your account.
- To protect the service: rate limits, abuse prevention and operational logs, which record requests and errors but not your code or questions.
We do not sell your data and do not send marketing emails.
Cookies and browser storage
__Host-ctxe_at: keeps you signed in to the dashboard (HttpOnly, Secure, one hour, renewed while you use it).__Host-ctxe_rt: renews that sign-in (HttpOnly, Secure, up to 30 days).__Host-ctxe_oauth: protects the Google or GitHub sign-in flow (10 minutes).- Session storage: your balance and plan before a checkout, to confirm the payment when you come back.
These are strictly necessary. There are no analytics or advertising cookies.
Service providers
- Cloudflare: hosting, database and request logs.
- Google and GitHub: sign-in.
- Creem (Armitage Labs OÜ, Estonia): merchant of record for plans and credit packs. When you start a checkout, your account email and account ID are sent to Creem, which collects your payment and billing details under its own privacy policy.
- Voyage AI, TypeSafe, OpenAI, DeepSeek, xAI, MiniMax and Xiaomi: only for the requests described above.
These providers may process data in countries other than yours.
How long we keep it
- Sign-in sessions end when you sign out or 30 days after their last renewal.
- Per-request usage details are deleted 7 days after the request completes; per-request charges are merged into one row per model and day.
- Account, credit and billing records are kept while your account exists.
Your choices
- See your profile, usage and billing history in the dashboard at any time.
- Ask for a copy, a correction or the deletion of your data by writing to ctxe@tlelabs.com. When we delete an account, its profile and sign-in links are removed; billing records are kept only as long as accounting rules require.
Children
CtxE is not meant for children under 16, and we do not knowingly collect their data.
Changes
We may update this policy. The date above shows the latest version.
Contact
Questions or requests about your data: ctxe@tlelabs.com. CtxE by TLE Labs is operated by Lê Phước Lộc, trading as TLE Labs, Vietnam. See also the Terms of Service.