Privacy Policy

Google or GitHub sign-in and your profile photo

If you choose Google or GitHub sign-in, we receive your name, email address, whether the address is verified, a stable sign-in identifier and your profile photo URL. We request no contacts or repositories. We use these details to sign you in to your iReliabee account.

We keep your Google or GitHub account identifier while your account exists, so later sign-ins reach the same account. To delete your account, write to [email protected]. Account deletion removes your stored profile photo and those Google and GitHub identifiers.

Profile photos are stored on our server (ireliabee.co.uk) and shown to people you collaborate with. Their browsers load our copy, never the provider's photo URL. You can upload or replace your photo, or choose Remove photo on the account page. Removal deletes the stored photo immediately and stops later sign-ins from adding it again. Replacement deletes the previous copy. Otherwise we keep it until you remove it or delete your account.

Figures in Write

Images you insert in a Write project are part of that project. When you edit it together, or keep it in the browser edition, we store those images with its text on our server. People with access to that project can see them. They are kept with the project and its existing version history; stopping sharing or deleting the hosted project removes them.

The short version

iReliabee supplies the AI. When you use a live session, a mock interview or anything else that thinks, your words go through our service on their way to the companies that do the speech recognition and run the model. So we handle the audio and the text of those sessions. We do not store them, and this page explains exactly what that means.

Everything you keep — your sessions, transcripts, CVs, stories, plans, notes, writing and library — is stored on your own computer, not on ours. What reaches us is the moment of use, not the record of it.

Your optional profile photo is also stored on our server (see Profile photos). There are four other exceptions, and each happens only if you choose it. A meeting reminder you ask for by email or text message is held on our server until it is sent, then deleted (see Meeting reminders). A Write project or a notebook you share is copied to our server, so the people you share it with can read it and comment, until you stop sharing it (see Sharing a Write project and Sharing a notebook). And if you use iReliabee in a web browser, the projects and notebooks you make there are kept on our server, because a browser has no app to keep them in, until you delete them (see Using iReliabee in a browser). And when you are signed in and Sync is on, your Speak progress and a few preferences are kept on our server so your devices stay in step (see Keeping your devices in step).

The rest of this page is the detail. We have tried to write it so you can check it against what the app actually does, rather than take our word for it.

Who we are

iReliabee is based in the United Kingdom and Ghana, and is responsible for your personal data as described here. For anything in this policy, including a request about your data, write to [email protected].

Where this policy talks about "we", that means iReliabee. Where it talks about "the app", that means the iReliabee desktop application for Windows and Linux. iReliabee in a web browser is described on its own, under Using iReliabee in a browser.

What we handle

This is the part that changed, so it comes first.

Earlier versions of iReliabee ran on API keys you created yourself, and your content went straight from your computer to the provider you chose. It no longer works that way. iReliabee now includes the AI, which means your content reaches the providers through us.

When you use a feature that thinks, the app sends us:

