Privacy Policy

1. Who we are

RightNow AI, Inc. (“RightNow”, “we”, “us”) is a company registered in Delaware, United States, at 131 Continental Dr, Newark, DE 19713, US. For any privacy question or request, email jaber@rightnowai.co.

This policy covers:

• our website, www.rightnowai.co, with its research, docs, blog and contact forms;
• our decision model, with its API and its console at www.rightnowai.co/dashboard, both in a private preview by invitation;
• RightNow Agent, our coding agent for the terminal, which is paused: our website no longer shows how to install it, but copies already installed keep working.

It does not cover RunInfra, RightNow's open models platform, which has its own site, privacy policy and terms at runinfra.ai, or other sites we link to. Your visit to another site is covered by its own policy.

When you follow a link to another site, such as a research paper, your browser tells that site only that you came from our domain. Most of our links to RunInfra also carry tags that name our site and where on it the link was, such as the navigation bar, and nothing about you.

2. The website

Visits

Vercel hosts the website. To count visits, Vercel Web Analytics receives the address of each page you open, including any query in it, the page that sent you and the time. Vercel works out your country, region and city from your IP address, notes your browser, operating system and device type, and tells visits apart with a hash of the request that it discards after 24 hours, without cookies. We see totals, not individual visitors.

Apart from page views, the website reports one event: a play of a video on the research page, with which video was played and the page's path, and nothing that identifies the visitor. Console pages load no analytics script of their own, but if you open the console from the website in the same tab, the website's script keeps running and can count the console pages you then open, by their path only.

Cookies and browser storage

The website's pages set no cookies. The console runs on the same site, at www.rightnowai.co/dashboard, and sets the cookies listed in section 3; once you sign in, your browser sends the cookies whose names start with __Host- with its requests to www.rightnowai.co, the website's pages included, which do not read them. If you choose a theme, the choice is saved in your browser's local storage under the name theme and stays there, also when you sign out of the console.

If an attack ever makes us ask your browser to pass a security check on our site, Vercel may set a cookie there that records the check. When you sign in with Google or GitHub, your browser passes through our sign-in host auth.rightnowai.co, which Cloudflare serves, and Cloudflare may set its own security cookies there: __cf_bm, which its bot protection uses and which ends after 30 minutes without use, and cf_clearance, which records that your browser passed its check. These cookies are strictly necessary for security.

Tracking across websites

Neither we nor any other company uses the website or the console to follow your activity across other websites. They show no advertising. Google or GitHub learn that you use the console only if you sign in with them, and Cloudflare sees the visits to the sign-in page that its check runs on. Since there is no such tracking, a Do Not Track signal from your browser changes nothing here.

Forms and email

The contact form asks for your email address and a message, which we receive under a topic such as a general question; a form for asking for access to our API can also ask for your company, which is optional. The enterprise form asks for your work email, company, team size, where your models should run, your interest and details, and optionally your name.

Resend sends each message to our team's mailboxes, which Google Workspace hosts, and the messages stay there for up to 3 years after the last message. The website itself does not store them. Email we exchange with you at our rightnowai.co addresses is kept in Google Workspace in the same way.

Limits against abuse

Each form counts the requests that come from one IP address for 60 seconds, under a one-way hash of the address kept in Upstash. An IP address can be found again from such a hash by trying every address, so we treat these hashes as personal information.

Logs

Vercel keeps logs of requests to the website, such as the page, query, browser, region and IP address, for the period our hosting plan sets. The website's own log lines carry only fixed labels and error codes and may still include salted IP address hashes from automated sign-ups to the now-closed waitlist. Vercel also sends those lines, with request details such as the path, the browser and a one-way fingerprint of how your browser set up its secure connection, to Better Stack, which removes the IP address from each line as it arrives, keeps the lines for 90 days, and then deletes them.

3. The console: sign-in, cookies and email

The API and its console are in a private preview, and access is by invitation: you get access when we invite you or when a workspace's owner or admin invites you to it. You sign in to the console with Google, with GitHub or with your email address. There is no password.

