Effective date: 2026-10-26
This policy covers the Cloakly mobile apps on the App Store and Google Play (iOS and Android, package id com.cloud52.cloakly). The desktop app, when you supply your own API keys, sends data to the services you choose and is outside this policy.
Other language: 繁體中文. Terms: English. Account deletion: How to delete an account.
Operator: Cloud52
Address: Taiwan
Email: contact@cloud-52.com
"We" means Cloud52. The backend is Supabase. Account and usage data are stored with our cloud provider Supabase, in data centers it operates. The project configuration in this repository does not record a region, so this policy does not name one.
Cloakly is an on-screen meeting assistant. It is not a hidden window and it is not a tool for cheating on interviews or exams. The microphone is used only after you start a meeting.
Before you record, you must tell the other participants and get their agreement, and you must follow the law that applies to the conversation. We do not collect that consent for you and we do not check that you have it.
| Data | When | Where it goes | Why |
|---|---|---|---|
| Email and password | Sign-up, sign-in, and the password check before account deletion | Supabase Auth stores the email and session. Cloakly's own tables have no password column. After sign-in the email is also set on the RevenueCat customer. | Account, confirmation email, subscription identity |
| User ID | Created by Supabase at sign-up | Supabase. The same UUID is the RevenueCat app user id. When a short-lived transcription key is created, user id:meeting session id is sent to Soniox as client_reference_id. |
Account, quota, and subscription |
| Device ID | Free quota and meeting start | iOS reads identifierForVendor. Android reads Settings.Secure.ANDROID_ID. The app prefixes ios: or android: and sends that string to our backend. free_device_claims stores the SHA-256 of that string with the user id and UTC date, not the raw value. |
One phone can spend the free allowance on only one account per UTC day. Not used for ads or cross-app tracking. |
| Microphone audio | After you start a meeting | A recording file stays in the app documents directory. PCM audio is streamed to Soniox at wss://stt-rt.soniox.com/transcribe-websocket (model stt-rt-v5). The mobile app does not upload the audio file into Cloakly's database and does not send audio to OpenAI. |
Live transcript and speaker labels |
| Transcript, notes, answer suggestions, minutes | During and after the meeting | SQLite on the phone (cloakly.db). When you use answer suggestions, minutes, project Q&A, or plan suggestions, the related text is sent to our backend and then to OpenAI. |
Show the content and produce the AI result. The backend does not insert transcript text into Postgres. |
| Excerpts from project files, glossary terms, project background | When you pick a folder or edit those fields | The index stays in on-device preferences. Excerpts are sent only for Q&A, planning, suggestions, or minutes. Glossary terms are included in the Soniox context. | Keep answers and transcription close to the project. Images and charts are not read. |
| Meeting sessions and usage counts | Start, finish, and AI calls | Supabase meeting_sessions, usage_ledger, and free_ai_usage. These rows store plan, seconds, and counts, not the transcript. |
Free quota and Pro entitlement |
| SHA-256 of the email and that day's free usage | Account deletion, or a new sign-up with the same email on the same UTC day | free_quota_carryovers and free_ai_carryovers. The value is a hash of the trimmed, lowercased email, not the email itself. |
Stop a same-day delete-and-re-register from resetting the free allowance |
| Subscription status | Purchase, restore, and store notifications | RevenueCat, and our entitlements row (product id, status, expiry). webhook_events may store the RevenueCat event payload. We do not receive card numbers. |
Decide whether the pro entitlement is active |
Cloakly's own code does not read location, contacts, photos, or the camera, and it does not include an advertising identifier, analytics SDK, or crash-reporting SDK. The iOS file-picker package still compiles photo, camera, and music-picker code, plus code that can read photo location and save into the photo library, so the system requires the matching purpose strings. This app only asks you to choose a folder. It does not open those pickers and it does not collect location. If a meeting happens to include health or other sensitive topics, that is user content you recorded. There is no separate health feature.
iOS file sharing is on. After the device is unlocked, the Files app can show the app documents folder, which may contain recordings and cloakly.db. That lets you take your own files out. It is not an upload to us.
A free account can transcribe up to 1,800 seconds (30 minutes) per UTC day, plus 5 project questions and 5 plan suggestions. Cloakly Pro does not consume those daily caps. Every live transcription session, including Pro, still stops at 30 minutes. There is also a shared daily pool for all free accounts. That is an operations limit, not an advertising setting.
These services process data to provide the product. Re-read their current terms before you submit the app, and update this page if they differ.
api.soniox.com. The phone then opens the WebSocket. Public Soniox documents read on 2026-10-26 say real-time requests are processed transiently, customer content is not used to train models, and operational logs do not contain raw audio or transcripts, though usage records can include client_reference_id. Cloakly does not call the async API that stores audio files. If Soniox's latest terms differ, those terms win and this page should be updated.https://api.openai.com/v1/chat/completions. The default model is gpt-4o-mini, overridable with the server environment variable OPENAI_CHAT_MODEL. The payload is text, not audio. Cloakly does not send content to any other large language model. OpenAI's public API data controls say that data sent to the API is not used to train or improve OpenAI models by default unless the customer explicitly opts in, and that abuse-monitoring logs may include prompts and responses and are retained for up to 30 days for this endpoint, or longer when the law requires it or when that is reasonably necessary to prevent harm. This code does not send a training opt-in and does not request zero data retention. If OpenAI's policy or the project's settings differ, that current policy controls.We do not sell personal information and we do not use this data for cross-app advertising.
delete-account. The function checks the email, tries to delete the RevenueCat subscriber, stores that day's free usage under an email hash, deletes webhook events whose payload contains your user id, then deletes the Supabase user. Account tables cascade from that user.free_device_claims has no foreign key to the user. Account deletion does not remove those rows. What remains is the SHA-256 of the device id, the UTC date, and the id of the deleted user.Steps: Delete an account.
Connections to Supabase, Soniox, OpenAI, and RevenueCat use TLS (HTTPS or WSS). The on-device SQLite database is not encrypted by the app. Use a device passcode. We do not promise that transmission or storage cannot be compromised.
The service is not directed at children. You must be at least 13 years old to create an account. We do not knowingly collect an account from someone under 13.
Supabase, Soniox, OpenAI, RevenueCat, Apple, and Google may process data outside Taiwan and outside your country, in data centers those providers operate. This policy does not name a Supabase region, because the project configuration in this repository does not record one. Where the other services keep data follows their current documentation.
You can delete the account in the app. For access, correction, or deletion when you cannot sign in, email contact@cloud-52.com from the account address. There is no transcript archive on the server to export; the transcript is on your phone. There is no separate web portal for privacy requests.
If the processing changes in a material way, we will update this page and the effective date. Continued use is of the version then published.
Cloud52
contact@cloud-52.com
Taiwan
© 2026 Cloud52