• Audio, while listening is on — your microphone, the meeting's audio, or both, depending on what you switched on. It is sent as it is captured, transcribed, and discarded, unless you choose On this computer under Settings → Listening: then it is transcribed on your computer and not sent to us or to any speech provider (see Transcribing on your computer). If you read the call in another language, each finished line of its transcript is then translated as text, like any other text job. Dictation (the microphone button in Write, Notebook, Ask, Speak and Talk, in the app) is the same: only your microphone, only from when you press it until you stop. Beside it in Write, Notebook, Speak and Talk you can choose, for dictation alone, On this computer (Parakeet), which keeps the audio on your computer, or Deepgram, which receives it through our relay, opted out of training as below, and uses credits. The words then go into your text on your computer; they are not sent to an AI unless you later use a feature on that text.
• Text — the transcript of what was said, plus whatever the job at hand is built from: the parts of your profile, CV, stories and library files it needs, and anything you give it to work on, such as a job description, a meeting agenda, a calendar invite, a talk script, or a work message you paste into Write it shorter in Practice. A cue built from your CV requires your CV. When you press Suggest beside any box in any of the app's forms, it is what you have filled in on that form so far, plus the parts of your profile it needs (and, in a live session, the last few lines of its transcript), so the suggestion fits. Nothing is sent until you press it, and never your name, email address, phone number, or any password, key or payment detail.
• Pages of a document, when you make reading notes from it — only the pages you chose, a few at a time as they are worked on, never the file itself. For a deep read, also the terms found in those pages with what the document says they mean, and how much you told the app you already know about the subject (new to it, some background, or expert). When you ask to understand a paragraph of your notes another way (in plainer words, explained for a newcomer, with an example or an analogy, step by step, or its key terms), that paragraph, the way you asked for and how simple or technical you want it, and for reading notes the text of the page(s) it came from. When you select words in a notebook and press Explain, those words, the line they are in, whether you asked for a basic or technical explanation, and (for reading notes) the text of the pages that line cites and of up to three pages of the document that mention the words. When you ask a follow-up question about words or a paragraph that was explained, your question, the explanation and your earlier questions and answers about it, those words or that paragraph with the same pages, and the notebook's title and summary. When you check your understanding of a paragraph, that paragraph (with its pages, for reading notes), the question you are asked and the answer you write, to mark it. When you ask a notebook's glossary to find unfamiliar terms, the notebook's text, the terms it already explains, and for each term found the line it is used in and a short passage of the document around its first mention. When you explain a chapter back from memory, what you wrote and that chapter's notes, to mark what you got. When you highlight a passage and ask for a mind map, that passage and, for reading notes, the text of the pages it cites and of up to three pages that mention it. When you study a chapter, that chapter's notes, to write the questions you read it for, and then each question with your answer and the notes it came from, to mark it; a question answered again in a later review is sent the same way. When you explain a chapter twice, both explanations (to an expert and to a beginner) with the chapter's notes. When you ask for a memory aid for a fact, a flashcard or a glossary term, that fact's own words (and its term), never the rest of the notebook, to suggest an acronym, a saying and a picture described in words; to tell two facts apart, both facts. Writing your own aid sends nothing. Spoken answers are transcribed first, as audio, like any practice answer.
• Your academic writing, in Write, when you ask for it to be checked. For a review, the section or whole draft, with the task, focus and thesis you gave it. For Find evidence, the sentence you selected, with the title, authors, year, venue and abstract of each paper found for it (up to 20). For a claim check, the section you check, with its title and citation markers, and the title, authors, year and abstract of each source it cites. Never your notes on a source, and nothing until you have seen the price and pressed the button.
• Text you ask to see in plain words, in Write or in a notebook: the words you selected, the section, or the whole document (each section's title and text), whichever you choose, and the level you pick (simple, very simple or key points). Up to about 1,700 words at a time. Then, in a second short request priced in with the first, that text again with its plain version, sentence by sentence, so the AI can say which plain sentences add something and which points are missing. Nothing is sent until you have seen the price and pressed the button. The citations, Bible references and numbers are compared with your text without AI (on your computer in the app; in a browser, by our AI worker, which keeps nothing). Neither text is kept by us, and the plain version changes your text only if you choose Keep as a note, Insert below or Replace. In the app, with your own AI assistant chosen in Settings → AI, the same text goes to that assistant instead (see If you use your own AI assistant).
• Your writing, read aloud with a Deepgram voice, in Write, only when you choose a Deepgram voice for Read aloud and press play: the text being read, a sentence or paragraph at a time, from where you start to where you stop, goes to Deepgram to be turned into speech. So that each word can be highlighted as it is said, the speech Deepgram has just made is then sent back to Deepgram to be transcribed, which says when each word starts and ends: the same words, as audio, and nothing else. The price is shown before it plays, and includes this. Reading aloud with your device's own voice sends nothing: see What stays on your computer.
• A topic you prepare to speak about, in Speak's Topics: the topic, who the talk is for (beginner, competent or executive), its length, and the title and an excerpt of up to 3,000 characters of each source you choose from your Library or Research (up to five), to build the pack's outline and terms. Then the topic with the terms and their one-line meanings, a few at a time, to write how each is said at three levels and the challenge it may meet. The excerpts are not kept in the pack, and a shared pack carries the sources' titles only. Your rehearsals are matched against the terms on your computer and send nothing.
• A screenshot, when you ask about what is on your screen — only the one taken for that question.
• The question being answered, and the conversation so far in that session.

We do not store any of it. It exists in our service for the length of the request — long enough to pass to the provider and pass the answer back — and is not written to any database or log of ours. We keep a record that the request happened, which is described under How long we keep things, and that record contains no part of what was said.

We do not use your sessions to train anything, we do not read them, and we do not sell or share them with anyone beyond the processors listed below who are doing the work.

What this costs you in privacy, stated plainly: iReliabee is now in the path of your interview answers and meeting conversations. We have designed that path to keep nothing, but it is a path that did not exist before, and you should decide about it knowingly rather than discover it here.

What stays on your computer

All of the following is written only to your own machine. There is no mechanism in the app to upload any of it to us:

• Sessions and transcripts — every practice session and live meeting, and what was said in it. We process this text in the moment; the stored copy is yours alone.
• Your profile, CVs, stories and library files — including anything you upload to the app.
• Plans, debriefs, meeting notes, recaps and study packs.
• Notebooks and reading notes, their earlier versions, and the PDFs you make them from (the file and the text read from each page). The one exception is a notebook you choose to share, described under Sharing a notebook; its recording, transcript and PDF stay here even then.
• Your writing in Write — projects, drafts, sources and their abstracts, and the reviews, evidence and claim checks you have run on them. The one exception is a project you choose to share, described under Sharing a Write project.
• Spelling, grammar, the thesaurus and your device's own voice in Write — the spelling dictionaries (English UK and US) and the thesaurus (from Open English WordNet) come with the app, and the checks and look-ups run on your device. The words you add to your dictionary are kept on it. Reading aloud with your device's own voice uses the speech your device already has; the text never leaves your device. Voices that your browser offers online (such as Google's or Microsoft's online voices) are never used, because they would send the text to their maker.
• Calendar data — meetings you create in iReliabee, events from calendars you connect, and the sign-in tokens or private iCal links used to fetch them. Calendar access is read-only; the app never writes to your calendar. The one exception to "stays on your computer" is the text of an email or text-message reminder you turn on, described under Meeting reminders.
• Feature usage counts — how often each screen is opened, used to decide what to improve. These are counts only, never text, and they are excluded from exports and never transmitted.
• A local log file for diagnosing problems, at ~/.config/ireliabee/backend.log.

On most systems this lives in ~/.config/ireliabee and ~/.local/share/ireliabee. You can export or delete all of it from Settings → Your data, or by deleting those folders.

Microphone and meeting audio are captured only while you have turned listening on, and stop the moment you pause or stop. Audio is never recorded to a file, by the app or by us — it is transcribed as it arrives and the text is stored on your computer as described above.

What leaves your computer

There are ten kinds of outgoing request, and this is all of them.

1. The AI service

Described in full under What we handle. In short: audio and text go to ireliabee.co.uk, which forwards them to the speech and model providers on our account, and passes the answer back.

2. Signing in, and your credits

Signing in sends your email address so we can send you a link. Once signed in, the app asks us for your credit balance and tells us when a session starts and stops, so that the right number of credits is spent. Those messages carry the kind of session and how long it ran. They do not carry what was said in it.

The app also sends a device identifier and a device name, so that a lost laptop can be signed out without ending your other machines. The identifier is a one-way hash of your computer's machine ID with a salt specific to iReliabee. We cannot reverse it, and it cannot be matched to the same machine by any other product. We never read your computer's MAC address or serial numbers.

The free monthly credit is one per account, in the app or in a browser. To stop it being claimed by account after account, a new account's first free credit is held back when many new accounts have claimed one from the same computer or the same network that month. For that we keep, with each new account's first free credit, its device identifier and a one-way, salted hash of the network address the request came from — never the address itself — for two months, then delete them.

3. Update checks

The app checks cdn.ewooral.com for a newer version. That request necessarily reveals your IP address, your operating system and the version you are running. It contains nothing else.

4. Web search, if you use People research

People research queries a web search provider. The names and organisations you search for go to that provider under their privacy policy.

5. Buying credits

Handled by Paystack, and described under When you buy credits.

6. Meeting reminders by email or text message, if you turn them on

Reminders that pop up on your computer never leave it. An email or text-message reminder has to, because our server sends it, so that it reaches you even when your laptop is asleep or switched off.

These are off until you turn them on, meeting by meeting. When you do, the app sends us, for each reminder:

• when to send it, and whether by email or text message;
• the meeting's title as you wrote it, its time in your time zone (and in theirs, if you set one), the join link or place, the topics, and what you noted to prepare;
• for a follow-up you ask to be reminded of by email or text (something you promised, or were asked to do, after a meeting): its text, its due date and the meeting it came from.

You can read this text in the app before you turn the reminder on. It never includes the meeting's notes, your plan for it, the people you linked to it, transcripts, or anything from your other meetings.

Emails go to your account's email address. Text messages go only to a Ghanaian mobile number you add in Settings and confirm with a code we text to it. We use that number for your reminders and for important messages about your account, such as a problem with a payment. We never send marketing to it unless you have separately agreed to that.

A text message shows on your phone's lock screen. If a meeting's title or topics are private, keep them short or use email.

Text messages cost credits, a small amount for each message; the app shows the price before you turn them on, and each one appears in your credit history. Email reminders are free.

7. Finding papers in Write

Searching for papers, and checking your sources for retractions, sends search words, filters and DOIs to public scholarly indexes, straight from your computer. Find evidence takes its search words from the sentence you select, and shows them to you first. The originality check sends short excerpts of your draft to the same indexes only when you tick "Also search open published papers" for that check. All of it is described under Finding papers and adding sources in Write.

8. Sharing a Write project, if you share one

Nothing in Write is shared until you press Share on a project. Then a copy of that project goes to our server, and the comments people leave on it come back to the app. If you also turn on Edit together for it, every change you or the people you invited make to it goes through our server while you are online. All of it is described under Sharing a Write project.

9. Sharing a notebook, if you share one

The same goes for Notebook: nothing in it is shared until you press Share on a notebook, and then only that notebook's notes go to our server, never the recording, transcript or PDF it was made from. It is described under Sharing a notebook.

10. Reading aloud with a Deepgram voice, if you choose one

Only when you choose a Deepgram voice for Read aloud in Write and press play. The text being read goes through our service to Deepgram, which returns it as speech. Our service then sends that speech back to Deepgram to be transcribed with the time of each word, so the app can highlight each word as it is said. Each request, the speech and its transcription, opts out of Deepgram's Model Improvement Program, so Deepgram does not use the text or the speech to train its models. It costs credits, and the app shows the price before it plays. Audio you have already heard is kept on your device so that hearing it again is free. It is described under What we handle.

11. Downloading an on-device speech model, if you choose one

Only when you choose one of the On this computer options under Settings → Listening. The app then downloads that speech model (about 480 MB for Parakeet, about 106 MB for the streaming FastConformer model) from the sherpa-onnx project's releases on GitHub. That is an ordinary file download: GitHub sees your address and that you fetched the file, and nothing from your account or your sessions is sent. It is described under Transcribing on your computer.

Transcribing on your computer

By default, speech is turned into text by the providers named under Who processes it for us. Settings → Listening has a second choice, On this computer, in two forms, both running on your own computer through the open-source sherpa-onnx library: NVIDIA's Parakeet-TDT 0.6B v2 speech model, and NVIDIA's streaming FastConformer model, which writes words as they are spoken. You may choose one of them, or neither.

• Your audio is transcribed on your computer and is not sent to iReliabee or to any speech provider. Nothing about it leaves the machine, so it uses no credits.
• Each model is downloaded once, from the sherpa-onnx project's GitHub releases, and then works without a connection. You can remove either one in Settings at any time.
• While you are speaking, Parakeet re-reads the audio you have spoken so far, about once a second, to show words before you pause. That happens inside the app on your computer; nothing is sent anywhere.
• The words it produces are then used like any other transcript: stored on your computer, and sent as text to the AI when a feature needs it, as described under What we handle.
• It understands English only. In any other session language, the app keeps using the default speech provider.
• Parakeet is licensed Creative Commons Attribution 4.0 (CC-BY-4.0) by NVIDIA. The streaming FastConformer model is also NVIDIA's, converted by the sherpa-onnx project, and is used under the terms NVIDIA publishes for it, linked from Settings.

Who processes it for us

We do not run speech recognition or language models ourselves. We choose which company does each job, and can move a job from one to another — to keep the service running when one of them fails, or to get a better or cheaper result. Your content reaches whichever of these is doing the work:

• Language models — writing cues, answers, debriefs, plans, recaps, study packs, translations, reading notes, the answers to questions you type in Ask iReliabee (the question is sent with the matching help text from the app) and the text suggested for a form when you press Suggest, reviewing your academic writing and checking it against the papers it cites or could cite, and reading screenshots: Groq (privacy policy), Anthropic (privacy policy), OpenAI (privacy policy), Google (privacy policy) and DeepSeek (privacy policy). For each kind of job we choose one of them to do the work, and can choose a second to take over when the first is unavailable; any of the five can be either. Screenshots are only ever read by Anthropic, OpenAI or Google. When we use Google's free tier, Google may use what it receives, screenshots included, to improve its products; on its paid tier it does not. DeepSeek handles your content differently from the others — see DeepSeek below.
• Speech — turning audio into text: Deepgram (privacy policy), Groq or OpenAI, chosen the same way. If you choose On this computer in Settings, none of them receives your audio: it is transcribed on your computer (see Transcribing on your computer). The voice of the mock interviewer is Deepgram's, and a voice mock interview's conversation is also read by a Google model, which Deepgram runs for us. When you choose a Deepgram voice for Read aloud in Write, Deepgram also receives the text being read, to turn it into speech, and that speech, to time each word for the highlight (see What we handle). Deepgram is in the United States.
• Cloudflare — sits in front of our service and this website, so every request passes through them. They also tell us which country a request comes from, which sets the price you see (see This website). Privacy policy
• Contabo — rents us the server our service and our mail run on, in France. Privacy policy
• Paystack — payments. Privacy policy
• Lemon Squeezy or Dodo Payments — when one of them is switched on, sells credits to buyers outside Africa as merchant of record (see When you buy credits). Lemon Squeezy's privacy policy · Dodo Payments' privacy policy
• Arkesel — sends the text-message reminders you ask for, and the code that confirms your number. It receives your phone number and the message, and passes them to your mobile network to deliver. Arkesel is in Ghana. Its privacy policy does not say how long it keeps the messages it sends. Privacy policy

Sign-in links and receipts are sent through Resend (privacy policy). When Resend is unavailable, sign-in links go through our own mail server instead; receipts are only ever sent through Resend. They carry your email address and nothing from your sessions; a receipt also carries your first name if Paystack has it, what you bought and your new balance. Meeting reminders you ask for by email are sent the same way, through Resend or, when it is unavailable, our own mail server, and carry the reminder text described under Meeting reminders. Emails about new comments on a shared Write project go the same way and carry the comment, the words it is on, its section, the commenter's name and the project's title, as described under Emails about new comments.

When a new account is created, we also tell our own administrators. The email, to our own admin mailbox and sent the same way (Resend or our own mail server), carries the new account's email address, its name if it has one, how it signed in, the time and how many accounts there are. A text message through Arkesel goes too, and carries none of that: only how the person signed in and the number of accounts, never an email address or a name.

We use these companies' business APIs, whose terms say that content sent through them is not used to train their models. Deepgram is an exception by default — it keeps audio for training unless each request opts out — so every request that sends it your audio, your writing to read aloud, or a phrase for a voice preview or the pronunciation helper, opts out (Deepgram's Model Improvement Program covers text-to-speech too, and is left with mip_opt_out=true on the request). DeepSeek is the other exception, and one we cannot opt out of for you; see below. Their policies are linked above and they, not we, are the authority on their own practice; if this matters to you, read them.

DeepSeek. We use DeepSeek because it costs far less than Anthropic's models, which keeps credits affordable. We may choose it to do a job outright, not only to take over when another provider is unavailable. It works differently from the rest, in two ways you should know about:

• It is in China. DeepSeek's privacy policy says it collects, processes and stores personal data in the People's Republic of China.
• It may train on what you send. DeepSeek's privacy policy lists training and improving its models among the uses of the data it receives. Its terms for businesses using its API do not say otherwise, and it offers us no way to opt out on your behalf. Assume that anything a request to DeepSeek carries — the conversation so far, your notes, CV or documents where the job needs them — may be kept and used that way.

DeepSeek only ever works on text. It can be given any job where iReliabee writes something for you to read, apart from reading a screenshot, so what it may receive is:

