Privacy policy.
What personal information RoundReply handles, why, who processes it for us, where, for how long, and how to use your rights.
Who is responsible
RoundReply (“we”, “us”) is responsible for the personal information described here. Write to hello@roundreply.com about anything in this policy.
What we handle, and why
- Your account: your email address and name, and an identifier for you. You sign in with Google, which tells us your email address and name and keeps your Google password, or with a code we send to your email address. There is no RoundReply password. We use them to give you your account.
- Usage: when each call started and ended, the minutes it counted, what paid for it (a free session, hours or a plan), and what your account allows. We use them to count your free sessions, your hours and your plan’s minutes, to apply the service’s limits and to prevent abuse.
- Problems and first use: when a call in the Windows app fails or cannot start, the app tells our service that it failed and one of a fixed list of causes, with the time. It also tells us the first time an answer was shown in a call. These reports hold no words of the call, no transcript, no question, no answer and nothing from your documents. We use them to find and fix what stops calls from working, and to help you when one failed.
- A call’s audio, from the moment you press Start until you press Stop: what your computer plays and, if you added it, your microphone; in a call in your browser, your microphone and the sound of the tab you share. From the Windows app it goes from your computer straight to Speechmatics to be turned into text as it arrives, and does not pass through our servers; from your browser it goes through our relay, our server in Microsoft Azure in the United States, to Speechmatics. We do not store it: the relay holds it in memory only while it passes it on.
- What a suggestion needs: the question, recent lines of the conversation and the parts of your context the suggestion uses. They go to our account service, which has Azure OpenAI write the suggestion and sends it back. Our service keeps none of these words: not in its database, its files or its logs. To write the next suggestion faster, our account service holds the text of your résumé and documents that came with a question, and your confirmed facts, in its memory only, linked to your account. It removes them within about 30 minutes after they were last used, and never writes them to a disk, a database or its logs. A call you share with Share live view is the one exception while you share it: Live share, below, says what is kept and for how long.
- Sessions you synchronize: one saved session at a time, when you choose Sync this session… and confirm. A copy holds the transcript, the questions and the suggestions; never audio, screenshots, your notes, your documents or your facts.
- Purchases: a record of each purchase (the pack or the plan, its dates, what it gave and its state) and the identifier Dodo Payments gave you as its customer. What you paid, your card and your receipts are held by Dodo Payments; card details are entered on its page and never reach us.
- Logs: technical records of the requests to our service, which name your account by its identifier and not by your email address, used to keep the service running and secure. The lines of one call also carry a code made from that call’s identifier, so that the records of one call can be read together.
- What you tell us when you start, if you choose to: the role you are interviewing for and your years of experience, the kinds of interview ahead, the companies you are applying to, the date of your next interview, the language of your interviews, the programming language you use, and where you heard of RoundReply. We use them to set up your account for you (your new sessions start in that language, with the résumé you add, and we point you to your role’s questions in the Question Bank) and to understand who uses RoundReply. Every answer is optional, and you can change or clear it on your Profile.
- Your phone number, if you give it: we use it only to help you on WhatsApp when the setup of a call goes wrong, and we message you there about your account only if you tick that choice, which you can untick on your Profile at any time. We keep when you ticked it. We never sell or share your phone number, and never use it for advertising.
- Your account’s other signed-in devices: the kind of app, the name an app gave its computer, and when each signed in and was last used, which your Profile lists so that you can sign them out. Your invoices are fetched from Dodo Payments when you open them; we do not store them.
- Sessions you set up in your account: the company, the role and the job description (or a call’s title and description), a job post address you paste, your language, model and answer style, your AI instructions, and which of your résumés and documents you chose for the session.
- Transcripts and answers of those sessions: if Save transcript is on for a session (it is on for a new session of your account, and always on for a mock interview), the transcript of the call, by speaker and with times, and the AI answers shown to you during it. You can turn Save transcript off for any session. Recording or transcribing a conversation may need the consent of everyone in it where you are, and asking for it is yours to do.
- Practice sessions: if you use Practice, we keep the questions you were asked, your typed or spoken-and-transcribed answers, and the AI drafts written from your resume, in your account, so you can read them again.
- We do not send Practice answers to the Question Bank. You can delete a practice session at any time, and deleting it removes its answers and drafts.
- Spoken answers go through the same transcription service as a call in the browser, and are charged by the minute like one.
- AI notes, a summary and Ask AI: after a call we can write AI notes (a summary, the questions you were asked with what you said, and next steps), a short title and a one-line summary, and answers to the questions you ask about the call. To do it we send the session’s transcript and details to Azure OpenAI. AI-written content can be wrong.
- A job post link you paste: our server fetches that one public page and reads the company, the role and the description from it, and sends the page’s text to Azure OpenAI when the page does not describe the job in a structured form. Nothing is saved unless you create the session with it.
- Documents you add to your account: the file as you uploaded it and the text read from it; for a web page you ask us to read, the document Azure OpenAI writes from that one page’s text and your instructions, with the page’s address and your instructions, and no copy of the page; for a document you write, what you write. They are kept with your account and are not shared with other users. A call in the browser reads the documents you chose for its session, to write its answers.
- A review you write of a company’s interview process, kept with the session; how helpful you rated a call’s answers (1 to 5) and any comment; and whether you dismissed or followed our request to review us on Google.
- Company logos in your dashboard are loaded by your browser from Google’s public favicon service, which receives the company’s web address and your internet address.
- Question Bank contributions: when you end an interview session of your account that was paid for with hours or a plan, held in English, with Save transcript on, or with Save this session on in the Windows app (it is off for a new session) while you are signed in, the questions your interviewer asked, as detected in your transcript, are sent to Azure OpenAI to be rewritten in general words, with names, employers, projects, contact details and other personal details removed. We keep the rewritten questions with the company, the day the interview ended and the country it was held from, and count them in the Question Bank. A question is shown to other users only after at least two different accounts have reported it, and never with your name or your session. Contributing is on by default; you can turn it off in Profile, under Privacy, and what your past interviews gave is then removed the next time the Question Bank is counted, about once an hour. Deleting a session or your account removes its contribution the same way. Mock interviews, regular calls and free sessions never contribute.
- Questions you report: when you use I was just asked, we keep the question you type, the company, the role, the round if you give it and the day you were asked, with your account. Before we keep it, we remove email addresses, phone numbers and links. If it may name a person, an employer or a project, our team reads it before it is published. An accepted question is shown to other users and visitors of our website straight away, with its company, role and day, never with your name or account. We keep a record with your account of each question you reported, whether it was accepted and why, and the free minutes it earned, to apply the limits and the reward. A question that was not accepted is kept without its words.
- Résumés: a résumé you add (the PDF of up to 5 MB, or the text you paste), a picture of its first page made on your device, and the parts read from it; the profile address you give when you bring in a LinkedIn profile (we do not visit LinkedIn: only the file or the text you give is read). A résumé you make in the Resume Maker is kept with its saved versions (the newest 100), its design, a photo if you add one, the facts you confirm and a job post if you paste one, which is never printed and is used only to score and tailor that résumé.
- Improve with AI: the parts of your résumé a request is about, and the rest as background, without your name, contact details, location or links; the job post, your instruction and the figures you give, if you choose to. They go to Azure OpenAI, which may keep text its safety checks flag for its own abuse review. We keep each conversation (what you asked and which changes came back) and each suggestion until you use it or set it aside, and the time and size of each request, to apply the fair-use limit. When you download a résumé, we record which version, when and how it was paid for, so that a version you paid for downloads again for free.
- Transcribe sessions: the title and keywords you give a session, when it ran, where it listened and how many words it had. While Save the transcript and audio is on for a session (it is on for a new session), its transcript, by speaker and with times, is saved to your account as it is written, and its audio is recorded in your browser and saved privately for your account on Microsoft Azure in the United States. Both are kept until you delete the session or your account. While it listens, the audio goes through our relay to Speechmatics to be turned into text; Speechmatics does not keep it. After you stop a session whose transcript was saved, we send that transcript to Azure OpenAI to write its summary (the questions the call’s side asked, with a short note of each answer), and keep the summary with the session until you delete it or your account. AI-written content can be wrong.
- Answers from a shared transcript: if you read a shared transcript and press Draft my answers, we send the questions picked from the call’s lines you were shown and, if you choose one, your résumé to Azure OpenAI to write an answer to each. We keep the questions and answers with your account until you delete them or your account. They are yours to keep: ending the share or deleting the host’s session does not remove them. We do not keep which link they came from. While the share’s record exists (at most 7 hours after it ends), it counts how many answer sets were asked for, not who asked. AI-written answers can be wrong.
- Support chat in your dashboard: the messages you write there and the assistant’s answers, the screenshots you paste (PNG or JPEG), and the requests you send to our team (the form you filled in or the conversation you sent, what you add to it, our replies and whether you have read them). To answer, the assistant sends your message, the conversation so far, a screenshot you pasted, our help pages and a short summary of your account (your plan or hours and your recent calls, never their words) to Azure OpenAI. We count how many answers the assistant gives your account each day, to apply its daily limit. The dashboard keeps, in the storage of the browser that shows it, which version of its tutorials you have seen. Answers are written by AI and can be wrong.
- The Feedback Hub: a problem or an idea you report (your words, the part of RoundReply it is about and a screenshot if you add one), and the items you vote for. Your report and your screenshot are seen only by you and our team. To find where a report belongs on the board, we send its words and the board’s items to Azure OpenAI. The board itself, which every signed-in user can read and vote on, shows only words our team has written or approved, and never names who reported or voted. We count how many reports your account sends each day.
- Requests for a call’s hours back: the call, the words you give, the facts our rules read when you asked (the length of the call and whether the app reported it as failed), and our decision with its note.
- A friend’s invite: if you join through a friend’s referral link or code, we record that you did and which code, and whether your first purchase earned referral hours. To stop abuse, when your first purchase is completed we compare, inside our systems, the sign-in email addresses of the two accounts and the network address and browser of their signed-in sessions, and keep only the result: hours given, or held back and why. The account that shared the code sees how many people joined and bought with it, never who.
- Emails about your account: to your sign-in address we send a welcome when you join, receipts and payment problems, and, unless you turn them off on Email in your dashboard, setup and usage tips. We send product news only if you turn it on there. They go through Azure Communication Services, which receives your address and the message.
- Messages you send us by email, used to answer you.
The Windows app keeps every call on this computer, with what was said and the answers it wrote, until you delete it. Delete a call from its page. A call goes to your account only when you copy it there. A report is written only when you press Write the report.
Your profiles, confirmed facts, documents, prepared sessions, saved sessions and settings stay in the app’s data folder on your computer. We receive only the parts described above.
The dashboard keeps three display choices in the storage of the browser that shows it (its theme, a folded sidebar and folded menu groups). The only thing about you it keeps there is a call’s setup on the Live page, and only if you choose to keep it, as How long it is kept says.
The grounds we rely on
Where the law asks for a legal ground (for example the GDPR in the European Union and the United Kingdom), we rely on these:
- to perform our agreement with you: your account, your calls, your suggestions, answers drafted from a shared transcript, your purchases and the sessions you synchronize;
- our legitimate interests: keeping the service secure, preventing abuse of the free sessions and of the limits, and fixing faults from the logs;
- your consent: WhatsApp messages about your account, which you can withdraw on your Profile at any time;
- a legal obligation: keeping records of purchases.
Who processes it for us
- Microsoft: Azure hosts our account service and its database in the United States, which also sign you in; Azure’s email service sends the sign-in codes; Azure OpenAI writes the suggestions. Microsoft’s documentation says prompts and responses are not used to train models and are not available to OpenAI, and that a sample may be stored and reviewed by its staff when its abuse monitoring flags a pattern.
- Google: if you choose to sign in with Google, Google signs you in and tells us your email address and name, under its own privacy policy.
- Speechmatics: turns a call’s audio into text, in its service in the United States. Its documentation for this service says it does not store audio, transcripts or settings.
- Hostinger: holds the mailbox of our contact address, so it holds the email you send us.
- WhatsApp (Meta): if you agree to WhatsApp messages, the messages we exchange with you there pass through WhatsApp, under its own privacy policy.
- Dodo Payments, a payment company that acts as the merchant of record: when you first buy, we give it your email address, your name and an identifier for your account, so that it can make you its customer. It takes the payment and handles tax and receipts, under its own privacy policy.
We do not sell your personal information, show advertising, or use your content to train AI models. This website counts visits and uses cookies only as Cookies and visit counts below says.
Cookies and visit counts
We count visits to this website ourselves. Without any cookie, we count each page you open, a click on Download and a click on a link to the sign-in page, with the page’s path and, when your browser gives them, the name of the website you came from and the campaign labels (utm_source, utm_medium, utm_campaign) in the link you followed. Your IP address and what your browser says about itself are not stored with these counts; our service holds the IP address only in its memory, for up to two minutes, to limit how many counts one address can send.
Apart from the Necessary cookies below, we set cookies only if you agree in the cookie banner. You can change your choice at any time with Cookie settings at the foot of every page, and switching a category off deletes its cookies from your browser. If your browser sends Do Not Track or Global Privacy Control, we treat that as declining Analytics and Marketing, show no banner and store nothing.
- rr_consent (Necessary, 1 year): remembers the choice you made in the cookie banner, including a refusal. The same choice is kept in this browser’s storage.
- rr_signed_in (Necessary, 30 days): set when you sign in to your account and removed when you sign out. It holds only the value 1, no id and nothing about you. This website reads it to show Dashboard in place of Sign in.
- rr_vid (Analytics, 1 year, only after you accept Analytics): a random id that tells one visitor from another. While it is set, it is sent with the counts above, and once when you accept.
- rr_src (Analytics, 90 days, only after you accept Analytics): where your first visit came from, which is the website you came from, the campaign labels and a ref code in the link you followed. Only if you also accept Marketing, it holds the click id an advertisement added to that link (gclid, fbclid, ttclid or li_fat_id).
If you sign in or create an account from a browser that holds these cookies, the dashboard reads them once after you sign in, and we keep the visitor id and that first visit’s source with your account, so that we can see which sources lead to accounts. It is in your data export and is deleted with your account.
When you accept Marketing cookies, these advertising services may load on this website: Google (Google Analytics and Google Ads), Meta (the Meta Pixel), TikTok (the TikTok Pixel) and LinkedIn (the Insight Tag). Each loads only after you accept, may set its own cookies, and receives from your browser the address of the page you are on and your IP address; we tell it when a page is opened and when Download is clicked. Each uses what it receives under its own privacy policy. They do not load on the sign-in page or in the dashboard. When you switch Marketing off, we tell them you withdrew, delete the cookies they set for this website and load the page again without them.
A count is deleted after 400 days; counts already sent with your random id stay until then. We do not sell these counts or the visitor id.
Where it is processed
Our account service, its database and transcription are in the United States. If you live elsewhere, your information is transferred there; we rely on the data processing terms of the providers above for those transfers.
How long it is kept
- A saved session on your computer: until you delete it. A synchronized copy in your account: until you remove it.
- Your account: until you delete it, or ask us to.
- Usage and billing records: 24 months.
- Logs: 30 days.
- Backups of the database: 7 days, so something deleted can stay in a backup for up to 7 days.
- A call in your browser: its transcript and suggestions only in the tab’s memory, gone when you close it. Its setup (the company, the job description, your notes, your confirmed facts and your answer style) only if you tick “Keep this setup in this browser”, not encrypted, in that browser’s storage on your computer, for the account signed in, until you press “Forget it” or log out, or another account signs in there. While you share it with Share live view, our service also keeps its transcript, line by line, until the share ends, and 7 hours at most.
- The lines of a call you share with Share live view, and the share’s title: until the share ends, and 7 hours at most (Live share, below).
- What you told us when you started, including your phone number and your WhatsApp choice: until you change or clear it on your Profile, or delete your account.
- Sessions of your account, their transcripts, answers, AI notes and chats: until you clear them, delete the session or delete your account.
- Documents in your account: until you delete them or your account.
- The wording detected in a contributing interview: until it is rewritten, and 14 days at most. The rewritten questions: until your contribution is removed by the Profile switch, by deleting the session or by deleting your account.
- Questions you reported, and the record of each and its reward: until you delete your account. An accepted question then leaves the Question Bank with it.
- Résumés, with their versions, suggestions and conversations: until you delete them or your account.
- Questions and answers from a shared transcript: until you delete them or your account.
- Your referral record: with your account.
- The website’s visit counts: 400 days. The visitor id and first visit’s source kept with your account: until you delete your account.
- Support chat: a conversation until you clear it or delete your account; your requests to our team, with their messages and pictures, and the daily count of answers: until you delete your account.
- Your Feedback Hub reports, their pictures and your votes: until you delete your account. The items on the board name nobody and stay after that.
- Requests for a call’s hours back, with the facts they were decided by and our decision: until you delete your account.
- After an account is deleted: that it used its free sessions, kept as the account’s identifier and a one-way code made from its sign-in email address that cannot be turned back into the address, so that the free sessions are not given again; and a line saying that the account was deleted, and when. Dodo Payments keeps its own records of your payments and receipts.
Your rights
You can ask for a copy of your personal information, ask us to correct it or delete it, ask for it in a form you can take elsewhere, and object to or ask us to restrict how we use it. Write to us from the email address of your account; we answer within one month.
In the app you can delete a saved session and remove a synchronized copy yourself, and remove your profiles, facts and documents. On the Account page of the dashboard you can export everything your account holds as one file (Export your data) and delete your account (Delete your account). If either does not work for you, write to hello@roundreply.com.
You can also complain to the data protection authority of the country where you live.
Security
Information travels to our service and to our providers over encrypted connections. Our service answers only a signed-in request, and only with that account’s own information. On your computer, the app’s files are plain files, not encrypted; your sign-in is kept protected by Windows for your user account.
The one exception is the Live view of a call you share: while the share is live it answers any signed-in account that has its link, and only with that call’s transcript.
Children
RoundReply is not for anyone under 18, and we do not knowingly hold information about them. If you think a child has an account, write to us and we will delete it.
Changes to this policy
A new version of this policy is published on this page with the date it was written.