sayloom.Who this policy covers
Sayloom is developed by Siddhu Bonam. This policy describes the Sayloom website and the current Mac, iPhone, iPad and Android apps. For privacy questions, contact hello@lasyaaitech.com.
Your speech and transcripts
Core speech recognition runs on your device. The Mac app includes local Whisper models and can use supported on-device Apple Speech. iPhone/iPad use supported on-device Apple Speech; Android uses a compatible on-device speech service. Availability depends on the device and installed language assets.
Sayloom does not operate a transcription server for this local workflow. On Mac, you can separately configure and explicitly enable a cloud speech endpoint. If you do, audio is sent to that provider for transcription.
Optional AI writing and context
Mac edition scope: external CLI execution and selected/window/OCR context are Direct-edition features. The sandboxed Mac App Store edition sends only the transcript to its optional configured writing provider and does not gather other apps' context.
Email, Rewrite and other AI writing modes use the provider you configure. On Mac, local Ollama requests go to a loopback service on your computer. A configured HTTPS provider receives the transcript. An explicitly enabled installed CLI is governed by that tool and its configuration.
Mac modes can optionally include selected text, clipboard contents, window text or screen text obtained with OCR. Enabled context is included in the writing request to the chosen provider. Mobile writing modes send the transcript to your configured HTTPS provider; they do not gather Mac window or clipboard context.
Provider retention, training, international processing and account practices are controlled by that provider. Check its privacy terms before enabling it. Sayloom cannot delete copies already sent to a third-party service.
What stays on your device
The apps store history, dictionary replacements and preferences locally. You can disable transcript history and delete saved entries. Mac audio retention is off by default. When enabled, retained recordings can be played or retried; the default retention setting is seven days, and cleanup runs in the app. Deleting the associated history also removes its retained audio.
Recording may use temporary local audio during processing. Temporary capture files are removed by the capture workflow. Mobile does not provide a retained-audio library.
Provider keys use Apple Keychain or Android secure storage backed by Android Keystore. Workspace JSON backups exclude provider secrets. Your own exports, backups and copies in other apps remain under your control.
If you opt in to the iOS transcript keyboard, only the latest completed text, its mode and date are written to a local App Group container shared with the extension. The keyboard reads that result for explicit insertion; it does not record audio, collect host-app keystrokes or receive your provider keys. Keyboard Full Access is required by iOS for this local sharing. Clear this separate copy with Clear in the keyboard, or switch off keyboard sharing in Sayloom Settings. Deleting History does not clear clipboard, exported or shared-keyboard copies.
Permissions and writing into apps
The sandboxed Mac App Store edition records in its own window and uses Copy/Share with manual paste. It does not request Accessibility, monitor global keyboard activity or insert text into other apps. The Mac insertion descriptions below apply to the Direct website edition.
Microphone access is needed to record. Apple Speech authorization is requested on Apple devices when required by the selected engine. Mac Accessibility access enables insertion into the writing target you choose. Optional screen-related context may require its own system authorization.
Sayloom records only after you start dictation. The Mac Direct recorder keeps the original writing target and selection for insertion. Android provides an optional on-device voice keyboard; secure fields are excluded. On iPhone/iPad, recording happens in Sayloom. You can Copy/Share the result, or opt in to local transcript sharing and explicitly insert through the Sayloom keyboard in builds that include it. The iOS keyboard cannot access the microphone or float over other apps. Permissions and keyboard access are approved and revoked in system settings.
Purchases and the offline trial
Apple or Google processes store purchases. Sayloom checks the store entitlement and keeps local purchase/restore information needed to unlock Lifetime Pro. Sayloom does not receive your payment-card number.
The offline ten-use trial keeps a local usage record separately from transcript history. Clearing history or restoring a workspace does not reset this record. Apple uses Keychain; Android uses app-private storage. Reinstall/data/device resets can affect offline protection. There is no Sayloom account or server-backed trial ledger in this build.
Website and hosting
This website does not request microphone access, create Sayloom accounts or process payments. Product examples are illustrative. No advertising or analytics SDK is configured in the website or apps. The site serves its fonts locally.
The hosting provider necessarily handles connection information, such as IP address and browser request metadata, to deliver and protect the website. External links open services with their own policies. This site does not use advertising tracking or set application analytics cookies.
Support messages
If you email support, your email address and the contents or attachments you choose to send are received by the support mailbox. Use only the minimum information needed to explain the issue. Do not send API keys or payment-card details.
Support correspondence is kept while needed to handle the request and related follow-up. You can ask us to delete the correspondence, subject to records we need to keep for applicable obligations. Your email provider and our mailbox provider process those messages.
Deletion and your choices
Delete local history from Sayloom, disable optional retention, remove provider credentials and revoke OS permissions when you no longer need them. Remove your own exported files and backups separately. Contact hello@lasyaaitech.com to ask about information you sent to support.
The apps do not create a Sayloom account, so there is no Sayloom account-deletion workflow. Store accounts and purchases are managed with Apple or Google. Local usage and entitlement records are separate from writing history.
Policy changes
We will update this page when the app’s data practices change. The date at the top identifies the current version. Public release remains subject to final store configuration, distribution and device testing.