• In Ask iReliabee — the question you type, with the matching help text from the app (the names and descriptions of features and where they are) and the name of the screen and item you have open (for example "Write, TEST name tags"; never its text), when iReliabee's AI answers it. Files and images you attach are never sent to it.
• During a call or a practice session — the transcript so far and the question being answered, for cues, answers and the follow-up questions you are likely to be asked next, and each finished line of the call when you read it in another language (caption translation).
• Afterwards — the saved transcript, for debriefs, confidence scores, meeting notes and recaps, follow-up emails and study packs, and to translate it into another language when you ask.
• When you prepare — a job description or meeting agenda you paste or link to, a calendar invite you make a plan from (including the names and email addresses of the people invited), a talk script you rehearse, notes you turn into stories, what People research found about the person you are meeting, your answers in mock interviews, drills and practice tests (including Talk at work's situations and 60-second talks), a chat message or email you paste into Write it shorter, and what you have filled in on a form when you press Suggest for one of its boxes. In the Research track this includes the research proposal, replication plan, paper summary, paper draft, peer review or talk you practise with the supervisor, journal club, proposal panel, reviewer, conference audience, viva committee or professor. In Wordcraft, the English course, this includes the writing you ask the Editor to check, with the task it answers, and your answers when you talk to a Wordcraft character (the Guide, Shopkeeper, Neighbour, Colleague, Debater, Interviewer or Audience). Wordcraft's cards, exercises and placement check run on your computer and send nothing. In Speak's Scene Lab, when you pay with credits, this includes the description of a scene you type and ask to have checked, each revision you check, and the scene's own text (its title, the facts it shows and its labelled words). Speak's games and the rest of Scene Lab run on your computer and send nothing. In Speak's Topics, it includes the topic, audience and length of a talk you prepare, the titles and excerpts of the sources you choose for it, and its terms with their meanings; rehearsing sends nothing, and practising a challenge with Challenge me sends nothing either.
• Your own material — the parts of your profile, CV, stories and library files that a job is built from, your notebooks, and the text of the document pages you make reading notes or a deep read from, with the terms found in them, the words you select in a notebook to have explained, with their line and pages, the follow-up questions you ask about them, the answers you write when you check your understanding of a paragraph, a passage you highlight for a mind map, a chapter's notes and your answers when you study it or review its questions, your two explanations when you explain a chapter twice, a fact's words (or two facts) when you ask for a memory aid, a notebook's text when its glossary looks for unfamiliar terms, the transcript of a video you saved from a link when you ask to tidy it (with the video's title, channel and description, so its speakers can be named), and in Write, the academic writing coach: the section or whole draft you ask it to review, with the task, focus and thesis you gave it and the kind of writing it is; a sentence you ask it to find evidence for, with the titles, authors, years, venues and abstracts of the papers found for it; and a section you claim-check, with the titles, authors, years and abstracts of the sources it cites. It also includes the words, section or whole document you ask to see in plain words, in Write or in a notebook, with the level you chose, and that text with its plain version for the sentence-by-sentence check. This includes the review and the notebook study tools when your own assistant asks for them through iReliabee's paid tools, if you choose Standard for them (the default, Anthropic only, never uses DeepSeek).

It never receives audio, which goes only to the speech providers above, and it never receives screenshots. If you would rather none of your content went to DeepSeek, email [email protected] and we will tell you what we can do. If we add a provider, it will be named here first.

These providers are outside the United Kingdom and Ghana, so using iReliabee means your content is processed in other countries: mainly in the United States and the European Union, and in China when DeepSeek does the work.

If we add or change a processor in a way that affects what happens to your content, we will say so in the app's release notes as well as updating this page.

If your account uses its own API keys

Most accounts never see this: it applies only if iReliabee has switched on own API keys for your account, and you have then entered keys of your own in the app. We can switch it off again at any time, and your account then goes back to credits and to the path described above.

With it on, the app sends your content — audio, text, document pages and screenshots, as listed under What we handle — straight from your computer to the provider whose key you entered, not through us. Which providers that can be is your choice: Anthropic, OpenAI, Google (Gemini), Groq, DeepSeek or Deepgram, and Tavily, Brave or GitHub for research. You use them under your own agreement with that provider, and its terms decide where your content is processed and whether it is kept or used for training — not ours, and not the list of processors above. DeepSeek, for example, processes data in China and may train on it, as described above.

Your keys are stored on your own computer and are never sent to us. We do not see or keep the content of those requests, and they are not charged in credits. A job for which you have not entered a key still goes through us, as described above, and is charged in credits. The app still signs in with us and checks your account and balance, as every account does.

If you use your own AI assistant

