Legal
Privacy Policy
1. Who we are
Reco is made and run by OSSA FRAME INC, a company in the United States (“we”, “us”), 237 58th Street, Brooklyn, NY 11220, USA. Privacy contact: privacy@recobot.app.
2. What this policy covers
The Reco Chrome extension, Reco’s service at api.recobot.app, the meeting page at app.recobot.app, the recobot.app website, and messages you send to our addresses.
3. What we process
- Account data: your name, email address and Google account ID from Sign in with Google, and Reco’s sign-in session token, which is kept in your browser and stored on our side only as a hash. We ask Google only for these (scopes
openid,email,profile). - Meeting audio: the audio of the Google Meet call in your browser, what the other participants say and what you say, recorded only during a call and only on meet.google.com. Audio is temporary (see section 8).
- Speaker activity: which participant the Meet page shows as speaking, and when, so that the transcript can name speakers. This includes participants’ display names as Meet shows them.
- Meeting details: the meeting title and Meet code shown on the page, the participants’ names as Meet shows them, and start and end times.
- Results: the transcript, the summary with decisions, action items, open questions and suggestions, and the Word, Excel and text files made from them.
- Sharing settings: whether you shared a meeting with your company’s domain.
- Questions to Ask Reco: sent with the meeting’s transcript to the AI provider to produce an answer. We do not store or log the questions or the answers.
- Data kept in your browser: Reco’s settings, your sign-in session and audio pieces waiting to be sent.
- Security records: which account did what and when (for example sign-in, sharing or deletion), with the IP address.
- Messages you send to hello@recobot.app or privacy@recobot.app.
Reco does not intentionally collect video, browsing history, clicks or keystrokes, location, payment information, or the content of your email, calendar or Drive. Meeting audio and transcripts may contain sensitive information spoken by participants.
4. Why we process it
To provide Reco: sign you in, record the call you chose to record, transcribe it, name speakers, write the summary, make the files, answer your questions about the meeting, show the meeting to you and to the colleagues you share it with. To keep the service secure and working. To answer your messages.
5. Roles
You decide which calls Reco records, and you (or your organisation, if you record for work) are responsible for informing the other participants and, where needed, getting their consent. We process the meeting data to provide Reco to you. For your account, the website and messages sent to us, we decide the purposes ourselves.
6. How the extension gets the audio
On Google Meet pages, a script that is part of the Reco package runs inside the page and reads the audio streams of the call. It reads audio only and changes nothing Meet plays or shows. A second Reco script shows the start notice, estimates speaker activity from visible Meet tiles and attempts to post a chat notice, which may not be delivered. Both work only on meet.google.com and only during a call, and their data goes only to Reco’s service. Where automatic capture is not possible, you click the Reco icon and Chrome lets Reco record the sound of the Meet tab together with your microphone.
7. Chrome extension
- Reco has one purpose: recording and transcribing your Google Meet calls and giving you the notes.
- It uses the data it handles only for that purpose. We do not sell it, use it for advertising, use it to decide creditworthiness or lending, or transfer it to anyone except as needed to provide Reco (section 9), for security, or where the law requires.
- People do not read your meeting content except with your permission (including colleagues you share a meeting with), for security, or where the law requires.
- The permissions Reco asks for, and why, are listed on Privacy & security.
8. How long we keep data
- Meeting audio: deleted as soon as the transcript is saved; if transcription fails, after 72 hours; if transcription is paused because the monthly processing limit is reached, after at most 14 days.
- Audio pieces in your browser: until the service confirms receipt.
- Transcripts, summaries, files and speaker activity: until you delete the meeting.
- Account data: while your account exists. Ask us to delete your account at privacy@recobot.app.
- Security records: as long as needed to keep Reco secure.
- Questions and answers from Ask Reco: not stored.
- Messages: as long as needed to answer them.
9. Who receives data
Reco uses hosting, speech-to-text and AI service providers to process meeting data, and a hosting provider for this website. Sign in with Google is provided by Google, which processes your sign-in under its own privacy policy. We do not sell personal data, and Reco does not send your notes by email or to any other service.
10. International transfers
We are based in the United States, and our providers may process data in the United States and other countries. Where the law requires, we use appropriate safeguards for these transfers, such as standard contractual clauses.
11. Security
Data travels over encrypted connections. Meetings are private to their owner by default; an owner may choose read-only sharing with eligible signed-in colleagues on an allowed company domain. Sign-in sessions end when you sign out and can be revoked.
12. Your rights
Depending on where you live, you can ask for access to your data, correction, deletion, restriction, a copy, or object to processing. You can delete your meetings yourself at app.recobot.app. For anything else, write to privacy@recobot.app. You can complain to your data protection authority.
13. Automated processing
Transcripts and summaries are produced by AI systems. No decision with legal or similarly significant effect on you is made by them.
14. Children
Reco is not meant for children. We do not knowingly process children’s data.
15. Cookies and tracking
The recobot.app website sets no cookies and uses no analytics, advertising or third-party scripts. The meeting page at app.recobot.app uses one secure sign-in cookie to keep you signed in, and Sign in with Google, which is provided by Google. Reco uses no analytics or advertising tracking anywhere.
16. Changes
If we change this policy, we update the date above.
17. Contact
privacy@recobot.app, or by post: OSSA FRAME INC, 237 58th Street, Brooklyn, NY 11220, USA.