Signing in

When you sign in with Google or GitHub and approve the sign-in, the provider shares your account's email address and whether it is verified, your name, your profile picture link, the provider's identifier for your account and, for GitHub, your username. From Google we ask only for the openid, email and profile permissions.

If you sign in with your email address, you type it on the sign-in page, and Supabase Auth emails you a sign-in link and a code from login.rightnowai.co, through Resend. The link and the code expire after 10 minutes. To stop abuse, we limit the sign-in emails sent to each address and those asked for from each network address.

The sign-in page runs Cloudflare Turnstile for every visitor, in its email form, above the Send link button: a check that tells people from automated programs. The console asks for a sign-in email only once that check has passed. For the check, Cloudflare receives your IP address and signals from your browser, such as its user agent and TLS fingerprint, whichever way you sign in, and it also uses those signals, under its own terms, to improve the check.

Supabase Auth keeps your sign-in profile with your sessions, and logs each sign-in event with the IP address and browser it came from, to keep accounts secure. Those log entries also hold your email address, and we keep them for up to 90 days. Supabase's own request logs can also hold IP addresses.

Of your sign-in profile, the console itself uses only three things: the email addresses verified for you, by Google, by GitHub or by a sign-in link or code sent to the address; the names of the sign-in methods you use; and, once, your name, if Google or GitHub shared one, to greet you in the welcome email. It shows one of those addresses as yours and makes it the first billing email of each workspace you create, and it checks all of them against our invite list and your invitations. During the preview, we keep the email addresses we invite on that list.

Who can sign in

During the preview, a sign-in makes a new sign-in identity only for an email address that is on our invite list or holds an open invitation to a workspace, whether you sign in with Google, with GitHub or with your email address, and never for an address we suspended. A first sign-in with any other address is refused, and no sign-in identity is made for it. The rule applies only to a new sign-in identity: once you have one, you keep signing in to it with its email address, also after the invitation that admitted you is no longer open.

If you belong to no workspace and open the console other than through an invitation link, the console makes a workspace in your name: for example, when you sign in without following your invitation's link, when your invitation closed before you accepted it, or after you left or were removed from every workspace. It makes none if we suspended you or you have reached a limit on the workspaces you can create.

If one of your verified addresses is on our invite list, a new workspace is active at once. Other new workspaces are pending and cannot use the API. Workspace limits still apply.

Cookies and browser storage

The console sets only these cookies. Your browser sends them only to www.rightnowai.co, and only over HTTPS:

• __Host-rn-auth, in one or more parts, holds your session. The cookie can stay in your browser for up to 400 days, but the session in it ends when you sign out, after 7 days without use, or after 30 days, whichever comes first.
• __Host-rn-auth-code-verifier completes a sign-in. It is removed when the sign-in completes, and otherwise can stay up to 400 days.
• __Host-rn-ws remembers the workspace you opened last, so the console can open it again. It holds only that workspace's id and lasts up to 30 days.
• __Host-rn-join keeps an invitation link while you sign in, for up to 15 minutes, and is deleted when you accept.
• __Host-rn-link lets an emailed sign-in link work only in the browser that asked for it. It holds a one-way hash of your email address, never the address itself, lasts up to 10 minutes, and is deleted when the link signs you in.
• rn-get-started remembers whether Get started is open or closed in each workspace in this browser. It holds only workspace ids and that choice. Your browser sends this first-party cookie only to console pages. It is not used for tracking and lasts up to 365 days.