If you choose My subscription in Settings → AI, the app uses the assistant you pick there, for Ask iReliabee and for text features alike, and connects to your local assistant (such as Anthropic's Claude Code or Claude Desktop, OpenAI's Codex, or Google's Gemini CLI or Gemini in Antigravity) through the Model Context Protocol (MCP) rather than spending iReliabee credits. With Codex, what it reads goes to OpenAI; with Claude Code or Claude Desktop, to Anthropic; with Gemini CLI or Antigravity, to Google: each under your own account and that company's terms. Text features run on the assistant you chose: Claude Code, Codex or Gemini CLI. On Google's free tier, Google may use what Gemini receives to improve its products.

Setting it up from the app. When Ask iReliabee can't reach an assistant, it looks for Claude Code, Codex, Gemini CLI and Claude Desktop on your computer and offers to connect them. It changes nothing until you click Connect: then it adds iReliabee to that assistant's own settings on your computer (for Claude Desktop, after keeping a copy of its settings file next to it). Nothing about this is sent to us. When you choose your own assistant in Ask and none is listening, iReliabee starts the assistant you picked on your computer, on your own plan, to answer: Claude Code by default, or Codex (on your ChatGPT plan) or Gemini CLI (on your Google plan) if you pick one in Settings or in Ask; that assistant can use only iReliabee's tools, each asking you first as described below. Access to your files and command line is off unless you enable the separate setting described below. It keeps listening until you stop it (Ask shows a Stop, and asks whether to keep it running after ten minutes without a question) or quit iReliabee.

In this mode, content is processed by the assistant you connect under your own account and that provider's terms, not by iReliabee. Only the text needed to complete the task is sent: text features such as notes, documents, CV, stories, plans, call transcripts, practice answers, selected passages, your academic writing in Write with the abstracts of the papers it is checked against, or prompt instructions. When using the Live Companion with your own assistant, answers may take 5–15 seconds to stream back through your assistant. Audio, speech transcription, and screenshots never go through this relay; they are always handled by the service as described elsewhere in this policy.

The relay runs entirely on your own computer over a loopback connection protected by your local app token. We do not see, relay, or store the content or the answers, and those requests are not charged in credits. If no assistant is listening or you choose to fall back to credits, the request goes through us as described under What leaves your computer.

If you also turn on Use my Claude subscription, the app starts Claude Code on your computer by itself when a feature needs it, signed in with your own Claude account, and it stops when there is nothing left to answer. Those runs can use only the iReliabee relay: none of your other MCP servers, and no tools that read files, run commands or browse. They are not saved in your Claude Code history, and they count towards your Claude plan's usage limits under Anthropic's terms, not iReliabee credits.

If you let your assistant use this computer's terminal and files

This is available only in the Windows and Linux desktop app. It is off by default. In Settings, under Assistants, you can enable Let your assistant use this computer's terminal and files, after confirming the explanation. You can switch it off there at any time. Switching it off stops running commands and removes these tools from your assistant's available tools.

Each folder listing (list_folder), text file read (read_file), file-name search (search_files) and text search (search_text) asks you first. Each command (run_command) always asks, showing the exact command, working folder and shell. Commands can change or delete files and use the network with your computer's permissions. Approve only commands you understand. There is no Always allow or auto-accept for these tools. They are blocked during live calls.

Only the folder names, file names, text or command output covered by your approval are returned to the assistant you chose and then to its provider under your own account and its terms. They do not pass through iReliabee's servers. command_output asks you before that same assistant collects output from its approved command. Text reads are limited to about 200 KB; binary files are refused. Text searches skip binary files, files over 2 MB, .git and node_modules, and return a limited number of matching excerpts. Command output is limited to about 100 KB, keeping its beginning and end.

File tools only use folders you add in Settings, under Folders Ask can use. You choose read-only or read-and-write access and can revoke it at any time. Commands need a read-and-write working folder, but can still reach other locations with your computer's permissions, so each command needs approval.

Before returning text, the app removes recognisable API keys, tokens, password assignments and private keys. This automatic check cannot recognise every secret. Sensitive locations, including SSH keys, iReliabee's settings, browser profiles, password stores and environment files, are refused by the file tools. A command is a general-purpose shell and can reach other locations: the file-tool restrictions do not make an approved command safe.

Commands stop after 60 seconds unless you choose ten minutes on the approval card. You can Stop a command while it runs. Quitting the app or switching access off stops its commands too. A local activity log records the time, path or command, and the command's exit status, without file contents or output. You can view and clear it in Settings. Recognisable secrets in log entries are removed. The log follows the same local retention limits as the assistant activity log below.

Computer tools (optional)

Once terminal and file access is on, you can also switch on computer tools in Settings, Connected assistants. They are off by default, and you confirm before they turn on. With them on, your assistant can ask to:

• create, edit, patch, copy, move and remove files and folders (file_operation). Nothing is overwritten or deleted outright: the original file or folder is kept beside it as a recovery copy until you remove it;
• open an application (launch_application), and install or remove software for your account only (software_package: winget on Windows, Flatpak on Linux), which downloads from those repositories;
• check or stop a process it started (process_status, stop_process);
• on Windows, list open windows (desktop_windows), capture a window you choose (desktop_capture) and click or type into it (desktop_input). A capture can contain anything visible in that window.

Every operation asks you first, including reads, unless you explicitly switch on Allow routine edits in these folders until I stop. This session permission covers only new files, edits, patches and new folders inside your read-and-write folders. Commands, deletes, copies and moves still ask. A tool you set to Never stays blocked. The session ends on Stop all, when you turn it off, or when the app restarts. Each file change is logged and can be undone from the activity log while its recovery data is available; Undo refuses if the affected files have changed since or the folder is no longer authorised. There is no Always allow for these tools. The card shows exactly what will run: the command, paths and working folder, with a limited diff preview for new files, edits and patches. Commands and applications run with your account's permissions and can have effects the card cannot predict.

Your assistant cannot see or control iReliabee's own window or Windows security prompts, is refused for password, payment, verification and CAPTCHA steps, cannot read SSH keys, password stores or other credentials, and gets no administrator access. Stop all in Settings cancels anything waiting for approval and ends the processes these tools started. It cannot undo a change already made.

Commands you run yourself

Some steps should never go through an assistant: signing in, using keys or passwords, connecting to a server. For these your assistant can only suggest a command (propose_command). It appears in Ask under "For you to run" with the assistant's reason. Nothing runs until you choose Run in my terminal, which types it into a terminal inside Ask, and you press Enter.

That terminal is yours. What you type and what it shows stay on this computer: they are not recorded, not sent to iReliabee, and not visible to your assistant. Your assistant sees terminal output only if you choose Share output…: iReliabee removes recognisable secrets, you review and can edit the text, and it is added to your next question, which you send yourself. It then goes to your assistant and its provider like anything else you ask. The terminal runs as your account, without iReliabee's own internal keys.

Code mode: your own Claude Code working in a project folder

In the Windows and Linux desktop app, Ask has a Code mode. In it you choose a project folder you have allowed for reading and writing (Settings, Folders Ask can use, or Add a folder in Code mode), and iReliabee starts Anthropic's Claude Code on your computer, in that folder, signed in with your own Claude account and on your own Claude plan. It uses no iReliabee credits, and it is never started with an API key of ours or yours: the app removes any Anthropic key from its environment so it uses your plan.

With your approval, Claude Code can read and change files in that folder, run commands such as your tests, and use git and GitHub on your behalf: create branches and commits, push, open pull requests with the gh tool, and merge when you say so. It uses your own git identity and your own GitHub sign-in on this computer; iReliabee never sees or stores them. What Claude Code reads (file contents, command output, your messages) goes to Anthropic under your account and Anthropic's terms, the same as using Claude Code in a terminal. It does not pass through iReliabee's servers, and none of it is sent to iReliabee's AI providers, including DeepSeek.

Claude Code asks before it changes a file or runs a command, as a card in Ask: Allow once, Always for this project or Deny. Some steps always ask and can never be allowed for good, even if your own Claude Code settings would allow them: anything that reaches another computer (push, pull, fetch, gh, downloads, SSH), merges, rebases and other history rewrites, force options, deleting or moving files or branches, publishing packages, administrator rights, and changes outside the project folder or to files that hold keys or secrets. "Always for this project" answers are kept on this computer and you can remove them. Command output shown in Ask has recognisable secrets removed first; this check cannot recognise every secret.

The conversation is Claude Code's own: Claude Code keeps it in its history on your computer, so you can continue it in your terminal (Open in terminal types claude --resume for you), and Ask can show and continue conversations you started with Claude Code in a terminal in that folder. iReliabee reads that history on your computer only when you open the list, and keeps only which conversations were started from Ask. It does not start during a live call. Claude Code stops when you close the conversation, after 20 minutes without use, and when iReliabee quits.

Mail and calendar connections (optional)

In Settings, Connections you can connect a Google account (Gmail, Google Calendar) or a Microsoft account (Outlook mail and calendar). You sign in on Google's or Microsoft's own page and choose what to allow. iReliabee asks to read your mail, save drafts, and read your calendar events; it never sends, forwards or deletes mail. Your sign-in is kept in your computer's keychain and is not sent to iReliabee's servers. You can disconnect at any time; iReliabee then forgets the sign-in and, for Google, revokes it.

Mail and events are read on your computer when you search, open one, or turn one into a task. When you ask your own assistant to use them, it can ask to search_mail, read_mail, read_mail_thread, draft_mail_reply (saved as a draft, never sent), list_calendar_events, read_calendar_event and list_connected_accounts. Every one of these asks you first, showing the account and, for a draft, the exact text and recipient; you can turn any of them off. What an approved request returns, including the words of an email, goes to that assistant and its provider. iReliabee's own AI, and so none of the providers in Who processes it for us (including DeepSeek), is never given your connected mail or calendar.

iReliabee's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. iReliabee does not use Gmail data for advertising, does not sell it, and does not use it to train AI models.

If you let your own assistant use iReliabee's tools

Optional desktop terminal and file access has its own setting and approvals, described above.

Ask doesn't currently use other connectors you've set up in Claude Code.

You can connect an AI assistant you already use on this computer, such as Anthropic's Claude Code or Claude Desktop, to iReliabee through the Model Context Protocol (MCP), so it can look things up in iReliabee for you, open a screen in the app or move around it while you watch and, when you allow it, add a note, pin a sticky note to an idea board, change a section's text, create a project or notebook, or run Write's review or a notebook study tool on your credits. This is the other way round from using your own AI assistant: there iReliabee gives your assistant work to do; here your assistant asks iReliabee for something.

iReliabee asks you every time. Each request shows a card in the app saying exactly what the assistant wants and what it will get, with Allow once, Always allow this tool and Deny. Nothing is sent until you answer, and if you don't answer within 50 seconds nothing is sent. The card shows the name the assistant gives itself, which iReliabee can't check, so allow a request only when you have just asked your assistant for it. Always allow belongs to that one connection, not to the name: it lasts until that assistant restarts or you disconnect it, and another program calling itself by the same name is asked again. An assistant that connects without a connection key can only be allowed once. While iReliabee is listening to a call or a voice practice, every tool is refused without asking, unless you turn on Tools during calls.

Auto-accept, for one connection only. In Settings → Connected assistants you can let one connection use every read tool, or every read and write tool, without a card. Like Always allow, it belongs to that connection and ends when the assistant restarts or you disconnect it; it is never set for every assistant at once, and a connection without a connection key can't have it. It never applies while tools are off during a call, or to a tool you set to Never. Some tools always ask, whatever you set: list_meetings (meeting details), read_session (what other people said), get_live_session (the call that is on now), read_meeting (who is invited and what the invite says), delete_note and delete_board_note (anything that deletes), reading a meeting notebook, reading a project or notebook someone else shared with you, the paid tools, every action in iReliabee's browser window or your own browser, and any tool that would share, invite, delete or send. A write that runs without a card shows a notice in the app straight away, so you can undo it.

What you allow goes to your assistant's provider. Your assistant sends what a tool returns to its own company to be processed, under your account with them and their terms: for Claude Code and Claude Desktop, that is Anthropic. Their terms decide where it is processed, how long it is kept and whether it is used for training, not ours. The connection runs only on your computer, over a loopback connection locked with your pairing key. Our service doesn't see, relay or keep these requests or what they return, and none of it is sent to DeepSeek or to any of the providers we use, with one exception: the two paid tools below send your content to iReliabee's AI to do their job, to Anthropic only unless you choose otherwise.

What each tool returns:

• ireliabee_overview and feature_help: iReliabee's own description of its features. None of your data.
• list_projects: your Write projects' titles, kinds of writing, word counts, word limits and dates.
• list_notebooks: your notebooks' titles, kinds, number of sections and dates.
• list_boards: your idea boards' titles, number of notes and dates. Never what the notes say.
• list_documents: your Library documents' names, file names, file types and dates. Never what is in them.
• list_sessions: your sessions' titles, kinds, number of turns and dates. Never what was said.
• read_session: one session's transcript, as it was said: each line marked as yours or the other people's, up to 24,000 characters a request. It includes what other people said on the call or in the lecture. Never the audio, text read from your screen, the coach's answers, the debrief or a translation. It always asks.
• list_meetings: your calendar meetings' titles, start and end times and the kind of calendar (Google, Microsoft or an iCal link). Not the invite's text, the people invited, the join link or the calendar's account.
• get_live_session: the call or practice that is on now: its title and kind, the plan it follows and the latest 60 lines said, each marked as yours or the other people's. It includes what other people said. It works only during a call, when you have allowed tools then, and it always asks.
• read_meeting: one calendar meeting's invite: the title, times, place, organizer, the people invited with their email addresses, and the invite's text. Not the join link or the calendar's account. It always asks.
• read_progress: your sessions' scores, filler words, pace and confidence, your practice minutes and your streak, as the Progress screen shows them. Not what was said.
• read_board: one idea board's sticky notes: their text, colours and pins.
• read_document: the text iReliabee found in one Library document, up to 24,000 characters a request. Not the file itself.
• read_account: whether you are signed in, your credit balance and which AI answers your questions. Never payment details, cards or invoices, and it can't change any of them.
• search_content: where a word or phrase appears in your notebooks and Write projects: the notebook or project, the section and a few words around it.
• list_notes: the numbered notes of one notebook section, so a note can be named.
• read_project: one Write project's brief, focus, thesis and the text of its sections, up to 24,000 characters a request. Not your section notes. A project you edit with other people includes what they wrote.
• read_notebook: one notebook's notes as text, up to 24,000 characters a request.
• get_notebook_formatting_capabilities, read_notebook_structure, format_notebook: inspect editor formatting capabilities, view rich notebook structure, and apply inline or block formatting styles (bold, italic, underline, strike, highlights, colors, headings) with previews and Undo support.
• open_screen: nothing. It brings iReliabee to a screen.
• app_action: nothing from your data. It moves the app while you watch: it opens a notebook at a section, a Write project at a section, an idea board, a session, or Deep Read's "What should I cover?" for a Library document, turns the open notebook's page, or scrolls. It returns only that it did so. Deep Read makes nothing and spends nothing until you choose there.
• capture_app_screenshot: captures a screenshot of the application window. Always asks you first.
• control_live_session: controls an active session (pause, resume, stop), toggles microphone or captions, or sets overlay modes. Always asks you first.
• run_simulation: practice speaking drills using predefined fictional scenarios and personas, clearly labelled [SIMULATION: FICTIONAL DATA].
• practice_activity: lists practice drills or retrieves drill details.
• get_settings: reads your app preferences (persona, tone, pause tolerance, text size). Never API keys or secrets.
• list_research_projects and read_research_project: your research proposals and replications.
• list_research_terms: scientific and methodological terms in your term bank.
• list_paper_cards and read_paper_card: your academic paper reading cards.
• get_share_status: checks whether a Write project or notebook is shared. Always asks you first.
• export_content: exports a Write project or notebook as formatted Markdown.
• list_tasks: your to-do tasks across iReliabee.

The write tools change only your own content on this computer, and return only what they did and the ids they touched (for example "added a note to notebook 12, section 2"), never your text:

• add_note: adds a note your assistant wrote to one of your notebooks, in a section that is there or a new one with the title it gives.
• edit_section: replaces the text of one section of a Write project with text your assistant wrote.
• edit_note, move_note, delete_note, rename_notebook, rename_section: change a note or a title in a notebook. Each asks first and shows the exact change; a delete always asks and can be undone. They return only that they worked.
• update_board_note, delete_board_note: change, recolour, move or delete one sticky note. Same rules.
• update_project_details, edit_section_part, add_source: change a Write project's brief, focus or thesis, replace one passage of a section, or add a source you describe. Nothing is looked up or fetched.
• add_story, create_plan, add_to_library: add a story, a meeting plan or a text document you write. Links are not fetched.
• add_board_note: pins a sticky note your assistant wrote to one of your idea boards.
• add_task: adds a task your assistant wrote, with an optional due date and priority, to your task list, optionally linked to an email it found with your approval.
• create_project and create_notebook: make a new, empty Write project or notebook with the title your assistant gave.
• update_settings: updates app preferences (persona, tone, pause tolerance, text size). Previews the change and can be undone.
• create_research_project, update_research_project, delete_research_project: create, update, or remove research proposals and replications. Deletes always ask and can be undone.
• add_research_term: adds a term, definition, and example to your research term bank.
• create_paper_card, update_paper_card, delete_paper_card: create, update, or remove paper reading cards. Deletes always ask and can be undone.
• share_item and stop_sharing: create, update, or revoke a public share link for a project or notebook. Always asks you first.
• update_task and delete_task: update title, due date, priority, or completion of a task, or remove it. Deletes always ask and can be undone.

You see it being written. When a write runs, the app goes to what it changed and shows the new words appearing, with a caret named iReliabee, and everything your assistant wrote carries an iReliabee tag. The tag is a note kept on your computer of which words it wrote: it is never sent to us, to your assistant or to any AI provider, and it isn't in exports (the data transfer file included), prints, shared copies or a notebook you edit with others. Words you change become yours and lose the tag.

The card for a write shows the exact change before anything happens: the note's whole text, or a section's words before and after with what changed, or the new title. What your assistant wrote is marked as its own and shown as text, never as a web page: a link shows its whole address and can't be clicked. A write can be at most 20,000 characters and nothing it contains is fetched or opened: a link stays text, and no file or photo can be attached. An assistant can't change a project or notebook that is shared and edited together, or one shared with you in a role that can't edit it. Once written, what your assistant wrote is part of your content, like anything you type: if you later use a feature on it, it is handled as that feature describes in this policy.

Undo. Before each write, iReliabee keeps what it needs to undo it (the section's text it replaced, or which notes or sticky note it added) on your computer, with the activity log, so you can press Undo on that entry in Settings → Connected assistants. Undo works only if nothing has changed since, so it never undoes your own edits; if something has, it says what. Undoing a new project or notebook removes it only if it hasn't been touched, and moves it to Removed by Undo, where you can restore it for 90 days. These copies are kept for as long as the log entry is (the last 500 requests, up to 90 days), never leave your computer, and go when you clear the log or delete that project, section or notebook. Only you can press Undo, in the app: no assistant can undo, restore or delete anything.

A browser window your assistant can use. When you allow it, your assistant can open web pages in a real Chrome, Firefox or Edge window on your computer, read them, look at them and use them: click, type into boxes, choose from lists, press a key, go back. Unless you turn on the iReliabee extension (below), the window uses iReliabee's own browser profile, kept on your computer (~/.local/share/ireliabee/browser), not your everyday one, so the passwords, cookies and accounts in your own browser aren't used. Anything you sign in to there yourself stays in that profile on your computer until you sign out or delete the folder.

Using your own browser, with the iReliabee extension. If you add the iReliabee extension to your everyday Chrome or Edge and switch it on in its menu, your assistant can open a tab there instead, where you are signed in. That tab can see and use what you are signed in to on the site it opens, as you could: your email, your accounts, anything behind a sign-in. So the card for opening a page says so, every time, and you can't allow it always.

• It uses only tabs it opened itself, one at a time, never your other tabs, and it can't close or change your browser as a whole. Chrome shows its own "is debugging this browser" bar while it works; closing the tab, or pressing Cancel on that bar, stops it at once. Switching the extension off stops it too.
• The extension talks only to the iReliabee app on this computer, through your browser's native messaging, locked with a key of its own. It sends nothing to us or anyone else, keeps no browsing history and has no access to your tabs until it opens one for a request you allowed.
• What the tab returns to your assistant, and where it goes, is as above: the page's address, title, text and parts, and screenshots of that page, to your assistant's provider. Never what is in a password or card box, and it never types into one.
• To use it, the app registers the extension's helper with Chrome and Edge for your Windows or Linux user only. Uninstalling iReliabee, or removing the extension, ends it.

• browser_open, browser_click, browser_type, browser_select, browser_press and browser_back act on a page, so each asks you every time: the card names the address, the button or box, and the exact text to be typed. They can't be allowed always or auto-accepted.
• browser_read, browser_scroll, browser_screenshot and browser_close only look, and ask like iReliabee's other read tools.

What they return to your assistant: the page's address, title and text, a list of its links, buttons and boxes with what is typed in them, and, for browser_screenshot, a picture of that page as the browser shows it. Never a picture of your screen, and never what is in a password or card box. All of it goes to your assistant's provider, as above. Your assistant decides what to do on your own subscription: iReliabee's AI and our service aren't involved, and no credits are spent. iReliabee never types a password, card or bank details: it stops at sign-in and payment pages and leaves those to you, and it stops at a CAPTCHA and never tries to get past one. It opens web pages only (http and https), not files on your computer. What a page says is passed on marked as the page's words, never as instructions, and each action is in the activity log. A website you use this way sees an ordinary browser visiting it, and its own terms and privacy policy apply to what you do there.

Paid tools: your content goes to iReliabee's AI. Two tools run one of iReliabee's own AI features for your assistant, as the button in the app does, and spend your credits:

• run_review: Write's coach reviews one section, or the whole draft, of a Write project. It sends that text, the task, focus and thesis you gave the project and the kind of writing it is. A project you edit with other people includes what they wrote.
• study_tool: one study tool on one section of a notebook: a mind map of the section, the questions to read it for, or one paragraph put another way. When the notebook was made from a document: for a mind map, it sends that section's notes with the text of up to 3 source pages they cite and, when the notes are 80 characters or fewer, up to 3 more pages of the source that mention them; for the questions, the section's notes with the page numbers they cite; for a paragraph, that paragraph with the text of up to 3 source pages it cites. Without a source document, only the notes or the paragraph.

Unlike the other tools, these send your content to iReliabee's service, which has it processed by a language model. You choose which, in Settings → Connected assistants → Which AI paid tools use, once for every assistant on this computer:

• Anthropic only, the default: your content goes only to Anthropic's Claude models, including when one is unavailable and another takes over. It is never sent to DeepSeek or to any other provider. It usually costs more. If no Anthropic model is available for that kind of job, the request is refused and nothing is charged.
• Standard (may use DeepSeek): it usually costs less, though the most a request can hold while it runs is the same or higher, because any of the models for that kind of job may answer, Anthropic's included. Your content goes to the language model we choose for that kind of job, as for the rest of the app (see Who processes it for us). That can be DeepSeek, as the main model or the backup, which is in China and may train on what it receives (see DeepSeek).

iReliabee's service enforces the choice itself: a request made under Anthropic only can't be passed to another provider, and its price is worked out from Anthropic's models alone. Each request's card says which option it uses, and if you change the option while a card is open, that request is stopped and nothing is charged. The AI's answer, which quotes your text, then goes to your assistant and from there to its own provider under its terms, like everything a tool returns. A review is also kept in Write, as when you press Review, and a chapter's questions are kept with the notebook.

A paid tool always asks, and says the price first. Its card shows the most the request can hold from your credits while it runs, and what it usually costs. It can never be always allowed or auto-accepted. A request never holds more than its card said: if the price has gone up since, nothing is charged and your assistant is told to ask again. Paid tools use your credits even if you chose to have your own assistant do iReliabee's AI work. In Settings → Connected assistants you can set a daily credit cap for paid tools, for all your assistants on this computer together; a request that would go past it still asks, and its card says by how much. What each paid request held and spent is kept on your computer for 90 days, with what it was about but never your content.

Never photos or recordings. No tool returns audio, recordings, screenshots, camera images or the photos in your notebooks: a photo appears only as its caption. No tool can share, send or delete anything; the only changes an assistant can make are the writes above, each asked first unless you set otherwise for that connection. A paid tool never sends photos or recordings to iReliabee's AI either.

Seeing it, and stopping it. Settings → Connected assistants lists each connection that has asked, with the name it gave, the permission you gave it for each tool, and an activity log of every request: which assistant, which tool, when, what it was about and what happened. The log keeps the last 500 requests, for up to 90 days, on your computer only, never with what a tool returned, and you can clear it. A connection is listed once you have answered one of its requests, and the list keeps the last 50, each for 30 days after it was last used. Disconnect removes every Always allow you gave that connection. Setting a tool to Never refuses it without asking for every assistant giving that name, and stays after it restarts or is disconnected, until you change it. To stop an assistant reaching iReliabee at all, remove iReliabee from that assistant's MCP settings (for Claude Code, claude mcp remove ireliabee --scope user).

Scene Lab in Speak

Scene Lab shows you an illustrated scene, such as a ward round or a stand-up, and you describe it in your own words. Looking at the scene, its word cards, your writing, your revisions and the comparison all stay on this computer (in the app's or browser's own storage) and send nothing. Only when you press Check my description, after the screen has shown you what it sends and what it costs, does one request go to an AI. It carries the description you typed (or the revision you are checking), which round you are on, and the scene's own text: its title, the facts it shows and its labelled words. Nothing else is added: no profile, CV, notes or other writing.

What comes back is feedback on that text: the words it would change and why, a few strengths, and scores for accuracy, precision, clarity and register. It is checked on this computer and shown only to you. It is used for nothing else: not to train any model of ours, not to build a profile, not shared.

You choose who does the work:

• iReliabee credits (the only way in the browser edition, and the default unless Settings → AI names your own assistant): the request goes through our service, which holds the most it can cost before it is sent and settles what it used after. It is processed by the provider of the tier that does the job, which can include DeepSeek (in China, and it may train on what it receives) as the main model or the backup, whatever an admin picks for that tier.
• Your own subscription (desktop only): the request goes over the same connection as Ask iReliabee with your own assistant to the assistant you chose in Settings → AI and listening on this computer (Claude Code, Codex or Gemini CLI, with the model you picked there), which sends it to Anthropic, OpenAI or Google under your own account and their terms. It uses no credits, and our service, DeepSeek and our other providers don't receive it. On Google's free tier, Google may use what Gemini receives to improve its products.

If a reply can't be read, the app asks once more with the same text; the price shown before you press the button already covers that second request. Spoken descriptions are not part of Scene Lab yet.

Saved Ask iReliabee conversations

The Ask iReliabee panel keeps your conversations so you can reopen them after closing the app or restarting your computer: each question, the answer, and when it was asked, with a title taken from your first question. In the desktop app they are saved in the app's own database on your computer. In the browser edition they are saved in your browser's own storage on that device. Saving them sends nothing to our service or anywhere else; they are not synced between devices, and they are not part of Download everything. You can rename or delete any chat in the panel's history, and Clear all chats in Settings deletes them all. Clearing your browser's site data also removes the browser edition's copy. What you send to be answered is described in the sections around this one.

What goes along with a question in Ask iReliabee

When you ask a question in a chat with My own assistant chosen, the recent messages of that chat (up to your last 8 exchanges, about 12,000 characters, the newest kept, long answers shortened in the middle) are sent along with your question to the same assistant you chose, such as your own Claude Code, so a follow-up like "put the above into a notebook" can be understood. They are sent as quoted data for context, not as instructions. A new chat sends none, and a past Claude Code conversation you continue already has its own history there, so it is not sent again. If you edit or delete a message, the history sent from then on reflects that, never the old text. When iReliabee is chosen, the answer comes from iReliabee's AI: the question you type is sent to our service, with the matching help text from the app and the name of the screen and item you have open (never its text), and on to one of the language-model providers named under Who processes it for us (DeepSeek among them, if we have chosen it for Ask; see DeepSeek). That costs credits, and the cost is shown before your first such answer and with each one; no earlier messages of the chat, files or images are sent. If you are signed out, offline or out of credits, Ask falls back to a search that runs on your computer, which sends nothing anywhere, costs nothing and says that is what answered. An administrator answering with their own key is not charged, and the answer says so.

You can also attach up to 3 text files (about 200 KB each) and up to 3 images (PNG, JPEG or WebP, resized on your computer to at most 1568 pixels) to a question. They go only to your own assistant, over the same connection, and from it to its company (for Claude, Anthropic) under their terms; the images are handed over in memory and are not written to disk by iReliabee. Files and images are never sent to iReliabee's AI, to DeepSeek or to our service, and attaching is switched off when iReliabee answers. A saved chat keeps a file's name and a short excerpt of it, and an image as a small thumbnail only, on your computer (or in your browser), never the full file or image.

Reopening past Claude Code conversations in Ask

If Use my own AI assistant is on in Settings and Claude Code is installed, the history in the Ask iReliabee panel can also list your past Claude Code conversations. When you open that list, iReliabee reads Claude Code's own conversation files on your computer (in your .claude folder) to show each one's first message, project folder, date and, for small files, its length, and reads one conversation's text when you open it. It keeps no copy beyond what is on screen, and sends nothing to iReliabee or any other service; tool calls are shown as one-line summaries and system notes are left out. iReliabee never changes or deletes those files. If you continue one, iReliabee starts Claude Code on your own plan to resume that conversation in its project folder, with the same limits as any Ask answer (iReliabee's tools only, each behind its consent card; no files, shell or other servers), and your new message goes to Claude Code and its company, for Claude that is Anthropic, under their terms. It uses no credits. This is off in the browser edition.

Answering Ask iReliabee with your own assistant

The Ask iReliabee panel answers questions about the app with iReliabee's own answers unless you choose My own assistant. Then your question, and a summary of iReliabee's features (what the app does and each screen and feature's name, purpose and place in the app, none of your data), go over the same connection to your own assistant on this computer, such as Claude Code, Codex, Gemini CLI or Claude Desktop: whichever assistant you connected to iReliabee over MCP and set listening. Your assistant sends them to its own company, for Claude that is Anthropic, for Codex OpenAI, for Gemini Google, to be processed under your account with them and their terms. On Google's free tier, Google may use what Gemini receives to improve its products. Its answer is shown in the panel. Our service doesn't see, relay or keep the question or the answer, and the question itself goes to neither iReliabee's AI nor DeepSeek. The Claude Code that iReliabee starts by itself for Use my Claude subscription never answers these questions.

Answering uses no credits: your assistant answers on your own plan with its provider. If it asks to use iReliabee's tools to answer, for example to read a project or open a screen, those requests follow your settings in Connected assistants as described above, including any auto-accept you set for that connection; a paid tool would use credits, and always asks first. If you ask it to look at or use a website, it uses its own browser tools if it has them, such as Claude in Chrome, in your everyday browser where you are signed in (those are your assistant's own tools, under its provider's terms and its own permission prompts, not iReliabee's), or otherwise iReliabee's browser window, where each action asks you in the app first. The question isn't sent while iReliabee is listening to a call or a voice practice, and one still waiting for your assistant when a call starts is never handed to it. ChatGPT can't answer here yet: it would need a hosted connection through ireliabee.co.uk, which isn't built.

Links and screenshots added as sources

When you add a public web page or post from its link, the app downloads it on your computer and extracts its readable text there. Public YouTube captions, X/Twitter's public embed data and oEmbed, TikTok oEmbed, Bluesky's and Mastodon's public post APIs, the US National Library of Medicine's PubMed and PubMed Central API (for those links), and a paper's PDF when its page links one are also fetched by your computer. These downloads do not use your social-site login.

For public Instagram and Facebook oEmbed, the app sends the post URL through iReliabee's service to Meta. The service's Meta credential stays on our server. If this is unavailable, you can open the link yourself or use a screenshot.

The separate in-app browser keeps your own social-site logins in its own browser storage on your computer. You sign in yourself. The app captures the text currently visible only when you click Save to notebook, then shows it for review before saving it. It does not automatically crawl, scroll or collect private posts.

Screenshots you paste, drop or choose stay local until you confirm the displayed credit cost. The confirmed image is sent through our billed vision service to Anthropic, OpenAI or Google, as selected for screenshots in the AI-provider section above. Images never go through your assistant relay. You review the transcribed text before adding it as a source.

Saved sources record their URL, platform, author when available, capture date and import method in your local Library. Existing text features process them under the same choices described above.

Finding papers and adding sources in Write

When you search for papers in Write's Sources panel, the app sends only the words you typed in the search box and the filters you chose (years, open access, minimum citations, preprints, field) to public scholarly indexes: OpenAlex, run by the non-profit OurResearch, and Semantic Scholar, run by the Allen Institute for AI, both in the United States, and the further sources named in the next paragraph. Your drafts, notes, task brief, project titles and sources are never sent, apart from the search words of a Find evidence check, described below. The request goes from your computer, not through iReliabee's service, without an account, like searching their websites; OpenAlex's request carries our support address so it is answered in its polite queue.

More paper sources. Find papers also searches CORE (the open research aggregator run by The Open University, in the United Kingdom, which needs a key that only our server holds, so that search is sent through our server), PubMed (the US National Library of Medicine's NCBI, in the United States; the request names the app and our contact address as NCBI asks), arXiv (run by Cornell University, in the United States) and DOAJ (the Directory of Open Access Journals, in the United Kingdom). They receive the same search words and filters and nothing else. In Filters you can turn any source off, and nothing is sent to a source that is off.

When you add a paper, or a source by its DOI, the app sends that DOI to doi.org, which answers with the publisher's citation record from Crossref (or DataCite or mEDRA, whichever registered it). Nothing else about you or your writing is sent.

To warn you about a source that has been retracted or corrected, or a preprint that has since been published, and to find a free copy of it, the app sends each source's DOI to Crossref (a non-profit registry of scholarly records, in the United States and the United Kingdom) and to Unpaywall (run by OurResearch, in the United States), with our support address. This happens when you open your sources or a citation card, at most once a week for each source. Only the DOI is sent: never your draft, the sentence you cite it in, or anything else.

These are search services, not AI providers: finding papers, adding sources and the source warnings use no AI and none of your credits. Search results are kept on your computer for up to seven days so the same search is not sent again. A paper's abstract, citation count and open-access link are kept with the source in your local Write project.

Find evidence and the claim check use the AI. Find evidence looks for papers that support a sentence you wrote. First it searches the paper sources above, with search words taken from your sentence on your computer (its main words, without citation markers). You see those words, and can change them, before anything is sent; they are the only words of your draft these indexes receive. Then the sentence and the papers found for it (title, authors, year, venue and abstract, up to 20) go to the AI, which says which of them support it and quotes the words of each abstract that do. A claim check sends a section you choose, with the title, authors, year and abstract of each source it cites, and the AI marks each claim as supported, partly supported or unsupported by those abstracts. Your notes on a source are never sent. Neither check writes or rewrites your text.

Both are charged in credits, and the price is shown before you run them. They go through ireliabee.co.uk to the language models named under Who processes it for us, kept for no longer than the request, exactly like a review; that can include DeepSeek, which is in China and may train on what it receives. If you use your own AI assistant, they go to it instead, as described under If you use your own AI assistant, and are not charged in credits. What a check found is kept in your local Write project.

The originality check uses no AI, and sends nothing unless you tick the box described in the next paragraph. It compares your draft with your sources' abstracts and Library files, the rest of your Library, your other Write projects and your notebooks (and, only if you tick it, projects shared with you), on your computer. In a browser it runs in the page, on the projects and notebooks you keep on the web, which the page already reads from our server; your draft isn't sent anywhere for it. Its report stays with you unless you download it.

Searching open published papers, only if you tick it. In the desktop app the originality check has a box, "Also search open published papers", which is unticked at the start of every check and applies to that check only. When you tick it, the app chooses short excerpts of your draft (8 to 14 words each, never from a quotation, a sentence that cites a source or your reference list): about one for every 60 words that can be searched, with 2 or 3 from every paragraph (its start, middle and end), at least 12 and at most 40, so a longer draft sends more of them, and the report says what share of your draft they cover. It sends each one as a search to OpenAlex, CORE (only through our server, which holds its key and keeps nothing; where that route isn't available CORE is left out, and the report says so), arXiv, PubMed and DOAJ, the same indexes and under the same terms as Find papers above. The report lists the exact excerpts sent. Your whole draft, its title, your notes and your sources are never sent. For papers the indexes say are open access, the app then downloads the paper from its publisher's or repository's public link, as your browser would, which tells that site your IP address; closed papers are never downloaded. The comparison itself happens on your computer. Searches and the papers read are kept in the app's local cache on your computer for up to 7 days so a second check doesn't ask again. No AI is used, and nothing is sent to iReliabee's AI providers.

Sharing a Write project

Write keeps your projects on your computer. Sharing is off for every project until you turn it on for that one, with Share in its toolbar. You choose each project you share; nothing else you have written leaves your computer because of it.

What is sent, and stored on our server. When you share a project, the app sends us a copy of it as it is at that moment: its title, the kind of writing, the citation style, the title and text of each section, with your citations formatted, and the reference list. That copy is stored on our server in France (see This website), so the people you share it with can read it while your computer is off. It never includes your notes on a section, your notes on a source, the abstracts of your sources, your stage checklists, or any review, evidence or claim check you have run. Nor does it include the task brief, focus or thesis you set, unless you turn on Edit together for the project (see Editing a project together).

It changes only when you share again. What you write after sharing stays on your computer. The shared copy is replaced only when you press Update shared copy, and the app shows you when the shared copy was made.

Who can see it.

• Anyone who has the link can read the shared copy, with no account and nothing to install. The link contains a long random code that cannot be guessed, and we keep only a one-way hash of that code. But anyone you, or the people you send it to, pass the link on to can open it, so share it as you would a link to any document. Shared pages tell search engines not to list them.
• People who can comment see the comments as well: the people you invite by email and, only if you allow it for that project, anyone with the link who signs in. Someone reading without signing in does not see the comments.
• You see the comments in the app, with the email address of each person who wrote one.
• iReliabee. We do not read shared projects or their comments. We look at one only when it is reported to us as abuse, or when the law requires it.

No AI. A shared copy and its comments are never sent to an AI provider, never used to train anything, and never sold or shared with anyone beyond emailing new comments to the people on the project (below). Nobody can run an AI check on the copy on our server.

Inviting people by email. When you invite someone, we send them one email from iReliabee with your email address, the project's title and the link, and keep their address with the share so they can comment once they sign in. We do not add them to any list or send them anything else.

If you comment on a project shared with you. To comment you sign in with your email address, which creates a free iReliabee account if you do not have one. We keep your comment, the words you selected for it, the section it is on, the name you give, and your account. The project's owner sees your email address with each comment; other people who can comment see the name you gave. You can delete your own comments, and the owner can delete any comment on their project. Signing in on a shared page sets one cookie that only keeps you signed in on ireliabee.co.uk, for 30 days. It is not used for anything else.

Emails about new comments. When someone comments on a shared Write project, we email the others on it: the owner, and the people the owner invited to edit or comment, never the person who wrote the comment, and never people invited only to read, people the owner has removed or suspended accounts. The email says who commented (the name they gave), the words they commented on, the comment itself (up to about 500 characters of it), the section it is on, the project's title and a link to open it. That means the comment and the words it quotes are sent to our email providers to deliver it: Resend, or, when Resend is unavailable, our own mail server (see the companies we use). They deliver it and do not use it for anything else, and no AI reads it. Several comments from one person within about two minutes come in one email, and we send each person no more than a few of these an hour for one project. The emails have no tracking pixels and nothing in them tells us whether you opened them. Every one has a link to stop emails about comments on this project, which works without signing in, and you can turn off all of them with Comment emails in your account (the account menu in the web app); they are on until you do. To remember either choice we keep your email address, and the project for the first.

Stopping sharing, and deleting it. Press Stop sharing in the app and we delete the shared copy, its comments and the addresses you invited from our server, and the link stops working. Deleting the project in the app does the same. If your computer is offline when you do either, the link keeps working until the app is back online and has deleted it; the app tells you so until then. New link makes the old link stop working and keeps everything else. Comments you have already seen in the app stay in the project on your computer, where you can delete them. Our database backups are replaced as they age, so a deleted shared copy is gone from them within 14 days. You can also ask us to delete a shared project, or your account with everything shared from it, at [email protected].

Editing a project together

You can also let people you invite edit a shared project with you, at the same time, with Edit together in the Share window. It is off for every project until you turn it on for that one.

What is stored, and for how long. With Edit together on, the shared copy is no longer a copy made at one moment: every change anyone makes goes through our server in France and is stored there as it is made, so that the others receive it, including while your computer is off. Besides what a shared copy holds (above), it holds the task brief, focus, thesis and key terms you set, because the people writing with you write to the same brief, and each section's word target. It still never includes your notes on a section or a source, the abstracts of your sources, your stage checklists, or any review, evidence or claim check anyone has run: those stay on the computer of whoever made them. We also keep one earlier version of the project a day, for the last 14 days, so that you can restore it if something is deleted by mistake. All of it is kept until you turn Edit together off, stop sharing, delete the project or delete your account, and then deleted from our server as described below.

What the people editing with you see. The people you invite to edit, comment or read see the project as it is now, the names of the others who have it open, and where each of them is in the text while they have it open. Where someone is in the text is passed on and never stored. Each person sees the name on the others' iReliabee accounts; you, as the owner, also see their email addresses, as you invited them by email. Someone you invite to edit can change any part of the project that is shared. When someone types with Suggest changes on, each change they suggest is kept in the text with the name on their account and the time they made it, so the others can see who suggested what and when; it is stored with the rest of the project, as above, until someone accepts or rejects that change.

A copy on each computer. So that everyone can keep writing offline, the app of each person you invite keeps a copy of the shared parts on their computer, as yours does. If you remove someone, or stop sharing, they can no longer see your changes or make any, but the copy already on their computer stays there, as an email attachment would. Invite people you trust with the text.

Editing in a browser. Someone you invite to edit can also edit from the link, in a web browser, without the app. They sign in on the shared page with the address you invited, as people who comment do, and the same cookie keeps them signed in (see above). Their changes go through our server and are stored there exactly as changes made in the app are, and the same people see where they are in the text while the page is open, which is never stored. Unlike the app, the browser keeps no copy: the project is held in the open page only, and nothing of it is saved in the browser's storage, so closing the tab leaves nothing behind on that computer but the sign-in cookie. People you invite to comment or read, and anyone who only has the link, read the shared page as before and cannot edit it. The same applies to a notebook edited together.

AI checks. Anyone who has the project in their app can run Write's AI checks (review, claim check, find evidence) on their copy, from their own computer, exactly as on their own writing. The same things are sent to the same AI providers (see What leaves your computer and Find evidence and the claim check), and they pay from their own credits, or use their own AI assistant. If you choose to cover your collaborators' checks on a project, up to a monthly limit you set, the credits come from your account instead, and your credit history shows which of them ran which check and what it cost. The people who can edit or comment then see, before they run a check, that you cover it and how many of this month's credits are left; nothing else about your account or balance is shown to them. Each check you cover is reserved from your balance before it runs, and never past the limit you set. Readers and people you have removed can't have a check covered, and the cover is only ever for those three checks (on a shared notebook, for its study tools: see Sharing a notebook). Nothing on our server runs an AI check on the project.

Sharing, and editing together, is free and uses no credits.

Sharing a notebook

A notebook is shared the same way as a Write project, with Share in the notebook's toolbar, and everything said under Sharing a Write project applies to it: off until you turn it on for that notebook, the link and who can read it, inviting people by email, comments, stopping sharing and deleting, and, if you turn it on, editing it together. What differs is what a notebook holds, so here is exactly what is sent.

What a shared copy holds. The notebook's title, who it is by, its summary and its Test yourself questions; each section's title and notes, with what kind of note each one is (a decision, a definition and its term, a quote and who said it, an action with its owner, due date and whether it is done, a table); a meeting's decisions, actions, questions, risks and numbers; and the terms found for it, with their meanings. It is stored on our server in France, as a shared Write project is.

What it never holds. The recording, the transcript, the PDF or any text read from it: the source a notebook was made from stays on your computer, and the people you share with cannot open it. Nor your photos and mind-map pictures (the others see that a picture is there, not the picture), the notebook's earlier versions, how it looks (paper, font, size), the name, class and year on an exercise book's cover, or anyone's study answers and progress: what you wrote to explain a chapter back, your answers to Check your understanding, your review cards, and explanations you did not add to the page. Those stay on the computer of whoever made them.

Editing a notebook together. With Edit together on, every change goes through our server and is stored there as it is made, as for a Write project, with one earlier version a day for 14 days. Besides what a shared copy holds, it then holds the notes' formatting (highlights, bold, colours and line styles), so everyone sees the same page, and the page or line numbers each note cites, so that your own copy keeps its links to the source. Those are numbers only: the source itself is never sent. The people editing with you see each other's names and where each of them is in the notebook while they have it open, which is never stored, and each of their computers keeps a copy of the shared notes, which stays there if you remove them or stop sharing.

A meeting's notebook holds other people's words. Its notes say what was decided and said in the meeting, and its actions name the people who agreed to them. Sharing it shares that with everyone you share it with, so share it as you would forward the meeting's notes (see also Other people in your meetings). The app reminds you before you first share one.

Study tools on a shared notebook. Anyone who has the notebook in their app can use its study tools on their copy (Explain, Simplify, a follow-up question, Mind map, Check your understanding, finding terms, Explain back, chapter questions and Explain twice), from their own computer, exactly as on their own notebooks: the same things are sent to the same AI providers (see What we handle), except the pages of the source, which are not on their computer, so only the notes' words go. They pay from their own credits, or use their own AI assistant. If you choose to cover the people you invited, as for a Write project, their study tools on that notebook are charged to your credits up to the monthly limit you set, and your credit history shows who used a study tool and what it cost. The cover on a notebook is only ever for its study tools. Building notes from a recording or a PDF needs the source, so only you can do it, on your computer, and not while the notebook is edited together.

Sharing a notebook, and editing one together, is free and uses no credits.

Sharing a topic pack

A topic pack from Speak's Topics is shared with Share on the pack, and everything said under Sharing a Write project applies to it: off until you turn it on for that pack, the link and who can read it, inviting people by email, comments, stopping sharing and deleting. A topic pack is read and commented on only; it is never edited together.

What a shared copy holds. The pack's title, its length and who the talk is for, its outline, and each term with its meaning, the three ways of saying it, the challenge it may meet and the answer, and the title of the Library file it came from, if any. It is stored on our server in France, as a shared Write project is.

What it never holds. What you said or typed when you rehearsed, and the text of your Library files: only their titles.

Keeping your devices in step (Sync)

Sync keeps the same account on several devices, and in the browser, in step. It does nothing until you are signed in, and each kind of thing has its own switch in Settings, under Sync. With a switch off, nothing of that kind is sent.

What is stored on our server when Sync is on, today:

• Speak progress — your level and points, your best combo, the days you practised and your streak, the rounds you have finished, what you have seen and when each phrase is due to come back, the fields you chose, your own field, which steps of Today's stack you ticked, My glossary (each word, the sentence you wrote with it, its field and when you saved it), and the minutes and words you logged for reading. It is the same progress the Speak game keeps on your computer, as one record.
• Preferences — your theme and look, whether you want motion reduced, and whether Speak plays sounds.

Each record carries a version number and the time it was last changed, so devices can merge their changes without losing any. The content is stored on our server in France (see This website), is used for nothing but giving it back to your devices, and is never sent to an AI provider. It is not end-to-end encrypted: it has the same protection as the rest of your account, and we can technically read it, and we do not.

What Sync does not send, in this version: your sessions, live call transcripts and recordings, the terminal log, your assistant and connector settings, Ask chats, your library, and your profile, CV, stories and people. Write projects and notebooks are on our server only if you use them in a browser or edit them together (see Using iReliabee in a browser). If we ever add anything to Sync we will change this page first, and anything that holds personal documents will be a separate switch that starts off.

Switching it off. In Settings, under Sync, switch off the kind of thing you do not want kept there. From then on nothing of that kind is sent from that device. Sync is also paused while a live call is running. Switching off does not delete what is already stored.

Deleting it, and taking it with you. Delete my synced data, in the same place, removes everything Sync has stored for your account from our server at once (the copies on your devices stay as they are); our database backups are replaced as they age, so it is gone from them within 14 days. Download my synced data gives you everything stored, as one file. Signing out does not delete it; deleting your account does (write to [email protected]).

How much, and how long. One account can sync up to 2 MB, or 20 MB once you have bought credits. It is kept until you delete it or your account is deleted.

Using iReliabee in a browser

You can also use Write and Notebook in a web browser, at ireliabee.co.uk, without installing the app. You sign in with your email address, by a link we email you, with the same account the app uses. This part says what is different in a browser; the rest of this policy applies as it does in the app.

Your projects and notebooks are stored on our server. In the app they are kept on your computer. A browser has nowhere safe to keep them, so a Write project or a notebook you make in a browser is stored on our server in France (see This website) as you type: its title, its sections or pages and their text, its notes and what kind each one is, its summary, the task brief, focus, thesis and key terms you set, word targets, and its sources with the details needed to cite them. Your own notes on sections and sources, the stage you have open and your checklist ticks are kept too, with your account, for you alone: on a project shared with you, the others never see them, and they are deleted with the project, or when you leave it or are removed from it. We also keep one earlier version of each a day, for the last 14 days, so a mistake can be undone. The browser itself keeps no copy: nothing of your projects is saved in its storage, so a shared or library computer keeps nothing but the cookie that keeps you signed in (see This website). With your account we also keep one choice you make there, that you've closed the note about the desktop app, so it stays closed in every browser you sign in to.

Who can see them. Only you, until you share one; sharing it works as described under Sharing a Write project and Sharing a notebook. A project you keep in a browser is not shared and does not count as one of your shared projects. We do not read your projects. We look at one only when it is reported to us as abuse, or when the law requires it.

Between the app and a browser. In the app, Put on the web sends a Write project or a notebook to our server, to keep in a browser as described here. It sends the same parts that Edit together sends. It also sends what the app keeps for you alone about the project or notebook, which is then kept with your account, for you alone, as described above:

• your notes on sections and sources, the stage you have open and your checklist ticks;
• the abstracts of the sources you found;
• the results of reviews and checks;
• for a notebook, its look and its label, your score for each chapter you explain back, the questions made for a chapter you study, and the questions you have answered, each with the paragraph it is about, your last mark and when it comes back for review.

It never sends a notebook's photos, the files in your Library or the history of your answers shown on the Progress screen.

After that, the project and what is kept for you alone about it stay in step between your computer and our server, both ways, while the app is signed in to your account. A project or notebook you keep in a browser can also be opened in the app, which then keeps a copy of both on your computer. Deleting it in the app deletes only the copy on your computer. To delete it from our server, delete it in the browser. None of this applies to a project you share from the app with Edit together: your own notes on it stay on your computer.

Adding a source by its DOI. When you add a source by its DOI in a browser, our server asks Crossref for the source's details, sending only the DOI, as the app does from your computer. Nothing else about you or your project is sent.

Finding papers in a browser. Finding papers, and the search a Find evidence check makes, send the same search words and filters to the same paper sources (OpenAlex, Semantic Scholar, CORE, PubMed, arXiv and DOAJ) as the app does (see Finding papers), but from our server rather than your computer, so those services see our server's address, not yours. Our server keeps no copy of the search or its results. When you add a paper you found, its DOI goes to doi.org as described there, and its abstract is kept with the project, for you alone, like your own notes in a browser: it is what a claim check reads. Find evidence and the claim check then work as described under Find evidence and the claim check, through our server as for a review. What a check found is kept with the project, for you alone, and deleted with it.

AI checks and study tools in a browser. Nothing is sent to an AI provider until you press a check's or a tool's button, and for a priced check only once you have seen the price. Then the same content as from the app goes to the same AI providers, described under What we handle and Processors: for a review, the section or draft with the task, focus and thesis; for a study tool, the words, paragraph or notes it works on; for Plain words, the text you chose, then that text with its plain version. A plain version is not kept: it changes your project or notebook only if you choose to. The difference is where the request is put together. The app does that on your computer; in a browser, your browser sends that content to our server in France, and a part of our server that keeps nothing builds the request and passes it on, as the app would. Never your own notes or a notebook's photos, and nothing for training. Kept with the project or notebook, for you alone, like your own notes in a browser, and deleted with them: the result of a review; your score for each chapter you explain back; the questions made for a chapter you study; and the questions you have answered, each with the paragraph it is about, your last mark and when it comes back for review. Answers you speak are not possible in a browser: you type them.

Nothing else uses AI. Keeping, editing and sharing a project in a browser never sends it to an AI provider.

Limits. You can keep up to 20 projects and notebooks in a browser, taking up to 50 MB in all, until you have bought credits once, and up to 500, taking up to 1 GB, after that; and make up to 20 new ones a day. These stop the service being used to store anything but writing; they are not a charge. Keeping projects in a browser uses no credits.

Taking them with you, and deleting them. Download everything gives you one file with every project and notebook you keep in a browser, at any time. Deleting a project or notebook in the browser deletes it, its earlier versions and anything shared from it from our server at once; our database backups are replaced as they age, so it is gone from them within 14 days. To delete your account, with everything you keep in a browser, write to [email protected].

Other people in your meetings

When you use the live companion, the audio of your meeting is transcribed — and that audio contains other people. They have not agreed to this policy, and they may not know it is happening.

Whether you may do that is your responsibility, not ours. In some countries and some workplaces, transcribing a conversation requires telling the other people or getting their agreement. We cannot know which rules apply to your call. The Terms of Service say the same thing in the language of an obligation.

What we can tell you is what happens to it: the audio is transcribed and discarded, the transcript is stored on your computer and not ours, and nothing about the other participants is kept by us. The one thing that can change that is you sharing the meeting's notebook: its notes, which say what others said and name them on actions, then go to the people you share it with, and are kept on our server while you share it (see Sharing a notebook). The transcript never goes.

Screen recordings

The live companion can record your screen, the call's audio and your microphone into one video. It does this only when you start a recording, and only after you tick that you will make sure everyone on the call agrees to being recorded. Nothing is recorded by default, and the question is asked again before every recording.

The video stays on your computer. It is never sent to us, to any AI provider, or anywhere else: the app plays it back from your own disk and nothing uploads it. While it records, a red “Recording” mark with the time is always showing, and one click or the V key stops it. You can delete any recording in the app, or ask it to delete recordings after a number of days you choose.

Whether you may record a call, and what you must tell the people on it, is your responsibility (see Other people in your meetings). The words in a recording are not transcribed by it: the transcript of a session is made by the live companion as described above, whether or not you record.

This website

ireliabee.co.uk runs on our server in France, behind Cloudflare. It has no analytics, no tracking pixels and no advertising cookies. We do not know who visits it. The only cookies it sets keep you signed in, if you sign in to comment on or edit something shared with you, to use iReliabee in a browser, or to the backoffice that runs the service.

The country you connect from. Cloudflare works out which country each request comes from, from your connection, and tells our server. The pricing page and the checkout use it for one thing: to choose the regional price (prices are lower in Africa) and the currency an estimate is shown in. It is not stored when you only look at the page. If you buy, it is kept with that purchase — see When you buy credits.

The estimate in your own currency uses exchange rates our server fetches about twice a day from a public rate service (ExchangeRate-API, at open.er-api.com). That is one request for the whole table of rates, the same for everyone: nothing about you or your visit is sent to it.

Cloudflare processes request logs, including IP addresses, to serve the site and protect it from attack. That is a normal part of hosting, and is covered by Cloudflare's privacy policy.

Fonts are loaded from Google Fonts, which means your browser makes a request to Google when you open a page.

When you buy credits

Payments are processed by Paystack. They collect your name, email address and payment details — card, Apple Pay or mobile money — and handle the transaction on our behalf. Apple Pay pays with a card in your Apple Wallet, so it counts as a card payment below.

We never see or store your card, Apple Pay or mobile money details. What reaches us is your email address, your name, what you bought and when, so that we can add the credits to your account and support you afterwards.

With each purchase we also keep the country you were connecting from when you opened the checkout (as Cloudflare saw it), the regional price that gave you, and — when you pay by card or Apple Pay — the country your card was issued in, which Paystack tells us. Not the card itself: only its country. We keep these to price fairly and to prevent misuse, such as a connection routed through another country to get a price meant for somewhere else. A purchase at the price for Africa paid with a card from outside Africa is still credited; it is marked for the people who run our backoffice to see. Mobile money and bank payments have no card country, so none is kept.

Their handling of your payment data is covered by Paystack's privacy policy.

Outside Africa, credit packs may instead be sold to you by Lemon Squeezy or Dodo Payments (whichever we use at the time; the checkout names it) as merchant of record: they are the seller of that purchase, charge you in US dollars by card, PayPal, Apple Pay or Google Pay (your card converts it), and work out and pay the sales tax or VAT where you are. To do that they collect your name, email address, billing country (and postcode where tax needs it), any tax number you give, and your payment details, and handle them under their own privacy policies: Lemon Squeezy, Dodo Payments. What reaches us is the same as with Paystack — your email address, name, what you bought, when, and what was paid before tax — plus the country you connected from. We never see your card or PayPal details.

How long we keep things

Five different answers, because there are five different kinds of thing.

• The content of your sessions — audio, transcripts, questions and answers: not kept at all. It lives in our service only for the length of the request that carries it. There is no database table for it and no log that contains it.
• Records of use — the time, the kind of session, how long it ran, which model answered, how many tokens it took and what it cost. This is what your credit balance is calculated from, so it has to exist, and it contains no part of what was said. Kept for 24 months, so that a billing question raised a year later can still be answered.
• Your account — email address, name, credit balance, the history of credits bought and spent (including any we add or take away by hand; a purchase includes the country you bought from and, for a card, the card's country), and its status: whether it is suspended, since when and why. Whenever we suspend an account, lift a suspension, add or take away credits by hand, or hold back a payment to check it, we also write down when, what and why, and who did it. Kept while your account exists. If you ask us to delete it, the purchase records are kept for seven years afterwards because tax rules require records of sales; everything else goes.
• Reminders you ask for by email or text message — the reminder's text is kept on our server only until it is sent, then deleted; sooner if you move or delete the meeting or turn the reminder off. We keep a record that a reminder was sent — when, by which channel, and what a text message cost in credits — as part of your records of use, and that record contains none of the reminder's text. Your phone number is kept with your account for as long as it exists, as your email address is, and is deleted with your account.
• Write projects you share — the shared copy, its comments and the addresses you invited are kept while you share it, and deleted when you stop sharing it, delete the project in the app, or delete your account (see Sharing a Write project). A comment you write on someone else's project is kept until you or they delete it, or they stop sharing. With Edit together on, the project and its daily versions are kept on our server while you share it, and deleted with it.
• Projects and notebooks you keep in a browser — kept on our server, with one earlier version a day for 14 days, until you delete them or your account (see Using iReliabee in a browser).
• Notebooks you share — exactly as Write projects you share: kept while you share the notebook, and deleted when you stop sharing it, turn Edit together off (for the live copy and its daily versions), delete the notebook in the app, or delete your account (see Sharing a notebook).

Inside iReliabee, your account and its records of use are seen only by the people who run our backoffice, to support you and to run the service. Where your credit history is shown to you, credits we add or take away by hand appear as added or removed by iReliabee, and a suspended account is told that it is suspended. The reasons we write down, and which of us acted, are notes for the people who run iReliabee and are not shown to you in the app or on this website, though they are part of what you can ask us for (see Your rights).

Sign-in links, one-time codes (including the one that confirms your phone number) and device tokens are stored only as a SHA-256 hash, never in a form that could be used to sign in as you, and expire on their own.

Everything on your computer lasts as long as you keep it. Deleting it in the app deletes it.

Your rights

Depending on where you live, you may have the right to ask for a copy of the personal data we hold, to have it corrected, to have it deleted, or to object to how we use it. In Ghana these rights come from the Data Protection Act, 2012 (Act 843); in the UK and EU from the UK GDPR and GDPR.

What we hold is your email address, your name if you gave one, your phone number if you added one, any meeting reminders waiting to be sent, any Write project you share with its comments and the addresses you invited, comments you have written on projects shared with you, your credit balance, the record of credits bought, spent, added and taken away, the devices you have signed in on, the records of use described above, your account's status, and the notes we keep on any suspension, any credits we moved by hand and any payment we held back to check. You can ask for any of it, or ask us to delete your account, by writing to [email protected]. We will reply within 30 days.

We cannot give you a copy of your sessions or transcripts, because we do not keep them. Export them yourself from Settings → Your data.

If you are unhappy with how we have handled your data, please tell us first, at the address above. You can also complain to Ghana's Data Protection Commission (dpc.gov.gh, formerly dataprotection.org.gh).

Children

iReliabee is not intended for children under 16, and we do not knowingly collect their data.

Changes to this policy

If we change this policy we will update the date at the top of the page. If a change materially affects you — for example if the app started sending somewhere it previously did not — we will say so in the app's release notes rather than hoping you notice here.

This version is one of those changes. Until this date, iReliabee ran on API keys you supplied, and your content went straight to the provider you chose without passing through us. That is no longer true, and the section on what we handle is where the difference is written down.

Contact

Privacy questions: [email protected]
Help with the app: [email protected]