Privacy policy

The Think-Reason-Learn API is provided by Vela Partners Management, LLC, a Delaware limited liability company, of 1 Ferry Building, Suite 201, San Francisco, CA 94111, United States (“we”). We are the controller of the personal data described here.

Privacy questions and requests go to support@thinkreasonlearn.com. Security reports go to security@thinkreasonlearn.com. We have not appointed a data protection officer.

We offer pretrained prediction models, such as the LinkedIn viral post predictor, that return a score and the checks behind it. You call them over HTTP at /v1/predict or the OpenAI-compatible /v1/chat/completions, try them in the console playground, or call them through OpenRouter.

When you create an account, we store:

• your name and email address;
• a hashed password, or, if you sign in with Google or GitHub, a link to that account. We don't receive your Google or GitHub password;
• the organizations you belong to and your role in each;
• records of your sign-in sessions, including the IP address and browser user agent of each session;
• your API keys. A key is shown once, when you create it. We store only a SHA-256 hash of it and its first few characters, so we can't show it to you again;
• your organization's credit balance, top-ups and usage charges.

We do not store the inputs you send to a model, such as post text, images, LinkedIn profile URLs or account snapshots, and we do not store the outputs it returns. This applies to requests from the API, the playground and OpenRouter.

To answer a request, your inputs pass through our servers and, where a model needs them, to the sub-processors listed below, for as long as it takes to produce the answer. Then we discard them.

We do not use your inputs or outputs to train or tune any model.

The LinkedIn viral post predictor (with account) reads the public profile and recent public posts of the LinkedIn account you ask about. It returns them to you as a signed account snapshot, which you can store and send back on later calls. We don't keep the snapshot or the profile data.

For every request we record metadata, which we use for billing, rate limits and credit limits, the usage page in the console, and to keep the service running:

• the time;
• the organization, the API key id, and for playground requests the user who ran it;
• where the request came from (API, playground or OpenRouter) and which endpoint it used;
• the model and the model release;
• the response status and any error code;
• latency;
• token counts;
• the price charged and our cost to serve it.

We keep request metadata for 13 months, then delete it. It does not include your inputs or outputs.

When you sign in, we set a cookie that keeps you signed in. The console sets a cookie that remembers whether its sidebar is open, and the site saves your light or dark theme choice in your browser's local storage.

We use no analytics, advertising or tracking. Our fonts are served from our own server. Like any web host, Google Cloud receives your IP address and browser type when you load a page or call the API, and keeps standard request logs.

• To provide the service: run your account, answer your requests, show your usage, and bill you. We do this to perform our contract with you.
• To keep it secure and fair: enforce rate limits, prevent abuse and investigate problems. We do this in our legitimate interest in running a reliable service.
• To email you: verification, password resets and messages about your account or changes to the service.
• To meet legal obligations, such as keeping payment records.

We do not sell personal data, share it for targeted advertising, or use it for any other purpose.

These companies handle data for us. Each receives only what it needs for the job described.

OpenRouter passes each language-model call to a model provider to run it. How OpenRouter and those providers handle that content is governed by their own terms and policies.

Email sent to our support and security addresses is handled by Google Workspace (Google LLC).

We disclose personal data to anyone else only if the law requires it, for example in answer to a valid legal request.

Your account and billing relationship is with OpenRouter, and OpenRouter receives your request first, under its own privacy policy. We don't receive your OpenRouter account details. This policy applies to the requests we serve: we don't store their inputs or outputs, we don't train on them, and we keep the same request metadata.

• Inputs and outputs: not kept. Held only while a request is being answered.
• Request metadata: 13 months.
• Account details, organizations, sessions and API key hashes: while your account exists.
• Credit and payment history: while the organization exists, and longer where tax or accounting law requires it.
• Emails you send us: until your question is resolved, and no longer than 24 months.

When an organization is deleted, its API keys, request metadata and credit history are deleted with it. Copies in database backups are removed as those backups expire.

An organization's owner can delete it from the organization's settings page in the console. This revokes its API keys, removes its members and deletes its data. Unused credits in a deleted organization are not refunded, so ask us about a refund first.

To delete your user account, email support@thinkreasonlearn.com from the address you signed up with.

We are based in the United States, and our servers and database are in Google Cloud's us-central1 region in the United States. Our sub-processors may process data in other countries.

If you are in the UK or the European Economic Area, the UK GDPR or the EU GDPR applies to how we handle your data. Google is certified under the EU-US Data Privacy Framework and its UK Extension, and Google's Cloud Data Processing Addendum includes the EU Standard Contractual Clauses and the UK Addendum. You can ask us for details of the safeguards that apply to each sub-processor.

Depending on where you live, you can ask to access, correct, delete or restrict your personal data, to receive it in a portable form, and to object to our processing. Write to support@thinkreasonlearn.com. We will respond within one month. If a request is complex, we may take up to two further months, and we will tell you within the first month if we need to.

If you are unhappy with how we handle your data, tell us first. You can also complain to a data protection authority, such as the UK Information Commissioner's Office or the authority where you live or work in the European Economic Area.

The API and console are served only over HTTPS. Passwords are stored hashed, and API keys are stored only as SHA-256 hashes. Card details are handled by Stripe and never reach us. If a data breach affects you, we will tell the relevant authority and, where the law requires it, you.

The service is not meant for anyone under 18, and we do not knowingly collect data about children.

If we change this policy, we will post the new version here with a new date. For a change that affects how we use your data, we will post a notice on this page at least 14 days before it takes effect.