Your browser also keeps your theme and the sign-in method you last used in local storage, so the console can offer that method again. While you are signed in, the dashboard also keeps a mark in your browser's local storage so the Site's menu shows Dashboard instead of Sign in; signing out removes it. Your Playground draft (the Playground is the console's page for trying requests), the time of the last automatic page reload and, for each console page, a count of the changes made in that tab stay in session storage, which ends when you close the tab.

Signing out removes rn-get-started and the cookies that hold your session and complete a sign-in, and leaves the other three. The console page you sign out from also clears the console's own entries from your browser's storage, but not your theme or the sign-in method you last used.

The console loads no analytics script of its own (section 2 says when the website's script can count console pages), and the only third-party script it loads is Cloudflare Turnstile's, on the sign-in page. If something on a console page breaks its content security policy, your browser may send us a report; we keep only the kind of problem and the part of the console, not the addresses in the report.

Email from the console

The console sends you a welcome email once, the first time you belong to an active workspace, at sign-in or when you accept an invitation. Replies to the welcome email reach our team's mailbox. It also sends the invitation emails that section 4 describes. Resend delivers them for us. It receives each address and its email, which can include the name your Google or GitHub profile shares. Each email carries an identifier that stops a retry from sending it twice. These emails contain no tracking pixels and no tracked links. We also note when your welcome email was sent or tried.

The console's emails may show our logo as an image from assets.rightnowai.co, which Cloudflare serves; if your email app loads it, Cloudflare receives your IP address and the app's user agent.

Feedback

If you send feedback from the console, we keep your message and its category with your sign-in identity and, if you include the page's details, the workspace, the kind of page and your browser. We email it to our team through Resend, with your address to reply to. That email stays in our team's mailboxes like a form message.

4. The console: workspaces, keys and usage

Workspaces and members

Everything in the console belongs to a workspace, and everyone who uses the console has at least one. A workspace keeps its name, its creator, its status and limits, when it was created and changed, a billing email, and its members with their roles. Members of a workspace can see each other's email addresses, roles and join dates; owners and admins also see its open invitations.

A workspace's billing email starts as its creator's address, and among its members only owners can see it. It stays until it is changed or the workspace is deleted, even after the creator leaves the workspace or is removed from it, or we delete the creator's sign-in identity.

When a workspace invites someone, Resend emails that address a link that works once and expires after 7 days. The email shows the workspace's name and the inviter's email address, and replies go to the inviter. Before accepting, the invitee also sees the role, and only someone who has verified the invited address, through Google, GitHub or a sign-in link or code sent to it, can accept.

Each workspace keeps a change history. It records when:

• the workspace was created, renamed, scheduled for deletion, restored, suspended or unsuspended;
• a member joined, left or was removed, or had their role changed;
• the API keys a member created were revoked because the member left, was removed or was suspended, or because the workspace was scheduled for deletion;
• an invitation was created, resent, revoked or accepted.

For a change a member makes, an entry names who made it and, for a change to a member, the member concerned. When we make one of these changes, such as a suspension, its entry does not name who made it. Once a person's sign-in identity is deleted, entries no longer name them, but the entries of an invitation keep the address it was sent to until the workspace is deleted.

API keys

For each API key we keep its name, a one-way hash of the key, the first and last few characters that the console shows so you can recognize it, who created and who revoked it, and when it was created, last used and revoked. The full key is shown once, when you create it, and is not stored.

Usage records

For requests made with your keys or from the Playground, we keep usage records: ids, the time, the key, the model and route, the status and any error code, sizes, timings, question counts, token counts and cost figures, and for Playground runs, which member ran them. A record can count several requests together, such as the requests of one key that a rate limit refused within the same minute. A usage record never contains what you sent, the answer, your IP address or your browser. The console's charts use hourly totals built from these records.

Suspension

If we suspend someone, for example for breaking our terms, we:

• record the suspension;
• revoke the API keys and the open invitations they made;
• suspend the workspaces they alone own, and schedule each for deletion 30 days later unless we lift the suspension first; if we delete their sign-in identity before then, those workspaces are deleted with it;
• keep a one-way hash of each email address verified for them, by Google, GitHub or a sign-in link or code, so that those addresses cannot be used to get access again;
• take those addresses off our invite list.

Anyone who has an address can match its hash, so we treat these hashes as personal information. We keep them while the suspension stands, even after the person's sign-in identity is deleted, review them each year, and delete them if we lift the suspension. Lifting it also gives back the workspaces it suspended that are not yet deleted; the keys and invitations it revoked stay revoked.

5. The API

Requests and answers

When you send a request to our API, its content goes to Fly.io, which runs the API on its machines in Ashburn, Virginia, in the United States. When you run a request in the Playground, it goes first to the console's server at Vercel, which sends it to the API. The API passes the request to Modal, which runs the model on GPUs in AWS us-east in the United States. A request that includes an image or audio, or a document whose pages must be read as images, is processed on Modal's GPUs in AWS ap-south in India. The answer returns the same way.

We use the content you send only to answer your requests and to keep the service safe and working. Your Playground draft leaves your browser only when you run it, and a run is then handled like any other request.

We do not log the content you send. When a request carries an Idempotency-Key, as every Playground run does, we keep its answer so that, for up to 24 hours, a retry gets the same reply. That answer repeats the question names, choice labels and score levels from your request. For the same 24 hours, a one-way fingerprint of the request stops the same Idempotency-Key from being reused for a different request. Both are deleted about a minute after those 24 hours end. A request sent without an Idempotency-Key leaves no answer stored for retries.

Caches that speed up repeated inputs live in memory only, kept apart for each workspace. If a request names a session, we use that name, joined to your workspace and hashed, only to send related requests to the same model server, where its cache can help. We do not keep it after the request.

Training

We never use the content you send, or the answers the API returns to you, to train our models or any other model. As between you and us, those answers belong to you, to the extent the law allows.

Limits

To protect the service, the API counts requests per IP address under a one-way hash of the address, for windows of one second and one minute, and marks for an hour each hashed address from which a valid key was used. A cache holds each key's workspace, status and limits for up to 16 minutes so that keys can be checked quickly. Changes in the console, such as creating keys, inviting members or deleting a workspace, are also rate limited per person, under a one-way hash of your user id kept for 60 seconds.

Logs

The console's and the API's log lines never contain request content, email addresses or names. They carry ids, counts, codes and timings, and in two cases a whole usage record: when it could not be queued, or when the database refused it.

The API sends its lines to Better Stack itself, and Fly.io also keeps them for 7 days. Vercel sends the console's lines to Better Stack with request details such as the path, the browser and a one-way fingerprint of how your browser set up its secure connection, and Better Stack removes the IP address from them as they arrive. Better Stack keeps the API's lines for 30 days and the console's for 90 days, then deletes them. Vercel also keeps its own logs of console requests for the period our hosting plan sets.

Our database also keeps a security record of administrative actions, with the time, the database operator, the action, any person or workspace identifier it concerns, counts and the outcome. It holds no request content or email address. We keep it for two years, then a nightly cleanup deletes older records. Deleting your sign-in identity removes its identifier and the identifiers of workspaces you created from this record; deleting a workspace removes that workspace's identifier.

Receipts and crash records

The model servers keep a receipt of each request they answer, with its time, its request id, a one-way hash derived from your workspace, the route, the number of questions, token counts and a cost figure. If a model server crashes, it also records keyed one-way fingerprints of the requests it was running and of their workspaces, so that an input that keeps crashing the servers can be refused for up to 24 hours. Neither holds content, and neither is deleted automatically yet.

6. RightNow Agent

RightNow Agent runs on your machine, and its configuration, sessions, transcripts, receipts, memory and local log stay there, under ~/.rightnow by default.

Its RightNow account sign-in is retired. The published version still has the rightnow login, rightnow status and rightnow logout commands: rightnow login now opens RunInfra's pricing page, and our website refuses the other account commands and keeps nothing from them beyond its request logs. If you signed in before September 13, 2026, your machine may still hold that account's email address and plan in ~/.rightnow/account.json and its old sign-in tokens in ~/.rightnow/auth.json, until you run rightnow logout or delete them.

It connects to the model provider you select with that provider's API key, which you enter in its Connect screen, add through its auth command, or set in an environment variable. It checks a key with the provider before storing it, and by default stores keys on your machine in ~/.rightnow/auth.json, a file it writes with owner-only permissions.

To answer you, it sends your prompt, the relevant contents of files it reads and tool results to the model provider in your configuration, which is RunInfra in the shipped configuration, and that provider handles them under its own terms. Web searches go to the search service your configuration selects, DuckDuckGo in the shipped configuration, and web fetches go to the sites requested.

It also uses the MCP servers and hooks set up on your machine or in a project you open, including those set up for Claude Code or Cursor, which it picks up by default. It sends them the tool calls and session events they handle; those that run elsewhere receive them under their own terms. MCP servers are programs that give it more tools, and hooks are commands or web addresses it calls at set points in a session. Our docs on MCP servers and hooks list where it finds them.

At launch, at most once every 30 minutes, it checks releases.rightnowai.co for a new version. The check carries no account or device identifier; Cloudflare, which serves that address, sees your IP address and request details. You can turn the check off with --no-auto-update or RIGHTNOW_DISABLE_AUTOUPDATER=1.

Telemetry is off, and shipped builds contain no telemetry address. Error reports go to Sentry only if you set a Sentry address yourself, and OpenTelemetry data goes only to a collector you configure.

7. Who processes data for us

These providers process personal information for us, for the purposes shown, except the model providers you select in RightNow Agent, which handle your requests under their own terms (RunInfra under its own privacy policy).

Our public status page, status.rightnowai.co, is hosted by Better Stack and accepts no email subscriptions.

Google and GitHub act under their own terms when you sign in with them. Before we start charging for the API, we will add Stripe, which will process those payments, to this list.

The retired rows cover the closed RightNow Agent waitlist and information collected before we closed the website's accounts and paid plans on September 13, 2026; they stay listed until that information is deleted, and the accounts' database is planned for deletion in about January 2027. Before that database is deleted, we will email its account holders once, from updates.rightnowai.co through Resend, to say that their accounts are retired, when they will be deleted and when this policy changes for the information we hold about them, and we delete that list of addresses 30 days after the email.

8. How we use and share information

We use personal information to:

• provide the services: sign you in, run your workspaces, keys and requests, and send the emails described above, to perform our agreement with you;
• keep the services secure and working, with limits, logs, monitoring and the suspension of accounts that break our terms, which is our legitimate interest;
• understand in totals how the website, the console and the API are used, which is our legitimate interest;
• answer your messages and review your requests for access, which is our legitimate interest or a step you ask for before an agreement;
• tell the holders of the retired website accounts, once, that their accounts are retired, when they will be deleted and when this policy changes for them, which is our legitimate interest;
• meet our legal obligations;
• enforce our terms, which is our legitimate interest.

You do not have to give us personal information, but some things need it: the console needs the email address you sign in with, and we can answer a form only with an email address. Some information comes from others: the address on an invitation comes from the member who sends it, and the addresses on our invite list are ones we add. We make no decision about you based only on automated processing that has legal or similarly significant effects on you.

We do not sell personal information, and we do not share it for advertising. We share it only:

• with the providers in section 7;
• with the members of your workspace and, for an invitation, the person invited, as section 4 describes;
• when the law requires it, or to protect people, the services or our rights;
• with a buyer or successor, if we are part of a merger or a sale of assets.

9. How long we keep it

The website

The console and the API

RightNow Agent and retired products

10. Deleting your data

Deleting a workspace. In the console's Settings, an owner can choose Delete workspace after signing in again. The workspace is then scheduled for deletion. Its keys stop working, normally at once, and its open invitations are revoked. For 30 days an owner can restore it. A restore brings the workspace back, but not its API keys: they stay revoked, and you create new ones. After 30 days we delete its usage records and then the workspace itself, with its members, invitations, billing details, change history, keys and hourly totals.

Leaving a workspace. If you leave a workspace or are removed from it, the API keys and open invitations you created in it are revoked, and the workspace keeps its billing email, even if it is your address.

Your sign-in identity. Deleting a workspace ends it, not your sign-in identity. To delete your identity and profile, or any other personal information we hold about you, email jaber@rightnowai.co.

When we delete your sign-in identity at your request, we delete at once every workspace in which you are the only member, and remove you from the others, revoking the API keys and open invitations you made there. We also delete, from the console database, your entries in the sign-in event log and the feedback you sent. Unless we suspended you (section 4), if you are the only owner of a workspace that has other members, we first ask you to make another member an owner or to delete the workspace. We may keep what the law requires us to keep, such as payment records.

What remains. Backups of the console database keep copies for up to 8 days after a deletion. Answers kept for retries and their request fingerprints are deleted about a minute after their 24 hours. Usage records normally stay in the console database for about 30 to 31 days; an hourly cleanup deletes each day together once its hourly totals have been applied. Queued usage records of a deleted workspace are dropped when they reach the database.

Logs at Better Stack, Fly.io and Vercel, and our emails at Resend, follow the schedules in section 9. The model servers' receipts and crash records are not deleted yet.

Administrative audit records follow the two-year schedule in section 9, with the identifiers described in section 5 removed on deletion.

Where your address stays. When we delete your sign-in identity, other workspaces keep your address on the invitations sent to it and in their change history until those workspaces are deleted. A workspace you created that others still use keeps your address as its billing email until it is changed or that workspace is deleted. If your address is on our invite list, it stays there until we remove it.

Supabase's own logs follow Supabase's schedule. Our team's mailboxes keep the email we exchanged with you, and the notices that brought us your feedback, for up to 3 years after the last message (section 2). If we suspended you, the one-way hashes of your email addresses stay while the suspension stands.

RightNow Agent. Its files are on your machine, and you can delete them yourself.

11. Your rights

Depending on where you live, you have the right to:

• access your personal information and get a copy of it in a portable form;
• have it corrected or deleted;
• restrict how we use it;
• withdraw your consent where we rely on consent, which does not affect what we did before you withdrew it.

Where we rely on our legitimate interests, you can also object at any time, and we will stop unless we have compelling grounds or need the information for a legal claim.

California residents can also ask what we collect, and opt out of its sale or of its sharing for cross-context behavioral advertising; we do neither.

To use these rights, email jaber@rightnowai.co. We will check that the request comes from you and answer within the time the law sets, and we will not treat you differently for using them. In the European Economic Area, the United Kingdom and Switzerland, you can also complain to your data protection authority.

For the console and the API, the copy you can ask for is one machine-readable file of the records our console database keeps about you. It names no one else and holds no API key, key hash or sign-in token.

12. Security

We protect information with measures such as:

• HTTPS;
• API keys and invitation tokens kept in our database only as one-way hashes;
• console cookies that your browser sends only to www.rightnowai.co, and only over HTTPS;
• database rules that let each person read only the data of their own workspaces and of the invitations sent to them.

No system is perfectly secure, so we cannot promise that information will never be accessed without permission. Keep your API keys secret, revoke any key that may be exposed, and sign out of the console on shared computers.

13. International transfers

We are based in the United States. If you use our services from another country, your information is transferred to and processed in the United States. Our providers may also process it in other countries where they operate: for example, requests to the API that include images, audio or picture documents are processed in India, the website's email is sent from Japan, and Cloudflare, Fly.io and Vercel run networks worldwide. Section 7 shows each provider's location where we have recorded it. Data protection law in those places may differ from the law where you live.

14. Children

Our services are not directed to children under 13, and the console is only for people 18 or older, or the age of majority where they live if that is higher. If you believe a child has given us personal information, email jaber@rightnowai.co and we will delete it.

15. Changes to this policy

We post every change on this page with a new date. If a change is material, we will tell console users by email or show a notice on the website at least 30 days before it takes effect.

16. Contact