You press record
On the phone, the desktop app or the Dot. The Dot shows a red light the whole time; your phone shows the running time on its lock screen. Nothing records unless you start it.
Your device
Privacy policy
What happens to your words.
Recolo writes down what is said around you and turns it into a brain you can ask. This page shows exactly where those words go, who can hear them, and how to take them back. Pictures first, the full wording under each chapter.
- You start every recording. Nothing listens on its own.
- The audio is deleted as soon as it has been written down.
- No ads, no selling, no training AI on your data. Ever.
- Delete anything, or your whole account, from inside the app.
Chapter 01
The life of one recording
Follow a single conversation from the moment you tap record to the moment you ask your brain about it. At each step, the chips say where a copy exists right then.
The audio travels, sealed
When you stop, the file goes to our servers over an encrypted connection (TLS), the same lock your bank uses. A Dot recording first hops to your phone over Bluetooth, then travels the same way.
Your deviceRecolo storage
Voice becomes text
Our service sends the audio, through OpenRouter with zero data retention, to a Google Gemini model that writes down what was said. The transcript is read once more to pull out the summary, decisions, people, dates and to-dos.
Recolo storageAI model, secondsRecolo database
The audio is deleted
As soon as the note has been written down, the recording itself is erased from our storage. The words are what Recolo keeps, not your voice. (A Dot day recording is kept until that day is wrapped up, then goes the same way.)
Recolo storageRecolo database
It rests in your vault
The transcript, the note and everything drawn from it rest in our database in Singapore, encrypted on disk. People, topics and decisions are added to your knowledge graph as names, never as transcripts.
Database · SingaporeGraph · Mumbai
You ask, it answers only you
When you ask your brain a question, the relevant notes are read once by the model to write the answer, then dropped. Nobody but you sees a note unless you choose to share it.
Your screenAI model, seconds
Three things never happen in that journey: the recording is never kept once it has been written down, the model never keeps or learns from your words, and no human at Recolo listens or reads along.
Read the full wording
1. Processing stages
Recolo processes a recording in these stages: capture on your device; encrypted transfer to Recolo's object storage on Google Cloud; transcription and analysis by a third-party model reached through OpenRouter under its Zero Data Retention policy; storage of the resulting transcript and derived fields in Recolo's database; deletion of the source audio once analysis has succeeded; addition of names and relationships to your knowledge graph; and, on request, reading of relevant notes by a model to answer your question or produce a document.
Audio that could not be analysed (for example, an interrupted upload) is retained in object storage for at most 30 days, after which a lifecycle rule deletes it. Audio captured by the Recolo Dot as part of the Today feature is retained until the day has been wrapped up into notes, and is then deleted on the same basis.
Longer recordings are transcribed in chunks, which may be processed in parallel. Chunks above 12 MB are passed to the model provider through a temporary file that is deleted immediately after use.
Chapter 02
What we collect, and why
Only what the product needs to do its job. Here is the whole list, in the order you will meet it.
- Your account: name and email, through Google sign-in or an emailed code. No password unless you choose one; passwords are stored hashed.
- What you capture: recordings, documents, photos and links you add. The audio is deleted after it is written down.
- What Recolo makes from it: transcripts, notes, summaries, to-dos, your knowledge graph, ideas, your Today view, wellbeing readings, chats and Studio drafts.
- Your voice, if you choose: a numerical voiceprint so Recolo knows which words are yours. Encrypted, never the audio itself.
- How the app runs: crash reports and which screens are used, if you leave that switch on. Never your words.
- Billing: your plan, credits used per AI step, and the country you paid from.
Recolo contains no advertising identifiers and no third-party tracking. The website sets no cookies and runs no analytics; its one form stores the email you type to be told when Recolo opens. The dashboard sets one cookie, which keeps you signed in.
Read the full wording
2.1 Information you give us
- Account details: your name and email address, received from Google when you sign in with Google, or typed by you when you sign in with an emailed code. If you set a password it is stored as a salted hash. Recolo uses Firebase Authentication on Google Cloud to issue your sign-in.
- Captured content: audio you record on the phone, the desktop app (microphone and, if you choose, system audio) or the Recolo Dot; documents, photos, PDFs and web links you attach; and text you type or dictate.
- Your vocabulary: names and terms you teach Recolo so it spells them right.
- What you do, if you tell us: your role (for example "teacher" or "doctor") so readings and ideas fit your work.
- Support messages you send to contact@recolomind.ai.
2.2 Information Recolo derives
- Transcripts, titles, categories, summaries, what happened and why it matters, people and organisations named, themes, action items, commitments, decisions, risks and dates.
- Section summaries of long recordings; your knowledge graph (conversations, people, topics, decisions and the links between them); ideas Recolo proposes; briefcase reports; Studio drafts and articles; Workspace documents, slides and sheets; your day as the Today view assembles it; reminders.
- Wellbeing and tone readings: an occasional reading of how your conversations sound (for example tiredness, stress, warmth) computed from your own transcripts. It is shown only to you, it is not a medical assessment, and it is deleted with the notes it was read from.
- Chat history with your brain, including answers produced on your phone in offline mode, which are uploaded afterwards so your history is complete.
2.3 Voice identification (optional)
If you record a short passage, Recolo computes a voiceprint: a list of numbers that describes how your voice sounds. It is used only to label which words in a recording are yours, and, if you add a family member, friend or colleague with their agreement, which are theirs. Voiceprints are encrypted with a key held by Recolo (AES-256-GCM); the audio used to make them is not kept. Tap "Forget my voice" in Profile to delete yours, or a person's entry to delete theirs. Voiceprints are never sold, never shared and never used to identify anyone outside your own recordings.
2.4 Connected apps (optional)
If you connect Google Calendar, Recolo reads your events to name a recording after the meeting it was made in, show your day, brief you before a meeting and, when you tap "Add to calendar" on a reminder, write that one event. If you connect Gmail, Recolo writes a draft follow-up after a named meeting; it does not read your inbox. The connection is brokered by Composio; Recolo keeps only a reference to it, never your Google password or access token. Recolo's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Disconnect any time in Profile → Connected apps.
2.5 Device, usage and billing
- Crash and usage reports: device model, operating system, app version, which screens were opened and which buttons were tapped, and the technical details of a crash. Collected by Firebase Crashlytics and Google Analytics for Firebase only while the "Share crash reports and usage" switch in Profile is on. These reports never contain recordings, transcripts, notes or chat messages.
- Usage ledger: one record per AI step Recolo performs for you (what kind of step, which model, how many tokens, what it cost in credits). This is how credits are counted and how we keep Recolo affordable. It names the note or chat it belonged to, never the content.
- Billing: your plan, payment status and the country of your payment, received from Razorpay. Your card, UPI or bank details stay with Razorpay; Recolo never sees them.
- Region: the country our edge network reports for your connection at sign-in, used only to show the right prices.
- Server logs: for each request, the time, the path, the status and how long it took. Logs hold no content and are kept for 30 days.
- Consent record: the recording promise you agreed to in the app, with its wording, version, date and the platform you agreed on.
2.6 Website and dashboard
recolomind.ai sets no cookies and loads no analytics or advertising scripts. The "Notify me" form stores the email address you type and where you typed it. dashboard.recolomind.ai sets one first-party session cookie to keep you signed in and uses your browser's local storage for your preferences.
2.7 What we do not collect
No precise location. No contacts list. No photos beyond those you attach. No microphone access outside a recording you started. No background listening. No advertising identifiers. No data brokers.
Chapter 03
The AI that reads your words
Recolo does not run its own giant models. Your words are read, once, by models from Google and OpenAI through a single gateway that keeps nothing. Here is exactly how.
- One door. Every AI request leaves through OpenRouter, so there is one place to check and one setting that governs all of it.
- Zero Data Retention. We route only to providers under OpenRouter's ZDR policy: your audio and text are used to produce the answer and not stored afterwards.
- No training. Neither Recolo nor any model provider trains on your data. That is a contract term, not a hope.
- Only what is needed. A question about one note sends that note, not your whole library. A visual sends a summary, not the transcript.
- Offline, nothing leaves. Switch on offline chat and a small model on your phone answers from a copy kept on the phone. Your choice
Which model does what: Google Gemini listens to the recording and writes the transcript, reads it for the summary and the to-dos, weaves your day and finds ideas. OpenAI GPT models answer the harder questions in Ask Brain, type what you dictate, and draw the visuals you ask for. A tiny decision model picks the shape of an answer before it is written. We publish which models we use because you should not have to guess.
Read the full wording
3.1 Providers and routing
All model requests are sent by Recolo's service to OpenRouter, Inc. (United States), which forwards each request to the model's provider: Google (Gemini models) for transcription, analysis, day grouping and idea finding; OpenAI (GPT, GPT Image and Whisper models) for brain chat, dictation and image generation; and TypeSafe (Jev decision models) for short typed decisions such as the size of an answer. Recolo's OpenRouter account is configured for Zero Data Retention, which restricts routing to providers that do not retain prompts or outputs after the response and do not use them for training. Recolo may change models as better or cheaper ones appear; this list is updated when it does.
3.2 What is sent
For transcription: the audio of the recording and your vocabulary list. For analysis: the transcript. For a brain question: your question, the relevant passages Recolo finds in your notes and wiki, and the recent turns of that chat. For a document or visual: the summary or passages you point at. For connected-app features: the calendar event or meeting details involved. Your name and email are not sent to a model unless they appear in the content itself.
3.3 What is not done with your data
Recolo does not train, fine-tune or evaluate machine-learning models on your content. Recolo does not permit its providers to do so. Recolo does not build profiles of you for advertising or sell or rent any data about you.
3.4 On-device models
If you enable offline chat, the app downloads a small open model (Gemma 3 1B or Qwen3 0.6B, verified by size and checksum) or uses Apple's on-device models, and keeps a copy of your notes in a database on your phone. Questions asked in offline mode are answered entirely on the phone. The answers are uploaded to your chat history when you are next online. See Chapter 08.
3.5 Accuracy
Transcripts and AI answers can be wrong, incomplete or misattributed. Recolo shows sources so you can check. Do not rely on an AI answer for a medical, legal, financial or safety decision without checking the source yourself.
Chapter 04
Where your data lives
Three places on the map, and one that only passes through. We tell you the cities, not just the continents.
1
Singapore · Google CloudThe Recolo service and your database (MongoDB Atlas, hosted on Google Cloud). This is where transcripts, notes, chats and your account rest.
2
Mumbai, India · Neo4j AuraYour knowledge graph: the names of conversations, people, topics and decisions and how they connect. No transcripts.
3
United States · in transitAI models read your audio and text here for seconds under zero data retention. Files you attach and images Recolo draws are stored on Google Cloud in the US today, and are moving to Singapore beside the database. Rolling out
Your data crosses borders to be processed. Where the law of your country requires it, that transfer rests on the contractual protections our providers offer (standard contractual clauses or their equivalent) and on the encryption described in the next chapter.
Read the full wording
4.1 Storage locations
- Application service: Google Cloud Run, region asia-southeast1 (Singapore).
- Database: MongoDB Atlas, deployed on Google Cloud in Singapore.
- Knowledge graph: Neo4j Aura, deployed in Mumbai (asia-south1).
- Files (attachments, generated images, audio awaiting transcription): Google Cloud Storage. The current bucket is in the United States (us-central1); a Singapore bucket owned by the production project and encrypted with a Recolo-managed key is being introduced, and new files will be written there once the cut-over completes.
- Encryption keys and secrets: Google Cloud KMS and Secret Manager, in the production project in Singapore.
- AI processing: OpenRouter and its model providers, United States, transient only.
- Crash and usage reports: Google (Firebase), United States.
- Email we send: Google Workspace.
4.2 International transfers
Recolo is operated from India and serves people in India and elsewhere. If you are in the European Economic Area, the United Kingdom or Switzerland, transfers to the providers above rely on the European Commission's standard contractual clauses (or the UK addendum) that those providers offer, together with the technical measures in Chapter 05. You may request a copy of the relevant clauses by email.
Chapter 05
How it is locked
Encrypted on the way, encrypted at rest, and only the service that needs a piece of data can reach it. We also tell you what is still being built.
- On the way: every connection, between your device and Recolo and between Recolo and every provider, is encrypted with TLS. Live
- At rest: Google Cloud, MongoDB Atlas and Neo4j Aura encrypt every disk with AES-256. Live
- Voiceprints are encrypted a second time by Recolo's own key before they are stored. Live
- A second lock on your words: transcripts and notes encrypted inside Recolo's service with a key held in Google Cloud KMS, so even our database host sees scrambled text. Rolling out
- Who can reach it: one service identity per service, secrets in Secret Manager, each request checked against your account. No Recolo person reads your notes to run the product.
If something goes wrong, we say so. If your data were ever exposed, we would tell you without delay, and notify the authorities the law names (in India, CERT-In and the Data Protection Board). Security findings from our own audits are tracked and fixed; we keep the current list and we will publish a summary as a trust page.
Read the full wording
5.1 Technical measures
- Transport encryption (TLS 1.2 or higher) between clients and api.recolomind.ai and between the service and every provider.
- Provider-managed encryption at rest (AES-256) on Google Cloud Storage, MongoDB Atlas and Neo4j Aura.
- Application-layer encryption of voiceprints (AES-256-GCM) with a Recolo-held key.
- Client-side field-level encryption of content fields (transcripts, summaries, notes, chats, documents and about 140 further fields) inside the Recolo service, with the data key wrapped by a Google Cloud KMS key that only the service identity may use. The code is complete and the production switch-on is in progress; this page will drop the "Rolling out" label on the day it is live.
- Per-user scoping of every database query; cross-origin requests restricted to Recolo's own domains; rate limits on sign-in and uploads; uploads checked by size and file signature.
- One dedicated service account per service; secrets held in Secret Manager; no secrets in code or on laptops.
- Sign-in through Firebase Authentication (Google sign-in or emailed code), with session revocation on sign-out and account deletion.
5.2 Organisational measures
- Recolo staff do not access customer content in the course of operating the service. The founder console shows usage and billing per account, not notes. Access to content happens only when you ask for help with a specific item, or where the law compels it, and is limited to what is needed.
- Logs carry no personal content. Client-facing errors name no vendor.
- An internal security dossier reviews the whole system; its findings are tracked to closure.
5.3 Incidents
If a breach affects your personal data, Recolo will notify you without undue delay with what happened, what data was involved and what we are doing, and will notify the relevant authorities within the time the law requires (72 hours under the GDPR; the timelines of the Digital Personal Data Protection Act and CERT-In directions in India).
5.4 No system is perfect
No method of transmission or storage is completely secure. We promise care, speed and honesty, not perfection.
Chapter 06
What we never do
Four promises that do not change with a pricing plan, a partner or a fundraising round.
- No advertising. Recolo has no ads and no advertising identifiers, and never will.
- No selling or renting your data, your voiceprint or anything derived from them, to anyone, for any price.
- No training AI models on your content, by us or by anyone we work with.
- No listening in. No background recording, no wake word, no human review of your notes.
If Recolo were ever sold or merged, this policy would travel with your data: the buyer would be bound by the same promises, and you would be told before anything changed, with the chance to delete your account first.
Read the full wording
Recolo does not sell personal information, does not share it for cross-context behavioural advertising, and does not process it for targeted advertising, as those terms are used in United States state privacy laws. Recolo does not use personal data to train, fine-tune or benchmark machine-learning models and does not permit its processors to do so. Recolo does not make decisions with legal or similarly significant effects about you by solely automated means. In a merger, acquisition or sale of assets, personal data may be transferred to the successor only subject to this policy; you will be notified in the app or by email at least 30 days before any change in how your data is handled.
Chapter 07
The Recolo Dot
A small Bluetooth wearable with a microphone, a button and a red light. It has no Wi-Fi and no internet of its own, which is a privacy feature, not a limitation.
- It records only when you tell it to, with a double tap or from the app, and glows red the whole time so the room can see.
- It keeps the recording in its own memory until your phone pulls it over Bluetooth. Then the Dot's copy is removed.
- It talks to one phone. A Dot is claimed by your phone; another phone cannot read it until you release it.
- No Wi-Fi, no cloud of its own, no microSD card. Everything goes through your phone and then the same journey as any other recording.
The Dot's memory is small (a couple of hours of speech) and it has no way to send audio anywhere but to the phone that claimed it. If you lose the Dot, what is on it is a few recent recordings in a compressed format; release it from the app and it will not pair with your account again.
Read the full wording
7.1 What the Dot holds
The Recolo Dot (Nano) stores recordings as compressed Ogg Opus audio in 2 MB of on-board flash memory until the paired phone has retrieved them, and then deletes them. It holds no account details, no transcripts and no network credentials. It has Bluetooth Low Energy only.
7.2 Pairing
A Dot is claimed by one phone at a time. The claim is stored on the Dot and in your account. Releasing the Dot in the app clears the claim. Bluetooth transfers between the Dot and your phone are not separately encrypted; they take place over a short range and the audio is encrypted from the phone onwards.
7.3 Day recordings
If you let the Dot record your day in stretches for the Today view, each stretch is uploaded like any recording, grouped into events and wrapped up into notes. The audio of those stretches is kept until the day has been wrapped up, and is then deleted.
7.4 The red light and the law
The light is on whenever the microphone is. Do not cover it. You remain responsible for telling the people around you and for following the recording laws where you are (Chapter 09).
Chapter 08
On your phone and laptop
Some of your data lives on your own devices, where we cannot see it and cannot delete it for you. Here is what, and how to clear it.
- Recordings waiting to upload sit in the app's private folder and are removed once the note is registered.
- Offline chat, if you turn it on, keeps a copy of your whole library on the phone so a small model can answer with no connection. Sign out or switch it off and it is removed. Your choice
- Your sign-in is kept in the phone's secure storage, the Mac's keychain, or one dashboard cookie.
- Phone backups (iCloud, Google) may include the offline copy; the model files are excluded. Turn off app backup if you prefer.
Read the full wording
8.1 Phone
The app keeps, in its private sandbox: recordings until they are registered with the service; your session; your profile and preferences; a cache of lists you have viewed; and, only with offline chat enabled, a local database (SQLite) containing your notes, transcripts, section summaries and knowledge graph for the whole library, refreshed on each sync, plus the downloaded model file. "Remove from this phone" in Profile → Offline chat, signing out, or deleting the app removes all of it. The local database may be included in device backups; the model files are excluded.
8.2 Desktop
The Mac and Windows app records to a local folder, encodes the audio and uploads it; local parts are deleted once the upload succeeds. Your session token is stored in the operating system keychain.
8.3 Dashboard
dashboard.recolomind.ai keeps your session in one first-party cookie and your preferences in the browser's local storage. Sign out to clear the session.
Chapter 09
Other people's voices
A recording holds what other people said. They are not Recolo users and did not sign up to this. We take responsibility for their words too, and we ask you to do your part.
- Tell the room. Before you record, say Recolo is on and stop if anyone minds. In many places recording without consent is against the law. You promise this in the app before your first recording.
- Their words get the same protection as yours: same encryption, same zero-retention AI, same no-selling, no-training promise.
- Anyone recorded can ask us to remove what they said. Write to contact@recolomind.ai; we act within 30 days and tell you we did.
- No children. Recolo is for adults, and you must not use it to record children except your own, in your own home.
Recolo treats the other voices in your recordings as personal data we are responsible for, not as a side effect. We minimise what reaches the models, we keep no audio, and we build the controls (notice, deletion, redaction) into the product rather than into footnotes.
Read the full wording
9.1 Legal basis
Recolo processes the personal data of people who appear in your recordings on the basis of your instruction and the legitimate interest of you and Recolo in keeping an accurate record of conversations you took part in, balanced against the interests of those people by the measures in this policy. Where the law of your place requires the consent of the other parties to a recording, obtaining that consent is your responsibility and a condition of using Recolo (see the Terms of use).
9.2 Rights of recorded people
A person who believes they appear in a Recolo recording may ask Recolo to confirm whether a specific recording exists, to correct or remove their words, or to object to the processing. Recolo will act on a verified request within 30 days, may ask the account holder to identify the recording, and will inform the account holder of the removal.
9.3 Children
Recolo is not directed at anyone under 18 and does not knowingly collect personal data from children. If you believe a child's data has reached Recolo, write to us and we will delete it.
Chapter 10
Who else touches your data
Every company that processes your data on our behalf, what it does, what it can see, and where to read its own policy. Nobody else.
Google Cloud
Runs the Recolo service, stores your files, keeps our secrets and encryption keys, and signs you in (Firebase Authentication).
Everything, encrypted on diskSign-in email
Their privacy policy →MongoDB Atlas
The database that holds your notes, transcripts, chats and account. Hosted on Google Cloud in Singapore.
Notes & transcripts, encrypted on disk
Their privacy policy →Neo4j Aura
Keeps the map of how your conversations, people, topics and decisions connect. Names and short descriptions only, never a transcript.
Names of people, topics, decisions
Their privacy policy →OpenRouter
The single door every AI request goes through. We route only to model providers under its Zero Data Retention setting, so your words are not kept after the answer.
Audio while transcribingTranscripts while answering
Their privacy policy →Google Gemini · OpenAI
Gemini transcribes and reads your recordings; OpenAI's GPT models answer harder questions, type what you dictate and draw the visuals you ask for. Neither trains on your data.
Audio or text for that one task
Their privacy policy →Composio
Brokers your Google Calendar and Gmail connection when you switch it on. Recolo keeps only a reference to the connection, never your Google password or token.
Calendar events, Gmail drafts it writes
Their privacy policy →Razorpay
Takes your payment by card, UPI or netbanking. Recolo never sees your card number.
Payment detailsBilling country
Their privacy policy →Firebase Crashlytics & Analytics
Tells us when the app crashes and which screens get used. Switch it off in Profile → Help improve Recolo. Never contains your recordings or notes.
Device model, app version, screen names
Their privacy policy →Google Workspace
Sign-in codes, receipts and the rare service notice come from our own Google Workspace account.
Your email address
Their privacy policy →Each of these companies is a processor: it acts on our written instructions, may use your data only to provide its service to us, and is bound by its own security commitments. Apple and Google also see the usual app store data when you install Recolo, under their own policies. We share data with nobody else, except as the law requires (Chapter 13).
Read the full wording
10.1 Categories of recipients
- Infrastructure: Google Cloud (compute, storage, key management, authentication), MongoDB, Inc. (database), Neo4j, Inc. (graph database).
- AI processing: OpenRouter, Inc. and, through it, Google, OpenAI and TypeSafe, under Zero Data Retention.
- Integrations you authorise: Composio, Inc. for Google Calendar and Gmail.
- Payments: Razorpay Software Pvt. Ltd.
- Diagnostics: Google (Firebase Crashlytics and Google Analytics for Firebase), only while enabled by you.
- Email delivery: Google Workspace.
- Distribution: Apple App Store and Google Play, under their own terms.
- People you choose: when you share a note, a section of your brain or a prompt, the recipient receives a copy that is theirs to keep.
- Legal: authorities, where a law or court order compels disclosure; we will tell you unless the law forbids it.
Chapter 11
Deleting, and what deletion really erases
Delete a note and it is gone from the database, the files and your graph. Delete your account and everything goes. Here is the honest list of what remains, and for how long.
| What | Kept until | Then |
|---|---|---|
| The recording (audio) | It has been written down. Minutes, usually. | Deleted from storage. 30-day safety net if analysis failed. |
| Dot day recordings | The day is wrapped up into notes. | Deleted. |
| Notes, transcripts, chats, documents, ideas, graph | You delete them, or your account. | Deleted from the database, storage and the graph. |
| Background job results | 7 days after the job finishes. | Deleted automatically; also deleted with your account. |
| Voiceprints | You tap "Forget my voice", remove a person, or delete your account. | Deleted. |
| Offline copy on your phone | You sign out, switch offline chat off, or delete the app. | Removed by the app. We cannot reach your phone. |
| Things you shared | The recipient deletes them. | Like a sent email: their copy is theirs. |
| Usage and billing ledger | As long as accounts law requires. | Unlinked from your identity when your account is deleted; no content inside. |
| Server logs | 30 days. | Deleted automatically. |
| Waitlist email | Recolo opens, or you ask. | Deleted. |
How to delete: swipe a note away, or open Profile → Delete account. Account deletion runs immediately and cannot be undone. You can also email contact@recolomind.ai and we will do it for you.
Read the full wording
11.1 Account deletion
Deleting your account removes your notes, transcripts, section summaries, documents, chats, ideas, briefcase items, Studio drafts, Workspace documents, wiki pages, day logs and segments, reminders, wellbeing readings, voiceprints and registered people, vocabulary, prompts and marketplace listings, connections, background jobs, consent records, every file you own in storage, your knowledge graph and your sign-in. Shares you sent or received are removed from your side; a recipient's accepted copy stays with them. Payment records and the usage ledger are kept as accounting law requires, with the link to your identity removed.
11.2 Backups
Where a provider keeps short-term backups of the database, deleted data leaves those backups as they roll off, within 35 days. Backups are never used to restore an individual's deleted data.
Chapter 12
Your rights, and how to use them
Most of them are buttons in the app. The rest is one email away, answered by a person.
- See: everything Recolo holds is in the app, the dashboard and your brain. Ask us for a copy in a machine-readable file.
- Correct: edit a note, rename a conversation, fix a transcript, teach Recolo a spelling.
- Delete: a note, a person, your voice, your account (Chapter 11).
- Switch off: crash reports, connected apps, offline chat, voice ID, day recording. Each is a switch in Profile.
- Object or complain: write to us, and if you are not satisfied, to your data protection authority.
Recolo is the data fiduciary under India's Digital Personal Data Protection Act and the data controller under the GDPR where it applies. Our grievance and data protection contact is the founder, Jaydeep Chakrabarty, at contact@recolomind.ai. We acknowledge requests within 3 working days and act within 30 days; if a request is complex we tell you why and when.
Read the full wording
12.1 Everyone
You may access your data, obtain a copy, correct it, delete it, withdraw a consent you gave (without affecting what was done before), object to or restrict processing, and nominate someone to exercise these rights for you. Exercising a right costs nothing and never affects the service you receive.
12.2 India
Under the Digital Personal Data Protection Act, 2023 you may also make a complaint to the Data Protection Board of India after you have raised it with us. Our grievance officer is named above.
12.3 European Economic Area, United Kingdom and Switzerland
Our legal bases are: performance of our contract with you (providing Recolo); your consent (voice identification, connected apps, crash reports, offline chat); our legitimate interests (securing the service, preventing abuse, improving the product from aggregate usage) and yours and ours in an accurate record of your conversations (Chapter 09); and legal obligations (accounting records). You may lodge a complaint with your supervisory authority.
12.4 United States
Residents of states with privacy laws (including California, Virginia, Colorado, Connecticut, Utah, Oregon and Texas) may access, delete, correct and port their data and opt out of sales, sharing and targeted advertising. Recolo does not sell or share personal information or use it for targeted advertising or profiling with significant effects, so there is nothing to opt out of. You may appeal a decision by replying to our response; we answer appeals within 45 days.
12.5 Verifying who is asking
To protect your data we verify requests through the email address on the account, or through a signed-in action in the app.
Chapter 13
The legal part
Who we are, what this policy covers, when it changes and how to reach us.
- Who: Recolo, operated from Bengaluru, India, at recolomind.ai.
- Covers: the Recolo apps for iPhone, Android, Mac and Windows, the Recolo Dot, dashboard.recolomind.ai, recolomind.ai and our support channels.
- Changes: we update this page and its date; for anything that matters we tell you in the app or by email first, at least 30 days ahead.
- Contact: contact@recolomind.ai. A person answers.
Read the full wording
13.1 Who is responsible
This policy is issued by Recolo ("Recolo", "we", "us"), the operator of recolomind.ai and the Recolo apps and devices, based in Bengaluru, India. Recolo is the data fiduciary (India) and data controller (GDPR) for the personal data described here.
13.2 Scope
This policy covers personal data processed through the Recolo mobile apps, desktop apps, the Recolo Dot and its companion features, the dashboard at dashboard.recolomind.ai, the website at recolomind.ai, our connectors for Claude and ChatGPT, and your communications with us. It does not cover third-party sites or services you reach through links; they have their own policies.
13.3 Legal disclosures
We may disclose personal data where required by law, regulation, legal process or an enforceable governmental request; to protect the rights, property or safety of Recolo, our users or the public; or to detect, prevent or address fraud, security or technical issues. We will notify you of such requests unless legally prohibited, and we challenge requests we believe are overbroad.
13.4 Changes to this policy
We will post changes here with a new "Last updated" date. For changes that materially affect how your data is handled, we will notify you in the app or by email at least 30 days before they take effect, and you may delete your account before then. Continued use after that date means you accept the updated policy.
13.5 Contact
Recolo · Bengaluru, India · contact@recolomind.ai. Grievance and data protection contact: Jaydeep Chakrabarty, Founder.
Questions, requests or a worry about your data?
Write to us and a person answers. Privacy requests are acknowledged within 3 working days and acted on within 30 days.