Effective date: 2026-09-18 Contact: q0115643@gmail.com
The public URL for the Google OAuth consent screen and app stores is https://recly.dev/policy/privacy-policy. The technical basis is docs/recly.md §15 (privacy and data flow). 한국어
Recly is a recording app. Recordings are uploaded to your own Google Drive, and what happens next is decided by the workflow you build.
Recly has no servers. There is no backend, no database, and no account system operated by the developer. The app does not send your recordings, transcripts, workflows, or Google account data to the developer. Google and any transcription providers or webhook operators you choose process the data sent to them under their own policies and your account agreements.
| Data | Where it is stored |
|---|---|
| Audio files and metadata (title, timestamps, duration, device name) | Your device, and your own Google Drive if you added an upload step |
| Workflow definitions | On your device only (never sent to Drive) |
| Google access and refresh tokens | Your device’s secure storage (Android Keystore-backed encrypted storage / Apple Keychain / Windows Credential Manager) |
| Webhook signing keys and any STT API keys you enter | The same secure storage. They are not synced between devices and are never sent to Recly (there is no server to receive them). Only if you added a transcription step, that API key is sent straight to the provider you chose, for authentication only (§3(3)). A webhook signing key is never sent at all — it is only used to compute the signature |
| The email address of the Google account you signed in with | On the device only. The Android phone keeps it in secure storage to pick the same account again on the next launch; iPhone and Mac keep the value held by the Google Sign-In SDK as a hint that prefills the next sign-in. Windows stores none. Signing out removes it |
| Execution state (job queue, retries, upload progress) and iPhone transfer permissions | A local database on your device; transfer permissions are not included in workflow exports |
| Diagnostic logs | Your device’s system log. They leave the device only when you export them yourself |
(1) Your Google Drive.
The app writes audio parts and meta.json into a recording folder. It uses only one permission — drive.file (files this app created) — and therefore cannot see your other Drive files. These files are yours and are visible only to you unless you share them.
(2) A webhook address you configured.
Only when you add a webhook step and enter a URL, the app sends one notification to that address. The body contains recording metadata and Drive file links; it does not contain the audio itself or the transcript text.
You choose the endpoint and its operator. Check that operator’s privacy policy before sending recording metadata to it.
(3) A transcription provider you chose — only if you added that step. Transcription (STT) is an optional step you may put into your workflow, not a fixed processing stage. Only when you add such a step and enter your own API key does the device call the provider you selected, directly, with your key.
The supported providers are listed below; availability may depend on your App Store region. What is sent is the same whichever one you pick — one audio track file, and the language and diarization options (the speaker-count hint) that ride on the same request. What happens to it afterwards — retention, training — differs by provider, so read that provider’s own policy before you pick it.
provider in the workflow |
Company | Policy |
|---|---|---|
assemblyai |
AssemblyAI | https://www.assemblyai.com/ |
clova |
NAVER Cloud CLOVA Speech | https://www.ncloud.com/ |
rtzr |
Return Zero (RTZR) | https://www.rtzr.ai/ |
openai |
OpenAI | https://openai.com/ |
groq |
Groq | https://groq.com/ |
together |
Together AI | https://www.together.ai/ |
mistral |
Mistral AI | https://mistral.ai/ |
elevenlabs |
ElevenLabs | https://elevenlabs.io/ |
deepgram |
Deepgram | https://deepgram.com/ |
azure |
Microsoft Azure AI Speech | https://azure.microsoft.com/ |
daglo |
Daglo | https://daglo.ai/ |
speechmatics |
Speechmatics | https://www.speechmatics.com/ |
rev |
Rev AI | https://www.rev.ai/ |
gladia |
Gladia | https://www.gladia.io/ |
(4) Your own paired devices — between watch and phone. When you record on a Galaxy Watch or an Apple Watch, the audio files and their metadata (title, timestamps, duration, checksums) move to the paired phone, because the watch neither uploads nor runs workflows. This transfer happens even when your workflow has no Drive upload step at all. In the other direction, the phone sends the watch a workflow summary — the id and name of each workflow, so the watch can offer a list. The steps inside a workflow are never sent.
There is nothing else. No path other than these four exists by which data leaves your device.
Before a new destination is used, the workflow editor or import confirmation shows the recipient, endpoint, data sent and purpose. Choose Allow & save or Allow & import to authorize future recordings on this device. Existing jobs, including recordings received from Apple Watch, wait for permission and can be continued from Settings → Privacy. Recording itself does not require this permission.
Permission is remembered for the same provider and configured endpoint, independently of API keys and workflow names. Changing the provider or destination, withdrawing permission, using a new device, or materially changing the data or purpose requires permission again. Permission is not exported with workflows. On iPhone it is bound to a device-only Keychain marker, so restoring the database onto a different phone does not restore permission. Withdraw permission stops subsequent requests, including transcription status queries; an already dispatched request may finish. It does not delete data already sent or stored API keys. Google Drive access uses its separate Google authorization flow. Other platforms currently use their existing workflow configuration flow.
App Store region. On iPhone and iPad, Recly reads the current App Store country or region through Apple StoreKit to determine whether the OpenAI transcription integration is available. This integration is disabled for the China mainland storefront. If the region cannot be verified, affected transcription waits. Recly does not send audio, transcripts, workflow definitions or third-party API keys as part of this StoreKit lookup, and does not store the storefront country on disk. Apple manages the underlying account and storefront service. Local recording and Google Drive upload are independent of this check.
drive.file; it does not request profile or contacts scopes. But signing in with Google necessarily tells the app which account it is, and that account’s email address stays on the device — to pick the same account next time, and as described in the §2 table it is not transmitted to Recly or anywhere else.Recly’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Drive data is used only to provide the features you requested (uploading, listing and retrieving your recordings and transcripts), is never used for advertising, and is not read by humans — there is no server that could read it.
127.0.0.1/localhost receiver you configure yourself.~/Library/Application Support/app.recly.mac/, and on Windows in %LOCALAPPDATA%\Recly\ — other programs running under the same user account can read them. What protects them there is the operating system’s user-account permissions (file access control) and, if you have turned it on, disk encryption (FileVault on macOS, BitLocker on Windows). API keys and tokens are not kept with those files; they are in the Keychain and Credential Manager instead.meta.json, local transcript copies) and every record of that recording — not only the recording and part records but the job records too (job and step_run: the copy of the workflow definition that recording ran, the per-step execution state, failure messages, upload and transcription progress, and step outputs). Those are what an earlier build left sitting in the database, invisible in the list; they no longer stay behind. Choosing “also delete the Drive folder” removes that recording’s Drive folder as well.| Platform | Uninstalling | What is left, and how to remove it |
|---|---|---|
| Android phone · Galaxy Watch | App data goes with it — recordings, the local database and the encrypted store holding tokens and API keys all live in the app’s private area and the OS removes them with the app | Nothing. Files in Drive stay, because they are yours |
| iPhone · Apple Watch | The app container (recordings, database, settings and iPhone transfer permissions) is removed | Keychain items can persist after uninstalling. On iPhone, delete each API key and webhook signing key from Workflows → Secrets on this phone, then revoke Google access before uninstalling. Revoking Google access removes Google credentials but does not delete those keys. Recly’s own secret items are device-only. A non-credential permission-binding marker (app.recly.privacy) may also remain; without the deleted local permission records it grants no access. The watch stores an install identifier, with no sign-in or API-key entry; it has no in-app control for deleting that Keychain identifier |
| macOS | Only the .app bundle is removed |
(1) Delete ~/Library/Application Support/app.recly.mac/ (recordings, rec.db, device.id) yourself. (2) In Keychain Access delete the items whose service is app.recly.mac.secrets (the API keys and webhook signing keys you entered) plus the item the Google Sign-In SDK created (the Google token). (3) App settings and the last account’s email hint stay in UserDefaults — recording mode, the consent reminder, language and accessibility settings, plus the email address used to prefill your next sign-in (app.recly.auth.lastAccount). Clear them with defaults delete app.recly.mac in Terminal |
| Windows | Only the installed files are removed | (1) Delete %LOCALAPPDATA%\Recly\ (recordings, rec.db, device.id) yourself. (2) In Credential Manager → Windows Credentials delete the app.recly.windows/tokens/… and app.recly.windows/secrets/… entries. (3) App settings stay in the registry — the consent reminder, language, theme and accessibility settings live under HKCU\Software\JavaSoft\Prefs\app\recly\windows; delete that key in Registry Editor. The Windows app stores no account email, so there is none to remove |
Before uninstalling, delete each saved API key and webhook signing key from the workflow screen’s secret list, then use Revoke Google access in Settings → Google Drive to clear Google credentials and this device’s job records. To remove recordings too, delete individual recordings from the list. To stop future third-party transfers on iPhone, use Settings → Privacy → Withdraw permission. Workflows, settings and desktop data folders remain until separately removed as described above. Data already held by Drive, a transcription provider or a webhook operator is managed separately with that service.
Recly does not, and cannot, automatically notify other participants that a recording is taking place. Laws about recording conversations differ by country and region — for example, Korea permits recording a conversation you are part of but criminalizes recording conversations between others, while several U.S. states and the EU require all-party consent or prior notice. It is your responsibility to know the law that applies to you and to obtain any consent required. Nothing here is legal advice.
So the app asks you once, before a recording starts, whether you told the participants. That reminder is in all four apps — Mac, Windows, iPhone and the Android phone — with the same question, the same body text and the same link to a summary of the rules by jurisdiction. Without a confirmation the recording does not start; choosing “Do not ask again”, or switching the setting off, stops it asking, and you can switch it back on in Settings.
Recly is not directed at children and does not knowingly collect personal information from them — it does not collect personal information at all.
If this policy changes, the effective date above is updated and the change is kept in the repository history. Any change that creates a new path for data to leave the device is also announced inside the app.
q0115643@gmail.com